Wikifunctions wikifunctionswiki https://www.wikifunctions.org/wiki/Wikifunctions:Main_Page MediaWiki 1.47.0-wmf.2 first-letter Media Special Talk User User talk Wikifunctions Wikifunctions 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 Event Event talk 0 249 275688 215683 2026-05-17T06:39:06Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275688 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1023" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mak" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Makasar" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "マカッサル語" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Makassar" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Makassaars" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Makasar" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "मकास्सरी" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "makassar" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } l1wtd8pc4bv1bu9bl985mtypvq2bdvr 0 352 275723 150588 2026-05-17T09:05:08Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275723 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1126" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "crh-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Crimean Tatar (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1126", "Z11K2": "qırımtatarca (Latin)‎" }, { "Z1K1": "Z11", "Z11K1": "Z1592", "Z11K2": "krimtatariska (latinska tecken)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Krimtatarisch (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Krim-Tataars (Latijns schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "クリミア・タタール語（ラテン文字）" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "tatar de Crimée en écriture latine" }, { "Z1K1": "Z11", "Z11K1": "Z1237", "Z11K2": "Kırım Tatarcası (Latin alfabesi)" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "tatar de Crimée (latin)" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 8s3540flsydy8tq891n02rbel3p21mh 0 408 275697 243111 2026-05-17T07:03:39Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275697 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1182" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "ksh" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Colognian" }, { "Z1K1": "Z11", "Z11K1": "Z1182", "Z11K2": "Kölsch " }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Kölsch" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Keuls" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "kölsch" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "colognais" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "West-Germaanse taal" } ] } } 0xg93la9gg1jv1cfjsgbhlygccmcxeg 0 418 275694 215763 2026-05-17T06:56:35Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275694 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1192" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "gom-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Goan Konkani (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1192", "Z11K2": "Gõychi Konknni" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Goa-Konkani (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Goan Konkani (Latijns schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "ゴア・コンカニ語（ラテン文字）" }, { "Z1K1": "Z11", "Z11K1": "Z1005", "Z11K2": "гоанский конкани (латиница)" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "गोवा कोंकणी (लातिन लिपि)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "konkani de Goa en écriture latine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1005", "Z31K2": [ "Z6", "конкани (Гоа) (латиница)" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } awyzwz4mmvo0g7rodl9bv9ku5fxafc4 0 423 275695 215558 2026-05-17T06:57:32Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275695 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1197" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "as" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Assamese" }, { "Z1K1": "Z11", "Z11K1": "Z1197", "Z11K2": "অসমীয়া" }, { "Z1K1": "Z11", "Z11K1": "Z1592", "Z11K2": "assamesiska" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "অসমীয়া" }, { "Z1K1": "Z11", "Z11K1": "Z1012", "Z11K2": "ആസാമീസ്" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "アッサム語" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Assamesisch" }, { "Z1K1": "Z11", "Z11K1": "Z1657", "Z11K2": "ਆਸਾਮੀ" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Assamees" }, { "Z1K1": "Z11", "Z11K1": "Z1083", "Z11K2": "آسامی" }, { "Z1K1": "Z11", "Z11K1": "Z1005", "Z11K2": "ассамский" }, { "Z1K1": "Z11", "Z11K1": "Z1237", "Z11K2": "Assamca" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "असमिया" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "assamais" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } t3c3l3bxaa1ax9erl42hy924j2c8y4q 0 424 275696 216254 2026-05-17T06:58:04Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275696 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1198" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nwc" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Classical Newari" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Klassisches Newari" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "klassiek Newaars" }, { "Z1K1": "Z11", "Z11K1": "Z1005", "Z11K2": "классический неварский" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "शास्त्रीय नेवारी" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "newari classique" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } svx8z9fwfhdmliidmplc1xxos0u7koh 0 447 275501 264155 2026-05-16T12:05:48Z Ameisenigel 44 275501 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1221" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nan", "Z60K2": [ "Z6", "zh-min-nan" ] }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Minnan" }, { "Z1K1": "Z11", "Z11K1": "Z1221", "Z11K2": "閩南語 / Bân-lâm-gú" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "মিন নান চীনা" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Nan" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Minnan" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "閩南語" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "minnan" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Min Selatan" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "闽南语" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "閩南語" }, { "Z1K1": "Z11", "Z11K1": "Z1005", "Z11K2": "южноминьский" }, { "Z1K1": "Z11", "Z11K1": "Z1592", "Z11K2": "minnan" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "मिन-नान" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1078", "Z31K2": [ "Z6", "Tionghoa Min Selatan" ] }, { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Min-nan", "Southern Min", "Min Nan", "Minnan Chinese", "Min-nan Chinese", "Min Nan Chinese" ] }, { "Z1K1": "Z31", "Z31K1": "Z1011", "Z31K2": [ "Z6", "চীনা (মিন নান)" ] }, { "Z1K1": "Z31", "Z31K1": "Z1430", "Z31K2": [ "Z6", "Minnan Chinesisch", "Min Nan", "Min Nan Chinesisch" ] }, { "Z1K1": "Z31", "Z31K1": "Z1157", "Z31K2": [ "Z6", "Minnanyu" ] }, { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "sud-foukiénois", "min méridionnal" ] }, { "Z1K1": "Z31", "Z31K1": "Z1820", "Z31K2": [ "Z6", "मिन-नान चीनी" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "use Z1892/nan-hant, Z1501/nan-latn-pehoeji, Z1922/nan-latn-tailo instead" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "इसके बजाय Z1892/nan-hant, Z1501/nan-latn-pehoeji, Z1922/nan-latn-tailo का प्रयोग करें।" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "für missbilligtes zh-min-nan, verwende stattdessen Z1892/nan-hant, Z1501/nan-latn-pehoeji, Z1922/nan-latn-tailo; vermeide die Verwendung von Z1221/nan ohne spezifiziertes Schriftsystem" } ] } } 2z62wmr3qs3h1fspr1lv1f6b0isp0j1 275691 275501 2026-05-17T06:44:48Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275691 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1221" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nan", "Z60K2": [ "Z6", "zh-min-nan" ] }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Minnan" }, { "Z1K1": "Z11", "Z11K1": "Z1221", "Z11K2": "閩南語 / Bân-lâm-gú" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "মিন নান চীনা" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Nan" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Minnan" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "閩南語" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "minnan" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Min Selatan" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "闽南语" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "閩南語" }, { "Z1K1": "Z11", "Z11K1": "Z1005", "Z11K2": "южноминьский" }, { "Z1K1": "Z11", "Z11K1": "Z1592", "Z11K2": "minnan" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "मिन-नान" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1078", "Z31K2": [ "Z6", "Tionghoa Min Selatan" ] }, { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Min-nan", "Southern Min", "Min Nan", "Minnan Chinese", "Min-nan Chinese", "Min Nan Chinese" ] }, { "Z1K1": "Z31", "Z31K1": "Z1011", "Z31K2": [ "Z6", "চীনা (মিন নান)" ] }, { "Z1K1": "Z31", "Z31K1": "Z1430", "Z31K2": [ "Z6", "Minnan Chinesisch", "Min Nan", "Min Nan Chinesisch" ] }, { "Z1K1": "Z31", "Z31K1": "Z1157", "Z31K2": [ "Z6", "Minnanyu" ] }, { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "sud-foukiénois", "min méridional" ] }, { "Z1K1": "Z31", "Z31K1": "Z1820", "Z31K2": [ "Z6", "मिन-नान चीनी" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "use Z1892/nan-hant, Z1501/nan-latn-pehoeji, Z1922/nan-latn-tailo instead" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "इसके बजाय Z1892/nan-hant, Z1501/nan-latn-pehoeji, Z1922/nan-latn-tailo का प्रयोग करें।" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "für missbilligtes zh-min-nan, verwende stattdessen Z1892/nan-hant, Z1501/nan-latn-pehoeji, Z1922/nan-latn-tailo; vermeide die Verwendung von Z1221/nan ohne spezifiziertes Schriftsystem" } ] } } 0094ah4up181llbsjk3pegbqjmxgq9s 0 727 275502 274505 2026-05-16T12:07:21Z Ameisenigel 44 275502 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1501" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nan-latn-pehoeji", "Z60K2": [ "Z6", "nan-hntl-pehoeji" ] }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Minnan (Pe̍h-ōe-jī)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Nan (Pe̍h-ōe-jī)" }, { "Z1K1": "Z11", "Z11K1": "Z1501", "Z11K2": "Bân-lâm-gú (Pe̍h-ōe-jī)" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "闽南语（白话字）" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "閩南語（白話字）" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Min-nan (Pe̍h-ōe-jī)", "Southern Min (Pe̍h-ōe-jī)", "Min Nan (Pe̍h-ōe-jī)" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } lznt5q1txekybdigu2wh2oaosi9qz60 0 745 275733 180850 2026-05-17T09:20:05Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275733 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1519" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "se" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Northern Sami" }, { "Z1K1": "Z11", "Z11K1": "Z1519", "Z11K2": "davvisámegiella" }, { "Z1K1": "Z11", "Z11K1": "Z1592", "Z11K2": "nordsamiska" }, { "Z1K1": "Z11", "Z11K1": "Z1005", "Z11K2": "северносаамский" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "北部サーミ語" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Nordsamisch" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Noord-Samisch" }, { "Z1K1": "Z11", "Z11K1": "Z1643", "Z11K2": "북부 사미어" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "same du Nord" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } s13noilot112nelad56r7cwvzwmmmmg 0 873 275503 200241 2026-05-16T12:08:52Z Ameisenigel 44 275503 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1647" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nan-hani" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Minnan (Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "মিন নাম (হাঞ্জি)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Nan (Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Minnanyu (Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Min Selatan (Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "闽南语（汉字）" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "閩南語（漢字）" }, { "Z1K1": "Z11", "Z11K1": "Z1647", "Z11K2": "閩南語（漢字）/ 闽南语（汉字）" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Min-nan (Han script)", "Southern Min (Han script)" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "use Z1892/nan-hant instead" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "verwende stattdessen Z1892/nan-hant" } ] } } 9rpa5lm17mqo7m5rhlt5lih16mna0fh 275725 275503 2026-05-17T09:07:56Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275725 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1647" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nan-hani" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Minnan (Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "মিন নাম (হাঞ্জি)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Nan (Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Minnanyu (Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Min Selatan (Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "闽南语（汉字）" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "閩南語（漢字）" }, { "Z1K1": "Z11", "Z11K1": "Z1647", "Z11K2": "閩南語（漢字）/ 闽南语（汉字）" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "minnan en sinogrammes" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Min-nan (Han script)", "Southern Min (Han script)" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "use Z1892/nan-hant instead" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "verwende stattdessen Z1892/nan-hant" } ] } } d8agpbvj8bpeboeh888hdxdyev34tu0 0 895 275726 210359 2026-05-17T09:08:27Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275726 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1669" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "sh-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Serbo-Croatian (Latin)" }, { "Z1K1": "Z11", "Z11K1": "Z1669", "Z11K2": "srpskohrvatski (latinica)" }, { "Z1K1": "Z11", "Z11K1": "Z1592", "Z11K2": "serbokroatiska (latinska tecken)" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "সার্বো-ক্রোয়েশীয় (লাতিন)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Servo-Kroatisch (Latijns schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Serbokroatisch (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "セルボ・クロアート語（ラテン文字）" }, { "Z1K1": "Z11", "Z11K1": "Z1181", "Z11K2": "српскохрватски (латиница)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "serbo-croate en écriture latine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 3ztgrfzeympc9c7tkbcn4jkuj7wzu4c 0 896 275727 46094 2026-05-17T09:09:03Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275727 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1670" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "phn-phnx" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Phoenician (Phoenician script)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Phönizisch (phönizische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Fenicisch (Fenicisch schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "フェニキア語（フェニキア文字）" }, { "Z1K1": "Z11", "Z11K1": "Z1592", "Z11K2": "feniciska (feniciska tecken)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "phénicien en écriture phénicienne" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } mayrusj6bvar0ylzbgyejmaxcb1do11 0 918 275728 180857 2026-05-17T09:11:09Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275728 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1692" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "hrx" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Hunsrik" }, { "Z1K1": "Z11", "Z11K1": "Z1692", "Z11K2": "Hunsrik" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Riograndenser Hunsrückisch" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Hunsrik" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "hunsrik" }, { "Z1K1": "Z11", "Z11K1": "Z1643", "Z11K2": "훈스리크어" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "riograndenser hunsruckisch" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "dialect of German, spoken in parts of Brazil" } ] } } 2a2f9ouyv9z0jb5pymt2iwx9093gcq0 0 919 275729 45670 2026-05-17T09:13:05Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275729 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1693" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "ki" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Kikuyu" }, { "Z1K1": "Z11", "Z11K1": "Z1693", "Z11K2": "Gĩkũyũ" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Kikuyu" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Gikuyu" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "キクユ語" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "kikuyu" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "kikouyou", "gikuyu" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } q2ph6pe564i1tbgsw1vxzkevu240eer 0 925 275730 215785 2026-05-17T09:14:24Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275730 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1699" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "kk-arab" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Kazakh (Arabic script)" }, { "Z1K1": "Z11", "Z11K1": "Z1699", "Z11K2": "قازاقشا (تٴوتە)‏" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "কাজাখ (আরবি লিপি)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Kasachisch (arabische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Kazachs (Arabisch schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "カザフ語（アラビア文字）" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "kazakh en écriture arabe" }, { "Z1K1": "Z11", "Z11K1": "Z1237", "Z11K2": "Kazakça (Arap alfabesi)" }, { "Z1K1": "Z11", "Z11K1": "Z1181", "Z11K2": "казашки (арапско писмо)" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "कज़ाख़ (अरबी लिपि)" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "kazakh (arabe)" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 7n47he4zq5zxopxgsgzd40qjtjhu1kv 0 1096 275732 188302 2026-05-17T09:19:32Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275732 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1870" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "se-fi" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Northern Sami (Finland)" }, { "Z1K1": "Z11", "Z11K1": "Z1870", "Z11K2": "davvisámegiella (Suoma bealde)" }, { "Z1K1": "Z11", "Z11K1": "Z1592", "Z11K2": "finländsk nordsamiska" }, { "Z1K1": "Z11", "Z11K1": "Z1005", "Z11K2": "северносаамский (Финляндия)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Noord-Samisch (Finland)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Nordsamisch (Finnland)" }, { "Z1K1": "Z11", "Z11K1": "Z1643", "Z11K2": "북부 사미어(핀란드)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "same du Nord (Finlande)" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1592", "Z31K2": [ "Z6", "nordsamiska (Finland)" ] }, { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "se-fi" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } fkpbvo43mclf4544j08bp222oq5or25 0 1097 275731 188303 2026-05-17T09:19:13Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275731 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1871" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "se-no" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Northern Sami (Norway)" }, { "Z1K1": "Z11", "Z11K1": "Z1871", "Z11K2": "davvisámegiella (Norgga bealde)" }, { "Z1K1": "Z11", "Z11K1": "Z1592", "Z11K2": "norsk nordsamiska" }, { "Z1K1": "Z11", "Z11K1": "Z1005", "Z11K2": "северносаамский (Норвегия)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Noord-Samisch (Noorwegen)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Nordsamisch (Norwegen)" }, { "Z1K1": "Z11", "Z11K1": "Z1643", "Z11K2": "북부 사미어(노르웨이)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "same du Nord (Norvège)" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1592", "Z31K2": [ "Z6", "nordsamiska (Norge)" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 0il4k5tgso1uf0ygti5ic0q1m0mearn 0 1119 275507 274506 2026-05-16T12:10:25Z Ameisenigel 44 de 275507 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1893" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nan-latn", "Z60K2": [ "Z6", "nan-hntl" ] }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Minnan (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1893", "Z11K2": "Bân-lâm-gú (Lô-má-jī)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Minnanyu (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Nan (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Min Selatan (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "閩南語（羅馬字）" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1672", "Z31K2": [ "Z6", "閩南語（拉丁文字）" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "use Z1501/nan-latn-pehoeji, Z1922/nan-latn-tailo instead" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "verwende stattdessen Z1501/nan-latn-pehoeji, Z1922/nan-latn-tailo" } ] } } 7en463gv7vzjp9zl0dq6uuooq12jqpw 0 1126 275736 274611 2026-05-17T10:09:11Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275736 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1900" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "wuu-hant" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Wu (Traditional Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z1900", "Z11K2": "吳語（正體）" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "উ (ঐতিহ্যবাহী হান)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Wu (traditioneel Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Wu (traditionelles Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Wu (Han tradisional)" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "吳語（繁體）" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "吴语（繁体）" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "wu en sinogrammes traditionnels" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } h1wxroqfe61rz7h7r59kycpve2zib87 0 1127 275737 214238 2026-05-17T10:11:58Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275737 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1901" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "yue-hans" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Cantonese (Simplified Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z1901", "Z11K2": "粵语（简体）" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Kantonees (vereenvoudigd Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Kantonesisch (vereinfachtes Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Kanton (Han sederhana)" }, { "Z1K1": "Z11", "Z11K1": "Z1643", "Z11K2": "광둥어(간체 한자)" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "Cantonese (Han Semplificato)" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "粵語（簡體）" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "cantonais en sinogrammes simplifiés" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } jey1e2pps6zu1v8xgvnri3fnb54456r 0 1128 275738 214237 2026-05-17T10:12:26Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275738 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1902" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "yue-hant" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Cantonese (Traditional Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z1902", "Z11K2": "粵語（繁體）" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Kantonees (traditioneel Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Kantonesisch (traditionelles Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Kanton (Han tradisional)" }, { "Z1K1": "Z11", "Z11K1": "Z1643", "Z11K2": "광둥어(번체 한자)" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "Cantonese (Han Tradizionale)" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "粵語（繁體）" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "cantonais en sinogrammes traditionnels" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } br5hh664txtzvj2zpwzzqjbi3nde1lu 0 1130 275739 165252 2026-05-17T10:13:12Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275739 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1904" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "cpx-hant" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Puxian (Traditional Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z1904", "Z11K2": "莆仙語（繁體）" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "পুক্সীয় (ঐতিহ্যবাহী হান)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Puxian (traditioneel Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Puxian (traditionelles Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "莆仙语（繁体）" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "莆仙語（繁體）" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "puxian en sinogrammes traditionnels" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } bguu3ivh4lr4zcad04mfc985nux4q6j 0 1131 275741 165253 2026-05-17T10:13:31Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275741 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1905" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "cpx-hans" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Puxian (Simplified Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z1905", "Z11K2": "莆仙语（简体）" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Puxian (vereenvoudigd Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Puxian (vereinfachtes Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "莆仙语（简体）" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "莆仙語（簡體）" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "puxian en sinogrammes simplifiés" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } mq112noak4ey8u682nvue91n48pavnc 0 1132 275742 165256 2026-05-17T10:13:47Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275742 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1906" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "cpx-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Puxian (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1906", "Z11K2": "Pó-sing-gṳ̂ (Hing-hua̍ Báⁿ-uā-ci̍)" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Puxian (Hinghwa-geromaniseerd)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Puxian (Hinghwa romanisiert)" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "莆仙语（兴化平话字）" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "莆仙語（興化平話字）" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "puxian en écriture latine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 1c759qukng2zspjm3yqsx1gpub4khm2 0 1134 275743 72751 2026-05-17T10:16:01Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275743 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1908" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "bug-bugi" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Buginese (Lontara script)" }, { "Z1K1": "Z11", "Z11K1": "Z1908", "Z11K2": "ᨅᨔ ᨕᨘᨁᨗ" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Boeginees (Lontara schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "ブギス語（ロンタラ文字）" }, { "Z1K1": "Z11", "Z11K1": "Z1592", "Z11K2": "buginesiska (lontara-tecken)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Buginesisch (Lontara-Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1237", "Z11K2": "Bugice (Lontara alfabesi)" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Bugis (aksara Lontara)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "bouguinais en écriture lontara" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1078", "Z31K2": [ "Z6", "Bugis (Lontara)" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "bahasa alami" } ] } } 7nu1tw9grds3xq66kdd9txt0mgordll 0 1135 275744 72750 2026-05-17T10:16:16Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275744 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1909" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "bug-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Buginese (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1909", "Z11K2": "Basa Ugi" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Boeginees (Latijns schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "ブギス語（ラテン文字）" }, { "Z1K1": "Z11", "Z11K1": "Z1592", "Z11K2": "buginesiska (latinska tecken)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Buginesisch (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Bugis (aksara Latin)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "bouguinais en écriture latine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "bahasa alami" } ] } } 3s0m3bxxsvslyq6sfswdl5w148jm7gl 4 1184 275535 275087 2026-05-16T16:48:41Z JJPMaster 6409 /* Z34510 */ new section 275535 wikitext text/x-wiki {{shortcut|[[WF:CHAT]]|[[WF:PC]]|[[WF:VP]]}} __NEWSECTIONLINK__ [[Category:Help]] <!-- please do not remove this line --> Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc. Other places to find help: * [[Wikifunctions:Administrators' noticeboard]] * [[Wikifunctions:Report a technical problem]] * [[Wikifunctions:FAQ]] {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |timeout=30 }} {{Archives|{{#tag:div|<br />{{Flatlist|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1|hideredirects=1}} |class=mw-collapsible-content|style=font-size:92%;}}|class="mw-collapsible mw-collapsible-toggle mw-collapsed"}} |prefix=WF:Project chat/Archive/ }} == "language" argument for certain functions == Hello. I am relatively new to Wikifunctions. Recently, I tried to create functions for Chinese translation of {{Z|Z26570}} and {{Z|Z26095}} (which became [[Z32788]] and [[Z32900]]). During the creation of these functions, I was trying to take {{Z|Z32212}} as reference. And I realized that the defining role sentence function is taking <code>language</code> as an argument (and the test case of the Chinese-language function already contains two varieties of Chinese). This makes it possible to output monolingual text in <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code>, or any varieties of the language. I think for this reason, it is better to have <code>language</code> as arguments for the implementation of Z26570 and Z26095, and potentially more functions that require {{Z|Z14294}}, since it would output the varieties code instead of just saying <code>zh</code> for <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code> in the output of type {{Z|Z11}}. I am not sure how the fallback mechanism works if one of the language (varieties) do not have a labels/lexemes, but to me, it is reasonable to have a <code>language</code> argument. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 09:38, 31 March 2026 (UTC) :The functions you mention do have a language argument. For Wikifunctions, the {{Z|Z60}} can be at a higher or lower level; whether a {{Z|Z11}} is for a language or a variant is determined by the function that constructs it. Please see {{Z|Z26565}} for an example and feel free to add test cases in Chinese. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:54, 11 April 2026 (UTC) ::Hello @[[User:GrounderUK|GrounderUK]], thanks for the answer. I understand that whether {{Z|Z11}} is for a language or a variant depends on the function. But that is exactly what I am asking for. It is true that [[Z26570]] and [[Z26095]] takes [[Z60]] as argument, but the language-specific functions in {{Z|Z29843}} and {{Z|Z26096}} don't. ::Let me give you an example: INPUT to [[Z26570]]: <code>entity</code>: Tokyo, <code>class</code>: city, <code>location</code>: Japan, <code>language</code>: zh-cn, the config would select [[Z33030]] (created after my previous comment by elseone) as the implementation, and it would RETURN 东京是日本的一个城市。(zh-hans), which is not zh-cn as requested in the INPUT. It would also be using the term not for the variant (when it is different) because it is hardcoded to use the term in zh-hans. However, if we have the implementation like [[Z32790]] (which was created by me but a natural language argument was added by elseone) or [[Z32213]] (that works in the defining role sentence function because of the extra argument), it could cater for different variant. ::If we don't have the language argument in the language-specific function, the desire for article creation on Abstract Wikipedia would be to create a function for every variant. Is it then better to create functions for every variant? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:18, 11 April 2026 (UTC) :::I forgot to mention that there are some hardcoding in {{Z|Z32790}} as well, but I cannot fix it because it is a connected function and I am not a functioneer. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:31, 11 April 2026 (UTC) ::::Okay, I think it’s safe to disconnect this one as the function is not yet configured for use on Abstract Wikipedia. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:04, 11 April 2026 (UTC) :::Ah, sorry… I misunderstood you. I agree that the called function should be able to accept the original language argument. That is simpler in theory than in practice, because the configured functions all have to have the same argument types, as I understand it. I’m not sure which the best approach is, really, but we probably want to avoid two levels of configuration. That suggests that all language-specific functions would need to accept the additional argument, which is unrewarding work for someone. @[[User:99of9|99of9]], @[[User:Jdforrester (WMF)|Jdforrester (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]] Any thoughts? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:57, 11 April 2026 (UTC) ::::I mean, we would need to modify all the functions in each language, which could take some time. But we are still in an early stage. If we don't fix it now and we want to fix it later, it would be a disaster. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 19:25, 11 April 2026 (UTC) :::::Agreed. And we probably want them converted to HTML too, with separate language spans for text in different languages. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:35, 11 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]: This sounds like a reasonable change to make. Note that (given these Functions are primarily for use on Abstract Wikipedia), altering/replacing them to return Z89/HTML fragments is already a desired but breaking change, so making a second breaking change at the same time is probably easiest for fixing things swiftly. That said, that's of course a decision for the Abstract Wikipedia and Wikifunctions communities, not me! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:43, 12 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]@[[User:Sun8908|Sun8908]] to make it a non-breaking change, I've created {{Z|Z34039}} which allows a composition {{Z|Z34043}}. This way you can make functions which either need the specified variant or don't! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:52, 24 April 2026 (UTC) :I have now created {{Z|Z33465}}, which is an implementation of [[Z26570]]. Maybe we can migrate to use that function when more (language-specific) functions for it are ready? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:19, 14 April 2026 (UTC) == No place to ask to activate a function? == I just discovered the {{Z|Z11390}} function and decided to make an overarching language-selecting function for it. After some fiddling around and studying how {{Z|Z32321}} and its set works, I now have {{Z|Z33439}} which has a config object ({{Z|Z33441}}) that selects between the two preexisting language-specific versions I found (English and Malayalam) and the new one I created for my other native language, {{Z|Z33440}}. Except I can't get these to work, because, from what I understand, only [[Wikifunctions:Functioneers|functioneers]] can activate newly created functions and implementations? So where do I apply for the {{Z|Z33439}} and {{Z|Z33440}} functions to be activated? Perhaps we should have a place to ask for it, a la [[w:WP:NPP]] — call it [[Project:New Functions Patrol|New Functions Patrol]] if you will. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] ([[User talk:UndueMarmot|talk]]) 08:58, 14 April 2026 (UTC) :There's [[Wikifunctions:Community portal]] for this. By the way, {{Z|Z33445}} doesn't work because all the code must be inside the main function in Python code. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 09:19, 14 April 2026 (UTC) ::Huh. How could I have missed that? ::But anyway, I've moved the code in {{Z|Z33445}} into inside the main function block. ::Is there any reason why WF decided not to simply allow anyone to write functions? After all, that's how it works with wikitext templates, and these functions are fundamentally serving the same purposes as templates, just written in a different way. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 11:25, 14 April 2026 (UTC) :::I've fixed a couple of technical issues, but tests still fail. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:28, 14 April 2026 (UTC) ::::The tests pass now after some more changes to the code: [[Special:Diff/265232/cur]]. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 12:01, 14 April 2026 (UTC) :::::{{D|Connected}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:02, 14 April 2026 (UTC) :::I think it's a security issue, since Wikifunctions implementations could teoretically be malicious. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:29, 14 April 2026 (UTC) ::::This ^^^. We're very lenient, though, once you've created a few working functions you can apply for the right, per [[WF:Functioneer]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:26, 14 April 2026 (UTC) ::::That explanation [[phab:T343559#11421293|doesn't add up]]. A reason to limit ''connection powers'' to Functioneers might be to prevent vandalism, considering Functions can be used across wikis. But user-provided code is already being executed even without a Functioneer connecting it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 April 2026 (UTC) == Actual difference between {{Z|Z26039}} and {{Z|Z26095}} == What is the actual difference between these two functions? I ask, since it seems to me that the current distinction is more or less that the first one doesn't use an indefinite article in English, while the second does. Which is not a good distinction in a project that should be language neutral. This doubt emerged from my use of the first one in [[abstract:Q124441]], which @[[User:Hogü-456|Hogü-456]] made me notice that is probably wrong. My question is: why is it wrong? How could we clarify the difference? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:46, 19 April 2026 (UTC) :I think the difference is if there is an indefinite article like a or an before the subject or not. In German there can be cases where a definite article is necessary before the subject. I looked at the functions and before the object both times an article is mentioned. As it depends on the language and the word what is the correct function to use I hope it will be clarified and it is an example of the necessity to have a human with understanding in a specific language check it. I hope there will be longer functions what generate more content about a specific kind of item. Then it is necessary to write one such function per language and it can be then applied to several items. It still requires checks and so maybe it is better to write down what item category needs what kind of introduction sentence function for what language. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:05, 19 April 2026 (UTC) ::The point of these two functions (and of the entire Abstract Wikipedia project) is that they should be defined in a purely language-independent way, so that the translation to actual language can be done automatically. This is the reason why these functions have been renamed; I think that this attempt was not succesful, since meaning is still unclear. My proposal to clarify them would be to invoke the concept of [[w:specificity (linguistics)|specificity]]: {{Z|Z26039}} should be named "specific subject is instance of (string)", and should be used only when the QID of the subject uniquely identifies a single thing; {{Z|Z26095}} should instead be renamed in "non-specific subject is kind of (Monolingual text)", and should be used when the QID refers to a multitude of real life items, and we are specifying the class that all these item belong to. This clarification would not still be enough, since it doesn't explain how mass nouns are handled (is water a unique thing? Does {{Q|Q7802}} refer to a single piece of bread or to the entirety of bread, like water?). This problem is very tricky, since mass noun are language-specific and blurry the line between these two functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 20:58, 19 April 2026 (UTC) :Simply put, one corresponds to P31 and the other to P279. Paris is an {{Q|P31}} a {{Q|Q1549591}} :whereas a {{Q|Q1549591}} is a {{Q|P279}} (alias “kind of”) {{Q|Q515}}. Whether the Wikidata knowledge representation will be sufficient to resolve into fluent natural language representations in all languages is, of course, a crucial question. Where it is not, the Abstract Wikipedia knowledge representation will need to supplement the Wikidata content with additional details about the relation between the participants or the participants themselves, and these details should be language-neutral, to the extent that this is practicable. The item {{Q|Q124441}} has no [[:d:Q124441#P31|P31]] statements; it has only [[:d:Q124441#P279|P279]]s, including one relating it to {{Q|Q212920}}, which suggests {{Z|Z26095}} is the appropriate choice here even if the rendering in some languages is the same. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:52, 19 April 2026 (UTC) ::Thanks for explaining it. I think that I'll change the implementation of {{Z|Z26095}}, so that in Italian it produces more or less the same output of {{Z|Z26039}} (both with the definite article). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:24, 20 April 2026 (UTC) == Equivalent of Z6830 for lexemes == Is there an equivalent of {{Z|Z6830}} that enables retrieving all lexemes pointing to a particular lexeme using a specific property? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 21:06, 20 April 2026 (UTC) :There's {{Z|6831}} but I think that's slightly different again to what you're after. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 12:31, 21 April 2026 (UTC) ::Thanks for sharing that one, I did not know it existed. But you are right, it’s not quite what I am looking for. I want a function that would take a Wikidata property reference (like P5191, which is ‘derived from lexeme’) and a Wikidata lexeme reference, and return a list of lexemes that reference that lexeme using that property. [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 13:23, 21 April 2026 (UTC) == Storing huge datasets == It is not a necessity I suppose, but an idea came to me earlier to write a function that would give the corresponding [[en:Shavian alphabet|Shavian alphabet representation]] of an English word written with the Latin alphabet, or perhaps apply that operation to an entire sentence. However, just trying to guess as to what the IPA pronunciation of each word passed into it could be is is both not ideal (pronunciations obviously can and will vary widely between accents) and infeasible <s>(Wikidata lexemes don't really seem to account for pronunciation)</s>. It happens, though, that a comprehensive Shavian dictionary exists named the [https://readlex.pythonanywhere.com/ ''Read Lexicon''], which uses pronunciation and spelling similar to that used by the creator of the alphabet himself. This would be a good dataset to use in performing this translation in the function, but it appears that, all in all, the total size of the dictionary is [https://github.com/Shavian-info/readlex/blob/main/readlex.json ''nearly 26MB''] when formatted as JSON, which would certainly be larger when converted into a typed list. I am wondering if this will ever be feasible or admissible, or if there is really a way around this if importing such a large set of data is deemed impractical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 22:30, 20 April 2026 (UTC) :{{re|Theki}} "Wikidata lexemes don't really seem to account for pronunciation"" is patently untrue; not only does every Bokmål lexeme form have IPA attached to it (thanks to Jon Harald Søby), but there are lots of languages--including English--that have pronunciation information, whether through IPA or otherwise, indicated on their forms. The big issue of course is that adding this data is not always possible to perform efficiently--for instance, I'd love to have Yiddish pronunciation respellings from Paul Abelson's dictionary on as many English forms as possible, but this dictionary not being previously processed makes this difficult. The data set you have brought up, if a suitable reading of [[:m:Wikilegal/Lexicographical_Data]] allows it, could be added as {{P|7243}} statements on various English forms. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 23:20, 20 April 2026 (UTC) ::Well, sorry... I haven't witnessed these pronunciation statements before, I wasn't aware of their existence until you pointed it out. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 21 April 2026 (UTC) :I got 1,900,000 characters into [[Z33875]] before the UI gave up on me. I'm not sure what the limit is. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:21, 21 April 2026 (UTC) == Could not serialize input JS object: Number <small><small>[insert tested number here]</small></small> == I'm not one to throw my problems at others, but I have no idea how to fix this. Am implementing {{Z|Z24602}} in JavaScript, which requires returning a typed map. It now works for every type of value except numbers. Tried explicitly converting the numbers to float64, but either way it throws the error above. Would appreciate it if anyone could diagnose or fix the problem, as my knowledge of Wikifunctions is amateur at best. Thank you. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:32, 23 April 2026 (UTC) :The quick answer is that like some list-related functions, code implementations returning typed maps are not possible unless the type of the objects in the map is specified in the function signature (e.g. if it was a map from Strings to Natural numbers only). So unfortunately, I think you've chosen a function that is not really possible at the moment. There are a few ideas of how we might address this, but for the moment, work on something else. Sorry! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:21, 23 April 2026 (UTC) :Maybe explicitly using [[Z13518|natural numbers]] would work? I would try using <code>{ "Z1K1": "Z13518", "Z13518K1": "[number]" }</code> to represent numbers, perhaps, and seeing if that works. Of course, you would also probably have to adapt this for other types that cannot be serialized, and I'm not sure how easy that would be to generalize (assuming [[w:Don't repeat yourself|DRYness]] is desired). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:39, 23 April 2026 (UTC) == Help with creating a function for Abstract Wikipedia == Hello! I was inspired by {{Z|Z26570}} to create {{Z|Z33975}}, however I'm not sure how I add specific language implementations here. Can anybody help me? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 10:41, 23 April 2026 (UTC) : I think I figured it out, I created a new object with the language config type, added {{Z|Z14310}} to my implementation, and added a new function for English... At least I think that's how it works... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 13:16, 23 April 2026 (UTC) ::You have the right idea, as far as I know. I went ahead and connected the implementations you created as they appear to work fine for English, and added a test for {{Z|Z33975}} (which passes [[File:Twemoji 1f601.svg|24px]]). I also corrected an error you made on the config object where you appear to have accidentally connected English to {{Z|Z33975}} instead of {{Z|Z33977}}. Thank you for contributing! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 23 April 2026 (UTC) ::: {{re|Theki}} Thank you so much for you help! Could you please kindly also connect the implementations for {{Z|Z33986}} which I just made, which is going to be used for the Hebrew implementation of {{Z|Z33975}}. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:11, 23 April 2026 (UTC) ::::You seem to be returning the wrong type in both implementations. Functioneers should not connect implementations that don't work for non-functioneers. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:13, 23 April 2026 (UTC) ::::: {{re|Feeglgeef}} Oh thank you for pointing that out! I am still a bit new to this project and confused, so I need to read up some more about this. How do I return a monolingual text object? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:17, 23 April 2026 (UTC) ::::::I'm trying to fix it for you, the construction of ZObjects in code implementations is a bit difficult right now. Since the State origin using entity and class function will (presumably) be composition, perhaps {{Z|33975}} can be adjusted to return a string, using {{Z|26107}} and {{Z|26107}}? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:21, 23 April 2026 (UTC) :::::I did not notice any discrepancies from looking at the functions by themselves, and it seemed to work fine on my end. Is it bad practice for NLG functions to return the monolingual text type? I had assumed it was logical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:24, 23 April 2026 (UTC) ::::::Both implementations are failing all three tests on my end. No consensus has been established as to whether monolingual texts or strings should be used, so it's like the [[w:War of the currents|war of the currents]] but for Wikifunctions. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:27, 23 April 2026 (UTC) :::::::Oh, you were referring to {{Z|Z33986}}. I assumed you were stating that something was wrong in the earlier English functions that I missed; I apologize for the misunderstanding. Has there been any centralized discussion on this string vs. monolingual text issue? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:31, 23 April 2026 (UTC) ::::::::Not that I'm aware of, I've brought it up on the telegram twice before, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:49, 23 April 2026 (UTC) ::::::::The centralised discussion is at [[WT:Abstract Wikipedia/2025 fragment experiments#Proposed recommendation: Fragments should return Z11/monolingual strings]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:19, 24 April 2026 (UTC) ::::::: {{re|Theki|Feeglgeef}} Can only functioneers test implementations? For me I can't test it at all... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:32, 23 April 2026 (UTC) ::::::::AFAIK, test cases are only immediately testable during editing of a function if they are connected. This is one of my personal pain points with Wikifunctions, iterating on functions without exhaustive connected test cases makes debugging practically impossible for non-functioneers working on newly-created functions... I (or Feeglgeef) can quickly connect the tests you need for you if you want, although if they are not well-formed they may need to be disconnected again afterwards. Additionally, I could temporarily connect the implementation you are writing so that you can test it on the sidebar as you work, but I'm not sure if this is advisable. That functionality is also something that unfortunately only works when not disconnected. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:43, 23 April 2026 (UTC) :::::::::Yup, agree with you on all points, thanks. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:48, 23 April 2026 (UTC) == Please disconnect implementation == I think I've fixed my issue with {{Z|Z33986}}, but I can't edit an actively connected implementations with my rights. I must admit it is an AI-aided fix, I feel very strongly about disclosing that. Courtesy pinging [[User:Theki]] and [[User:Feeglgeef]]. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:51, 23 April 2026 (UTC) : Additionally, I think the JS might be working. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:52, 23 April 2026 (UTC) : Just to clarify, I mean disconnect the Python implementation please. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:53, 23 April 2026 (UTC) :{{Done}} I've disconnected the Python implementation. :I've also added a couple of tests. The rule is a bit more complicated than adding a maqaf before every character that is not a Hebrew letter. Unfortunately, I don't think I'll have time to fix the implementations any time soon. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:03, 23 April 2026 (UTC) :: Thank you! :: Also, for some reason I thought you put a maqaf before all gershayim, so thanks for correcting me. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:09, 23 April 2026 (UTC) :::No, that's not the rule. :::The rest of this reply is an [[:wikt:info-dump|infodump]], feel free to ignore it :) :::In [https://hebrew-academy.org.il/topic/hahlatot/punctuation/ the Academy's punctuation rules], the rule for adding a maqaf is written kind of badly: שמים מקף ברצף שיש בו שני סוגי גופנים, כגון אותיות ומספרים ("maqaf is added in a sequence in which there are two types of fonts, such as letters and numerals"). These are not different types of "fonts", but different types of characters, and I should email them about it. It gives the examples <span lang="he" dir="rtl">ה־12</span> and <span lang="he" dir="rtl">ב־DNA</span>. It doesn't say anything explicitly about quotation marks, but in other places on the same page, you have stuff like <span lang="he" dir="rtl">ב"הארץ"</span>, and from that I deduce that a maqaf is not needed before double quotes if there are Hebrew letters inside the double quotes. :::That said, a few people do think that there must be a maqaf before double quotes. I have a somewhat surprising example of somebody who always does it: translators of Scientology materials into Hebrew. At least that's what they did last time I looked at them, about ten years ago. Those people are certainly prolific, and they get points from me for consistency, but this not the prevalent standard. (And if I recall correctly, they use the minus and not the proper Hebrew maqaf, and they don't get any points from me for that!) :::Also, the name of the character is just "double quotes" and not "gershayim". Gershayim are mostly for abbreviations, although most people use the same character for them. I use ״ for gershayim, as do a few other nerds, but we're the minority. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:35, 23 April 2026 (UTC) :::: {{re|Amire80}} Yeah, "font" is a weird choice of wording here by the Academy...<br> I think I'll follow your guidance and not use a maqaf for quotes beginning with Hebrew letters. <br> I should also add more tests for different types of quotes, like straight (", '), curly (“, ”, ‘, ’), gershayim (״, ׳), including single quotes.<br> P.S. gotta deduct points from Scientology for being a cult but that's neither here nor there [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:49, 23 April 2026 (UTC) :::: {{re|Amire80}} Courtesy ping because I mistyped your username on the last message. Anyways I'm also gonna do that tomorrow because I'm tired now... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:50, 23 April 2026 (UTC) == Connect implementations == Hello! I'm done with the implementations of {{Z|Z33986}} both in JS and Python, and all tests pass. Pinging @[[User:Amire80|Amire80]] to check if all the tests I've added are alright. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 15:24, 24 April 2026 (UTC) :Connected. It's possible that some more changes will be needed, but it looks OK now. :Another little comment: It should be called "clitic" and not "prefix". [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:56, 24 April 2026 (UTC) : {{re|Amire80}} Thanks for your comment! Luckily labels are easy to edit, so I'll get to it. : Currently I'm working on Bulgarian {{z|Z34072}} and {{z|Z34084}}, along with other Bulgarian functions. After I'm finished with those I'll take your advice. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 16:01, 24 April 2026 (UTC) == Please connect my Bulgarian implementations == I recently created the following Bulgarian functions: * {{Z|Z34070}} (currently broken, I think because another function I built it upon is unimplemented) * {{Z|Z34088}} * {{Z|Z34105}} * {{Z|Z34072}} * {{Z|Z34084}} Can somebody please connect these functions, and perhaps suggest other functions I could localize? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:03, 24 April 2026 (UTC) : Specifically, [[Z34070]] is based on [[Z34072]] [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:05, 24 April 2026 (UTC) :{{done}} for everything that passes, [[Z34070]] still does not work after purging WF's cache, though. For future reference, please request on the [[WF:Community portal|community portal]] instead of the project chat. Thank you for your work! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:03, 24 April 2026 (UTC) :: {{re|Feeglgeef}} Thank you for your help! I will keep in mind to go to the [[project: community portal| community portal]] in future instead for this. :: I still don't understand why {{Z|Z34070}} fails... It's implementation is almost completely identical to [[Z30399]] from {{Z|Z30397}}, unless I messed something up... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:11, 24 April 2026 (UTC) :::{{done}} No, it was mostly just timing out. It is better to use selective fetches where possible. One case is failing to match the expected results, but at least it is returning something. For all I know, it might even be acceptable! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 20:35, 24 April 2026 (UTC) :::: {{re|GrounderUK}} Thank you so much for your help! The one failed case is with a definite article, so I feel like that might be fixed in the future... <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:43, 24 April 2026 (UTC) == Editor experience suggestions == I'm a bit frustrated with the editing experience on Wikifunctions, and I have suggestions based on pain points I've had contributing to this project: * Adding a wizard to create functions, implementations, and tests in one flow, somewhat like Wikimedia Commons' upload wizard * A sandbox for experimenting without changing mainspace functions, and maybe letting non-functioneers connect implementations ([[Project: Sandbox]] doesn't seem to fit this) * We could have functions for creation based on the sandbox, like how Wikipedia has articles for creation and edit requests, * Maybe even another test instance of Wikifunctions, like how Wikidata has [[testwikidata:|Test Wikidata]] I really like this project and I don't mean to whine, but it certainly has a lot of pain points both for technical and non-technical people. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:41, 24 April 2026 (UTC) : It's also really complicated to localize functions, so maybe we should add another wizard for that, where you can choose a language, and then create the new function with the aforementioned function wizard, and it just automatically adds it to the related language configuration object of the related function. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:48, 24 April 2026 (UTC) :# Sounds good to me. :# A sandbox available is [[Z10119]], though an extension-provided sandbox that allows you to manipulate the types, code, and tests easily without interfering with the mainspace would be nice. :# [[WF:Suggest a function|This page]] works to some extent, though it's too messy in my opinion. :# We used to have a "beta cluster" but it [[phab:rOMWC5f625c5846b5f779473fa32c9a02d87e59215dfa|got shut down]] just over a year ago because it was broken. :[[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:07, 24 April 2026 (UTC) == Language parameters in language-specific functions == I think that an effort should be made to give the different natural language options corresponding to different English dialects, Chinese scripts, etc. more of a use (I added the test {{Z|Z34119}} to {{Z|Z26095}} and unsurprisingly it fails). There are two main problems with this approach that I can identify: * If you ask the majority of these functions to make a sentence in British English, much of the time it will give you an output with missing words, because it does not fallback to English labels in the case of a British English label for that item missing. The same applies for every other English dialect, British English is just an example here. * Uninformed editors will probably see the presence of a language parameter on these functions, consider it redundant, and remove it. [[Special:Diff/268074|I have made this mistake before]]. In my opinion, in a perfect world, all of these language generation functions would output monolingual text, and if the user asks for American English text, then American English text is what they'll get. If the user asks for Japanese text in hiragana specifically, then that's what they'll get in return. This is not as high-priority as just rendering text in the language plainly in the first place, but it's something that I feel is still worth devoting some effort to. Right now switching functions to use this paradigm is difficult because, on the one hand, I don't know if consensus tends towards this direction being ideal or advisable, and I don't want to make changes like this without at least notifying the wider community. In addition, all tests break once a parameter is added or removed, and the function editor does not recognize the change in number of parameters and therefore you have to remove the function call, re-add it along with all of its parameters it had previously (which is a tedious cut-and-paste job), and then it will work again. This is something that you can do in five seconds by just adding a few lines of JSON to the test source, but this is not directly editable from the Web browser. This tedium is largely what's preventing me from doing this on a larger scale, besides asking for comments first. If anyone has any insights or comments on this, then that would be appreciated. If a reference of functions with and without the support for language variants is needed, of course [[WF:NLG]] can be perused, but I've also my own list cataloged at [[User:Theki/functions#language]]... Of course, this thread has many similarities to [[#"language" argument for certain functions|the one above]], but this concerns me going out and making this consistent across these NLG functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:09, 24 April 2026 (UTC) :I've created {{Z|Z34122}} as an extension to {{Z|Z34039}} for larger functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:34, 24 April 2026 (UTC) :Just to confirm that I, for one, support a Natural language parameter for all natural-language functions. The concern about getting them all aligned is just that we haven’t finally settled on {{Z|Z11}} being preferred to {{Z|Z89}} or some other type that conserves the text’s provenance, so we risk having to change them all again. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:07, 25 April 2026 (UTC) == “Key not found ()”? == What am I doing wrong in {{Z|Z34137}}? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 00:39, 25 April 2026 (UTC) :You were passing a [[Z6091]] to {{Z|32290}}, but it takes a [[Z6001]]. Fixed. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:10, 26 April 2026 (UTC) ::{{done|Thank you}}! [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 14:13, 26 April 2026 (UTC) == Why is my test failing? == Hello! I recently made {{Z|Z34139}} based on [[wikt:Module:bg-translit]], and the test case {{Z|Z34141}} is failing on both implementations, despite the expected output and actual output being the same as far as I can tell. I tried looking at the Unicode codepoints of the output, but those are also identical. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 06:21, 25 April 2026 (UTC) :Yes, it’s a tricky one. I’ve added a normalize step to the result validation in {{Z|Z34141}}, which confirms it is a normalization issue. It looks like it is in the code but I don’t know whether simply normalizing the result is the way to go. Logically, you would normalize both the input and the result. The implementations of {{Z|Z10384}} show you how to do this. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:41, 25 April 2026 (UTC) == Edit request == Hello! I have an edit request for {{Z|Z23752}} and {{Z|Z23414}}. Please replace all the "an/a" logic with <code>Z21739(Argument reference)</code>, both for readability and for more accuracy ("a university is an institution") <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:50, 25 April 2026 (UTC) :{{D}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:24, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #245 is out: The Foundation's search for the perfect language == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-25|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present an academic paper about Abstract Wikipedia, we discuss our latest Type created, and we take a look at the newest created functions. 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:54, 25 April 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=30325620 --> :@[[User:Sannita (WMF)|Sannita (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], technical meta-question: the newsletter quotes the article: ::the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016) :This quotation sounds sensible, but the article's [https://link.springer.com/article/10.1007/s00146-026-02899-w web version], and the PDF that is downloadable from the same page doesn't actually show the emojis. It rather shows text that looks lacking: ::the only way to contest its algorithm is to click or (Crawford and Gillespie [https://link.springer.com/article/10.1007/s00146-026-02899-w#ref-CR14 2016]) :Where did you get the emojis? Is it your (probably correct) guess or is there a version somewhere that actually shows the emojis? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:16, 25 April 2026 (UTC) ::Scratch that. I've found a version with correct emojis: https://wikihistories.github.io/wikilambda-the-ultimate/ [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:37, 25 April 2026 (UTC) == Requested deletion of test == Please delete {{Z|Z34143}}. this was never valid Bulgarian, I messed up. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:19, 25 April 2026 (UTC) :[[WF:RFD]] please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:40, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|talk]]) 00:57, 26 April 2026 (UTC) </bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == Is it OK to connect the implementation? == Hello! I recently applied for functioneer on [[WF:RFG]], and I was wondering whether I could connect the implementation for {{Z|Z34165}} despite its dependency {{Z|Z34149}} being currently unimplemented. That is <em>if</em> I get accepted. I am planning on implementing it based on [[wikt:module:bg-nominal]], but am still having trouble figuring it out for now. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:04, 26 April 2026 (UTC) == Past tense function == Is there a function like {{Z|Z26039}}, but for the past tense (e.g. "Leo Tolstoy <em>was</em> a writer.")? If not, I will create it myself, I just want to make sure there's not a duplicate. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:10, 26 April 2026 (UTC) : {{Done}} with {{Z|Z34224}}, but I have a few kinks to work out with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:35, 26 April 2026 (UTC) :: I need to create some other similar functions for the past tense, I have some ideas: ::* {{Z|Z26095}} ::* {{Z|Z32643}} ::* {{Z|Z28016}} ::* {{Z|Z26570}} ::* {{Z|Z33975}} ::* {{Z|Z27243}} ::* <ins>{{Z|Z26627}}</ins> ::* <ins>{{Z|Z27627}}</ins> ::* <ins>{{Z|Z27173}}</ins> ::* <ins>{{Z|Z29591}}</ins> :: :: Are there any I have missed? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:57, 26 April 2026 (UTC) :I think that here we are starting to walk on dangerous waters: what does past mean? Is it a recent o a far past? Does it have ripercussions on the present or not? Is it just a thing that happened once, many times or for a continuative period of time? :Consider that various languages distinguish between many different types of past. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:38, 26 April 2026 (UTC) :: {{re|Dv103}} That is a fair point... :: How do we go about solving this problem though? I don't think having every sentence on Abstract Wikipedia be "X is a Y" is a very good idea. :: Maybe we have different functions for all these variations of past you mentioned that just map into "X was a Y." in English? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 13:31, 26 April 2026 (UTC) :::To properly solve this problem, we should use a more complete abstract content representation model, like for example the proposal of [[Wikifunctions:Type proposals/Semantic unit|Semantic units]] (look at [[Wikifunctions:Type proposals/Semantic unit/Douglas Adams|the example]] to see how times could be handled). For now, since we're still stuck with single fragment generation functions (that I hope will be slowly replaced with the complete represenation model, when available), we could just restrict your function to a very specific meaning, like "subject was an instance of, for most of its existence" (which means for example that it could be used to say "Douglas Adams was a writer", but not "Abraham Lincoln was a president", since he only was a president for 4 years). Probably my definition is still too vague, and this is why we need to go beyond these fragment generating functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:47, 26 April 2026 (UTC) ::Nitpick... I don't like that it outputs a string instead of monolingual text. With {{Z|Z26039}} it's used so much that I think it's unfixable in that case beyond deprecating it if people care that much, but {{Z|Z34224}} doesn't even have any connected implementations yet. Consider it, maybe? ::Nitpick 2... {{Z|Z34227}} is missing a language parameter. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:08, 26 April 2026 (UTC) ::: I will consider that! ::: I just did that because that's what {{Z|Z26039}} does, so I assumed I should follow suit with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 26 April 2026 (UTC) == Legacy functions == If and when more robust methods of abstractly representing and generating linguistic content come around, and more efficient ways of creating abstract content are devised and implemented, I suspect that our current methods will require some form of deprecation. This is a significant source of concern for me in relation to WF and AW, questioning how prone our current methods of doing things are and eventually will be prone to obsolescence, and how it will be worked around when it comes. We have over 1 250 articles on AW presently, and these are rather all over the place. I suspect the maintenance burden from keeping these articles up to code will eventually, err, creep up on us, I suppose, and some kind of major refactoring will be necessary. We are definitely in a period of experimentation and whatnot right now but eventually, like with enwiki, some sort of structure and rigor will form and I suspect it will start to become rather boring for me... I, for one, very much enjoy experimenting with new and better ways to do things here. I don't personally mind changing things to use a new and better paradigm if need be, that sort of thing highly excites me, but of course there will be things that are left behind, and I suspect maybe bots will be employed to deal with this? A lot of Wikipedia sister sites seem to do that, e.g. going and fixing up use of deprecated templates. Considering the nature of Wikifunctions and Abstract Wikipedia I suspect certain maintenance tasks will be made simpler or even trivial by the typical uniformity of our implementations. I guess I am just concerned if Wikifunctions or Abstract Wikipedia will ever accrue its own kind of "technical debt" with how we are plowing through things presently, and if there is a plan for how we will eventually seek to mitigate that. Maybe too early to ask this question, but I am a notoriously anxious person, so I thought it wouldn't hurt to raise the question regardless... &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:30, 26 April 2026 (UTC) :I very much agree, thank you for expressing my position so well. {{ping|Immanuelle}} has been using an AI-generated tool (well, they haven't edited in a week, perhaps it's a break or perhaps they don't wish to contribute to the project any more) to create a bunch of articles en masse, which I have warned them multiple times is a bad idea (on top of evolving functions, all of the articles are one-sentence-per-paragraph, [[abstract:Q12184|like so]]). That's why I've been avoiding creating articles recently, I'd say I have a good fourth (no data to support, rough guess) of the comments on the wiki, yet less than a percentage of the article count (only three, including the [[abstract:Q319|first article]], though, so perhaps I'm the next [[w:Special:Permalink/908493298|office.bomis.com]]). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:41, 27 April 2026 (UTC) :: I feel that the overwhelming presence of these low-quality articles (which I admit I myself am [[abstract:Q1710970|guilty]]/[[abstract:Q7601858|of]]/[[abstract:Q39338|creating]], usually as testbeds) may incur a large maintenance burden. I do expect them to be easy to detect, however, as searching for the presence of "deprecated" NLG functions is trivial, and it is possible that replacing them with their future ''even abstracter&trade;'' counterparts could be done automatically since they all have the same signatures and can be expected to create the same form of sentence. If it needs to be done manually for a while or for certain delinquent instances, my hope is that it will be fun, at least for a while. :: I just hope that these hypothetical future waves of "this new and versatile way of abstractly representing linguistic content" obsoleting previous methods and requiring refactoring across all articles is only a one-time thing. We should strive to be as robust and flexible as possible from the outset as each brand new paradigm of abstraction is also a brand new maintenance burden for updating old articles. At the end of the day, at least ''some'' of these articles will still render to many different languages even if their methods of creating those sentences of theirs is completely outdated. Ergo, the time it takes for the switchover to be performed across our articles should not be a persistent inconvenience for users (as, of course, they will always still be able to read the content as it was before since these legacy functions aren't being deleted outright), and the increased availability that the new methods will bring about will likely act as motivation for them to join the effort in refactoring (&#x300C;You're telling me that if I rewrite this article in this cool Lisp-looking stuff then I can probably read it in [[abstract:Q9307|Galician]]?? COOL!&#x300D;). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 20:26, 27 April 2026 (UTC) :::Totally agree. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:54, 28 April 2026 (UTC) :::My vague plan is to implement a default function returning an {{Z|Z89}}, for each language-neutral function. A single function would convert any of these to a {{Z|Z11}}, so that a composition of the two can be implemented as the current default until such time as the language-neutral function is ready to return a [[Z89]]. We can already convert a [[Z11]] to a [[Z89]] so, although there is more to be done in this space, existing language-specific functions could be adapted to return a [[Z89]] quite mechanistically. :::Although we certainly could deliver parallel Z89 functions for each existing Z11 function, I don’t think we should assume that particular outcome. Provided the Z89 captures a lang attribute from the Z11’s language tag, the two representations should be largely interchangeable, although I am expecting a Z89 to carry additional attributes at the span level that would be lost on conversion to a Z11 (along with any higher-level tags and attributes). :::When I say there is “more to be done in this space”, I am referring to a new type that would allow HTML fragments to be represented as tractable Wikifunctions objects, but this is currently drafted only in my head! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:21, 29 April 2026 (UTC) == Filtering types of objects == Hello! I have tried to comb through my own edit history several times, but it's really hard to search for specifics because there's no differentiation between different types of objects (functions, implementations, tests, etc.) in the logs as far as I can tell. Am I missing anything? I want it to work sort of like how filtering by namespace works. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 27 April 2026 (UTC) :There is differentiation, it's just rather hard to look through. Since all ZObjects are just JSON data at their core, you can search for instances of <code>{ "Z1K1": "Z[type]"</code>. I haven't tried this so I'm not sure how well it would work and I know MediaWiki search syntax treats quotation marks as a special character, but I have seen Wikifunctions pages link to searches using this before. There is also [[Special:ListObjectsByType]] but it is sitewide rather than specific to your edit history in particular. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:59, 27 April 2026 (UTC) ::''[It doesn’t help directly here, but please see [[WF:Find]] for more details of how this works.]'' [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:24, 29 April 2026 (UTC) :See the feature requests [[phab:T399244]]/[[phab:T373735]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 06:06, 28 April 2026 (UTC) :The lack of filtering edits by namespace is exactly the problem that I was trying to solve with the [[User:Amire80/wikifunctionsanalytics]] tool. :I even kind of succeeded, but it has two major problems: :# It doesn't have any real frontend, so you have to know some SQL to use it (or ask other people who know SQL). :# It doesn't get information from the live site, but from the dump, which appears to be updated once a month. :I've made a [https://quarry.wmcloud.org/query/104794 sample query for you]. Unfortunately, it won't do anything at the moment because of the second problem—your edits started in April 2026, which isn't over yet, so the dump for it hasn't been processed. But I hope that early in May you'll be able to use the same query and see something useful. :(I plan to add support for recent edits, but I haven't done it yet. Now that I more or less figured out how to process Wikifunctions edits, I'm focused on trying to understand Abstract Wikipedia edits. Processing up-to-date edits from both sites will possibly be the next thing I work on, but if you know some Python and want to try doing it yourself, don't wait for me—[https://gitlab.wikimedia.org/toolforge-repos/wikifunctions-analytics Patches welcome].) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:51, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]], I've just updated the data until the end of April. Now the query to which I linked above gives some results. You can also try running other queries if you know SQL. (Or try asking for other queries if you don't.) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:26, 3 May 2026 (UTC) == [[Z34213]] == I'm not quite sure why this implementation is failing. Could someone take a look? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:24, 28 April 2026 (UTC) :I've [https://phabricator.wikimedia.org/T419933#11863997 notified] the team that this is still occurring, the issue was marked as resolved. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:52, 28 April 2026 (UTC) :Some useful tips: :* create more testcases: sometimes it is a random error, so try to see how consistent it is between testcases :* your implementation is very inefficient, since it fetches items and lexemes a lot of times. Ideally, each item and each lexeme should be only fetched once in all the execution tree. :[[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 06:06, 28 April 2026 (UTC) ::Caching (''should?'') means that the lexeme and item data are cached, so the call doesn't actually execute multiple times. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:51, 28 April 2026 (UTC) :::Are lexemes and items actually cached within the same function execution? Even if they are only partially fetched and/or fetched in bulk? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 17:54, 28 April 2026 (UTC) ::::I don't have any evidence to prove that it works but that's definitely A. what's supposed to happen and B. the ideal behavior. This happens because the Z680X functions can be cached just like any other. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 28 April 2026 (UTC) ::::It is unclear. In general, I believe identical branches are resolved only once in orchestration, but there is also independent caching of Wikidata fetches. ::::According to @[[User:DMartin (WMF)|DMartin (WMF)]] ([https://t.me/Wikifunctions/30374 on Telegram]): ::::<blockquote>Well, no. We have caching of Wikidata entities that have been retrieved, but not of the results of nested function calls. There is a proposal for doing this in the context of the V2 composition language, when it's a bit more mature, and it's regarded as a relatively high priority.</blockquote> ::::It’s hard to tell whether fetches in nested calls are, in fact, cached and available for other nested calls in the same call, since it is not generally the actual fetch that consumes the most resources. Rather (I believe), it is construction and transmission of the result object, which is currently repeated afresh in each nested call (unless it is in an identical branch). ::::I hope that’s clear, and I apologise in advance if it happens to be inaccurate! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 29 April 2026 (UTC) :::::Oh, I should clarify.  There is a lot of caching going on, in several different places.  Lexemes and items ''are'' cached by the orchestrator within the same function execution, even if they are only partially fetched and/or fetched in bulk.  When I said that we don't have caching of the results of nested function calls, I meant that's not happening in general, for all nested function calls in compositions.  But fetching of Wikidata entities gets special treatment, so yes, fetched content from Wikidata is cached, regardless if it was fetched by a top-level call or a nested call. :::::It is also true that the construction of a ZObject from the fetched JSON might happen more than once within the same function execution, depending on how a composition has been structured. However, the construction of the ZObject is actually very fast, compared to the elapsed time of getting the JSON from Wikidata. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 18:04, 1 May 2026 (UTC) == Question about cardinal numbers == I was about to edit {{Z|Z16435}} to add my function {{Z|Z34308}}, but I noticed that none of the other functions have a gender parameter. Should I create a new wrapper function "Bulgarian cardinal, neuter", or should I just remove the gender parameter and always return neuter? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:39, 28 April 2026 (UTC) :The “cardinal” functions should return the words used for “counting” numbers in the abstract. :We should consider converting them to return a {{Z|Z11}} rather than a {{Z|Z6}}. It may even be appropriate to return a {{Z|Z12}} to cater for language variants. Either way, I think that would be the approach to adopt for inflected forms, unless reference to specific lexeme-forms is required. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:52, 28 April 2026 (UTC) ::This. If a native of your language were to count up, which form would they be most likely to use? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:29, 28 April 2026 (UTC) ::: {{re|GrounderUK|Feeglgeef}} Thanks for both your input! ::: I relabeled the aforementioned function to {{Z|Z34308}}, and created a new wrapper function {{Z|Z34457}}. ::: Should I specify that my old function is a monolingual text in parentheses? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:26, 28 April 2026 (UTC) ::::You don't have to, unless you think that is something that would require distinction when viewing the function in a list of search results &c. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:36, 28 April 2026 (UTC) == Optional/nullable function parameters == Hello! Recently, I was informed that Wikifunctions has no optional/nullable function parameters as of now. Are there any future plans to support this, and/or workarounds? Maybe create a union type system like "{{Z|6}} or {{Z|23}}". <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 17:53, 28 April 2026 (UTC) :What I do for this is use an "is empty" function corresponding to the type of the parameter in an If statement. If it isn't empty, the function works as intended. Otherwise, it does something else. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:58, 28 April 2026 (UTC) :Unions are not a thing (yet) on Wikifunctions, but you can always define an argument of type {{Z|Z1}}, which means that all types are allowed (I already did this for {{Z|Z26737}}; note that it is still a ugly workaround, don't use it for high level functions). Also, note that usually on Wikifunctions we use {{Z|Z24}} as the null value. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:00, 28 April 2026 (UTC) :: {{re|JJPMaster|Dv103}} Thanks for your help! :: @[[User:Dv103|Dv103]] told me a function call with a missing parameter is treated as an invalid function call, so how does the "is empty" function work with that? :: Also, setting the type to {{Z|1}} seems naive, like setting the type as <code>any</code> in TypeScript... :: Related question: Are there plans to add default values to parameters (outside of "if empty")? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 18:19, 28 April 2026 (UTC) :::Setting the type to {{Z|Z1}} is actually naive, and that's why I advised you to only use it for low-level functions. Currently there is nothing better. Sometimes, type correctness is not actually checked, so it might seem that nullable types are possible. But it is still an hack, and it could broke anytime since it is not intended behavior. :::I don't think that there are current plans to add default values (but correct me if I'm wrong). The closest thing that comes to my mind is that, if you incorporate Wikifunctions into Wikitext, you can leave empty some fields (only of some specific types) and Parsoid will replace them to their default value. This is done only depending on the type, and not on the functions. For example, {{Z|Z6091}} and {{Z|Z6001}} are assigned the QID associated to the page, and {{Z|Z20420}} is assigned the current date. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:56, 28 April 2026 (UTC) :::@[[User:QuickQuokka|QuickQuokka]]: At the very least, [[Z10008]] accepts a null input. Maybe that feature is unique to the String type—I am not sure. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 19:10, 28 April 2026 (UTC) ::::I think it's just not checked, but it shouldn't be intended. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:20, 28 April 2026 (UTC) ::::Strings and typed lists can be “empty” in the sense that their length can be zero. Typed pairs may also be “empty” in a degenerate sense, but such an object will not be returned from a code implementation. A typed map with no entries will also fail to be returned from code, although it is fine in compositions. ::::For a genuinely optional parameter, I prefer a properly typed list, which at least encourages an argument of the correct type. {{Z|Z813}} is also typically faster than {{Z|Z10008}}. Quite a good example of this approach is {{Z|Z23723}}, where it helps to resolve the type union (using [[Z1]]) for both Z6003K1 and Z6003K3. Of course, there’s nothing to prevent more than one element in the list, but additional elements are easily ignored. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:55, 28 April 2026 (UTC) :Pinging {{ping|Jdforrester (WMF)|prefix=|p=}}, I believe there are no current plans. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:02, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]]: I'm afraid there are no current plans to build out optional params, indeed; we would be happy to review this if a compelling case was made, but it'd be a lot of work to re-build the [[Wikifunctions:Function model|function model]] with that support and ensure we don't break (too many) things. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:11, 28 April 2026 (UTC) == Z6830 for Chinese == I was trying to use {{Z|Z6830}} for implementation in the Chinese-language. And turns out most of the Lexeme on Wikidata is using [[d:Q727694]] as the language instead of [[d:Q7850]]. This makes it impossible to use the mentioned function above, since Standard Chinese is not available (or did I miss something?). Is there a way to fetch lexemes with language=[[d:Q727694]] from item? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:20, 30 April 2026 (UTC) :@[[User:Sun8908|Sun8908]] There is [[Z1006]] for Chinese and it has the language code zh. There is an overview of languages in [[Module:Wikifunctions label]] so you can search there for chinese versions and choose the one you need. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 5 May 2026 (UTC) ::I know that. The problem is when using the function [[Z6830]], it cannot retrieve lexeme with language [[d:Q727694]] (but it is the "Chinese language" with the most current Wikidata lexemes, see [https://ordia.toolforge.org/language/ ordia]). I think it should be a Wikidata problem, I might fix it (possibly by creating the same lexemes with language code zh) on Wikidata. Thanks anyway. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 05:39, 6 May 2026 (UTC) :Could you provide an example of a Chinese lexeme that has a linked Wikidata item, or a Z6830 function call that fails to find such a lexeme where one exists? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 07:55, 6 May 2026 (UTC) ::Here: [[d:Lexeme:L846083]]. I think that's a primary reason of me trying to look into this problem, as the label in zh for [[d:Q6256]] (country) is not a single phrase (see its talk page on WD for more information). This makes some Abstract Wikipedia articles very weird in Chinese when {{Z|Z26570}} is used, so lexeme could potentially fix that. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 10:33, 6 May 2026 (UTC) :::Thank you. It looks as though {{Z|Z6830}} [https://www.wikifunctions.org/view/en/Z6830?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z6830%22%2C%22Z6830K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q6256%22%7D%2C%22Z6830K2%22%3A%7B%22Z1K1%22%3A%22Z6092%22%2C%22Z6092K1%22%3A%22P5137%22%7D%2C%22Z6830K3%22%3A%7B%22Z1K1%22%3A%22Z60%22%2C%22Z60K1%22%3A%22cmn%22%2C%22Z60K2%22%3A%5B%22Z6%22%5D%7D%7D returns that lexeme for language tag "cmn"]. Perhaps that tag should be added into the helpers for {{Z|Z24144}}? If it is widely used for lexemes, perhaps it should have its own {{Z|Z60}}? In any event, improvements might be considered under [[:phab:T390563]] (or otherwise), including amending [[Z6830]] to also consider "cmn" (and "zho", "chi"…?) when requests are made for "zh-hans" or "zho-hant" (or others?) @[[User:Winston Sung|Winston Sung]] @[[User:DMartin (WMF)|DMartin (WMF)]] [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:22, 6 May 2026 (UTC) ::::If you go to [[d:Special:NewLexeme]] and put in [[d:Q727694]] as the language, it is going to tell you it has an unrecognized language code. So I believe "cmn" should not be a {{Z|Z60}} by default? I also started [[d:Wikidata:Project_chat#Lexemes_with_language_Standard_Chinese_(Q727694)|a discussion on WD]] regarding this. I guess we can still use it as a fallback language though if possible. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 03:43, 7 May 2026 (UTC) ::::We don't have a separated <code>cmn</code> BCP 47 language subtag in MediaWiki and Wikidata at the moment. <code>zho</code> and <code>chi</code> are ISO 639 language codes but not BCP 47 language subtags. ::::For Modern Standard Mandarin, please use <code>zh-*</code> language tags for now. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 15:26, 8 May 2026 (UTC) == Key not found error == Is there a reason why I am getting key not found error for this [[Z34677|function]] {{Z|Z34677}}? All the underlying functions run and all the test cases work. The debug information does not give more details. Any pointers? Thanks in advance [[User:Jsamwrites|John Samuel]] 19:24, 1 May 2026 (UTC) :It was passing the [[Z6091]] to {{Z|34641}} when that takes a [[Z6001]]. I've fixed that, but there's some other problem with the logic, so I've left it disconnected. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 19:42, 1 May 2026 (UTC) ::@[[User:YoshiRulz|YoshiRulz]] Thanks a lot. [[User:Jsamwrites|John Samuel]] 20:21, 1 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, 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:21, 2 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=30325620 --> == Any formal process for deletion of pages == Does a formal process exist for the deletion of functions, implementations, and tests that includes a notification system for creators, analogous to Wikidata’s process, explaining the rationale behind the deletion (or proposal for deletion)? [[User:Jsamwrites|John Samuel]] 12:36, 3 May 2026 (UTC) :Does [[Wikifunctions:Requests for deletions]] work? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:00, 3 May 2026 (UTC) :Please see the discussion at [[Wikifunctions talk:Requests for deletions#Should we expect Objects' creators to get pinged on deletion proposals?]]. :As I see it, it is the proposer’s responsibility to consult appropriately before making a request and we expect our administrators to act only when satisfied that appropriate consultation has occurred. In many cases, no consultation is required. Administrators may delete their own contributions without making a request, but this is not a practice I would encourage. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:51, 3 May 2026 (UTC) == Implementation of rational number in JS doesn't match in Z19677 (Rational number) and Z28579 (RGBA colour) == In {{Z|19677}} it's <syntaxhighlight lang=js> { "K1": sign * numerator, "K2": denominator } </syntaxhighlight> but in {{Z|28579}} it's <syntaxhighlight lang=js> [ sign * numerator, denominator ] </syntaxhighlight> '''<span style="font-family:Iosevka,monospace">[[User:沈澄心|<span style="color:#9f3526">dring</span>]][[User talk:沈澄心|<span style="color:#534fa3">sim</span>]]</span>''' 05:15, 4 May 2026 (UTC) == Nested functions in compositions == I wish it will be easier to a add another function about a specific existing function in a function implementation based on a composition. When I write long functions in spreadsheets I usually stat with a small part and then I try to go further and after important steps I test if the output is as expected. I created [[Z34826]] to get the German gender specific occupation lexeme for a specific person based on their gender. I wanted to add a function around the existing one and it was not successful. It is not very easy to implement as it requires the possibily to move a part to another section but I think it can be helpful if it will be implemented. So far I spend more time as expected on the function. Describing it with words what the function needs to do is much easier than implementing it here in Wikifunctions. So I think there needs to be improvement to make Wikifunctions more accessible. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:10, 5 May 2026 (UTC) :Have you tried to use the copy-paste functionality? It is very useful to move parts of composition arounn. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 07:12, 6 May 2026 (UTC) :I've also found the composition editor to be wholly unsuitable for any expressions more than a few levels deep. (Even with the <code>localStorage</code> clipboard, because of its overzealous type checks.) Compositions naturally grow out from the "leaves", the immediate operations on the inputs, while the interface really wants you to build from the "root". I mostly use the [https://yoshirulz.gitlab.io/WikiLambdaBlockly drag-and-drop block editor] which I made to smooth over some of the site's problems, so if you want to try that out and give me some feedback I'd appreciate it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 14:36, 6 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the 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 [[: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/1778520600 May 11, 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]]) 11:16, 8 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=30325620 --> == RGBA colour, spelling... == Something that has always irked me a little bit is the spelling of [[Z28579|RGBA colour (Z28579)]]. I guess this is not unsurprising for me considering my use of US English but I think there is more to it than preference and I want to try to argue for it being changed to use American spelling. I know that this probably has a snowball's chance in hell of actually garnering any support, so I won't really be miffed if the spelling remains as it is, but I thought it wouldn't hurt to raise this regardless. The main issue I have with it is the spelling of the original proposal. When infernostars raised the [[Wikifunctions:Type proposals/RGBA color|type proposal]], the spelling was 「RGBA color」. Of the comments that mentioned the word 「colo[u]r」, two used British spelling while six used the American spelling as used in the proposal. The only thing that really pointed to the use of ''colour'' was the fact that the catalog page on color functions used that spelling already. For all intents and purposes, the spelling of the original proposal should have been maintained, but it was not; [[User:DVrandecic (WMF)|DVrandecic]], the eventual creator of the type, used a different spelling. It should be noted that there was really no reason for this to occur and while it is an undoubtedly minor issue I still believe it should be rolled back and the type should use the spelling of the original proposal and majority of editor comments. In [[abstract:Q936|OpenStreetMap]], there have been keyvalue proposals that have had the finalized spelling that gets put to use be in British English despite the original proposal being in American English; this has usually occurred with proposals relating to 「X center/centre」 tags. This makes sense on the surface, because OpenStreetMap is maintained by a UK organization, and still has close ties to Europe. The Wikimedia Foundation, however, is an ''American'' company. This is often brought up as a fallible argument when debating article spelling on the English Wikipedia, and I don't bring it up to support that 「RGBA color」 should be used for that exact reason, but rather to state that OpenStreetMap's general policy on tag names need not apply here. It appears to me that, at least initially, the majority of 「core contributors」 to Wikifunctions used British English; I can name YoshiRulz, 99of9, GrounderUK, and VIGNERON.<ref group="color">I'm avoiding linking to these folks because I don't think pinging them about this discussion is all too necessary unless they themselves want to be involved; I don't want to clutter their inboxes just to briefly mention them. I pinged Denny because, well, I'm asking him a question directly, but everyone else I would prefer to join this discussion by their own accord... not that I wish for this decision to be confused as me going 「these people use British English so they will probably oppose my idea, I won't invite them to the discussion because of that」...no, I promise you that is not the reason.</ref> I see (or saw) these people ''everywhere'', so it makes sense that British English has prevailed in some sorts on this website, but I don't think that indicates that it should be the ''preferred'' spelling across the website, at least not to the point where a proposal should have its name changed to match such a "consensus".<ref group="color">It could be argued that the front-and-center ''Function catalogue'' using 「catalogue」 is actually indicative of such a "consensus", but ''catalogue'' is in a similar position to the word ''grey'' where I live (that is, the US) in that it is used just as often as its American counterpart. Also, consider Wiktionary's ''Beer parlour'' project chat.</ref> The unnecessary modification of the original spelling is my main argument for changing it back... but of course, I must obligatorily state that on English Wikipedia, it is [[w:Color|Color]] and [[w:RGBA color model|RGBA color model]]; on Wikidata, it is [[d:Q1075|color]] and [[d:Q2325624|RGBA color space]]; in CSS (which typically uses hexadecimal triplets to specify RGBA values), the properties are <code>color</code>, <code>background-color</code>, etc.; bit of a weak jab, but on Schema.org it is [https://schema.org/color color], [https://schema.org/colorSwatch colorSwatch]; et cetera. {{Z|Z28580}} uses ''color'', so does {{Z|Z28591}} and its Python counterpart. Mr. Vrandečić, I have to ask, I'm rather confused... you created the color type using British English spelling, but you were also responsible for the creation of the equality function which uses the American English spelling. You also seem to be writing in American English for the status updates, judging by your use of -''ize'' over -''ise'' endings and use of ''program'' over ''programme'' in [[Wikifunctions:Status updates/2026-04-16]]. Is there something I'm missing or have you switched your preferred variant somewhere along the way? Anyways, do consider this if you wish... again, I don't suppose this will garner much support, it is the ''non-issuest'' of ''non-issues'', but it has irked me to the point where I want to ask about it to get some answers, if nothing else. I am not arguing for every other color function to have its name changed, just the type itself. <references group="color"></references> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 8 May 2026 (UTC) :This is a multilingual project; the <code>en</code> label is <code>RGBA colour</code> and the <code>en-us</code> label is <code>RGBA color</code>. Though I'm not able to switch to <code>en-us</code> via the language picker so that would need to be fixed.<!-- --><br>edit after reading your whole comment: The same is true of {{Q|1075}}, there are labels specified for multiple English variants. (In {{Q|2325624}} it's only an alias.) I agree that other websites' choices aren't binding on us, but from that, I conclude that the more widespread British/Commonwealth spellings should be used for the generic <code>en</code>. As for myself, I'm Aussie and I will continue to use the BrE spellings ([[w:en:Oxford_spelling#Language_tag_comparison|+ "routing"]], TIL) if only by muscle memory.<!-- --><br>[[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 17:42, 8 May 2026 (UTC) :: Your lattermost point would normally be fine in a perfect world. Wikipedia's <code>convert</code> function defaults to "international" English, which I don't personally take issue with because it happens that we here in America are actually outliers for saying and spelling things differently... err, or we were for a while at least, nowadays it seems like an even split (plus you have "yield" vs. "give way" which is effectively the logical opposite of US's use of "meter" over "metre"). :: However, this is not a perfect world, and I don't think <code>en</code> should correspond to any particular variant. It is too fragmented across all software at this point to impose such a requirement. The inability to switch to <code>en-us</code> on this website foregoes an easy and simple solution to this problem that makes everyone happy, because the yanks (such as myself) can't be happy because we can't see the labels in American English even if we wanted to, and the other folk can't switch either as far as I'm aware (and the en-CA and en-GB languages in the preferences page seems to be deprecated). My point being, <code>en</code> is abused to mean "en-UK" just as often as it is abused to mean <code>en-US</code>; I think a decision shouldn't be made on such an assumption of one "default". &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:48, 12 May 2026 (UTC) :Hi @[[User:Theki|rae]]! I have no opinion nor preference on this, and given my background, I am just entirely confused about my spelling preferences myself, as you can tell from my inconsistent usage. I learned British English in school and used that for maybe two decades or so, but moved to the US and lived there for more than a decade, enough to be naturalized, but now I am back in Europe and I am technically a professor at King's College London, soooo.... honestly, I do not know. I don't remember having put too much thought into it at the moment I created it. The good thing is that in Wikifunctions, just as in Wikidata, it is easy to change, without messing things up too much (unlike in Wikipedia), so my suggestion is, just make the change, see if anyone complains, and if they do, discuss it more. I don't know if there is a guideline already in Wikifunctions about the variants. I am happy either way, and honestly, I keep forgetting which variant is which most of the time. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 18:16, 10 May 2026 (UTC) :: I can definitely understand this, although I am unfortunately rather passionate about any minutiae involving preferential minor differences in ''anything'', of which AmE vs. BrE chiefly is. So I dedicate a lot of headspace to it. More than I should. Not that I wish to imply that the comment above that I have wrote is of an irrational nature, or done out of spite or pure emotion and subjectivity; I do genuinely believe that ''RGBA color'' is beyond just a personal preference and is just logical. I may boldly go and change it, but for some reason I was expecting that changing the English label of a Type would require elevated permissions, and I also didn't want to do it only to get immediately reverted because it ''did'' strike a chord with someone, when I could instead see how apathetic, supportive, or in opposition interested people are beforehand and ''then'' act accordingly. I was not meaning to antagonize you over your spelling habits, I did actually use British English for a few years starting in 2020 before I went back to American English, so I'd be a hypocrite for me to decry you for not always sticking to some arbitrary standard of spelling words over the other. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:55, 12 May 2026 (UTC) :Although I spell it “colour”, I think it makes more sense to use “color” for the type, since that is almost always the required spelling when the string functions as a keyword. :More generally, though, Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en". This is unusual, in my experience, as "en" is widely misused in place of "en-US", where there are recorded spelling differences. :(I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere. Use of -ize rather than -ise is a matter of personal preference or house style, but regional autocorrect encourages -ise.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:00, 12 May 2026 (UTC) :: ''Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en"'' :: Definitely agreeing with you on the latter being a good choice. However, I suspect the favoring of "colour" over "color" may be because, in terms of language codes, when sorted alphabetically <code>en-us</code> actually comes ''after'' <code>en-gb</code>. Although, the frontend seems to be sorting <code>en-ca</code> after <code>en-gb</code>, so I don't actually know how correct that is. :: ''I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere'' :: The context of the spelling was "''No program for the NLG SIG meeting for next Tuesday has been proposed''". In that usage context, I think it makes sense to assume that ''program'' is not being used to refer to a computer program, but to a ''program of events'' or similar, something that you would spell as a ''programme'' in British English. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 12 May 2026 (UTC) :{{s}} this. I'm obviously biased but I believe American English is preferable generally, American dominance on the internet (our Department of Defen'''s'''e invented it!) and rapidly-increasing consumption of American media by international English speakers means that more people use American English's conventions, this is clear through for example [http://trends.google.com/explore?q=color%2Ccolour&date=all&geo=Worldwide search trends] (though they aren't particularly reliable). Perhaps this is a bit of a supremacist opinion, but we should have internal consistency, and if we must choose, American English should be our first choice (then Indian and then British English) [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:10, 12 May 2026 (UTC) :: This is rather flawed reasoning, though. I think probably any given British or Indian person would not agree on using that as the reasoning for this, not that you are necessarily ''completely wrong'', but if this is not a good enough reason for English Wikipedia's (admittedly extremely flawed) ''ENGVAR'' policy then I don't think it's likely it will pass here either. :: Although of note is that [https://books.google.com/ngrams/graph?content=color%2Ccolour&year_start=1800&year_end=2022&corpus=en&smoothing=3&case_insensitive=true Google ngrams] agree with you, but "color" vs. "colour" is an eternal holy war that will not be won by demonstrating that more books use US spelling over Commonwealth spelling. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:44, 12 May 2026 (UTC) :::You're probably right that it's not very sound. I'm biased in that other varieties of English irk me, and that's probably mutual for people who are used to other varieties of English when they read what I write! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:56, 12 May 2026 (UTC) :I've decided to boldly [[Special:Permalink/274271|make the change]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:02, 12 May 2026 (UTC) :: Thank you. Considering both you and GrounderUK seem to consider it an okay change, I think this will do for now. :: I should note that the matter of whether to move [[Wikifunctions:Catalogue/Colour functions]] in response to this (however this discussion will ultimately turn out) is a whole other can of worms, in my view. I can't say I have an opinion on that at the moment, but I'm putting it out there regardless. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:06, 12 May 2026 (UTC) :::Personally, I'm in favor of moving the page and renaming all of the items on it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:10, 12 May 2026 (UTC) ::I don't like this (exactly because of the American hegemony you cited), but again, it shouldn't matter because the software is meant to be multilingual. Clearly there's a bug preventing you from picking an English variant/dialect as your display language. But the search bar and Function/Type autocompletion do check the English variants for matches. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 15:15, 12 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[abstract:User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:31, 11 May 2026 (UTC) :Thank you for dedicating your time to writing this, it is very informative. I will try to add input once I'm not in over my head with finals. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:27, 12 May 2026 (UTC) == Display function for HTML fragment == Currently, any collapsed Z89 literal appears as<blockquote>&lt;&gt; [[Z89|HTML fragment]]</blockquote>If I were to create a new Function which returned something like<blockquote>&lt;&gt; 123-byte HTML fragment <q><nowiki><td><span lang=</nowiki>&hellip;</q></blockquote>could that be connected to replace the collapsed form, or would it require changes to the Wikilambda software? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 16:14, 11 May 2026 (UTC) :It might work, but I doubt it. Those angled brackets suggest that the collapsed form is not simply defaulting to the type’s label. Looking at [[:phab:T410509]], I’ve concluded that enhancements to the collapsed form were never considered, rather than being actively rejected. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:12, 12 May 2026 (UTC) ::[[:Phab:T391985]] documents the original design. Note the fifth bullet point under “Acceptance criteria”. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:21, 12 May 2026 (UTC) :I'm not sure the byte-size is necessary, but the outer tag (or first outer tag, though generally I'd prefer most fragments use a wrapper tag if it needs multiple like JSX does, but that's a whole different topic) would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:51, 12 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in 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]]) 14:36, 15 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 --> == [[Z34510]] == This function, which determines if a Wikidata item for a {{q|5}} has an undeprecated {{p|21}} statement of {{q|6581097}}, returns false for {{q|173399}}, a transgender man. This is because his item assigns his P21 statement to {{q|2449503}}, not {{q|6581097}}. I'm not sure how to account for this discrepancy. Should {{z|34510}}: # Include {{q|2449503}} as a value that can lead to a true result, # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a man?") could return true for either "male" or "trans man", # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a trans man?") could return true for "trans man", # Not exist at all? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:48, 16 May 2026 (UTC) m79hzmk1flmey6h3dt3rc1bkgyq257a 275549 275535 2026-05-16T19:03:22Z Theki 2389 /* Z34510 */ re 275549 wikitext text/x-wiki {{shortcut|[[WF:CHAT]]|[[WF:PC]]|[[WF:VP]]}} __NEWSECTIONLINK__ [[Category:Help]] <!-- please do not remove this line --> Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc. Other places to find help: * [[Wikifunctions:Administrators' noticeboard]] * [[Wikifunctions:Report a technical problem]] * [[Wikifunctions:FAQ]] {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |timeout=30 }} {{Archives|{{#tag:div|<br />{{Flatlist|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1|hideredirects=1}} |class=mw-collapsible-content|style=font-size:92%;}}|class="mw-collapsible mw-collapsible-toggle mw-collapsed"}} |prefix=WF:Project chat/Archive/ }} == "language" argument for certain functions == Hello. I am relatively new to Wikifunctions. Recently, I tried to create functions for Chinese translation of {{Z|Z26570}} and {{Z|Z26095}} (which became [[Z32788]] and [[Z32900]]). During the creation of these functions, I was trying to take {{Z|Z32212}} as reference. And I realized that the defining role sentence function is taking <code>language</code> as an argument (and the test case of the Chinese-language function already contains two varieties of Chinese). This makes it possible to output monolingual text in <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code>, or any varieties of the language. I think for this reason, it is better to have <code>language</code> as arguments for the implementation of Z26570 and Z26095, and potentially more functions that require {{Z|Z14294}}, since it would output the varieties code instead of just saying <code>zh</code> for <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code> in the output of type {{Z|Z11}}. I am not sure how the fallback mechanism works if one of the language (varieties) do not have a labels/lexemes, but to me, it is reasonable to have a <code>language</code> argument. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 09:38, 31 March 2026 (UTC) :The functions you mention do have a language argument. For Wikifunctions, the {{Z|Z60}} can be at a higher or lower level; whether a {{Z|Z11}} is for a language or a variant is determined by the function that constructs it. Please see {{Z|Z26565}} for an example and feel free to add test cases in Chinese. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:54, 11 April 2026 (UTC) ::Hello @[[User:GrounderUK|GrounderUK]], thanks for the answer. I understand that whether {{Z|Z11}} is for a language or a variant depends on the function. But that is exactly what I am asking for. It is true that [[Z26570]] and [[Z26095]] takes [[Z60]] as argument, but the language-specific functions in {{Z|Z29843}} and {{Z|Z26096}} don't. ::Let me give you an example: INPUT to [[Z26570]]: <code>entity</code>: Tokyo, <code>class</code>: city, <code>location</code>: Japan, <code>language</code>: zh-cn, the config would select [[Z33030]] (created after my previous comment by elseone) as the implementation, and it would RETURN 东京是日本的一个城市。(zh-hans), which is not zh-cn as requested in the INPUT. It would also be using the term not for the variant (when it is different) because it is hardcoded to use the term in zh-hans. However, if we have the implementation like [[Z32790]] (which was created by me but a natural language argument was added by elseone) or [[Z32213]] (that works in the defining role sentence function because of the extra argument), it could cater for different variant. ::If we don't have the language argument in the language-specific function, the desire for article creation on Abstract Wikipedia would be to create a function for every variant. Is it then better to create functions for every variant? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:18, 11 April 2026 (UTC) :::I forgot to mention that there are some hardcoding in {{Z|Z32790}} as well, but I cannot fix it because it is a connected function and I am not a functioneer. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:31, 11 April 2026 (UTC) ::::Okay, I think it’s safe to disconnect this one as the function is not yet configured for use on Abstract Wikipedia. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:04, 11 April 2026 (UTC) :::Ah, sorry… I misunderstood you. I agree that the called function should be able to accept the original language argument. That is simpler in theory than in practice, because the configured functions all have to have the same argument types, as I understand it. I’m not sure which the best approach is, really, but we probably want to avoid two levels of configuration. That suggests that all language-specific functions would need to accept the additional argument, which is unrewarding work for someone. @[[User:99of9|99of9]], @[[User:Jdforrester (WMF)|Jdforrester (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]] Any thoughts? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:57, 11 April 2026 (UTC) ::::I mean, we would need to modify all the functions in each language, which could take some time. But we are still in an early stage. If we don't fix it now and we want to fix it later, it would be a disaster. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 19:25, 11 April 2026 (UTC) :::::Agreed. And we probably want them converted to HTML too, with separate language spans for text in different languages. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:35, 11 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]: This sounds like a reasonable change to make. Note that (given these Functions are primarily for use on Abstract Wikipedia), altering/replacing them to return Z89/HTML fragments is already a desired but breaking change, so making a second breaking change at the same time is probably easiest for fixing things swiftly. That said, that's of course a decision for the Abstract Wikipedia and Wikifunctions communities, not me! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:43, 12 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]@[[User:Sun8908|Sun8908]] to make it a non-breaking change, I've created {{Z|Z34039}} which allows a composition {{Z|Z34043}}. This way you can make functions which either need the specified variant or don't! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:52, 24 April 2026 (UTC) :I have now created {{Z|Z33465}}, which is an implementation of [[Z26570]]. Maybe we can migrate to use that function when more (language-specific) functions for it are ready? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:19, 14 April 2026 (UTC) == No place to ask to activate a function? == I just discovered the {{Z|Z11390}} function and decided to make an overarching language-selecting function for it. After some fiddling around and studying how {{Z|Z32321}} and its set works, I now have {{Z|Z33439}} which has a config object ({{Z|Z33441}}) that selects between the two preexisting language-specific versions I found (English and Malayalam) and the new one I created for my other native language, {{Z|Z33440}}. Except I can't get these to work, because, from what I understand, only [[Wikifunctions:Functioneers|functioneers]] can activate newly created functions and implementations? So where do I apply for the {{Z|Z33439}} and {{Z|Z33440}} functions to be activated? Perhaps we should have a place to ask for it, a la [[w:WP:NPP]] — call it [[Project:New Functions Patrol|New Functions Patrol]] if you will. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] ([[User talk:UndueMarmot|talk]]) 08:58, 14 April 2026 (UTC) :There's [[Wikifunctions:Community portal]] for this. By the way, {{Z|Z33445}} doesn't work because all the code must be inside the main function in Python code. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 09:19, 14 April 2026 (UTC) ::Huh. How could I have missed that? ::But anyway, I've moved the code in {{Z|Z33445}} into inside the main function block. ::Is there any reason why WF decided not to simply allow anyone to write functions? After all, that's how it works with wikitext templates, and these functions are fundamentally serving the same purposes as templates, just written in a different way. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 11:25, 14 April 2026 (UTC) :::I've fixed a couple of technical issues, but tests still fail. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:28, 14 April 2026 (UTC) ::::The tests pass now after some more changes to the code: [[Special:Diff/265232/cur]]. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 12:01, 14 April 2026 (UTC) :::::{{D|Connected}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:02, 14 April 2026 (UTC) :::I think it's a security issue, since Wikifunctions implementations could teoretically be malicious. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:29, 14 April 2026 (UTC) ::::This ^^^. We're very lenient, though, once you've created a few working functions you can apply for the right, per [[WF:Functioneer]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:26, 14 April 2026 (UTC) ::::That explanation [[phab:T343559#11421293|doesn't add up]]. A reason to limit ''connection powers'' to Functioneers might be to prevent vandalism, considering Functions can be used across wikis. But user-provided code is already being executed even without a Functioneer connecting it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 April 2026 (UTC) == Actual difference between {{Z|Z26039}} and {{Z|Z26095}} == What is the actual difference between these two functions? I ask, since it seems to me that the current distinction is more or less that the first one doesn't use an indefinite article in English, while the second does. Which is not a good distinction in a project that should be language neutral. This doubt emerged from my use of the first one in [[abstract:Q124441]], which @[[User:Hogü-456|Hogü-456]] made me notice that is probably wrong. My question is: why is it wrong? How could we clarify the difference? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:46, 19 April 2026 (UTC) :I think the difference is if there is an indefinite article like a or an before the subject or not. In German there can be cases where a definite article is necessary before the subject. I looked at the functions and before the object both times an article is mentioned. As it depends on the language and the word what is the correct function to use I hope it will be clarified and it is an example of the necessity to have a human with understanding in a specific language check it. I hope there will be longer functions what generate more content about a specific kind of item. Then it is necessary to write one such function per language and it can be then applied to several items. It still requires checks and so maybe it is better to write down what item category needs what kind of introduction sentence function for what language. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:05, 19 April 2026 (UTC) ::The point of these two functions (and of the entire Abstract Wikipedia project) is that they should be defined in a purely language-independent way, so that the translation to actual language can be done automatically. This is the reason why these functions have been renamed; I think that this attempt was not succesful, since meaning is still unclear. My proposal to clarify them would be to invoke the concept of [[w:specificity (linguistics)|specificity]]: {{Z|Z26039}} should be named "specific subject is instance of (string)", and should be used only when the QID of the subject uniquely identifies a single thing; {{Z|Z26095}} should instead be renamed in "non-specific subject is kind of (Monolingual text)", and should be used when the QID refers to a multitude of real life items, and we are specifying the class that all these item belong to. This clarification would not still be enough, since it doesn't explain how mass nouns are handled (is water a unique thing? Does {{Q|Q7802}} refer to a single piece of bread or to the entirety of bread, like water?). This problem is very tricky, since mass noun are language-specific and blurry the line between these two functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 20:58, 19 April 2026 (UTC) :Simply put, one corresponds to P31 and the other to P279. Paris is an {{Q|P31}} a {{Q|Q1549591}} :whereas a {{Q|Q1549591}} is a {{Q|P279}} (alias “kind of”) {{Q|Q515}}. Whether the Wikidata knowledge representation will be sufficient to resolve into fluent natural language representations in all languages is, of course, a crucial question. Where it is not, the Abstract Wikipedia knowledge representation will need to supplement the Wikidata content with additional details about the relation between the participants or the participants themselves, and these details should be language-neutral, to the extent that this is practicable. The item {{Q|Q124441}} has no [[:d:Q124441#P31|P31]] statements; it has only [[:d:Q124441#P279|P279]]s, including one relating it to {{Q|Q212920}}, which suggests {{Z|Z26095}} is the appropriate choice here even if the rendering in some languages is the same. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:52, 19 April 2026 (UTC) ::Thanks for explaining it. I think that I'll change the implementation of {{Z|Z26095}}, so that in Italian it produces more or less the same output of {{Z|Z26039}} (both with the definite article). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:24, 20 April 2026 (UTC) == Equivalent of Z6830 for lexemes == Is there an equivalent of {{Z|Z6830}} that enables retrieving all lexemes pointing to a particular lexeme using a specific property? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 21:06, 20 April 2026 (UTC) :There's {{Z|6831}} but I think that's slightly different again to what you're after. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 12:31, 21 April 2026 (UTC) ::Thanks for sharing that one, I did not know it existed. But you are right, it’s not quite what I am looking for. I want a function that would take a Wikidata property reference (like P5191, which is ‘derived from lexeme’) and a Wikidata lexeme reference, and return a list of lexemes that reference that lexeme using that property. [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 13:23, 21 April 2026 (UTC) == Storing huge datasets == It is not a necessity I suppose, but an idea came to me earlier to write a function that would give the corresponding [[en:Shavian alphabet|Shavian alphabet representation]] of an English word written with the Latin alphabet, or perhaps apply that operation to an entire sentence. However, just trying to guess as to what the IPA pronunciation of each word passed into it could be is is both not ideal (pronunciations obviously can and will vary widely between accents) and infeasible <s>(Wikidata lexemes don't really seem to account for pronunciation)</s>. It happens, though, that a comprehensive Shavian dictionary exists named the [https://readlex.pythonanywhere.com/ ''Read Lexicon''], which uses pronunciation and spelling similar to that used by the creator of the alphabet himself. This would be a good dataset to use in performing this translation in the function, but it appears that, all in all, the total size of the dictionary is [https://github.com/Shavian-info/readlex/blob/main/readlex.json ''nearly 26MB''] when formatted as JSON, which would certainly be larger when converted into a typed list. I am wondering if this will ever be feasible or admissible, or if there is really a way around this if importing such a large set of data is deemed impractical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 22:30, 20 April 2026 (UTC) :{{re|Theki}} "Wikidata lexemes don't really seem to account for pronunciation"" is patently untrue; not only does every Bokmål lexeme form have IPA attached to it (thanks to Jon Harald Søby), but there are lots of languages--including English--that have pronunciation information, whether through IPA or otherwise, indicated on their forms. The big issue of course is that adding this data is not always possible to perform efficiently--for instance, I'd love to have Yiddish pronunciation respellings from Paul Abelson's dictionary on as many English forms as possible, but this dictionary not being previously processed makes this difficult. The data set you have brought up, if a suitable reading of [[:m:Wikilegal/Lexicographical_Data]] allows it, could be added as {{P|7243}} statements on various English forms. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 23:20, 20 April 2026 (UTC) ::Well, sorry... I haven't witnessed these pronunciation statements before, I wasn't aware of their existence until you pointed it out. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 21 April 2026 (UTC) :I got 1,900,000 characters into [[Z33875]] before the UI gave up on me. I'm not sure what the limit is. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:21, 21 April 2026 (UTC) == Could not serialize input JS object: Number <small><small>[insert tested number here]</small></small> == I'm not one to throw my problems at others, but I have no idea how to fix this. Am implementing {{Z|Z24602}} in JavaScript, which requires returning a typed map. It now works for every type of value except numbers. Tried explicitly converting the numbers to float64, but either way it throws the error above. Would appreciate it if anyone could diagnose or fix the problem, as my knowledge of Wikifunctions is amateur at best. Thank you. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:32, 23 April 2026 (UTC) :The quick answer is that like some list-related functions, code implementations returning typed maps are not possible unless the type of the objects in the map is specified in the function signature (e.g. if it was a map from Strings to Natural numbers only). So unfortunately, I think you've chosen a function that is not really possible at the moment. There are a few ideas of how we might address this, but for the moment, work on something else. Sorry! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:21, 23 April 2026 (UTC) :Maybe explicitly using [[Z13518|natural numbers]] would work? I would try using <code>{ "Z1K1": "Z13518", "Z13518K1": "[number]" }</code> to represent numbers, perhaps, and seeing if that works. Of course, you would also probably have to adapt this for other types that cannot be serialized, and I'm not sure how easy that would be to generalize (assuming [[w:Don't repeat yourself|DRYness]] is desired). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:39, 23 April 2026 (UTC) == Help with creating a function for Abstract Wikipedia == Hello! I was inspired by {{Z|Z26570}} to create {{Z|Z33975}}, however I'm not sure how I add specific language implementations here. Can anybody help me? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 10:41, 23 April 2026 (UTC) : I think I figured it out, I created a new object with the language config type, added {{Z|Z14310}} to my implementation, and added a new function for English... At least I think that's how it works... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 13:16, 23 April 2026 (UTC) ::You have the right idea, as far as I know. I went ahead and connected the implementations you created as they appear to work fine for English, and added a test for {{Z|Z33975}} (which passes [[File:Twemoji 1f601.svg|24px]]). I also corrected an error you made on the config object where you appear to have accidentally connected English to {{Z|Z33975}} instead of {{Z|Z33977}}. Thank you for contributing! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 23 April 2026 (UTC) ::: {{re|Theki}} Thank you so much for you help! Could you please kindly also connect the implementations for {{Z|Z33986}} which I just made, which is going to be used for the Hebrew implementation of {{Z|Z33975}}. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:11, 23 April 2026 (UTC) ::::You seem to be returning the wrong type in both implementations. Functioneers should not connect implementations that don't work for non-functioneers. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:13, 23 April 2026 (UTC) ::::: {{re|Feeglgeef}} Oh thank you for pointing that out! I am still a bit new to this project and confused, so I need to read up some more about this. How do I return a monolingual text object? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:17, 23 April 2026 (UTC) ::::::I'm trying to fix it for you, the construction of ZObjects in code implementations is a bit difficult right now. Since the State origin using entity and class function will (presumably) be composition, perhaps {{Z|33975}} can be adjusted to return a string, using {{Z|26107}} and {{Z|26107}}? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:21, 23 April 2026 (UTC) :::::I did not notice any discrepancies from looking at the functions by themselves, and it seemed to work fine on my end. Is it bad practice for NLG functions to return the monolingual text type? I had assumed it was logical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:24, 23 April 2026 (UTC) ::::::Both implementations are failing all three tests on my end. No consensus has been established as to whether monolingual texts or strings should be used, so it's like the [[w:War of the currents|war of the currents]] but for Wikifunctions. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:27, 23 April 2026 (UTC) :::::::Oh, you were referring to {{Z|Z33986}}. I assumed you were stating that something was wrong in the earlier English functions that I missed; I apologize for the misunderstanding. Has there been any centralized discussion on this string vs. monolingual text issue? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:31, 23 April 2026 (UTC) ::::::::Not that I'm aware of, I've brought it up on the telegram twice before, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:49, 23 April 2026 (UTC) ::::::::The centralised discussion is at [[WT:Abstract Wikipedia/2025 fragment experiments#Proposed recommendation: Fragments should return Z11/monolingual strings]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:19, 24 April 2026 (UTC) ::::::: {{re|Theki|Feeglgeef}} Can only functioneers test implementations? For me I can't test it at all... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:32, 23 April 2026 (UTC) ::::::::AFAIK, test cases are only immediately testable during editing of a function if they are connected. This is one of my personal pain points with Wikifunctions, iterating on functions without exhaustive connected test cases makes debugging practically impossible for non-functioneers working on newly-created functions... I (or Feeglgeef) can quickly connect the tests you need for you if you want, although if they are not well-formed they may need to be disconnected again afterwards. Additionally, I could temporarily connect the implementation you are writing so that you can test it on the sidebar as you work, but I'm not sure if this is advisable. That functionality is also something that unfortunately only works when not disconnected. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:43, 23 April 2026 (UTC) :::::::::Yup, agree with you on all points, thanks. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:48, 23 April 2026 (UTC) == Please disconnect implementation == I think I've fixed my issue with {{Z|Z33986}}, but I can't edit an actively connected implementations with my rights. I must admit it is an AI-aided fix, I feel very strongly about disclosing that. Courtesy pinging [[User:Theki]] and [[User:Feeglgeef]]. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:51, 23 April 2026 (UTC) : Additionally, I think the JS might be working. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:52, 23 April 2026 (UTC) : Just to clarify, I mean disconnect the Python implementation please. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:53, 23 April 2026 (UTC) :{{Done}} I've disconnected the Python implementation. :I've also added a couple of tests. The rule is a bit more complicated than adding a maqaf before every character that is not a Hebrew letter. Unfortunately, I don't think I'll have time to fix the implementations any time soon. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:03, 23 April 2026 (UTC) :: Thank you! :: Also, for some reason I thought you put a maqaf before all gershayim, so thanks for correcting me. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:09, 23 April 2026 (UTC) :::No, that's not the rule. :::The rest of this reply is an [[:wikt:info-dump|infodump]], feel free to ignore it :) :::In [https://hebrew-academy.org.il/topic/hahlatot/punctuation/ the Academy's punctuation rules], the rule for adding a maqaf is written kind of badly: שמים מקף ברצף שיש בו שני סוגי גופנים, כגון אותיות ומספרים ("maqaf is added in a sequence in which there are two types of fonts, such as letters and numerals"). These are not different types of "fonts", but different types of characters, and I should email them about it. It gives the examples <span lang="he" dir="rtl">ה־12</span> and <span lang="he" dir="rtl">ב־DNA</span>. It doesn't say anything explicitly about quotation marks, but in other places on the same page, you have stuff like <span lang="he" dir="rtl">ב"הארץ"</span>, and from that I deduce that a maqaf is not needed before double quotes if there are Hebrew letters inside the double quotes. :::That said, a few people do think that there must be a maqaf before double quotes. I have a somewhat surprising example of somebody who always does it: translators of Scientology materials into Hebrew. At least that's what they did last time I looked at them, about ten years ago. Those people are certainly prolific, and they get points from me for consistency, but this not the prevalent standard. (And if I recall correctly, they use the minus and not the proper Hebrew maqaf, and they don't get any points from me for that!) :::Also, the name of the character is just "double quotes" and not "gershayim". Gershayim are mostly for abbreviations, although most people use the same character for them. I use ״ for gershayim, as do a few other nerds, but we're the minority. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:35, 23 April 2026 (UTC) :::: {{re|Amire80}} Yeah, "font" is a weird choice of wording here by the Academy...<br> I think I'll follow your guidance and not use a maqaf for quotes beginning with Hebrew letters. <br> I should also add more tests for different types of quotes, like straight (", '), curly (“, ”, ‘, ’), gershayim (״, ׳), including single quotes.<br> P.S. gotta deduct points from Scientology for being a cult but that's neither here nor there [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:49, 23 April 2026 (UTC) :::: {{re|Amire80}} Courtesy ping because I mistyped your username on the last message. Anyways I'm also gonna do that tomorrow because I'm tired now... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:50, 23 April 2026 (UTC) == Connect implementations == Hello! I'm done with the implementations of {{Z|Z33986}} both in JS and Python, and all tests pass. Pinging @[[User:Amire80|Amire80]] to check if all the tests I've added are alright. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 15:24, 24 April 2026 (UTC) :Connected. It's possible that some more changes will be needed, but it looks OK now. :Another little comment: It should be called "clitic" and not "prefix". [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:56, 24 April 2026 (UTC) : {{re|Amire80}} Thanks for your comment! Luckily labels are easy to edit, so I'll get to it. : Currently I'm working on Bulgarian {{z|Z34072}} and {{z|Z34084}}, along with other Bulgarian functions. After I'm finished with those I'll take your advice. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 16:01, 24 April 2026 (UTC) == Please connect my Bulgarian implementations == I recently created the following Bulgarian functions: * {{Z|Z34070}} (currently broken, I think because another function I built it upon is unimplemented) * {{Z|Z34088}} * {{Z|Z34105}} * {{Z|Z34072}} * {{Z|Z34084}} Can somebody please connect these functions, and perhaps suggest other functions I could localize? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:03, 24 April 2026 (UTC) : Specifically, [[Z34070]] is based on [[Z34072]] [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:05, 24 April 2026 (UTC) :{{done}} for everything that passes, [[Z34070]] still does not work after purging WF's cache, though. For future reference, please request on the [[WF:Community portal|community portal]] instead of the project chat. Thank you for your work! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:03, 24 April 2026 (UTC) :: {{re|Feeglgeef}} Thank you for your help! I will keep in mind to go to the [[project: community portal| community portal]] in future instead for this. :: I still don't understand why {{Z|Z34070}} fails... It's implementation is almost completely identical to [[Z30399]] from {{Z|Z30397}}, unless I messed something up... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:11, 24 April 2026 (UTC) :::{{done}} No, it was mostly just timing out. It is better to use selective fetches where possible. One case is failing to match the expected results, but at least it is returning something. For all I know, it might even be acceptable! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 20:35, 24 April 2026 (UTC) :::: {{re|GrounderUK}} Thank you so much for your help! The one failed case is with a definite article, so I feel like that might be fixed in the future... <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:43, 24 April 2026 (UTC) == Editor experience suggestions == I'm a bit frustrated with the editing experience on Wikifunctions, and I have suggestions based on pain points I've had contributing to this project: * Adding a wizard to create functions, implementations, and tests in one flow, somewhat like Wikimedia Commons' upload wizard * A sandbox for experimenting without changing mainspace functions, and maybe letting non-functioneers connect implementations ([[Project: Sandbox]] doesn't seem to fit this) * We could have functions for creation based on the sandbox, like how Wikipedia has articles for creation and edit requests, * Maybe even another test instance of Wikifunctions, like how Wikidata has [[testwikidata:|Test Wikidata]] I really like this project and I don't mean to whine, but it certainly has a lot of pain points both for technical and non-technical people. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:41, 24 April 2026 (UTC) : It's also really complicated to localize functions, so maybe we should add another wizard for that, where you can choose a language, and then create the new function with the aforementioned function wizard, and it just automatically adds it to the related language configuration object of the related function. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:48, 24 April 2026 (UTC) :# Sounds good to me. :# A sandbox available is [[Z10119]], though an extension-provided sandbox that allows you to manipulate the types, code, and tests easily without interfering with the mainspace would be nice. :# [[WF:Suggest a function|This page]] works to some extent, though it's too messy in my opinion. :# We used to have a "beta cluster" but it [[phab:rOMWC5f625c5846b5f779473fa32c9a02d87e59215dfa|got shut down]] just over a year ago because it was broken. :[[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:07, 24 April 2026 (UTC) == Language parameters in language-specific functions == I think that an effort should be made to give the different natural language options corresponding to different English dialects, Chinese scripts, etc. more of a use (I added the test {{Z|Z34119}} to {{Z|Z26095}} and unsurprisingly it fails). There are two main problems with this approach that I can identify: * If you ask the majority of these functions to make a sentence in British English, much of the time it will give you an output with missing words, because it does not fallback to English labels in the case of a British English label for that item missing. The same applies for every other English dialect, British English is just an example here. * Uninformed editors will probably see the presence of a language parameter on these functions, consider it redundant, and remove it. [[Special:Diff/268074|I have made this mistake before]]. In my opinion, in a perfect world, all of these language generation functions would output monolingual text, and if the user asks for American English text, then American English text is what they'll get. If the user asks for Japanese text in hiragana specifically, then that's what they'll get in return. This is not as high-priority as just rendering text in the language plainly in the first place, but it's something that I feel is still worth devoting some effort to. Right now switching functions to use this paradigm is difficult because, on the one hand, I don't know if consensus tends towards this direction being ideal or advisable, and I don't want to make changes like this without at least notifying the wider community. In addition, all tests break once a parameter is added or removed, and the function editor does not recognize the change in number of parameters and therefore you have to remove the function call, re-add it along with all of its parameters it had previously (which is a tedious cut-and-paste job), and then it will work again. This is something that you can do in five seconds by just adding a few lines of JSON to the test source, but this is not directly editable from the Web browser. This tedium is largely what's preventing me from doing this on a larger scale, besides asking for comments first. If anyone has any insights or comments on this, then that would be appreciated. If a reference of functions with and without the support for language variants is needed, of course [[WF:NLG]] can be perused, but I've also my own list cataloged at [[User:Theki/functions#language]]... Of course, this thread has many similarities to [[#"language" argument for certain functions|the one above]], but this concerns me going out and making this consistent across these NLG functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:09, 24 April 2026 (UTC) :I've created {{Z|Z34122}} as an extension to {{Z|Z34039}} for larger functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:34, 24 April 2026 (UTC) :Just to confirm that I, for one, support a Natural language parameter for all natural-language functions. The concern about getting them all aligned is just that we haven’t finally settled on {{Z|Z11}} being preferred to {{Z|Z89}} or some other type that conserves the text’s provenance, so we risk having to change them all again. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:07, 25 April 2026 (UTC) == “Key not found ()”? == What am I doing wrong in {{Z|Z34137}}? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 00:39, 25 April 2026 (UTC) :You were passing a [[Z6091]] to {{Z|32290}}, but it takes a [[Z6001]]. Fixed. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:10, 26 April 2026 (UTC) ::{{done|Thank you}}! [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 14:13, 26 April 2026 (UTC) == Why is my test failing? == Hello! I recently made {{Z|Z34139}} based on [[wikt:Module:bg-translit]], and the test case {{Z|Z34141}} is failing on both implementations, despite the expected output and actual output being the same as far as I can tell. I tried looking at the Unicode codepoints of the output, but those are also identical. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 06:21, 25 April 2026 (UTC) :Yes, it’s a tricky one. I’ve added a normalize step to the result validation in {{Z|Z34141}}, which confirms it is a normalization issue. It looks like it is in the code but I don’t know whether simply normalizing the result is the way to go. Logically, you would normalize both the input and the result. The implementations of {{Z|Z10384}} show you how to do this. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:41, 25 April 2026 (UTC) == Edit request == Hello! I have an edit request for {{Z|Z23752}} and {{Z|Z23414}}. Please replace all the "an/a" logic with <code>Z21739(Argument reference)</code>, both for readability and for more accuracy ("a university is an institution") <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:50, 25 April 2026 (UTC) :{{D}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:24, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #245 is out: The Foundation's search for the perfect language == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-25|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present an academic paper about Abstract Wikipedia, we discuss our latest Type created, and we take a look at the newest created functions. 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:54, 25 April 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=30325620 --> :@[[User:Sannita (WMF)|Sannita (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], technical meta-question: the newsletter quotes the article: ::the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016) :This quotation sounds sensible, but the article's [https://link.springer.com/article/10.1007/s00146-026-02899-w web version], and the PDF that is downloadable from the same page doesn't actually show the emojis. It rather shows text that looks lacking: ::the only way to contest its algorithm is to click or (Crawford and Gillespie [https://link.springer.com/article/10.1007/s00146-026-02899-w#ref-CR14 2016]) :Where did you get the emojis? Is it your (probably correct) guess or is there a version somewhere that actually shows the emojis? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:16, 25 April 2026 (UTC) ::Scratch that. I've found a version with correct emojis: https://wikihistories.github.io/wikilambda-the-ultimate/ [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:37, 25 April 2026 (UTC) == Requested deletion of test == Please delete {{Z|Z34143}}. this was never valid Bulgarian, I messed up. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:19, 25 April 2026 (UTC) :[[WF:RFD]] please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:40, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|talk]]) 00:57, 26 April 2026 (UTC) </bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == Is it OK to connect the implementation? == Hello! I recently applied for functioneer on [[WF:RFG]], and I was wondering whether I could connect the implementation for {{Z|Z34165}} despite its dependency {{Z|Z34149}} being currently unimplemented. That is <em>if</em> I get accepted. I am planning on implementing it based on [[wikt:module:bg-nominal]], but am still having trouble figuring it out for now. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:04, 26 April 2026 (UTC) == Past tense function == Is there a function like {{Z|Z26039}}, but for the past tense (e.g. "Leo Tolstoy <em>was</em> a writer.")? If not, I will create it myself, I just want to make sure there's not a duplicate. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:10, 26 April 2026 (UTC) : {{Done}} with {{Z|Z34224}}, but I have a few kinks to work out with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:35, 26 April 2026 (UTC) :: I need to create some other similar functions for the past tense, I have some ideas: ::* {{Z|Z26095}} ::* {{Z|Z32643}} ::* {{Z|Z28016}} ::* {{Z|Z26570}} ::* {{Z|Z33975}} ::* {{Z|Z27243}} ::* <ins>{{Z|Z26627}}</ins> ::* <ins>{{Z|Z27627}}</ins> ::* <ins>{{Z|Z27173}}</ins> ::* <ins>{{Z|Z29591}}</ins> :: :: Are there any I have missed? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:57, 26 April 2026 (UTC) :I think that here we are starting to walk on dangerous waters: what does past mean? Is it a recent o a far past? Does it have ripercussions on the present or not? Is it just a thing that happened once, many times or for a continuative period of time? :Consider that various languages distinguish between many different types of past. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:38, 26 April 2026 (UTC) :: {{re|Dv103}} That is a fair point... :: How do we go about solving this problem though? I don't think having every sentence on Abstract Wikipedia be "X is a Y" is a very good idea. :: Maybe we have different functions for all these variations of past you mentioned that just map into "X was a Y." in English? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 13:31, 26 April 2026 (UTC) :::To properly solve this problem, we should use a more complete abstract content representation model, like for example the proposal of [[Wikifunctions:Type proposals/Semantic unit|Semantic units]] (look at [[Wikifunctions:Type proposals/Semantic unit/Douglas Adams|the example]] to see how times could be handled). For now, since we're still stuck with single fragment generation functions (that I hope will be slowly replaced with the complete represenation model, when available), we could just restrict your function to a very specific meaning, like "subject was an instance of, for most of its existence" (which means for example that it could be used to say "Douglas Adams was a writer", but not "Abraham Lincoln was a president", since he only was a president for 4 years). Probably my definition is still too vague, and this is why we need to go beyond these fragment generating functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:47, 26 April 2026 (UTC) ::Nitpick... I don't like that it outputs a string instead of monolingual text. With {{Z|Z26039}} it's used so much that I think it's unfixable in that case beyond deprecating it if people care that much, but {{Z|Z34224}} doesn't even have any connected implementations yet. Consider it, maybe? ::Nitpick 2... {{Z|Z34227}} is missing a language parameter. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:08, 26 April 2026 (UTC) ::: I will consider that! ::: I just did that because that's what {{Z|Z26039}} does, so I assumed I should follow suit with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 26 April 2026 (UTC) == Legacy functions == If and when more robust methods of abstractly representing and generating linguistic content come around, and more efficient ways of creating abstract content are devised and implemented, I suspect that our current methods will require some form of deprecation. This is a significant source of concern for me in relation to WF and AW, questioning how prone our current methods of doing things are and eventually will be prone to obsolescence, and how it will be worked around when it comes. We have over 1 250 articles on AW presently, and these are rather all over the place. I suspect the maintenance burden from keeping these articles up to code will eventually, err, creep up on us, I suppose, and some kind of major refactoring will be necessary. We are definitely in a period of experimentation and whatnot right now but eventually, like with enwiki, some sort of structure and rigor will form and I suspect it will start to become rather boring for me... I, for one, very much enjoy experimenting with new and better ways to do things here. I don't personally mind changing things to use a new and better paradigm if need be, that sort of thing highly excites me, but of course there will be things that are left behind, and I suspect maybe bots will be employed to deal with this? A lot of Wikipedia sister sites seem to do that, e.g. going and fixing up use of deprecated templates. Considering the nature of Wikifunctions and Abstract Wikipedia I suspect certain maintenance tasks will be made simpler or even trivial by the typical uniformity of our implementations. I guess I am just concerned if Wikifunctions or Abstract Wikipedia will ever accrue its own kind of "technical debt" with how we are plowing through things presently, and if there is a plan for how we will eventually seek to mitigate that. Maybe too early to ask this question, but I am a notoriously anxious person, so I thought it wouldn't hurt to raise the question regardless... &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:30, 26 April 2026 (UTC) :I very much agree, thank you for expressing my position so well. {{ping|Immanuelle}} has been using an AI-generated tool (well, they haven't edited in a week, perhaps it's a break or perhaps they don't wish to contribute to the project any more) to create a bunch of articles en masse, which I have warned them multiple times is a bad idea (on top of evolving functions, all of the articles are one-sentence-per-paragraph, [[abstract:Q12184|like so]]). That's why I've been avoiding creating articles recently, I'd say I have a good fourth (no data to support, rough guess) of the comments on the wiki, yet less than a percentage of the article count (only three, including the [[abstract:Q319|first article]], though, so perhaps I'm the next [[w:Special:Permalink/908493298|office.bomis.com]]). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:41, 27 April 2026 (UTC) :: I feel that the overwhelming presence of these low-quality articles (which I admit I myself am [[abstract:Q1710970|guilty]]/[[abstract:Q7601858|of]]/[[abstract:Q39338|creating]], usually as testbeds) may incur a large maintenance burden. I do expect them to be easy to detect, however, as searching for the presence of "deprecated" NLG functions is trivial, and it is possible that replacing them with their future ''even abstracter&trade;'' counterparts could be done automatically since they all have the same signatures and can be expected to create the same form of sentence. If it needs to be done manually for a while or for certain delinquent instances, my hope is that it will be fun, at least for a while. :: I just hope that these hypothetical future waves of "this new and versatile way of abstractly representing linguistic content" obsoleting previous methods and requiring refactoring across all articles is only a one-time thing. We should strive to be as robust and flexible as possible from the outset as each brand new paradigm of abstraction is also a brand new maintenance burden for updating old articles. At the end of the day, at least ''some'' of these articles will still render to many different languages even if their methods of creating those sentences of theirs is completely outdated. Ergo, the time it takes for the switchover to be performed across our articles should not be a persistent inconvenience for users (as, of course, they will always still be able to read the content as it was before since these legacy functions aren't being deleted outright), and the increased availability that the new methods will bring about will likely act as motivation for them to join the effort in refactoring (&#x300C;You're telling me that if I rewrite this article in this cool Lisp-looking stuff then I can probably read it in [[abstract:Q9307|Galician]]?? COOL!&#x300D;). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 20:26, 27 April 2026 (UTC) :::Totally agree. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:54, 28 April 2026 (UTC) :::My vague plan is to implement a default function returning an {{Z|Z89}}, for each language-neutral function. A single function would convert any of these to a {{Z|Z11}}, so that a composition of the two can be implemented as the current default until such time as the language-neutral function is ready to return a [[Z89]]. We can already convert a [[Z11]] to a [[Z89]] so, although there is more to be done in this space, existing language-specific functions could be adapted to return a [[Z89]] quite mechanistically. :::Although we certainly could deliver parallel Z89 functions for each existing Z11 function, I don’t think we should assume that particular outcome. Provided the Z89 captures a lang attribute from the Z11’s language tag, the two representations should be largely interchangeable, although I am expecting a Z89 to carry additional attributes at the span level that would be lost on conversion to a Z11 (along with any higher-level tags and attributes). :::When I say there is “more to be done in this space”, I am referring to a new type that would allow HTML fragments to be represented as tractable Wikifunctions objects, but this is currently drafted only in my head! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:21, 29 April 2026 (UTC) == Filtering types of objects == Hello! I have tried to comb through my own edit history several times, but it's really hard to search for specifics because there's no differentiation between different types of objects (functions, implementations, tests, etc.) in the logs as far as I can tell. Am I missing anything? I want it to work sort of like how filtering by namespace works. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 27 April 2026 (UTC) :There is differentiation, it's just rather hard to look through. Since all ZObjects are just JSON data at their core, you can search for instances of <code>{ "Z1K1": "Z[type]"</code>. I haven't tried this so I'm not sure how well it would work and I know MediaWiki search syntax treats quotation marks as a special character, but I have seen Wikifunctions pages link to searches using this before. There is also [[Special:ListObjectsByType]] but it is sitewide rather than specific to your edit history in particular. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:59, 27 April 2026 (UTC) ::''[It doesn’t help directly here, but please see [[WF:Find]] for more details of how this works.]'' [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:24, 29 April 2026 (UTC) :See the feature requests [[phab:T399244]]/[[phab:T373735]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 06:06, 28 April 2026 (UTC) :The lack of filtering edits by namespace is exactly the problem that I was trying to solve with the [[User:Amire80/wikifunctionsanalytics]] tool. :I even kind of succeeded, but it has two major problems: :# It doesn't have any real frontend, so you have to know some SQL to use it (or ask other people who know SQL). :# It doesn't get information from the live site, but from the dump, which appears to be updated once a month. :I've made a [https://quarry.wmcloud.org/query/104794 sample query for you]. Unfortunately, it won't do anything at the moment because of the second problem—your edits started in April 2026, which isn't over yet, so the dump for it hasn't been processed. But I hope that early in May you'll be able to use the same query and see something useful. :(I plan to add support for recent edits, but I haven't done it yet. Now that I more or less figured out how to process Wikifunctions edits, I'm focused on trying to understand Abstract Wikipedia edits. Processing up-to-date edits from both sites will possibly be the next thing I work on, but if you know some Python and want to try doing it yourself, don't wait for me—[https://gitlab.wikimedia.org/toolforge-repos/wikifunctions-analytics Patches welcome].) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:51, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]], I've just updated the data until the end of April. Now the query to which I linked above gives some results. You can also try running other queries if you know SQL. (Or try asking for other queries if you don't.) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:26, 3 May 2026 (UTC) == [[Z34213]] == I'm not quite sure why this implementation is failing. Could someone take a look? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:24, 28 April 2026 (UTC) :I've [https://phabricator.wikimedia.org/T419933#11863997 notified] the team that this is still occurring, the issue was marked as resolved. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:52, 28 April 2026 (UTC) :Some useful tips: :* create more testcases: sometimes it is a random error, so try to see how consistent it is between testcases :* your implementation is very inefficient, since it fetches items and lexemes a lot of times. Ideally, each item and each lexeme should be only fetched once in all the execution tree. :[[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 06:06, 28 April 2026 (UTC) ::Caching (''should?'') means that the lexeme and item data are cached, so the call doesn't actually execute multiple times. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:51, 28 April 2026 (UTC) :::Are lexemes and items actually cached within the same function execution? Even if they are only partially fetched and/or fetched in bulk? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 17:54, 28 April 2026 (UTC) ::::I don't have any evidence to prove that it works but that's definitely A. what's supposed to happen and B. the ideal behavior. This happens because the Z680X functions can be cached just like any other. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 28 April 2026 (UTC) ::::It is unclear. In general, I believe identical branches are resolved only once in orchestration, but there is also independent caching of Wikidata fetches. ::::According to @[[User:DMartin (WMF)|DMartin (WMF)]] ([https://t.me/Wikifunctions/30374 on Telegram]): ::::<blockquote>Well, no. We have caching of Wikidata entities that have been retrieved, but not of the results of nested function calls. There is a proposal for doing this in the context of the V2 composition language, when it's a bit more mature, and it's regarded as a relatively high priority.</blockquote> ::::It’s hard to tell whether fetches in nested calls are, in fact, cached and available for other nested calls in the same call, since it is not generally the actual fetch that consumes the most resources. Rather (I believe), it is construction and transmission of the result object, which is currently repeated afresh in each nested call (unless it is in an identical branch). ::::I hope that’s clear, and I apologise in advance if it happens to be inaccurate! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 29 April 2026 (UTC) :::::Oh, I should clarify.  There is a lot of caching going on, in several different places.  Lexemes and items ''are'' cached by the orchestrator within the same function execution, even if they are only partially fetched and/or fetched in bulk.  When I said that we don't have caching of the results of nested function calls, I meant that's not happening in general, for all nested function calls in compositions.  But fetching of Wikidata entities gets special treatment, so yes, fetched content from Wikidata is cached, regardless if it was fetched by a top-level call or a nested call. :::::It is also true that the construction of a ZObject from the fetched JSON might happen more than once within the same function execution, depending on how a composition has been structured. However, the construction of the ZObject is actually very fast, compared to the elapsed time of getting the JSON from Wikidata. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 18:04, 1 May 2026 (UTC) == Question about cardinal numbers == I was about to edit {{Z|Z16435}} to add my function {{Z|Z34308}}, but I noticed that none of the other functions have a gender parameter. Should I create a new wrapper function "Bulgarian cardinal, neuter", or should I just remove the gender parameter and always return neuter? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:39, 28 April 2026 (UTC) :The “cardinal” functions should return the words used for “counting” numbers in the abstract. :We should consider converting them to return a {{Z|Z11}} rather than a {{Z|Z6}}. It may even be appropriate to return a {{Z|Z12}} to cater for language variants. Either way, I think that would be the approach to adopt for inflected forms, unless reference to specific lexeme-forms is required. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:52, 28 April 2026 (UTC) ::This. If a native of your language were to count up, which form would they be most likely to use? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:29, 28 April 2026 (UTC) ::: {{re|GrounderUK|Feeglgeef}} Thanks for both your input! ::: I relabeled the aforementioned function to {{Z|Z34308}}, and created a new wrapper function {{Z|Z34457}}. ::: Should I specify that my old function is a monolingual text in parentheses? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:26, 28 April 2026 (UTC) ::::You don't have to, unless you think that is something that would require distinction when viewing the function in a list of search results &c. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:36, 28 April 2026 (UTC) == Optional/nullable function parameters == Hello! Recently, I was informed that Wikifunctions has no optional/nullable function parameters as of now. Are there any future plans to support this, and/or workarounds? Maybe create a union type system like "{{Z|6}} or {{Z|23}}". <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 17:53, 28 April 2026 (UTC) :What I do for this is use an "is empty" function corresponding to the type of the parameter in an If statement. If it isn't empty, the function works as intended. Otherwise, it does something else. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:58, 28 April 2026 (UTC) :Unions are not a thing (yet) on Wikifunctions, but you can always define an argument of type {{Z|Z1}}, which means that all types are allowed (I already did this for {{Z|Z26737}}; note that it is still a ugly workaround, don't use it for high level functions). Also, note that usually on Wikifunctions we use {{Z|Z24}} as the null value. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:00, 28 April 2026 (UTC) :: {{re|JJPMaster|Dv103}} Thanks for your help! :: @[[User:Dv103|Dv103]] told me a function call with a missing parameter is treated as an invalid function call, so how does the "is empty" function work with that? :: Also, setting the type to {{Z|1}} seems naive, like setting the type as <code>any</code> in TypeScript... :: Related question: Are there plans to add default values to parameters (outside of "if empty")? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 18:19, 28 April 2026 (UTC) :::Setting the type to {{Z|Z1}} is actually naive, and that's why I advised you to only use it for low-level functions. Currently there is nothing better. Sometimes, type correctness is not actually checked, so it might seem that nullable types are possible. But it is still an hack, and it could broke anytime since it is not intended behavior. :::I don't think that there are current plans to add default values (but correct me if I'm wrong). The closest thing that comes to my mind is that, if you incorporate Wikifunctions into Wikitext, you can leave empty some fields (only of some specific types) and Parsoid will replace them to their default value. This is done only depending on the type, and not on the functions. For example, {{Z|Z6091}} and {{Z|Z6001}} are assigned the QID associated to the page, and {{Z|Z20420}} is assigned the current date. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:56, 28 April 2026 (UTC) :::@[[User:QuickQuokka|QuickQuokka]]: At the very least, [[Z10008]] accepts a null input. Maybe that feature is unique to the String type—I am not sure. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 19:10, 28 April 2026 (UTC) ::::I think it's just not checked, but it shouldn't be intended. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:20, 28 April 2026 (UTC) ::::Strings and typed lists can be “empty” in the sense that their length can be zero. Typed pairs may also be “empty” in a degenerate sense, but such an object will not be returned from a code implementation. A typed map with no entries will also fail to be returned from code, although it is fine in compositions. ::::For a genuinely optional parameter, I prefer a properly typed list, which at least encourages an argument of the correct type. {{Z|Z813}} is also typically faster than {{Z|Z10008}}. Quite a good example of this approach is {{Z|Z23723}}, where it helps to resolve the type union (using [[Z1]]) for both Z6003K1 and Z6003K3. Of course, there’s nothing to prevent more than one element in the list, but additional elements are easily ignored. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:55, 28 April 2026 (UTC) :Pinging {{ping|Jdforrester (WMF)|prefix=|p=}}, I believe there are no current plans. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:02, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]]: I'm afraid there are no current plans to build out optional params, indeed; we would be happy to review this if a compelling case was made, but it'd be a lot of work to re-build the [[Wikifunctions:Function model|function model]] with that support and ensure we don't break (too many) things. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:11, 28 April 2026 (UTC) == Z6830 for Chinese == I was trying to use {{Z|Z6830}} for implementation in the Chinese-language. And turns out most of the Lexeme on Wikidata is using [[d:Q727694]] as the language instead of [[d:Q7850]]. This makes it impossible to use the mentioned function above, since Standard Chinese is not available (or did I miss something?). Is there a way to fetch lexemes with language=[[d:Q727694]] from item? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:20, 30 April 2026 (UTC) :@[[User:Sun8908|Sun8908]] There is [[Z1006]] for Chinese and it has the language code zh. There is an overview of languages in [[Module:Wikifunctions label]] so you can search there for chinese versions and choose the one you need. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 5 May 2026 (UTC) ::I know that. The problem is when using the function [[Z6830]], it cannot retrieve lexeme with language [[d:Q727694]] (but it is the "Chinese language" with the most current Wikidata lexemes, see [https://ordia.toolforge.org/language/ ordia]). I think it should be a Wikidata problem, I might fix it (possibly by creating the same lexemes with language code zh) on Wikidata. Thanks anyway. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 05:39, 6 May 2026 (UTC) :Could you provide an example of a Chinese lexeme that has a linked Wikidata item, or a Z6830 function call that fails to find such a lexeme where one exists? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 07:55, 6 May 2026 (UTC) ::Here: [[d:Lexeme:L846083]]. I think that's a primary reason of me trying to look into this problem, as the label in zh for [[d:Q6256]] (country) is not a single phrase (see its talk page on WD for more information). This makes some Abstract Wikipedia articles very weird in Chinese when {{Z|Z26570}} is used, so lexeme could potentially fix that. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 10:33, 6 May 2026 (UTC) :::Thank you. It looks as though {{Z|Z6830}} [https://www.wikifunctions.org/view/en/Z6830?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z6830%22%2C%22Z6830K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q6256%22%7D%2C%22Z6830K2%22%3A%7B%22Z1K1%22%3A%22Z6092%22%2C%22Z6092K1%22%3A%22P5137%22%7D%2C%22Z6830K3%22%3A%7B%22Z1K1%22%3A%22Z60%22%2C%22Z60K1%22%3A%22cmn%22%2C%22Z60K2%22%3A%5B%22Z6%22%5D%7D%7D returns that lexeme for language tag "cmn"]. Perhaps that tag should be added into the helpers for {{Z|Z24144}}? If it is widely used for lexemes, perhaps it should have its own {{Z|Z60}}? In any event, improvements might be considered under [[:phab:T390563]] (or otherwise), including amending [[Z6830]] to also consider "cmn" (and "zho", "chi"…?) when requests are made for "zh-hans" or "zho-hant" (or others?) @[[User:Winston Sung|Winston Sung]] @[[User:DMartin (WMF)|DMartin (WMF)]] [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:22, 6 May 2026 (UTC) ::::If you go to [[d:Special:NewLexeme]] and put in [[d:Q727694]] as the language, it is going to tell you it has an unrecognized language code. So I believe "cmn" should not be a {{Z|Z60}} by default? I also started [[d:Wikidata:Project_chat#Lexemes_with_language_Standard_Chinese_(Q727694)|a discussion on WD]] regarding this. I guess we can still use it as a fallback language though if possible. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 03:43, 7 May 2026 (UTC) ::::We don't have a separated <code>cmn</code> BCP 47 language subtag in MediaWiki and Wikidata at the moment. <code>zho</code> and <code>chi</code> are ISO 639 language codes but not BCP 47 language subtags. ::::For Modern Standard Mandarin, please use <code>zh-*</code> language tags for now. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 15:26, 8 May 2026 (UTC) == Key not found error == Is there a reason why I am getting key not found error for this [[Z34677|function]] {{Z|Z34677}}? All the underlying functions run and all the test cases work. The debug information does not give more details. Any pointers? Thanks in advance [[User:Jsamwrites|John Samuel]] 19:24, 1 May 2026 (UTC) :It was passing the [[Z6091]] to {{Z|34641}} when that takes a [[Z6001]]. I've fixed that, but there's some other problem with the logic, so I've left it disconnected. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 19:42, 1 May 2026 (UTC) ::@[[User:YoshiRulz|YoshiRulz]] Thanks a lot. [[User:Jsamwrites|John Samuel]] 20:21, 1 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, 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:21, 2 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=30325620 --> == Any formal process for deletion of pages == Does a formal process exist for the deletion of functions, implementations, and tests that includes a notification system for creators, analogous to Wikidata’s process, explaining the rationale behind the deletion (or proposal for deletion)? [[User:Jsamwrites|John Samuel]] 12:36, 3 May 2026 (UTC) :Does [[Wikifunctions:Requests for deletions]] work? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:00, 3 May 2026 (UTC) :Please see the discussion at [[Wikifunctions talk:Requests for deletions#Should we expect Objects' creators to get pinged on deletion proposals?]]. :As I see it, it is the proposer’s responsibility to consult appropriately before making a request and we expect our administrators to act only when satisfied that appropriate consultation has occurred. In many cases, no consultation is required. Administrators may delete their own contributions without making a request, but this is not a practice I would encourage. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:51, 3 May 2026 (UTC) == Implementation of rational number in JS doesn't match in Z19677 (Rational number) and Z28579 (RGBA colour) == In {{Z|19677}} it's <syntaxhighlight lang=js> { "K1": sign * numerator, "K2": denominator } </syntaxhighlight> but in {{Z|28579}} it's <syntaxhighlight lang=js> [ sign * numerator, denominator ] </syntaxhighlight> '''<span style="font-family:Iosevka,monospace">[[User:沈澄心|<span style="color:#9f3526">dring</span>]][[User talk:沈澄心|<span style="color:#534fa3">sim</span>]]</span>''' 05:15, 4 May 2026 (UTC) == Nested functions in compositions == I wish it will be easier to a add another function about a specific existing function in a function implementation based on a composition. When I write long functions in spreadsheets I usually stat with a small part and then I try to go further and after important steps I test if the output is as expected. I created [[Z34826]] to get the German gender specific occupation lexeme for a specific person based on their gender. I wanted to add a function around the existing one and it was not successful. It is not very easy to implement as it requires the possibily to move a part to another section but I think it can be helpful if it will be implemented. So far I spend more time as expected on the function. Describing it with words what the function needs to do is much easier than implementing it here in Wikifunctions. So I think there needs to be improvement to make Wikifunctions more accessible. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:10, 5 May 2026 (UTC) :Have you tried to use the copy-paste functionality? It is very useful to move parts of composition arounn. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 07:12, 6 May 2026 (UTC) :I've also found the composition editor to be wholly unsuitable for any expressions more than a few levels deep. (Even with the <code>localStorage</code> clipboard, because of its overzealous type checks.) Compositions naturally grow out from the "leaves", the immediate operations on the inputs, while the interface really wants you to build from the "root". I mostly use the [https://yoshirulz.gitlab.io/WikiLambdaBlockly drag-and-drop block editor] which I made to smooth over some of the site's problems, so if you want to try that out and give me some feedback I'd appreciate it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 14:36, 6 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the 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 [[: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/1778520600 May 11, 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]]) 11:16, 8 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=30325620 --> == RGBA colour, spelling... == Something that has always irked me a little bit is the spelling of [[Z28579|RGBA colour (Z28579)]]. I guess this is not unsurprising for me considering my use of US English but I think there is more to it than preference and I want to try to argue for it being changed to use American spelling. I know that this probably has a snowball's chance in hell of actually garnering any support, so I won't really be miffed if the spelling remains as it is, but I thought it wouldn't hurt to raise this regardless. The main issue I have with it is the spelling of the original proposal. When infernostars raised the [[Wikifunctions:Type proposals/RGBA color|type proposal]], the spelling was 「RGBA color」. Of the comments that mentioned the word 「colo[u]r」, two used British spelling while six used the American spelling as used in the proposal. The only thing that really pointed to the use of ''colour'' was the fact that the catalog page on color functions used that spelling already. For all intents and purposes, the spelling of the original proposal should have been maintained, but it was not; [[User:DVrandecic (WMF)|DVrandecic]], the eventual creator of the type, used a different spelling. It should be noted that there was really no reason for this to occur and while it is an undoubtedly minor issue I still believe it should be rolled back and the type should use the spelling of the original proposal and majority of editor comments. In [[abstract:Q936|OpenStreetMap]], there have been keyvalue proposals that have had the finalized spelling that gets put to use be in British English despite the original proposal being in American English; this has usually occurred with proposals relating to 「X center/centre」 tags. This makes sense on the surface, because OpenStreetMap is maintained by a UK organization, and still has close ties to Europe. The Wikimedia Foundation, however, is an ''American'' company. This is often brought up as a fallible argument when debating article spelling on the English Wikipedia, and I don't bring it up to support that 「RGBA color」 should be used for that exact reason, but rather to state that OpenStreetMap's general policy on tag names need not apply here. It appears to me that, at least initially, the majority of 「core contributors」 to Wikifunctions used British English; I can name YoshiRulz, 99of9, GrounderUK, and VIGNERON.<ref group="color">I'm avoiding linking to these folks because I don't think pinging them about this discussion is all too necessary unless they themselves want to be involved; I don't want to clutter their inboxes just to briefly mention them. I pinged Denny because, well, I'm asking him a question directly, but everyone else I would prefer to join this discussion by their own accord... not that I wish for this decision to be confused as me going 「these people use British English so they will probably oppose my idea, I won't invite them to the discussion because of that」...no, I promise you that is not the reason.</ref> I see (or saw) these people ''everywhere'', so it makes sense that British English has prevailed in some sorts on this website, but I don't think that indicates that it should be the ''preferred'' spelling across the website, at least not to the point where a proposal should have its name changed to match such a "consensus".<ref group="color">It could be argued that the front-and-center ''Function catalogue'' using 「catalogue」 is actually indicative of such a "consensus", but ''catalogue'' is in a similar position to the word ''grey'' where I live (that is, the US) in that it is used just as often as its American counterpart. Also, consider Wiktionary's ''Beer parlour'' project chat.</ref> The unnecessary modification of the original spelling is my main argument for changing it back... but of course, I must obligatorily state that on English Wikipedia, it is [[w:Color|Color]] and [[w:RGBA color model|RGBA color model]]; on Wikidata, it is [[d:Q1075|color]] and [[d:Q2325624|RGBA color space]]; in CSS (which typically uses hexadecimal triplets to specify RGBA values), the properties are <code>color</code>, <code>background-color</code>, etc.; bit of a weak jab, but on Schema.org it is [https://schema.org/color color], [https://schema.org/colorSwatch colorSwatch]; et cetera. {{Z|Z28580}} uses ''color'', so does {{Z|Z28591}} and its Python counterpart. Mr. Vrandečić, I have to ask, I'm rather confused... you created the color type using British English spelling, but you were also responsible for the creation of the equality function which uses the American English spelling. You also seem to be writing in American English for the status updates, judging by your use of -''ize'' over -''ise'' endings and use of ''program'' over ''programme'' in [[Wikifunctions:Status updates/2026-04-16]]. Is there something I'm missing or have you switched your preferred variant somewhere along the way? Anyways, do consider this if you wish... again, I don't suppose this will garner much support, it is the ''non-issuest'' of ''non-issues'', but it has irked me to the point where I want to ask about it to get some answers, if nothing else. I am not arguing for every other color function to have its name changed, just the type itself. <references group="color"></references> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 8 May 2026 (UTC) :This is a multilingual project; the <code>en</code> label is <code>RGBA colour</code> and the <code>en-us</code> label is <code>RGBA color</code>. Though I'm not able to switch to <code>en-us</code> via the language picker so that would need to be fixed.<!-- --><br>edit after reading your whole comment: The same is true of {{Q|1075}}, there are labels specified for multiple English variants. (In {{Q|2325624}} it's only an alias.) I agree that other websites' choices aren't binding on us, but from that, I conclude that the more widespread British/Commonwealth spellings should be used for the generic <code>en</code>. As for myself, I'm Aussie and I will continue to use the BrE spellings ([[w:en:Oxford_spelling#Language_tag_comparison|+ "routing"]], TIL) if only by muscle memory.<!-- --><br>[[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 17:42, 8 May 2026 (UTC) :: Your lattermost point would normally be fine in a perfect world. Wikipedia's <code>convert</code> function defaults to "international" English, which I don't personally take issue with because it happens that we here in America are actually outliers for saying and spelling things differently... err, or we were for a while at least, nowadays it seems like an even split (plus you have "yield" vs. "give way" which is effectively the logical opposite of US's use of "meter" over "metre"). :: However, this is not a perfect world, and I don't think <code>en</code> should correspond to any particular variant. It is too fragmented across all software at this point to impose such a requirement. The inability to switch to <code>en-us</code> on this website foregoes an easy and simple solution to this problem that makes everyone happy, because the yanks (such as myself) can't be happy because we can't see the labels in American English even if we wanted to, and the other folk can't switch either as far as I'm aware (and the en-CA and en-GB languages in the preferences page seems to be deprecated). My point being, <code>en</code> is abused to mean "en-UK" just as often as it is abused to mean <code>en-US</code>; I think a decision shouldn't be made on such an assumption of one "default". &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:48, 12 May 2026 (UTC) :Hi @[[User:Theki|rae]]! I have no opinion nor preference on this, and given my background, I am just entirely confused about my spelling preferences myself, as you can tell from my inconsistent usage. I learned British English in school and used that for maybe two decades or so, but moved to the US and lived there for more than a decade, enough to be naturalized, but now I am back in Europe and I am technically a professor at King's College London, soooo.... honestly, I do not know. I don't remember having put too much thought into it at the moment I created it. The good thing is that in Wikifunctions, just as in Wikidata, it is easy to change, without messing things up too much (unlike in Wikipedia), so my suggestion is, just make the change, see if anyone complains, and if they do, discuss it more. I don't know if there is a guideline already in Wikifunctions about the variants. I am happy either way, and honestly, I keep forgetting which variant is which most of the time. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 18:16, 10 May 2026 (UTC) :: I can definitely understand this, although I am unfortunately rather passionate about any minutiae involving preferential minor differences in ''anything'', of which AmE vs. BrE chiefly is. So I dedicate a lot of headspace to it. More than I should. Not that I wish to imply that the comment above that I have wrote is of an irrational nature, or done out of spite or pure emotion and subjectivity; I do genuinely believe that ''RGBA color'' is beyond just a personal preference and is just logical. I may boldly go and change it, but for some reason I was expecting that changing the English label of a Type would require elevated permissions, and I also didn't want to do it only to get immediately reverted because it ''did'' strike a chord with someone, when I could instead see how apathetic, supportive, or in opposition interested people are beforehand and ''then'' act accordingly. I was not meaning to antagonize you over your spelling habits, I did actually use British English for a few years starting in 2020 before I went back to American English, so I'd be a hypocrite for me to decry you for not always sticking to some arbitrary standard of spelling words over the other. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:55, 12 May 2026 (UTC) :Although I spell it “colour”, I think it makes more sense to use “color” for the type, since that is almost always the required spelling when the string functions as a keyword. :More generally, though, Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en". This is unusual, in my experience, as "en" is widely misused in place of "en-US", where there are recorded spelling differences. :(I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere. Use of -ize rather than -ise is a matter of personal preference or house style, but regional autocorrect encourages -ise.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:00, 12 May 2026 (UTC) :: ''Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en"'' :: Definitely agreeing with you on the latter being a good choice. However, I suspect the favoring of "colour" over "color" may be because, in terms of language codes, when sorted alphabetically <code>en-us</code> actually comes ''after'' <code>en-gb</code>. Although, the frontend seems to be sorting <code>en-ca</code> after <code>en-gb</code>, so I don't actually know how correct that is. :: ''I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere'' :: The context of the spelling was "''No program for the NLG SIG meeting for next Tuesday has been proposed''". In that usage context, I think it makes sense to assume that ''program'' is not being used to refer to a computer program, but to a ''program of events'' or similar, something that you would spell as a ''programme'' in British English. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 12 May 2026 (UTC) :{{s}} this. I'm obviously biased but I believe American English is preferable generally, American dominance on the internet (our Department of Defen'''s'''e invented it!) and rapidly-increasing consumption of American media by international English speakers means that more people use American English's conventions, this is clear through for example [http://trends.google.com/explore?q=color%2Ccolour&date=all&geo=Worldwide search trends] (though they aren't particularly reliable). Perhaps this is a bit of a supremacist opinion, but we should have internal consistency, and if we must choose, American English should be our first choice (then Indian and then British English) [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:10, 12 May 2026 (UTC) :: This is rather flawed reasoning, though. I think probably any given British or Indian person would not agree on using that as the reasoning for this, not that you are necessarily ''completely wrong'', but if this is not a good enough reason for English Wikipedia's (admittedly extremely flawed) ''ENGVAR'' policy then I don't think it's likely it will pass here either. :: Although of note is that [https://books.google.com/ngrams/graph?content=color%2Ccolour&year_start=1800&year_end=2022&corpus=en&smoothing=3&case_insensitive=true Google ngrams] agree with you, but "color" vs. "colour" is an eternal holy war that will not be won by demonstrating that more books use US spelling over Commonwealth spelling. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:44, 12 May 2026 (UTC) :::You're probably right that it's not very sound. I'm biased in that other varieties of English irk me, and that's probably mutual for people who are used to other varieties of English when they read what I write! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:56, 12 May 2026 (UTC) :I've decided to boldly [[Special:Permalink/274271|make the change]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:02, 12 May 2026 (UTC) :: Thank you. Considering both you and GrounderUK seem to consider it an okay change, I think this will do for now. :: I should note that the matter of whether to move [[Wikifunctions:Catalogue/Colour functions]] in response to this (however this discussion will ultimately turn out) is a whole other can of worms, in my view. I can't say I have an opinion on that at the moment, but I'm putting it out there regardless. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:06, 12 May 2026 (UTC) :::Personally, I'm in favor of moving the page and renaming all of the items on it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:10, 12 May 2026 (UTC) ::I don't like this (exactly because of the American hegemony you cited), but again, it shouldn't matter because the software is meant to be multilingual. Clearly there's a bug preventing you from picking an English variant/dialect as your display language. But the search bar and Function/Type autocompletion do check the English variants for matches. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 15:15, 12 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[abstract:User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:31, 11 May 2026 (UTC) :Thank you for dedicating your time to writing this, it is very informative. I will try to add input once I'm not in over my head with finals. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:27, 12 May 2026 (UTC) == Display function for HTML fragment == Currently, any collapsed Z89 literal appears as<blockquote>&lt;&gt; [[Z89|HTML fragment]]</blockquote>If I were to create a new Function which returned something like<blockquote>&lt;&gt; 123-byte HTML fragment <q><nowiki><td><span lang=</nowiki>&hellip;</q></blockquote>could that be connected to replace the collapsed form, or would it require changes to the Wikilambda software? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 16:14, 11 May 2026 (UTC) :It might work, but I doubt it. Those angled brackets suggest that the collapsed form is not simply defaulting to the type’s label. Looking at [[:phab:T410509]], I’ve concluded that enhancements to the collapsed form were never considered, rather than being actively rejected. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:12, 12 May 2026 (UTC) ::[[:Phab:T391985]] documents the original design. Note the fifth bullet point under “Acceptance criteria”. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:21, 12 May 2026 (UTC) :I'm not sure the byte-size is necessary, but the outer tag (or first outer tag, though generally I'd prefer most fragments use a wrapper tag if it needs multiple like JSX does, but that's a whole different topic) would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:51, 12 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in 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]]) 14:36, 15 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 --> == [[Z34510]] == This function, which determines if a Wikidata item for a {{q|5}} has an undeprecated {{p|21}} statement of {{q|6581097}}, returns false for {{q|173399}}, a transgender man. This is because his item assigns his P21 statement to {{q|2449503}}, not {{q|6581097}}. I'm not sure how to account for this discrepancy. Should {{z|34510}}: # Include {{q|2449503}} as a value that can lead to a true result, # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a man?") could return true for either "male" or "trans man", # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a trans man?") could return true for "trans man", # Not exist at all? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:48, 16 May 2026 (UTC) :I can't think of a single use case where you would need to determine if a person is a cisgender man and nothing else. Functions are good for generalizing across multiple possibilities when they exist, so I think it would be best if trans men were considered a part of the criteria for returning a true value. If asking for specifically {{q|6581097}}s and ''nothing'' else was desired then the function name would be a misnomer as Elliot Page is inarguably a male (at least in the view of most reasonable and intelligent people). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:03, 16 May 2026 (UTC) r1gvw20pkmxcozkyl1omln7a9h0lf2v 275557 275549 2026-05-16T20:01:16Z YoshiRulz 10156 /* Z34510 */ Reply 275557 wikitext text/x-wiki {{shortcut|[[WF:CHAT]]|[[WF:PC]]|[[WF:VP]]}} __NEWSECTIONLINK__ [[Category:Help]] <!-- please do not remove this line --> Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc. Other places to find help: * [[Wikifunctions:Administrators' noticeboard]] * [[Wikifunctions:Report a technical problem]] * [[Wikifunctions:FAQ]] {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |timeout=30 }} {{Archives|{{#tag:div|<br />{{Flatlist|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1|hideredirects=1}} |class=mw-collapsible-content|style=font-size:92%;}}|class="mw-collapsible mw-collapsible-toggle mw-collapsed"}} |prefix=WF:Project chat/Archive/ }} == "language" argument for certain functions == Hello. I am relatively new to Wikifunctions. Recently, I tried to create functions for Chinese translation of {{Z|Z26570}} and {{Z|Z26095}} (which became [[Z32788]] and [[Z32900]]). During the creation of these functions, I was trying to take {{Z|Z32212}} as reference. And I realized that the defining role sentence function is taking <code>language</code> as an argument (and the test case of the Chinese-language function already contains two varieties of Chinese). This makes it possible to output monolingual text in <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code>, or any varieties of the language. I think for this reason, it is better to have <code>language</code> as arguments for the implementation of Z26570 and Z26095, and potentially more functions that require {{Z|Z14294}}, since it would output the varieties code instead of just saying <code>zh</code> for <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code> in the output of type {{Z|Z11}}. I am not sure how the fallback mechanism works if one of the language (varieties) do not have a labels/lexemes, but to me, it is reasonable to have a <code>language</code> argument. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 09:38, 31 March 2026 (UTC) :The functions you mention do have a language argument. For Wikifunctions, the {{Z|Z60}} can be at a higher or lower level; whether a {{Z|Z11}} is for a language or a variant is determined by the function that constructs it. Please see {{Z|Z26565}} for an example and feel free to add test cases in Chinese. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:54, 11 April 2026 (UTC) ::Hello @[[User:GrounderUK|GrounderUK]], thanks for the answer. I understand that whether {{Z|Z11}} is for a language or a variant depends on the function. But that is exactly what I am asking for. It is true that [[Z26570]] and [[Z26095]] takes [[Z60]] as argument, but the language-specific functions in {{Z|Z29843}} and {{Z|Z26096}} don't. ::Let me give you an example: INPUT to [[Z26570]]: <code>entity</code>: Tokyo, <code>class</code>: city, <code>location</code>: Japan, <code>language</code>: zh-cn, the config would select [[Z33030]] (created after my previous comment by elseone) as the implementation, and it would RETURN 东京是日本的一个城市。(zh-hans), which is not zh-cn as requested in the INPUT. It would also be using the term not for the variant (when it is different) because it is hardcoded to use the term in zh-hans. However, if we have the implementation like [[Z32790]] (which was created by me but a natural language argument was added by elseone) or [[Z32213]] (that works in the defining role sentence function because of the extra argument), it could cater for different variant. ::If we don't have the language argument in the language-specific function, the desire for article creation on Abstract Wikipedia would be to create a function for every variant. Is it then better to create functions for every variant? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:18, 11 April 2026 (UTC) :::I forgot to mention that there are some hardcoding in {{Z|Z32790}} as well, but I cannot fix it because it is a connected function and I am not a functioneer. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:31, 11 April 2026 (UTC) ::::Okay, I think it’s safe to disconnect this one as the function is not yet configured for use on Abstract Wikipedia. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:04, 11 April 2026 (UTC) :::Ah, sorry… I misunderstood you. I agree that the called function should be able to accept the original language argument. That is simpler in theory than in practice, because the configured functions all have to have the same argument types, as I understand it. I’m not sure which the best approach is, really, but we probably want to avoid two levels of configuration. That suggests that all language-specific functions would need to accept the additional argument, which is unrewarding work for someone. @[[User:99of9|99of9]], @[[User:Jdforrester (WMF)|Jdforrester (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]] Any thoughts? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:57, 11 April 2026 (UTC) ::::I mean, we would need to modify all the functions in each language, which could take some time. But we are still in an early stage. If we don't fix it now and we want to fix it later, it would be a disaster. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 19:25, 11 April 2026 (UTC) :::::Agreed. And we probably want them converted to HTML too, with separate language spans for text in different languages. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:35, 11 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]: This sounds like a reasonable change to make. Note that (given these Functions are primarily for use on Abstract Wikipedia), altering/replacing them to return Z89/HTML fragments is already a desired but breaking change, so making a second breaking change at the same time is probably easiest for fixing things swiftly. That said, that's of course a decision for the Abstract Wikipedia and Wikifunctions communities, not me! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:43, 12 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]@[[User:Sun8908|Sun8908]] to make it a non-breaking change, I've created {{Z|Z34039}} which allows a composition {{Z|Z34043}}. This way you can make functions which either need the specified variant or don't! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:52, 24 April 2026 (UTC) :I have now created {{Z|Z33465}}, which is an implementation of [[Z26570]]. Maybe we can migrate to use that function when more (language-specific) functions for it are ready? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:19, 14 April 2026 (UTC) == No place to ask to activate a function? == I just discovered the {{Z|Z11390}} function and decided to make an overarching language-selecting function for it. After some fiddling around and studying how {{Z|Z32321}} and its set works, I now have {{Z|Z33439}} which has a config object ({{Z|Z33441}}) that selects between the two preexisting language-specific versions I found (English and Malayalam) and the new one I created for my other native language, {{Z|Z33440}}. Except I can't get these to work, because, from what I understand, only [[Wikifunctions:Functioneers|functioneers]] can activate newly created functions and implementations? So where do I apply for the {{Z|Z33439}} and {{Z|Z33440}} functions to be activated? Perhaps we should have a place to ask for it, a la [[w:WP:NPP]] — call it [[Project:New Functions Patrol|New Functions Patrol]] if you will. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] ([[User talk:UndueMarmot|talk]]) 08:58, 14 April 2026 (UTC) :There's [[Wikifunctions:Community portal]] for this. By the way, {{Z|Z33445}} doesn't work because all the code must be inside the main function in Python code. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 09:19, 14 April 2026 (UTC) ::Huh. How could I have missed that? ::But anyway, I've moved the code in {{Z|Z33445}} into inside the main function block. ::Is there any reason why WF decided not to simply allow anyone to write functions? After all, that's how it works with wikitext templates, and these functions are fundamentally serving the same purposes as templates, just written in a different way. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 11:25, 14 April 2026 (UTC) :::I've fixed a couple of technical issues, but tests still fail. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:28, 14 April 2026 (UTC) ::::The tests pass now after some more changes to the code: [[Special:Diff/265232/cur]]. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 12:01, 14 April 2026 (UTC) :::::{{D|Connected}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:02, 14 April 2026 (UTC) :::I think it's a security issue, since Wikifunctions implementations could teoretically be malicious. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:29, 14 April 2026 (UTC) ::::This ^^^. We're very lenient, though, once you've created a few working functions you can apply for the right, per [[WF:Functioneer]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:26, 14 April 2026 (UTC) ::::That explanation [[phab:T343559#11421293|doesn't add up]]. A reason to limit ''connection powers'' to Functioneers might be to prevent vandalism, considering Functions can be used across wikis. But user-provided code is already being executed even without a Functioneer connecting it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 April 2026 (UTC) == Actual difference between {{Z|Z26039}} and {{Z|Z26095}} == What is the actual difference between these two functions? I ask, since it seems to me that the current distinction is more or less that the first one doesn't use an indefinite article in English, while the second does. Which is not a good distinction in a project that should be language neutral. This doubt emerged from my use of the first one in [[abstract:Q124441]], which @[[User:Hogü-456|Hogü-456]] made me notice that is probably wrong. My question is: why is it wrong? How could we clarify the difference? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:46, 19 April 2026 (UTC) :I think the difference is if there is an indefinite article like a or an before the subject or not. In German there can be cases where a definite article is necessary before the subject. I looked at the functions and before the object both times an article is mentioned. As it depends on the language and the word what is the correct function to use I hope it will be clarified and it is an example of the necessity to have a human with understanding in a specific language check it. I hope there will be longer functions what generate more content about a specific kind of item. Then it is necessary to write one such function per language and it can be then applied to several items. It still requires checks and so maybe it is better to write down what item category needs what kind of introduction sentence function for what language. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:05, 19 April 2026 (UTC) ::The point of these two functions (and of the entire Abstract Wikipedia project) is that they should be defined in a purely language-independent way, so that the translation to actual language can be done automatically. This is the reason why these functions have been renamed; I think that this attempt was not succesful, since meaning is still unclear. My proposal to clarify them would be to invoke the concept of [[w:specificity (linguistics)|specificity]]: {{Z|Z26039}} should be named "specific subject is instance of (string)", and should be used only when the QID of the subject uniquely identifies a single thing; {{Z|Z26095}} should instead be renamed in "non-specific subject is kind of (Monolingual text)", and should be used when the QID refers to a multitude of real life items, and we are specifying the class that all these item belong to. This clarification would not still be enough, since it doesn't explain how mass nouns are handled (is water a unique thing? Does {{Q|Q7802}} refer to a single piece of bread or to the entirety of bread, like water?). This problem is very tricky, since mass noun are language-specific and blurry the line between these two functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 20:58, 19 April 2026 (UTC) :Simply put, one corresponds to P31 and the other to P279. Paris is an {{Q|P31}} a {{Q|Q1549591}} :whereas a {{Q|Q1549591}} is a {{Q|P279}} (alias “kind of”) {{Q|Q515}}. Whether the Wikidata knowledge representation will be sufficient to resolve into fluent natural language representations in all languages is, of course, a crucial question. Where it is not, the Abstract Wikipedia knowledge representation will need to supplement the Wikidata content with additional details about the relation between the participants or the participants themselves, and these details should be language-neutral, to the extent that this is practicable. The item {{Q|Q124441}} has no [[:d:Q124441#P31|P31]] statements; it has only [[:d:Q124441#P279|P279]]s, including one relating it to {{Q|Q212920}}, which suggests {{Z|Z26095}} is the appropriate choice here even if the rendering in some languages is the same. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:52, 19 April 2026 (UTC) ::Thanks for explaining it. I think that I'll change the implementation of {{Z|Z26095}}, so that in Italian it produces more or less the same output of {{Z|Z26039}} (both with the definite article). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:24, 20 April 2026 (UTC) == Equivalent of Z6830 for lexemes == Is there an equivalent of {{Z|Z6830}} that enables retrieving all lexemes pointing to a particular lexeme using a specific property? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 21:06, 20 April 2026 (UTC) :There's {{Z|6831}} but I think that's slightly different again to what you're after. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 12:31, 21 April 2026 (UTC) ::Thanks for sharing that one, I did not know it existed. But you are right, it’s not quite what I am looking for. I want a function that would take a Wikidata property reference (like P5191, which is ‘derived from lexeme’) and a Wikidata lexeme reference, and return a list of lexemes that reference that lexeme using that property. [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 13:23, 21 April 2026 (UTC) == Storing huge datasets == It is not a necessity I suppose, but an idea came to me earlier to write a function that would give the corresponding [[en:Shavian alphabet|Shavian alphabet representation]] of an English word written with the Latin alphabet, or perhaps apply that operation to an entire sentence. However, just trying to guess as to what the IPA pronunciation of each word passed into it could be is is both not ideal (pronunciations obviously can and will vary widely between accents) and infeasible <s>(Wikidata lexemes don't really seem to account for pronunciation)</s>. It happens, though, that a comprehensive Shavian dictionary exists named the [https://readlex.pythonanywhere.com/ ''Read Lexicon''], which uses pronunciation and spelling similar to that used by the creator of the alphabet himself. This would be a good dataset to use in performing this translation in the function, but it appears that, all in all, the total size of the dictionary is [https://github.com/Shavian-info/readlex/blob/main/readlex.json ''nearly 26MB''] when formatted as JSON, which would certainly be larger when converted into a typed list. I am wondering if this will ever be feasible or admissible, or if there is really a way around this if importing such a large set of data is deemed impractical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 22:30, 20 April 2026 (UTC) :{{re|Theki}} "Wikidata lexemes don't really seem to account for pronunciation"" is patently untrue; not only does every Bokmål lexeme form have IPA attached to it (thanks to Jon Harald Søby), but there are lots of languages--including English--that have pronunciation information, whether through IPA or otherwise, indicated on their forms. The big issue of course is that adding this data is not always possible to perform efficiently--for instance, I'd love to have Yiddish pronunciation respellings from Paul Abelson's dictionary on as many English forms as possible, but this dictionary not being previously processed makes this difficult. The data set you have brought up, if a suitable reading of [[:m:Wikilegal/Lexicographical_Data]] allows it, could be added as {{P|7243}} statements on various English forms. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 23:20, 20 April 2026 (UTC) ::Well, sorry... I haven't witnessed these pronunciation statements before, I wasn't aware of their existence until you pointed it out. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 21 April 2026 (UTC) :I got 1,900,000 characters into [[Z33875]] before the UI gave up on me. I'm not sure what the limit is. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:21, 21 April 2026 (UTC) == Could not serialize input JS object: Number <small><small>[insert tested number here]</small></small> == I'm not one to throw my problems at others, but I have no idea how to fix this. Am implementing {{Z|Z24602}} in JavaScript, which requires returning a typed map. It now works for every type of value except numbers. Tried explicitly converting the numbers to float64, but either way it throws the error above. Would appreciate it if anyone could diagnose or fix the problem, as my knowledge of Wikifunctions is amateur at best. Thank you. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:32, 23 April 2026 (UTC) :The quick answer is that like some list-related functions, code implementations returning typed maps are not possible unless the type of the objects in the map is specified in the function signature (e.g. if it was a map from Strings to Natural numbers only). So unfortunately, I think you've chosen a function that is not really possible at the moment. There are a few ideas of how we might address this, but for the moment, work on something else. Sorry! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:21, 23 April 2026 (UTC) :Maybe explicitly using [[Z13518|natural numbers]] would work? I would try using <code>{ "Z1K1": "Z13518", "Z13518K1": "[number]" }</code> to represent numbers, perhaps, and seeing if that works. Of course, you would also probably have to adapt this for other types that cannot be serialized, and I'm not sure how easy that would be to generalize (assuming [[w:Don't repeat yourself|DRYness]] is desired). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:39, 23 April 2026 (UTC) == Help with creating a function for Abstract Wikipedia == Hello! I was inspired by {{Z|Z26570}} to create {{Z|Z33975}}, however I'm not sure how I add specific language implementations here. Can anybody help me? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 10:41, 23 April 2026 (UTC) : I think I figured it out, I created a new object with the language config type, added {{Z|Z14310}} to my implementation, and added a new function for English... At least I think that's how it works... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 13:16, 23 April 2026 (UTC) ::You have the right idea, as far as I know. I went ahead and connected the implementations you created as they appear to work fine for English, and added a test for {{Z|Z33975}} (which passes [[File:Twemoji 1f601.svg|24px]]). I also corrected an error you made on the config object where you appear to have accidentally connected English to {{Z|Z33975}} instead of {{Z|Z33977}}. Thank you for contributing! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 23 April 2026 (UTC) ::: {{re|Theki}} Thank you so much for you help! Could you please kindly also connect the implementations for {{Z|Z33986}} which I just made, which is going to be used for the Hebrew implementation of {{Z|Z33975}}. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:11, 23 April 2026 (UTC) ::::You seem to be returning the wrong type in both implementations. Functioneers should not connect implementations that don't work for non-functioneers. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:13, 23 April 2026 (UTC) ::::: {{re|Feeglgeef}} Oh thank you for pointing that out! I am still a bit new to this project and confused, so I need to read up some more about this. How do I return a monolingual text object? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:17, 23 April 2026 (UTC) ::::::I'm trying to fix it for you, the construction of ZObjects in code implementations is a bit difficult right now. Since the State origin using entity and class function will (presumably) be composition, perhaps {{Z|33975}} can be adjusted to return a string, using {{Z|26107}} and {{Z|26107}}? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:21, 23 April 2026 (UTC) :::::I did not notice any discrepancies from looking at the functions by themselves, and it seemed to work fine on my end. Is it bad practice for NLG functions to return the monolingual text type? I had assumed it was logical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:24, 23 April 2026 (UTC) ::::::Both implementations are failing all three tests on my end. No consensus has been established as to whether monolingual texts or strings should be used, so it's like the [[w:War of the currents|war of the currents]] but for Wikifunctions. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:27, 23 April 2026 (UTC) :::::::Oh, you were referring to {{Z|Z33986}}. I assumed you were stating that something was wrong in the earlier English functions that I missed; I apologize for the misunderstanding. Has there been any centralized discussion on this string vs. monolingual text issue? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:31, 23 April 2026 (UTC) ::::::::Not that I'm aware of, I've brought it up on the telegram twice before, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:49, 23 April 2026 (UTC) ::::::::The centralised discussion is at [[WT:Abstract Wikipedia/2025 fragment experiments#Proposed recommendation: Fragments should return Z11/monolingual strings]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:19, 24 April 2026 (UTC) ::::::: {{re|Theki|Feeglgeef}} Can only functioneers test implementations? For me I can't test it at all... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:32, 23 April 2026 (UTC) ::::::::AFAIK, test cases are only immediately testable during editing of a function if they are connected. This is one of my personal pain points with Wikifunctions, iterating on functions without exhaustive connected test cases makes debugging practically impossible for non-functioneers working on newly-created functions... I (or Feeglgeef) can quickly connect the tests you need for you if you want, although if they are not well-formed they may need to be disconnected again afterwards. Additionally, I could temporarily connect the implementation you are writing so that you can test it on the sidebar as you work, but I'm not sure if this is advisable. That functionality is also something that unfortunately only works when not disconnected. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:43, 23 April 2026 (UTC) :::::::::Yup, agree with you on all points, thanks. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:48, 23 April 2026 (UTC) == Please disconnect implementation == I think I've fixed my issue with {{Z|Z33986}}, but I can't edit an actively connected implementations with my rights. I must admit it is an AI-aided fix, I feel very strongly about disclosing that. Courtesy pinging [[User:Theki]] and [[User:Feeglgeef]]. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:51, 23 April 2026 (UTC) : Additionally, I think the JS might be working. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:52, 23 April 2026 (UTC) : Just to clarify, I mean disconnect the Python implementation please. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:53, 23 April 2026 (UTC) :{{Done}} I've disconnected the Python implementation. :I've also added a couple of tests. The rule is a bit more complicated than adding a maqaf before every character that is not a Hebrew letter. Unfortunately, I don't think I'll have time to fix the implementations any time soon. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:03, 23 April 2026 (UTC) :: Thank you! :: Also, for some reason I thought you put a maqaf before all gershayim, so thanks for correcting me. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:09, 23 April 2026 (UTC) :::No, that's not the rule. :::The rest of this reply is an [[:wikt:info-dump|infodump]], feel free to ignore it :) :::In [https://hebrew-academy.org.il/topic/hahlatot/punctuation/ the Academy's punctuation rules], the rule for adding a maqaf is written kind of badly: שמים מקף ברצף שיש בו שני סוגי גופנים, כגון אותיות ומספרים ("maqaf is added in a sequence in which there are two types of fonts, such as letters and numerals"). These are not different types of "fonts", but different types of characters, and I should email them about it. It gives the examples <span lang="he" dir="rtl">ה־12</span> and <span lang="he" dir="rtl">ב־DNA</span>. It doesn't say anything explicitly about quotation marks, but in other places on the same page, you have stuff like <span lang="he" dir="rtl">ב"הארץ"</span>, and from that I deduce that a maqaf is not needed before double quotes if there are Hebrew letters inside the double quotes. :::That said, a few people do think that there must be a maqaf before double quotes. I have a somewhat surprising example of somebody who always does it: translators of Scientology materials into Hebrew. At least that's what they did last time I looked at them, about ten years ago. Those people are certainly prolific, and they get points from me for consistency, but this not the prevalent standard. (And if I recall correctly, they use the minus and not the proper Hebrew maqaf, and they don't get any points from me for that!) :::Also, the name of the character is just "double quotes" and not "gershayim". Gershayim are mostly for abbreviations, although most people use the same character for them. I use ״ for gershayim, as do a few other nerds, but we're the minority. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:35, 23 April 2026 (UTC) :::: {{re|Amire80}} Yeah, "font" is a weird choice of wording here by the Academy...<br> I think I'll follow your guidance and not use a maqaf for quotes beginning with Hebrew letters. <br> I should also add more tests for different types of quotes, like straight (", '), curly (“, ”, ‘, ’), gershayim (״, ׳), including single quotes.<br> P.S. gotta deduct points from Scientology for being a cult but that's neither here nor there [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:49, 23 April 2026 (UTC) :::: {{re|Amire80}} Courtesy ping because I mistyped your username on the last message. Anyways I'm also gonna do that tomorrow because I'm tired now... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:50, 23 April 2026 (UTC) == Connect implementations == Hello! I'm done with the implementations of {{Z|Z33986}} both in JS and Python, and all tests pass. Pinging @[[User:Amire80|Amire80]] to check if all the tests I've added are alright. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 15:24, 24 April 2026 (UTC) :Connected. It's possible that some more changes will be needed, but it looks OK now. :Another little comment: It should be called "clitic" and not "prefix". [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:56, 24 April 2026 (UTC) : {{re|Amire80}} Thanks for your comment! Luckily labels are easy to edit, so I'll get to it. : Currently I'm working on Bulgarian {{z|Z34072}} and {{z|Z34084}}, along with other Bulgarian functions. After I'm finished with those I'll take your advice. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 16:01, 24 April 2026 (UTC) == Please connect my Bulgarian implementations == I recently created the following Bulgarian functions: * {{Z|Z34070}} (currently broken, I think because another function I built it upon is unimplemented) * {{Z|Z34088}} * {{Z|Z34105}} * {{Z|Z34072}} * {{Z|Z34084}} Can somebody please connect these functions, and perhaps suggest other functions I could localize? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:03, 24 April 2026 (UTC) : Specifically, [[Z34070]] is based on [[Z34072]] [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:05, 24 April 2026 (UTC) :{{done}} for everything that passes, [[Z34070]] still does not work after purging WF's cache, though. For future reference, please request on the [[WF:Community portal|community portal]] instead of the project chat. Thank you for your work! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:03, 24 April 2026 (UTC) :: {{re|Feeglgeef}} Thank you for your help! I will keep in mind to go to the [[project: community portal| community portal]] in future instead for this. :: I still don't understand why {{Z|Z34070}} fails... It's implementation is almost completely identical to [[Z30399]] from {{Z|Z30397}}, unless I messed something up... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:11, 24 April 2026 (UTC) :::{{done}} No, it was mostly just timing out. It is better to use selective fetches where possible. One case is failing to match the expected results, but at least it is returning something. For all I know, it might even be acceptable! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 20:35, 24 April 2026 (UTC) :::: {{re|GrounderUK}} Thank you so much for your help! The one failed case is with a definite article, so I feel like that might be fixed in the future... <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:43, 24 April 2026 (UTC) == Editor experience suggestions == I'm a bit frustrated with the editing experience on Wikifunctions, and I have suggestions based on pain points I've had contributing to this project: * Adding a wizard to create functions, implementations, and tests in one flow, somewhat like Wikimedia Commons' upload wizard * A sandbox for experimenting without changing mainspace functions, and maybe letting non-functioneers connect implementations ([[Project: Sandbox]] doesn't seem to fit this) * We could have functions for creation based on the sandbox, like how Wikipedia has articles for creation and edit requests, * Maybe even another test instance of Wikifunctions, like how Wikidata has [[testwikidata:|Test Wikidata]] I really like this project and I don't mean to whine, but it certainly has a lot of pain points both for technical and non-technical people. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:41, 24 April 2026 (UTC) : It's also really complicated to localize functions, so maybe we should add another wizard for that, where you can choose a language, and then create the new function with the aforementioned function wizard, and it just automatically adds it to the related language configuration object of the related function. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:48, 24 April 2026 (UTC) :# Sounds good to me. :# A sandbox available is [[Z10119]], though an extension-provided sandbox that allows you to manipulate the types, code, and tests easily without interfering with the mainspace would be nice. :# [[WF:Suggest a function|This page]] works to some extent, though it's too messy in my opinion. :# We used to have a "beta cluster" but it [[phab:rOMWC5f625c5846b5f779473fa32c9a02d87e59215dfa|got shut down]] just over a year ago because it was broken. :[[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:07, 24 April 2026 (UTC) == Language parameters in language-specific functions == I think that an effort should be made to give the different natural language options corresponding to different English dialects, Chinese scripts, etc. more of a use (I added the test {{Z|Z34119}} to {{Z|Z26095}} and unsurprisingly it fails). There are two main problems with this approach that I can identify: * If you ask the majority of these functions to make a sentence in British English, much of the time it will give you an output with missing words, because it does not fallback to English labels in the case of a British English label for that item missing. The same applies for every other English dialect, British English is just an example here. * Uninformed editors will probably see the presence of a language parameter on these functions, consider it redundant, and remove it. [[Special:Diff/268074|I have made this mistake before]]. In my opinion, in a perfect world, all of these language generation functions would output monolingual text, and if the user asks for American English text, then American English text is what they'll get. If the user asks for Japanese text in hiragana specifically, then that's what they'll get in return. This is not as high-priority as just rendering text in the language plainly in the first place, but it's something that I feel is still worth devoting some effort to. Right now switching functions to use this paradigm is difficult because, on the one hand, I don't know if consensus tends towards this direction being ideal or advisable, and I don't want to make changes like this without at least notifying the wider community. In addition, all tests break once a parameter is added or removed, and the function editor does not recognize the change in number of parameters and therefore you have to remove the function call, re-add it along with all of its parameters it had previously (which is a tedious cut-and-paste job), and then it will work again. This is something that you can do in five seconds by just adding a few lines of JSON to the test source, but this is not directly editable from the Web browser. This tedium is largely what's preventing me from doing this on a larger scale, besides asking for comments first. If anyone has any insights or comments on this, then that would be appreciated. If a reference of functions with and without the support for language variants is needed, of course [[WF:NLG]] can be perused, but I've also my own list cataloged at [[User:Theki/functions#language]]... Of course, this thread has many similarities to [[#"language" argument for certain functions|the one above]], but this concerns me going out and making this consistent across these NLG functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:09, 24 April 2026 (UTC) :I've created {{Z|Z34122}} as an extension to {{Z|Z34039}} for larger functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:34, 24 April 2026 (UTC) :Just to confirm that I, for one, support a Natural language parameter for all natural-language functions. The concern about getting them all aligned is just that we haven’t finally settled on {{Z|Z11}} being preferred to {{Z|Z89}} or some other type that conserves the text’s provenance, so we risk having to change them all again. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:07, 25 April 2026 (UTC) == “Key not found ()”? == What am I doing wrong in {{Z|Z34137}}? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 00:39, 25 April 2026 (UTC) :You were passing a [[Z6091]] to {{Z|32290}}, but it takes a [[Z6001]]. Fixed. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:10, 26 April 2026 (UTC) ::{{done|Thank you}}! [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 14:13, 26 April 2026 (UTC) == Why is my test failing? == Hello! I recently made {{Z|Z34139}} based on [[wikt:Module:bg-translit]], and the test case {{Z|Z34141}} is failing on both implementations, despite the expected output and actual output being the same as far as I can tell. I tried looking at the Unicode codepoints of the output, but those are also identical. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 06:21, 25 April 2026 (UTC) :Yes, it’s a tricky one. I’ve added a normalize step to the result validation in {{Z|Z34141}}, which confirms it is a normalization issue. It looks like it is in the code but I don’t know whether simply normalizing the result is the way to go. Logically, you would normalize both the input and the result. The implementations of {{Z|Z10384}} show you how to do this. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:41, 25 April 2026 (UTC) == Edit request == Hello! I have an edit request for {{Z|Z23752}} and {{Z|Z23414}}. Please replace all the "an/a" logic with <code>Z21739(Argument reference)</code>, both for readability and for more accuracy ("a university is an institution") <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:50, 25 April 2026 (UTC) :{{D}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:24, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #245 is out: The Foundation's search for the perfect language == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-25|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present an academic paper about Abstract Wikipedia, we discuss our latest Type created, and we take a look at the newest created functions. 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:54, 25 April 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=30325620 --> :@[[User:Sannita (WMF)|Sannita (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], technical meta-question: the newsletter quotes the article: ::the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016) :This quotation sounds sensible, but the article's [https://link.springer.com/article/10.1007/s00146-026-02899-w web version], and the PDF that is downloadable from the same page doesn't actually show the emojis. It rather shows text that looks lacking: ::the only way to contest its algorithm is to click or (Crawford and Gillespie [https://link.springer.com/article/10.1007/s00146-026-02899-w#ref-CR14 2016]) :Where did you get the emojis? Is it your (probably correct) guess or is there a version somewhere that actually shows the emojis? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:16, 25 April 2026 (UTC) ::Scratch that. I've found a version with correct emojis: https://wikihistories.github.io/wikilambda-the-ultimate/ [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:37, 25 April 2026 (UTC) == Requested deletion of test == Please delete {{Z|Z34143}}. this was never valid Bulgarian, I messed up. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:19, 25 April 2026 (UTC) :[[WF:RFD]] please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:40, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|talk]]) 00:57, 26 April 2026 (UTC) </bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == Is it OK to connect the implementation? == Hello! I recently applied for functioneer on [[WF:RFG]], and I was wondering whether I could connect the implementation for {{Z|Z34165}} despite its dependency {{Z|Z34149}} being currently unimplemented. That is <em>if</em> I get accepted. I am planning on implementing it based on [[wikt:module:bg-nominal]], but am still having trouble figuring it out for now. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:04, 26 April 2026 (UTC) == Past tense function == Is there a function like {{Z|Z26039}}, but for the past tense (e.g. "Leo Tolstoy <em>was</em> a writer.")? If not, I will create it myself, I just want to make sure there's not a duplicate. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:10, 26 April 2026 (UTC) : {{Done}} with {{Z|Z34224}}, but I have a few kinks to work out with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:35, 26 April 2026 (UTC) :: I need to create some other similar functions for the past tense, I have some ideas: ::* {{Z|Z26095}} ::* {{Z|Z32643}} ::* {{Z|Z28016}} ::* {{Z|Z26570}} ::* {{Z|Z33975}} ::* {{Z|Z27243}} ::* <ins>{{Z|Z26627}}</ins> ::* <ins>{{Z|Z27627}}</ins> ::* <ins>{{Z|Z27173}}</ins> ::* <ins>{{Z|Z29591}}</ins> :: :: Are there any I have missed? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:57, 26 April 2026 (UTC) :I think that here we are starting to walk on dangerous waters: what does past mean? Is it a recent o a far past? Does it have ripercussions on the present or not? Is it just a thing that happened once, many times or for a continuative period of time? :Consider that various languages distinguish between many different types of past. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:38, 26 April 2026 (UTC) :: {{re|Dv103}} That is a fair point... :: How do we go about solving this problem though? I don't think having every sentence on Abstract Wikipedia be "X is a Y" is a very good idea. :: Maybe we have different functions for all these variations of past you mentioned that just map into "X was a Y." in English? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 13:31, 26 April 2026 (UTC) :::To properly solve this problem, we should use a more complete abstract content representation model, like for example the proposal of [[Wikifunctions:Type proposals/Semantic unit|Semantic units]] (look at [[Wikifunctions:Type proposals/Semantic unit/Douglas Adams|the example]] to see how times could be handled). For now, since we're still stuck with single fragment generation functions (that I hope will be slowly replaced with the complete represenation model, when available), we could just restrict your function to a very specific meaning, like "subject was an instance of, for most of its existence" (which means for example that it could be used to say "Douglas Adams was a writer", but not "Abraham Lincoln was a president", since he only was a president for 4 years). Probably my definition is still too vague, and this is why we need to go beyond these fragment generating functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:47, 26 April 2026 (UTC) ::Nitpick... I don't like that it outputs a string instead of monolingual text. With {{Z|Z26039}} it's used so much that I think it's unfixable in that case beyond deprecating it if people care that much, but {{Z|Z34224}} doesn't even have any connected implementations yet. Consider it, maybe? ::Nitpick 2... {{Z|Z34227}} is missing a language parameter. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:08, 26 April 2026 (UTC) ::: I will consider that! ::: I just did that because that's what {{Z|Z26039}} does, so I assumed I should follow suit with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 26 April 2026 (UTC) == Legacy functions == If and when more robust methods of abstractly representing and generating linguistic content come around, and more efficient ways of creating abstract content are devised and implemented, I suspect that our current methods will require some form of deprecation. This is a significant source of concern for me in relation to WF and AW, questioning how prone our current methods of doing things are and eventually will be prone to obsolescence, and how it will be worked around when it comes. We have over 1 250 articles on AW presently, and these are rather all over the place. I suspect the maintenance burden from keeping these articles up to code will eventually, err, creep up on us, I suppose, and some kind of major refactoring will be necessary. We are definitely in a period of experimentation and whatnot right now but eventually, like with enwiki, some sort of structure and rigor will form and I suspect it will start to become rather boring for me... I, for one, very much enjoy experimenting with new and better ways to do things here. I don't personally mind changing things to use a new and better paradigm if need be, that sort of thing highly excites me, but of course there will be things that are left behind, and I suspect maybe bots will be employed to deal with this? A lot of Wikipedia sister sites seem to do that, e.g. going and fixing up use of deprecated templates. Considering the nature of Wikifunctions and Abstract Wikipedia I suspect certain maintenance tasks will be made simpler or even trivial by the typical uniformity of our implementations. I guess I am just concerned if Wikifunctions or Abstract Wikipedia will ever accrue its own kind of "technical debt" with how we are plowing through things presently, and if there is a plan for how we will eventually seek to mitigate that. Maybe too early to ask this question, but I am a notoriously anxious person, so I thought it wouldn't hurt to raise the question regardless... &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:30, 26 April 2026 (UTC) :I very much agree, thank you for expressing my position so well. {{ping|Immanuelle}} has been using an AI-generated tool (well, they haven't edited in a week, perhaps it's a break or perhaps they don't wish to contribute to the project any more) to create a bunch of articles en masse, which I have warned them multiple times is a bad idea (on top of evolving functions, all of the articles are one-sentence-per-paragraph, [[abstract:Q12184|like so]]). That's why I've been avoiding creating articles recently, I'd say I have a good fourth (no data to support, rough guess) of the comments on the wiki, yet less than a percentage of the article count (only three, including the [[abstract:Q319|first article]], though, so perhaps I'm the next [[w:Special:Permalink/908493298|office.bomis.com]]). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:41, 27 April 2026 (UTC) :: I feel that the overwhelming presence of these low-quality articles (which I admit I myself am [[abstract:Q1710970|guilty]]/[[abstract:Q7601858|of]]/[[abstract:Q39338|creating]], usually as testbeds) may incur a large maintenance burden. I do expect them to be easy to detect, however, as searching for the presence of "deprecated" NLG functions is trivial, and it is possible that replacing them with their future ''even abstracter&trade;'' counterparts could be done automatically since they all have the same signatures and can be expected to create the same form of sentence. If it needs to be done manually for a while or for certain delinquent instances, my hope is that it will be fun, at least for a while. :: I just hope that these hypothetical future waves of "this new and versatile way of abstractly representing linguistic content" obsoleting previous methods and requiring refactoring across all articles is only a one-time thing. We should strive to be as robust and flexible as possible from the outset as each brand new paradigm of abstraction is also a brand new maintenance burden for updating old articles. At the end of the day, at least ''some'' of these articles will still render to many different languages even if their methods of creating those sentences of theirs is completely outdated. Ergo, the time it takes for the switchover to be performed across our articles should not be a persistent inconvenience for users (as, of course, they will always still be able to read the content as it was before since these legacy functions aren't being deleted outright), and the increased availability that the new methods will bring about will likely act as motivation for them to join the effort in refactoring (&#x300C;You're telling me that if I rewrite this article in this cool Lisp-looking stuff then I can probably read it in [[abstract:Q9307|Galician]]?? COOL!&#x300D;). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 20:26, 27 April 2026 (UTC) :::Totally agree. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:54, 28 April 2026 (UTC) :::My vague plan is to implement a default function returning an {{Z|Z89}}, for each language-neutral function. A single function would convert any of these to a {{Z|Z11}}, so that a composition of the two can be implemented as the current default until such time as the language-neutral function is ready to return a [[Z89]]. We can already convert a [[Z11]] to a [[Z89]] so, although there is more to be done in this space, existing language-specific functions could be adapted to return a [[Z89]] quite mechanistically. :::Although we certainly could deliver parallel Z89 functions for each existing Z11 function, I don’t think we should assume that particular outcome. Provided the Z89 captures a lang attribute from the Z11’s language tag, the two representations should be largely interchangeable, although I am expecting a Z89 to carry additional attributes at the span level that would be lost on conversion to a Z11 (along with any higher-level tags and attributes). :::When I say there is “more to be done in this space”, I am referring to a new type that would allow HTML fragments to be represented as tractable Wikifunctions objects, but this is currently drafted only in my head! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:21, 29 April 2026 (UTC) == Filtering types of objects == Hello! I have tried to comb through my own edit history several times, but it's really hard to search for specifics because there's no differentiation between different types of objects (functions, implementations, tests, etc.) in the logs as far as I can tell. Am I missing anything? I want it to work sort of like how filtering by namespace works. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 27 April 2026 (UTC) :There is differentiation, it's just rather hard to look through. Since all ZObjects are just JSON data at their core, you can search for instances of <code>{ "Z1K1": "Z[type]"</code>. I haven't tried this so I'm not sure how well it would work and I know MediaWiki search syntax treats quotation marks as a special character, but I have seen Wikifunctions pages link to searches using this before. There is also [[Special:ListObjectsByType]] but it is sitewide rather than specific to your edit history in particular. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:59, 27 April 2026 (UTC) ::''[It doesn’t help directly here, but please see [[WF:Find]] for more details of how this works.]'' [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:24, 29 April 2026 (UTC) :See the feature requests [[phab:T399244]]/[[phab:T373735]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 06:06, 28 April 2026 (UTC) :The lack of filtering edits by namespace is exactly the problem that I was trying to solve with the [[User:Amire80/wikifunctionsanalytics]] tool. :I even kind of succeeded, but it has two major problems: :# It doesn't have any real frontend, so you have to know some SQL to use it (or ask other people who know SQL). :# It doesn't get information from the live site, but from the dump, which appears to be updated once a month. :I've made a [https://quarry.wmcloud.org/query/104794 sample query for you]. Unfortunately, it won't do anything at the moment because of the second problem—your edits started in April 2026, which isn't over yet, so the dump for it hasn't been processed. But I hope that early in May you'll be able to use the same query and see something useful. :(I plan to add support for recent edits, but I haven't done it yet. Now that I more or less figured out how to process Wikifunctions edits, I'm focused on trying to understand Abstract Wikipedia edits. Processing up-to-date edits from both sites will possibly be the next thing I work on, but if you know some Python and want to try doing it yourself, don't wait for me—[https://gitlab.wikimedia.org/toolforge-repos/wikifunctions-analytics Patches welcome].) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:51, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]], I've just updated the data until the end of April. Now the query to which I linked above gives some results. You can also try running other queries if you know SQL. (Or try asking for other queries if you don't.) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:26, 3 May 2026 (UTC) == [[Z34213]] == I'm not quite sure why this implementation is failing. Could someone take a look? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:24, 28 April 2026 (UTC) :I've [https://phabricator.wikimedia.org/T419933#11863997 notified] the team that this is still occurring, the issue was marked as resolved. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:52, 28 April 2026 (UTC) :Some useful tips: :* create more testcases: sometimes it is a random error, so try to see how consistent it is between testcases :* your implementation is very inefficient, since it fetches items and lexemes a lot of times. Ideally, each item and each lexeme should be only fetched once in all the execution tree. :[[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 06:06, 28 April 2026 (UTC) ::Caching (''should?'') means that the lexeme and item data are cached, so the call doesn't actually execute multiple times. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:51, 28 April 2026 (UTC) :::Are lexemes and items actually cached within the same function execution? Even if they are only partially fetched and/or fetched in bulk? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 17:54, 28 April 2026 (UTC) ::::I don't have any evidence to prove that it works but that's definitely A. what's supposed to happen and B. the ideal behavior. This happens because the Z680X functions can be cached just like any other. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 28 April 2026 (UTC) ::::It is unclear. In general, I believe identical branches are resolved only once in orchestration, but there is also independent caching of Wikidata fetches. ::::According to @[[User:DMartin (WMF)|DMartin (WMF)]] ([https://t.me/Wikifunctions/30374 on Telegram]): ::::<blockquote>Well, no. We have caching of Wikidata entities that have been retrieved, but not of the results of nested function calls. There is a proposal for doing this in the context of the V2 composition language, when it's a bit more mature, and it's regarded as a relatively high priority.</blockquote> ::::It’s hard to tell whether fetches in nested calls are, in fact, cached and available for other nested calls in the same call, since it is not generally the actual fetch that consumes the most resources. Rather (I believe), it is construction and transmission of the result object, which is currently repeated afresh in each nested call (unless it is in an identical branch). ::::I hope that’s clear, and I apologise in advance if it happens to be inaccurate! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 29 April 2026 (UTC) :::::Oh, I should clarify.  There is a lot of caching going on, in several different places.  Lexemes and items ''are'' cached by the orchestrator within the same function execution, even if they are only partially fetched and/or fetched in bulk.  When I said that we don't have caching of the results of nested function calls, I meant that's not happening in general, for all nested function calls in compositions.  But fetching of Wikidata entities gets special treatment, so yes, fetched content from Wikidata is cached, regardless if it was fetched by a top-level call or a nested call. :::::It is also true that the construction of a ZObject from the fetched JSON might happen more than once within the same function execution, depending on how a composition has been structured. However, the construction of the ZObject is actually very fast, compared to the elapsed time of getting the JSON from Wikidata. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 18:04, 1 May 2026 (UTC) == Question about cardinal numbers == I was about to edit {{Z|Z16435}} to add my function {{Z|Z34308}}, but I noticed that none of the other functions have a gender parameter. Should I create a new wrapper function "Bulgarian cardinal, neuter", or should I just remove the gender parameter and always return neuter? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:39, 28 April 2026 (UTC) :The “cardinal” functions should return the words used for “counting” numbers in the abstract. :We should consider converting them to return a {{Z|Z11}} rather than a {{Z|Z6}}. It may even be appropriate to return a {{Z|Z12}} to cater for language variants. Either way, I think that would be the approach to adopt for inflected forms, unless reference to specific lexeme-forms is required. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:52, 28 April 2026 (UTC) ::This. If a native of your language were to count up, which form would they be most likely to use? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:29, 28 April 2026 (UTC) ::: {{re|GrounderUK|Feeglgeef}} Thanks for both your input! ::: I relabeled the aforementioned function to {{Z|Z34308}}, and created a new wrapper function {{Z|Z34457}}. ::: Should I specify that my old function is a monolingual text in parentheses? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:26, 28 April 2026 (UTC) ::::You don't have to, unless you think that is something that would require distinction when viewing the function in a list of search results &c. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:36, 28 April 2026 (UTC) == Optional/nullable function parameters == Hello! Recently, I was informed that Wikifunctions has no optional/nullable function parameters as of now. Are there any future plans to support this, and/or workarounds? Maybe create a union type system like "{{Z|6}} or {{Z|23}}". <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 17:53, 28 April 2026 (UTC) :What I do for this is use an "is empty" function corresponding to the type of the parameter in an If statement. If it isn't empty, the function works as intended. Otherwise, it does something else. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:58, 28 April 2026 (UTC) :Unions are not a thing (yet) on Wikifunctions, but you can always define an argument of type {{Z|Z1}}, which means that all types are allowed (I already did this for {{Z|Z26737}}; note that it is still a ugly workaround, don't use it for high level functions). Also, note that usually on Wikifunctions we use {{Z|Z24}} as the null value. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:00, 28 April 2026 (UTC) :: {{re|JJPMaster|Dv103}} Thanks for your help! :: @[[User:Dv103|Dv103]] told me a function call with a missing parameter is treated as an invalid function call, so how does the "is empty" function work with that? :: Also, setting the type to {{Z|1}} seems naive, like setting the type as <code>any</code> in TypeScript... :: Related question: Are there plans to add default values to parameters (outside of "if empty")? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 18:19, 28 April 2026 (UTC) :::Setting the type to {{Z|Z1}} is actually naive, and that's why I advised you to only use it for low-level functions. Currently there is nothing better. Sometimes, type correctness is not actually checked, so it might seem that nullable types are possible. But it is still an hack, and it could broke anytime since it is not intended behavior. :::I don't think that there are current plans to add default values (but correct me if I'm wrong). The closest thing that comes to my mind is that, if you incorporate Wikifunctions into Wikitext, you can leave empty some fields (only of some specific types) and Parsoid will replace them to their default value. This is done only depending on the type, and not on the functions. For example, {{Z|Z6091}} and {{Z|Z6001}} are assigned the QID associated to the page, and {{Z|Z20420}} is assigned the current date. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:56, 28 April 2026 (UTC) :::@[[User:QuickQuokka|QuickQuokka]]: At the very least, [[Z10008]] accepts a null input. Maybe that feature is unique to the String type—I am not sure. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 19:10, 28 April 2026 (UTC) ::::I think it's just not checked, but it shouldn't be intended. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:20, 28 April 2026 (UTC) ::::Strings and typed lists can be “empty” in the sense that their length can be zero. Typed pairs may also be “empty” in a degenerate sense, but such an object will not be returned from a code implementation. A typed map with no entries will also fail to be returned from code, although it is fine in compositions. ::::For a genuinely optional parameter, I prefer a properly typed list, which at least encourages an argument of the correct type. {{Z|Z813}} is also typically faster than {{Z|Z10008}}. Quite a good example of this approach is {{Z|Z23723}}, where it helps to resolve the type union (using [[Z1]]) for both Z6003K1 and Z6003K3. Of course, there’s nothing to prevent more than one element in the list, but additional elements are easily ignored. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:55, 28 April 2026 (UTC) :Pinging {{ping|Jdforrester (WMF)|prefix=|p=}}, I believe there are no current plans. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:02, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]]: I'm afraid there are no current plans to build out optional params, indeed; we would be happy to review this if a compelling case was made, but it'd be a lot of work to re-build the [[Wikifunctions:Function model|function model]] with that support and ensure we don't break (too many) things. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:11, 28 April 2026 (UTC) == Z6830 for Chinese == I was trying to use {{Z|Z6830}} for implementation in the Chinese-language. And turns out most of the Lexeme on Wikidata is using [[d:Q727694]] as the language instead of [[d:Q7850]]. This makes it impossible to use the mentioned function above, since Standard Chinese is not available (or did I miss something?). Is there a way to fetch lexemes with language=[[d:Q727694]] from item? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:20, 30 April 2026 (UTC) :@[[User:Sun8908|Sun8908]] There is [[Z1006]] for Chinese and it has the language code zh. There is an overview of languages in [[Module:Wikifunctions label]] so you can search there for chinese versions and choose the one you need. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 5 May 2026 (UTC) ::I know that. The problem is when using the function [[Z6830]], it cannot retrieve lexeme with language [[d:Q727694]] (but it is the "Chinese language" with the most current Wikidata lexemes, see [https://ordia.toolforge.org/language/ ordia]). I think it should be a Wikidata problem, I might fix it (possibly by creating the same lexemes with language code zh) on Wikidata. Thanks anyway. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 05:39, 6 May 2026 (UTC) :Could you provide an example of a Chinese lexeme that has a linked Wikidata item, or a Z6830 function call that fails to find such a lexeme where one exists? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 07:55, 6 May 2026 (UTC) ::Here: [[d:Lexeme:L846083]]. I think that's a primary reason of me trying to look into this problem, as the label in zh for [[d:Q6256]] (country) is not a single phrase (see its talk page on WD for more information). This makes some Abstract Wikipedia articles very weird in Chinese when {{Z|Z26570}} is used, so lexeme could potentially fix that. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 10:33, 6 May 2026 (UTC) :::Thank you. It looks as though {{Z|Z6830}} [https://www.wikifunctions.org/view/en/Z6830?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z6830%22%2C%22Z6830K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q6256%22%7D%2C%22Z6830K2%22%3A%7B%22Z1K1%22%3A%22Z6092%22%2C%22Z6092K1%22%3A%22P5137%22%7D%2C%22Z6830K3%22%3A%7B%22Z1K1%22%3A%22Z60%22%2C%22Z60K1%22%3A%22cmn%22%2C%22Z60K2%22%3A%5B%22Z6%22%5D%7D%7D returns that lexeme for language tag "cmn"]. Perhaps that tag should be added into the helpers for {{Z|Z24144}}? If it is widely used for lexemes, perhaps it should have its own {{Z|Z60}}? In any event, improvements might be considered under [[:phab:T390563]] (or otherwise), including amending [[Z6830]] to also consider "cmn" (and "zho", "chi"…?) when requests are made for "zh-hans" or "zho-hant" (or others?) @[[User:Winston Sung|Winston Sung]] @[[User:DMartin (WMF)|DMartin (WMF)]] [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:22, 6 May 2026 (UTC) ::::If you go to [[d:Special:NewLexeme]] and put in [[d:Q727694]] as the language, it is going to tell you it has an unrecognized language code. So I believe "cmn" should not be a {{Z|Z60}} by default? I also started [[d:Wikidata:Project_chat#Lexemes_with_language_Standard_Chinese_(Q727694)|a discussion on WD]] regarding this. I guess we can still use it as a fallback language though if possible. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 03:43, 7 May 2026 (UTC) ::::We don't have a separated <code>cmn</code> BCP 47 language subtag in MediaWiki and Wikidata at the moment. <code>zho</code> and <code>chi</code> are ISO 639 language codes but not BCP 47 language subtags. ::::For Modern Standard Mandarin, please use <code>zh-*</code> language tags for now. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 15:26, 8 May 2026 (UTC) == Key not found error == Is there a reason why I am getting key not found error for this [[Z34677|function]] {{Z|Z34677}}? All the underlying functions run and all the test cases work. The debug information does not give more details. Any pointers? Thanks in advance [[User:Jsamwrites|John Samuel]] 19:24, 1 May 2026 (UTC) :It was passing the [[Z6091]] to {{Z|34641}} when that takes a [[Z6001]]. I've fixed that, but there's some other problem with the logic, so I've left it disconnected. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 19:42, 1 May 2026 (UTC) ::@[[User:YoshiRulz|YoshiRulz]] Thanks a lot. [[User:Jsamwrites|John Samuel]] 20:21, 1 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, 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:21, 2 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=30325620 --> == Any formal process for deletion of pages == Does a formal process exist for the deletion of functions, implementations, and tests that includes a notification system for creators, analogous to Wikidata’s process, explaining the rationale behind the deletion (or proposal for deletion)? [[User:Jsamwrites|John Samuel]] 12:36, 3 May 2026 (UTC) :Does [[Wikifunctions:Requests for deletions]] work? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:00, 3 May 2026 (UTC) :Please see the discussion at [[Wikifunctions talk:Requests for deletions#Should we expect Objects' creators to get pinged on deletion proposals?]]. :As I see it, it is the proposer’s responsibility to consult appropriately before making a request and we expect our administrators to act only when satisfied that appropriate consultation has occurred. In many cases, no consultation is required. Administrators may delete their own contributions without making a request, but this is not a practice I would encourage. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:51, 3 May 2026 (UTC) == Implementation of rational number in JS doesn't match in Z19677 (Rational number) and Z28579 (RGBA colour) == In {{Z|19677}} it's <syntaxhighlight lang=js> { "K1": sign * numerator, "K2": denominator } </syntaxhighlight> but in {{Z|28579}} it's <syntaxhighlight lang=js> [ sign * numerator, denominator ] </syntaxhighlight> '''<span style="font-family:Iosevka,monospace">[[User:沈澄心|<span style="color:#9f3526">dring</span>]][[User talk:沈澄心|<span style="color:#534fa3">sim</span>]]</span>''' 05:15, 4 May 2026 (UTC) == Nested functions in compositions == I wish it will be easier to a add another function about a specific existing function in a function implementation based on a composition. When I write long functions in spreadsheets I usually stat with a small part and then I try to go further and after important steps I test if the output is as expected. I created [[Z34826]] to get the German gender specific occupation lexeme for a specific person based on their gender. I wanted to add a function around the existing one and it was not successful. It is not very easy to implement as it requires the possibily to move a part to another section but I think it can be helpful if it will be implemented. So far I spend more time as expected on the function. Describing it with words what the function needs to do is much easier than implementing it here in Wikifunctions. So I think there needs to be improvement to make Wikifunctions more accessible. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:10, 5 May 2026 (UTC) :Have you tried to use the copy-paste functionality? It is very useful to move parts of composition arounn. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 07:12, 6 May 2026 (UTC) :I've also found the composition editor to be wholly unsuitable for any expressions more than a few levels deep. (Even with the <code>localStorage</code> clipboard, because of its overzealous type checks.) Compositions naturally grow out from the "leaves", the immediate operations on the inputs, while the interface really wants you to build from the "root". I mostly use the [https://yoshirulz.gitlab.io/WikiLambdaBlockly drag-and-drop block editor] which I made to smooth over some of the site's problems, so if you want to try that out and give me some feedback I'd appreciate it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 14:36, 6 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the 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 [[: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/1778520600 May 11, 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]]) 11:16, 8 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=30325620 --> == RGBA colour, spelling... == Something that has always irked me a little bit is the spelling of [[Z28579|RGBA colour (Z28579)]]. I guess this is not unsurprising for me considering my use of US English but I think there is more to it than preference and I want to try to argue for it being changed to use American spelling. I know that this probably has a snowball's chance in hell of actually garnering any support, so I won't really be miffed if the spelling remains as it is, but I thought it wouldn't hurt to raise this regardless. The main issue I have with it is the spelling of the original proposal. When infernostars raised the [[Wikifunctions:Type proposals/RGBA color|type proposal]], the spelling was 「RGBA color」. Of the comments that mentioned the word 「colo[u]r」, two used British spelling while six used the American spelling as used in the proposal. The only thing that really pointed to the use of ''colour'' was the fact that the catalog page on color functions used that spelling already. For all intents and purposes, the spelling of the original proposal should have been maintained, but it was not; [[User:DVrandecic (WMF)|DVrandecic]], the eventual creator of the type, used a different spelling. It should be noted that there was really no reason for this to occur and while it is an undoubtedly minor issue I still believe it should be rolled back and the type should use the spelling of the original proposal and majority of editor comments. In [[abstract:Q936|OpenStreetMap]], there have been keyvalue proposals that have had the finalized spelling that gets put to use be in British English despite the original proposal being in American English; this has usually occurred with proposals relating to 「X center/centre」 tags. This makes sense on the surface, because OpenStreetMap is maintained by a UK organization, and still has close ties to Europe. The Wikimedia Foundation, however, is an ''American'' company. This is often brought up as a fallible argument when debating article spelling on the English Wikipedia, and I don't bring it up to support that 「RGBA color」 should be used for that exact reason, but rather to state that OpenStreetMap's general policy on tag names need not apply here. It appears to me that, at least initially, the majority of 「core contributors」 to Wikifunctions used British English; I can name YoshiRulz, 99of9, GrounderUK, and VIGNERON.<ref group="color">I'm avoiding linking to these folks because I don't think pinging them about this discussion is all too necessary unless they themselves want to be involved; I don't want to clutter their inboxes just to briefly mention them. I pinged Denny because, well, I'm asking him a question directly, but everyone else I would prefer to join this discussion by their own accord... not that I wish for this decision to be confused as me going 「these people use British English so they will probably oppose my idea, I won't invite them to the discussion because of that」...no, I promise you that is not the reason.</ref> I see (or saw) these people ''everywhere'', so it makes sense that British English has prevailed in some sorts on this website, but I don't think that indicates that it should be the ''preferred'' spelling across the website, at least not to the point where a proposal should have its name changed to match such a "consensus".<ref group="color">It could be argued that the front-and-center ''Function catalogue'' using 「catalogue」 is actually indicative of such a "consensus", but ''catalogue'' is in a similar position to the word ''grey'' where I live (that is, the US) in that it is used just as often as its American counterpart. Also, consider Wiktionary's ''Beer parlour'' project chat.</ref> The unnecessary modification of the original spelling is my main argument for changing it back... but of course, I must obligatorily state that on English Wikipedia, it is [[w:Color|Color]] and [[w:RGBA color model|RGBA color model]]; on Wikidata, it is [[d:Q1075|color]] and [[d:Q2325624|RGBA color space]]; in CSS (which typically uses hexadecimal triplets to specify RGBA values), the properties are <code>color</code>, <code>background-color</code>, etc.; bit of a weak jab, but on Schema.org it is [https://schema.org/color color], [https://schema.org/colorSwatch colorSwatch]; et cetera. {{Z|Z28580}} uses ''color'', so does {{Z|Z28591}} and its Python counterpart. Mr. Vrandečić, I have to ask, I'm rather confused... you created the color type using British English spelling, but you were also responsible for the creation of the equality function which uses the American English spelling. You also seem to be writing in American English for the status updates, judging by your use of -''ize'' over -''ise'' endings and use of ''program'' over ''programme'' in [[Wikifunctions:Status updates/2026-04-16]]. Is there something I'm missing or have you switched your preferred variant somewhere along the way? Anyways, do consider this if you wish... again, I don't suppose this will garner much support, it is the ''non-issuest'' of ''non-issues'', but it has irked me to the point where I want to ask about it to get some answers, if nothing else. I am not arguing for every other color function to have its name changed, just the type itself. <references group="color"></references> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 8 May 2026 (UTC) :This is a multilingual project; the <code>en</code> label is <code>RGBA colour</code> and the <code>en-us</code> label is <code>RGBA color</code>. Though I'm not able to switch to <code>en-us</code> via the language picker so that would need to be fixed.<!-- --><br>edit after reading your whole comment: The same is true of {{Q|1075}}, there are labels specified for multiple English variants. (In {{Q|2325624}} it's only an alias.) I agree that other websites' choices aren't binding on us, but from that, I conclude that the more widespread British/Commonwealth spellings should be used for the generic <code>en</code>. As for myself, I'm Aussie and I will continue to use the BrE spellings ([[w:en:Oxford_spelling#Language_tag_comparison|+ "routing"]], TIL) if only by muscle memory.<!-- --><br>[[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 17:42, 8 May 2026 (UTC) :: Your lattermost point would normally be fine in a perfect world. Wikipedia's <code>convert</code> function defaults to "international" English, which I don't personally take issue with because it happens that we here in America are actually outliers for saying and spelling things differently... err, or we were for a while at least, nowadays it seems like an even split (plus you have "yield" vs. "give way" which is effectively the logical opposite of US's use of "meter" over "metre"). :: However, this is not a perfect world, and I don't think <code>en</code> should correspond to any particular variant. It is too fragmented across all software at this point to impose such a requirement. The inability to switch to <code>en-us</code> on this website foregoes an easy and simple solution to this problem that makes everyone happy, because the yanks (such as myself) can't be happy because we can't see the labels in American English even if we wanted to, and the other folk can't switch either as far as I'm aware (and the en-CA and en-GB languages in the preferences page seems to be deprecated). My point being, <code>en</code> is abused to mean "en-UK" just as often as it is abused to mean <code>en-US</code>; I think a decision shouldn't be made on such an assumption of one "default". &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:48, 12 May 2026 (UTC) :Hi @[[User:Theki|rae]]! I have no opinion nor preference on this, and given my background, I am just entirely confused about my spelling preferences myself, as you can tell from my inconsistent usage. I learned British English in school and used that for maybe two decades or so, but moved to the US and lived there for more than a decade, enough to be naturalized, but now I am back in Europe and I am technically a professor at King's College London, soooo.... honestly, I do not know. I don't remember having put too much thought into it at the moment I created it. The good thing is that in Wikifunctions, just as in Wikidata, it is easy to change, without messing things up too much (unlike in Wikipedia), so my suggestion is, just make the change, see if anyone complains, and if they do, discuss it more. I don't know if there is a guideline already in Wikifunctions about the variants. I am happy either way, and honestly, I keep forgetting which variant is which most of the time. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 18:16, 10 May 2026 (UTC) :: I can definitely understand this, although I am unfortunately rather passionate about any minutiae involving preferential minor differences in ''anything'', of which AmE vs. BrE chiefly is. So I dedicate a lot of headspace to it. More than I should. Not that I wish to imply that the comment above that I have wrote is of an irrational nature, or done out of spite or pure emotion and subjectivity; I do genuinely believe that ''RGBA color'' is beyond just a personal preference and is just logical. I may boldly go and change it, but for some reason I was expecting that changing the English label of a Type would require elevated permissions, and I also didn't want to do it only to get immediately reverted because it ''did'' strike a chord with someone, when I could instead see how apathetic, supportive, or in opposition interested people are beforehand and ''then'' act accordingly. I was not meaning to antagonize you over your spelling habits, I did actually use British English for a few years starting in 2020 before I went back to American English, so I'd be a hypocrite for me to decry you for not always sticking to some arbitrary standard of spelling words over the other. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:55, 12 May 2026 (UTC) :Although I spell it “colour”, I think it makes more sense to use “color” for the type, since that is almost always the required spelling when the string functions as a keyword. :More generally, though, Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en". This is unusual, in my experience, as "en" is widely misused in place of "en-US", where there are recorded spelling differences. :(I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere. Use of -ize rather than -ise is a matter of personal preference or house style, but regional autocorrect encourages -ise.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:00, 12 May 2026 (UTC) :: ''Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en"'' :: Definitely agreeing with you on the latter being a good choice. However, I suspect the favoring of "colour" over "color" may be because, in terms of language codes, when sorted alphabetically <code>en-us</code> actually comes ''after'' <code>en-gb</code>. Although, the frontend seems to be sorting <code>en-ca</code> after <code>en-gb</code>, so I don't actually know how correct that is. :: ''I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere'' :: The context of the spelling was "''No program for the NLG SIG meeting for next Tuesday has been proposed''". In that usage context, I think it makes sense to assume that ''program'' is not being used to refer to a computer program, but to a ''program of events'' or similar, something that you would spell as a ''programme'' in British English. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 12 May 2026 (UTC) :{{s}} this. I'm obviously biased but I believe American English is preferable generally, American dominance on the internet (our Department of Defen'''s'''e invented it!) and rapidly-increasing consumption of American media by international English speakers means that more people use American English's conventions, this is clear through for example [http://trends.google.com/explore?q=color%2Ccolour&date=all&geo=Worldwide search trends] (though they aren't particularly reliable). Perhaps this is a bit of a supremacist opinion, but we should have internal consistency, and if we must choose, American English should be our first choice (then Indian and then British English) [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:10, 12 May 2026 (UTC) :: This is rather flawed reasoning, though. I think probably any given British or Indian person would not agree on using that as the reasoning for this, not that you are necessarily ''completely wrong'', but if this is not a good enough reason for English Wikipedia's (admittedly extremely flawed) ''ENGVAR'' policy then I don't think it's likely it will pass here either. :: Although of note is that [https://books.google.com/ngrams/graph?content=color%2Ccolour&year_start=1800&year_end=2022&corpus=en&smoothing=3&case_insensitive=true Google ngrams] agree with you, but "color" vs. "colour" is an eternal holy war that will not be won by demonstrating that more books use US spelling over Commonwealth spelling. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:44, 12 May 2026 (UTC) :::You're probably right that it's not very sound. I'm biased in that other varieties of English irk me, and that's probably mutual for people who are used to other varieties of English when they read what I write! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:56, 12 May 2026 (UTC) :I've decided to boldly [[Special:Permalink/274271|make the change]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:02, 12 May 2026 (UTC) :: Thank you. Considering both you and GrounderUK seem to consider it an okay change, I think this will do for now. :: I should note that the matter of whether to move [[Wikifunctions:Catalogue/Colour functions]] in response to this (however this discussion will ultimately turn out) is a whole other can of worms, in my view. I can't say I have an opinion on that at the moment, but I'm putting it out there regardless. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:06, 12 May 2026 (UTC) :::Personally, I'm in favor of moving the page and renaming all of the items on it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:10, 12 May 2026 (UTC) ::I don't like this (exactly because of the American hegemony you cited), but again, it shouldn't matter because the software is meant to be multilingual. Clearly there's a bug preventing you from picking an English variant/dialect as your display language. But the search bar and Function/Type autocompletion do check the English variants for matches. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 15:15, 12 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[abstract:User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:31, 11 May 2026 (UTC) :Thank you for dedicating your time to writing this, it is very informative. I will try to add input once I'm not in over my head with finals. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:27, 12 May 2026 (UTC) == Display function for HTML fragment == Currently, any collapsed Z89 literal appears as<blockquote>&lt;&gt; [[Z89|HTML fragment]]</blockquote>If I were to create a new Function which returned something like<blockquote>&lt;&gt; 123-byte HTML fragment <q><nowiki><td><span lang=</nowiki>&hellip;</q></blockquote>could that be connected to replace the collapsed form, or would it require changes to the Wikilambda software? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 16:14, 11 May 2026 (UTC) :It might work, but I doubt it. Those angled brackets suggest that the collapsed form is not simply defaulting to the type’s label. Looking at [[:phab:T410509]], I’ve concluded that enhancements to the collapsed form were never considered, rather than being actively rejected. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:12, 12 May 2026 (UTC) ::[[:Phab:T391985]] documents the original design. Note the fifth bullet point under “Acceptance criteria”. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:21, 12 May 2026 (UTC) :I'm not sure the byte-size is necessary, but the outer tag (or first outer tag, though generally I'd prefer most fragments use a wrapper tag if it needs multiple like JSX does, but that's a whole different topic) would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:51, 12 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in 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]]) 14:36, 15 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 --> == [[Z34510]] == This function, which determines if a Wikidata item for a {{q|5}} has an undeprecated {{p|21}} statement of {{q|6581097}}, returns false for {{q|173399}}, a transgender man. This is because his item assigns his P21 statement to {{q|2449503}}, not {{q|6581097}}. I'm not sure how to account for this discrepancy. Should {{z|34510}}: # Include {{q|2449503}} as a value that can lead to a true result, # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a man?") could return true for either "male" or "trans man", # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a trans man?") could return true for "trans man", # Not exist at all? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:48, 16 May 2026 (UTC) :I can't think of a single use case where you would need to determine if a person is a cisgender man and nothing else. Functions are good for generalizing across multiple possibilities when they exist, so I think it would be best if trans men were considered a part of the criteria for returning a true value. If asking for specifically {{q|6581097}}s and ''nothing'' else was desired then the function name would be a misnomer as Elliot Page is inarguably a male (at least in the view of most reasonable and intelligent people). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:03, 16 May 2026 (UTC) :You made the function in the first place; what were you planning on using it for? AW? Maybe it should return a {{Z|25501}} which can then be passed on to other NLG functions. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 May 2026 (UTC) a0htehsfudpc4k3lw13255l4da7do1q 275558 275557 2026-05-16T20:02:44Z Aaron Liu 2395 /* Lexeme from wikidata label, or "best" lexeme from wikidata item */ new topic ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]]) 275558 wikitext text/x-wiki {{shortcut|[[WF:CHAT]]|[[WF:PC]]|[[WF:VP]]}} __NEWSECTIONLINK__ [[Category:Help]] <!-- please do not remove this line --> Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc. Other places to find help: * [[Wikifunctions:Administrators' noticeboard]] * [[Wikifunctions:Report a technical problem]] * [[Wikifunctions:FAQ]] {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |timeout=30 }} {{Archives|{{#tag:div|<br />{{Flatlist|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1|hideredirects=1}} |class=mw-collapsible-content|style=font-size:92%;}}|class="mw-collapsible mw-collapsible-toggle mw-collapsed"}} |prefix=WF:Project chat/Archive/ }} == "language" argument for certain functions == Hello. I am relatively new to Wikifunctions. Recently, I tried to create functions for Chinese translation of {{Z|Z26570}} and {{Z|Z26095}} (which became [[Z32788]] and [[Z32900]]). During the creation of these functions, I was trying to take {{Z|Z32212}} as reference. And I realized that the defining role sentence function is taking <code>language</code> as an argument (and the test case of the Chinese-language function already contains two varieties of Chinese). This makes it possible to output monolingual text in <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code>, or any varieties of the language. I think for this reason, it is better to have <code>language</code> as arguments for the implementation of Z26570 and Z26095, and potentially more functions that require {{Z|Z14294}}, since it would output the varieties code instead of just saying <code>zh</code> for <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code> in the output of type {{Z|Z11}}. I am not sure how the fallback mechanism works if one of the language (varieties) do not have a labels/lexemes, but to me, it is reasonable to have a <code>language</code> argument. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 09:38, 31 March 2026 (UTC) :The functions you mention do have a language argument. For Wikifunctions, the {{Z|Z60}} can be at a higher or lower level; whether a {{Z|Z11}} is for a language or a variant is determined by the function that constructs it. Please see {{Z|Z26565}} for an example and feel free to add test cases in Chinese. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:54, 11 April 2026 (UTC) ::Hello @[[User:GrounderUK|GrounderUK]], thanks for the answer. I understand that whether {{Z|Z11}} is for a language or a variant depends on the function. But that is exactly what I am asking for. It is true that [[Z26570]] and [[Z26095]] takes [[Z60]] as argument, but the language-specific functions in {{Z|Z29843}} and {{Z|Z26096}} don't. ::Let me give you an example: INPUT to [[Z26570]]: <code>entity</code>: Tokyo, <code>class</code>: city, <code>location</code>: Japan, <code>language</code>: zh-cn, the config would select [[Z33030]] (created after my previous comment by elseone) as the implementation, and it would RETURN 东京是日本的一个城市。(zh-hans), which is not zh-cn as requested in the INPUT. It would also be using the term not for the variant (when it is different) because it is hardcoded to use the term in zh-hans. However, if we have the implementation like [[Z32790]] (which was created by me but a natural language argument was added by elseone) or [[Z32213]] (that works in the defining role sentence function because of the extra argument), it could cater for different variant. ::If we don't have the language argument in the language-specific function, the desire for article creation on Abstract Wikipedia would be to create a function for every variant. Is it then better to create functions for every variant? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:18, 11 April 2026 (UTC) :::I forgot to mention that there are some hardcoding in {{Z|Z32790}} as well, but I cannot fix it because it is a connected function and I am not a functioneer. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:31, 11 April 2026 (UTC) ::::Okay, I think it’s safe to disconnect this one as the function is not yet configured for use on Abstract Wikipedia. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:04, 11 April 2026 (UTC) :::Ah, sorry… I misunderstood you. I agree that the called function should be able to accept the original language argument. That is simpler in theory than in practice, because the configured functions all have to have the same argument types, as I understand it. I’m not sure which the best approach is, really, but we probably want to avoid two levels of configuration. That suggests that all language-specific functions would need to accept the additional argument, which is unrewarding work for someone. @[[User:99of9|99of9]], @[[User:Jdforrester (WMF)|Jdforrester (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]] Any thoughts? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:57, 11 April 2026 (UTC) ::::I mean, we would need to modify all the functions in each language, which could take some time. But we are still in an early stage. If we don't fix it now and we want to fix it later, it would be a disaster. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 19:25, 11 April 2026 (UTC) :::::Agreed. And we probably want them converted to HTML too, with separate language spans for text in different languages. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:35, 11 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]: This sounds like a reasonable change to make. Note that (given these Functions are primarily for use on Abstract Wikipedia), altering/replacing them to return Z89/HTML fragments is already a desired but breaking change, so making a second breaking change at the same time is probably easiest for fixing things swiftly. That said, that's of course a decision for the Abstract Wikipedia and Wikifunctions communities, not me! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:43, 12 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]@[[User:Sun8908|Sun8908]] to make it a non-breaking change, I've created {{Z|Z34039}} which allows a composition {{Z|Z34043}}. This way you can make functions which either need the specified variant or don't! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:52, 24 April 2026 (UTC) :I have now created {{Z|Z33465}}, which is an implementation of [[Z26570]]. Maybe we can migrate to use that function when more (language-specific) functions for it are ready? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:19, 14 April 2026 (UTC) == No place to ask to activate a function? == I just discovered the {{Z|Z11390}} function and decided to make an overarching language-selecting function for it. After some fiddling around and studying how {{Z|Z32321}} and its set works, I now have {{Z|Z33439}} which has a config object ({{Z|Z33441}}) that selects between the two preexisting language-specific versions I found (English and Malayalam) and the new one I created for my other native language, {{Z|Z33440}}. Except I can't get these to work, because, from what I understand, only [[Wikifunctions:Functioneers|functioneers]] can activate newly created functions and implementations? So where do I apply for the {{Z|Z33439}} and {{Z|Z33440}} functions to be activated? Perhaps we should have a place to ask for it, a la [[w:WP:NPP]] — call it [[Project:New Functions Patrol|New Functions Patrol]] if you will. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] ([[User talk:UndueMarmot|talk]]) 08:58, 14 April 2026 (UTC) :There's [[Wikifunctions:Community portal]] for this. By the way, {{Z|Z33445}} doesn't work because all the code must be inside the main function in Python code. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 09:19, 14 April 2026 (UTC) ::Huh. How could I have missed that? ::But anyway, I've moved the code in {{Z|Z33445}} into inside the main function block. ::Is there any reason why WF decided not to simply allow anyone to write functions? After all, that's how it works with wikitext templates, and these functions are fundamentally serving the same purposes as templates, just written in a different way. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 11:25, 14 April 2026 (UTC) :::I've fixed a couple of technical issues, but tests still fail. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:28, 14 April 2026 (UTC) ::::The tests pass now after some more changes to the code: [[Special:Diff/265232/cur]]. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 12:01, 14 April 2026 (UTC) :::::{{D|Connected}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:02, 14 April 2026 (UTC) :::I think it's a security issue, since Wikifunctions implementations could teoretically be malicious. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:29, 14 April 2026 (UTC) ::::This ^^^. We're very lenient, though, once you've created a few working functions you can apply for the right, per [[WF:Functioneer]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:26, 14 April 2026 (UTC) ::::That explanation [[phab:T343559#11421293|doesn't add up]]. A reason to limit ''connection powers'' to Functioneers might be to prevent vandalism, considering Functions can be used across wikis. But user-provided code is already being executed even without a Functioneer connecting it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 April 2026 (UTC) == Actual difference between {{Z|Z26039}} and {{Z|Z26095}} == What is the actual difference between these two functions? I ask, since it seems to me that the current distinction is more or less that the first one doesn't use an indefinite article in English, while the second does. Which is not a good distinction in a project that should be language neutral. This doubt emerged from my use of the first one in [[abstract:Q124441]], which @[[User:Hogü-456|Hogü-456]] made me notice that is probably wrong. My question is: why is it wrong? How could we clarify the difference? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:46, 19 April 2026 (UTC) :I think the difference is if there is an indefinite article like a or an before the subject or not. In German there can be cases where a definite article is necessary before the subject. I looked at the functions and before the object both times an article is mentioned. As it depends on the language and the word what is the correct function to use I hope it will be clarified and it is an example of the necessity to have a human with understanding in a specific language check it. I hope there will be longer functions what generate more content about a specific kind of item. Then it is necessary to write one such function per language and it can be then applied to several items. It still requires checks and so maybe it is better to write down what item category needs what kind of introduction sentence function for what language. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:05, 19 April 2026 (UTC) ::The point of these two functions (and of the entire Abstract Wikipedia project) is that they should be defined in a purely language-independent way, so that the translation to actual language can be done automatically. This is the reason why these functions have been renamed; I think that this attempt was not succesful, since meaning is still unclear. My proposal to clarify them would be to invoke the concept of [[w:specificity (linguistics)|specificity]]: {{Z|Z26039}} should be named "specific subject is instance of (string)", and should be used only when the QID of the subject uniquely identifies a single thing; {{Z|Z26095}} should instead be renamed in "non-specific subject is kind of (Monolingual text)", and should be used when the QID refers to a multitude of real life items, and we are specifying the class that all these item belong to. This clarification would not still be enough, since it doesn't explain how mass nouns are handled (is water a unique thing? Does {{Q|Q7802}} refer to a single piece of bread or to the entirety of bread, like water?). This problem is very tricky, since mass noun are language-specific and blurry the line between these two functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 20:58, 19 April 2026 (UTC) :Simply put, one corresponds to P31 and the other to P279. Paris is an {{Q|P31}} a {{Q|Q1549591}} :whereas a {{Q|Q1549591}} is a {{Q|P279}} (alias “kind of”) {{Q|Q515}}. Whether the Wikidata knowledge representation will be sufficient to resolve into fluent natural language representations in all languages is, of course, a crucial question. Where it is not, the Abstract Wikipedia knowledge representation will need to supplement the Wikidata content with additional details about the relation between the participants or the participants themselves, and these details should be language-neutral, to the extent that this is practicable. The item {{Q|Q124441}} has no [[:d:Q124441#P31|P31]] statements; it has only [[:d:Q124441#P279|P279]]s, including one relating it to {{Q|Q212920}}, which suggests {{Z|Z26095}} is the appropriate choice here even if the rendering in some languages is the same. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:52, 19 April 2026 (UTC) ::Thanks for explaining it. I think that I'll change the implementation of {{Z|Z26095}}, so that in Italian it produces more or less the same output of {{Z|Z26039}} (both with the definite article). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:24, 20 April 2026 (UTC) == Equivalent of Z6830 for lexemes == Is there an equivalent of {{Z|Z6830}} that enables retrieving all lexemes pointing to a particular lexeme using a specific property? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 21:06, 20 April 2026 (UTC) :There's {{Z|6831}} but I think that's slightly different again to what you're after. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 12:31, 21 April 2026 (UTC) ::Thanks for sharing that one, I did not know it existed. But you are right, it’s not quite what I am looking for. I want a function that would take a Wikidata property reference (like P5191, which is ‘derived from lexeme’) and a Wikidata lexeme reference, and return a list of lexemes that reference that lexeme using that property. [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 13:23, 21 April 2026 (UTC) == Storing huge datasets == It is not a necessity I suppose, but an idea came to me earlier to write a function that would give the corresponding [[en:Shavian alphabet|Shavian alphabet representation]] of an English word written with the Latin alphabet, or perhaps apply that operation to an entire sentence. However, just trying to guess as to what the IPA pronunciation of each word passed into it could be is is both not ideal (pronunciations obviously can and will vary widely between accents) and infeasible <s>(Wikidata lexemes don't really seem to account for pronunciation)</s>. It happens, though, that a comprehensive Shavian dictionary exists named the [https://readlex.pythonanywhere.com/ ''Read Lexicon''], which uses pronunciation and spelling similar to that used by the creator of the alphabet himself. This would be a good dataset to use in performing this translation in the function, but it appears that, all in all, the total size of the dictionary is [https://github.com/Shavian-info/readlex/blob/main/readlex.json ''nearly 26MB''] when formatted as JSON, which would certainly be larger when converted into a typed list. I am wondering if this will ever be feasible or admissible, or if there is really a way around this if importing such a large set of data is deemed impractical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 22:30, 20 April 2026 (UTC) :{{re|Theki}} "Wikidata lexemes don't really seem to account for pronunciation"" is patently untrue; not only does every Bokmål lexeme form have IPA attached to it (thanks to Jon Harald Søby), but there are lots of languages--including English--that have pronunciation information, whether through IPA or otherwise, indicated on their forms. The big issue of course is that adding this data is not always possible to perform efficiently--for instance, I'd love to have Yiddish pronunciation respellings from Paul Abelson's dictionary on as many English forms as possible, but this dictionary not being previously processed makes this difficult. The data set you have brought up, if a suitable reading of [[:m:Wikilegal/Lexicographical_Data]] allows it, could be added as {{P|7243}} statements on various English forms. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 23:20, 20 April 2026 (UTC) ::Well, sorry... I haven't witnessed these pronunciation statements before, I wasn't aware of their existence until you pointed it out. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 21 April 2026 (UTC) :I got 1,900,000 characters into [[Z33875]] before the UI gave up on me. I'm not sure what the limit is. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:21, 21 April 2026 (UTC) == Could not serialize input JS object: Number <small><small>[insert tested number here]</small></small> == I'm not one to throw my problems at others, but I have no idea how to fix this. Am implementing {{Z|Z24602}} in JavaScript, which requires returning a typed map. It now works for every type of value except numbers. Tried explicitly converting the numbers to float64, but either way it throws the error above. Would appreciate it if anyone could diagnose or fix the problem, as my knowledge of Wikifunctions is amateur at best. Thank you. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:32, 23 April 2026 (UTC) :The quick answer is that like some list-related functions, code implementations returning typed maps are not possible unless the type of the objects in the map is specified in the function signature (e.g. if it was a map from Strings to Natural numbers only). So unfortunately, I think you've chosen a function that is not really possible at the moment. There are a few ideas of how we might address this, but for the moment, work on something else. Sorry! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:21, 23 April 2026 (UTC) :Maybe explicitly using [[Z13518|natural numbers]] would work? I would try using <code>{ "Z1K1": "Z13518", "Z13518K1": "[number]" }</code> to represent numbers, perhaps, and seeing if that works. Of course, you would also probably have to adapt this for other types that cannot be serialized, and I'm not sure how easy that would be to generalize (assuming [[w:Don't repeat yourself|DRYness]] is desired). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:39, 23 April 2026 (UTC) == Help with creating a function for Abstract Wikipedia == Hello! I was inspired by {{Z|Z26570}} to create {{Z|Z33975}}, however I'm not sure how I add specific language implementations here. Can anybody help me? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 10:41, 23 April 2026 (UTC) : I think I figured it out, I created a new object with the language config type, added {{Z|Z14310}} to my implementation, and added a new function for English... At least I think that's how it works... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 13:16, 23 April 2026 (UTC) ::You have the right idea, as far as I know. I went ahead and connected the implementations you created as they appear to work fine for English, and added a test for {{Z|Z33975}} (which passes [[File:Twemoji 1f601.svg|24px]]). I also corrected an error you made on the config object where you appear to have accidentally connected English to {{Z|Z33975}} instead of {{Z|Z33977}}. Thank you for contributing! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 23 April 2026 (UTC) ::: {{re|Theki}} Thank you so much for you help! Could you please kindly also connect the implementations for {{Z|Z33986}} which I just made, which is going to be used for the Hebrew implementation of {{Z|Z33975}}. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:11, 23 April 2026 (UTC) ::::You seem to be returning the wrong type in both implementations. Functioneers should not connect implementations that don't work for non-functioneers. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:13, 23 April 2026 (UTC) ::::: {{re|Feeglgeef}} Oh thank you for pointing that out! I am still a bit new to this project and confused, so I need to read up some more about this. How do I return a monolingual text object? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:17, 23 April 2026 (UTC) ::::::I'm trying to fix it for you, the construction of ZObjects in code implementations is a bit difficult right now. Since the State origin using entity and class function will (presumably) be composition, perhaps {{Z|33975}} can be adjusted to return a string, using {{Z|26107}} and {{Z|26107}}? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:21, 23 April 2026 (UTC) :::::I did not notice any discrepancies from looking at the functions by themselves, and it seemed to work fine on my end. Is it bad practice for NLG functions to return the monolingual text type? I had assumed it was logical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:24, 23 April 2026 (UTC) ::::::Both implementations are failing all three tests on my end. No consensus has been established as to whether monolingual texts or strings should be used, so it's like the [[w:War of the currents|war of the currents]] but for Wikifunctions. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:27, 23 April 2026 (UTC) :::::::Oh, you were referring to {{Z|Z33986}}. I assumed you were stating that something was wrong in the earlier English functions that I missed; I apologize for the misunderstanding. Has there been any centralized discussion on this string vs. monolingual text issue? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:31, 23 April 2026 (UTC) ::::::::Not that I'm aware of, I've brought it up on the telegram twice before, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:49, 23 April 2026 (UTC) ::::::::The centralised discussion is at [[WT:Abstract Wikipedia/2025 fragment experiments#Proposed recommendation: Fragments should return Z11/monolingual strings]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:19, 24 April 2026 (UTC) ::::::: {{re|Theki|Feeglgeef}} Can only functioneers test implementations? For me I can't test it at all... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:32, 23 April 2026 (UTC) ::::::::AFAIK, test cases are only immediately testable during editing of a function if they are connected. This is one of my personal pain points with Wikifunctions, iterating on functions without exhaustive connected test cases makes debugging practically impossible for non-functioneers working on newly-created functions... I (or Feeglgeef) can quickly connect the tests you need for you if you want, although if they are not well-formed they may need to be disconnected again afterwards. Additionally, I could temporarily connect the implementation you are writing so that you can test it on the sidebar as you work, but I'm not sure if this is advisable. That functionality is also something that unfortunately only works when not disconnected. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:43, 23 April 2026 (UTC) :::::::::Yup, agree with you on all points, thanks. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:48, 23 April 2026 (UTC) == Please disconnect implementation == I think I've fixed my issue with {{Z|Z33986}}, but I can't edit an actively connected implementations with my rights. I must admit it is an AI-aided fix, I feel very strongly about disclosing that. Courtesy pinging [[User:Theki]] and [[User:Feeglgeef]]. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:51, 23 April 2026 (UTC) : Additionally, I think the JS might be working. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:52, 23 April 2026 (UTC) : Just to clarify, I mean disconnect the Python implementation please. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:53, 23 April 2026 (UTC) :{{Done}} I've disconnected the Python implementation. :I've also added a couple of tests. The rule is a bit more complicated than adding a maqaf before every character that is not a Hebrew letter. Unfortunately, I don't think I'll have time to fix the implementations any time soon. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:03, 23 April 2026 (UTC) :: Thank you! :: Also, for some reason I thought you put a maqaf before all gershayim, so thanks for correcting me. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:09, 23 April 2026 (UTC) :::No, that's not the rule. :::The rest of this reply is an [[:wikt:info-dump|infodump]], feel free to ignore it :) :::In [https://hebrew-academy.org.il/topic/hahlatot/punctuation/ the Academy's punctuation rules], the rule for adding a maqaf is written kind of badly: שמים מקף ברצף שיש בו שני סוגי גופנים, כגון אותיות ומספרים ("maqaf is added in a sequence in which there are two types of fonts, such as letters and numerals"). These are not different types of "fonts", but different types of characters, and I should email them about it. It gives the examples <span lang="he" dir="rtl">ה־12</span> and <span lang="he" dir="rtl">ב־DNA</span>. It doesn't say anything explicitly about quotation marks, but in other places on the same page, you have stuff like <span lang="he" dir="rtl">ב"הארץ"</span>, and from that I deduce that a maqaf is not needed before double quotes if there are Hebrew letters inside the double quotes. :::That said, a few people do think that there must be a maqaf before double quotes. I have a somewhat surprising example of somebody who always does it: translators of Scientology materials into Hebrew. At least that's what they did last time I looked at them, about ten years ago. Those people are certainly prolific, and they get points from me for consistency, but this not the prevalent standard. (And if I recall correctly, they use the minus and not the proper Hebrew maqaf, and they don't get any points from me for that!) :::Also, the name of the character is just "double quotes" and not "gershayim". Gershayim are mostly for abbreviations, although most people use the same character for them. I use ״ for gershayim, as do a few other nerds, but we're the minority. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:35, 23 April 2026 (UTC) :::: {{re|Amire80}} Yeah, "font" is a weird choice of wording here by the Academy...<br> I think I'll follow your guidance and not use a maqaf for quotes beginning with Hebrew letters. <br> I should also add more tests for different types of quotes, like straight (", '), curly (“, ”, ‘, ’), gershayim (״, ׳), including single quotes.<br> P.S. gotta deduct points from Scientology for being a cult but that's neither here nor there [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:49, 23 April 2026 (UTC) :::: {{re|Amire80}} Courtesy ping because I mistyped your username on the last message. Anyways I'm also gonna do that tomorrow because I'm tired now... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:50, 23 April 2026 (UTC) == Connect implementations == Hello! I'm done with the implementations of {{Z|Z33986}} both in JS and Python, and all tests pass. Pinging @[[User:Amire80|Amire80]] to check if all the tests I've added are alright. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 15:24, 24 April 2026 (UTC) :Connected. It's possible that some more changes will be needed, but it looks OK now. :Another little comment: It should be called "clitic" and not "prefix". [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:56, 24 April 2026 (UTC) : {{re|Amire80}} Thanks for your comment! Luckily labels are easy to edit, so I'll get to it. : Currently I'm working on Bulgarian {{z|Z34072}} and {{z|Z34084}}, along with other Bulgarian functions. After I'm finished with those I'll take your advice. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 16:01, 24 April 2026 (UTC) == Please connect my Bulgarian implementations == I recently created the following Bulgarian functions: * {{Z|Z34070}} (currently broken, I think because another function I built it upon is unimplemented) * {{Z|Z34088}} * {{Z|Z34105}} * {{Z|Z34072}} * {{Z|Z34084}} Can somebody please connect these functions, and perhaps suggest other functions I could localize? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:03, 24 April 2026 (UTC) : Specifically, [[Z34070]] is based on [[Z34072]] [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:05, 24 April 2026 (UTC) :{{done}} for everything that passes, [[Z34070]] still does not work after purging WF's cache, though. For future reference, please request on the [[WF:Community portal|community portal]] instead of the project chat. Thank you for your work! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:03, 24 April 2026 (UTC) :: {{re|Feeglgeef}} Thank you for your help! I will keep in mind to go to the [[project: community portal| community portal]] in future instead for this. :: I still don't understand why {{Z|Z34070}} fails... It's implementation is almost completely identical to [[Z30399]] from {{Z|Z30397}}, unless I messed something up... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:11, 24 April 2026 (UTC) :::{{done}} No, it was mostly just timing out. It is better to use selective fetches where possible. One case is failing to match the expected results, but at least it is returning something. For all I know, it might even be acceptable! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 20:35, 24 April 2026 (UTC) :::: {{re|GrounderUK}} Thank you so much for your help! The one failed case is with a definite article, so I feel like that might be fixed in the future... <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:43, 24 April 2026 (UTC) == Editor experience suggestions == I'm a bit frustrated with the editing experience on Wikifunctions, and I have suggestions based on pain points I've had contributing to this project: * Adding a wizard to create functions, implementations, and tests in one flow, somewhat like Wikimedia Commons' upload wizard * A sandbox for experimenting without changing mainspace functions, and maybe letting non-functioneers connect implementations ([[Project: Sandbox]] doesn't seem to fit this) * We could have functions for creation based on the sandbox, like how Wikipedia has articles for creation and edit requests, * Maybe even another test instance of Wikifunctions, like how Wikidata has [[testwikidata:|Test Wikidata]] I really like this project and I don't mean to whine, but it certainly has a lot of pain points both for technical and non-technical people. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:41, 24 April 2026 (UTC) : It's also really complicated to localize functions, so maybe we should add another wizard for that, where you can choose a language, and then create the new function with the aforementioned function wizard, and it just automatically adds it to the related language configuration object of the related function. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:48, 24 April 2026 (UTC) :# Sounds good to me. :# A sandbox available is [[Z10119]], though an extension-provided sandbox that allows you to manipulate the types, code, and tests easily without interfering with the mainspace would be nice. :# [[WF:Suggest a function|This page]] works to some extent, though it's too messy in my opinion. :# We used to have a "beta cluster" but it [[phab:rOMWC5f625c5846b5f779473fa32c9a02d87e59215dfa|got shut down]] just over a year ago because it was broken. :[[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:07, 24 April 2026 (UTC) == Language parameters in language-specific functions == I think that an effort should be made to give the different natural language options corresponding to different English dialects, Chinese scripts, etc. more of a use (I added the test {{Z|Z34119}} to {{Z|Z26095}} and unsurprisingly it fails). There are two main problems with this approach that I can identify: * If you ask the majority of these functions to make a sentence in British English, much of the time it will give you an output with missing words, because it does not fallback to English labels in the case of a British English label for that item missing. The same applies for every other English dialect, British English is just an example here. * Uninformed editors will probably see the presence of a language parameter on these functions, consider it redundant, and remove it. [[Special:Diff/268074|I have made this mistake before]]. In my opinion, in a perfect world, all of these language generation functions would output monolingual text, and if the user asks for American English text, then American English text is what they'll get. If the user asks for Japanese text in hiragana specifically, then that's what they'll get in return. This is not as high-priority as just rendering text in the language plainly in the first place, but it's something that I feel is still worth devoting some effort to. Right now switching functions to use this paradigm is difficult because, on the one hand, I don't know if consensus tends towards this direction being ideal or advisable, and I don't want to make changes like this without at least notifying the wider community. In addition, all tests break once a parameter is added or removed, and the function editor does not recognize the change in number of parameters and therefore you have to remove the function call, re-add it along with all of its parameters it had previously (which is a tedious cut-and-paste job), and then it will work again. This is something that you can do in five seconds by just adding a few lines of JSON to the test source, but this is not directly editable from the Web browser. This tedium is largely what's preventing me from doing this on a larger scale, besides asking for comments first. If anyone has any insights or comments on this, then that would be appreciated. If a reference of functions with and without the support for language variants is needed, of course [[WF:NLG]] can be perused, but I've also my own list cataloged at [[User:Theki/functions#language]]... Of course, this thread has many similarities to [[#"language" argument for certain functions|the one above]], but this concerns me going out and making this consistent across these NLG functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:09, 24 April 2026 (UTC) :I've created {{Z|Z34122}} as an extension to {{Z|Z34039}} for larger functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:34, 24 April 2026 (UTC) :Just to confirm that I, for one, support a Natural language parameter for all natural-language functions. The concern about getting them all aligned is just that we haven’t finally settled on {{Z|Z11}} being preferred to {{Z|Z89}} or some other type that conserves the text’s provenance, so we risk having to change them all again. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:07, 25 April 2026 (UTC) == “Key not found ()”? == What am I doing wrong in {{Z|Z34137}}? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 00:39, 25 April 2026 (UTC) :You were passing a [[Z6091]] to {{Z|32290}}, but it takes a [[Z6001]]. Fixed. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:10, 26 April 2026 (UTC) ::{{done|Thank you}}! [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 14:13, 26 April 2026 (UTC) == Why is my test failing? == Hello! I recently made {{Z|Z34139}} based on [[wikt:Module:bg-translit]], and the test case {{Z|Z34141}} is failing on both implementations, despite the expected output and actual output being the same as far as I can tell. I tried looking at the Unicode codepoints of the output, but those are also identical. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 06:21, 25 April 2026 (UTC) :Yes, it’s a tricky one. I’ve added a normalize step to the result validation in {{Z|Z34141}}, which confirms it is a normalization issue. It looks like it is in the code but I don’t know whether simply normalizing the result is the way to go. Logically, you would normalize both the input and the result. The implementations of {{Z|Z10384}} show you how to do this. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:41, 25 April 2026 (UTC) == Edit request == Hello! I have an edit request for {{Z|Z23752}} and {{Z|Z23414}}. Please replace all the "an/a" logic with <code>Z21739(Argument reference)</code>, both for readability and for more accuracy ("a university is an institution") <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:50, 25 April 2026 (UTC) :{{D}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:24, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #245 is out: The Foundation's search for the perfect language == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-25|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present an academic paper about Abstract Wikipedia, we discuss our latest Type created, and we take a look at the newest created functions. 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:54, 25 April 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=30325620 --> :@[[User:Sannita (WMF)|Sannita (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], technical meta-question: the newsletter quotes the article: ::the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016) :This quotation sounds sensible, but the article's [https://link.springer.com/article/10.1007/s00146-026-02899-w web version], and the PDF that is downloadable from the same page doesn't actually show the emojis. It rather shows text that looks lacking: ::the only way to contest its algorithm is to click or (Crawford and Gillespie [https://link.springer.com/article/10.1007/s00146-026-02899-w#ref-CR14 2016]) :Where did you get the emojis? Is it your (probably correct) guess or is there a version somewhere that actually shows the emojis? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:16, 25 April 2026 (UTC) ::Scratch that. I've found a version with correct emojis: https://wikihistories.github.io/wikilambda-the-ultimate/ [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:37, 25 April 2026 (UTC) == Requested deletion of test == Please delete {{Z|Z34143}}. this was never valid Bulgarian, I messed up. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:19, 25 April 2026 (UTC) :[[WF:RFD]] please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:40, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|talk]]) 00:57, 26 April 2026 (UTC) </bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == Is it OK to connect the implementation? == Hello! I recently applied for functioneer on [[WF:RFG]], and I was wondering whether I could connect the implementation for {{Z|Z34165}} despite its dependency {{Z|Z34149}} being currently unimplemented. That is <em>if</em> I get accepted. I am planning on implementing it based on [[wikt:module:bg-nominal]], but am still having trouble figuring it out for now. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:04, 26 April 2026 (UTC) == Past tense function == Is there a function like {{Z|Z26039}}, but for the past tense (e.g. "Leo Tolstoy <em>was</em> a writer.")? If not, I will create it myself, I just want to make sure there's not a duplicate. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:10, 26 April 2026 (UTC) : {{Done}} with {{Z|Z34224}}, but I have a few kinks to work out with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:35, 26 April 2026 (UTC) :: I need to create some other similar functions for the past tense, I have some ideas: ::* {{Z|Z26095}} ::* {{Z|Z32643}} ::* {{Z|Z28016}} ::* {{Z|Z26570}} ::* {{Z|Z33975}} ::* {{Z|Z27243}} ::* <ins>{{Z|Z26627}}</ins> ::* <ins>{{Z|Z27627}}</ins> ::* <ins>{{Z|Z27173}}</ins> ::* <ins>{{Z|Z29591}}</ins> :: :: Are there any I have missed? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:57, 26 April 2026 (UTC) :I think that here we are starting to walk on dangerous waters: what does past mean? Is it a recent o a far past? Does it have ripercussions on the present or not? Is it just a thing that happened once, many times or for a continuative period of time? :Consider that various languages distinguish between many different types of past. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:38, 26 April 2026 (UTC) :: {{re|Dv103}} That is a fair point... :: How do we go about solving this problem though? I don't think having every sentence on Abstract Wikipedia be "X is a Y" is a very good idea. :: Maybe we have different functions for all these variations of past you mentioned that just map into "X was a Y." in English? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 13:31, 26 April 2026 (UTC) :::To properly solve this problem, we should use a more complete abstract content representation model, like for example the proposal of [[Wikifunctions:Type proposals/Semantic unit|Semantic units]] (look at [[Wikifunctions:Type proposals/Semantic unit/Douglas Adams|the example]] to see how times could be handled). For now, since we're still stuck with single fragment generation functions (that I hope will be slowly replaced with the complete represenation model, when available), we could just restrict your function to a very specific meaning, like "subject was an instance of, for most of its existence" (which means for example that it could be used to say "Douglas Adams was a writer", but not "Abraham Lincoln was a president", since he only was a president for 4 years). Probably my definition is still too vague, and this is why we need to go beyond these fragment generating functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:47, 26 April 2026 (UTC) ::Nitpick... I don't like that it outputs a string instead of monolingual text. With {{Z|Z26039}} it's used so much that I think it's unfixable in that case beyond deprecating it if people care that much, but {{Z|Z34224}} doesn't even have any connected implementations yet. Consider it, maybe? ::Nitpick 2... {{Z|Z34227}} is missing a language parameter. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:08, 26 April 2026 (UTC) ::: I will consider that! ::: I just did that because that's what {{Z|Z26039}} does, so I assumed I should follow suit with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 26 April 2026 (UTC) == Legacy functions == If and when more robust methods of abstractly representing and generating linguistic content come around, and more efficient ways of creating abstract content are devised and implemented, I suspect that our current methods will require some form of deprecation. This is a significant source of concern for me in relation to WF and AW, questioning how prone our current methods of doing things are and eventually will be prone to obsolescence, and how it will be worked around when it comes. We have over 1 250 articles on AW presently, and these are rather all over the place. I suspect the maintenance burden from keeping these articles up to code will eventually, err, creep up on us, I suppose, and some kind of major refactoring will be necessary. We are definitely in a period of experimentation and whatnot right now but eventually, like with enwiki, some sort of structure and rigor will form and I suspect it will start to become rather boring for me... I, for one, very much enjoy experimenting with new and better ways to do things here. I don't personally mind changing things to use a new and better paradigm if need be, that sort of thing highly excites me, but of course there will be things that are left behind, and I suspect maybe bots will be employed to deal with this? A lot of Wikipedia sister sites seem to do that, e.g. going and fixing up use of deprecated templates. Considering the nature of Wikifunctions and Abstract Wikipedia I suspect certain maintenance tasks will be made simpler or even trivial by the typical uniformity of our implementations. I guess I am just concerned if Wikifunctions or Abstract Wikipedia will ever accrue its own kind of "technical debt" with how we are plowing through things presently, and if there is a plan for how we will eventually seek to mitigate that. Maybe too early to ask this question, but I am a notoriously anxious person, so I thought it wouldn't hurt to raise the question regardless... &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:30, 26 April 2026 (UTC) :I very much agree, thank you for expressing my position so well. {{ping|Immanuelle}} has been using an AI-generated tool (well, they haven't edited in a week, perhaps it's a break or perhaps they don't wish to contribute to the project any more) to create a bunch of articles en masse, which I have warned them multiple times is a bad idea (on top of evolving functions, all of the articles are one-sentence-per-paragraph, [[abstract:Q12184|like so]]). That's why I've been avoiding creating articles recently, I'd say I have a good fourth (no data to support, rough guess) of the comments on the wiki, yet less than a percentage of the article count (only three, including the [[abstract:Q319|first article]], though, so perhaps I'm the next [[w:Special:Permalink/908493298|office.bomis.com]]). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:41, 27 April 2026 (UTC) :: I feel that the overwhelming presence of these low-quality articles (which I admit I myself am [[abstract:Q1710970|guilty]]/[[abstract:Q7601858|of]]/[[abstract:Q39338|creating]], usually as testbeds) may incur a large maintenance burden. I do expect them to be easy to detect, however, as searching for the presence of "deprecated" NLG functions is trivial, and it is possible that replacing them with their future ''even abstracter&trade;'' counterparts could be done automatically since they all have the same signatures and can be expected to create the same form of sentence. If it needs to be done manually for a while or for certain delinquent instances, my hope is that it will be fun, at least for a while. :: I just hope that these hypothetical future waves of "this new and versatile way of abstractly representing linguistic content" obsoleting previous methods and requiring refactoring across all articles is only a one-time thing. We should strive to be as robust and flexible as possible from the outset as each brand new paradigm of abstraction is also a brand new maintenance burden for updating old articles. At the end of the day, at least ''some'' of these articles will still render to many different languages even if their methods of creating those sentences of theirs is completely outdated. Ergo, the time it takes for the switchover to be performed across our articles should not be a persistent inconvenience for users (as, of course, they will always still be able to read the content as it was before since these legacy functions aren't being deleted outright), and the increased availability that the new methods will bring about will likely act as motivation for them to join the effort in refactoring (&#x300C;You're telling me that if I rewrite this article in this cool Lisp-looking stuff then I can probably read it in [[abstract:Q9307|Galician]]?? COOL!&#x300D;). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 20:26, 27 April 2026 (UTC) :::Totally agree. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:54, 28 April 2026 (UTC) :::My vague plan is to implement a default function returning an {{Z|Z89}}, for each language-neutral function. A single function would convert any of these to a {{Z|Z11}}, so that a composition of the two can be implemented as the current default until such time as the language-neutral function is ready to return a [[Z89]]. We can already convert a [[Z11]] to a [[Z89]] so, although there is more to be done in this space, existing language-specific functions could be adapted to return a [[Z89]] quite mechanistically. :::Although we certainly could deliver parallel Z89 functions for each existing Z11 function, I don’t think we should assume that particular outcome. Provided the Z89 captures a lang attribute from the Z11’s language tag, the two representations should be largely interchangeable, although I am expecting a Z89 to carry additional attributes at the span level that would be lost on conversion to a Z11 (along with any higher-level tags and attributes). :::When I say there is “more to be done in this space”, I am referring to a new type that would allow HTML fragments to be represented as tractable Wikifunctions objects, but this is currently drafted only in my head! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:21, 29 April 2026 (UTC) == Filtering types of objects == Hello! I have tried to comb through my own edit history several times, but it's really hard to search for specifics because there's no differentiation between different types of objects (functions, implementations, tests, etc.) in the logs as far as I can tell. Am I missing anything? I want it to work sort of like how filtering by namespace works. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 27 April 2026 (UTC) :There is differentiation, it's just rather hard to look through. Since all ZObjects are just JSON data at their core, you can search for instances of <code>{ "Z1K1": "Z[type]"</code>. I haven't tried this so I'm not sure how well it would work and I know MediaWiki search syntax treats quotation marks as a special character, but I have seen Wikifunctions pages link to searches using this before. There is also [[Special:ListObjectsByType]] but it is sitewide rather than specific to your edit history in particular. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:59, 27 April 2026 (UTC) ::''[It doesn’t help directly here, but please see [[WF:Find]] for more details of how this works.]'' [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:24, 29 April 2026 (UTC) :See the feature requests [[phab:T399244]]/[[phab:T373735]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 06:06, 28 April 2026 (UTC) :The lack of filtering edits by namespace is exactly the problem that I was trying to solve with the [[User:Amire80/wikifunctionsanalytics]] tool. :I even kind of succeeded, but it has two major problems: :# It doesn't have any real frontend, so you have to know some SQL to use it (or ask other people who know SQL). :# It doesn't get information from the live site, but from the dump, which appears to be updated once a month. :I've made a [https://quarry.wmcloud.org/query/104794 sample query for you]. Unfortunately, it won't do anything at the moment because of the second problem—your edits started in April 2026, which isn't over yet, so the dump for it hasn't been processed. But I hope that early in May you'll be able to use the same query and see something useful. :(I plan to add support for recent edits, but I haven't done it yet. Now that I more or less figured out how to process Wikifunctions edits, I'm focused on trying to understand Abstract Wikipedia edits. Processing up-to-date edits from both sites will possibly be the next thing I work on, but if you know some Python and want to try doing it yourself, don't wait for me—[https://gitlab.wikimedia.org/toolforge-repos/wikifunctions-analytics Patches welcome].) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:51, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]], I've just updated the data until the end of April. Now the query to which I linked above gives some results. You can also try running other queries if you know SQL. (Or try asking for other queries if you don't.) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:26, 3 May 2026 (UTC) == [[Z34213]] == I'm not quite sure why this implementation is failing. Could someone take a look? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:24, 28 April 2026 (UTC) :I've [https://phabricator.wikimedia.org/T419933#11863997 notified] the team that this is still occurring, the issue was marked as resolved. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:52, 28 April 2026 (UTC) :Some useful tips: :* create more testcases: sometimes it is a random error, so try to see how consistent it is between testcases :* your implementation is very inefficient, since it fetches items and lexemes a lot of times. Ideally, each item and each lexeme should be only fetched once in all the execution tree. :[[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 06:06, 28 April 2026 (UTC) ::Caching (''should?'') means that the lexeme and item data are cached, so the call doesn't actually execute multiple times. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:51, 28 April 2026 (UTC) :::Are lexemes and items actually cached within the same function execution? Even if they are only partially fetched and/or fetched in bulk? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 17:54, 28 April 2026 (UTC) ::::I don't have any evidence to prove that it works but that's definitely A. what's supposed to happen and B. the ideal behavior. This happens because the Z680X functions can be cached just like any other. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 28 April 2026 (UTC) ::::It is unclear. In general, I believe identical branches are resolved only once in orchestration, but there is also independent caching of Wikidata fetches. ::::According to @[[User:DMartin (WMF)|DMartin (WMF)]] ([https://t.me/Wikifunctions/30374 on Telegram]): ::::<blockquote>Well, no. We have caching of Wikidata entities that have been retrieved, but not of the results of nested function calls. There is a proposal for doing this in the context of the V2 composition language, when it's a bit more mature, and it's regarded as a relatively high priority.</blockquote> ::::It’s hard to tell whether fetches in nested calls are, in fact, cached and available for other nested calls in the same call, since it is not generally the actual fetch that consumes the most resources. Rather (I believe), it is construction and transmission of the result object, which is currently repeated afresh in each nested call (unless it is in an identical branch). ::::I hope that’s clear, and I apologise in advance if it happens to be inaccurate! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 29 April 2026 (UTC) :::::Oh, I should clarify.  There is a lot of caching going on, in several different places.  Lexemes and items ''are'' cached by the orchestrator within the same function execution, even if they are only partially fetched and/or fetched in bulk.  When I said that we don't have caching of the results of nested function calls, I meant that's not happening in general, for all nested function calls in compositions.  But fetching of Wikidata entities gets special treatment, so yes, fetched content from Wikidata is cached, regardless if it was fetched by a top-level call or a nested call. :::::It is also true that the construction of a ZObject from the fetched JSON might happen more than once within the same function execution, depending on how a composition has been structured. However, the construction of the ZObject is actually very fast, compared to the elapsed time of getting the JSON from Wikidata. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 18:04, 1 May 2026 (UTC) == Question about cardinal numbers == I was about to edit {{Z|Z16435}} to add my function {{Z|Z34308}}, but I noticed that none of the other functions have a gender parameter. Should I create a new wrapper function "Bulgarian cardinal, neuter", or should I just remove the gender parameter and always return neuter? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:39, 28 April 2026 (UTC) :The “cardinal” functions should return the words used for “counting” numbers in the abstract. :We should consider converting them to return a {{Z|Z11}} rather than a {{Z|Z6}}. It may even be appropriate to return a {{Z|Z12}} to cater for language variants. Either way, I think that would be the approach to adopt for inflected forms, unless reference to specific lexeme-forms is required. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:52, 28 April 2026 (UTC) ::This. If a native of your language were to count up, which form would they be most likely to use? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:29, 28 April 2026 (UTC) ::: {{re|GrounderUK|Feeglgeef}} Thanks for both your input! ::: I relabeled the aforementioned function to {{Z|Z34308}}, and created a new wrapper function {{Z|Z34457}}. ::: Should I specify that my old function is a monolingual text in parentheses? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:26, 28 April 2026 (UTC) ::::You don't have to, unless you think that is something that would require distinction when viewing the function in a list of search results &c. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:36, 28 April 2026 (UTC) == Optional/nullable function parameters == Hello! Recently, I was informed that Wikifunctions has no optional/nullable function parameters as of now. Are there any future plans to support this, and/or workarounds? Maybe create a union type system like "{{Z|6}} or {{Z|23}}". <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 17:53, 28 April 2026 (UTC) :What I do for this is use an "is empty" function corresponding to the type of the parameter in an If statement. If it isn't empty, the function works as intended. Otherwise, it does something else. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:58, 28 April 2026 (UTC) :Unions are not a thing (yet) on Wikifunctions, but you can always define an argument of type {{Z|Z1}}, which means that all types are allowed (I already did this for {{Z|Z26737}}; note that it is still a ugly workaround, don't use it for high level functions). Also, note that usually on Wikifunctions we use {{Z|Z24}} as the null value. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:00, 28 April 2026 (UTC) :: {{re|JJPMaster|Dv103}} Thanks for your help! :: @[[User:Dv103|Dv103]] told me a function call with a missing parameter is treated as an invalid function call, so how does the "is empty" function work with that? :: Also, setting the type to {{Z|1}} seems naive, like setting the type as <code>any</code> in TypeScript... :: Related question: Are there plans to add default values to parameters (outside of "if empty")? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 18:19, 28 April 2026 (UTC) :::Setting the type to {{Z|Z1}} is actually naive, and that's why I advised you to only use it for low-level functions. Currently there is nothing better. Sometimes, type correctness is not actually checked, so it might seem that nullable types are possible. But it is still an hack, and it could broke anytime since it is not intended behavior. :::I don't think that there are current plans to add default values (but correct me if I'm wrong). The closest thing that comes to my mind is that, if you incorporate Wikifunctions into Wikitext, you can leave empty some fields (only of some specific types) and Parsoid will replace them to their default value. This is done only depending on the type, and not on the functions. For example, {{Z|Z6091}} and {{Z|Z6001}} are assigned the QID associated to the page, and {{Z|Z20420}} is assigned the current date. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:56, 28 April 2026 (UTC) :::@[[User:QuickQuokka|QuickQuokka]]: At the very least, [[Z10008]] accepts a null input. Maybe that feature is unique to the String type—I am not sure. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 19:10, 28 April 2026 (UTC) ::::I think it's just not checked, but it shouldn't be intended. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:20, 28 April 2026 (UTC) ::::Strings and typed lists can be “empty” in the sense that their length can be zero. Typed pairs may also be “empty” in a degenerate sense, but such an object will not be returned from a code implementation. A typed map with no entries will also fail to be returned from code, although it is fine in compositions. ::::For a genuinely optional parameter, I prefer a properly typed list, which at least encourages an argument of the correct type. {{Z|Z813}} is also typically faster than {{Z|Z10008}}. Quite a good example of this approach is {{Z|Z23723}}, where it helps to resolve the type union (using [[Z1]]) for both Z6003K1 and Z6003K3. Of course, there’s nothing to prevent more than one element in the list, but additional elements are easily ignored. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:55, 28 April 2026 (UTC) :Pinging {{ping|Jdforrester (WMF)|prefix=|p=}}, I believe there are no current plans. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:02, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]]: I'm afraid there are no current plans to build out optional params, indeed; we would be happy to review this if a compelling case was made, but it'd be a lot of work to re-build the [[Wikifunctions:Function model|function model]] with that support and ensure we don't break (too many) things. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:11, 28 April 2026 (UTC) == Z6830 for Chinese == I was trying to use {{Z|Z6830}} for implementation in the Chinese-language. And turns out most of the Lexeme on Wikidata is using [[d:Q727694]] as the language instead of [[d:Q7850]]. This makes it impossible to use the mentioned function above, since Standard Chinese is not available (or did I miss something?). Is there a way to fetch lexemes with language=[[d:Q727694]] from item? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:20, 30 April 2026 (UTC) :@[[User:Sun8908|Sun8908]] There is [[Z1006]] for Chinese and it has the language code zh. There is an overview of languages in [[Module:Wikifunctions label]] so you can search there for chinese versions and choose the one you need. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 5 May 2026 (UTC) ::I know that. The problem is when using the function [[Z6830]], it cannot retrieve lexeme with language [[d:Q727694]] (but it is the "Chinese language" with the most current Wikidata lexemes, see [https://ordia.toolforge.org/language/ ordia]). I think it should be a Wikidata problem, I might fix it (possibly by creating the same lexemes with language code zh) on Wikidata. Thanks anyway. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 05:39, 6 May 2026 (UTC) :Could you provide an example of a Chinese lexeme that has a linked Wikidata item, or a Z6830 function call that fails to find such a lexeme where one exists? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 07:55, 6 May 2026 (UTC) ::Here: [[d:Lexeme:L846083]]. I think that's a primary reason of me trying to look into this problem, as the label in zh for [[d:Q6256]] (country) is not a single phrase (see its talk page on WD for more information). This makes some Abstract Wikipedia articles very weird in Chinese when {{Z|Z26570}} is used, so lexeme could potentially fix that. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 10:33, 6 May 2026 (UTC) :::Thank you. It looks as though {{Z|Z6830}} [https://www.wikifunctions.org/view/en/Z6830?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z6830%22%2C%22Z6830K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q6256%22%7D%2C%22Z6830K2%22%3A%7B%22Z1K1%22%3A%22Z6092%22%2C%22Z6092K1%22%3A%22P5137%22%7D%2C%22Z6830K3%22%3A%7B%22Z1K1%22%3A%22Z60%22%2C%22Z60K1%22%3A%22cmn%22%2C%22Z60K2%22%3A%5B%22Z6%22%5D%7D%7D returns that lexeme for language tag "cmn"]. Perhaps that tag should be added into the helpers for {{Z|Z24144}}? If it is widely used for lexemes, perhaps it should have its own {{Z|Z60}}? In any event, improvements might be considered under [[:phab:T390563]] (or otherwise), including amending [[Z6830]] to also consider "cmn" (and "zho", "chi"…?) when requests are made for "zh-hans" or "zho-hant" (or others?) @[[User:Winston Sung|Winston Sung]] @[[User:DMartin (WMF)|DMartin (WMF)]] [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:22, 6 May 2026 (UTC) ::::If you go to [[d:Special:NewLexeme]] and put in [[d:Q727694]] as the language, it is going to tell you it has an unrecognized language code. So I believe "cmn" should not be a {{Z|Z60}} by default? I also started [[d:Wikidata:Project_chat#Lexemes_with_language_Standard_Chinese_(Q727694)|a discussion on WD]] regarding this. I guess we can still use it as a fallback language though if possible. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 03:43, 7 May 2026 (UTC) ::::We don't have a separated <code>cmn</code> BCP 47 language subtag in MediaWiki and Wikidata at the moment. <code>zho</code> and <code>chi</code> are ISO 639 language codes but not BCP 47 language subtags. ::::For Modern Standard Mandarin, please use <code>zh-*</code> language tags for now. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 15:26, 8 May 2026 (UTC) == Key not found error == Is there a reason why I am getting key not found error for this [[Z34677|function]] {{Z|Z34677}}? All the underlying functions run and all the test cases work. The debug information does not give more details. Any pointers? Thanks in advance [[User:Jsamwrites|John Samuel]] 19:24, 1 May 2026 (UTC) :It was passing the [[Z6091]] to {{Z|34641}} when that takes a [[Z6001]]. I've fixed that, but there's some other problem with the logic, so I've left it disconnected. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 19:42, 1 May 2026 (UTC) ::@[[User:YoshiRulz|YoshiRulz]] Thanks a lot. [[User:Jsamwrites|John Samuel]] 20:21, 1 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, 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:21, 2 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=30325620 --> == Any formal process for deletion of pages == Does a formal process exist for the deletion of functions, implementations, and tests that includes a notification system for creators, analogous to Wikidata’s process, explaining the rationale behind the deletion (or proposal for deletion)? [[User:Jsamwrites|John Samuel]] 12:36, 3 May 2026 (UTC) :Does [[Wikifunctions:Requests for deletions]] work? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:00, 3 May 2026 (UTC) :Please see the discussion at [[Wikifunctions talk:Requests for deletions#Should we expect Objects' creators to get pinged on deletion proposals?]]. :As I see it, it is the proposer’s responsibility to consult appropriately before making a request and we expect our administrators to act only when satisfied that appropriate consultation has occurred. In many cases, no consultation is required. Administrators may delete their own contributions without making a request, but this is not a practice I would encourage. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:51, 3 May 2026 (UTC) == Implementation of rational number in JS doesn't match in Z19677 (Rational number) and Z28579 (RGBA colour) == In {{Z|19677}} it's <syntaxhighlight lang=js> { "K1": sign * numerator, "K2": denominator } </syntaxhighlight> but in {{Z|28579}} it's <syntaxhighlight lang=js> [ sign * numerator, denominator ] </syntaxhighlight> '''<span style="font-family:Iosevka,monospace">[[User:沈澄心|<span style="color:#9f3526">dring</span>]][[User talk:沈澄心|<span style="color:#534fa3">sim</span>]]</span>''' 05:15, 4 May 2026 (UTC) == Nested functions in compositions == I wish it will be easier to a add another function about a specific existing function in a function implementation based on a composition. When I write long functions in spreadsheets I usually stat with a small part and then I try to go further and after important steps I test if the output is as expected. I created [[Z34826]] to get the German gender specific occupation lexeme for a specific person based on their gender. I wanted to add a function around the existing one and it was not successful. It is not very easy to implement as it requires the possibily to move a part to another section but I think it can be helpful if it will be implemented. So far I spend more time as expected on the function. Describing it with words what the function needs to do is much easier than implementing it here in Wikifunctions. So I think there needs to be improvement to make Wikifunctions more accessible. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:10, 5 May 2026 (UTC) :Have you tried to use the copy-paste functionality? It is very useful to move parts of composition arounn. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 07:12, 6 May 2026 (UTC) :I've also found the composition editor to be wholly unsuitable for any expressions more than a few levels deep. (Even with the <code>localStorage</code> clipboard, because of its overzealous type checks.) Compositions naturally grow out from the "leaves", the immediate operations on the inputs, while the interface really wants you to build from the "root". I mostly use the [https://yoshirulz.gitlab.io/WikiLambdaBlockly drag-and-drop block editor] which I made to smooth over some of the site's problems, so if you want to try that out and give me some feedback I'd appreciate it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 14:36, 6 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the 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 [[: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/1778520600 May 11, 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]]) 11:16, 8 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=30325620 --> == RGBA colour, spelling... == Something that has always irked me a little bit is the spelling of [[Z28579|RGBA colour (Z28579)]]. I guess this is not unsurprising for me considering my use of US English but I think there is more to it than preference and I want to try to argue for it being changed to use American spelling. I know that this probably has a snowball's chance in hell of actually garnering any support, so I won't really be miffed if the spelling remains as it is, but I thought it wouldn't hurt to raise this regardless. The main issue I have with it is the spelling of the original proposal. When infernostars raised the [[Wikifunctions:Type proposals/RGBA color|type proposal]], the spelling was 「RGBA color」. Of the comments that mentioned the word 「colo[u]r」, two used British spelling while six used the American spelling as used in the proposal. The only thing that really pointed to the use of ''colour'' was the fact that the catalog page on color functions used that spelling already. For all intents and purposes, the spelling of the original proposal should have been maintained, but it was not; [[User:DVrandecic (WMF)|DVrandecic]], the eventual creator of the type, used a different spelling. It should be noted that there was really no reason for this to occur and while it is an undoubtedly minor issue I still believe it should be rolled back and the type should use the spelling of the original proposal and majority of editor comments. In [[abstract:Q936|OpenStreetMap]], there have been keyvalue proposals that have had the finalized spelling that gets put to use be in British English despite the original proposal being in American English; this has usually occurred with proposals relating to 「X center/centre」 tags. This makes sense on the surface, because OpenStreetMap is maintained by a UK organization, and still has close ties to Europe. The Wikimedia Foundation, however, is an ''American'' company. This is often brought up as a fallible argument when debating article spelling on the English Wikipedia, and I don't bring it up to support that 「RGBA color」 should be used for that exact reason, but rather to state that OpenStreetMap's general policy on tag names need not apply here. It appears to me that, at least initially, the majority of 「core contributors」 to Wikifunctions used British English; I can name YoshiRulz, 99of9, GrounderUK, and VIGNERON.<ref group="color">I'm avoiding linking to these folks because I don't think pinging them about this discussion is all too necessary unless they themselves want to be involved; I don't want to clutter their inboxes just to briefly mention them. I pinged Denny because, well, I'm asking him a question directly, but everyone else I would prefer to join this discussion by their own accord... not that I wish for this decision to be confused as me going 「these people use British English so they will probably oppose my idea, I won't invite them to the discussion because of that」...no, I promise you that is not the reason.</ref> I see (or saw) these people ''everywhere'', so it makes sense that British English has prevailed in some sorts on this website, but I don't think that indicates that it should be the ''preferred'' spelling across the website, at least not to the point where a proposal should have its name changed to match such a "consensus".<ref group="color">It could be argued that the front-and-center ''Function catalogue'' using 「catalogue」 is actually indicative of such a "consensus", but ''catalogue'' is in a similar position to the word ''grey'' where I live (that is, the US) in that it is used just as often as its American counterpart. Also, consider Wiktionary's ''Beer parlour'' project chat.</ref> The unnecessary modification of the original spelling is my main argument for changing it back... but of course, I must obligatorily state that on English Wikipedia, it is [[w:Color|Color]] and [[w:RGBA color model|RGBA color model]]; on Wikidata, it is [[d:Q1075|color]] and [[d:Q2325624|RGBA color space]]; in CSS (which typically uses hexadecimal triplets to specify RGBA values), the properties are <code>color</code>, <code>background-color</code>, etc.; bit of a weak jab, but on Schema.org it is [https://schema.org/color color], [https://schema.org/colorSwatch colorSwatch]; et cetera. {{Z|Z28580}} uses ''color'', so does {{Z|Z28591}} and its Python counterpart. Mr. Vrandečić, I have to ask, I'm rather confused... you created the color type using British English spelling, but you were also responsible for the creation of the equality function which uses the American English spelling. You also seem to be writing in American English for the status updates, judging by your use of -''ize'' over -''ise'' endings and use of ''program'' over ''programme'' in [[Wikifunctions:Status updates/2026-04-16]]. Is there something I'm missing or have you switched your preferred variant somewhere along the way? Anyways, do consider this if you wish... again, I don't suppose this will garner much support, it is the ''non-issuest'' of ''non-issues'', but it has irked me to the point where I want to ask about it to get some answers, if nothing else. I am not arguing for every other color function to have its name changed, just the type itself. <references group="color"></references> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 8 May 2026 (UTC) :This is a multilingual project; the <code>en</code> label is <code>RGBA colour</code> and the <code>en-us</code> label is <code>RGBA color</code>. Though I'm not able to switch to <code>en-us</code> via the language picker so that would need to be fixed.<!-- --><br>edit after reading your whole comment: The same is true of {{Q|1075}}, there are labels specified for multiple English variants. (In {{Q|2325624}} it's only an alias.) I agree that other websites' choices aren't binding on us, but from that, I conclude that the more widespread British/Commonwealth spellings should be used for the generic <code>en</code>. As for myself, I'm Aussie and I will continue to use the BrE spellings ([[w:en:Oxford_spelling#Language_tag_comparison|+ "routing"]], TIL) if only by muscle memory.<!-- --><br>[[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 17:42, 8 May 2026 (UTC) :: Your lattermost point would normally be fine in a perfect world. Wikipedia's <code>convert</code> function defaults to "international" English, which I don't personally take issue with because it happens that we here in America are actually outliers for saying and spelling things differently... err, or we were for a while at least, nowadays it seems like an even split (plus you have "yield" vs. "give way" which is effectively the logical opposite of US's use of "meter" over "metre"). :: However, this is not a perfect world, and I don't think <code>en</code> should correspond to any particular variant. It is too fragmented across all software at this point to impose such a requirement. The inability to switch to <code>en-us</code> on this website foregoes an easy and simple solution to this problem that makes everyone happy, because the yanks (such as myself) can't be happy because we can't see the labels in American English even if we wanted to, and the other folk can't switch either as far as I'm aware (and the en-CA and en-GB languages in the preferences page seems to be deprecated). My point being, <code>en</code> is abused to mean "en-UK" just as often as it is abused to mean <code>en-US</code>; I think a decision shouldn't be made on such an assumption of one "default". &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:48, 12 May 2026 (UTC) :Hi @[[User:Theki|rae]]! I have no opinion nor preference on this, and given my background, I am just entirely confused about my spelling preferences myself, as you can tell from my inconsistent usage. I learned British English in school and used that for maybe two decades or so, but moved to the US and lived there for more than a decade, enough to be naturalized, but now I am back in Europe and I am technically a professor at King's College London, soooo.... honestly, I do not know. I don't remember having put too much thought into it at the moment I created it. The good thing is that in Wikifunctions, just as in Wikidata, it is easy to change, without messing things up too much (unlike in Wikipedia), so my suggestion is, just make the change, see if anyone complains, and if they do, discuss it more. I don't know if there is a guideline already in Wikifunctions about the variants. I am happy either way, and honestly, I keep forgetting which variant is which most of the time. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 18:16, 10 May 2026 (UTC) :: I can definitely understand this, although I am unfortunately rather passionate about any minutiae involving preferential minor differences in ''anything'', of which AmE vs. BrE chiefly is. So I dedicate a lot of headspace to it. More than I should. Not that I wish to imply that the comment above that I have wrote is of an irrational nature, or done out of spite or pure emotion and subjectivity; I do genuinely believe that ''RGBA color'' is beyond just a personal preference and is just logical. I may boldly go and change it, but for some reason I was expecting that changing the English label of a Type would require elevated permissions, and I also didn't want to do it only to get immediately reverted because it ''did'' strike a chord with someone, when I could instead see how apathetic, supportive, or in opposition interested people are beforehand and ''then'' act accordingly. I was not meaning to antagonize you over your spelling habits, I did actually use British English for a few years starting in 2020 before I went back to American English, so I'd be a hypocrite for me to decry you for not always sticking to some arbitrary standard of spelling words over the other. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:55, 12 May 2026 (UTC) :Although I spell it “colour”, I think it makes more sense to use “color” for the type, since that is almost always the required spelling when the string functions as a keyword. :More generally, though, Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en". This is unusual, in my experience, as "en" is widely misused in place of "en-US", where there are recorded spelling differences. :(I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere. Use of -ize rather than -ise is a matter of personal preference or house style, but regional autocorrect encourages -ise.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:00, 12 May 2026 (UTC) :: ''Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en"'' :: Definitely agreeing with you on the latter being a good choice. However, I suspect the favoring of "colour" over "color" may be because, in terms of language codes, when sorted alphabetically <code>en-us</code> actually comes ''after'' <code>en-gb</code>. Although, the frontend seems to be sorting <code>en-ca</code> after <code>en-gb</code>, so I don't actually know how correct that is. :: ''I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere'' :: The context of the spelling was "''No program for the NLG SIG meeting for next Tuesday has been proposed''". In that usage context, I think it makes sense to assume that ''program'' is not being used to refer to a computer program, but to a ''program of events'' or similar, something that you would spell as a ''programme'' in British English. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 12 May 2026 (UTC) :{{s}} this. I'm obviously biased but I believe American English is preferable generally, American dominance on the internet (our Department of Defen'''s'''e invented it!) and rapidly-increasing consumption of American media by international English speakers means that more people use American English's conventions, this is clear through for example [http://trends.google.com/explore?q=color%2Ccolour&date=all&geo=Worldwide search trends] (though they aren't particularly reliable). Perhaps this is a bit of a supremacist opinion, but we should have internal consistency, and if we must choose, American English should be our first choice (then Indian and then British English) [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:10, 12 May 2026 (UTC) :: This is rather flawed reasoning, though. I think probably any given British or Indian person would not agree on using that as the reasoning for this, not that you are necessarily ''completely wrong'', but if this is not a good enough reason for English Wikipedia's (admittedly extremely flawed) ''ENGVAR'' policy then I don't think it's likely it will pass here either. :: Although of note is that [https://books.google.com/ngrams/graph?content=color%2Ccolour&year_start=1800&year_end=2022&corpus=en&smoothing=3&case_insensitive=true Google ngrams] agree with you, but "color" vs. "colour" is an eternal holy war that will not be won by demonstrating that more books use US spelling over Commonwealth spelling. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:44, 12 May 2026 (UTC) :::You're probably right that it's not very sound. I'm biased in that other varieties of English irk me, and that's probably mutual for people who are used to other varieties of English when they read what I write! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:56, 12 May 2026 (UTC) :I've decided to boldly [[Special:Permalink/274271|make the change]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:02, 12 May 2026 (UTC) :: Thank you. Considering both you and GrounderUK seem to consider it an okay change, I think this will do for now. :: I should note that the matter of whether to move [[Wikifunctions:Catalogue/Colour functions]] in response to this (however this discussion will ultimately turn out) is a whole other can of worms, in my view. I can't say I have an opinion on that at the moment, but I'm putting it out there regardless. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:06, 12 May 2026 (UTC) :::Personally, I'm in favor of moving the page and renaming all of the items on it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:10, 12 May 2026 (UTC) ::I don't like this (exactly because of the American hegemony you cited), but again, it shouldn't matter because the software is meant to be multilingual. Clearly there's a bug preventing you from picking an English variant/dialect as your display language. But the search bar and Function/Type autocompletion do check the English variants for matches. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 15:15, 12 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[abstract:User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:31, 11 May 2026 (UTC) :Thank you for dedicating your time to writing this, it is very informative. I will try to add input once I'm not in over my head with finals. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:27, 12 May 2026 (UTC) == Display function for HTML fragment == Currently, any collapsed Z89 literal appears as<blockquote>&lt;&gt; [[Z89|HTML fragment]]</blockquote>If I were to create a new Function which returned something like<blockquote>&lt;&gt; 123-byte HTML fragment <q><nowiki><td><span lang=</nowiki>&hellip;</q></blockquote>could that be connected to replace the collapsed form, or would it require changes to the Wikilambda software? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 16:14, 11 May 2026 (UTC) :It might work, but I doubt it. Those angled brackets suggest that the collapsed form is not simply defaulting to the type’s label. Looking at [[:phab:T410509]], I’ve concluded that enhancements to the collapsed form were never considered, rather than being actively rejected. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:12, 12 May 2026 (UTC) ::[[:Phab:T391985]] documents the original design. Note the fifth bullet point under “Acceptance criteria”. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:21, 12 May 2026 (UTC) :I'm not sure the byte-size is necessary, but the outer tag (or first outer tag, though generally I'd prefer most fragments use a wrapper tag if it needs multiple like JSX does, but that's a whole different topic) would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:51, 12 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in 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]]) 14:36, 15 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 --> == [[Z34510]] == This function, which determines if a Wikidata item for a {{q|5}} has an undeprecated {{p|21}} statement of {{q|6581097}}, returns false for {{q|173399}}, a transgender man. This is because his item assigns his P21 statement to {{q|2449503}}, not {{q|6581097}}. I'm not sure how to account for this discrepancy. Should {{z|34510}}: # Include {{q|2449503}} as a value that can lead to a true result, # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a man?") could return true for either "male" or "trans man", # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a trans man?") could return true for "trans man", # Not exist at all? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:48, 16 May 2026 (UTC) :I can't think of a single use case where you would need to determine if a person is a cisgender man and nothing else. Functions are good for generalizing across multiple possibilities when they exist, so I think it would be best if trans men were considered a part of the criteria for returning a true value. If asking for specifically {{q|6581097}}s and ''nothing'' else was desired then the function name would be a misnomer as Elliot Page is inarguably a male (at least in the view of most reasonable and intelligent people). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:03, 16 May 2026 (UTC) :You made the function in the first place; what were you planning on using it for? AW? Maybe it should return a {{Z|25501}} which can then be passed on to other NLG functions. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 May 2026 (UTC) == Lexeme from wikidata label, or "best" lexeme from wikidata item == I was looking into fixing [[Z28028]]. I found that I could add "requires grammatical feature: definite article" to "United Kingdom" (L8558). Now I'm stuck on how to get to that lexeme from {{Q|145}}. There's [[Z23471]], but that for very good reason gives you multiple lexemes with the same sense, and I just want the best one like how the label is always the best string. Is there a function that can do this? There's definitely the case of a Wikidata label that isn't a lexeme (most commonly multiple lexemes) but I'm only considering the case where it is one lexeme here. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:02, 16 May 2026 (UTC) dndzwkyp1k7wdjcd06vfawgdtp9xy94 275574 275558 2026-05-16T22:22:40Z Dv103 11127 /* Lexeme from wikidata label, or "best" lexeme from wikidata item */ Reply 275574 wikitext text/x-wiki {{shortcut|[[WF:CHAT]]|[[WF:PC]]|[[WF:VP]]}} __NEWSECTIONLINK__ [[Category:Help]] <!-- please do not remove this line --> Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc. Other places to find help: * [[Wikifunctions:Administrators' noticeboard]] * [[Wikifunctions:Report a technical problem]] * [[Wikifunctions:FAQ]] {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |timeout=30 }} {{Archives|{{#tag:div|<br />{{Flatlist|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1|hideredirects=1}} |class=mw-collapsible-content|style=font-size:92%;}}|class="mw-collapsible mw-collapsible-toggle mw-collapsed"}} |prefix=WF:Project chat/Archive/ }} == "language" argument for certain functions == Hello. I am relatively new to Wikifunctions. Recently, I tried to create functions for Chinese translation of {{Z|Z26570}} and {{Z|Z26095}} (which became [[Z32788]] and [[Z32900]]). During the creation of these functions, I was trying to take {{Z|Z32212}} as reference. And I realized that the defining role sentence function is taking <code>language</code> as an argument (and the test case of the Chinese-language function already contains two varieties of Chinese). This makes it possible to output monolingual text in <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code>, or any varieties of the language. I think for this reason, it is better to have <code>language</code> as arguments for the implementation of Z26570 and Z26095, and potentially more functions that require {{Z|Z14294}}, since it would output the varieties code instead of just saying <code>zh</code> for <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code> in the output of type {{Z|Z11}}. I am not sure how the fallback mechanism works if one of the language (varieties) do not have a labels/lexemes, but to me, it is reasonable to have a <code>language</code> argument. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 09:38, 31 March 2026 (UTC) :The functions you mention do have a language argument. For Wikifunctions, the {{Z|Z60}} can be at a higher or lower level; whether a {{Z|Z11}} is for a language or a variant is determined by the function that constructs it. Please see {{Z|Z26565}} for an example and feel free to add test cases in Chinese. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:54, 11 April 2026 (UTC) ::Hello @[[User:GrounderUK|GrounderUK]], thanks for the answer. I understand that whether {{Z|Z11}} is for a language or a variant depends on the function. But that is exactly what I am asking for. It is true that [[Z26570]] and [[Z26095]] takes [[Z60]] as argument, but the language-specific functions in {{Z|Z29843}} and {{Z|Z26096}} don't. ::Let me give you an example: INPUT to [[Z26570]]: <code>entity</code>: Tokyo, <code>class</code>: city, <code>location</code>: Japan, <code>language</code>: zh-cn, the config would select [[Z33030]] (created after my previous comment by elseone) as the implementation, and it would RETURN 东京是日本的一个城市。(zh-hans), which is not zh-cn as requested in the INPUT. It would also be using the term not for the variant (when it is different) because it is hardcoded to use the term in zh-hans. However, if we have the implementation like [[Z32790]] (which was created by me but a natural language argument was added by elseone) or [[Z32213]] (that works in the defining role sentence function because of the extra argument), it could cater for different variant. ::If we don't have the language argument in the language-specific function, the desire for article creation on Abstract Wikipedia would be to create a function for every variant. Is it then better to create functions for every variant? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:18, 11 April 2026 (UTC) :::I forgot to mention that there are some hardcoding in {{Z|Z32790}} as well, but I cannot fix it because it is a connected function and I am not a functioneer. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:31, 11 April 2026 (UTC) ::::Okay, I think it’s safe to disconnect this one as the function is not yet configured for use on Abstract Wikipedia. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:04, 11 April 2026 (UTC) :::Ah, sorry… I misunderstood you. I agree that the called function should be able to accept the original language argument. That is simpler in theory than in practice, because the configured functions all have to have the same argument types, as I understand it. I’m not sure which the best approach is, really, but we probably want to avoid two levels of configuration. That suggests that all language-specific functions would need to accept the additional argument, which is unrewarding work for someone. @[[User:99of9|99of9]], @[[User:Jdforrester (WMF)|Jdforrester (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]] Any thoughts? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:57, 11 April 2026 (UTC) ::::I mean, we would need to modify all the functions in each language, which could take some time. But we are still in an early stage. If we don't fix it now and we want to fix it later, it would be a disaster. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 19:25, 11 April 2026 (UTC) :::::Agreed. And we probably want them converted to HTML too, with separate language spans for text in different languages. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:35, 11 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]: This sounds like a reasonable change to make. Note that (given these Functions are primarily for use on Abstract Wikipedia), altering/replacing them to return Z89/HTML fragments is already a desired but breaking change, so making a second breaking change at the same time is probably easiest for fixing things swiftly. That said, that's of course a decision for the Abstract Wikipedia and Wikifunctions communities, not me! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:43, 12 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]@[[User:Sun8908|Sun8908]] to make it a non-breaking change, I've created {{Z|Z34039}} which allows a composition {{Z|Z34043}}. This way you can make functions which either need the specified variant or don't! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:52, 24 April 2026 (UTC) :I have now created {{Z|Z33465}}, which is an implementation of [[Z26570]]. Maybe we can migrate to use that function when more (language-specific) functions for it are ready? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:19, 14 April 2026 (UTC) == No place to ask to activate a function? == I just discovered the {{Z|Z11390}} function and decided to make an overarching language-selecting function for it. After some fiddling around and studying how {{Z|Z32321}} and its set works, I now have {{Z|Z33439}} which has a config object ({{Z|Z33441}}) that selects between the two preexisting language-specific versions I found (English and Malayalam) and the new one I created for my other native language, {{Z|Z33440}}. Except I can't get these to work, because, from what I understand, only [[Wikifunctions:Functioneers|functioneers]] can activate newly created functions and implementations? So where do I apply for the {{Z|Z33439}} and {{Z|Z33440}} functions to be activated? Perhaps we should have a place to ask for it, a la [[w:WP:NPP]] — call it [[Project:New Functions Patrol|New Functions Patrol]] if you will. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] ([[User talk:UndueMarmot|talk]]) 08:58, 14 April 2026 (UTC) :There's [[Wikifunctions:Community portal]] for this. By the way, {{Z|Z33445}} doesn't work because all the code must be inside the main function in Python code. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 09:19, 14 April 2026 (UTC) ::Huh. How could I have missed that? ::But anyway, I've moved the code in {{Z|Z33445}} into inside the main function block. ::Is there any reason why WF decided not to simply allow anyone to write functions? After all, that's how it works with wikitext templates, and these functions are fundamentally serving the same purposes as templates, just written in a different way. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 11:25, 14 April 2026 (UTC) :::I've fixed a couple of technical issues, but tests still fail. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:28, 14 April 2026 (UTC) ::::The tests pass now after some more changes to the code: [[Special:Diff/265232/cur]]. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 12:01, 14 April 2026 (UTC) :::::{{D|Connected}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:02, 14 April 2026 (UTC) :::I think it's a security issue, since Wikifunctions implementations could teoretically be malicious. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:29, 14 April 2026 (UTC) ::::This ^^^. We're very lenient, though, once you've created a few working functions you can apply for the right, per [[WF:Functioneer]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:26, 14 April 2026 (UTC) ::::That explanation [[phab:T343559#11421293|doesn't add up]]. A reason to limit ''connection powers'' to Functioneers might be to prevent vandalism, considering Functions can be used across wikis. But user-provided code is already being executed even without a Functioneer connecting it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 April 2026 (UTC) == Actual difference between {{Z|Z26039}} and {{Z|Z26095}} == What is the actual difference between these two functions? I ask, since it seems to me that the current distinction is more or less that the first one doesn't use an indefinite article in English, while the second does. Which is not a good distinction in a project that should be language neutral. This doubt emerged from my use of the first one in [[abstract:Q124441]], which @[[User:Hogü-456|Hogü-456]] made me notice that is probably wrong. My question is: why is it wrong? How could we clarify the difference? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:46, 19 April 2026 (UTC) :I think the difference is if there is an indefinite article like a or an before the subject or not. In German there can be cases where a definite article is necessary before the subject. I looked at the functions and before the object both times an article is mentioned. As it depends on the language and the word what is the correct function to use I hope it will be clarified and it is an example of the necessity to have a human with understanding in a specific language check it. I hope there will be longer functions what generate more content about a specific kind of item. Then it is necessary to write one such function per language and it can be then applied to several items. It still requires checks and so maybe it is better to write down what item category needs what kind of introduction sentence function for what language. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:05, 19 April 2026 (UTC) ::The point of these two functions (and of the entire Abstract Wikipedia project) is that they should be defined in a purely language-independent way, so that the translation to actual language can be done automatically. This is the reason why these functions have been renamed; I think that this attempt was not succesful, since meaning is still unclear. My proposal to clarify them would be to invoke the concept of [[w:specificity (linguistics)|specificity]]: {{Z|Z26039}} should be named "specific subject is instance of (string)", and should be used only when the QID of the subject uniquely identifies a single thing; {{Z|Z26095}} should instead be renamed in "non-specific subject is kind of (Monolingual text)", and should be used when the QID refers to a multitude of real life items, and we are specifying the class that all these item belong to. This clarification would not still be enough, since it doesn't explain how mass nouns are handled (is water a unique thing? Does {{Q|Q7802}} refer to a single piece of bread or to the entirety of bread, like water?). This problem is very tricky, since mass noun are language-specific and blurry the line between these two functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 20:58, 19 April 2026 (UTC) :Simply put, one corresponds to P31 and the other to P279. Paris is an {{Q|P31}} a {{Q|Q1549591}} :whereas a {{Q|Q1549591}} is a {{Q|P279}} (alias “kind of”) {{Q|Q515}}. Whether the Wikidata knowledge representation will be sufficient to resolve into fluent natural language representations in all languages is, of course, a crucial question. Where it is not, the Abstract Wikipedia knowledge representation will need to supplement the Wikidata content with additional details about the relation between the participants or the participants themselves, and these details should be language-neutral, to the extent that this is practicable. The item {{Q|Q124441}} has no [[:d:Q124441#P31|P31]] statements; it has only [[:d:Q124441#P279|P279]]s, including one relating it to {{Q|Q212920}}, which suggests {{Z|Z26095}} is the appropriate choice here even if the rendering in some languages is the same. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:52, 19 April 2026 (UTC) ::Thanks for explaining it. I think that I'll change the implementation of {{Z|Z26095}}, so that in Italian it produces more or less the same output of {{Z|Z26039}} (both with the definite article). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:24, 20 April 2026 (UTC) == Equivalent of Z6830 for lexemes == Is there an equivalent of {{Z|Z6830}} that enables retrieving all lexemes pointing to a particular lexeme using a specific property? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 21:06, 20 April 2026 (UTC) :There's {{Z|6831}} but I think that's slightly different again to what you're after. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 12:31, 21 April 2026 (UTC) ::Thanks for sharing that one, I did not know it existed. But you are right, it’s not quite what I am looking for. I want a function that would take a Wikidata property reference (like P5191, which is ‘derived from lexeme’) and a Wikidata lexeme reference, and return a list of lexemes that reference that lexeme using that property. [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 13:23, 21 April 2026 (UTC) == Storing huge datasets == It is not a necessity I suppose, but an idea came to me earlier to write a function that would give the corresponding [[en:Shavian alphabet|Shavian alphabet representation]] of an English word written with the Latin alphabet, or perhaps apply that operation to an entire sentence. However, just trying to guess as to what the IPA pronunciation of each word passed into it could be is is both not ideal (pronunciations obviously can and will vary widely between accents) and infeasible <s>(Wikidata lexemes don't really seem to account for pronunciation)</s>. It happens, though, that a comprehensive Shavian dictionary exists named the [https://readlex.pythonanywhere.com/ ''Read Lexicon''], which uses pronunciation and spelling similar to that used by the creator of the alphabet himself. This would be a good dataset to use in performing this translation in the function, but it appears that, all in all, the total size of the dictionary is [https://github.com/Shavian-info/readlex/blob/main/readlex.json ''nearly 26MB''] when formatted as JSON, which would certainly be larger when converted into a typed list. I am wondering if this will ever be feasible or admissible, or if there is really a way around this if importing such a large set of data is deemed impractical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 22:30, 20 April 2026 (UTC) :{{re|Theki}} "Wikidata lexemes don't really seem to account for pronunciation"" is patently untrue; not only does every Bokmål lexeme form have IPA attached to it (thanks to Jon Harald Søby), but there are lots of languages--including English--that have pronunciation information, whether through IPA or otherwise, indicated on their forms. The big issue of course is that adding this data is not always possible to perform efficiently--for instance, I'd love to have Yiddish pronunciation respellings from Paul Abelson's dictionary on as many English forms as possible, but this dictionary not being previously processed makes this difficult. The data set you have brought up, if a suitable reading of [[:m:Wikilegal/Lexicographical_Data]] allows it, could be added as {{P|7243}} statements on various English forms. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 23:20, 20 April 2026 (UTC) ::Well, sorry... I haven't witnessed these pronunciation statements before, I wasn't aware of their existence until you pointed it out. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 21 April 2026 (UTC) :I got 1,900,000 characters into [[Z33875]] before the UI gave up on me. I'm not sure what the limit is. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:21, 21 April 2026 (UTC) == Could not serialize input JS object: Number <small><small>[insert tested number here]</small></small> == I'm not one to throw my problems at others, but I have no idea how to fix this. Am implementing {{Z|Z24602}} in JavaScript, which requires returning a typed map. It now works for every type of value except numbers. Tried explicitly converting the numbers to float64, but either way it throws the error above. Would appreciate it if anyone could diagnose or fix the problem, as my knowledge of Wikifunctions is amateur at best. Thank you. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:32, 23 April 2026 (UTC) :The quick answer is that like some list-related functions, code implementations returning typed maps are not possible unless the type of the objects in the map is specified in the function signature (e.g. if it was a map from Strings to Natural numbers only). So unfortunately, I think you've chosen a function that is not really possible at the moment. There are a few ideas of how we might address this, but for the moment, work on something else. Sorry! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:21, 23 April 2026 (UTC) :Maybe explicitly using [[Z13518|natural numbers]] would work? I would try using <code>{ "Z1K1": "Z13518", "Z13518K1": "[number]" }</code> to represent numbers, perhaps, and seeing if that works. Of course, you would also probably have to adapt this for other types that cannot be serialized, and I'm not sure how easy that would be to generalize (assuming [[w:Don't repeat yourself|DRYness]] is desired). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:39, 23 April 2026 (UTC) == Help with creating a function for Abstract Wikipedia == Hello! I was inspired by {{Z|Z26570}} to create {{Z|Z33975}}, however I'm not sure how I add specific language implementations here. Can anybody help me? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 10:41, 23 April 2026 (UTC) : I think I figured it out, I created a new object with the language config type, added {{Z|Z14310}} to my implementation, and added a new function for English... At least I think that's how it works... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 13:16, 23 April 2026 (UTC) ::You have the right idea, as far as I know. I went ahead and connected the implementations you created as they appear to work fine for English, and added a test for {{Z|Z33975}} (which passes [[File:Twemoji 1f601.svg|24px]]). I also corrected an error you made on the config object where you appear to have accidentally connected English to {{Z|Z33975}} instead of {{Z|Z33977}}. Thank you for contributing! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 23 April 2026 (UTC) ::: {{re|Theki}} Thank you so much for you help! Could you please kindly also connect the implementations for {{Z|Z33986}} which I just made, which is going to be used for the Hebrew implementation of {{Z|Z33975}}. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:11, 23 April 2026 (UTC) ::::You seem to be returning the wrong type in both implementations. Functioneers should not connect implementations that don't work for non-functioneers. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:13, 23 April 2026 (UTC) ::::: {{re|Feeglgeef}} Oh thank you for pointing that out! I am still a bit new to this project and confused, so I need to read up some more about this. How do I return a monolingual text object? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:17, 23 April 2026 (UTC) ::::::I'm trying to fix it for you, the construction of ZObjects in code implementations is a bit difficult right now. Since the State origin using entity and class function will (presumably) be composition, perhaps {{Z|33975}} can be adjusted to return a string, using {{Z|26107}} and {{Z|26107}}? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:21, 23 April 2026 (UTC) :::::I did not notice any discrepancies from looking at the functions by themselves, and it seemed to work fine on my end. Is it bad practice for NLG functions to return the monolingual text type? I had assumed it was logical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:24, 23 April 2026 (UTC) ::::::Both implementations are failing all three tests on my end. No consensus has been established as to whether monolingual texts or strings should be used, so it's like the [[w:War of the currents|war of the currents]] but for Wikifunctions. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:27, 23 April 2026 (UTC) :::::::Oh, you were referring to {{Z|Z33986}}. I assumed you were stating that something was wrong in the earlier English functions that I missed; I apologize for the misunderstanding. Has there been any centralized discussion on this string vs. monolingual text issue? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:31, 23 April 2026 (UTC) ::::::::Not that I'm aware of, I've brought it up on the telegram twice before, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:49, 23 April 2026 (UTC) ::::::::The centralised discussion is at [[WT:Abstract Wikipedia/2025 fragment experiments#Proposed recommendation: Fragments should return Z11/monolingual strings]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:19, 24 April 2026 (UTC) ::::::: {{re|Theki|Feeglgeef}} Can only functioneers test implementations? For me I can't test it at all... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:32, 23 April 2026 (UTC) ::::::::AFAIK, test cases are only immediately testable during editing of a function if they are connected. This is one of my personal pain points with Wikifunctions, iterating on functions without exhaustive connected test cases makes debugging practically impossible for non-functioneers working on newly-created functions... I (or Feeglgeef) can quickly connect the tests you need for you if you want, although if they are not well-formed they may need to be disconnected again afterwards. Additionally, I could temporarily connect the implementation you are writing so that you can test it on the sidebar as you work, but I'm not sure if this is advisable. That functionality is also something that unfortunately only works when not disconnected. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:43, 23 April 2026 (UTC) :::::::::Yup, agree with you on all points, thanks. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:48, 23 April 2026 (UTC) == Please disconnect implementation == I think I've fixed my issue with {{Z|Z33986}}, but I can't edit an actively connected implementations with my rights. I must admit it is an AI-aided fix, I feel very strongly about disclosing that. Courtesy pinging [[User:Theki]] and [[User:Feeglgeef]]. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:51, 23 April 2026 (UTC) : Additionally, I think the JS might be working. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:52, 23 April 2026 (UTC) : Just to clarify, I mean disconnect the Python implementation please. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:53, 23 April 2026 (UTC) :{{Done}} I've disconnected the Python implementation. :I've also added a couple of tests. The rule is a bit more complicated than adding a maqaf before every character that is not a Hebrew letter. Unfortunately, I don't think I'll have time to fix the implementations any time soon. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:03, 23 April 2026 (UTC) :: Thank you! :: Also, for some reason I thought you put a maqaf before all gershayim, so thanks for correcting me. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:09, 23 April 2026 (UTC) :::No, that's not the rule. :::The rest of this reply is an [[:wikt:info-dump|infodump]], feel free to ignore it :) :::In [https://hebrew-academy.org.il/topic/hahlatot/punctuation/ the Academy's punctuation rules], the rule for adding a maqaf is written kind of badly: שמים מקף ברצף שיש בו שני סוגי גופנים, כגון אותיות ומספרים ("maqaf is added in a sequence in which there are two types of fonts, such as letters and numerals"). These are not different types of "fonts", but different types of characters, and I should email them about it. It gives the examples <span lang="he" dir="rtl">ה־12</span> and <span lang="he" dir="rtl">ב־DNA</span>. It doesn't say anything explicitly about quotation marks, but in other places on the same page, you have stuff like <span lang="he" dir="rtl">ב"הארץ"</span>, and from that I deduce that a maqaf is not needed before double quotes if there are Hebrew letters inside the double quotes. :::That said, a few people do think that there must be a maqaf before double quotes. I have a somewhat surprising example of somebody who always does it: translators of Scientology materials into Hebrew. At least that's what they did last time I looked at them, about ten years ago. Those people are certainly prolific, and they get points from me for consistency, but this not the prevalent standard. (And if I recall correctly, they use the minus and not the proper Hebrew maqaf, and they don't get any points from me for that!) :::Also, the name of the character is just "double quotes" and not "gershayim". Gershayim are mostly for abbreviations, although most people use the same character for them. I use ״ for gershayim, as do a few other nerds, but we're the minority. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:35, 23 April 2026 (UTC) :::: {{re|Amire80}} Yeah, "font" is a weird choice of wording here by the Academy...<br> I think I'll follow your guidance and not use a maqaf for quotes beginning with Hebrew letters. <br> I should also add more tests for different types of quotes, like straight (", '), curly (“, ”, ‘, ’), gershayim (״, ׳), including single quotes.<br> P.S. gotta deduct points from Scientology for being a cult but that's neither here nor there [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:49, 23 April 2026 (UTC) :::: {{re|Amire80}} Courtesy ping because I mistyped your username on the last message. Anyways I'm also gonna do that tomorrow because I'm tired now... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:50, 23 April 2026 (UTC) == Connect implementations == Hello! I'm done with the implementations of {{Z|Z33986}} both in JS and Python, and all tests pass. Pinging @[[User:Amire80|Amire80]] to check if all the tests I've added are alright. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 15:24, 24 April 2026 (UTC) :Connected. It's possible that some more changes will be needed, but it looks OK now. :Another little comment: It should be called "clitic" and not "prefix". [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:56, 24 April 2026 (UTC) : {{re|Amire80}} Thanks for your comment! Luckily labels are easy to edit, so I'll get to it. : Currently I'm working on Bulgarian {{z|Z34072}} and {{z|Z34084}}, along with other Bulgarian functions. After I'm finished with those I'll take your advice. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 16:01, 24 April 2026 (UTC) == Please connect my Bulgarian implementations == I recently created the following Bulgarian functions: * {{Z|Z34070}} (currently broken, I think because another function I built it upon is unimplemented) * {{Z|Z34088}} * {{Z|Z34105}} * {{Z|Z34072}} * {{Z|Z34084}} Can somebody please connect these functions, and perhaps suggest other functions I could localize? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:03, 24 April 2026 (UTC) : Specifically, [[Z34070]] is based on [[Z34072]] [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:05, 24 April 2026 (UTC) :{{done}} for everything that passes, [[Z34070]] still does not work after purging WF's cache, though. For future reference, please request on the [[WF:Community portal|community portal]] instead of the project chat. Thank you for your work! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:03, 24 April 2026 (UTC) :: {{re|Feeglgeef}} Thank you for your help! I will keep in mind to go to the [[project: community portal| community portal]] in future instead for this. :: I still don't understand why {{Z|Z34070}} fails... It's implementation is almost completely identical to [[Z30399]] from {{Z|Z30397}}, unless I messed something up... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:11, 24 April 2026 (UTC) :::{{done}} No, it was mostly just timing out. It is better to use selective fetches where possible. One case is failing to match the expected results, but at least it is returning something. For all I know, it might even be acceptable! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 20:35, 24 April 2026 (UTC) :::: {{re|GrounderUK}} Thank you so much for your help! The one failed case is with a definite article, so I feel like that might be fixed in the future... <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:43, 24 April 2026 (UTC) == Editor experience suggestions == I'm a bit frustrated with the editing experience on Wikifunctions, and I have suggestions based on pain points I've had contributing to this project: * Adding a wizard to create functions, implementations, and tests in one flow, somewhat like Wikimedia Commons' upload wizard * A sandbox for experimenting without changing mainspace functions, and maybe letting non-functioneers connect implementations ([[Project: Sandbox]] doesn't seem to fit this) * We could have functions for creation based on the sandbox, like how Wikipedia has articles for creation and edit requests, * Maybe even another test instance of Wikifunctions, like how Wikidata has [[testwikidata:|Test Wikidata]] I really like this project and I don't mean to whine, but it certainly has a lot of pain points both for technical and non-technical people. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:41, 24 April 2026 (UTC) : It's also really complicated to localize functions, so maybe we should add another wizard for that, where you can choose a language, and then create the new function with the aforementioned function wizard, and it just automatically adds it to the related language configuration object of the related function. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:48, 24 April 2026 (UTC) :# Sounds good to me. :# A sandbox available is [[Z10119]], though an extension-provided sandbox that allows you to manipulate the types, code, and tests easily without interfering with the mainspace would be nice. :# [[WF:Suggest a function|This page]] works to some extent, though it's too messy in my opinion. :# We used to have a "beta cluster" but it [[phab:rOMWC5f625c5846b5f779473fa32c9a02d87e59215dfa|got shut down]] just over a year ago because it was broken. :[[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:07, 24 April 2026 (UTC) == Language parameters in language-specific functions == I think that an effort should be made to give the different natural language options corresponding to different English dialects, Chinese scripts, etc. more of a use (I added the test {{Z|Z34119}} to {{Z|Z26095}} and unsurprisingly it fails). There are two main problems with this approach that I can identify: * If you ask the majority of these functions to make a sentence in British English, much of the time it will give you an output with missing words, because it does not fallback to English labels in the case of a British English label for that item missing. The same applies for every other English dialect, British English is just an example here. * Uninformed editors will probably see the presence of a language parameter on these functions, consider it redundant, and remove it. [[Special:Diff/268074|I have made this mistake before]]. In my opinion, in a perfect world, all of these language generation functions would output monolingual text, and if the user asks for American English text, then American English text is what they'll get. If the user asks for Japanese text in hiragana specifically, then that's what they'll get in return. This is not as high-priority as just rendering text in the language plainly in the first place, but it's something that I feel is still worth devoting some effort to. Right now switching functions to use this paradigm is difficult because, on the one hand, I don't know if consensus tends towards this direction being ideal or advisable, and I don't want to make changes like this without at least notifying the wider community. In addition, all tests break once a parameter is added or removed, and the function editor does not recognize the change in number of parameters and therefore you have to remove the function call, re-add it along with all of its parameters it had previously (which is a tedious cut-and-paste job), and then it will work again. This is something that you can do in five seconds by just adding a few lines of JSON to the test source, but this is not directly editable from the Web browser. This tedium is largely what's preventing me from doing this on a larger scale, besides asking for comments first. If anyone has any insights or comments on this, then that would be appreciated. If a reference of functions with and without the support for language variants is needed, of course [[WF:NLG]] can be perused, but I've also my own list cataloged at [[User:Theki/functions#language]]... Of course, this thread has many similarities to [[#"language" argument for certain functions|the one above]], but this concerns me going out and making this consistent across these NLG functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:09, 24 April 2026 (UTC) :I've created {{Z|Z34122}} as an extension to {{Z|Z34039}} for larger functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:34, 24 April 2026 (UTC) :Just to confirm that I, for one, support a Natural language parameter for all natural-language functions. The concern about getting them all aligned is just that we haven’t finally settled on {{Z|Z11}} being preferred to {{Z|Z89}} or some other type that conserves the text’s provenance, so we risk having to change them all again. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:07, 25 April 2026 (UTC) == “Key not found ()”? == What am I doing wrong in {{Z|Z34137}}? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 00:39, 25 April 2026 (UTC) :You were passing a [[Z6091]] to {{Z|32290}}, but it takes a [[Z6001]]. Fixed. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:10, 26 April 2026 (UTC) ::{{done|Thank you}}! [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 14:13, 26 April 2026 (UTC) == Why is my test failing? == Hello! I recently made {{Z|Z34139}} based on [[wikt:Module:bg-translit]], and the test case {{Z|Z34141}} is failing on both implementations, despite the expected output and actual output being the same as far as I can tell. I tried looking at the Unicode codepoints of the output, but those are also identical. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 06:21, 25 April 2026 (UTC) :Yes, it’s a tricky one. I’ve added a normalize step to the result validation in {{Z|Z34141}}, which confirms it is a normalization issue. It looks like it is in the code but I don’t know whether simply normalizing the result is the way to go. Logically, you would normalize both the input and the result. The implementations of {{Z|Z10384}} show you how to do this. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:41, 25 April 2026 (UTC) == Edit request == Hello! I have an edit request for {{Z|Z23752}} and {{Z|Z23414}}. Please replace all the "an/a" logic with <code>Z21739(Argument reference)</code>, both for readability and for more accuracy ("a university is an institution") <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:50, 25 April 2026 (UTC) :{{D}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:24, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #245 is out: The Foundation's search for the perfect language == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-25|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present an academic paper about Abstract Wikipedia, we discuss our latest Type created, and we take a look at the newest created functions. 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:54, 25 April 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=30325620 --> :@[[User:Sannita (WMF)|Sannita (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], technical meta-question: the newsletter quotes the article: ::the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016) :This quotation sounds sensible, but the article's [https://link.springer.com/article/10.1007/s00146-026-02899-w web version], and the PDF that is downloadable from the same page doesn't actually show the emojis. It rather shows text that looks lacking: ::the only way to contest its algorithm is to click or (Crawford and Gillespie [https://link.springer.com/article/10.1007/s00146-026-02899-w#ref-CR14 2016]) :Where did you get the emojis? Is it your (probably correct) guess or is there a version somewhere that actually shows the emojis? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:16, 25 April 2026 (UTC) ::Scratch that. I've found a version with correct emojis: https://wikihistories.github.io/wikilambda-the-ultimate/ [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:37, 25 April 2026 (UTC) == Requested deletion of test == Please delete {{Z|Z34143}}. this was never valid Bulgarian, I messed up. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:19, 25 April 2026 (UTC) :[[WF:RFD]] please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:40, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|talk]]) 00:57, 26 April 2026 (UTC) </bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == Is it OK to connect the implementation? == Hello! I recently applied for functioneer on [[WF:RFG]], and I was wondering whether I could connect the implementation for {{Z|Z34165}} despite its dependency {{Z|Z34149}} being currently unimplemented. That is <em>if</em> I get accepted. I am planning on implementing it based on [[wikt:module:bg-nominal]], but am still having trouble figuring it out for now. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:04, 26 April 2026 (UTC) == Past tense function == Is there a function like {{Z|Z26039}}, but for the past tense (e.g. "Leo Tolstoy <em>was</em> a writer.")? If not, I will create it myself, I just want to make sure there's not a duplicate. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:10, 26 April 2026 (UTC) : {{Done}} with {{Z|Z34224}}, but I have a few kinks to work out with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:35, 26 April 2026 (UTC) :: I need to create some other similar functions for the past tense, I have some ideas: ::* {{Z|Z26095}} ::* {{Z|Z32643}} ::* {{Z|Z28016}} ::* {{Z|Z26570}} ::* {{Z|Z33975}} ::* {{Z|Z27243}} ::* <ins>{{Z|Z26627}}</ins> ::* <ins>{{Z|Z27627}}</ins> ::* <ins>{{Z|Z27173}}</ins> ::* <ins>{{Z|Z29591}}</ins> :: :: Are there any I have missed? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:57, 26 April 2026 (UTC) :I think that here we are starting to walk on dangerous waters: what does past mean? Is it a recent o a far past? Does it have ripercussions on the present or not? Is it just a thing that happened once, many times or for a continuative period of time? :Consider that various languages distinguish between many different types of past. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:38, 26 April 2026 (UTC) :: {{re|Dv103}} That is a fair point... :: How do we go about solving this problem though? I don't think having every sentence on Abstract Wikipedia be "X is a Y" is a very good idea. :: Maybe we have different functions for all these variations of past you mentioned that just map into "X was a Y." in English? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 13:31, 26 April 2026 (UTC) :::To properly solve this problem, we should use a more complete abstract content representation model, like for example the proposal of [[Wikifunctions:Type proposals/Semantic unit|Semantic units]] (look at [[Wikifunctions:Type proposals/Semantic unit/Douglas Adams|the example]] to see how times could be handled). For now, since we're still stuck with single fragment generation functions (that I hope will be slowly replaced with the complete represenation model, when available), we could just restrict your function to a very specific meaning, like "subject was an instance of, for most of its existence" (which means for example that it could be used to say "Douglas Adams was a writer", but not "Abraham Lincoln was a president", since he only was a president for 4 years). Probably my definition is still too vague, and this is why we need to go beyond these fragment generating functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:47, 26 April 2026 (UTC) ::Nitpick... I don't like that it outputs a string instead of monolingual text. With {{Z|Z26039}} it's used so much that I think it's unfixable in that case beyond deprecating it if people care that much, but {{Z|Z34224}} doesn't even have any connected implementations yet. Consider it, maybe? ::Nitpick 2... {{Z|Z34227}} is missing a language parameter. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:08, 26 April 2026 (UTC) ::: I will consider that! ::: I just did that because that's what {{Z|Z26039}} does, so I assumed I should follow suit with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 26 April 2026 (UTC) == Legacy functions == If and when more robust methods of abstractly representing and generating linguistic content come around, and more efficient ways of creating abstract content are devised and implemented, I suspect that our current methods will require some form of deprecation. This is a significant source of concern for me in relation to WF and AW, questioning how prone our current methods of doing things are and eventually will be prone to obsolescence, and how it will be worked around when it comes. We have over 1 250 articles on AW presently, and these are rather all over the place. I suspect the maintenance burden from keeping these articles up to code will eventually, err, creep up on us, I suppose, and some kind of major refactoring will be necessary. We are definitely in a period of experimentation and whatnot right now but eventually, like with enwiki, some sort of structure and rigor will form and I suspect it will start to become rather boring for me... I, for one, very much enjoy experimenting with new and better ways to do things here. I don't personally mind changing things to use a new and better paradigm if need be, that sort of thing highly excites me, but of course there will be things that are left behind, and I suspect maybe bots will be employed to deal with this? A lot of Wikipedia sister sites seem to do that, e.g. going and fixing up use of deprecated templates. Considering the nature of Wikifunctions and Abstract Wikipedia I suspect certain maintenance tasks will be made simpler or even trivial by the typical uniformity of our implementations. I guess I am just concerned if Wikifunctions or Abstract Wikipedia will ever accrue its own kind of "technical debt" with how we are plowing through things presently, and if there is a plan for how we will eventually seek to mitigate that. Maybe too early to ask this question, but I am a notoriously anxious person, so I thought it wouldn't hurt to raise the question regardless... &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:30, 26 April 2026 (UTC) :I very much agree, thank you for expressing my position so well. {{ping|Immanuelle}} has been using an AI-generated tool (well, they haven't edited in a week, perhaps it's a break or perhaps they don't wish to contribute to the project any more) to create a bunch of articles en masse, which I have warned them multiple times is a bad idea (on top of evolving functions, all of the articles are one-sentence-per-paragraph, [[abstract:Q12184|like so]]). That's why I've been avoiding creating articles recently, I'd say I have a good fourth (no data to support, rough guess) of the comments on the wiki, yet less than a percentage of the article count (only three, including the [[abstract:Q319|first article]], though, so perhaps I'm the next [[w:Special:Permalink/908493298|office.bomis.com]]). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:41, 27 April 2026 (UTC) :: I feel that the overwhelming presence of these low-quality articles (which I admit I myself am [[abstract:Q1710970|guilty]]/[[abstract:Q7601858|of]]/[[abstract:Q39338|creating]], usually as testbeds) may incur a large maintenance burden. I do expect them to be easy to detect, however, as searching for the presence of "deprecated" NLG functions is trivial, and it is possible that replacing them with their future ''even abstracter&trade;'' counterparts could be done automatically since they all have the same signatures and can be expected to create the same form of sentence. If it needs to be done manually for a while or for certain delinquent instances, my hope is that it will be fun, at least for a while. :: I just hope that these hypothetical future waves of "this new and versatile way of abstractly representing linguistic content" obsoleting previous methods and requiring refactoring across all articles is only a one-time thing. We should strive to be as robust and flexible as possible from the outset as each brand new paradigm of abstraction is also a brand new maintenance burden for updating old articles. At the end of the day, at least ''some'' of these articles will still render to many different languages even if their methods of creating those sentences of theirs is completely outdated. Ergo, the time it takes for the switchover to be performed across our articles should not be a persistent inconvenience for users (as, of course, they will always still be able to read the content as it was before since these legacy functions aren't being deleted outright), and the increased availability that the new methods will bring about will likely act as motivation for them to join the effort in refactoring (&#x300C;You're telling me that if I rewrite this article in this cool Lisp-looking stuff then I can probably read it in [[abstract:Q9307|Galician]]?? COOL!&#x300D;). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 20:26, 27 April 2026 (UTC) :::Totally agree. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:54, 28 April 2026 (UTC) :::My vague plan is to implement a default function returning an {{Z|Z89}}, for each language-neutral function. A single function would convert any of these to a {{Z|Z11}}, so that a composition of the two can be implemented as the current default until such time as the language-neutral function is ready to return a [[Z89]]. We can already convert a [[Z11]] to a [[Z89]] so, although there is more to be done in this space, existing language-specific functions could be adapted to return a [[Z89]] quite mechanistically. :::Although we certainly could deliver parallel Z89 functions for each existing Z11 function, I don’t think we should assume that particular outcome. Provided the Z89 captures a lang attribute from the Z11’s language tag, the two representations should be largely interchangeable, although I am expecting a Z89 to carry additional attributes at the span level that would be lost on conversion to a Z11 (along with any higher-level tags and attributes). :::When I say there is “more to be done in this space”, I am referring to a new type that would allow HTML fragments to be represented as tractable Wikifunctions objects, but this is currently drafted only in my head! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:21, 29 April 2026 (UTC) == Filtering types of objects == Hello! I have tried to comb through my own edit history several times, but it's really hard to search for specifics because there's no differentiation between different types of objects (functions, implementations, tests, etc.) in the logs as far as I can tell. Am I missing anything? I want it to work sort of like how filtering by namespace works. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 27 April 2026 (UTC) :There is differentiation, it's just rather hard to look through. Since all ZObjects are just JSON data at their core, you can search for instances of <code>{ "Z1K1": "Z[type]"</code>. I haven't tried this so I'm not sure how well it would work and I know MediaWiki search syntax treats quotation marks as a special character, but I have seen Wikifunctions pages link to searches using this before. There is also [[Special:ListObjectsByType]] but it is sitewide rather than specific to your edit history in particular. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:59, 27 April 2026 (UTC) ::''[It doesn’t help directly here, but please see [[WF:Find]] for more details of how this works.]'' [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:24, 29 April 2026 (UTC) :See the feature requests [[phab:T399244]]/[[phab:T373735]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 06:06, 28 April 2026 (UTC) :The lack of filtering edits by namespace is exactly the problem that I was trying to solve with the [[User:Amire80/wikifunctionsanalytics]] tool. :I even kind of succeeded, but it has two major problems: :# It doesn't have any real frontend, so you have to know some SQL to use it (or ask other people who know SQL). :# It doesn't get information from the live site, but from the dump, which appears to be updated once a month. :I've made a [https://quarry.wmcloud.org/query/104794 sample query for you]. Unfortunately, it won't do anything at the moment because of the second problem—your edits started in April 2026, which isn't over yet, so the dump for it hasn't been processed. But I hope that early in May you'll be able to use the same query and see something useful. :(I plan to add support for recent edits, but I haven't done it yet. Now that I more or less figured out how to process Wikifunctions edits, I'm focused on trying to understand Abstract Wikipedia edits. Processing up-to-date edits from both sites will possibly be the next thing I work on, but if you know some Python and want to try doing it yourself, don't wait for me—[https://gitlab.wikimedia.org/toolforge-repos/wikifunctions-analytics Patches welcome].) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:51, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]], I've just updated the data until the end of April. Now the query to which I linked above gives some results. You can also try running other queries if you know SQL. (Or try asking for other queries if you don't.) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:26, 3 May 2026 (UTC) == [[Z34213]] == I'm not quite sure why this implementation is failing. Could someone take a look? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:24, 28 April 2026 (UTC) :I've [https://phabricator.wikimedia.org/T419933#11863997 notified] the team that this is still occurring, the issue was marked as resolved. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:52, 28 April 2026 (UTC) :Some useful tips: :* create more testcases: sometimes it is a random error, so try to see how consistent it is between testcases :* your implementation is very inefficient, since it fetches items and lexemes a lot of times. Ideally, each item and each lexeme should be only fetched once in all the execution tree. :[[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 06:06, 28 April 2026 (UTC) ::Caching (''should?'') means that the lexeme and item data are cached, so the call doesn't actually execute multiple times. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:51, 28 April 2026 (UTC) :::Are lexemes and items actually cached within the same function execution? Even if they are only partially fetched and/or fetched in bulk? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 17:54, 28 April 2026 (UTC) ::::I don't have any evidence to prove that it works but that's definitely A. what's supposed to happen and B. the ideal behavior. This happens because the Z680X functions can be cached just like any other. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 28 April 2026 (UTC) ::::It is unclear. In general, I believe identical branches are resolved only once in orchestration, but there is also independent caching of Wikidata fetches. ::::According to @[[User:DMartin (WMF)|DMartin (WMF)]] ([https://t.me/Wikifunctions/30374 on Telegram]): ::::<blockquote>Well, no. We have caching of Wikidata entities that have been retrieved, but not of the results of nested function calls. There is a proposal for doing this in the context of the V2 composition language, when it's a bit more mature, and it's regarded as a relatively high priority.</blockquote> ::::It’s hard to tell whether fetches in nested calls are, in fact, cached and available for other nested calls in the same call, since it is not generally the actual fetch that consumes the most resources. Rather (I believe), it is construction and transmission of the result object, which is currently repeated afresh in each nested call (unless it is in an identical branch). ::::I hope that’s clear, and I apologise in advance if it happens to be inaccurate! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 29 April 2026 (UTC) :::::Oh, I should clarify.  There is a lot of caching going on, in several different places.  Lexemes and items ''are'' cached by the orchestrator within the same function execution, even if they are only partially fetched and/or fetched in bulk.  When I said that we don't have caching of the results of nested function calls, I meant that's not happening in general, for all nested function calls in compositions.  But fetching of Wikidata entities gets special treatment, so yes, fetched content from Wikidata is cached, regardless if it was fetched by a top-level call or a nested call. :::::It is also true that the construction of a ZObject from the fetched JSON might happen more than once within the same function execution, depending on how a composition has been structured. However, the construction of the ZObject is actually very fast, compared to the elapsed time of getting the JSON from Wikidata. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 18:04, 1 May 2026 (UTC) == Question about cardinal numbers == I was about to edit {{Z|Z16435}} to add my function {{Z|Z34308}}, but I noticed that none of the other functions have a gender parameter. Should I create a new wrapper function "Bulgarian cardinal, neuter", or should I just remove the gender parameter and always return neuter? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:39, 28 April 2026 (UTC) :The “cardinal” functions should return the words used for “counting” numbers in the abstract. :We should consider converting them to return a {{Z|Z11}} rather than a {{Z|Z6}}. It may even be appropriate to return a {{Z|Z12}} to cater for language variants. Either way, I think that would be the approach to adopt for inflected forms, unless reference to specific lexeme-forms is required. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:52, 28 April 2026 (UTC) ::This. If a native of your language were to count up, which form would they be most likely to use? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:29, 28 April 2026 (UTC) ::: {{re|GrounderUK|Feeglgeef}} Thanks for both your input! ::: I relabeled the aforementioned function to {{Z|Z34308}}, and created a new wrapper function {{Z|Z34457}}. ::: Should I specify that my old function is a monolingual text in parentheses? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:26, 28 April 2026 (UTC) ::::You don't have to, unless you think that is something that would require distinction when viewing the function in a list of search results &c. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:36, 28 April 2026 (UTC) == Optional/nullable function parameters == Hello! Recently, I was informed that Wikifunctions has no optional/nullable function parameters as of now. Are there any future plans to support this, and/or workarounds? Maybe create a union type system like "{{Z|6}} or {{Z|23}}". <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 17:53, 28 April 2026 (UTC) :What I do for this is use an "is empty" function corresponding to the type of the parameter in an If statement. If it isn't empty, the function works as intended. Otherwise, it does something else. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:58, 28 April 2026 (UTC) :Unions are not a thing (yet) on Wikifunctions, but you can always define an argument of type {{Z|Z1}}, which means that all types are allowed (I already did this for {{Z|Z26737}}; note that it is still a ugly workaround, don't use it for high level functions). Also, note that usually on Wikifunctions we use {{Z|Z24}} as the null value. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:00, 28 April 2026 (UTC) :: {{re|JJPMaster|Dv103}} Thanks for your help! :: @[[User:Dv103|Dv103]] told me a function call with a missing parameter is treated as an invalid function call, so how does the "is empty" function work with that? :: Also, setting the type to {{Z|1}} seems naive, like setting the type as <code>any</code> in TypeScript... :: Related question: Are there plans to add default values to parameters (outside of "if empty")? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 18:19, 28 April 2026 (UTC) :::Setting the type to {{Z|Z1}} is actually naive, and that's why I advised you to only use it for low-level functions. Currently there is nothing better. Sometimes, type correctness is not actually checked, so it might seem that nullable types are possible. But it is still an hack, and it could broke anytime since it is not intended behavior. :::I don't think that there are current plans to add default values (but correct me if I'm wrong). The closest thing that comes to my mind is that, if you incorporate Wikifunctions into Wikitext, you can leave empty some fields (only of some specific types) and Parsoid will replace them to their default value. This is done only depending on the type, and not on the functions. For example, {{Z|Z6091}} and {{Z|Z6001}} are assigned the QID associated to the page, and {{Z|Z20420}} is assigned the current date. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:56, 28 April 2026 (UTC) :::@[[User:QuickQuokka|QuickQuokka]]: At the very least, [[Z10008]] accepts a null input. Maybe that feature is unique to the String type—I am not sure. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 19:10, 28 April 2026 (UTC) ::::I think it's just not checked, but it shouldn't be intended. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:20, 28 April 2026 (UTC) ::::Strings and typed lists can be “empty” in the sense that their length can be zero. Typed pairs may also be “empty” in a degenerate sense, but such an object will not be returned from a code implementation. A typed map with no entries will also fail to be returned from code, although it is fine in compositions. ::::For a genuinely optional parameter, I prefer a properly typed list, which at least encourages an argument of the correct type. {{Z|Z813}} is also typically faster than {{Z|Z10008}}. Quite a good example of this approach is {{Z|Z23723}}, where it helps to resolve the type union (using [[Z1]]) for both Z6003K1 and Z6003K3. Of course, there’s nothing to prevent more than one element in the list, but additional elements are easily ignored. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:55, 28 April 2026 (UTC) :Pinging {{ping|Jdforrester (WMF)|prefix=|p=}}, I believe there are no current plans. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:02, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]]: I'm afraid there are no current plans to build out optional params, indeed; we would be happy to review this if a compelling case was made, but it'd be a lot of work to re-build the [[Wikifunctions:Function model|function model]] with that support and ensure we don't break (too many) things. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:11, 28 April 2026 (UTC) == Z6830 for Chinese == I was trying to use {{Z|Z6830}} for implementation in the Chinese-language. And turns out most of the Lexeme on Wikidata is using [[d:Q727694]] as the language instead of [[d:Q7850]]. This makes it impossible to use the mentioned function above, since Standard Chinese is not available (or did I miss something?). Is there a way to fetch lexemes with language=[[d:Q727694]] from item? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:20, 30 April 2026 (UTC) :@[[User:Sun8908|Sun8908]] There is [[Z1006]] for Chinese and it has the language code zh. There is an overview of languages in [[Module:Wikifunctions label]] so you can search there for chinese versions and choose the one you need. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 5 May 2026 (UTC) ::I know that. The problem is when using the function [[Z6830]], it cannot retrieve lexeme with language [[d:Q727694]] (but it is the "Chinese language" with the most current Wikidata lexemes, see [https://ordia.toolforge.org/language/ ordia]). I think it should be a Wikidata problem, I might fix it (possibly by creating the same lexemes with language code zh) on Wikidata. Thanks anyway. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 05:39, 6 May 2026 (UTC) :Could you provide an example of a Chinese lexeme that has a linked Wikidata item, or a Z6830 function call that fails to find such a lexeme where one exists? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 07:55, 6 May 2026 (UTC) ::Here: [[d:Lexeme:L846083]]. I think that's a primary reason of me trying to look into this problem, as the label in zh for [[d:Q6256]] (country) is not a single phrase (see its talk page on WD for more information). This makes some Abstract Wikipedia articles very weird in Chinese when {{Z|Z26570}} is used, so lexeme could potentially fix that. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 10:33, 6 May 2026 (UTC) :::Thank you. It looks as though {{Z|Z6830}} [https://www.wikifunctions.org/view/en/Z6830?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z6830%22%2C%22Z6830K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q6256%22%7D%2C%22Z6830K2%22%3A%7B%22Z1K1%22%3A%22Z6092%22%2C%22Z6092K1%22%3A%22P5137%22%7D%2C%22Z6830K3%22%3A%7B%22Z1K1%22%3A%22Z60%22%2C%22Z60K1%22%3A%22cmn%22%2C%22Z60K2%22%3A%5B%22Z6%22%5D%7D%7D returns that lexeme for language tag "cmn"]. Perhaps that tag should be added into the helpers for {{Z|Z24144}}? If it is widely used for lexemes, perhaps it should have its own {{Z|Z60}}? In any event, improvements might be considered under [[:phab:T390563]] (or otherwise), including amending [[Z6830]] to also consider "cmn" (and "zho", "chi"…?) when requests are made for "zh-hans" or "zho-hant" (or others?) @[[User:Winston Sung|Winston Sung]] @[[User:DMartin (WMF)|DMartin (WMF)]] [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:22, 6 May 2026 (UTC) ::::If you go to [[d:Special:NewLexeme]] and put in [[d:Q727694]] as the language, it is going to tell you it has an unrecognized language code. So I believe "cmn" should not be a {{Z|Z60}} by default? I also started [[d:Wikidata:Project_chat#Lexemes_with_language_Standard_Chinese_(Q727694)|a discussion on WD]] regarding this. I guess we can still use it as a fallback language though if possible. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 03:43, 7 May 2026 (UTC) ::::We don't have a separated <code>cmn</code> BCP 47 language subtag in MediaWiki and Wikidata at the moment. <code>zho</code> and <code>chi</code> are ISO 639 language codes but not BCP 47 language subtags. ::::For Modern Standard Mandarin, please use <code>zh-*</code> language tags for now. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 15:26, 8 May 2026 (UTC) == Key not found error == Is there a reason why I am getting key not found error for this [[Z34677|function]] {{Z|Z34677}}? All the underlying functions run and all the test cases work. The debug information does not give more details. Any pointers? Thanks in advance [[User:Jsamwrites|John Samuel]] 19:24, 1 May 2026 (UTC) :It was passing the [[Z6091]] to {{Z|34641}} when that takes a [[Z6001]]. I've fixed that, but there's some other problem with the logic, so I've left it disconnected. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 19:42, 1 May 2026 (UTC) ::@[[User:YoshiRulz|YoshiRulz]] Thanks a lot. [[User:Jsamwrites|John Samuel]] 20:21, 1 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, 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:21, 2 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=30325620 --> == Any formal process for deletion of pages == Does a formal process exist for the deletion of functions, implementations, and tests that includes a notification system for creators, analogous to Wikidata’s process, explaining the rationale behind the deletion (or proposal for deletion)? [[User:Jsamwrites|John Samuel]] 12:36, 3 May 2026 (UTC) :Does [[Wikifunctions:Requests for deletions]] work? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:00, 3 May 2026 (UTC) :Please see the discussion at [[Wikifunctions talk:Requests for deletions#Should we expect Objects' creators to get pinged on deletion proposals?]]. :As I see it, it is the proposer’s responsibility to consult appropriately before making a request and we expect our administrators to act only when satisfied that appropriate consultation has occurred. In many cases, no consultation is required. Administrators may delete their own contributions without making a request, but this is not a practice I would encourage. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:51, 3 May 2026 (UTC) == Implementation of rational number in JS doesn't match in Z19677 (Rational number) and Z28579 (RGBA colour) == In {{Z|19677}} it's <syntaxhighlight lang=js> { "K1": sign * numerator, "K2": denominator } </syntaxhighlight> but in {{Z|28579}} it's <syntaxhighlight lang=js> [ sign * numerator, denominator ] </syntaxhighlight> '''<span style="font-family:Iosevka,monospace">[[User:沈澄心|<span style="color:#9f3526">dring</span>]][[User talk:沈澄心|<span style="color:#534fa3">sim</span>]]</span>''' 05:15, 4 May 2026 (UTC) == Nested functions in compositions == I wish it will be easier to a add another function about a specific existing function in a function implementation based on a composition. When I write long functions in spreadsheets I usually stat with a small part and then I try to go further and after important steps I test if the output is as expected. I created [[Z34826]] to get the German gender specific occupation lexeme for a specific person based on their gender. I wanted to add a function around the existing one and it was not successful. It is not very easy to implement as it requires the possibily to move a part to another section but I think it can be helpful if it will be implemented. So far I spend more time as expected on the function. Describing it with words what the function needs to do is much easier than implementing it here in Wikifunctions. So I think there needs to be improvement to make Wikifunctions more accessible. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:10, 5 May 2026 (UTC) :Have you tried to use the copy-paste functionality? It is very useful to move parts of composition arounn. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 07:12, 6 May 2026 (UTC) :I've also found the composition editor to be wholly unsuitable for any expressions more than a few levels deep. (Even with the <code>localStorage</code> clipboard, because of its overzealous type checks.) Compositions naturally grow out from the "leaves", the immediate operations on the inputs, while the interface really wants you to build from the "root". I mostly use the [https://yoshirulz.gitlab.io/WikiLambdaBlockly drag-and-drop block editor] which I made to smooth over some of the site's problems, so if you want to try that out and give me some feedback I'd appreciate it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 14:36, 6 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the 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 [[: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/1778520600 May 11, 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]]) 11:16, 8 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=30325620 --> == RGBA colour, spelling... == Something that has always irked me a little bit is the spelling of [[Z28579|RGBA colour (Z28579)]]. I guess this is not unsurprising for me considering my use of US English but I think there is more to it than preference and I want to try to argue for it being changed to use American spelling. I know that this probably has a snowball's chance in hell of actually garnering any support, so I won't really be miffed if the spelling remains as it is, but I thought it wouldn't hurt to raise this regardless. The main issue I have with it is the spelling of the original proposal. When infernostars raised the [[Wikifunctions:Type proposals/RGBA color|type proposal]], the spelling was 「RGBA color」. Of the comments that mentioned the word 「colo[u]r」, two used British spelling while six used the American spelling as used in the proposal. The only thing that really pointed to the use of ''colour'' was the fact that the catalog page on color functions used that spelling already. For all intents and purposes, the spelling of the original proposal should have been maintained, but it was not; [[User:DVrandecic (WMF)|DVrandecic]], the eventual creator of the type, used a different spelling. It should be noted that there was really no reason for this to occur and while it is an undoubtedly minor issue I still believe it should be rolled back and the type should use the spelling of the original proposal and majority of editor comments. In [[abstract:Q936|OpenStreetMap]], there have been keyvalue proposals that have had the finalized spelling that gets put to use be in British English despite the original proposal being in American English; this has usually occurred with proposals relating to 「X center/centre」 tags. This makes sense on the surface, because OpenStreetMap is maintained by a UK organization, and still has close ties to Europe. The Wikimedia Foundation, however, is an ''American'' company. This is often brought up as a fallible argument when debating article spelling on the English Wikipedia, and I don't bring it up to support that 「RGBA color」 should be used for that exact reason, but rather to state that OpenStreetMap's general policy on tag names need not apply here. It appears to me that, at least initially, the majority of 「core contributors」 to Wikifunctions used British English; I can name YoshiRulz, 99of9, GrounderUK, and VIGNERON.<ref group="color">I'm avoiding linking to these folks because I don't think pinging them about this discussion is all too necessary unless they themselves want to be involved; I don't want to clutter their inboxes just to briefly mention them. I pinged Denny because, well, I'm asking him a question directly, but everyone else I would prefer to join this discussion by their own accord... not that I wish for this decision to be confused as me going 「these people use British English so they will probably oppose my idea, I won't invite them to the discussion because of that」...no, I promise you that is not the reason.</ref> I see (or saw) these people ''everywhere'', so it makes sense that British English has prevailed in some sorts on this website, but I don't think that indicates that it should be the ''preferred'' spelling across the website, at least not to the point where a proposal should have its name changed to match such a "consensus".<ref group="color">It could be argued that the front-and-center ''Function catalogue'' using 「catalogue」 is actually indicative of such a "consensus", but ''catalogue'' is in a similar position to the word ''grey'' where I live (that is, the US) in that it is used just as often as its American counterpart. Also, consider Wiktionary's ''Beer parlour'' project chat.</ref> The unnecessary modification of the original spelling is my main argument for changing it back... but of course, I must obligatorily state that on English Wikipedia, it is [[w:Color|Color]] and [[w:RGBA color model|RGBA color model]]; on Wikidata, it is [[d:Q1075|color]] and [[d:Q2325624|RGBA color space]]; in CSS (which typically uses hexadecimal triplets to specify RGBA values), the properties are <code>color</code>, <code>background-color</code>, etc.; bit of a weak jab, but on Schema.org it is [https://schema.org/color color], [https://schema.org/colorSwatch colorSwatch]; et cetera. {{Z|Z28580}} uses ''color'', so does {{Z|Z28591}} and its Python counterpart. Mr. Vrandečić, I have to ask, I'm rather confused... you created the color type using British English spelling, but you were also responsible for the creation of the equality function which uses the American English spelling. You also seem to be writing in American English for the status updates, judging by your use of -''ize'' over -''ise'' endings and use of ''program'' over ''programme'' in [[Wikifunctions:Status updates/2026-04-16]]. Is there something I'm missing or have you switched your preferred variant somewhere along the way? Anyways, do consider this if you wish... again, I don't suppose this will garner much support, it is the ''non-issuest'' of ''non-issues'', but it has irked me to the point where I want to ask about it to get some answers, if nothing else. I am not arguing for every other color function to have its name changed, just the type itself. <references group="color"></references> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 8 May 2026 (UTC) :This is a multilingual project; the <code>en</code> label is <code>RGBA colour</code> and the <code>en-us</code> label is <code>RGBA color</code>. Though I'm not able to switch to <code>en-us</code> via the language picker so that would need to be fixed.<!-- --><br>edit after reading your whole comment: The same is true of {{Q|1075}}, there are labels specified for multiple English variants. (In {{Q|2325624}} it's only an alias.) I agree that other websites' choices aren't binding on us, but from that, I conclude that the more widespread British/Commonwealth spellings should be used for the generic <code>en</code>. As for myself, I'm Aussie and I will continue to use the BrE spellings ([[w:en:Oxford_spelling#Language_tag_comparison|+ "routing"]], TIL) if only by muscle memory.<!-- --><br>[[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 17:42, 8 May 2026 (UTC) :: Your lattermost point would normally be fine in a perfect world. Wikipedia's <code>convert</code> function defaults to "international" English, which I don't personally take issue with because it happens that we here in America are actually outliers for saying and spelling things differently... err, or we were for a while at least, nowadays it seems like an even split (plus you have "yield" vs. "give way" which is effectively the logical opposite of US's use of "meter" over "metre"). :: However, this is not a perfect world, and I don't think <code>en</code> should correspond to any particular variant. It is too fragmented across all software at this point to impose such a requirement. The inability to switch to <code>en-us</code> on this website foregoes an easy and simple solution to this problem that makes everyone happy, because the yanks (such as myself) can't be happy because we can't see the labels in American English even if we wanted to, and the other folk can't switch either as far as I'm aware (and the en-CA and en-GB languages in the preferences page seems to be deprecated). My point being, <code>en</code> is abused to mean "en-UK" just as often as it is abused to mean <code>en-US</code>; I think a decision shouldn't be made on such an assumption of one "default". &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:48, 12 May 2026 (UTC) :Hi @[[User:Theki|rae]]! I have no opinion nor preference on this, and given my background, I am just entirely confused about my spelling preferences myself, as you can tell from my inconsistent usage. I learned British English in school and used that for maybe two decades or so, but moved to the US and lived there for more than a decade, enough to be naturalized, but now I am back in Europe and I am technically a professor at King's College London, soooo.... honestly, I do not know. I don't remember having put too much thought into it at the moment I created it. The good thing is that in Wikifunctions, just as in Wikidata, it is easy to change, without messing things up too much (unlike in Wikipedia), so my suggestion is, just make the change, see if anyone complains, and if they do, discuss it more. I don't know if there is a guideline already in Wikifunctions about the variants. I am happy either way, and honestly, I keep forgetting which variant is which most of the time. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 18:16, 10 May 2026 (UTC) :: I can definitely understand this, although I am unfortunately rather passionate about any minutiae involving preferential minor differences in ''anything'', of which AmE vs. BrE chiefly is. So I dedicate a lot of headspace to it. More than I should. Not that I wish to imply that the comment above that I have wrote is of an irrational nature, or done out of spite or pure emotion and subjectivity; I do genuinely believe that ''RGBA color'' is beyond just a personal preference and is just logical. I may boldly go and change it, but for some reason I was expecting that changing the English label of a Type would require elevated permissions, and I also didn't want to do it only to get immediately reverted because it ''did'' strike a chord with someone, when I could instead see how apathetic, supportive, or in opposition interested people are beforehand and ''then'' act accordingly. I was not meaning to antagonize you over your spelling habits, I did actually use British English for a few years starting in 2020 before I went back to American English, so I'd be a hypocrite for me to decry you for not always sticking to some arbitrary standard of spelling words over the other. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:55, 12 May 2026 (UTC) :Although I spell it “colour”, I think it makes more sense to use “color” for the type, since that is almost always the required spelling when the string functions as a keyword. :More generally, though, Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en". This is unusual, in my experience, as "en" is widely misused in place of "en-US", where there are recorded spelling differences. :(I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere. Use of -ize rather than -ise is a matter of personal preference or house style, but regional autocorrect encourages -ise.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:00, 12 May 2026 (UTC) :: ''Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en"'' :: Definitely agreeing with you on the latter being a good choice. However, I suspect the favoring of "colour" over "color" may be because, in terms of language codes, when sorted alphabetically <code>en-us</code> actually comes ''after'' <code>en-gb</code>. Although, the frontend seems to be sorting <code>en-ca</code> after <code>en-gb</code>, so I don't actually know how correct that is. :: ''I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere'' :: The context of the spelling was "''No program for the NLG SIG meeting for next Tuesday has been proposed''". In that usage context, I think it makes sense to assume that ''program'' is not being used to refer to a computer program, but to a ''program of events'' or similar, something that you would spell as a ''programme'' in British English. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 12 May 2026 (UTC) :{{s}} this. I'm obviously biased but I believe American English is preferable generally, American dominance on the internet (our Department of Defen'''s'''e invented it!) and rapidly-increasing consumption of American media by international English speakers means that more people use American English's conventions, this is clear through for example [http://trends.google.com/explore?q=color%2Ccolour&date=all&geo=Worldwide search trends] (though they aren't particularly reliable). Perhaps this is a bit of a supremacist opinion, but we should have internal consistency, and if we must choose, American English should be our first choice (then Indian and then British English) [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:10, 12 May 2026 (UTC) :: This is rather flawed reasoning, though. I think probably any given British or Indian person would not agree on using that as the reasoning for this, not that you are necessarily ''completely wrong'', but if this is not a good enough reason for English Wikipedia's (admittedly extremely flawed) ''ENGVAR'' policy then I don't think it's likely it will pass here either. :: Although of note is that [https://books.google.com/ngrams/graph?content=color%2Ccolour&year_start=1800&year_end=2022&corpus=en&smoothing=3&case_insensitive=true Google ngrams] agree with you, but "color" vs. "colour" is an eternal holy war that will not be won by demonstrating that more books use US spelling over Commonwealth spelling. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:44, 12 May 2026 (UTC) :::You're probably right that it's not very sound. I'm biased in that other varieties of English irk me, and that's probably mutual for people who are used to other varieties of English when they read what I write! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:56, 12 May 2026 (UTC) :I've decided to boldly [[Special:Permalink/274271|make the change]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:02, 12 May 2026 (UTC) :: Thank you. Considering both you and GrounderUK seem to consider it an okay change, I think this will do for now. :: I should note that the matter of whether to move [[Wikifunctions:Catalogue/Colour functions]] in response to this (however this discussion will ultimately turn out) is a whole other can of worms, in my view. I can't say I have an opinion on that at the moment, but I'm putting it out there regardless. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:06, 12 May 2026 (UTC) :::Personally, I'm in favor of moving the page and renaming all of the items on it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:10, 12 May 2026 (UTC) ::I don't like this (exactly because of the American hegemony you cited), but again, it shouldn't matter because the software is meant to be multilingual. Clearly there's a bug preventing you from picking an English variant/dialect as your display language. But the search bar and Function/Type autocompletion do check the English variants for matches. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 15:15, 12 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[abstract:User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:31, 11 May 2026 (UTC) :Thank you for dedicating your time to writing this, it is very informative. I will try to add input once I'm not in over my head with finals. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:27, 12 May 2026 (UTC) == Display function for HTML fragment == Currently, any collapsed Z89 literal appears as<blockquote>&lt;&gt; [[Z89|HTML fragment]]</blockquote>If I were to create a new Function which returned something like<blockquote>&lt;&gt; 123-byte HTML fragment <q><nowiki><td><span lang=</nowiki>&hellip;</q></blockquote>could that be connected to replace the collapsed form, or would it require changes to the Wikilambda software? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 16:14, 11 May 2026 (UTC) :It might work, but I doubt it. Those angled brackets suggest that the collapsed form is not simply defaulting to the type’s label. Looking at [[:phab:T410509]], I’ve concluded that enhancements to the collapsed form were never considered, rather than being actively rejected. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:12, 12 May 2026 (UTC) ::[[:Phab:T391985]] documents the original design. Note the fifth bullet point under “Acceptance criteria”. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:21, 12 May 2026 (UTC) :I'm not sure the byte-size is necessary, but the outer tag (or first outer tag, though generally I'd prefer most fragments use a wrapper tag if it needs multiple like JSX does, but that's a whole different topic) would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:51, 12 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in 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]]) 14:36, 15 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 --> == [[Z34510]] == This function, which determines if a Wikidata item for a {{q|5}} has an undeprecated {{p|21}} statement of {{q|6581097}}, returns false for {{q|173399}}, a transgender man. This is because his item assigns his P21 statement to {{q|2449503}}, not {{q|6581097}}. I'm not sure how to account for this discrepancy. Should {{z|34510}}: # Include {{q|2449503}} as a value that can lead to a true result, # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a man?") could return true for either "male" or "trans man", # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a trans man?") could return true for "trans man", # Not exist at all? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:48, 16 May 2026 (UTC) :I can't think of a single use case where you would need to determine if a person is a cisgender man and nothing else. Functions are good for generalizing across multiple possibilities when they exist, so I think it would be best if trans men were considered a part of the criteria for returning a true value. If asking for specifically {{q|6581097}}s and ''nothing'' else was desired then the function name would be a misnomer as Elliot Page is inarguably a male (at least in the view of most reasonable and intelligent people). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:03, 16 May 2026 (UTC) :You made the function in the first place; what were you planning on using it for? AW? Maybe it should return a {{Z|25501}} which can then be passed on to other NLG functions. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 May 2026 (UTC) == Lexeme from wikidata label, or "best" lexeme from wikidata item == I was looking into fixing [[Z28028]]. I found that I could add "requires grammatical feature: definite article" to "United Kingdom" (L8558). Now I'm stuck on how to get to that lexeme from {{Q|145}}. There's [[Z23471]], but that for very good reason gives you multiple lexemes with the same sense, and I just want the best one like how the label is always the best string. Is there a function that can do this? There's definitely the case of a Wikidata label that isn't a lexeme (most commonly multiple lexemes) but I'm only considering the case where it is one lexeme here. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:02, 16 May 2026 (UTC) :There is {{Z|Z27327}}, that tries to give the best lexeme through various heuristics. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 22:22, 16 May 2026 (UTC) iheecjg7rownhfciwh60d7xri2y7ajf 275588 275574 2026-05-17T00:25:29Z Aaron Liu 2395 /* Lexeme from wikidata label, or "best" lexeme from wikidata item */ reply to Dv103 ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]]) 275588 wikitext text/x-wiki {{shortcut|[[WF:CHAT]]|[[WF:PC]]|[[WF:VP]]}} __NEWSECTIONLINK__ [[Category:Help]] <!-- please do not remove this line --> Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc. Other places to find help: * [[Wikifunctions:Administrators' noticeboard]] * [[Wikifunctions:Report a technical problem]] * [[Wikifunctions:FAQ]] {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |timeout=30 }} {{Archives|{{#tag:div|<br />{{Flatlist|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1|hideredirects=1}} |class=mw-collapsible-content|style=font-size:92%;}}|class="mw-collapsible mw-collapsible-toggle mw-collapsed"}} |prefix=WF:Project chat/Archive/ }} == "language" argument for certain functions == Hello. I am relatively new to Wikifunctions. Recently, I tried to create functions for Chinese translation of {{Z|Z26570}} and {{Z|Z26095}} (which became [[Z32788]] and [[Z32900]]). During the creation of these functions, I was trying to take {{Z|Z32212}} as reference. And I realized that the defining role sentence function is taking <code>language</code> as an argument (and the test case of the Chinese-language function already contains two varieties of Chinese). This makes it possible to output monolingual text in <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code>, or any varieties of the language. I think for this reason, it is better to have <code>language</code> as arguments for the implementation of Z26570 and Z26095, and potentially more functions that require {{Z|Z14294}}, since it would output the varieties code instead of just saying <code>zh</code> for <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code> in the output of type {{Z|Z11}}. I am not sure how the fallback mechanism works if one of the language (varieties) do not have a labels/lexemes, but to me, it is reasonable to have a <code>language</code> argument. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 09:38, 31 March 2026 (UTC) :The functions you mention do have a language argument. For Wikifunctions, the {{Z|Z60}} can be at a higher or lower level; whether a {{Z|Z11}} is for a language or a variant is determined by the function that constructs it. Please see {{Z|Z26565}} for an example and feel free to add test cases in Chinese. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:54, 11 April 2026 (UTC) ::Hello @[[User:GrounderUK|GrounderUK]], thanks for the answer. I understand that whether {{Z|Z11}} is for a language or a variant depends on the function. But that is exactly what I am asking for. It is true that [[Z26570]] and [[Z26095]] takes [[Z60]] as argument, but the language-specific functions in {{Z|Z29843}} and {{Z|Z26096}} don't. ::Let me give you an example: INPUT to [[Z26570]]: <code>entity</code>: Tokyo, <code>class</code>: city, <code>location</code>: Japan, <code>language</code>: zh-cn, the config would select [[Z33030]] (created after my previous comment by elseone) as the implementation, and it would RETURN 东京是日本的一个城市。(zh-hans), which is not zh-cn as requested in the INPUT. It would also be using the term not for the variant (when it is different) because it is hardcoded to use the term in zh-hans. However, if we have the implementation like [[Z32790]] (which was created by me but a natural language argument was added by elseone) or [[Z32213]] (that works in the defining role sentence function because of the extra argument), it could cater for different variant. ::If we don't have the language argument in the language-specific function, the desire for article creation on Abstract Wikipedia would be to create a function for every variant. Is it then better to create functions for every variant? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:18, 11 April 2026 (UTC) :::I forgot to mention that there are some hardcoding in {{Z|Z32790}} as well, but I cannot fix it because it is a connected function and I am not a functioneer. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:31, 11 April 2026 (UTC) ::::Okay, I think it’s safe to disconnect this one as the function is not yet configured for use on Abstract Wikipedia. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:04, 11 April 2026 (UTC) :::Ah, sorry… I misunderstood you. I agree that the called function should be able to accept the original language argument. That is simpler in theory than in practice, because the configured functions all have to have the same argument types, as I understand it. I’m not sure which the best approach is, really, but we probably want to avoid two levels of configuration. That suggests that all language-specific functions would need to accept the additional argument, which is unrewarding work for someone. @[[User:99of9|99of9]], @[[User:Jdforrester (WMF)|Jdforrester (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]] Any thoughts? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:57, 11 April 2026 (UTC) ::::I mean, we would need to modify all the functions in each language, which could take some time. But we are still in an early stage. If we don't fix it now and we want to fix it later, it would be a disaster. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 19:25, 11 April 2026 (UTC) :::::Agreed. And we probably want them converted to HTML too, with separate language spans for text in different languages. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:35, 11 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]: This sounds like a reasonable change to make. Note that (given these Functions are primarily for use on Abstract Wikipedia), altering/replacing them to return Z89/HTML fragments is already a desired but breaking change, so making a second breaking change at the same time is probably easiest for fixing things swiftly. That said, that's of course a decision for the Abstract Wikipedia and Wikifunctions communities, not me! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:43, 12 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]@[[User:Sun8908|Sun8908]] to make it a non-breaking change, I've created {{Z|Z34039}} which allows a composition {{Z|Z34043}}. This way you can make functions which either need the specified variant or don't! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:52, 24 April 2026 (UTC) :I have now created {{Z|Z33465}}, which is an implementation of [[Z26570]]. Maybe we can migrate to use that function when more (language-specific) functions for it are ready? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:19, 14 April 2026 (UTC) == No place to ask to activate a function? == I just discovered the {{Z|Z11390}} function and decided to make an overarching language-selecting function for it. After some fiddling around and studying how {{Z|Z32321}} and its set works, I now have {{Z|Z33439}} which has a config object ({{Z|Z33441}}) that selects between the two preexisting language-specific versions I found (English and Malayalam) and the new one I created for my other native language, {{Z|Z33440}}. Except I can't get these to work, because, from what I understand, only [[Wikifunctions:Functioneers|functioneers]] can activate newly created functions and implementations? So where do I apply for the {{Z|Z33439}} and {{Z|Z33440}} functions to be activated? Perhaps we should have a place to ask for it, a la [[w:WP:NPP]] — call it [[Project:New Functions Patrol|New Functions Patrol]] if you will. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] ([[User talk:UndueMarmot|talk]]) 08:58, 14 April 2026 (UTC) :There's [[Wikifunctions:Community portal]] for this. By the way, {{Z|Z33445}} doesn't work because all the code must be inside the main function in Python code. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 09:19, 14 April 2026 (UTC) ::Huh. How could I have missed that? ::But anyway, I've moved the code in {{Z|Z33445}} into inside the main function block. ::Is there any reason why WF decided not to simply allow anyone to write functions? After all, that's how it works with wikitext templates, and these functions are fundamentally serving the same purposes as templates, just written in a different way. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 11:25, 14 April 2026 (UTC) :::I've fixed a couple of technical issues, but tests still fail. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:28, 14 April 2026 (UTC) ::::The tests pass now after some more changes to the code: [[Special:Diff/265232/cur]]. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 12:01, 14 April 2026 (UTC) :::::{{D|Connected}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:02, 14 April 2026 (UTC) :::I think it's a security issue, since Wikifunctions implementations could teoretically be malicious. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:29, 14 April 2026 (UTC) ::::This ^^^. We're very lenient, though, once you've created a few working functions you can apply for the right, per [[WF:Functioneer]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:26, 14 April 2026 (UTC) ::::That explanation [[phab:T343559#11421293|doesn't add up]]. A reason to limit ''connection powers'' to Functioneers might be to prevent vandalism, considering Functions can be used across wikis. But user-provided code is already being executed even without a Functioneer connecting it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 April 2026 (UTC) == Actual difference between {{Z|Z26039}} and {{Z|Z26095}} == What is the actual difference between these two functions? I ask, since it seems to me that the current distinction is more or less that the first one doesn't use an indefinite article in English, while the second does. Which is not a good distinction in a project that should be language neutral. This doubt emerged from my use of the first one in [[abstract:Q124441]], which @[[User:Hogü-456|Hogü-456]] made me notice that is probably wrong. My question is: why is it wrong? How could we clarify the difference? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:46, 19 April 2026 (UTC) :I think the difference is if there is an indefinite article like a or an before the subject or not. In German there can be cases where a definite article is necessary before the subject. I looked at the functions and before the object both times an article is mentioned. As it depends on the language and the word what is the correct function to use I hope it will be clarified and it is an example of the necessity to have a human with understanding in a specific language check it. I hope there will be longer functions what generate more content about a specific kind of item. Then it is necessary to write one such function per language and it can be then applied to several items. It still requires checks and so maybe it is better to write down what item category needs what kind of introduction sentence function for what language. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:05, 19 April 2026 (UTC) ::The point of these two functions (and of the entire Abstract Wikipedia project) is that they should be defined in a purely language-independent way, so that the translation to actual language can be done automatically. This is the reason why these functions have been renamed; I think that this attempt was not succesful, since meaning is still unclear. My proposal to clarify them would be to invoke the concept of [[w:specificity (linguistics)|specificity]]: {{Z|Z26039}} should be named "specific subject is instance of (string)", and should be used only when the QID of the subject uniquely identifies a single thing; {{Z|Z26095}} should instead be renamed in "non-specific subject is kind of (Monolingual text)", and should be used when the QID refers to a multitude of real life items, and we are specifying the class that all these item belong to. This clarification would not still be enough, since it doesn't explain how mass nouns are handled (is water a unique thing? Does {{Q|Q7802}} refer to a single piece of bread or to the entirety of bread, like water?). This problem is very tricky, since mass noun are language-specific and blurry the line between these two functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 20:58, 19 April 2026 (UTC) :Simply put, one corresponds to P31 and the other to P279. Paris is an {{Q|P31}} a {{Q|Q1549591}} :whereas a {{Q|Q1549591}} is a {{Q|P279}} (alias “kind of”) {{Q|Q515}}. Whether the Wikidata knowledge representation will be sufficient to resolve into fluent natural language representations in all languages is, of course, a crucial question. Where it is not, the Abstract Wikipedia knowledge representation will need to supplement the Wikidata content with additional details about the relation between the participants or the participants themselves, and these details should be language-neutral, to the extent that this is practicable. The item {{Q|Q124441}} has no [[:d:Q124441#P31|P31]] statements; it has only [[:d:Q124441#P279|P279]]s, including one relating it to {{Q|Q212920}}, which suggests {{Z|Z26095}} is the appropriate choice here even if the rendering in some languages is the same. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:52, 19 April 2026 (UTC) ::Thanks for explaining it. I think that I'll change the implementation of {{Z|Z26095}}, so that in Italian it produces more or less the same output of {{Z|Z26039}} (both with the definite article). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:24, 20 April 2026 (UTC) == Equivalent of Z6830 for lexemes == Is there an equivalent of {{Z|Z6830}} that enables retrieving all lexemes pointing to a particular lexeme using a specific property? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 21:06, 20 April 2026 (UTC) :There's {{Z|6831}} but I think that's slightly different again to what you're after. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 12:31, 21 April 2026 (UTC) ::Thanks for sharing that one, I did not know it existed. But you are right, it’s not quite what I am looking for. I want a function that would take a Wikidata property reference (like P5191, which is ‘derived from lexeme’) and a Wikidata lexeme reference, and return a list of lexemes that reference that lexeme using that property. [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 13:23, 21 April 2026 (UTC) == Storing huge datasets == It is not a necessity I suppose, but an idea came to me earlier to write a function that would give the corresponding [[en:Shavian alphabet|Shavian alphabet representation]] of an English word written with the Latin alphabet, or perhaps apply that operation to an entire sentence. However, just trying to guess as to what the IPA pronunciation of each word passed into it could be is is both not ideal (pronunciations obviously can and will vary widely between accents) and infeasible <s>(Wikidata lexemes don't really seem to account for pronunciation)</s>. It happens, though, that a comprehensive Shavian dictionary exists named the [https://readlex.pythonanywhere.com/ ''Read Lexicon''], which uses pronunciation and spelling similar to that used by the creator of the alphabet himself. This would be a good dataset to use in performing this translation in the function, but it appears that, all in all, the total size of the dictionary is [https://github.com/Shavian-info/readlex/blob/main/readlex.json ''nearly 26MB''] when formatted as JSON, which would certainly be larger when converted into a typed list. I am wondering if this will ever be feasible or admissible, or if there is really a way around this if importing such a large set of data is deemed impractical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 22:30, 20 April 2026 (UTC) :{{re|Theki}} "Wikidata lexemes don't really seem to account for pronunciation"" is patently untrue; not only does every Bokmål lexeme form have IPA attached to it (thanks to Jon Harald Søby), but there are lots of languages--including English--that have pronunciation information, whether through IPA or otherwise, indicated on their forms. The big issue of course is that adding this data is not always possible to perform efficiently--for instance, I'd love to have Yiddish pronunciation respellings from Paul Abelson's dictionary on as many English forms as possible, but this dictionary not being previously processed makes this difficult. The data set you have brought up, if a suitable reading of [[:m:Wikilegal/Lexicographical_Data]] allows it, could be added as {{P|7243}} statements on various English forms. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 23:20, 20 April 2026 (UTC) ::Well, sorry... I haven't witnessed these pronunciation statements before, I wasn't aware of their existence until you pointed it out. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 21 April 2026 (UTC) :I got 1,900,000 characters into [[Z33875]] before the UI gave up on me. I'm not sure what the limit is. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:21, 21 April 2026 (UTC) == Could not serialize input JS object: Number <small><small>[insert tested number here]</small></small> == I'm not one to throw my problems at others, but I have no idea how to fix this. Am implementing {{Z|Z24602}} in JavaScript, which requires returning a typed map. It now works for every type of value except numbers. Tried explicitly converting the numbers to float64, but either way it throws the error above. Would appreciate it if anyone could diagnose or fix the problem, as my knowledge of Wikifunctions is amateur at best. Thank you. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:32, 23 April 2026 (UTC) :The quick answer is that like some list-related functions, code implementations returning typed maps are not possible unless the type of the objects in the map is specified in the function signature (e.g. if it was a map from Strings to Natural numbers only). So unfortunately, I think you've chosen a function that is not really possible at the moment. There are a few ideas of how we might address this, but for the moment, work on something else. Sorry! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:21, 23 April 2026 (UTC) :Maybe explicitly using [[Z13518|natural numbers]] would work? I would try using <code>{ "Z1K1": "Z13518", "Z13518K1": "[number]" }</code> to represent numbers, perhaps, and seeing if that works. Of course, you would also probably have to adapt this for other types that cannot be serialized, and I'm not sure how easy that would be to generalize (assuming [[w:Don't repeat yourself|DRYness]] is desired). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:39, 23 April 2026 (UTC) == Help with creating a function for Abstract Wikipedia == Hello! I was inspired by {{Z|Z26570}} to create {{Z|Z33975}}, however I'm not sure how I add specific language implementations here. Can anybody help me? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 10:41, 23 April 2026 (UTC) : I think I figured it out, I created a new object with the language config type, added {{Z|Z14310}} to my implementation, and added a new function for English... At least I think that's how it works... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 13:16, 23 April 2026 (UTC) ::You have the right idea, as far as I know. I went ahead and connected the implementations you created as they appear to work fine for English, and added a test for {{Z|Z33975}} (which passes [[File:Twemoji 1f601.svg|24px]]). I also corrected an error you made on the config object where you appear to have accidentally connected English to {{Z|Z33975}} instead of {{Z|Z33977}}. Thank you for contributing! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 23 April 2026 (UTC) ::: {{re|Theki}} Thank you so much for you help! Could you please kindly also connect the implementations for {{Z|Z33986}} which I just made, which is going to be used for the Hebrew implementation of {{Z|Z33975}}. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:11, 23 April 2026 (UTC) ::::You seem to be returning the wrong type in both implementations. Functioneers should not connect implementations that don't work for non-functioneers. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:13, 23 April 2026 (UTC) ::::: {{re|Feeglgeef}} Oh thank you for pointing that out! I am still a bit new to this project and confused, so I need to read up some more about this. How do I return a monolingual text object? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:17, 23 April 2026 (UTC) ::::::I'm trying to fix it for you, the construction of ZObjects in code implementations is a bit difficult right now. Since the State origin using entity and class function will (presumably) be composition, perhaps {{Z|33975}} can be adjusted to return a string, using {{Z|26107}} and {{Z|26107}}? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:21, 23 April 2026 (UTC) :::::I did not notice any discrepancies from looking at the functions by themselves, and it seemed to work fine on my end. Is it bad practice for NLG functions to return the monolingual text type? I had assumed it was logical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:24, 23 April 2026 (UTC) ::::::Both implementations are failing all three tests on my end. No consensus has been established as to whether monolingual texts or strings should be used, so it's like the [[w:War of the currents|war of the currents]] but for Wikifunctions. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:27, 23 April 2026 (UTC) :::::::Oh, you were referring to {{Z|Z33986}}. I assumed you were stating that something was wrong in the earlier English functions that I missed; I apologize for the misunderstanding. Has there been any centralized discussion on this string vs. monolingual text issue? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:31, 23 April 2026 (UTC) ::::::::Not that I'm aware of, I've brought it up on the telegram twice before, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:49, 23 April 2026 (UTC) ::::::::The centralised discussion is at [[WT:Abstract Wikipedia/2025 fragment experiments#Proposed recommendation: Fragments should return Z11/monolingual strings]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:19, 24 April 2026 (UTC) ::::::: {{re|Theki|Feeglgeef}} Can only functioneers test implementations? For me I can't test it at all... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:32, 23 April 2026 (UTC) ::::::::AFAIK, test cases are only immediately testable during editing of a function if they are connected. This is one of my personal pain points with Wikifunctions, iterating on functions without exhaustive connected test cases makes debugging practically impossible for non-functioneers working on newly-created functions... I (or Feeglgeef) can quickly connect the tests you need for you if you want, although if they are not well-formed they may need to be disconnected again afterwards. Additionally, I could temporarily connect the implementation you are writing so that you can test it on the sidebar as you work, but I'm not sure if this is advisable. That functionality is also something that unfortunately only works when not disconnected. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:43, 23 April 2026 (UTC) :::::::::Yup, agree with you on all points, thanks. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:48, 23 April 2026 (UTC) == Please disconnect implementation == I think I've fixed my issue with {{Z|Z33986}}, but I can't edit an actively connected implementations with my rights. I must admit it is an AI-aided fix, I feel very strongly about disclosing that. Courtesy pinging [[User:Theki]] and [[User:Feeglgeef]]. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:51, 23 April 2026 (UTC) : Additionally, I think the JS might be working. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:52, 23 April 2026 (UTC) : Just to clarify, I mean disconnect the Python implementation please. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:53, 23 April 2026 (UTC) :{{Done}} I've disconnected the Python implementation. :I've also added a couple of tests. The rule is a bit more complicated than adding a maqaf before every character that is not a Hebrew letter. Unfortunately, I don't think I'll have time to fix the implementations any time soon. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:03, 23 April 2026 (UTC) :: Thank you! :: Also, for some reason I thought you put a maqaf before all gershayim, so thanks for correcting me. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:09, 23 April 2026 (UTC) :::No, that's not the rule. :::The rest of this reply is an [[:wikt:info-dump|infodump]], feel free to ignore it :) :::In [https://hebrew-academy.org.il/topic/hahlatot/punctuation/ the Academy's punctuation rules], the rule for adding a maqaf is written kind of badly: שמים מקף ברצף שיש בו שני סוגי גופנים, כגון אותיות ומספרים ("maqaf is added in a sequence in which there are two types of fonts, such as letters and numerals"). These are not different types of "fonts", but different types of characters, and I should email them about it. It gives the examples <span lang="he" dir="rtl">ה־12</span> and <span lang="he" dir="rtl">ב־DNA</span>. It doesn't say anything explicitly about quotation marks, but in other places on the same page, you have stuff like <span lang="he" dir="rtl">ב"הארץ"</span>, and from that I deduce that a maqaf is not needed before double quotes if there are Hebrew letters inside the double quotes. :::That said, a few people do think that there must be a maqaf before double quotes. I have a somewhat surprising example of somebody who always does it: translators of Scientology materials into Hebrew. At least that's what they did last time I looked at them, about ten years ago. Those people are certainly prolific, and they get points from me for consistency, but this not the prevalent standard. (And if I recall correctly, they use the minus and not the proper Hebrew maqaf, and they don't get any points from me for that!) :::Also, the name of the character is just "double quotes" and not "gershayim". Gershayim are mostly for abbreviations, although most people use the same character for them. I use ״ for gershayim, as do a few other nerds, but we're the minority. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:35, 23 April 2026 (UTC) :::: {{re|Amire80}} Yeah, "font" is a weird choice of wording here by the Academy...<br> I think I'll follow your guidance and not use a maqaf for quotes beginning with Hebrew letters. <br> I should also add more tests for different types of quotes, like straight (", '), curly (“, ”, ‘, ’), gershayim (״, ׳), including single quotes.<br> P.S. gotta deduct points from Scientology for being a cult but that's neither here nor there [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:49, 23 April 2026 (UTC) :::: {{re|Amire80}} Courtesy ping because I mistyped your username on the last message. Anyways I'm also gonna do that tomorrow because I'm tired now... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:50, 23 April 2026 (UTC) == Connect implementations == Hello! I'm done with the implementations of {{Z|Z33986}} both in JS and Python, and all tests pass. Pinging @[[User:Amire80|Amire80]] to check if all the tests I've added are alright. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 15:24, 24 April 2026 (UTC) :Connected. It's possible that some more changes will be needed, but it looks OK now. :Another little comment: It should be called "clitic" and not "prefix". [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:56, 24 April 2026 (UTC) : {{re|Amire80}} Thanks for your comment! Luckily labels are easy to edit, so I'll get to it. : Currently I'm working on Bulgarian {{z|Z34072}} and {{z|Z34084}}, along with other Bulgarian functions. After I'm finished with those I'll take your advice. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 16:01, 24 April 2026 (UTC) == Please connect my Bulgarian implementations == I recently created the following Bulgarian functions: * {{Z|Z34070}} (currently broken, I think because another function I built it upon is unimplemented) * {{Z|Z34088}} * {{Z|Z34105}} * {{Z|Z34072}} * {{Z|Z34084}} Can somebody please connect these functions, and perhaps suggest other functions I could localize? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:03, 24 April 2026 (UTC) : Specifically, [[Z34070]] is based on [[Z34072]] [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:05, 24 April 2026 (UTC) :{{done}} for everything that passes, [[Z34070]] still does not work after purging WF's cache, though. For future reference, please request on the [[WF:Community portal|community portal]] instead of the project chat. Thank you for your work! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:03, 24 April 2026 (UTC) :: {{re|Feeglgeef}} Thank you for your help! I will keep in mind to go to the [[project: community portal| community portal]] in future instead for this. :: I still don't understand why {{Z|Z34070}} fails... It's implementation is almost completely identical to [[Z30399]] from {{Z|Z30397}}, unless I messed something up... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:11, 24 April 2026 (UTC) :::{{done}} No, it was mostly just timing out. It is better to use selective fetches where possible. One case is failing to match the expected results, but at least it is returning something. For all I know, it might even be acceptable! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 20:35, 24 April 2026 (UTC) :::: {{re|GrounderUK}} Thank you so much for your help! The one failed case is with a definite article, so I feel like that might be fixed in the future... <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:43, 24 April 2026 (UTC) == Editor experience suggestions == I'm a bit frustrated with the editing experience on Wikifunctions, and I have suggestions based on pain points I've had contributing to this project: * Adding a wizard to create functions, implementations, and tests in one flow, somewhat like Wikimedia Commons' upload wizard * A sandbox for experimenting without changing mainspace functions, and maybe letting non-functioneers connect implementations ([[Project: Sandbox]] doesn't seem to fit this) * We could have functions for creation based on the sandbox, like how Wikipedia has articles for creation and edit requests, * Maybe even another test instance of Wikifunctions, like how Wikidata has [[testwikidata:|Test Wikidata]] I really like this project and I don't mean to whine, but it certainly has a lot of pain points both for technical and non-technical people. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:41, 24 April 2026 (UTC) : It's also really complicated to localize functions, so maybe we should add another wizard for that, where you can choose a language, and then create the new function with the aforementioned function wizard, and it just automatically adds it to the related language configuration object of the related function. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:48, 24 April 2026 (UTC) :# Sounds good to me. :# A sandbox available is [[Z10119]], though an extension-provided sandbox that allows you to manipulate the types, code, and tests easily without interfering with the mainspace would be nice. :# [[WF:Suggest a function|This page]] works to some extent, though it's too messy in my opinion. :# We used to have a "beta cluster" but it [[phab:rOMWC5f625c5846b5f779473fa32c9a02d87e59215dfa|got shut down]] just over a year ago because it was broken. :[[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:07, 24 April 2026 (UTC) == Language parameters in language-specific functions == I think that an effort should be made to give the different natural language options corresponding to different English dialects, Chinese scripts, etc. more of a use (I added the test {{Z|Z34119}} to {{Z|Z26095}} and unsurprisingly it fails). There are two main problems with this approach that I can identify: * If you ask the majority of these functions to make a sentence in British English, much of the time it will give you an output with missing words, because it does not fallback to English labels in the case of a British English label for that item missing. The same applies for every other English dialect, British English is just an example here. * Uninformed editors will probably see the presence of a language parameter on these functions, consider it redundant, and remove it. [[Special:Diff/268074|I have made this mistake before]]. In my opinion, in a perfect world, all of these language generation functions would output monolingual text, and if the user asks for American English text, then American English text is what they'll get. If the user asks for Japanese text in hiragana specifically, then that's what they'll get in return. This is not as high-priority as just rendering text in the language plainly in the first place, but it's something that I feel is still worth devoting some effort to. Right now switching functions to use this paradigm is difficult because, on the one hand, I don't know if consensus tends towards this direction being ideal or advisable, and I don't want to make changes like this without at least notifying the wider community. In addition, all tests break once a parameter is added or removed, and the function editor does not recognize the change in number of parameters and therefore you have to remove the function call, re-add it along with all of its parameters it had previously (which is a tedious cut-and-paste job), and then it will work again. This is something that you can do in five seconds by just adding a few lines of JSON to the test source, but this is not directly editable from the Web browser. This tedium is largely what's preventing me from doing this on a larger scale, besides asking for comments first. If anyone has any insights or comments on this, then that would be appreciated. If a reference of functions with and without the support for language variants is needed, of course [[WF:NLG]] can be perused, but I've also my own list cataloged at [[User:Theki/functions#language]]... Of course, this thread has many similarities to [[#"language" argument for certain functions|the one above]], but this concerns me going out and making this consistent across these NLG functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:09, 24 April 2026 (UTC) :I've created {{Z|Z34122}} as an extension to {{Z|Z34039}} for larger functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:34, 24 April 2026 (UTC) :Just to confirm that I, for one, support a Natural language parameter for all natural-language functions. The concern about getting them all aligned is just that we haven’t finally settled on {{Z|Z11}} being preferred to {{Z|Z89}} or some other type that conserves the text’s provenance, so we risk having to change them all again. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:07, 25 April 2026 (UTC) == “Key not found ()”? == What am I doing wrong in {{Z|Z34137}}? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 00:39, 25 April 2026 (UTC) :You were passing a [[Z6091]] to {{Z|32290}}, but it takes a [[Z6001]]. Fixed. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:10, 26 April 2026 (UTC) ::{{done|Thank you}}! [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 14:13, 26 April 2026 (UTC) == Why is my test failing? == Hello! I recently made {{Z|Z34139}} based on [[wikt:Module:bg-translit]], and the test case {{Z|Z34141}} is failing on both implementations, despite the expected output and actual output being the same as far as I can tell. I tried looking at the Unicode codepoints of the output, but those are also identical. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 06:21, 25 April 2026 (UTC) :Yes, it’s a tricky one. I’ve added a normalize step to the result validation in {{Z|Z34141}}, which confirms it is a normalization issue. It looks like it is in the code but I don’t know whether simply normalizing the result is the way to go. Logically, you would normalize both the input and the result. The implementations of {{Z|Z10384}} show you how to do this. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:41, 25 April 2026 (UTC) == Edit request == Hello! I have an edit request for {{Z|Z23752}} and {{Z|Z23414}}. Please replace all the "an/a" logic with <code>Z21739(Argument reference)</code>, both for readability and for more accuracy ("a university is an institution") <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:50, 25 April 2026 (UTC) :{{D}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:24, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #245 is out: The Foundation's search for the perfect language == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-25|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present an academic paper about Abstract Wikipedia, we discuss our latest Type created, and we take a look at the newest created functions. 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:54, 25 April 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=30325620 --> :@[[User:Sannita (WMF)|Sannita (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], technical meta-question: the newsletter quotes the article: ::the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016) :This quotation sounds sensible, but the article's [https://link.springer.com/article/10.1007/s00146-026-02899-w web version], and the PDF that is downloadable from the same page doesn't actually show the emojis. It rather shows text that looks lacking: ::the only way to contest its algorithm is to click or (Crawford and Gillespie [https://link.springer.com/article/10.1007/s00146-026-02899-w#ref-CR14 2016]) :Where did you get the emojis? Is it your (probably correct) guess or is there a version somewhere that actually shows the emojis? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:16, 25 April 2026 (UTC) ::Scratch that. I've found a version with correct emojis: https://wikihistories.github.io/wikilambda-the-ultimate/ [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:37, 25 April 2026 (UTC) == Requested deletion of test == Please delete {{Z|Z34143}}. this was never valid Bulgarian, I messed up. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:19, 25 April 2026 (UTC) :[[WF:RFD]] please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:40, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|talk]]) 00:57, 26 April 2026 (UTC) </bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == Is it OK to connect the implementation? == Hello! I recently applied for functioneer on [[WF:RFG]], and I was wondering whether I could connect the implementation for {{Z|Z34165}} despite its dependency {{Z|Z34149}} being currently unimplemented. That is <em>if</em> I get accepted. I am planning on implementing it based on [[wikt:module:bg-nominal]], but am still having trouble figuring it out for now. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:04, 26 April 2026 (UTC) == Past tense function == Is there a function like {{Z|Z26039}}, but for the past tense (e.g. "Leo Tolstoy <em>was</em> a writer.")? If not, I will create it myself, I just want to make sure there's not a duplicate. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:10, 26 April 2026 (UTC) : {{Done}} with {{Z|Z34224}}, but I have a few kinks to work out with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:35, 26 April 2026 (UTC) :: I need to create some other similar functions for the past tense, I have some ideas: ::* {{Z|Z26095}} ::* {{Z|Z32643}} ::* {{Z|Z28016}} ::* {{Z|Z26570}} ::* {{Z|Z33975}} ::* {{Z|Z27243}} ::* <ins>{{Z|Z26627}}</ins> ::* <ins>{{Z|Z27627}}</ins> ::* <ins>{{Z|Z27173}}</ins> ::* <ins>{{Z|Z29591}}</ins> :: :: Are there any I have missed? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:57, 26 April 2026 (UTC) :I think that here we are starting to walk on dangerous waters: what does past mean? Is it a recent o a far past? Does it have ripercussions on the present or not? Is it just a thing that happened once, many times or for a continuative period of time? :Consider that various languages distinguish between many different types of past. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:38, 26 April 2026 (UTC) :: {{re|Dv103}} That is a fair point... :: How do we go about solving this problem though? I don't think having every sentence on Abstract Wikipedia be "X is a Y" is a very good idea. :: Maybe we have different functions for all these variations of past you mentioned that just map into "X was a Y." in English? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 13:31, 26 April 2026 (UTC) :::To properly solve this problem, we should use a more complete abstract content representation model, like for example the proposal of [[Wikifunctions:Type proposals/Semantic unit|Semantic units]] (look at [[Wikifunctions:Type proposals/Semantic unit/Douglas Adams|the example]] to see how times could be handled). For now, since we're still stuck with single fragment generation functions (that I hope will be slowly replaced with the complete represenation model, when available), we could just restrict your function to a very specific meaning, like "subject was an instance of, for most of its existence" (which means for example that it could be used to say "Douglas Adams was a writer", but not "Abraham Lincoln was a president", since he only was a president for 4 years). Probably my definition is still too vague, and this is why we need to go beyond these fragment generating functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:47, 26 April 2026 (UTC) ::Nitpick... I don't like that it outputs a string instead of monolingual text. With {{Z|Z26039}} it's used so much that I think it's unfixable in that case beyond deprecating it if people care that much, but {{Z|Z34224}} doesn't even have any connected implementations yet. Consider it, maybe? ::Nitpick 2... {{Z|Z34227}} is missing a language parameter. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:08, 26 April 2026 (UTC) ::: I will consider that! ::: I just did that because that's what {{Z|Z26039}} does, so I assumed I should follow suit with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 26 April 2026 (UTC) == Legacy functions == If and when more robust methods of abstractly representing and generating linguistic content come around, and more efficient ways of creating abstract content are devised and implemented, I suspect that our current methods will require some form of deprecation. This is a significant source of concern for me in relation to WF and AW, questioning how prone our current methods of doing things are and eventually will be prone to obsolescence, and how it will be worked around when it comes. We have over 1 250 articles on AW presently, and these are rather all over the place. I suspect the maintenance burden from keeping these articles up to code will eventually, err, creep up on us, I suppose, and some kind of major refactoring will be necessary. We are definitely in a period of experimentation and whatnot right now but eventually, like with enwiki, some sort of structure and rigor will form and I suspect it will start to become rather boring for me... I, for one, very much enjoy experimenting with new and better ways to do things here. I don't personally mind changing things to use a new and better paradigm if need be, that sort of thing highly excites me, but of course there will be things that are left behind, and I suspect maybe bots will be employed to deal with this? A lot of Wikipedia sister sites seem to do that, e.g. going and fixing up use of deprecated templates. Considering the nature of Wikifunctions and Abstract Wikipedia I suspect certain maintenance tasks will be made simpler or even trivial by the typical uniformity of our implementations. I guess I am just concerned if Wikifunctions or Abstract Wikipedia will ever accrue its own kind of "technical debt" with how we are plowing through things presently, and if there is a plan for how we will eventually seek to mitigate that. Maybe too early to ask this question, but I am a notoriously anxious person, so I thought it wouldn't hurt to raise the question regardless... &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:30, 26 April 2026 (UTC) :I very much agree, thank you for expressing my position so well. {{ping|Immanuelle}} has been using an AI-generated tool (well, they haven't edited in a week, perhaps it's a break or perhaps they don't wish to contribute to the project any more) to create a bunch of articles en masse, which I have warned them multiple times is a bad idea (on top of evolving functions, all of the articles are one-sentence-per-paragraph, [[abstract:Q12184|like so]]). That's why I've been avoiding creating articles recently, I'd say I have a good fourth (no data to support, rough guess) of the comments on the wiki, yet less than a percentage of the article count (only three, including the [[abstract:Q319|first article]], though, so perhaps I'm the next [[w:Special:Permalink/908493298|office.bomis.com]]). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:41, 27 April 2026 (UTC) :: I feel that the overwhelming presence of these low-quality articles (which I admit I myself am [[abstract:Q1710970|guilty]]/[[abstract:Q7601858|of]]/[[abstract:Q39338|creating]], usually as testbeds) may incur a large maintenance burden. I do expect them to be easy to detect, however, as searching for the presence of "deprecated" NLG functions is trivial, and it is possible that replacing them with their future ''even abstracter&trade;'' counterparts could be done automatically since they all have the same signatures and can be expected to create the same form of sentence. If it needs to be done manually for a while or for certain delinquent instances, my hope is that it will be fun, at least for a while. :: I just hope that these hypothetical future waves of "this new and versatile way of abstractly representing linguistic content" obsoleting previous methods and requiring refactoring across all articles is only a one-time thing. We should strive to be as robust and flexible as possible from the outset as each brand new paradigm of abstraction is also a brand new maintenance burden for updating old articles. At the end of the day, at least ''some'' of these articles will still render to many different languages even if their methods of creating those sentences of theirs is completely outdated. Ergo, the time it takes for the switchover to be performed across our articles should not be a persistent inconvenience for users (as, of course, they will always still be able to read the content as it was before since these legacy functions aren't being deleted outright), and the increased availability that the new methods will bring about will likely act as motivation for them to join the effort in refactoring (&#x300C;You're telling me that if I rewrite this article in this cool Lisp-looking stuff then I can probably read it in [[abstract:Q9307|Galician]]?? COOL!&#x300D;). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 20:26, 27 April 2026 (UTC) :::Totally agree. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:54, 28 April 2026 (UTC) :::My vague plan is to implement a default function returning an {{Z|Z89}}, for each language-neutral function. A single function would convert any of these to a {{Z|Z11}}, so that a composition of the two can be implemented as the current default until such time as the language-neutral function is ready to return a [[Z89]]. We can already convert a [[Z11]] to a [[Z89]] so, although there is more to be done in this space, existing language-specific functions could be adapted to return a [[Z89]] quite mechanistically. :::Although we certainly could deliver parallel Z89 functions for each existing Z11 function, I don’t think we should assume that particular outcome. Provided the Z89 captures a lang attribute from the Z11’s language tag, the two representations should be largely interchangeable, although I am expecting a Z89 to carry additional attributes at the span level that would be lost on conversion to a Z11 (along with any higher-level tags and attributes). :::When I say there is “more to be done in this space”, I am referring to a new type that would allow HTML fragments to be represented as tractable Wikifunctions objects, but this is currently drafted only in my head! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:21, 29 April 2026 (UTC) == Filtering types of objects == Hello! I have tried to comb through my own edit history several times, but it's really hard to search for specifics because there's no differentiation between different types of objects (functions, implementations, tests, etc.) in the logs as far as I can tell. Am I missing anything? I want it to work sort of like how filtering by namespace works. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 27 April 2026 (UTC) :There is differentiation, it's just rather hard to look through. Since all ZObjects are just JSON data at their core, you can search for instances of <code>{ "Z1K1": "Z[type]"</code>. I haven't tried this so I'm not sure how well it would work and I know MediaWiki search syntax treats quotation marks as a special character, but I have seen Wikifunctions pages link to searches using this before. There is also [[Special:ListObjectsByType]] but it is sitewide rather than specific to your edit history in particular. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:59, 27 April 2026 (UTC) ::''[It doesn’t help directly here, but please see [[WF:Find]] for more details of how this works.]'' [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:24, 29 April 2026 (UTC) :See the feature requests [[phab:T399244]]/[[phab:T373735]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 06:06, 28 April 2026 (UTC) :The lack of filtering edits by namespace is exactly the problem that I was trying to solve with the [[User:Amire80/wikifunctionsanalytics]] tool. :I even kind of succeeded, but it has two major problems: :# It doesn't have any real frontend, so you have to know some SQL to use it (or ask other people who know SQL). :# It doesn't get information from the live site, but from the dump, which appears to be updated once a month. :I've made a [https://quarry.wmcloud.org/query/104794 sample query for you]. Unfortunately, it won't do anything at the moment because of the second problem—your edits started in April 2026, which isn't over yet, so the dump for it hasn't been processed. But I hope that early in May you'll be able to use the same query and see something useful. :(I plan to add support for recent edits, but I haven't done it yet. Now that I more or less figured out how to process Wikifunctions edits, I'm focused on trying to understand Abstract Wikipedia edits. Processing up-to-date edits from both sites will possibly be the next thing I work on, but if you know some Python and want to try doing it yourself, don't wait for me—[https://gitlab.wikimedia.org/toolforge-repos/wikifunctions-analytics Patches welcome].) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:51, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]], I've just updated the data until the end of April. Now the query to which I linked above gives some results. You can also try running other queries if you know SQL. (Or try asking for other queries if you don't.) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:26, 3 May 2026 (UTC) == [[Z34213]] == I'm not quite sure why this implementation is failing. Could someone take a look? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:24, 28 April 2026 (UTC) :I've [https://phabricator.wikimedia.org/T419933#11863997 notified] the team that this is still occurring, the issue was marked as resolved. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:52, 28 April 2026 (UTC) :Some useful tips: :* create more testcases: sometimes it is a random error, so try to see how consistent it is between testcases :* your implementation is very inefficient, since it fetches items and lexemes a lot of times. Ideally, each item and each lexeme should be only fetched once in all the execution tree. :[[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 06:06, 28 April 2026 (UTC) ::Caching (''should?'') means that the lexeme and item data are cached, so the call doesn't actually execute multiple times. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:51, 28 April 2026 (UTC) :::Are lexemes and items actually cached within the same function execution? Even if they are only partially fetched and/or fetched in bulk? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 17:54, 28 April 2026 (UTC) ::::I don't have any evidence to prove that it works but that's definitely A. what's supposed to happen and B. the ideal behavior. This happens because the Z680X functions can be cached just like any other. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 28 April 2026 (UTC) ::::It is unclear. In general, I believe identical branches are resolved only once in orchestration, but there is also independent caching of Wikidata fetches. ::::According to @[[User:DMartin (WMF)|DMartin (WMF)]] ([https://t.me/Wikifunctions/30374 on Telegram]): ::::<blockquote>Well, no. We have caching of Wikidata entities that have been retrieved, but not of the results of nested function calls. There is a proposal for doing this in the context of the V2 composition language, when it's a bit more mature, and it's regarded as a relatively high priority.</blockquote> ::::It’s hard to tell whether fetches in nested calls are, in fact, cached and available for other nested calls in the same call, since it is not generally the actual fetch that consumes the most resources. Rather (I believe), it is construction and transmission of the result object, which is currently repeated afresh in each nested call (unless it is in an identical branch). ::::I hope that’s clear, and I apologise in advance if it happens to be inaccurate! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 29 April 2026 (UTC) :::::Oh, I should clarify.  There is a lot of caching going on, in several different places.  Lexemes and items ''are'' cached by the orchestrator within the same function execution, even if they are only partially fetched and/or fetched in bulk.  When I said that we don't have caching of the results of nested function calls, I meant that's not happening in general, for all nested function calls in compositions.  But fetching of Wikidata entities gets special treatment, so yes, fetched content from Wikidata is cached, regardless if it was fetched by a top-level call or a nested call. :::::It is also true that the construction of a ZObject from the fetched JSON might happen more than once within the same function execution, depending on how a composition has been structured. However, the construction of the ZObject is actually very fast, compared to the elapsed time of getting the JSON from Wikidata. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 18:04, 1 May 2026 (UTC) == Question about cardinal numbers == I was about to edit {{Z|Z16435}} to add my function {{Z|Z34308}}, but I noticed that none of the other functions have a gender parameter. Should I create a new wrapper function "Bulgarian cardinal, neuter", or should I just remove the gender parameter and always return neuter? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:39, 28 April 2026 (UTC) :The “cardinal” functions should return the words used for “counting” numbers in the abstract. :We should consider converting them to return a {{Z|Z11}} rather than a {{Z|Z6}}. It may even be appropriate to return a {{Z|Z12}} to cater for language variants. Either way, I think that would be the approach to adopt for inflected forms, unless reference to specific lexeme-forms is required. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:52, 28 April 2026 (UTC) ::This. If a native of your language were to count up, which form would they be most likely to use? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:29, 28 April 2026 (UTC) ::: {{re|GrounderUK|Feeglgeef}} Thanks for both your input! ::: I relabeled the aforementioned function to {{Z|Z34308}}, and created a new wrapper function {{Z|Z34457}}. ::: Should I specify that my old function is a monolingual text in parentheses? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:26, 28 April 2026 (UTC) ::::You don't have to, unless you think that is something that would require distinction when viewing the function in a list of search results &c. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:36, 28 April 2026 (UTC) == Optional/nullable function parameters == Hello! Recently, I was informed that Wikifunctions has no optional/nullable function parameters as of now. Are there any future plans to support this, and/or workarounds? Maybe create a union type system like "{{Z|6}} or {{Z|23}}". <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 17:53, 28 April 2026 (UTC) :What I do for this is use an "is empty" function corresponding to the type of the parameter in an If statement. If it isn't empty, the function works as intended. Otherwise, it does something else. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:58, 28 April 2026 (UTC) :Unions are not a thing (yet) on Wikifunctions, but you can always define an argument of type {{Z|Z1}}, which means that all types are allowed (I already did this for {{Z|Z26737}}; note that it is still a ugly workaround, don't use it for high level functions). Also, note that usually on Wikifunctions we use {{Z|Z24}} as the null value. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:00, 28 April 2026 (UTC) :: {{re|JJPMaster|Dv103}} Thanks for your help! :: @[[User:Dv103|Dv103]] told me a function call with a missing parameter is treated as an invalid function call, so how does the "is empty" function work with that? :: Also, setting the type to {{Z|1}} seems naive, like setting the type as <code>any</code> in TypeScript... :: Related question: Are there plans to add default values to parameters (outside of "if empty")? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 18:19, 28 April 2026 (UTC) :::Setting the type to {{Z|Z1}} is actually naive, and that's why I advised you to only use it for low-level functions. Currently there is nothing better. Sometimes, type correctness is not actually checked, so it might seem that nullable types are possible. But it is still an hack, and it could broke anytime since it is not intended behavior. :::I don't think that there are current plans to add default values (but correct me if I'm wrong). The closest thing that comes to my mind is that, if you incorporate Wikifunctions into Wikitext, you can leave empty some fields (only of some specific types) and Parsoid will replace them to their default value. This is done only depending on the type, and not on the functions. For example, {{Z|Z6091}} and {{Z|Z6001}} are assigned the QID associated to the page, and {{Z|Z20420}} is assigned the current date. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:56, 28 April 2026 (UTC) :::@[[User:QuickQuokka|QuickQuokka]]: At the very least, [[Z10008]] accepts a null input. Maybe that feature is unique to the String type—I am not sure. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 19:10, 28 April 2026 (UTC) ::::I think it's just not checked, but it shouldn't be intended. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:20, 28 April 2026 (UTC) ::::Strings and typed lists can be “empty” in the sense that their length can be zero. Typed pairs may also be “empty” in a degenerate sense, but such an object will not be returned from a code implementation. A typed map with no entries will also fail to be returned from code, although it is fine in compositions. ::::For a genuinely optional parameter, I prefer a properly typed list, which at least encourages an argument of the correct type. {{Z|Z813}} is also typically faster than {{Z|Z10008}}. Quite a good example of this approach is {{Z|Z23723}}, where it helps to resolve the type union (using [[Z1]]) for both Z6003K1 and Z6003K3. Of course, there’s nothing to prevent more than one element in the list, but additional elements are easily ignored. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:55, 28 April 2026 (UTC) :Pinging {{ping|Jdforrester (WMF)|prefix=|p=}}, I believe there are no current plans. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:02, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]]: I'm afraid there are no current plans to build out optional params, indeed; we would be happy to review this if a compelling case was made, but it'd be a lot of work to re-build the [[Wikifunctions:Function model|function model]] with that support and ensure we don't break (too many) things. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:11, 28 April 2026 (UTC) == Z6830 for Chinese == I was trying to use {{Z|Z6830}} for implementation in the Chinese-language. And turns out most of the Lexeme on Wikidata is using [[d:Q727694]] as the language instead of [[d:Q7850]]. This makes it impossible to use the mentioned function above, since Standard Chinese is not available (or did I miss something?). Is there a way to fetch lexemes with language=[[d:Q727694]] from item? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:20, 30 April 2026 (UTC) :@[[User:Sun8908|Sun8908]] There is [[Z1006]] for Chinese and it has the language code zh. There is an overview of languages in [[Module:Wikifunctions label]] so you can search there for chinese versions and choose the one you need. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 5 May 2026 (UTC) ::I know that. The problem is when using the function [[Z6830]], it cannot retrieve lexeme with language [[d:Q727694]] (but it is the "Chinese language" with the most current Wikidata lexemes, see [https://ordia.toolforge.org/language/ ordia]). I think it should be a Wikidata problem, I might fix it (possibly by creating the same lexemes with language code zh) on Wikidata. Thanks anyway. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 05:39, 6 May 2026 (UTC) :Could you provide an example of a Chinese lexeme that has a linked Wikidata item, or a Z6830 function call that fails to find such a lexeme where one exists? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 07:55, 6 May 2026 (UTC) ::Here: [[d:Lexeme:L846083]]. I think that's a primary reason of me trying to look into this problem, as the label in zh for [[d:Q6256]] (country) is not a single phrase (see its talk page on WD for more information). This makes some Abstract Wikipedia articles very weird in Chinese when {{Z|Z26570}} is used, so lexeme could potentially fix that. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 10:33, 6 May 2026 (UTC) :::Thank you. It looks as though {{Z|Z6830}} [https://www.wikifunctions.org/view/en/Z6830?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z6830%22%2C%22Z6830K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q6256%22%7D%2C%22Z6830K2%22%3A%7B%22Z1K1%22%3A%22Z6092%22%2C%22Z6092K1%22%3A%22P5137%22%7D%2C%22Z6830K3%22%3A%7B%22Z1K1%22%3A%22Z60%22%2C%22Z60K1%22%3A%22cmn%22%2C%22Z60K2%22%3A%5B%22Z6%22%5D%7D%7D returns that lexeme for language tag "cmn"]. Perhaps that tag should be added into the helpers for {{Z|Z24144}}? If it is widely used for lexemes, perhaps it should have its own {{Z|Z60}}? In any event, improvements might be considered under [[:phab:T390563]] (or otherwise), including amending [[Z6830]] to also consider "cmn" (and "zho", "chi"…?) when requests are made for "zh-hans" or "zho-hant" (or others?) @[[User:Winston Sung|Winston Sung]] @[[User:DMartin (WMF)|DMartin (WMF)]] [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:22, 6 May 2026 (UTC) ::::If you go to [[d:Special:NewLexeme]] and put in [[d:Q727694]] as the language, it is going to tell you it has an unrecognized language code. So I believe "cmn" should not be a {{Z|Z60}} by default? I also started [[d:Wikidata:Project_chat#Lexemes_with_language_Standard_Chinese_(Q727694)|a discussion on WD]] regarding this. I guess we can still use it as a fallback language though if possible. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 03:43, 7 May 2026 (UTC) ::::We don't have a separated <code>cmn</code> BCP 47 language subtag in MediaWiki and Wikidata at the moment. <code>zho</code> and <code>chi</code> are ISO 639 language codes but not BCP 47 language subtags. ::::For Modern Standard Mandarin, please use <code>zh-*</code> language tags for now. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 15:26, 8 May 2026 (UTC) == Key not found error == Is there a reason why I am getting key not found error for this [[Z34677|function]] {{Z|Z34677}}? All the underlying functions run and all the test cases work. The debug information does not give more details. Any pointers? Thanks in advance [[User:Jsamwrites|John Samuel]] 19:24, 1 May 2026 (UTC) :It was passing the [[Z6091]] to {{Z|34641}} when that takes a [[Z6001]]. I've fixed that, but there's some other problem with the logic, so I've left it disconnected. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 19:42, 1 May 2026 (UTC) ::@[[User:YoshiRulz|YoshiRulz]] Thanks a lot. [[User:Jsamwrites|John Samuel]] 20:21, 1 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, 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:21, 2 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=30325620 --> == Any formal process for deletion of pages == Does a formal process exist for the deletion of functions, implementations, and tests that includes a notification system for creators, analogous to Wikidata’s process, explaining the rationale behind the deletion (or proposal for deletion)? [[User:Jsamwrites|John Samuel]] 12:36, 3 May 2026 (UTC) :Does [[Wikifunctions:Requests for deletions]] work? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:00, 3 May 2026 (UTC) :Please see the discussion at [[Wikifunctions talk:Requests for deletions#Should we expect Objects' creators to get pinged on deletion proposals?]]. :As I see it, it is the proposer’s responsibility to consult appropriately before making a request and we expect our administrators to act only when satisfied that appropriate consultation has occurred. In many cases, no consultation is required. Administrators may delete their own contributions without making a request, but this is not a practice I would encourage. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:51, 3 May 2026 (UTC) == Implementation of rational number in JS doesn't match in Z19677 (Rational number) and Z28579 (RGBA colour) == In {{Z|19677}} it's <syntaxhighlight lang=js> { "K1": sign * numerator, "K2": denominator } </syntaxhighlight> but in {{Z|28579}} it's <syntaxhighlight lang=js> [ sign * numerator, denominator ] </syntaxhighlight> '''<span style="font-family:Iosevka,monospace">[[User:沈澄心|<span style="color:#9f3526">dring</span>]][[User talk:沈澄心|<span style="color:#534fa3">sim</span>]]</span>''' 05:15, 4 May 2026 (UTC) == Nested functions in compositions == I wish it will be easier to a add another function about a specific existing function in a function implementation based on a composition. When I write long functions in spreadsheets I usually stat with a small part and then I try to go further and after important steps I test if the output is as expected. I created [[Z34826]] to get the German gender specific occupation lexeme for a specific person based on their gender. I wanted to add a function around the existing one and it was not successful. It is not very easy to implement as it requires the possibily to move a part to another section but I think it can be helpful if it will be implemented. So far I spend more time as expected on the function. Describing it with words what the function needs to do is much easier than implementing it here in Wikifunctions. So I think there needs to be improvement to make Wikifunctions more accessible. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:10, 5 May 2026 (UTC) :Have you tried to use the copy-paste functionality? It is very useful to move parts of composition arounn. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 07:12, 6 May 2026 (UTC) :I've also found the composition editor to be wholly unsuitable for any expressions more than a few levels deep. (Even with the <code>localStorage</code> clipboard, because of its overzealous type checks.) Compositions naturally grow out from the "leaves", the immediate operations on the inputs, while the interface really wants you to build from the "root". I mostly use the [https://yoshirulz.gitlab.io/WikiLambdaBlockly drag-and-drop block editor] which I made to smooth over some of the site's problems, so if you want to try that out and give me some feedback I'd appreciate it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 14:36, 6 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the 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 [[: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/1778520600 May 11, 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]]) 11:16, 8 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=30325620 --> == RGBA colour, spelling... == Something that has always irked me a little bit is the spelling of [[Z28579|RGBA colour (Z28579)]]. I guess this is not unsurprising for me considering my use of US English but I think there is more to it than preference and I want to try to argue for it being changed to use American spelling. I know that this probably has a snowball's chance in hell of actually garnering any support, so I won't really be miffed if the spelling remains as it is, but I thought it wouldn't hurt to raise this regardless. The main issue I have with it is the spelling of the original proposal. When infernostars raised the [[Wikifunctions:Type proposals/RGBA color|type proposal]], the spelling was 「RGBA color」. Of the comments that mentioned the word 「colo[u]r」, two used British spelling while six used the American spelling as used in the proposal. The only thing that really pointed to the use of ''colour'' was the fact that the catalog page on color functions used that spelling already. For all intents and purposes, the spelling of the original proposal should have been maintained, but it was not; [[User:DVrandecic (WMF)|DVrandecic]], the eventual creator of the type, used a different spelling. It should be noted that there was really no reason for this to occur and while it is an undoubtedly minor issue I still believe it should be rolled back and the type should use the spelling of the original proposal and majority of editor comments. In [[abstract:Q936|OpenStreetMap]], there have been keyvalue proposals that have had the finalized spelling that gets put to use be in British English despite the original proposal being in American English; this has usually occurred with proposals relating to 「X center/centre」 tags. This makes sense on the surface, because OpenStreetMap is maintained by a UK organization, and still has close ties to Europe. The Wikimedia Foundation, however, is an ''American'' company. This is often brought up as a fallible argument when debating article spelling on the English Wikipedia, and I don't bring it up to support that 「RGBA color」 should be used for that exact reason, but rather to state that OpenStreetMap's general policy on tag names need not apply here. It appears to me that, at least initially, the majority of 「core contributors」 to Wikifunctions used British English; I can name YoshiRulz, 99of9, GrounderUK, and VIGNERON.<ref group="color">I'm avoiding linking to these folks because I don't think pinging them about this discussion is all too necessary unless they themselves want to be involved; I don't want to clutter their inboxes just to briefly mention them. I pinged Denny because, well, I'm asking him a question directly, but everyone else I would prefer to join this discussion by their own accord... not that I wish for this decision to be confused as me going 「these people use British English so they will probably oppose my idea, I won't invite them to the discussion because of that」...no, I promise you that is not the reason.</ref> I see (or saw) these people ''everywhere'', so it makes sense that British English has prevailed in some sorts on this website, but I don't think that indicates that it should be the ''preferred'' spelling across the website, at least not to the point where a proposal should have its name changed to match such a "consensus".<ref group="color">It could be argued that the front-and-center ''Function catalogue'' using 「catalogue」 is actually indicative of such a "consensus", but ''catalogue'' is in a similar position to the word ''grey'' where I live (that is, the US) in that it is used just as often as its American counterpart. Also, consider Wiktionary's ''Beer parlour'' project chat.</ref> The unnecessary modification of the original spelling is my main argument for changing it back... but of course, I must obligatorily state that on English Wikipedia, it is [[w:Color|Color]] and [[w:RGBA color model|RGBA color model]]; on Wikidata, it is [[d:Q1075|color]] and [[d:Q2325624|RGBA color space]]; in CSS (which typically uses hexadecimal triplets to specify RGBA values), the properties are <code>color</code>, <code>background-color</code>, etc.; bit of a weak jab, but on Schema.org it is [https://schema.org/color color], [https://schema.org/colorSwatch colorSwatch]; et cetera. {{Z|Z28580}} uses ''color'', so does {{Z|Z28591}} and its Python counterpart. Mr. Vrandečić, I have to ask, I'm rather confused... you created the color type using British English spelling, but you were also responsible for the creation of the equality function which uses the American English spelling. You also seem to be writing in American English for the status updates, judging by your use of -''ize'' over -''ise'' endings and use of ''program'' over ''programme'' in [[Wikifunctions:Status updates/2026-04-16]]. Is there something I'm missing or have you switched your preferred variant somewhere along the way? Anyways, do consider this if you wish... again, I don't suppose this will garner much support, it is the ''non-issuest'' of ''non-issues'', but it has irked me to the point where I want to ask about it to get some answers, if nothing else. I am not arguing for every other color function to have its name changed, just the type itself. <references group="color"></references> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 8 May 2026 (UTC) :This is a multilingual project; the <code>en</code> label is <code>RGBA colour</code> and the <code>en-us</code> label is <code>RGBA color</code>. Though I'm not able to switch to <code>en-us</code> via the language picker so that would need to be fixed.<!-- --><br>edit after reading your whole comment: The same is true of {{Q|1075}}, there are labels specified for multiple English variants. (In {{Q|2325624}} it's only an alias.) I agree that other websites' choices aren't binding on us, but from that, I conclude that the more widespread British/Commonwealth spellings should be used for the generic <code>en</code>. As for myself, I'm Aussie and I will continue to use the BrE spellings ([[w:en:Oxford_spelling#Language_tag_comparison|+ "routing"]], TIL) if only by muscle memory.<!-- --><br>[[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 17:42, 8 May 2026 (UTC) :: Your lattermost point would normally be fine in a perfect world. Wikipedia's <code>convert</code> function defaults to "international" English, which I don't personally take issue with because it happens that we here in America are actually outliers for saying and spelling things differently... err, or we were for a while at least, nowadays it seems like an even split (plus you have "yield" vs. "give way" which is effectively the logical opposite of US's use of "meter" over "metre"). :: However, this is not a perfect world, and I don't think <code>en</code> should correspond to any particular variant. It is too fragmented across all software at this point to impose such a requirement. The inability to switch to <code>en-us</code> on this website foregoes an easy and simple solution to this problem that makes everyone happy, because the yanks (such as myself) can't be happy because we can't see the labels in American English even if we wanted to, and the other folk can't switch either as far as I'm aware (and the en-CA and en-GB languages in the preferences page seems to be deprecated). My point being, <code>en</code> is abused to mean "en-UK" just as often as it is abused to mean <code>en-US</code>; I think a decision shouldn't be made on such an assumption of one "default". &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:48, 12 May 2026 (UTC) :Hi @[[User:Theki|rae]]! I have no opinion nor preference on this, and given my background, I am just entirely confused about my spelling preferences myself, as you can tell from my inconsistent usage. I learned British English in school and used that for maybe two decades or so, but moved to the US and lived there for more than a decade, enough to be naturalized, but now I am back in Europe and I am technically a professor at King's College London, soooo.... honestly, I do not know. I don't remember having put too much thought into it at the moment I created it. The good thing is that in Wikifunctions, just as in Wikidata, it is easy to change, without messing things up too much (unlike in Wikipedia), so my suggestion is, just make the change, see if anyone complains, and if they do, discuss it more. I don't know if there is a guideline already in Wikifunctions about the variants. I am happy either way, and honestly, I keep forgetting which variant is which most of the time. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 18:16, 10 May 2026 (UTC) :: I can definitely understand this, although I am unfortunately rather passionate about any minutiae involving preferential minor differences in ''anything'', of which AmE vs. BrE chiefly is. So I dedicate a lot of headspace to it. More than I should. Not that I wish to imply that the comment above that I have wrote is of an irrational nature, or done out of spite or pure emotion and subjectivity; I do genuinely believe that ''RGBA color'' is beyond just a personal preference and is just logical. I may boldly go and change it, but for some reason I was expecting that changing the English label of a Type would require elevated permissions, and I also didn't want to do it only to get immediately reverted because it ''did'' strike a chord with someone, when I could instead see how apathetic, supportive, or in opposition interested people are beforehand and ''then'' act accordingly. I was not meaning to antagonize you over your spelling habits, I did actually use British English for a few years starting in 2020 before I went back to American English, so I'd be a hypocrite for me to decry you for not always sticking to some arbitrary standard of spelling words over the other. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:55, 12 May 2026 (UTC) :Although I spell it “colour”, I think it makes more sense to use “color” for the type, since that is almost always the required spelling when the string functions as a keyword. :More generally, though, Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en". This is unusual, in my experience, as "en" is widely misused in place of "en-US", where there are recorded spelling differences. :(I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere. Use of -ize rather than -ise is a matter of personal preference or house style, but regional autocorrect encourages -ise.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:00, 12 May 2026 (UTC) :: ''Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en"'' :: Definitely agreeing with you on the latter being a good choice. However, I suspect the favoring of "colour" over "color" may be because, in terms of language codes, when sorted alphabetically <code>en-us</code> actually comes ''after'' <code>en-gb</code>. Although, the frontend seems to be sorting <code>en-ca</code> after <code>en-gb</code>, so I don't actually know how correct that is. :: ''I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere'' :: The context of the spelling was "''No program for the NLG SIG meeting for next Tuesday has been proposed''". In that usage context, I think it makes sense to assume that ''program'' is not being used to refer to a computer program, but to a ''program of events'' or similar, something that you would spell as a ''programme'' in British English. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 12 May 2026 (UTC) :{{s}} this. I'm obviously biased but I believe American English is preferable generally, American dominance on the internet (our Department of Defen'''s'''e invented it!) and rapidly-increasing consumption of American media by international English speakers means that more people use American English's conventions, this is clear through for example [http://trends.google.com/explore?q=color%2Ccolour&date=all&geo=Worldwide search trends] (though they aren't particularly reliable). Perhaps this is a bit of a supremacist opinion, but we should have internal consistency, and if we must choose, American English should be our first choice (then Indian and then British English) [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:10, 12 May 2026 (UTC) :: This is rather flawed reasoning, though. I think probably any given British or Indian person would not agree on using that as the reasoning for this, not that you are necessarily ''completely wrong'', but if this is not a good enough reason for English Wikipedia's (admittedly extremely flawed) ''ENGVAR'' policy then I don't think it's likely it will pass here either. :: Although of note is that [https://books.google.com/ngrams/graph?content=color%2Ccolour&year_start=1800&year_end=2022&corpus=en&smoothing=3&case_insensitive=true Google ngrams] agree with you, but "color" vs. "colour" is an eternal holy war that will not be won by demonstrating that more books use US spelling over Commonwealth spelling. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:44, 12 May 2026 (UTC) :::You're probably right that it's not very sound. I'm biased in that other varieties of English irk me, and that's probably mutual for people who are used to other varieties of English when they read what I write! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:56, 12 May 2026 (UTC) :I've decided to boldly [[Special:Permalink/274271|make the change]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:02, 12 May 2026 (UTC) :: Thank you. Considering both you and GrounderUK seem to consider it an okay change, I think this will do for now. :: I should note that the matter of whether to move [[Wikifunctions:Catalogue/Colour functions]] in response to this (however this discussion will ultimately turn out) is a whole other can of worms, in my view. I can't say I have an opinion on that at the moment, but I'm putting it out there regardless. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:06, 12 May 2026 (UTC) :::Personally, I'm in favor of moving the page and renaming all of the items on it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:10, 12 May 2026 (UTC) ::I don't like this (exactly because of the American hegemony you cited), but again, it shouldn't matter because the software is meant to be multilingual. Clearly there's a bug preventing you from picking an English variant/dialect as your display language. But the search bar and Function/Type autocompletion do check the English variants for matches. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 15:15, 12 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[abstract:User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:31, 11 May 2026 (UTC) :Thank you for dedicating your time to writing this, it is very informative. I will try to add input once I'm not in over my head with finals. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:27, 12 May 2026 (UTC) == Display function for HTML fragment == Currently, any collapsed Z89 literal appears as<blockquote>&lt;&gt; [[Z89|HTML fragment]]</blockquote>If I were to create a new Function which returned something like<blockquote>&lt;&gt; 123-byte HTML fragment <q><nowiki><td><span lang=</nowiki>&hellip;</q></blockquote>could that be connected to replace the collapsed form, or would it require changes to the Wikilambda software? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 16:14, 11 May 2026 (UTC) :It might work, but I doubt it. Those angled brackets suggest that the collapsed form is not simply defaulting to the type’s label. Looking at [[:phab:T410509]], I’ve concluded that enhancements to the collapsed form were never considered, rather than being actively rejected. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:12, 12 May 2026 (UTC) ::[[:Phab:T391985]] documents the original design. Note the fifth bullet point under “Acceptance criteria”. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:21, 12 May 2026 (UTC) :I'm not sure the byte-size is necessary, but the outer tag (or first outer tag, though generally I'd prefer most fragments use a wrapper tag if it needs multiple like JSX does, but that's a whole different topic) would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:51, 12 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in 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]]) 14:36, 15 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 --> == [[Z34510]] == This function, which determines if a Wikidata item for a {{q|5}} has an undeprecated {{p|21}} statement of {{q|6581097}}, returns false for {{q|173399}}, a transgender man. This is because his item assigns his P21 statement to {{q|2449503}}, not {{q|6581097}}. I'm not sure how to account for this discrepancy. Should {{z|34510}}: # Include {{q|2449503}} as a value that can lead to a true result, # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a man?") could return true for either "male" or "trans man", # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a trans man?") could return true for "trans man", # Not exist at all? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:48, 16 May 2026 (UTC) :I can't think of a single use case where you would need to determine if a person is a cisgender man and nothing else. Functions are good for generalizing across multiple possibilities when they exist, so I think it would be best if trans men were considered a part of the criteria for returning a true value. If asking for specifically {{q|6581097}}s and ''nothing'' else was desired then the function name would be a misnomer as Elliot Page is inarguably a male (at least in the view of most reasonable and intelligent people). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:03, 16 May 2026 (UTC) :You made the function in the first place; what were you planning on using it for? AW? Maybe it should return a {{Z|25501}} which can then be passed on to other NLG functions. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 May 2026 (UTC) == Lexeme from wikidata label, or "best" lexeme from wikidata item == I was looking into fixing [[Z28028]]. I found that I could add "requires grammatical feature: definite article" to "United Kingdom" (L8558). Now I'm stuck on how to get to that lexeme from {{Q|145}}. There's [[Z23471]], but that for very good reason gives you multiple lexemes with the same sense, and I just want the best one like how the label is always the best string. Is there a function that can do this? There's definitely the case of a Wikidata label that isn't a lexeme (most commonly multiple lexemes) but I'm only considering the case where it is one lexeme here. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:02, 16 May 2026 (UTC) :There is {{Z|Z27327}}, that tries to give the best lexeme through various heuristics. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 22:22, 16 May 2026 (UTC) :: Wonderful! I did stumble upon [[Z33818]] but this is perfect. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 00:25, 17 May 2026 (UTC) 5935gv7f4o2ogvx4dnd18l5pqqv1m8j 275599 275588 2026-05-17T01:17:45Z JJPMaster 6409 /* Z29591 isn't working for me */ new section 275599 wikitext text/x-wiki {{shortcut|[[WF:CHAT]]|[[WF:PC]]|[[WF:VP]]}} __NEWSECTIONLINK__ [[Category:Help]] <!-- please do not remove this line --> Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc. Other places to find help: * [[Wikifunctions:Administrators' noticeboard]] * [[Wikifunctions:Report a technical problem]] * [[Wikifunctions:FAQ]] {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |timeout=30 }} {{Archives|{{#tag:div|<br />{{Flatlist|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1|hideredirects=1}} |class=mw-collapsible-content|style=font-size:92%;}}|class="mw-collapsible mw-collapsible-toggle mw-collapsed"}} |prefix=WF:Project chat/Archive/ }} == "language" argument for certain functions == Hello. I am relatively new to Wikifunctions. Recently, I tried to create functions for Chinese translation of {{Z|Z26570}} and {{Z|Z26095}} (which became [[Z32788]] and [[Z32900]]). During the creation of these functions, I was trying to take {{Z|Z32212}} as reference. And I realized that the defining role sentence function is taking <code>language</code> as an argument (and the test case of the Chinese-language function already contains two varieties of Chinese). This makes it possible to output monolingual text in <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code>, or any varieties of the language. I think for this reason, it is better to have <code>language</code> as arguments for the implementation of Z26570 and Z26095, and potentially more functions that require {{Z|Z14294}}, since it would output the varieties code instead of just saying <code>zh</code> for <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code> in the output of type {{Z|Z11}}. I am not sure how the fallback mechanism works if one of the language (varieties) do not have a labels/lexemes, but to me, it is reasonable to have a <code>language</code> argument. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 09:38, 31 March 2026 (UTC) :The functions you mention do have a language argument. For Wikifunctions, the {{Z|Z60}} can be at a higher or lower level; whether a {{Z|Z11}} is for a language or a variant is determined by the function that constructs it. Please see {{Z|Z26565}} for an example and feel free to add test cases in Chinese. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:54, 11 April 2026 (UTC) ::Hello @[[User:GrounderUK|GrounderUK]], thanks for the answer. I understand that whether {{Z|Z11}} is for a language or a variant depends on the function. But that is exactly what I am asking for. It is true that [[Z26570]] and [[Z26095]] takes [[Z60]] as argument, but the language-specific functions in {{Z|Z29843}} and {{Z|Z26096}} don't. ::Let me give you an example: INPUT to [[Z26570]]: <code>entity</code>: Tokyo, <code>class</code>: city, <code>location</code>: Japan, <code>language</code>: zh-cn, the config would select [[Z33030]] (created after my previous comment by elseone) as the implementation, and it would RETURN 东京是日本的一个城市。(zh-hans), which is not zh-cn as requested in the INPUT. It would also be using the term not for the variant (when it is different) because it is hardcoded to use the term in zh-hans. However, if we have the implementation like [[Z32790]] (which was created by me but a natural language argument was added by elseone) or [[Z32213]] (that works in the defining role sentence function because of the extra argument), it could cater for different variant. ::If we don't have the language argument in the language-specific function, the desire for article creation on Abstract Wikipedia would be to create a function for every variant. Is it then better to create functions for every variant? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:18, 11 April 2026 (UTC) :::I forgot to mention that there are some hardcoding in {{Z|Z32790}} as well, but I cannot fix it because it is a connected function and I am not a functioneer. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:31, 11 April 2026 (UTC) ::::Okay, I think it’s safe to disconnect this one as the function is not yet configured for use on Abstract Wikipedia. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:04, 11 April 2026 (UTC) :::Ah, sorry… I misunderstood you. I agree that the called function should be able to accept the original language argument. That is simpler in theory than in practice, because the configured functions all have to have the same argument types, as I understand it. I’m not sure which the best approach is, really, but we probably want to avoid two levels of configuration. That suggests that all language-specific functions would need to accept the additional argument, which is unrewarding work for someone. @[[User:99of9|99of9]], @[[User:Jdforrester (WMF)|Jdforrester (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]] Any thoughts? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:57, 11 April 2026 (UTC) ::::I mean, we would need to modify all the functions in each language, which could take some time. But we are still in an early stage. If we don't fix it now and we want to fix it later, it would be a disaster. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 19:25, 11 April 2026 (UTC) :::::Agreed. And we probably want them converted to HTML too, with separate language spans for text in different languages. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:35, 11 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]: This sounds like a reasonable change to make. Note that (given these Functions are primarily for use on Abstract Wikipedia), altering/replacing them to return Z89/HTML fragments is already a desired but breaking change, so making a second breaking change at the same time is probably easiest for fixing things swiftly. That said, that's of course a decision for the Abstract Wikipedia and Wikifunctions communities, not me! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:43, 12 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]@[[User:Sun8908|Sun8908]] to make it a non-breaking change, I've created {{Z|Z34039}} which allows a composition {{Z|Z34043}}. This way you can make functions which either need the specified variant or don't! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:52, 24 April 2026 (UTC) :I have now created {{Z|Z33465}}, which is an implementation of [[Z26570]]. Maybe we can migrate to use that function when more (language-specific) functions for it are ready? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:19, 14 April 2026 (UTC) == No place to ask to activate a function? == I just discovered the {{Z|Z11390}} function and decided to make an overarching language-selecting function for it. After some fiddling around and studying how {{Z|Z32321}} and its set works, I now have {{Z|Z33439}} which has a config object ({{Z|Z33441}}) that selects between the two preexisting language-specific versions I found (English and Malayalam) and the new one I created for my other native language, {{Z|Z33440}}. Except I can't get these to work, because, from what I understand, only [[Wikifunctions:Functioneers|functioneers]] can activate newly created functions and implementations? So where do I apply for the {{Z|Z33439}} and {{Z|Z33440}} functions to be activated? Perhaps we should have a place to ask for it, a la [[w:WP:NPP]] — call it [[Project:New Functions Patrol|New Functions Patrol]] if you will. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] ([[User talk:UndueMarmot|talk]]) 08:58, 14 April 2026 (UTC) :There's [[Wikifunctions:Community portal]] for this. By the way, {{Z|Z33445}} doesn't work because all the code must be inside the main function in Python code. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 09:19, 14 April 2026 (UTC) ::Huh. How could I have missed that? ::But anyway, I've moved the code in {{Z|Z33445}} into inside the main function block. ::Is there any reason why WF decided not to simply allow anyone to write functions? After all, that's how it works with wikitext templates, and these functions are fundamentally serving the same purposes as templates, just written in a different way. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 11:25, 14 April 2026 (UTC) :::I've fixed a couple of technical issues, but tests still fail. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:28, 14 April 2026 (UTC) ::::The tests pass now after some more changes to the code: [[Special:Diff/265232/cur]]. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 12:01, 14 April 2026 (UTC) :::::{{D|Connected}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:02, 14 April 2026 (UTC) :::I think it's a security issue, since Wikifunctions implementations could teoretically be malicious. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:29, 14 April 2026 (UTC) ::::This ^^^. We're very lenient, though, once you've created a few working functions you can apply for the right, per [[WF:Functioneer]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:26, 14 April 2026 (UTC) ::::That explanation [[phab:T343559#11421293|doesn't add up]]. A reason to limit ''connection powers'' to Functioneers might be to prevent vandalism, considering Functions can be used across wikis. But user-provided code is already being executed even without a Functioneer connecting it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 April 2026 (UTC) == Actual difference between {{Z|Z26039}} and {{Z|Z26095}} == What is the actual difference between these two functions? I ask, since it seems to me that the current distinction is more or less that the first one doesn't use an indefinite article in English, while the second does. Which is not a good distinction in a project that should be language neutral. This doubt emerged from my use of the first one in [[abstract:Q124441]], which @[[User:Hogü-456|Hogü-456]] made me notice that is probably wrong. My question is: why is it wrong? How could we clarify the difference? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:46, 19 April 2026 (UTC) :I think the difference is if there is an indefinite article like a or an before the subject or not. In German there can be cases where a definite article is necessary before the subject. I looked at the functions and before the object both times an article is mentioned. As it depends on the language and the word what is the correct function to use I hope it will be clarified and it is an example of the necessity to have a human with understanding in a specific language check it. I hope there will be longer functions what generate more content about a specific kind of item. Then it is necessary to write one such function per language and it can be then applied to several items. It still requires checks and so maybe it is better to write down what item category needs what kind of introduction sentence function for what language. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:05, 19 April 2026 (UTC) ::The point of these two functions (and of the entire Abstract Wikipedia project) is that they should be defined in a purely language-independent way, so that the translation to actual language can be done automatically. This is the reason why these functions have been renamed; I think that this attempt was not succesful, since meaning is still unclear. My proposal to clarify them would be to invoke the concept of [[w:specificity (linguistics)|specificity]]: {{Z|Z26039}} should be named "specific subject is instance of (string)", and should be used only when the QID of the subject uniquely identifies a single thing; {{Z|Z26095}} should instead be renamed in "non-specific subject is kind of (Monolingual text)", and should be used when the QID refers to a multitude of real life items, and we are specifying the class that all these item belong to. This clarification would not still be enough, since it doesn't explain how mass nouns are handled (is water a unique thing? Does {{Q|Q7802}} refer to a single piece of bread or to the entirety of bread, like water?). This problem is very tricky, since mass noun are language-specific and blurry the line between these two functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 20:58, 19 April 2026 (UTC) :Simply put, one corresponds to P31 and the other to P279. Paris is an {{Q|P31}} a {{Q|Q1549591}} :whereas a {{Q|Q1549591}} is a {{Q|P279}} (alias “kind of”) {{Q|Q515}}. Whether the Wikidata knowledge representation will be sufficient to resolve into fluent natural language representations in all languages is, of course, a crucial question. Where it is not, the Abstract Wikipedia knowledge representation will need to supplement the Wikidata content with additional details about the relation between the participants or the participants themselves, and these details should be language-neutral, to the extent that this is practicable. The item {{Q|Q124441}} has no [[:d:Q124441#P31|P31]] statements; it has only [[:d:Q124441#P279|P279]]s, including one relating it to {{Q|Q212920}}, which suggests {{Z|Z26095}} is the appropriate choice here even if the rendering in some languages is the same. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:52, 19 April 2026 (UTC) ::Thanks for explaining it. I think that I'll change the implementation of {{Z|Z26095}}, so that in Italian it produces more or less the same output of {{Z|Z26039}} (both with the definite article). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:24, 20 April 2026 (UTC) == Equivalent of Z6830 for lexemes == Is there an equivalent of {{Z|Z6830}} that enables retrieving all lexemes pointing to a particular lexeme using a specific property? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 21:06, 20 April 2026 (UTC) :There's {{Z|6831}} but I think that's slightly different again to what you're after. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 12:31, 21 April 2026 (UTC) ::Thanks for sharing that one, I did not know it existed. But you are right, it’s not quite what I am looking for. I want a function that would take a Wikidata property reference (like P5191, which is ‘derived from lexeme’) and a Wikidata lexeme reference, and return a list of lexemes that reference that lexeme using that property. [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 13:23, 21 April 2026 (UTC) == Storing huge datasets == It is not a necessity I suppose, but an idea came to me earlier to write a function that would give the corresponding [[en:Shavian alphabet|Shavian alphabet representation]] of an English word written with the Latin alphabet, or perhaps apply that operation to an entire sentence. However, just trying to guess as to what the IPA pronunciation of each word passed into it could be is is both not ideal (pronunciations obviously can and will vary widely between accents) and infeasible <s>(Wikidata lexemes don't really seem to account for pronunciation)</s>. It happens, though, that a comprehensive Shavian dictionary exists named the [https://readlex.pythonanywhere.com/ ''Read Lexicon''], which uses pronunciation and spelling similar to that used by the creator of the alphabet himself. This would be a good dataset to use in performing this translation in the function, but it appears that, all in all, the total size of the dictionary is [https://github.com/Shavian-info/readlex/blob/main/readlex.json ''nearly 26MB''] when formatted as JSON, which would certainly be larger when converted into a typed list. I am wondering if this will ever be feasible or admissible, or if there is really a way around this if importing such a large set of data is deemed impractical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 22:30, 20 April 2026 (UTC) :{{re|Theki}} "Wikidata lexemes don't really seem to account for pronunciation"" is patently untrue; not only does every Bokmål lexeme form have IPA attached to it (thanks to Jon Harald Søby), but there are lots of languages--including English--that have pronunciation information, whether through IPA or otherwise, indicated on their forms. The big issue of course is that adding this data is not always possible to perform efficiently--for instance, I'd love to have Yiddish pronunciation respellings from Paul Abelson's dictionary on as many English forms as possible, but this dictionary not being previously processed makes this difficult. The data set you have brought up, if a suitable reading of [[:m:Wikilegal/Lexicographical_Data]] allows it, could be added as {{P|7243}} statements on various English forms. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 23:20, 20 April 2026 (UTC) ::Well, sorry... I haven't witnessed these pronunciation statements before, I wasn't aware of their existence until you pointed it out. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 21 April 2026 (UTC) :I got 1,900,000 characters into [[Z33875]] before the UI gave up on me. I'm not sure what the limit is. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:21, 21 April 2026 (UTC) == Could not serialize input JS object: Number <small><small>[insert tested number here]</small></small> == I'm not one to throw my problems at others, but I have no idea how to fix this. Am implementing {{Z|Z24602}} in JavaScript, which requires returning a typed map. It now works for every type of value except numbers. Tried explicitly converting the numbers to float64, but either way it throws the error above. Would appreciate it if anyone could diagnose or fix the problem, as my knowledge of Wikifunctions is amateur at best. Thank you. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:32, 23 April 2026 (UTC) :The quick answer is that like some list-related functions, code implementations returning typed maps are not possible unless the type of the objects in the map is specified in the function signature (e.g. if it was a map from Strings to Natural numbers only). So unfortunately, I think you've chosen a function that is not really possible at the moment. There are a few ideas of how we might address this, but for the moment, work on something else. Sorry! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:21, 23 April 2026 (UTC) :Maybe explicitly using [[Z13518|natural numbers]] would work? I would try using <code>{ "Z1K1": "Z13518", "Z13518K1": "[number]" }</code> to represent numbers, perhaps, and seeing if that works. Of course, you would also probably have to adapt this for other types that cannot be serialized, and I'm not sure how easy that would be to generalize (assuming [[w:Don't repeat yourself|DRYness]] is desired). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:39, 23 April 2026 (UTC) == Help with creating a function for Abstract Wikipedia == Hello! I was inspired by {{Z|Z26570}} to create {{Z|Z33975}}, however I'm not sure how I add specific language implementations here. Can anybody help me? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 10:41, 23 April 2026 (UTC) : I think I figured it out, I created a new object with the language config type, added {{Z|Z14310}} to my implementation, and added a new function for English... At least I think that's how it works... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 13:16, 23 April 2026 (UTC) ::You have the right idea, as far as I know. I went ahead and connected the implementations you created as they appear to work fine for English, and added a test for {{Z|Z33975}} (which passes [[File:Twemoji 1f601.svg|24px]]). I also corrected an error you made on the config object where you appear to have accidentally connected English to {{Z|Z33975}} instead of {{Z|Z33977}}. Thank you for contributing! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 23 April 2026 (UTC) ::: {{re|Theki}} Thank you so much for you help! Could you please kindly also connect the implementations for {{Z|Z33986}} which I just made, which is going to be used for the Hebrew implementation of {{Z|Z33975}}. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:11, 23 April 2026 (UTC) ::::You seem to be returning the wrong type in both implementations. Functioneers should not connect implementations that don't work for non-functioneers. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:13, 23 April 2026 (UTC) ::::: {{re|Feeglgeef}} Oh thank you for pointing that out! I am still a bit new to this project and confused, so I need to read up some more about this. How do I return a monolingual text object? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:17, 23 April 2026 (UTC) ::::::I'm trying to fix it for you, the construction of ZObjects in code implementations is a bit difficult right now. Since the State origin using entity and class function will (presumably) be composition, perhaps {{Z|33975}} can be adjusted to return a string, using {{Z|26107}} and {{Z|26107}}? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:21, 23 April 2026 (UTC) :::::I did not notice any discrepancies from looking at the functions by themselves, and it seemed to work fine on my end. Is it bad practice for NLG functions to return the monolingual text type? I had assumed it was logical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:24, 23 April 2026 (UTC) ::::::Both implementations are failing all three tests on my end. No consensus has been established as to whether monolingual texts or strings should be used, so it's like the [[w:War of the currents|war of the currents]] but for Wikifunctions. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:27, 23 April 2026 (UTC) :::::::Oh, you were referring to {{Z|Z33986}}. I assumed you were stating that something was wrong in the earlier English functions that I missed; I apologize for the misunderstanding. Has there been any centralized discussion on this string vs. monolingual text issue? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:31, 23 April 2026 (UTC) ::::::::Not that I'm aware of, I've brought it up on the telegram twice before, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:49, 23 April 2026 (UTC) ::::::::The centralised discussion is at [[WT:Abstract Wikipedia/2025 fragment experiments#Proposed recommendation: Fragments should return Z11/monolingual strings]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:19, 24 April 2026 (UTC) ::::::: {{re|Theki|Feeglgeef}} Can only functioneers test implementations? For me I can't test it at all... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:32, 23 April 2026 (UTC) ::::::::AFAIK, test cases are only immediately testable during editing of a function if they are connected. This is one of my personal pain points with Wikifunctions, iterating on functions without exhaustive connected test cases makes debugging practically impossible for non-functioneers working on newly-created functions... I (or Feeglgeef) can quickly connect the tests you need for you if you want, although if they are not well-formed they may need to be disconnected again afterwards. Additionally, I could temporarily connect the implementation you are writing so that you can test it on the sidebar as you work, but I'm not sure if this is advisable. That functionality is also something that unfortunately only works when not disconnected. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:43, 23 April 2026 (UTC) :::::::::Yup, agree with you on all points, thanks. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:48, 23 April 2026 (UTC) == Please disconnect implementation == I think I've fixed my issue with {{Z|Z33986}}, but I can't edit an actively connected implementations with my rights. I must admit it is an AI-aided fix, I feel very strongly about disclosing that. Courtesy pinging [[User:Theki]] and [[User:Feeglgeef]]. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:51, 23 April 2026 (UTC) : Additionally, I think the JS might be working. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:52, 23 April 2026 (UTC) : Just to clarify, I mean disconnect the Python implementation please. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:53, 23 April 2026 (UTC) :{{Done}} I've disconnected the Python implementation. :I've also added a couple of tests. The rule is a bit more complicated than adding a maqaf before every character that is not a Hebrew letter. Unfortunately, I don't think I'll have time to fix the implementations any time soon. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:03, 23 April 2026 (UTC) :: Thank you! :: Also, for some reason I thought you put a maqaf before all gershayim, so thanks for correcting me. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:09, 23 April 2026 (UTC) :::No, that's not the rule. :::The rest of this reply is an [[:wikt:info-dump|infodump]], feel free to ignore it :) :::In [https://hebrew-academy.org.il/topic/hahlatot/punctuation/ the Academy's punctuation rules], the rule for adding a maqaf is written kind of badly: שמים מקף ברצף שיש בו שני סוגי גופנים, כגון אותיות ומספרים ("maqaf is added in a sequence in which there are two types of fonts, such as letters and numerals"). These are not different types of "fonts", but different types of characters, and I should email them about it. It gives the examples <span lang="he" dir="rtl">ה־12</span> and <span lang="he" dir="rtl">ב־DNA</span>. It doesn't say anything explicitly about quotation marks, but in other places on the same page, you have stuff like <span lang="he" dir="rtl">ב"הארץ"</span>, and from that I deduce that a maqaf is not needed before double quotes if there are Hebrew letters inside the double quotes. :::That said, a few people do think that there must be a maqaf before double quotes. I have a somewhat surprising example of somebody who always does it: translators of Scientology materials into Hebrew. At least that's what they did last time I looked at them, about ten years ago. Those people are certainly prolific, and they get points from me for consistency, but this not the prevalent standard. (And if I recall correctly, they use the minus and not the proper Hebrew maqaf, and they don't get any points from me for that!) :::Also, the name of the character is just "double quotes" and not "gershayim". Gershayim are mostly for abbreviations, although most people use the same character for them. I use ״ for gershayim, as do a few other nerds, but we're the minority. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:35, 23 April 2026 (UTC) :::: {{re|Amire80}} Yeah, "font" is a weird choice of wording here by the Academy...<br> I think I'll follow your guidance and not use a maqaf for quotes beginning with Hebrew letters. <br> I should also add more tests for different types of quotes, like straight (", '), curly (“, ”, ‘, ’), gershayim (״, ׳), including single quotes.<br> P.S. gotta deduct points from Scientology for being a cult but that's neither here nor there [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:49, 23 April 2026 (UTC) :::: {{re|Amire80}} Courtesy ping because I mistyped your username on the last message. Anyways I'm also gonna do that tomorrow because I'm tired now... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:50, 23 April 2026 (UTC) == Connect implementations == Hello! I'm done with the implementations of {{Z|Z33986}} both in JS and Python, and all tests pass. Pinging @[[User:Amire80|Amire80]] to check if all the tests I've added are alright. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 15:24, 24 April 2026 (UTC) :Connected. It's possible that some more changes will be needed, but it looks OK now. :Another little comment: It should be called "clitic" and not "prefix". [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:56, 24 April 2026 (UTC) : {{re|Amire80}} Thanks for your comment! Luckily labels are easy to edit, so I'll get to it. : Currently I'm working on Bulgarian {{z|Z34072}} and {{z|Z34084}}, along with other Bulgarian functions. After I'm finished with those I'll take your advice. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 16:01, 24 April 2026 (UTC) == Please connect my Bulgarian implementations == I recently created the following Bulgarian functions: * {{Z|Z34070}} (currently broken, I think because another function I built it upon is unimplemented) * {{Z|Z34088}} * {{Z|Z34105}} * {{Z|Z34072}} * {{Z|Z34084}} Can somebody please connect these functions, and perhaps suggest other functions I could localize? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:03, 24 April 2026 (UTC) : Specifically, [[Z34070]] is based on [[Z34072]] [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:05, 24 April 2026 (UTC) :{{done}} for everything that passes, [[Z34070]] still does not work after purging WF's cache, though. For future reference, please request on the [[WF:Community portal|community portal]] instead of the project chat. Thank you for your work! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:03, 24 April 2026 (UTC) :: {{re|Feeglgeef}} Thank you for your help! I will keep in mind to go to the [[project: community portal| community portal]] in future instead for this. :: I still don't understand why {{Z|Z34070}} fails... It's implementation is almost completely identical to [[Z30399]] from {{Z|Z30397}}, unless I messed something up... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:11, 24 April 2026 (UTC) :::{{done}} No, it was mostly just timing out. It is better to use selective fetches where possible. One case is failing to match the expected results, but at least it is returning something. For all I know, it might even be acceptable! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 20:35, 24 April 2026 (UTC) :::: {{re|GrounderUK}} Thank you so much for your help! The one failed case is with a definite article, so I feel like that might be fixed in the future... <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:43, 24 April 2026 (UTC) == Editor experience suggestions == I'm a bit frustrated with the editing experience on Wikifunctions, and I have suggestions based on pain points I've had contributing to this project: * Adding a wizard to create functions, implementations, and tests in one flow, somewhat like Wikimedia Commons' upload wizard * A sandbox for experimenting without changing mainspace functions, and maybe letting non-functioneers connect implementations ([[Project: Sandbox]] doesn't seem to fit this) * We could have functions for creation based on the sandbox, like how Wikipedia has articles for creation and edit requests, * Maybe even another test instance of Wikifunctions, like how Wikidata has [[testwikidata:|Test Wikidata]] I really like this project and I don't mean to whine, but it certainly has a lot of pain points both for technical and non-technical people. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:41, 24 April 2026 (UTC) : It's also really complicated to localize functions, so maybe we should add another wizard for that, where you can choose a language, and then create the new function with the aforementioned function wizard, and it just automatically adds it to the related language configuration object of the related function. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:48, 24 April 2026 (UTC) :# Sounds good to me. :# A sandbox available is [[Z10119]], though an extension-provided sandbox that allows you to manipulate the types, code, and tests easily without interfering with the mainspace would be nice. :# [[WF:Suggest a function|This page]] works to some extent, though it's too messy in my opinion. :# We used to have a "beta cluster" but it [[phab:rOMWC5f625c5846b5f779473fa32c9a02d87e59215dfa|got shut down]] just over a year ago because it was broken. :[[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:07, 24 April 2026 (UTC) == Language parameters in language-specific functions == I think that an effort should be made to give the different natural language options corresponding to different English dialects, Chinese scripts, etc. more of a use (I added the test {{Z|Z34119}} to {{Z|Z26095}} and unsurprisingly it fails). There are two main problems with this approach that I can identify: * If you ask the majority of these functions to make a sentence in British English, much of the time it will give you an output with missing words, because it does not fallback to English labels in the case of a British English label for that item missing. The same applies for every other English dialect, British English is just an example here. * Uninformed editors will probably see the presence of a language parameter on these functions, consider it redundant, and remove it. [[Special:Diff/268074|I have made this mistake before]]. In my opinion, in a perfect world, all of these language generation functions would output monolingual text, and if the user asks for American English text, then American English text is what they'll get. If the user asks for Japanese text in hiragana specifically, then that's what they'll get in return. This is not as high-priority as just rendering text in the language plainly in the first place, but it's something that I feel is still worth devoting some effort to. Right now switching functions to use this paradigm is difficult because, on the one hand, I don't know if consensus tends towards this direction being ideal or advisable, and I don't want to make changes like this without at least notifying the wider community. In addition, all tests break once a parameter is added or removed, and the function editor does not recognize the change in number of parameters and therefore you have to remove the function call, re-add it along with all of its parameters it had previously (which is a tedious cut-and-paste job), and then it will work again. This is something that you can do in five seconds by just adding a few lines of JSON to the test source, but this is not directly editable from the Web browser. This tedium is largely what's preventing me from doing this on a larger scale, besides asking for comments first. If anyone has any insights or comments on this, then that would be appreciated. If a reference of functions with and without the support for language variants is needed, of course [[WF:NLG]] can be perused, but I've also my own list cataloged at [[User:Theki/functions#language]]... Of course, this thread has many similarities to [[#"language" argument for certain functions|the one above]], but this concerns me going out and making this consistent across these NLG functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:09, 24 April 2026 (UTC) :I've created {{Z|Z34122}} as an extension to {{Z|Z34039}} for larger functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:34, 24 April 2026 (UTC) :Just to confirm that I, for one, support a Natural language parameter for all natural-language functions. The concern about getting them all aligned is just that we haven’t finally settled on {{Z|Z11}} being preferred to {{Z|Z89}} or some other type that conserves the text’s provenance, so we risk having to change them all again. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:07, 25 April 2026 (UTC) == “Key not found ()”? == What am I doing wrong in {{Z|Z34137}}? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 00:39, 25 April 2026 (UTC) :You were passing a [[Z6091]] to {{Z|32290}}, but it takes a [[Z6001]]. Fixed. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:10, 26 April 2026 (UTC) ::{{done|Thank you}}! [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 14:13, 26 April 2026 (UTC) == Why is my test failing? == Hello! I recently made {{Z|Z34139}} based on [[wikt:Module:bg-translit]], and the test case {{Z|Z34141}} is failing on both implementations, despite the expected output and actual output being the same as far as I can tell. I tried looking at the Unicode codepoints of the output, but those are also identical. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 06:21, 25 April 2026 (UTC) :Yes, it’s a tricky one. I’ve added a normalize step to the result validation in {{Z|Z34141}}, which confirms it is a normalization issue. It looks like it is in the code but I don’t know whether simply normalizing the result is the way to go. Logically, you would normalize both the input and the result. The implementations of {{Z|Z10384}} show you how to do this. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:41, 25 April 2026 (UTC) == Edit request == Hello! I have an edit request for {{Z|Z23752}} and {{Z|Z23414}}. Please replace all the "an/a" logic with <code>Z21739(Argument reference)</code>, both for readability and for more accuracy ("a university is an institution") <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:50, 25 April 2026 (UTC) :{{D}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:24, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #245 is out: The Foundation's search for the perfect language == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-25|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present an academic paper about Abstract Wikipedia, we discuss our latest Type created, and we take a look at the newest created functions. 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:54, 25 April 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=30325620 --> :@[[User:Sannita (WMF)|Sannita (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], technical meta-question: the newsletter quotes the article: ::the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016) :This quotation sounds sensible, but the article's [https://link.springer.com/article/10.1007/s00146-026-02899-w web version], and the PDF that is downloadable from the same page doesn't actually show the emojis. It rather shows text that looks lacking: ::the only way to contest its algorithm is to click or (Crawford and Gillespie [https://link.springer.com/article/10.1007/s00146-026-02899-w#ref-CR14 2016]) :Where did you get the emojis? Is it your (probably correct) guess or is there a version somewhere that actually shows the emojis? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:16, 25 April 2026 (UTC) ::Scratch that. I've found a version with correct emojis: https://wikihistories.github.io/wikilambda-the-ultimate/ [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:37, 25 April 2026 (UTC) == Requested deletion of test == Please delete {{Z|Z34143}}. this was never valid Bulgarian, I messed up. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:19, 25 April 2026 (UTC) :[[WF:RFD]] please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:40, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|talk]]) 00:57, 26 April 2026 (UTC) </bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == Is it OK to connect the implementation? == Hello! I recently applied for functioneer on [[WF:RFG]], and I was wondering whether I could connect the implementation for {{Z|Z34165}} despite its dependency {{Z|Z34149}} being currently unimplemented. That is <em>if</em> I get accepted. I am planning on implementing it based on [[wikt:module:bg-nominal]], but am still having trouble figuring it out for now. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:04, 26 April 2026 (UTC) == Past tense function == Is there a function like {{Z|Z26039}}, but for the past tense (e.g. "Leo Tolstoy <em>was</em> a writer.")? If not, I will create it myself, I just want to make sure there's not a duplicate. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:10, 26 April 2026 (UTC) : {{Done}} with {{Z|Z34224}}, but I have a few kinks to work out with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:35, 26 April 2026 (UTC) :: I need to create some other similar functions for the past tense, I have some ideas: ::* {{Z|Z26095}} ::* {{Z|Z32643}} ::* {{Z|Z28016}} ::* {{Z|Z26570}} ::* {{Z|Z33975}} ::* {{Z|Z27243}} ::* <ins>{{Z|Z26627}}</ins> ::* <ins>{{Z|Z27627}}</ins> ::* <ins>{{Z|Z27173}}</ins> ::* <ins>{{Z|Z29591}}</ins> :: :: Are there any I have missed? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:57, 26 April 2026 (UTC) :I think that here we are starting to walk on dangerous waters: what does past mean? Is it a recent o a far past? Does it have ripercussions on the present or not? Is it just a thing that happened once, many times or for a continuative period of time? :Consider that various languages distinguish between many different types of past. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:38, 26 April 2026 (UTC) :: {{re|Dv103}} That is a fair point... :: How do we go about solving this problem though? I don't think having every sentence on Abstract Wikipedia be "X is a Y" is a very good idea. :: Maybe we have different functions for all these variations of past you mentioned that just map into "X was a Y." in English? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 13:31, 26 April 2026 (UTC) :::To properly solve this problem, we should use a more complete abstract content representation model, like for example the proposal of [[Wikifunctions:Type proposals/Semantic unit|Semantic units]] (look at [[Wikifunctions:Type proposals/Semantic unit/Douglas Adams|the example]] to see how times could be handled). For now, since we're still stuck with single fragment generation functions (that I hope will be slowly replaced with the complete represenation model, when available), we could just restrict your function to a very specific meaning, like "subject was an instance of, for most of its existence" (which means for example that it could be used to say "Douglas Adams was a writer", but not "Abraham Lincoln was a president", since he only was a president for 4 years). Probably my definition is still too vague, and this is why we need to go beyond these fragment generating functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:47, 26 April 2026 (UTC) ::Nitpick... I don't like that it outputs a string instead of monolingual text. With {{Z|Z26039}} it's used so much that I think it's unfixable in that case beyond deprecating it if people care that much, but {{Z|Z34224}} doesn't even have any connected implementations yet. Consider it, maybe? ::Nitpick 2... {{Z|Z34227}} is missing a language parameter. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:08, 26 April 2026 (UTC) ::: I will consider that! ::: I just did that because that's what {{Z|Z26039}} does, so I assumed I should follow suit with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 26 April 2026 (UTC) == Legacy functions == If and when more robust methods of abstractly representing and generating linguistic content come around, and more efficient ways of creating abstract content are devised and implemented, I suspect that our current methods will require some form of deprecation. This is a significant source of concern for me in relation to WF and AW, questioning how prone our current methods of doing things are and eventually will be prone to obsolescence, and how it will be worked around when it comes. We have over 1 250 articles on AW presently, and these are rather all over the place. I suspect the maintenance burden from keeping these articles up to code will eventually, err, creep up on us, I suppose, and some kind of major refactoring will be necessary. We are definitely in a period of experimentation and whatnot right now but eventually, like with enwiki, some sort of structure and rigor will form and I suspect it will start to become rather boring for me... I, for one, very much enjoy experimenting with new and better ways to do things here. I don't personally mind changing things to use a new and better paradigm if need be, that sort of thing highly excites me, but of course there will be things that are left behind, and I suspect maybe bots will be employed to deal with this? A lot of Wikipedia sister sites seem to do that, e.g. going and fixing up use of deprecated templates. Considering the nature of Wikifunctions and Abstract Wikipedia I suspect certain maintenance tasks will be made simpler or even trivial by the typical uniformity of our implementations. I guess I am just concerned if Wikifunctions or Abstract Wikipedia will ever accrue its own kind of "technical debt" with how we are plowing through things presently, and if there is a plan for how we will eventually seek to mitigate that. Maybe too early to ask this question, but I am a notoriously anxious person, so I thought it wouldn't hurt to raise the question regardless... &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:30, 26 April 2026 (UTC) :I very much agree, thank you for expressing my position so well. {{ping|Immanuelle}} has been using an AI-generated tool (well, they haven't edited in a week, perhaps it's a break or perhaps they don't wish to contribute to the project any more) to create a bunch of articles en masse, which I have warned them multiple times is a bad idea (on top of evolving functions, all of the articles are one-sentence-per-paragraph, [[abstract:Q12184|like so]]). That's why I've been avoiding creating articles recently, I'd say I have a good fourth (no data to support, rough guess) of the comments on the wiki, yet less than a percentage of the article count (only three, including the [[abstract:Q319|first article]], though, so perhaps I'm the next [[w:Special:Permalink/908493298|office.bomis.com]]). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:41, 27 April 2026 (UTC) :: I feel that the overwhelming presence of these low-quality articles (which I admit I myself am [[abstract:Q1710970|guilty]]/[[abstract:Q7601858|of]]/[[abstract:Q39338|creating]], usually as testbeds) may incur a large maintenance burden. I do expect them to be easy to detect, however, as searching for the presence of "deprecated" NLG functions is trivial, and it is possible that replacing them with their future ''even abstracter&trade;'' counterparts could be done automatically since they all have the same signatures and can be expected to create the same form of sentence. If it needs to be done manually for a while or for certain delinquent instances, my hope is that it will be fun, at least for a while. :: I just hope that these hypothetical future waves of "this new and versatile way of abstractly representing linguistic content" obsoleting previous methods and requiring refactoring across all articles is only a one-time thing. We should strive to be as robust and flexible as possible from the outset as each brand new paradigm of abstraction is also a brand new maintenance burden for updating old articles. At the end of the day, at least ''some'' of these articles will still render to many different languages even if their methods of creating those sentences of theirs is completely outdated. Ergo, the time it takes for the switchover to be performed across our articles should not be a persistent inconvenience for users (as, of course, they will always still be able to read the content as it was before since these legacy functions aren't being deleted outright), and the increased availability that the new methods will bring about will likely act as motivation for them to join the effort in refactoring (&#x300C;You're telling me that if I rewrite this article in this cool Lisp-looking stuff then I can probably read it in [[abstract:Q9307|Galician]]?? COOL!&#x300D;). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 20:26, 27 April 2026 (UTC) :::Totally agree. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:54, 28 April 2026 (UTC) :::My vague plan is to implement a default function returning an {{Z|Z89}}, for each language-neutral function. A single function would convert any of these to a {{Z|Z11}}, so that a composition of the two can be implemented as the current default until such time as the language-neutral function is ready to return a [[Z89]]. We can already convert a [[Z11]] to a [[Z89]] so, although there is more to be done in this space, existing language-specific functions could be adapted to return a [[Z89]] quite mechanistically. :::Although we certainly could deliver parallel Z89 functions for each existing Z11 function, I don’t think we should assume that particular outcome. Provided the Z89 captures a lang attribute from the Z11’s language tag, the two representations should be largely interchangeable, although I am expecting a Z89 to carry additional attributes at the span level that would be lost on conversion to a Z11 (along with any higher-level tags and attributes). :::When I say there is “more to be done in this space”, I am referring to a new type that would allow HTML fragments to be represented as tractable Wikifunctions objects, but this is currently drafted only in my head! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:21, 29 April 2026 (UTC) == Filtering types of objects == Hello! I have tried to comb through my own edit history several times, but it's really hard to search for specifics because there's no differentiation between different types of objects (functions, implementations, tests, etc.) in the logs as far as I can tell. Am I missing anything? I want it to work sort of like how filtering by namespace works. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 27 April 2026 (UTC) :There is differentiation, it's just rather hard to look through. Since all ZObjects are just JSON data at their core, you can search for instances of <code>{ "Z1K1": "Z[type]"</code>. I haven't tried this so I'm not sure how well it would work and I know MediaWiki search syntax treats quotation marks as a special character, but I have seen Wikifunctions pages link to searches using this before. There is also [[Special:ListObjectsByType]] but it is sitewide rather than specific to your edit history in particular. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:59, 27 April 2026 (UTC) ::''[It doesn’t help directly here, but please see [[WF:Find]] for more details of how this works.]'' [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:24, 29 April 2026 (UTC) :See the feature requests [[phab:T399244]]/[[phab:T373735]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 06:06, 28 April 2026 (UTC) :The lack of filtering edits by namespace is exactly the problem that I was trying to solve with the [[User:Amire80/wikifunctionsanalytics]] tool. :I even kind of succeeded, but it has two major problems: :# It doesn't have any real frontend, so you have to know some SQL to use it (or ask other people who know SQL). :# It doesn't get information from the live site, but from the dump, which appears to be updated once a month. :I've made a [https://quarry.wmcloud.org/query/104794 sample query for you]. Unfortunately, it won't do anything at the moment because of the second problem—your edits started in April 2026, which isn't over yet, so the dump for it hasn't been processed. But I hope that early in May you'll be able to use the same query and see something useful. :(I plan to add support for recent edits, but I haven't done it yet. Now that I more or less figured out how to process Wikifunctions edits, I'm focused on trying to understand Abstract Wikipedia edits. Processing up-to-date edits from both sites will possibly be the next thing I work on, but if you know some Python and want to try doing it yourself, don't wait for me—[https://gitlab.wikimedia.org/toolforge-repos/wikifunctions-analytics Patches welcome].) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:51, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]], I've just updated the data until the end of April. Now the query to which I linked above gives some results. You can also try running other queries if you know SQL. (Or try asking for other queries if you don't.) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:26, 3 May 2026 (UTC) == [[Z34213]] == I'm not quite sure why this implementation is failing. Could someone take a look? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:24, 28 April 2026 (UTC) :I've [https://phabricator.wikimedia.org/T419933#11863997 notified] the team that this is still occurring, the issue was marked as resolved. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:52, 28 April 2026 (UTC) :Some useful tips: :* create more testcases: sometimes it is a random error, so try to see how consistent it is between testcases :* your implementation is very inefficient, since it fetches items and lexemes a lot of times. Ideally, each item and each lexeme should be only fetched once in all the execution tree. :[[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 06:06, 28 April 2026 (UTC) ::Caching (''should?'') means that the lexeme and item data are cached, so the call doesn't actually execute multiple times. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:51, 28 April 2026 (UTC) :::Are lexemes and items actually cached within the same function execution? Even if they are only partially fetched and/or fetched in bulk? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 17:54, 28 April 2026 (UTC) ::::I don't have any evidence to prove that it works but that's definitely A. what's supposed to happen and B. the ideal behavior. This happens because the Z680X functions can be cached just like any other. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 28 April 2026 (UTC) ::::It is unclear. In general, I believe identical branches are resolved only once in orchestration, but there is also independent caching of Wikidata fetches. ::::According to @[[User:DMartin (WMF)|DMartin (WMF)]] ([https://t.me/Wikifunctions/30374 on Telegram]): ::::<blockquote>Well, no. We have caching of Wikidata entities that have been retrieved, but not of the results of nested function calls. There is a proposal for doing this in the context of the V2 composition language, when it's a bit more mature, and it's regarded as a relatively high priority.</blockquote> ::::It’s hard to tell whether fetches in nested calls are, in fact, cached and available for other nested calls in the same call, since it is not generally the actual fetch that consumes the most resources. Rather (I believe), it is construction and transmission of the result object, which is currently repeated afresh in each nested call (unless it is in an identical branch). ::::I hope that’s clear, and I apologise in advance if it happens to be inaccurate! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 29 April 2026 (UTC) :::::Oh, I should clarify.  There is a lot of caching going on, in several different places.  Lexemes and items ''are'' cached by the orchestrator within the same function execution, even if they are only partially fetched and/or fetched in bulk.  When I said that we don't have caching of the results of nested function calls, I meant that's not happening in general, for all nested function calls in compositions.  But fetching of Wikidata entities gets special treatment, so yes, fetched content from Wikidata is cached, regardless if it was fetched by a top-level call or a nested call. :::::It is also true that the construction of a ZObject from the fetched JSON might happen more than once within the same function execution, depending on how a composition has been structured. However, the construction of the ZObject is actually very fast, compared to the elapsed time of getting the JSON from Wikidata. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 18:04, 1 May 2026 (UTC) == Question about cardinal numbers == I was about to edit {{Z|Z16435}} to add my function {{Z|Z34308}}, but I noticed that none of the other functions have a gender parameter. Should I create a new wrapper function "Bulgarian cardinal, neuter", or should I just remove the gender parameter and always return neuter? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:39, 28 April 2026 (UTC) :The “cardinal” functions should return the words used for “counting” numbers in the abstract. :We should consider converting them to return a {{Z|Z11}} rather than a {{Z|Z6}}. It may even be appropriate to return a {{Z|Z12}} to cater for language variants. Either way, I think that would be the approach to adopt for inflected forms, unless reference to specific lexeme-forms is required. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:52, 28 April 2026 (UTC) ::This. If a native of your language were to count up, which form would they be most likely to use? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:29, 28 April 2026 (UTC) ::: {{re|GrounderUK|Feeglgeef}} Thanks for both your input! ::: I relabeled the aforementioned function to {{Z|Z34308}}, and created a new wrapper function {{Z|Z34457}}. ::: Should I specify that my old function is a monolingual text in parentheses? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:26, 28 April 2026 (UTC) ::::You don't have to, unless you think that is something that would require distinction when viewing the function in a list of search results &c. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:36, 28 April 2026 (UTC) == Optional/nullable function parameters == Hello! Recently, I was informed that Wikifunctions has no optional/nullable function parameters as of now. Are there any future plans to support this, and/or workarounds? Maybe create a union type system like "{{Z|6}} or {{Z|23}}". <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 17:53, 28 April 2026 (UTC) :What I do for this is use an "is empty" function corresponding to the type of the parameter in an If statement. If it isn't empty, the function works as intended. Otherwise, it does something else. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:58, 28 April 2026 (UTC) :Unions are not a thing (yet) on Wikifunctions, but you can always define an argument of type {{Z|Z1}}, which means that all types are allowed (I already did this for {{Z|Z26737}}; note that it is still a ugly workaround, don't use it for high level functions). Also, note that usually on Wikifunctions we use {{Z|Z24}} as the null value. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:00, 28 April 2026 (UTC) :: {{re|JJPMaster|Dv103}} Thanks for your help! :: @[[User:Dv103|Dv103]] told me a function call with a missing parameter is treated as an invalid function call, so how does the "is empty" function work with that? :: Also, setting the type to {{Z|1}} seems naive, like setting the type as <code>any</code> in TypeScript... :: Related question: Are there plans to add default values to parameters (outside of "if empty")? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 18:19, 28 April 2026 (UTC) :::Setting the type to {{Z|Z1}} is actually naive, and that's why I advised you to only use it for low-level functions. Currently there is nothing better. Sometimes, type correctness is not actually checked, so it might seem that nullable types are possible. But it is still an hack, and it could broke anytime since it is not intended behavior. :::I don't think that there are current plans to add default values (but correct me if I'm wrong). The closest thing that comes to my mind is that, if you incorporate Wikifunctions into Wikitext, you can leave empty some fields (only of some specific types) and Parsoid will replace them to their default value. This is done only depending on the type, and not on the functions. For example, {{Z|Z6091}} and {{Z|Z6001}} are assigned the QID associated to the page, and {{Z|Z20420}} is assigned the current date. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:56, 28 April 2026 (UTC) :::@[[User:QuickQuokka|QuickQuokka]]: At the very least, [[Z10008]] accepts a null input. Maybe that feature is unique to the String type—I am not sure. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 19:10, 28 April 2026 (UTC) ::::I think it's just not checked, but it shouldn't be intended. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:20, 28 April 2026 (UTC) ::::Strings and typed lists can be “empty” in the sense that their length can be zero. Typed pairs may also be “empty” in a degenerate sense, but such an object will not be returned from a code implementation. A typed map with no entries will also fail to be returned from code, although it is fine in compositions. ::::For a genuinely optional parameter, I prefer a properly typed list, which at least encourages an argument of the correct type. {{Z|Z813}} is also typically faster than {{Z|Z10008}}. Quite a good example of this approach is {{Z|Z23723}}, where it helps to resolve the type union (using [[Z1]]) for both Z6003K1 and Z6003K3. Of course, there’s nothing to prevent more than one element in the list, but additional elements are easily ignored. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:55, 28 April 2026 (UTC) :Pinging {{ping|Jdforrester (WMF)|prefix=|p=}}, I believe there are no current plans. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:02, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]]: I'm afraid there are no current plans to build out optional params, indeed; we would be happy to review this if a compelling case was made, but it'd be a lot of work to re-build the [[Wikifunctions:Function model|function model]] with that support and ensure we don't break (too many) things. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:11, 28 April 2026 (UTC) == Z6830 for Chinese == I was trying to use {{Z|Z6830}} for implementation in the Chinese-language. And turns out most of the Lexeme on Wikidata is using [[d:Q727694]] as the language instead of [[d:Q7850]]. This makes it impossible to use the mentioned function above, since Standard Chinese is not available (or did I miss something?). Is there a way to fetch lexemes with language=[[d:Q727694]] from item? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:20, 30 April 2026 (UTC) :@[[User:Sun8908|Sun8908]] There is [[Z1006]] for Chinese and it has the language code zh. There is an overview of languages in [[Module:Wikifunctions label]] so you can search there for chinese versions and choose the one you need. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 5 May 2026 (UTC) ::I know that. The problem is when using the function [[Z6830]], it cannot retrieve lexeme with language [[d:Q727694]] (but it is the "Chinese language" with the most current Wikidata lexemes, see [https://ordia.toolforge.org/language/ ordia]). I think it should be a Wikidata problem, I might fix it (possibly by creating the same lexemes with language code zh) on Wikidata. Thanks anyway. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 05:39, 6 May 2026 (UTC) :Could you provide an example of a Chinese lexeme that has a linked Wikidata item, or a Z6830 function call that fails to find such a lexeme where one exists? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 07:55, 6 May 2026 (UTC) ::Here: [[d:Lexeme:L846083]]. I think that's a primary reason of me trying to look into this problem, as the label in zh for [[d:Q6256]] (country) is not a single phrase (see its talk page on WD for more information). This makes some Abstract Wikipedia articles very weird in Chinese when {{Z|Z26570}} is used, so lexeme could potentially fix that. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 10:33, 6 May 2026 (UTC) :::Thank you. It looks as though {{Z|Z6830}} [https://www.wikifunctions.org/view/en/Z6830?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z6830%22%2C%22Z6830K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q6256%22%7D%2C%22Z6830K2%22%3A%7B%22Z1K1%22%3A%22Z6092%22%2C%22Z6092K1%22%3A%22P5137%22%7D%2C%22Z6830K3%22%3A%7B%22Z1K1%22%3A%22Z60%22%2C%22Z60K1%22%3A%22cmn%22%2C%22Z60K2%22%3A%5B%22Z6%22%5D%7D%7D returns that lexeme for language tag "cmn"]. Perhaps that tag should be added into the helpers for {{Z|Z24144}}? If it is widely used for lexemes, perhaps it should have its own {{Z|Z60}}? In any event, improvements might be considered under [[:phab:T390563]] (or otherwise), including amending [[Z6830]] to also consider "cmn" (and "zho", "chi"…?) when requests are made for "zh-hans" or "zho-hant" (or others?) @[[User:Winston Sung|Winston Sung]] @[[User:DMartin (WMF)|DMartin (WMF)]] [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:22, 6 May 2026 (UTC) ::::If you go to [[d:Special:NewLexeme]] and put in [[d:Q727694]] as the language, it is going to tell you it has an unrecognized language code. So I believe "cmn" should not be a {{Z|Z60}} by default? I also started [[d:Wikidata:Project_chat#Lexemes_with_language_Standard_Chinese_(Q727694)|a discussion on WD]] regarding this. I guess we can still use it as a fallback language though if possible. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 03:43, 7 May 2026 (UTC) ::::We don't have a separated <code>cmn</code> BCP 47 language subtag in MediaWiki and Wikidata at the moment. <code>zho</code> and <code>chi</code> are ISO 639 language codes but not BCP 47 language subtags. ::::For Modern Standard Mandarin, please use <code>zh-*</code> language tags for now. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 15:26, 8 May 2026 (UTC) == Key not found error == Is there a reason why I am getting key not found error for this [[Z34677|function]] {{Z|Z34677}}? All the underlying functions run and all the test cases work. The debug information does not give more details. Any pointers? Thanks in advance [[User:Jsamwrites|John Samuel]] 19:24, 1 May 2026 (UTC) :It was passing the [[Z6091]] to {{Z|34641}} when that takes a [[Z6001]]. I've fixed that, but there's some other problem with the logic, so I've left it disconnected. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 19:42, 1 May 2026 (UTC) ::@[[User:YoshiRulz|YoshiRulz]] Thanks a lot. [[User:Jsamwrites|John Samuel]] 20:21, 1 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, 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:21, 2 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=30325620 --> == Any formal process for deletion of pages == Does a formal process exist for the deletion of functions, implementations, and tests that includes a notification system for creators, analogous to Wikidata’s process, explaining the rationale behind the deletion (or proposal for deletion)? [[User:Jsamwrites|John Samuel]] 12:36, 3 May 2026 (UTC) :Does [[Wikifunctions:Requests for deletions]] work? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:00, 3 May 2026 (UTC) :Please see the discussion at [[Wikifunctions talk:Requests for deletions#Should we expect Objects' creators to get pinged on deletion proposals?]]. :As I see it, it is the proposer’s responsibility to consult appropriately before making a request and we expect our administrators to act only when satisfied that appropriate consultation has occurred. In many cases, no consultation is required. Administrators may delete their own contributions without making a request, but this is not a practice I would encourage. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:51, 3 May 2026 (UTC) == Implementation of rational number in JS doesn't match in Z19677 (Rational number) and Z28579 (RGBA colour) == In {{Z|19677}} it's <syntaxhighlight lang=js> { "K1": sign * numerator, "K2": denominator } </syntaxhighlight> but in {{Z|28579}} it's <syntaxhighlight lang=js> [ sign * numerator, denominator ] </syntaxhighlight> '''<span style="font-family:Iosevka,monospace">[[User:沈澄心|<span style="color:#9f3526">dring</span>]][[User talk:沈澄心|<span style="color:#534fa3">sim</span>]]</span>''' 05:15, 4 May 2026 (UTC) == Nested functions in compositions == I wish it will be easier to a add another function about a specific existing function in a function implementation based on a composition. When I write long functions in spreadsheets I usually stat with a small part and then I try to go further and after important steps I test if the output is as expected. I created [[Z34826]] to get the German gender specific occupation lexeme for a specific person based on their gender. I wanted to add a function around the existing one and it was not successful. It is not very easy to implement as it requires the possibily to move a part to another section but I think it can be helpful if it will be implemented. So far I spend more time as expected on the function. Describing it with words what the function needs to do is much easier than implementing it here in Wikifunctions. So I think there needs to be improvement to make Wikifunctions more accessible. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:10, 5 May 2026 (UTC) :Have you tried to use the copy-paste functionality? It is very useful to move parts of composition arounn. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 07:12, 6 May 2026 (UTC) :I've also found the composition editor to be wholly unsuitable for any expressions more than a few levels deep. (Even with the <code>localStorage</code> clipboard, because of its overzealous type checks.) Compositions naturally grow out from the "leaves", the immediate operations on the inputs, while the interface really wants you to build from the "root". I mostly use the [https://yoshirulz.gitlab.io/WikiLambdaBlockly drag-and-drop block editor] which I made to smooth over some of the site's problems, so if you want to try that out and give me some feedback I'd appreciate it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 14:36, 6 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the 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 [[: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/1778520600 May 11, 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]]) 11:16, 8 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=30325620 --> == RGBA colour, spelling... == Something that has always irked me a little bit is the spelling of [[Z28579|RGBA colour (Z28579)]]. I guess this is not unsurprising for me considering my use of US English but I think there is more to it than preference and I want to try to argue for it being changed to use American spelling. I know that this probably has a snowball's chance in hell of actually garnering any support, so I won't really be miffed if the spelling remains as it is, but I thought it wouldn't hurt to raise this regardless. The main issue I have with it is the spelling of the original proposal. When infernostars raised the [[Wikifunctions:Type proposals/RGBA color|type proposal]], the spelling was 「RGBA color」. Of the comments that mentioned the word 「colo[u]r」, two used British spelling while six used the American spelling as used in the proposal. The only thing that really pointed to the use of ''colour'' was the fact that the catalog page on color functions used that spelling already. For all intents and purposes, the spelling of the original proposal should have been maintained, but it was not; [[User:DVrandecic (WMF)|DVrandecic]], the eventual creator of the type, used a different spelling. It should be noted that there was really no reason for this to occur and while it is an undoubtedly minor issue I still believe it should be rolled back and the type should use the spelling of the original proposal and majority of editor comments. In [[abstract:Q936|OpenStreetMap]], there have been keyvalue proposals that have had the finalized spelling that gets put to use be in British English despite the original proposal being in American English; this has usually occurred with proposals relating to 「X center/centre」 tags. This makes sense on the surface, because OpenStreetMap is maintained by a UK organization, and still has close ties to Europe. The Wikimedia Foundation, however, is an ''American'' company. This is often brought up as a fallible argument when debating article spelling on the English Wikipedia, and I don't bring it up to support that 「RGBA color」 should be used for that exact reason, but rather to state that OpenStreetMap's general policy on tag names need not apply here. It appears to me that, at least initially, the majority of 「core contributors」 to Wikifunctions used British English; I can name YoshiRulz, 99of9, GrounderUK, and VIGNERON.<ref group="color">I'm avoiding linking to these folks because I don't think pinging them about this discussion is all too necessary unless they themselves want to be involved; I don't want to clutter their inboxes just to briefly mention them. I pinged Denny because, well, I'm asking him a question directly, but everyone else I would prefer to join this discussion by their own accord... not that I wish for this decision to be confused as me going 「these people use British English so they will probably oppose my idea, I won't invite them to the discussion because of that」...no, I promise you that is not the reason.</ref> I see (or saw) these people ''everywhere'', so it makes sense that British English has prevailed in some sorts on this website, but I don't think that indicates that it should be the ''preferred'' spelling across the website, at least not to the point where a proposal should have its name changed to match such a "consensus".<ref group="color">It could be argued that the front-and-center ''Function catalogue'' using 「catalogue」 is actually indicative of such a "consensus", but ''catalogue'' is in a similar position to the word ''grey'' where I live (that is, the US) in that it is used just as often as its American counterpart. Also, consider Wiktionary's ''Beer parlour'' project chat.</ref> The unnecessary modification of the original spelling is my main argument for changing it back... but of course, I must obligatorily state that on English Wikipedia, it is [[w:Color|Color]] and [[w:RGBA color model|RGBA color model]]; on Wikidata, it is [[d:Q1075|color]] and [[d:Q2325624|RGBA color space]]; in CSS (which typically uses hexadecimal triplets to specify RGBA values), the properties are <code>color</code>, <code>background-color</code>, etc.; bit of a weak jab, but on Schema.org it is [https://schema.org/color color], [https://schema.org/colorSwatch colorSwatch]; et cetera. {{Z|Z28580}} uses ''color'', so does {{Z|Z28591}} and its Python counterpart. Mr. Vrandečić, I have to ask, I'm rather confused... you created the color type using British English spelling, but you were also responsible for the creation of the equality function which uses the American English spelling. You also seem to be writing in American English for the status updates, judging by your use of -''ize'' over -''ise'' endings and use of ''program'' over ''programme'' in [[Wikifunctions:Status updates/2026-04-16]]. Is there something I'm missing or have you switched your preferred variant somewhere along the way? Anyways, do consider this if you wish... again, I don't suppose this will garner much support, it is the ''non-issuest'' of ''non-issues'', but it has irked me to the point where I want to ask about it to get some answers, if nothing else. I am not arguing for every other color function to have its name changed, just the type itself. <references group="color"></references> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 8 May 2026 (UTC) :This is a multilingual project; the <code>en</code> label is <code>RGBA colour</code> and the <code>en-us</code> label is <code>RGBA color</code>. Though I'm not able to switch to <code>en-us</code> via the language picker so that would need to be fixed.<!-- --><br>edit after reading your whole comment: The same is true of {{Q|1075}}, there are labels specified for multiple English variants. (In {{Q|2325624}} it's only an alias.) I agree that other websites' choices aren't binding on us, but from that, I conclude that the more widespread British/Commonwealth spellings should be used for the generic <code>en</code>. As for myself, I'm Aussie and I will continue to use the BrE spellings ([[w:en:Oxford_spelling#Language_tag_comparison|+ "routing"]], TIL) if only by muscle memory.<!-- --><br>[[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 17:42, 8 May 2026 (UTC) :: Your lattermost point would normally be fine in a perfect world. Wikipedia's <code>convert</code> function defaults to "international" English, which I don't personally take issue with because it happens that we here in America are actually outliers for saying and spelling things differently... err, or we were for a while at least, nowadays it seems like an even split (plus you have "yield" vs. "give way" which is effectively the logical opposite of US's use of "meter" over "metre"). :: However, this is not a perfect world, and I don't think <code>en</code> should correspond to any particular variant. It is too fragmented across all software at this point to impose such a requirement. The inability to switch to <code>en-us</code> on this website foregoes an easy and simple solution to this problem that makes everyone happy, because the yanks (such as myself) can't be happy because we can't see the labels in American English even if we wanted to, and the other folk can't switch either as far as I'm aware (and the en-CA and en-GB languages in the preferences page seems to be deprecated). My point being, <code>en</code> is abused to mean "en-UK" just as often as it is abused to mean <code>en-US</code>; I think a decision shouldn't be made on such an assumption of one "default". &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:48, 12 May 2026 (UTC) :Hi @[[User:Theki|rae]]! I have no opinion nor preference on this, and given my background, I am just entirely confused about my spelling preferences myself, as you can tell from my inconsistent usage. I learned British English in school and used that for maybe two decades or so, but moved to the US and lived there for more than a decade, enough to be naturalized, but now I am back in Europe and I am technically a professor at King's College London, soooo.... honestly, I do not know. I don't remember having put too much thought into it at the moment I created it. The good thing is that in Wikifunctions, just as in Wikidata, it is easy to change, without messing things up too much (unlike in Wikipedia), so my suggestion is, just make the change, see if anyone complains, and if they do, discuss it more. I don't know if there is a guideline already in Wikifunctions about the variants. I am happy either way, and honestly, I keep forgetting which variant is which most of the time. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 18:16, 10 May 2026 (UTC) :: I can definitely understand this, although I am unfortunately rather passionate about any minutiae involving preferential minor differences in ''anything'', of which AmE vs. BrE chiefly is. So I dedicate a lot of headspace to it. More than I should. Not that I wish to imply that the comment above that I have wrote is of an irrational nature, or done out of spite or pure emotion and subjectivity; I do genuinely believe that ''RGBA color'' is beyond just a personal preference and is just logical. I may boldly go and change it, but for some reason I was expecting that changing the English label of a Type would require elevated permissions, and I also didn't want to do it only to get immediately reverted because it ''did'' strike a chord with someone, when I could instead see how apathetic, supportive, or in opposition interested people are beforehand and ''then'' act accordingly. I was not meaning to antagonize you over your spelling habits, I did actually use British English for a few years starting in 2020 before I went back to American English, so I'd be a hypocrite for me to decry you for not always sticking to some arbitrary standard of spelling words over the other. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:55, 12 May 2026 (UTC) :Although I spell it “colour”, I think it makes more sense to use “color” for the type, since that is almost always the required spelling when the string functions as a keyword. :More generally, though, Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en". This is unusual, in my experience, as "en" is widely misused in place of "en-US", where there are recorded spelling differences. :(I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere. Use of -ize rather than -ise is a matter of personal preference or house style, but regional autocorrect encourages -ise.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:00, 12 May 2026 (UTC) :: ''Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en"'' :: Definitely agreeing with you on the latter being a good choice. However, I suspect the favoring of "colour" over "color" may be because, in terms of language codes, when sorted alphabetically <code>en-us</code> actually comes ''after'' <code>en-gb</code>. Although, the frontend seems to be sorting <code>en-ca</code> after <code>en-gb</code>, so I don't actually know how correct that is. :: ''I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere'' :: The context of the spelling was "''No program for the NLG SIG meeting for next Tuesday has been proposed''". In that usage context, I think it makes sense to assume that ''program'' is not being used to refer to a computer program, but to a ''program of events'' or similar, something that you would spell as a ''programme'' in British English. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 12 May 2026 (UTC) :{{s}} this. I'm obviously biased but I believe American English is preferable generally, American dominance on the internet (our Department of Defen'''s'''e invented it!) and rapidly-increasing consumption of American media by international English speakers means that more people use American English's conventions, this is clear through for example [http://trends.google.com/explore?q=color%2Ccolour&date=all&geo=Worldwide search trends] (though they aren't particularly reliable). Perhaps this is a bit of a supremacist opinion, but we should have internal consistency, and if we must choose, American English should be our first choice (then Indian and then British English) [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:10, 12 May 2026 (UTC) :: This is rather flawed reasoning, though. I think probably any given British or Indian person would not agree on using that as the reasoning for this, not that you are necessarily ''completely wrong'', but if this is not a good enough reason for English Wikipedia's (admittedly extremely flawed) ''ENGVAR'' policy then I don't think it's likely it will pass here either. :: Although of note is that [https://books.google.com/ngrams/graph?content=color%2Ccolour&year_start=1800&year_end=2022&corpus=en&smoothing=3&case_insensitive=true Google ngrams] agree with you, but "color" vs. "colour" is an eternal holy war that will not be won by demonstrating that more books use US spelling over Commonwealth spelling. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:44, 12 May 2026 (UTC) :::You're probably right that it's not very sound. I'm biased in that other varieties of English irk me, and that's probably mutual for people who are used to other varieties of English when they read what I write! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:56, 12 May 2026 (UTC) :I've decided to boldly [[Special:Permalink/274271|make the change]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:02, 12 May 2026 (UTC) :: Thank you. Considering both you and GrounderUK seem to consider it an okay change, I think this will do for now. :: I should note that the matter of whether to move [[Wikifunctions:Catalogue/Colour functions]] in response to this (however this discussion will ultimately turn out) is a whole other can of worms, in my view. I can't say I have an opinion on that at the moment, but I'm putting it out there regardless. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:06, 12 May 2026 (UTC) :::Personally, I'm in favor of moving the page and renaming all of the items on it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:10, 12 May 2026 (UTC) ::I don't like this (exactly because of the American hegemony you cited), but again, it shouldn't matter because the software is meant to be multilingual. Clearly there's a bug preventing you from picking an English variant/dialect as your display language. But the search bar and Function/Type autocompletion do check the English variants for matches. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 15:15, 12 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[abstract:User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:31, 11 May 2026 (UTC) :Thank you for dedicating your time to writing this, it is very informative. I will try to add input once I'm not in over my head with finals. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:27, 12 May 2026 (UTC) == Display function for HTML fragment == Currently, any collapsed Z89 literal appears as<blockquote>&lt;&gt; [[Z89|HTML fragment]]</blockquote>If I were to create a new Function which returned something like<blockquote>&lt;&gt; 123-byte HTML fragment <q><nowiki><td><span lang=</nowiki>&hellip;</q></blockquote>could that be connected to replace the collapsed form, or would it require changes to the Wikilambda software? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 16:14, 11 May 2026 (UTC) :It might work, but I doubt it. Those angled brackets suggest that the collapsed form is not simply defaulting to the type’s label. Looking at [[:phab:T410509]], I’ve concluded that enhancements to the collapsed form were never considered, rather than being actively rejected. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:12, 12 May 2026 (UTC) ::[[:Phab:T391985]] documents the original design. Note the fifth bullet point under “Acceptance criteria”. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:21, 12 May 2026 (UTC) :I'm not sure the byte-size is necessary, but the outer tag (or first outer tag, though generally I'd prefer most fragments use a wrapper tag if it needs multiple like JSX does, but that's a whole different topic) would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:51, 12 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in 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]]) 14:36, 15 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 --> == [[Z34510]] == This function, which determines if a Wikidata item for a {{q|5}} has an undeprecated {{p|21}} statement of {{q|6581097}}, returns false for {{q|173399}}, a transgender man. This is because his item assigns his P21 statement to {{q|2449503}}, not {{q|6581097}}. I'm not sure how to account for this discrepancy. Should {{z|34510}}: # Include {{q|2449503}} as a value that can lead to a true result, # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a man?") could return true for either "male" or "trans man", # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a trans man?") could return true for "trans man", # Not exist at all? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:48, 16 May 2026 (UTC) :I can't think of a single use case where you would need to determine if a person is a cisgender man and nothing else. Functions are good for generalizing across multiple possibilities when they exist, so I think it would be best if trans men were considered a part of the criteria for returning a true value. If asking for specifically {{q|6581097}}s and ''nothing'' else was desired then the function name would be a misnomer as Elliot Page is inarguably a male (at least in the view of most reasonable and intelligent people). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:03, 16 May 2026 (UTC) :You made the function in the first place; what were you planning on using it for? AW? Maybe it should return a {{Z|25501}} which can then be passed on to other NLG functions. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 May 2026 (UTC) == Lexeme from wikidata label, or "best" lexeme from wikidata item == I was looking into fixing [[Z28028]]. I found that I could add "requires grammatical feature: definite article" to "United Kingdom" (L8558). Now I'm stuck on how to get to that lexeme from {{Q|145}}. There's [[Z23471]], but that for very good reason gives you multiple lexemes with the same sense, and I just want the best one like how the label is always the best string. Is there a function that can do this? There's definitely the case of a Wikidata label that isn't a lexeme (most commonly multiple lexemes) but I'm only considering the case where it is one lexeme here. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:02, 16 May 2026 (UTC) :There is {{Z|Z27327}}, that tries to give the best lexeme through various heuristics. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 22:22, 16 May 2026 (UTC) :: Wonderful! I did stumble upon [[Z33818]] but this is perfect. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 00:25, 17 May 2026 (UTC) == [[Z29591]] isn't working for me == For instance, trying to manually put in the exact inputs for one of the test cases just returns an empty Monolingual text. See [https://www.wikifunctions.org/wiki/Z29591?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z29591%22%2C%22Z29591K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q3257809%22%7D%2C%22Z29591K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q21264361%22%7D%2C%22Z29591K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q22006653%22%7D%2C%22Z29591K4%22%3A%22Z1002%22%7D]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 01:17, 17 May 2026 (UTC) 7nmvr03ica2fk3l8wo6y5cm7uolbw8v 275636 275599 2026-05-17T03:08:09Z SpBot 978 archive 1 section: 1 to [[Wikifunctions:Project chat/Archive/2026/04]] (after section [[Wikifunctions:Project chat/Archive/2026/04#No_place_to_ask_to_activate_a_function?|No_place_to_ask_to_activate_a_function?]]) - previous edit: [[:User:JJPMaster|JJPMaster]], 2026-05-17 01:17 275636 wikitext text/x-wiki {{shortcut|[[WF:CHAT]]|[[WF:PC]]|[[WF:VP]]}} __NEWSECTIONLINK__ [[Category:Help]] <!-- please do not remove this line --> Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc. Other places to find help: * [[Wikifunctions:Administrators' noticeboard]] * [[Wikifunctions:Report a technical problem]] * [[Wikifunctions:FAQ]] {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |timeout=30 }} {{Archives|{{#tag:div|<br />{{Flatlist|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1|hideredirects=1}} |class=mw-collapsible-content|style=font-size:92%;}}|class="mw-collapsible mw-collapsible-toggle mw-collapsed"}} |prefix=WF:Project chat/Archive/ }} == "language" argument for certain functions == Hello. I am relatively new to Wikifunctions. Recently, I tried to create functions for Chinese translation of {{Z|Z26570}} and {{Z|Z26095}} (which became [[Z32788]] and [[Z32900]]). During the creation of these functions, I was trying to take {{Z|Z32212}} as reference. And I realized that the defining role sentence function is taking <code>language</code> as an argument (and the test case of the Chinese-language function already contains two varieties of Chinese). This makes it possible to output monolingual text in <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code>, or any varieties of the language. I think for this reason, it is better to have <code>language</code> as arguments for the implementation of Z26570 and Z26095, and potentially more functions that require {{Z|Z14294}}, since it would output the varieties code instead of just saying <code>zh</code> for <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code> in the output of type {{Z|Z11}}. I am not sure how the fallback mechanism works if one of the language (varieties) do not have a labels/lexemes, but to me, it is reasonable to have a <code>language</code> argument. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 09:38, 31 March 2026 (UTC) :The functions you mention do have a language argument. For Wikifunctions, the {{Z|Z60}} can be at a higher or lower level; whether a {{Z|Z11}} is for a language or a variant is determined by the function that constructs it. Please see {{Z|Z26565}} for an example and feel free to add test cases in Chinese. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:54, 11 April 2026 (UTC) ::Hello @[[User:GrounderUK|GrounderUK]], thanks for the answer. I understand that whether {{Z|Z11}} is for a language or a variant depends on the function. But that is exactly what I am asking for. It is true that [[Z26570]] and [[Z26095]] takes [[Z60]] as argument, but the language-specific functions in {{Z|Z29843}} and {{Z|Z26096}} don't. ::Let me give you an example: INPUT to [[Z26570]]: <code>entity</code>: Tokyo, <code>class</code>: city, <code>location</code>: Japan, <code>language</code>: zh-cn, the config would select [[Z33030]] (created after my previous comment by elseone) as the implementation, and it would RETURN 东京是日本的一个城市。(zh-hans), which is not zh-cn as requested in the INPUT. It would also be using the term not for the variant (when it is different) because it is hardcoded to use the term in zh-hans. However, if we have the implementation like [[Z32790]] (which was created by me but a natural language argument was added by elseone) or [[Z32213]] (that works in the defining role sentence function because of the extra argument), it could cater for different variant. ::If we don't have the language argument in the language-specific function, the desire for article creation on Abstract Wikipedia would be to create a function for every variant. Is it then better to create functions for every variant? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:18, 11 April 2026 (UTC) :::I forgot to mention that there are some hardcoding in {{Z|Z32790}} as well, but I cannot fix it because it is a connected function and I am not a functioneer. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:31, 11 April 2026 (UTC) ::::Okay, I think it’s safe to disconnect this one as the function is not yet configured for use on Abstract Wikipedia. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:04, 11 April 2026 (UTC) :::Ah, sorry… I misunderstood you. I agree that the called function should be able to accept the original language argument. That is simpler in theory than in practice, because the configured functions all have to have the same argument types, as I understand it. I’m not sure which the best approach is, really, but we probably want to avoid two levels of configuration. That suggests that all language-specific functions would need to accept the additional argument, which is unrewarding work for someone. @[[User:99of9|99of9]], @[[User:Jdforrester (WMF)|Jdforrester (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]] Any thoughts? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:57, 11 April 2026 (UTC) ::::I mean, we would need to modify all the functions in each language, which could take some time. But we are still in an early stage. If we don't fix it now and we want to fix it later, it would be a disaster. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 19:25, 11 April 2026 (UTC) :::::Agreed. And we probably want them converted to HTML too, with separate language spans for text in different languages. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:35, 11 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]: This sounds like a reasonable change to make. Note that (given these Functions are primarily for use on Abstract Wikipedia), altering/replacing them to return Z89/HTML fragments is already a desired but breaking change, so making a second breaking change at the same time is probably easiest for fixing things swiftly. That said, that's of course a decision for the Abstract Wikipedia and Wikifunctions communities, not me! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:43, 12 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]@[[User:Sun8908|Sun8908]] to make it a non-breaking change, I've created {{Z|Z34039}} which allows a composition {{Z|Z34043}}. This way you can make functions which either need the specified variant or don't! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:52, 24 April 2026 (UTC) :I have now created {{Z|Z33465}}, which is an implementation of [[Z26570]]. Maybe we can migrate to use that function when more (language-specific) functions for it are ready? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:19, 14 April 2026 (UTC) == Actual difference between {{Z|Z26039}} and {{Z|Z26095}} == What is the actual difference between these two functions? I ask, since it seems to me that the current distinction is more or less that the first one doesn't use an indefinite article in English, while the second does. Which is not a good distinction in a project that should be language neutral. This doubt emerged from my use of the first one in [[abstract:Q124441]], which @[[User:Hogü-456|Hogü-456]] made me notice that is probably wrong. My question is: why is it wrong? How could we clarify the difference? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:46, 19 April 2026 (UTC) :I think the difference is if there is an indefinite article like a or an before the subject or not. In German there can be cases where a definite article is necessary before the subject. I looked at the functions and before the object both times an article is mentioned. As it depends on the language and the word what is the correct function to use I hope it will be clarified and it is an example of the necessity to have a human with understanding in a specific language check it. I hope there will be longer functions what generate more content about a specific kind of item. Then it is necessary to write one such function per language and it can be then applied to several items. It still requires checks and so maybe it is better to write down what item category needs what kind of introduction sentence function for what language. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:05, 19 April 2026 (UTC) ::The point of these two functions (and of the entire Abstract Wikipedia project) is that they should be defined in a purely language-independent way, so that the translation to actual language can be done automatically. This is the reason why these functions have been renamed; I think that this attempt was not succesful, since meaning is still unclear. My proposal to clarify them would be to invoke the concept of [[w:specificity (linguistics)|specificity]]: {{Z|Z26039}} should be named "specific subject is instance of (string)", and should be used only when the QID of the subject uniquely identifies a single thing; {{Z|Z26095}} should instead be renamed in "non-specific subject is kind of (Monolingual text)", and should be used when the QID refers to a multitude of real life items, and we are specifying the class that all these item belong to. This clarification would not still be enough, since it doesn't explain how mass nouns are handled (is water a unique thing? Does {{Q|Q7802}} refer to a single piece of bread or to the entirety of bread, like water?). This problem is very tricky, since mass noun are language-specific and blurry the line between these two functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 20:58, 19 April 2026 (UTC) :Simply put, one corresponds to P31 and the other to P279. Paris is an {{Q|P31}} a {{Q|Q1549591}} :whereas a {{Q|Q1549591}} is a {{Q|P279}} (alias “kind of”) {{Q|Q515}}. Whether the Wikidata knowledge representation will be sufficient to resolve into fluent natural language representations in all languages is, of course, a crucial question. Where it is not, the Abstract Wikipedia knowledge representation will need to supplement the Wikidata content with additional details about the relation between the participants or the participants themselves, and these details should be language-neutral, to the extent that this is practicable. The item {{Q|Q124441}} has no [[:d:Q124441#P31|P31]] statements; it has only [[:d:Q124441#P279|P279]]s, including one relating it to {{Q|Q212920}}, which suggests {{Z|Z26095}} is the appropriate choice here even if the rendering in some languages is the same. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:52, 19 April 2026 (UTC) ::Thanks for explaining it. I think that I'll change the implementation of {{Z|Z26095}}, so that in Italian it produces more or less the same output of {{Z|Z26039}} (both with the definite article). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:24, 20 April 2026 (UTC) == Equivalent of Z6830 for lexemes == Is there an equivalent of {{Z|Z6830}} that enables retrieving all lexemes pointing to a particular lexeme using a specific property? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 21:06, 20 April 2026 (UTC) :There's {{Z|6831}} but I think that's slightly different again to what you're after. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 12:31, 21 April 2026 (UTC) ::Thanks for sharing that one, I did not know it existed. But you are right, it’s not quite what I am looking for. I want a function that would take a Wikidata property reference (like P5191, which is ‘derived from lexeme’) and a Wikidata lexeme reference, and return a list of lexemes that reference that lexeme using that property. [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 13:23, 21 April 2026 (UTC) == Storing huge datasets == It is not a necessity I suppose, but an idea came to me earlier to write a function that would give the corresponding [[en:Shavian alphabet|Shavian alphabet representation]] of an English word written with the Latin alphabet, or perhaps apply that operation to an entire sentence. However, just trying to guess as to what the IPA pronunciation of each word passed into it could be is is both not ideal (pronunciations obviously can and will vary widely between accents) and infeasible <s>(Wikidata lexemes don't really seem to account for pronunciation)</s>. It happens, though, that a comprehensive Shavian dictionary exists named the [https://readlex.pythonanywhere.com/ ''Read Lexicon''], which uses pronunciation and spelling similar to that used by the creator of the alphabet himself. This would be a good dataset to use in performing this translation in the function, but it appears that, all in all, the total size of the dictionary is [https://github.com/Shavian-info/readlex/blob/main/readlex.json ''nearly 26MB''] when formatted as JSON, which would certainly be larger when converted into a typed list. I am wondering if this will ever be feasible or admissible, or if there is really a way around this if importing such a large set of data is deemed impractical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 22:30, 20 April 2026 (UTC) :{{re|Theki}} "Wikidata lexemes don't really seem to account for pronunciation"" is patently untrue; not only does every Bokmål lexeme form have IPA attached to it (thanks to Jon Harald Søby), but there are lots of languages--including English--that have pronunciation information, whether through IPA or otherwise, indicated on their forms. The big issue of course is that adding this data is not always possible to perform efficiently--for instance, I'd love to have Yiddish pronunciation respellings from Paul Abelson's dictionary on as many English forms as possible, but this dictionary not being previously processed makes this difficult. The data set you have brought up, if a suitable reading of [[:m:Wikilegal/Lexicographical_Data]] allows it, could be added as {{P|7243}} statements on various English forms. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 23:20, 20 April 2026 (UTC) ::Well, sorry... I haven't witnessed these pronunciation statements before, I wasn't aware of their existence until you pointed it out. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 21 April 2026 (UTC) :I got 1,900,000 characters into [[Z33875]] before the UI gave up on me. I'm not sure what the limit is. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:21, 21 April 2026 (UTC) == Could not serialize input JS object: Number <small><small>[insert tested number here]</small></small> == I'm not one to throw my problems at others, but I have no idea how to fix this. Am implementing {{Z|Z24602}} in JavaScript, which requires returning a typed map. It now works for every type of value except numbers. Tried explicitly converting the numbers to float64, but either way it throws the error above. Would appreciate it if anyone could diagnose or fix the problem, as my knowledge of Wikifunctions is amateur at best. Thank you. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:32, 23 April 2026 (UTC) :The quick answer is that like some list-related functions, code implementations returning typed maps are not possible unless the type of the objects in the map is specified in the function signature (e.g. if it was a map from Strings to Natural numbers only). So unfortunately, I think you've chosen a function that is not really possible at the moment. There are a few ideas of how we might address this, but for the moment, work on something else. Sorry! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:21, 23 April 2026 (UTC) :Maybe explicitly using [[Z13518|natural numbers]] would work? I would try using <code>{ "Z1K1": "Z13518", "Z13518K1": "[number]" }</code> to represent numbers, perhaps, and seeing if that works. Of course, you would also probably have to adapt this for other types that cannot be serialized, and I'm not sure how easy that would be to generalize (assuming [[w:Don't repeat yourself|DRYness]] is desired). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:39, 23 April 2026 (UTC) == Help with creating a function for Abstract Wikipedia == Hello! I was inspired by {{Z|Z26570}} to create {{Z|Z33975}}, however I'm not sure how I add specific language implementations here. Can anybody help me? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 10:41, 23 April 2026 (UTC) : I think I figured it out, I created a new object with the language config type, added {{Z|Z14310}} to my implementation, and added a new function for English... At least I think that's how it works... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 13:16, 23 April 2026 (UTC) ::You have the right idea, as far as I know. I went ahead and connected the implementations you created as they appear to work fine for English, and added a test for {{Z|Z33975}} (which passes [[File:Twemoji 1f601.svg|24px]]). I also corrected an error you made on the config object where you appear to have accidentally connected English to {{Z|Z33975}} instead of {{Z|Z33977}}. Thank you for contributing! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 23 April 2026 (UTC) ::: {{re|Theki}} Thank you so much for you help! Could you please kindly also connect the implementations for {{Z|Z33986}} which I just made, which is going to be used for the Hebrew implementation of {{Z|Z33975}}. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:11, 23 April 2026 (UTC) ::::You seem to be returning the wrong type in both implementations. Functioneers should not connect implementations that don't work for non-functioneers. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:13, 23 April 2026 (UTC) ::::: {{re|Feeglgeef}} Oh thank you for pointing that out! I am still a bit new to this project and confused, so I need to read up some more about this. How do I return a monolingual text object? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:17, 23 April 2026 (UTC) ::::::I'm trying to fix it for you, the construction of ZObjects in code implementations is a bit difficult right now. Since the State origin using entity and class function will (presumably) be composition, perhaps {{Z|33975}} can be adjusted to return a string, using {{Z|26107}} and {{Z|26107}}? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:21, 23 April 2026 (UTC) :::::I did not notice any discrepancies from looking at the functions by themselves, and it seemed to work fine on my end. Is it bad practice for NLG functions to return the monolingual text type? I had assumed it was logical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:24, 23 April 2026 (UTC) ::::::Both implementations are failing all three tests on my end. No consensus has been established as to whether monolingual texts or strings should be used, so it's like the [[w:War of the currents|war of the currents]] but for Wikifunctions. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:27, 23 April 2026 (UTC) :::::::Oh, you were referring to {{Z|Z33986}}. I assumed you were stating that something was wrong in the earlier English functions that I missed; I apologize for the misunderstanding. Has there been any centralized discussion on this string vs. monolingual text issue? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:31, 23 April 2026 (UTC) ::::::::Not that I'm aware of, I've brought it up on the telegram twice before, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:49, 23 April 2026 (UTC) ::::::::The centralised discussion is at [[WT:Abstract Wikipedia/2025 fragment experiments#Proposed recommendation: Fragments should return Z11/monolingual strings]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:19, 24 April 2026 (UTC) ::::::: {{re|Theki|Feeglgeef}} Can only functioneers test implementations? For me I can't test it at all... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:32, 23 April 2026 (UTC) ::::::::AFAIK, test cases are only immediately testable during editing of a function if they are connected. This is one of my personal pain points with Wikifunctions, iterating on functions without exhaustive connected test cases makes debugging practically impossible for non-functioneers working on newly-created functions... I (or Feeglgeef) can quickly connect the tests you need for you if you want, although if they are not well-formed they may need to be disconnected again afterwards. Additionally, I could temporarily connect the implementation you are writing so that you can test it on the sidebar as you work, but I'm not sure if this is advisable. That functionality is also something that unfortunately only works when not disconnected. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:43, 23 April 2026 (UTC) :::::::::Yup, agree with you on all points, thanks. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:48, 23 April 2026 (UTC) == Please disconnect implementation == I think I've fixed my issue with {{Z|Z33986}}, but I can't edit an actively connected implementations with my rights. I must admit it is an AI-aided fix, I feel very strongly about disclosing that. Courtesy pinging [[User:Theki]] and [[User:Feeglgeef]]. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:51, 23 April 2026 (UTC) : Additionally, I think the JS might be working. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:52, 23 April 2026 (UTC) : Just to clarify, I mean disconnect the Python implementation please. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:53, 23 April 2026 (UTC) :{{Done}} I've disconnected the Python implementation. :I've also added a couple of tests. The rule is a bit more complicated than adding a maqaf before every character that is not a Hebrew letter. Unfortunately, I don't think I'll have time to fix the implementations any time soon. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:03, 23 April 2026 (UTC) :: Thank you! :: Also, for some reason I thought you put a maqaf before all gershayim, so thanks for correcting me. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:09, 23 April 2026 (UTC) :::No, that's not the rule. :::The rest of this reply is an [[:wikt:info-dump|infodump]], feel free to ignore it :) :::In [https://hebrew-academy.org.il/topic/hahlatot/punctuation/ the Academy's punctuation rules], the rule for adding a maqaf is written kind of badly: שמים מקף ברצף שיש בו שני סוגי גופנים, כגון אותיות ומספרים ("maqaf is added in a sequence in which there are two types of fonts, such as letters and numerals"). These are not different types of "fonts", but different types of characters, and I should email them about it. It gives the examples <span lang="he" dir="rtl">ה־12</span> and <span lang="he" dir="rtl">ב־DNA</span>. It doesn't say anything explicitly about quotation marks, but in other places on the same page, you have stuff like <span lang="he" dir="rtl">ב"הארץ"</span>, and from that I deduce that a maqaf is not needed before double quotes if there are Hebrew letters inside the double quotes. :::That said, a few people do think that there must be a maqaf before double quotes. I have a somewhat surprising example of somebody who always does it: translators of Scientology materials into Hebrew. At least that's what they did last time I looked at them, about ten years ago. Those people are certainly prolific, and they get points from me for consistency, but this not the prevalent standard. (And if I recall correctly, they use the minus and not the proper Hebrew maqaf, and they don't get any points from me for that!) :::Also, the name of the character is just "double quotes" and not "gershayim". Gershayim are mostly for abbreviations, although most people use the same character for them. I use ״ for gershayim, as do a few other nerds, but we're the minority. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:35, 23 April 2026 (UTC) :::: {{re|Amire80}} Yeah, "font" is a weird choice of wording here by the Academy...<br> I think I'll follow your guidance and not use a maqaf for quotes beginning with Hebrew letters. <br> I should also add more tests for different types of quotes, like straight (", '), curly (“, ”, ‘, ’), gershayim (״, ׳), including single quotes.<br> P.S. gotta deduct points from Scientology for being a cult but that's neither here nor there [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:49, 23 April 2026 (UTC) :::: {{re|Amire80}} Courtesy ping because I mistyped your username on the last message. Anyways I'm also gonna do that tomorrow because I'm tired now... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:50, 23 April 2026 (UTC) == Connect implementations == Hello! I'm done with the implementations of {{Z|Z33986}} both in JS and Python, and all tests pass. Pinging @[[User:Amire80|Amire80]] to check if all the tests I've added are alright. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 15:24, 24 April 2026 (UTC) :Connected. It's possible that some more changes will be needed, but it looks OK now. :Another little comment: It should be called "clitic" and not "prefix". [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:56, 24 April 2026 (UTC) : {{re|Amire80}} Thanks for your comment! Luckily labels are easy to edit, so I'll get to it. : Currently I'm working on Bulgarian {{z|Z34072}} and {{z|Z34084}}, along with other Bulgarian functions. After I'm finished with those I'll take your advice. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 16:01, 24 April 2026 (UTC) == Please connect my Bulgarian implementations == I recently created the following Bulgarian functions: * {{Z|Z34070}} (currently broken, I think because another function I built it upon is unimplemented) * {{Z|Z34088}} * {{Z|Z34105}} * {{Z|Z34072}} * {{Z|Z34084}} Can somebody please connect these functions, and perhaps suggest other functions I could localize? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:03, 24 April 2026 (UTC) : Specifically, [[Z34070]] is based on [[Z34072]] [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:05, 24 April 2026 (UTC) :{{done}} for everything that passes, [[Z34070]] still does not work after purging WF's cache, though. For future reference, please request on the [[WF:Community portal|community portal]] instead of the project chat. Thank you for your work! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:03, 24 April 2026 (UTC) :: {{re|Feeglgeef}} Thank you for your help! I will keep in mind to go to the [[project: community portal| community portal]] in future instead for this. :: I still don't understand why {{Z|Z34070}} fails... It's implementation is almost completely identical to [[Z30399]] from {{Z|Z30397}}, unless I messed something up... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:11, 24 April 2026 (UTC) :::{{done}} No, it was mostly just timing out. It is better to use selective fetches where possible. One case is failing to match the expected results, but at least it is returning something. For all I know, it might even be acceptable! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 20:35, 24 April 2026 (UTC) :::: {{re|GrounderUK}} Thank you so much for your help! The one failed case is with a definite article, so I feel like that might be fixed in the future... <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:43, 24 April 2026 (UTC) == Editor experience suggestions == I'm a bit frustrated with the editing experience on Wikifunctions, and I have suggestions based on pain points I've had contributing to this project: * Adding a wizard to create functions, implementations, and tests in one flow, somewhat like Wikimedia Commons' upload wizard * A sandbox for experimenting without changing mainspace functions, and maybe letting non-functioneers connect implementations ([[Project: Sandbox]] doesn't seem to fit this) * We could have functions for creation based on the sandbox, like how Wikipedia has articles for creation and edit requests, * Maybe even another test instance of Wikifunctions, like how Wikidata has [[testwikidata:|Test Wikidata]] I really like this project and I don't mean to whine, but it certainly has a lot of pain points both for technical and non-technical people. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:41, 24 April 2026 (UTC) : It's also really complicated to localize functions, so maybe we should add another wizard for that, where you can choose a language, and then create the new function with the aforementioned function wizard, and it just automatically adds it to the related language configuration object of the related function. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:48, 24 April 2026 (UTC) :# Sounds good to me. :# A sandbox available is [[Z10119]], though an extension-provided sandbox that allows you to manipulate the types, code, and tests easily without interfering with the mainspace would be nice. :# [[WF:Suggest a function|This page]] works to some extent, though it's too messy in my opinion. :# We used to have a "beta cluster" but it [[phab:rOMWC5f625c5846b5f779473fa32c9a02d87e59215dfa|got shut down]] just over a year ago because it was broken. :[[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:07, 24 April 2026 (UTC) == Language parameters in language-specific functions == I think that an effort should be made to give the different natural language options corresponding to different English dialects, Chinese scripts, etc. more of a use (I added the test {{Z|Z34119}} to {{Z|Z26095}} and unsurprisingly it fails). There are two main problems with this approach that I can identify: * If you ask the majority of these functions to make a sentence in British English, much of the time it will give you an output with missing words, because it does not fallback to English labels in the case of a British English label for that item missing. The same applies for every other English dialect, British English is just an example here. * Uninformed editors will probably see the presence of a language parameter on these functions, consider it redundant, and remove it. [[Special:Diff/268074|I have made this mistake before]]. In my opinion, in a perfect world, all of these language generation functions would output monolingual text, and if the user asks for American English text, then American English text is what they'll get. If the user asks for Japanese text in hiragana specifically, then that's what they'll get in return. This is not as high-priority as just rendering text in the language plainly in the first place, but it's something that I feel is still worth devoting some effort to. Right now switching functions to use this paradigm is difficult because, on the one hand, I don't know if consensus tends towards this direction being ideal or advisable, and I don't want to make changes like this without at least notifying the wider community. In addition, all tests break once a parameter is added or removed, and the function editor does not recognize the change in number of parameters and therefore you have to remove the function call, re-add it along with all of its parameters it had previously (which is a tedious cut-and-paste job), and then it will work again. This is something that you can do in five seconds by just adding a few lines of JSON to the test source, but this is not directly editable from the Web browser. This tedium is largely what's preventing me from doing this on a larger scale, besides asking for comments first. If anyone has any insights or comments on this, then that would be appreciated. If a reference of functions with and without the support for language variants is needed, of course [[WF:NLG]] can be perused, but I've also my own list cataloged at [[User:Theki/functions#language]]... Of course, this thread has many similarities to [[#"language" argument for certain functions|the one above]], but this concerns me going out and making this consistent across these NLG functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:09, 24 April 2026 (UTC) :I've created {{Z|Z34122}} as an extension to {{Z|Z34039}} for larger functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:34, 24 April 2026 (UTC) :Just to confirm that I, for one, support a Natural language parameter for all natural-language functions. The concern about getting them all aligned is just that we haven’t finally settled on {{Z|Z11}} being preferred to {{Z|Z89}} or some other type that conserves the text’s provenance, so we risk having to change them all again. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:07, 25 April 2026 (UTC) == “Key not found ()”? == What am I doing wrong in {{Z|Z34137}}? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 00:39, 25 April 2026 (UTC) :You were passing a [[Z6091]] to {{Z|32290}}, but it takes a [[Z6001]]. Fixed. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:10, 26 April 2026 (UTC) ::{{done|Thank you}}! [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 14:13, 26 April 2026 (UTC) == Why is my test failing? == Hello! I recently made {{Z|Z34139}} based on [[wikt:Module:bg-translit]], and the test case {{Z|Z34141}} is failing on both implementations, despite the expected output and actual output being the same as far as I can tell. I tried looking at the Unicode codepoints of the output, but those are also identical. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 06:21, 25 April 2026 (UTC) :Yes, it’s a tricky one. I’ve added a normalize step to the result validation in {{Z|Z34141}}, which confirms it is a normalization issue. It looks like it is in the code but I don’t know whether simply normalizing the result is the way to go. Logically, you would normalize both the input and the result. The implementations of {{Z|Z10384}} show you how to do this. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:41, 25 April 2026 (UTC) == Edit request == Hello! I have an edit request for {{Z|Z23752}} and {{Z|Z23414}}. Please replace all the "an/a" logic with <code>Z21739(Argument reference)</code>, both for readability and for more accuracy ("a university is an institution") <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:50, 25 April 2026 (UTC) :{{D}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:24, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #245 is out: The Foundation's search for the perfect language == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-25|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present an academic paper about Abstract Wikipedia, we discuss our latest Type created, and we take a look at the newest created functions. 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:54, 25 April 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=30325620 --> :@[[User:Sannita (WMF)|Sannita (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], technical meta-question: the newsletter quotes the article: ::the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016) :This quotation sounds sensible, but the article's [https://link.springer.com/article/10.1007/s00146-026-02899-w web version], and the PDF that is downloadable from the same page doesn't actually show the emojis. It rather shows text that looks lacking: ::the only way to contest its algorithm is to click or (Crawford and Gillespie [https://link.springer.com/article/10.1007/s00146-026-02899-w#ref-CR14 2016]) :Where did you get the emojis? Is it your (probably correct) guess or is there a version somewhere that actually shows the emojis? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:16, 25 April 2026 (UTC) ::Scratch that. I've found a version with correct emojis: https://wikihistories.github.io/wikilambda-the-ultimate/ [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:37, 25 April 2026 (UTC) == Requested deletion of test == Please delete {{Z|Z34143}}. this was never valid Bulgarian, I messed up. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:19, 25 April 2026 (UTC) :[[WF:RFD]] please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:40, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|talk]]) 00:57, 26 April 2026 (UTC) </bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == Is it OK to connect the implementation? == Hello! I recently applied for functioneer on [[WF:RFG]], and I was wondering whether I could connect the implementation for {{Z|Z34165}} despite its dependency {{Z|Z34149}} being currently unimplemented. That is <em>if</em> I get accepted. I am planning on implementing it based on [[wikt:module:bg-nominal]], but am still having trouble figuring it out for now. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:04, 26 April 2026 (UTC) == Past tense function == Is there a function like {{Z|Z26039}}, but for the past tense (e.g. "Leo Tolstoy <em>was</em> a writer.")? If not, I will create it myself, I just want to make sure there's not a duplicate. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:10, 26 April 2026 (UTC) : {{Done}} with {{Z|Z34224}}, but I have a few kinks to work out with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:35, 26 April 2026 (UTC) :: I need to create some other similar functions for the past tense, I have some ideas: ::* {{Z|Z26095}} ::* {{Z|Z32643}} ::* {{Z|Z28016}} ::* {{Z|Z26570}} ::* {{Z|Z33975}} ::* {{Z|Z27243}} ::* <ins>{{Z|Z26627}}</ins> ::* <ins>{{Z|Z27627}}</ins> ::* <ins>{{Z|Z27173}}</ins> ::* <ins>{{Z|Z29591}}</ins> :: :: Are there any I have missed? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:57, 26 April 2026 (UTC) :I think that here we are starting to walk on dangerous waters: what does past mean? Is it a recent o a far past? Does it have ripercussions on the present or not? Is it just a thing that happened once, many times or for a continuative period of time? :Consider that various languages distinguish between many different types of past. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:38, 26 April 2026 (UTC) :: {{re|Dv103}} That is a fair point... :: How do we go about solving this problem though? I don't think having every sentence on Abstract Wikipedia be "X is a Y" is a very good idea. :: Maybe we have different functions for all these variations of past you mentioned that just map into "X was a Y." in English? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 13:31, 26 April 2026 (UTC) :::To properly solve this problem, we should use a more complete abstract content representation model, like for example the proposal of [[Wikifunctions:Type proposals/Semantic unit|Semantic units]] (look at [[Wikifunctions:Type proposals/Semantic unit/Douglas Adams|the example]] to see how times could be handled). For now, since we're still stuck with single fragment generation functions (that I hope will be slowly replaced with the complete represenation model, when available), we could just restrict your function to a very specific meaning, like "subject was an instance of, for most of its existence" (which means for example that it could be used to say "Douglas Adams was a writer", but not "Abraham Lincoln was a president", since he only was a president for 4 years). Probably my definition is still too vague, and this is why we need to go beyond these fragment generating functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:47, 26 April 2026 (UTC) ::Nitpick... I don't like that it outputs a string instead of monolingual text. With {{Z|Z26039}} it's used so much that I think it's unfixable in that case beyond deprecating it if people care that much, but {{Z|Z34224}} doesn't even have any connected implementations yet. Consider it, maybe? ::Nitpick 2... {{Z|Z34227}} is missing a language parameter. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:08, 26 April 2026 (UTC) ::: I will consider that! ::: I just did that because that's what {{Z|Z26039}} does, so I assumed I should follow suit with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 26 April 2026 (UTC) == Legacy functions == If and when more robust methods of abstractly representing and generating linguistic content come around, and more efficient ways of creating abstract content are devised and implemented, I suspect that our current methods will require some form of deprecation. This is a significant source of concern for me in relation to WF and AW, questioning how prone our current methods of doing things are and eventually will be prone to obsolescence, and how it will be worked around when it comes. We have over 1 250 articles on AW presently, and these are rather all over the place. I suspect the maintenance burden from keeping these articles up to code will eventually, err, creep up on us, I suppose, and some kind of major refactoring will be necessary. We are definitely in a period of experimentation and whatnot right now but eventually, like with enwiki, some sort of structure and rigor will form and I suspect it will start to become rather boring for me... I, for one, very much enjoy experimenting with new and better ways to do things here. I don't personally mind changing things to use a new and better paradigm if need be, that sort of thing highly excites me, but of course there will be things that are left behind, and I suspect maybe bots will be employed to deal with this? A lot of Wikipedia sister sites seem to do that, e.g. going and fixing up use of deprecated templates. Considering the nature of Wikifunctions and Abstract Wikipedia I suspect certain maintenance tasks will be made simpler or even trivial by the typical uniformity of our implementations. I guess I am just concerned if Wikifunctions or Abstract Wikipedia will ever accrue its own kind of "technical debt" with how we are plowing through things presently, and if there is a plan for how we will eventually seek to mitigate that. Maybe too early to ask this question, but I am a notoriously anxious person, so I thought it wouldn't hurt to raise the question regardless... &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:30, 26 April 2026 (UTC) :I very much agree, thank you for expressing my position so well. {{ping|Immanuelle}} has been using an AI-generated tool (well, they haven't edited in a week, perhaps it's a break or perhaps they don't wish to contribute to the project any more) to create a bunch of articles en masse, which I have warned them multiple times is a bad idea (on top of evolving functions, all of the articles are one-sentence-per-paragraph, [[abstract:Q12184|like so]]). That's why I've been avoiding creating articles recently, I'd say I have a good fourth (no data to support, rough guess) of the comments on the wiki, yet less than a percentage of the article count (only three, including the [[abstract:Q319|first article]], though, so perhaps I'm the next [[w:Special:Permalink/908493298|office.bomis.com]]). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:41, 27 April 2026 (UTC) :: I feel that the overwhelming presence of these low-quality articles (which I admit I myself am [[abstract:Q1710970|guilty]]/[[abstract:Q7601858|of]]/[[abstract:Q39338|creating]], usually as testbeds) may incur a large maintenance burden. I do expect them to be easy to detect, however, as searching for the presence of "deprecated" NLG functions is trivial, and it is possible that replacing them with their future ''even abstracter&trade;'' counterparts could be done automatically since they all have the same signatures and can be expected to create the same form of sentence. If it needs to be done manually for a while or for certain delinquent instances, my hope is that it will be fun, at least for a while. :: I just hope that these hypothetical future waves of "this new and versatile way of abstractly representing linguistic content" obsoleting previous methods and requiring refactoring across all articles is only a one-time thing. We should strive to be as robust and flexible as possible from the outset as each brand new paradigm of abstraction is also a brand new maintenance burden for updating old articles. At the end of the day, at least ''some'' of these articles will still render to many different languages even if their methods of creating those sentences of theirs is completely outdated. Ergo, the time it takes for the switchover to be performed across our articles should not be a persistent inconvenience for users (as, of course, they will always still be able to read the content as it was before since these legacy functions aren't being deleted outright), and the increased availability that the new methods will bring about will likely act as motivation for them to join the effort in refactoring (&#x300C;You're telling me that if I rewrite this article in this cool Lisp-looking stuff then I can probably read it in [[abstract:Q9307|Galician]]?? COOL!&#x300D;). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 20:26, 27 April 2026 (UTC) :::Totally agree. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:54, 28 April 2026 (UTC) :::My vague plan is to implement a default function returning an {{Z|Z89}}, for each language-neutral function. A single function would convert any of these to a {{Z|Z11}}, so that a composition of the two can be implemented as the current default until such time as the language-neutral function is ready to return a [[Z89]]. We can already convert a [[Z11]] to a [[Z89]] so, although there is more to be done in this space, existing language-specific functions could be adapted to return a [[Z89]] quite mechanistically. :::Although we certainly could deliver parallel Z89 functions for each existing Z11 function, I don’t think we should assume that particular outcome. Provided the Z89 captures a lang attribute from the Z11’s language tag, the two representations should be largely interchangeable, although I am expecting a Z89 to carry additional attributes at the span level that would be lost on conversion to a Z11 (along with any higher-level tags and attributes). :::When I say there is “more to be done in this space”, I am referring to a new type that would allow HTML fragments to be represented as tractable Wikifunctions objects, but this is currently drafted only in my head! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:21, 29 April 2026 (UTC) == Filtering types of objects == Hello! I have tried to comb through my own edit history several times, but it's really hard to search for specifics because there's no differentiation between different types of objects (functions, implementations, tests, etc.) in the logs as far as I can tell. Am I missing anything? I want it to work sort of like how filtering by namespace works. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 27 April 2026 (UTC) :There is differentiation, it's just rather hard to look through. Since all ZObjects are just JSON data at their core, you can search for instances of <code>{ "Z1K1": "Z[type]"</code>. I haven't tried this so I'm not sure how well it would work and I know MediaWiki search syntax treats quotation marks as a special character, but I have seen Wikifunctions pages link to searches using this before. There is also [[Special:ListObjectsByType]] but it is sitewide rather than specific to your edit history in particular. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:59, 27 April 2026 (UTC) ::''[It doesn’t help directly here, but please see [[WF:Find]] for more details of how this works.]'' [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:24, 29 April 2026 (UTC) :See the feature requests [[phab:T399244]]/[[phab:T373735]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 06:06, 28 April 2026 (UTC) :The lack of filtering edits by namespace is exactly the problem that I was trying to solve with the [[User:Amire80/wikifunctionsanalytics]] tool. :I even kind of succeeded, but it has two major problems: :# It doesn't have any real frontend, so you have to know some SQL to use it (or ask other people who know SQL). :# It doesn't get information from the live site, but from the dump, which appears to be updated once a month. :I've made a [https://quarry.wmcloud.org/query/104794 sample query for you]. Unfortunately, it won't do anything at the moment because of the second problem—your edits started in April 2026, which isn't over yet, so the dump for it hasn't been processed. But I hope that early in May you'll be able to use the same query and see something useful. :(I plan to add support for recent edits, but I haven't done it yet. Now that I more or less figured out how to process Wikifunctions edits, I'm focused on trying to understand Abstract Wikipedia edits. Processing up-to-date edits from both sites will possibly be the next thing I work on, but if you know some Python and want to try doing it yourself, don't wait for me—[https://gitlab.wikimedia.org/toolforge-repos/wikifunctions-analytics Patches welcome].) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:51, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]], I've just updated the data until the end of April. Now the query to which I linked above gives some results. You can also try running other queries if you know SQL. (Or try asking for other queries if you don't.) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:26, 3 May 2026 (UTC) == [[Z34213]] == I'm not quite sure why this implementation is failing. Could someone take a look? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:24, 28 April 2026 (UTC) :I've [https://phabricator.wikimedia.org/T419933#11863997 notified] the team that this is still occurring, the issue was marked as resolved. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:52, 28 April 2026 (UTC) :Some useful tips: :* create more testcases: sometimes it is a random error, so try to see how consistent it is between testcases :* your implementation is very inefficient, since it fetches items and lexemes a lot of times. Ideally, each item and each lexeme should be only fetched once in all the execution tree. :[[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 06:06, 28 April 2026 (UTC) ::Caching (''should?'') means that the lexeme and item data are cached, so the call doesn't actually execute multiple times. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:51, 28 April 2026 (UTC) :::Are lexemes and items actually cached within the same function execution? Even if they are only partially fetched and/or fetched in bulk? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 17:54, 28 April 2026 (UTC) ::::I don't have any evidence to prove that it works but that's definitely A. what's supposed to happen and B. the ideal behavior. This happens because the Z680X functions can be cached just like any other. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 28 April 2026 (UTC) ::::It is unclear. In general, I believe identical branches are resolved only once in orchestration, but there is also independent caching of Wikidata fetches. ::::According to @[[User:DMartin (WMF)|DMartin (WMF)]] ([https://t.me/Wikifunctions/30374 on Telegram]): ::::<blockquote>Well, no. We have caching of Wikidata entities that have been retrieved, but not of the results of nested function calls. There is a proposal for doing this in the context of the V2 composition language, when it's a bit more mature, and it's regarded as a relatively high priority.</blockquote> ::::It’s hard to tell whether fetches in nested calls are, in fact, cached and available for other nested calls in the same call, since it is not generally the actual fetch that consumes the most resources. Rather (I believe), it is construction and transmission of the result object, which is currently repeated afresh in each nested call (unless it is in an identical branch). ::::I hope that’s clear, and I apologise in advance if it happens to be inaccurate! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 29 April 2026 (UTC) :::::Oh, I should clarify.  There is a lot of caching going on, in several different places.  Lexemes and items ''are'' cached by the orchestrator within the same function execution, even if they are only partially fetched and/or fetched in bulk.  When I said that we don't have caching of the results of nested function calls, I meant that's not happening in general, for all nested function calls in compositions.  But fetching of Wikidata entities gets special treatment, so yes, fetched content from Wikidata is cached, regardless if it was fetched by a top-level call or a nested call. :::::It is also true that the construction of a ZObject from the fetched JSON might happen more than once within the same function execution, depending on how a composition has been structured. However, the construction of the ZObject is actually very fast, compared to the elapsed time of getting the JSON from Wikidata. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 18:04, 1 May 2026 (UTC) == Question about cardinal numbers == I was about to edit {{Z|Z16435}} to add my function {{Z|Z34308}}, but I noticed that none of the other functions have a gender parameter. Should I create a new wrapper function "Bulgarian cardinal, neuter", or should I just remove the gender parameter and always return neuter? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:39, 28 April 2026 (UTC) :The “cardinal” functions should return the words used for “counting” numbers in the abstract. :We should consider converting them to return a {{Z|Z11}} rather than a {{Z|Z6}}. It may even be appropriate to return a {{Z|Z12}} to cater for language variants. Either way, I think that would be the approach to adopt for inflected forms, unless reference to specific lexeme-forms is required. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:52, 28 April 2026 (UTC) ::This. If a native of your language were to count up, which form would they be most likely to use? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:29, 28 April 2026 (UTC) ::: {{re|GrounderUK|Feeglgeef}} Thanks for both your input! ::: I relabeled the aforementioned function to {{Z|Z34308}}, and created a new wrapper function {{Z|Z34457}}. ::: Should I specify that my old function is a monolingual text in parentheses? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:26, 28 April 2026 (UTC) ::::You don't have to, unless you think that is something that would require distinction when viewing the function in a list of search results &c. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:36, 28 April 2026 (UTC) == Optional/nullable function parameters == Hello! Recently, I was informed that Wikifunctions has no optional/nullable function parameters as of now. Are there any future plans to support this, and/or workarounds? Maybe create a union type system like "{{Z|6}} or {{Z|23}}". <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 17:53, 28 April 2026 (UTC) :What I do for this is use an "is empty" function corresponding to the type of the parameter in an If statement. If it isn't empty, the function works as intended. Otherwise, it does something else. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:58, 28 April 2026 (UTC) :Unions are not a thing (yet) on Wikifunctions, but you can always define an argument of type {{Z|Z1}}, which means that all types are allowed (I already did this for {{Z|Z26737}}; note that it is still a ugly workaround, don't use it for high level functions). Also, note that usually on Wikifunctions we use {{Z|Z24}} as the null value. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:00, 28 April 2026 (UTC) :: {{re|JJPMaster|Dv103}} Thanks for your help! :: @[[User:Dv103|Dv103]] told me a function call with a missing parameter is treated as an invalid function call, so how does the "is empty" function work with that? :: Also, setting the type to {{Z|1}} seems naive, like setting the type as <code>any</code> in TypeScript... :: Related question: Are there plans to add default values to parameters (outside of "if empty")? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 18:19, 28 April 2026 (UTC) :::Setting the type to {{Z|Z1}} is actually naive, and that's why I advised you to only use it for low-level functions. Currently there is nothing better. Sometimes, type correctness is not actually checked, so it might seem that nullable types are possible. But it is still an hack, and it could broke anytime since it is not intended behavior. :::I don't think that there are current plans to add default values (but correct me if I'm wrong). The closest thing that comes to my mind is that, if you incorporate Wikifunctions into Wikitext, you can leave empty some fields (only of some specific types) and Parsoid will replace them to their default value. This is done only depending on the type, and not on the functions. For example, {{Z|Z6091}} and {{Z|Z6001}} are assigned the QID associated to the page, and {{Z|Z20420}} is assigned the current date. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:56, 28 April 2026 (UTC) :::@[[User:QuickQuokka|QuickQuokka]]: At the very least, [[Z10008]] accepts a null input. Maybe that feature is unique to the String type—I am not sure. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 19:10, 28 April 2026 (UTC) ::::I think it's just not checked, but it shouldn't be intended. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:20, 28 April 2026 (UTC) ::::Strings and typed lists can be “empty” in the sense that their length can be zero. Typed pairs may also be “empty” in a degenerate sense, but such an object will not be returned from a code implementation. A typed map with no entries will also fail to be returned from code, although it is fine in compositions. ::::For a genuinely optional parameter, I prefer a properly typed list, which at least encourages an argument of the correct type. {{Z|Z813}} is also typically faster than {{Z|Z10008}}. Quite a good example of this approach is {{Z|Z23723}}, where it helps to resolve the type union (using [[Z1]]) for both Z6003K1 and Z6003K3. Of course, there’s nothing to prevent more than one element in the list, but additional elements are easily ignored. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:55, 28 April 2026 (UTC) :Pinging {{ping|Jdforrester (WMF)|prefix=|p=}}, I believe there are no current plans. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:02, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]]: I'm afraid there are no current plans to build out optional params, indeed; we would be happy to review this if a compelling case was made, but it'd be a lot of work to re-build the [[Wikifunctions:Function model|function model]] with that support and ensure we don't break (too many) things. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:11, 28 April 2026 (UTC) == Z6830 for Chinese == I was trying to use {{Z|Z6830}} for implementation in the Chinese-language. And turns out most of the Lexeme on Wikidata is using [[d:Q727694]] as the language instead of [[d:Q7850]]. This makes it impossible to use the mentioned function above, since Standard Chinese is not available (or did I miss something?). Is there a way to fetch lexemes with language=[[d:Q727694]] from item? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:20, 30 April 2026 (UTC) :@[[User:Sun8908|Sun8908]] There is [[Z1006]] for Chinese and it has the language code zh. There is an overview of languages in [[Module:Wikifunctions label]] so you can search there for chinese versions and choose the one you need. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 5 May 2026 (UTC) ::I know that. The problem is when using the function [[Z6830]], it cannot retrieve lexeme with language [[d:Q727694]] (but it is the "Chinese language" with the most current Wikidata lexemes, see [https://ordia.toolforge.org/language/ ordia]). I think it should be a Wikidata problem, I might fix it (possibly by creating the same lexemes with language code zh) on Wikidata. Thanks anyway. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 05:39, 6 May 2026 (UTC) :Could you provide an example of a Chinese lexeme that has a linked Wikidata item, or a Z6830 function call that fails to find such a lexeme where one exists? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 07:55, 6 May 2026 (UTC) ::Here: [[d:Lexeme:L846083]]. I think that's a primary reason of me trying to look into this problem, as the label in zh for [[d:Q6256]] (country) is not a single phrase (see its talk page on WD for more information). This makes some Abstract Wikipedia articles very weird in Chinese when {{Z|Z26570}} is used, so lexeme could potentially fix that. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 10:33, 6 May 2026 (UTC) :::Thank you. It looks as though {{Z|Z6830}} [https://www.wikifunctions.org/view/en/Z6830?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z6830%22%2C%22Z6830K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q6256%22%7D%2C%22Z6830K2%22%3A%7B%22Z1K1%22%3A%22Z6092%22%2C%22Z6092K1%22%3A%22P5137%22%7D%2C%22Z6830K3%22%3A%7B%22Z1K1%22%3A%22Z60%22%2C%22Z60K1%22%3A%22cmn%22%2C%22Z60K2%22%3A%5B%22Z6%22%5D%7D%7D returns that lexeme for language tag "cmn"]. Perhaps that tag should be added into the helpers for {{Z|Z24144}}? If it is widely used for lexemes, perhaps it should have its own {{Z|Z60}}? In any event, improvements might be considered under [[:phab:T390563]] (or otherwise), including amending [[Z6830]] to also consider "cmn" (and "zho", "chi"…?) when requests are made for "zh-hans" or "zho-hant" (or others?) @[[User:Winston Sung|Winston Sung]] @[[User:DMartin (WMF)|DMartin (WMF)]] [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:22, 6 May 2026 (UTC) ::::If you go to [[d:Special:NewLexeme]] and put in [[d:Q727694]] as the language, it is going to tell you it has an unrecognized language code. So I believe "cmn" should not be a {{Z|Z60}} by default? I also started [[d:Wikidata:Project_chat#Lexemes_with_language_Standard_Chinese_(Q727694)|a discussion on WD]] regarding this. I guess we can still use it as a fallback language though if possible. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 03:43, 7 May 2026 (UTC) ::::We don't have a separated <code>cmn</code> BCP 47 language subtag in MediaWiki and Wikidata at the moment. <code>zho</code> and <code>chi</code> are ISO 639 language codes but not BCP 47 language subtags. ::::For Modern Standard Mandarin, please use <code>zh-*</code> language tags for now. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 15:26, 8 May 2026 (UTC) == Key not found error == Is there a reason why I am getting key not found error for this [[Z34677|function]] {{Z|Z34677}}? All the underlying functions run and all the test cases work. The debug information does not give more details. Any pointers? Thanks in advance [[User:Jsamwrites|John Samuel]] 19:24, 1 May 2026 (UTC) :It was passing the [[Z6091]] to {{Z|34641}} when that takes a [[Z6001]]. I've fixed that, but there's some other problem with the logic, so I've left it disconnected. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 19:42, 1 May 2026 (UTC) ::@[[User:YoshiRulz|YoshiRulz]] Thanks a lot. [[User:Jsamwrites|John Samuel]] 20:21, 1 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, 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:21, 2 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=30325620 --> == Any formal process for deletion of pages == Does a formal process exist for the deletion of functions, implementations, and tests that includes a notification system for creators, analogous to Wikidata’s process, explaining the rationale behind the deletion (or proposal for deletion)? [[User:Jsamwrites|John Samuel]] 12:36, 3 May 2026 (UTC) :Does [[Wikifunctions:Requests for deletions]] work? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:00, 3 May 2026 (UTC) :Please see the discussion at [[Wikifunctions talk:Requests for deletions#Should we expect Objects' creators to get pinged on deletion proposals?]]. :As I see it, it is the proposer’s responsibility to consult appropriately before making a request and we expect our administrators to act only when satisfied that appropriate consultation has occurred. In many cases, no consultation is required. Administrators may delete their own contributions without making a request, but this is not a practice I would encourage. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:51, 3 May 2026 (UTC) == Implementation of rational number in JS doesn't match in Z19677 (Rational number) and Z28579 (RGBA colour) == In {{Z|19677}} it's <syntaxhighlight lang=js> { "K1": sign * numerator, "K2": denominator } </syntaxhighlight> but in {{Z|28579}} it's <syntaxhighlight lang=js> [ sign * numerator, denominator ] </syntaxhighlight> '''<span style="font-family:Iosevka,monospace">[[User:沈澄心|<span style="color:#9f3526">dring</span>]][[User talk:沈澄心|<span style="color:#534fa3">sim</span>]]</span>''' 05:15, 4 May 2026 (UTC) == Nested functions in compositions == I wish it will be easier to a add another function about a specific existing function in a function implementation based on a composition. When I write long functions in spreadsheets I usually stat with a small part and then I try to go further and after important steps I test if the output is as expected. I created [[Z34826]] to get the German gender specific occupation lexeme for a specific person based on their gender. I wanted to add a function around the existing one and it was not successful. It is not very easy to implement as it requires the possibily to move a part to another section but I think it can be helpful if it will be implemented. So far I spend more time as expected on the function. Describing it with words what the function needs to do is much easier than implementing it here in Wikifunctions. So I think there needs to be improvement to make Wikifunctions more accessible. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:10, 5 May 2026 (UTC) :Have you tried to use the copy-paste functionality? It is very useful to move parts of composition arounn. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 07:12, 6 May 2026 (UTC) :I've also found the composition editor to be wholly unsuitable for any expressions more than a few levels deep. (Even with the <code>localStorage</code> clipboard, because of its overzealous type checks.) Compositions naturally grow out from the "leaves", the immediate operations on the inputs, while the interface really wants you to build from the "root". I mostly use the [https://yoshirulz.gitlab.io/WikiLambdaBlockly drag-and-drop block editor] which I made to smooth over some of the site's problems, so if you want to try that out and give me some feedback I'd appreciate it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 14:36, 6 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the 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 [[: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/1778520600 May 11, 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]]) 11:16, 8 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=30325620 --> == RGBA colour, spelling... == Something that has always irked me a little bit is the spelling of [[Z28579|RGBA colour (Z28579)]]. I guess this is not unsurprising for me considering my use of US English but I think there is more to it than preference and I want to try to argue for it being changed to use American spelling. I know that this probably has a snowball's chance in hell of actually garnering any support, so I won't really be miffed if the spelling remains as it is, but I thought it wouldn't hurt to raise this regardless. The main issue I have with it is the spelling of the original proposal. When infernostars raised the [[Wikifunctions:Type proposals/RGBA color|type proposal]], the spelling was 「RGBA color」. Of the comments that mentioned the word 「colo[u]r」, two used British spelling while six used the American spelling as used in the proposal. The only thing that really pointed to the use of ''colour'' was the fact that the catalog page on color functions used that spelling already. For all intents and purposes, the spelling of the original proposal should have been maintained, but it was not; [[User:DVrandecic (WMF)|DVrandecic]], the eventual creator of the type, used a different spelling. It should be noted that there was really no reason for this to occur and while it is an undoubtedly minor issue I still believe it should be rolled back and the type should use the spelling of the original proposal and majority of editor comments. In [[abstract:Q936|OpenStreetMap]], there have been keyvalue proposals that have had the finalized spelling that gets put to use be in British English despite the original proposal being in American English; this has usually occurred with proposals relating to 「X center/centre」 tags. This makes sense on the surface, because OpenStreetMap is maintained by a UK organization, and still has close ties to Europe. The Wikimedia Foundation, however, is an ''American'' company. This is often brought up as a fallible argument when debating article spelling on the English Wikipedia, and I don't bring it up to support that 「RGBA color」 should be used for that exact reason, but rather to state that OpenStreetMap's general policy on tag names need not apply here. It appears to me that, at least initially, the majority of 「core contributors」 to Wikifunctions used British English; I can name YoshiRulz, 99of9, GrounderUK, and VIGNERON.<ref group="color">I'm avoiding linking to these folks because I don't think pinging them about this discussion is all too necessary unless they themselves want to be involved; I don't want to clutter their inboxes just to briefly mention them. I pinged Denny because, well, I'm asking him a question directly, but everyone else I would prefer to join this discussion by their own accord... not that I wish for this decision to be confused as me going 「these people use British English so they will probably oppose my idea, I won't invite them to the discussion because of that」...no, I promise you that is not the reason.</ref> I see (or saw) these people ''everywhere'', so it makes sense that British English has prevailed in some sorts on this website, but I don't think that indicates that it should be the ''preferred'' spelling across the website, at least not to the point where a proposal should have its name changed to match such a "consensus".<ref group="color">It could be argued that the front-and-center ''Function catalogue'' using 「catalogue」 is actually indicative of such a "consensus", but ''catalogue'' is in a similar position to the word ''grey'' where I live (that is, the US) in that it is used just as often as its American counterpart. Also, consider Wiktionary's ''Beer parlour'' project chat.</ref> The unnecessary modification of the original spelling is my main argument for changing it back... but of course, I must obligatorily state that on English Wikipedia, it is [[w:Color|Color]] and [[w:RGBA color model|RGBA color model]]; on Wikidata, it is [[d:Q1075|color]] and [[d:Q2325624|RGBA color space]]; in CSS (which typically uses hexadecimal triplets to specify RGBA values), the properties are <code>color</code>, <code>background-color</code>, etc.; bit of a weak jab, but on Schema.org it is [https://schema.org/color color], [https://schema.org/colorSwatch colorSwatch]; et cetera. {{Z|Z28580}} uses ''color'', so does {{Z|Z28591}} and its Python counterpart. Mr. Vrandečić, I have to ask, I'm rather confused... you created the color type using British English spelling, but you were also responsible for the creation of the equality function which uses the American English spelling. You also seem to be writing in American English for the status updates, judging by your use of -''ize'' over -''ise'' endings and use of ''program'' over ''programme'' in [[Wikifunctions:Status updates/2026-04-16]]. Is there something I'm missing or have you switched your preferred variant somewhere along the way? Anyways, do consider this if you wish... again, I don't suppose this will garner much support, it is the ''non-issuest'' of ''non-issues'', but it has irked me to the point where I want to ask about it to get some answers, if nothing else. I am not arguing for every other color function to have its name changed, just the type itself. <references group="color"></references> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 8 May 2026 (UTC) :This is a multilingual project; the <code>en</code> label is <code>RGBA colour</code> and the <code>en-us</code> label is <code>RGBA color</code>. Though I'm not able to switch to <code>en-us</code> via the language picker so that would need to be fixed.<!-- --><br>edit after reading your whole comment: The same is true of {{Q|1075}}, there are labels specified for multiple English variants. (In {{Q|2325624}} it's only an alias.) I agree that other websites' choices aren't binding on us, but from that, I conclude that the more widespread British/Commonwealth spellings should be used for the generic <code>en</code>. As for myself, I'm Aussie and I will continue to use the BrE spellings ([[w:en:Oxford_spelling#Language_tag_comparison|+ "routing"]], TIL) if only by muscle memory.<!-- --><br>[[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 17:42, 8 May 2026 (UTC) :: Your lattermost point would normally be fine in a perfect world. Wikipedia's <code>convert</code> function defaults to "international" English, which I don't personally take issue with because it happens that we here in America are actually outliers for saying and spelling things differently... err, or we were for a while at least, nowadays it seems like an even split (plus you have "yield" vs. "give way" which is effectively the logical opposite of US's use of "meter" over "metre"). :: However, this is not a perfect world, and I don't think <code>en</code> should correspond to any particular variant. It is too fragmented across all software at this point to impose such a requirement. The inability to switch to <code>en-us</code> on this website foregoes an easy and simple solution to this problem that makes everyone happy, because the yanks (such as myself) can't be happy because we can't see the labels in American English even if we wanted to, and the other folk can't switch either as far as I'm aware (and the en-CA and en-GB languages in the preferences page seems to be deprecated). My point being, <code>en</code> is abused to mean "en-UK" just as often as it is abused to mean <code>en-US</code>; I think a decision shouldn't be made on such an assumption of one "default". &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:48, 12 May 2026 (UTC) :Hi @[[User:Theki|rae]]! I have no opinion nor preference on this, and given my background, I am just entirely confused about my spelling preferences myself, as you can tell from my inconsistent usage. I learned British English in school and used that for maybe two decades or so, but moved to the US and lived there for more than a decade, enough to be naturalized, but now I am back in Europe and I am technically a professor at King's College London, soooo.... honestly, I do not know. I don't remember having put too much thought into it at the moment I created it. The good thing is that in Wikifunctions, just as in Wikidata, it is easy to change, without messing things up too much (unlike in Wikipedia), so my suggestion is, just make the change, see if anyone complains, and if they do, discuss it more. I don't know if there is a guideline already in Wikifunctions about the variants. I am happy either way, and honestly, I keep forgetting which variant is which most of the time. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 18:16, 10 May 2026 (UTC) :: I can definitely understand this, although I am unfortunately rather passionate about any minutiae involving preferential minor differences in ''anything'', of which AmE vs. BrE chiefly is. So I dedicate a lot of headspace to it. More than I should. Not that I wish to imply that the comment above that I have wrote is of an irrational nature, or done out of spite or pure emotion and subjectivity; I do genuinely believe that ''RGBA color'' is beyond just a personal preference and is just logical. I may boldly go and change it, but for some reason I was expecting that changing the English label of a Type would require elevated permissions, and I also didn't want to do it only to get immediately reverted because it ''did'' strike a chord with someone, when I could instead see how apathetic, supportive, or in opposition interested people are beforehand and ''then'' act accordingly. I was not meaning to antagonize you over your spelling habits, I did actually use British English for a few years starting in 2020 before I went back to American English, so I'd be a hypocrite for me to decry you for not always sticking to some arbitrary standard of spelling words over the other. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:55, 12 May 2026 (UTC) :Although I spell it “colour”, I think it makes more sense to use “color” for the type, since that is almost always the required spelling when the string functions as a keyword. :More generally, though, Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en". This is unusual, in my experience, as "en" is widely misused in place of "en-US", where there are recorded spelling differences. :(I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere. Use of -ize rather than -ise is a matter of personal preference or house style, but regional autocorrect encourages -ise.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:00, 12 May 2026 (UTC) :: ''Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en"'' :: Definitely agreeing with you on the latter being a good choice. However, I suspect the favoring of "colour" over "color" may be because, in terms of language codes, when sorted alphabetically <code>en-us</code> actually comes ''after'' <code>en-gb</code>. Although, the frontend seems to be sorting <code>en-ca</code> after <code>en-gb</code>, so I don't actually know how correct that is. :: ''I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere'' :: The context of the spelling was "''No program for the NLG SIG meeting for next Tuesday has been proposed''". In that usage context, I think it makes sense to assume that ''program'' is not being used to refer to a computer program, but to a ''program of events'' or similar, something that you would spell as a ''programme'' in British English. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 12 May 2026 (UTC) :{{s}} this. I'm obviously biased but I believe American English is preferable generally, American dominance on the internet (our Department of Defen'''s'''e invented it!) and rapidly-increasing consumption of American media by international English speakers means that more people use American English's conventions, this is clear through for example [http://trends.google.com/explore?q=color%2Ccolour&date=all&geo=Worldwide search trends] (though they aren't particularly reliable). Perhaps this is a bit of a supremacist opinion, but we should have internal consistency, and if we must choose, American English should be our first choice (then Indian and then British English) [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:10, 12 May 2026 (UTC) :: This is rather flawed reasoning, though. I think probably any given British or Indian person would not agree on using that as the reasoning for this, not that you are necessarily ''completely wrong'', but if this is not a good enough reason for English Wikipedia's (admittedly extremely flawed) ''ENGVAR'' policy then I don't think it's likely it will pass here either. :: Although of note is that [https://books.google.com/ngrams/graph?content=color%2Ccolour&year_start=1800&year_end=2022&corpus=en&smoothing=3&case_insensitive=true Google ngrams] agree with you, but "color" vs. "colour" is an eternal holy war that will not be won by demonstrating that more books use US spelling over Commonwealth spelling. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:44, 12 May 2026 (UTC) :::You're probably right that it's not very sound. I'm biased in that other varieties of English irk me, and that's probably mutual for people who are used to other varieties of English when they read what I write! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:56, 12 May 2026 (UTC) :I've decided to boldly [[Special:Permalink/274271|make the change]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:02, 12 May 2026 (UTC) :: Thank you. Considering both you and GrounderUK seem to consider it an okay change, I think this will do for now. :: I should note that the matter of whether to move [[Wikifunctions:Catalogue/Colour functions]] in response to this (however this discussion will ultimately turn out) is a whole other can of worms, in my view. I can't say I have an opinion on that at the moment, but I'm putting it out there regardless. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:06, 12 May 2026 (UTC) :::Personally, I'm in favor of moving the page and renaming all of the items on it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:10, 12 May 2026 (UTC) ::I don't like this (exactly because of the American hegemony you cited), but again, it shouldn't matter because the software is meant to be multilingual. Clearly there's a bug preventing you from picking an English variant/dialect as your display language. But the search bar and Function/Type autocompletion do check the English variants for matches. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 15:15, 12 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[abstract:User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:31, 11 May 2026 (UTC) :Thank you for dedicating your time to writing this, it is very informative. I will try to add input once I'm not in over my head with finals. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:27, 12 May 2026 (UTC) == Display function for HTML fragment == Currently, any collapsed Z89 literal appears as<blockquote>&lt;&gt; [[Z89|HTML fragment]]</blockquote>If I were to create a new Function which returned something like<blockquote>&lt;&gt; 123-byte HTML fragment <q><nowiki><td><span lang=</nowiki>&hellip;</q></blockquote>could that be connected to replace the collapsed form, or would it require changes to the Wikilambda software? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 16:14, 11 May 2026 (UTC) :It might work, but I doubt it. Those angled brackets suggest that the collapsed form is not simply defaulting to the type’s label. Looking at [[:phab:T410509]], I’ve concluded that enhancements to the collapsed form were never considered, rather than being actively rejected. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:12, 12 May 2026 (UTC) ::[[:Phab:T391985]] documents the original design. Note the fifth bullet point under “Acceptance criteria”. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:21, 12 May 2026 (UTC) :I'm not sure the byte-size is necessary, but the outer tag (or first outer tag, though generally I'd prefer most fragments use a wrapper tag if it needs multiple like JSX does, but that's a whole different topic) would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:51, 12 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in 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]]) 14:36, 15 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 --> == [[Z34510]] == This function, which determines if a Wikidata item for a {{q|5}} has an undeprecated {{p|21}} statement of {{q|6581097}}, returns false for {{q|173399}}, a transgender man. This is because his item assigns his P21 statement to {{q|2449503}}, not {{q|6581097}}. I'm not sure how to account for this discrepancy. Should {{z|34510}}: # Include {{q|2449503}} as a value that can lead to a true result, # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a man?") could return true for either "male" or "trans man", # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a trans man?") could return true for "trans man", # Not exist at all? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:48, 16 May 2026 (UTC) :I can't think of a single use case where you would need to determine if a person is a cisgender man and nothing else. Functions are good for generalizing across multiple possibilities when they exist, so I think it would be best if trans men were considered a part of the criteria for returning a true value. If asking for specifically {{q|6581097}}s and ''nothing'' else was desired then the function name would be a misnomer as Elliot Page is inarguably a male (at least in the view of most reasonable and intelligent people). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:03, 16 May 2026 (UTC) :You made the function in the first place; what were you planning on using it for? AW? Maybe it should return a {{Z|25501}} which can then be passed on to other NLG functions. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 May 2026 (UTC) == Lexeme from wikidata label, or "best" lexeme from wikidata item == I was looking into fixing [[Z28028]]. I found that I could add "requires grammatical feature: definite article" to "United Kingdom" (L8558). Now I'm stuck on how to get to that lexeme from {{Q|145}}. There's [[Z23471]], but that for very good reason gives you multiple lexemes with the same sense, and I just want the best one like how the label is always the best string. Is there a function that can do this? There's definitely the case of a Wikidata label that isn't a lexeme (most commonly multiple lexemes) but I'm only considering the case where it is one lexeme here. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:02, 16 May 2026 (UTC) :There is {{Z|Z27327}}, that tries to give the best lexeme through various heuristics. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 22:22, 16 May 2026 (UTC) :: Wonderful! I did stumble upon [[Z33818]] but this is perfect. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 00:25, 17 May 2026 (UTC) == [[Z29591]] isn't working for me == For instance, trying to manually put in the exact inputs for one of the test cases just returns an empty Monolingual text. See [https://www.wikifunctions.org/wiki/Z29591?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z29591%22%2C%22Z29591K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q3257809%22%7D%2C%22Z29591K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q21264361%22%7D%2C%22Z29591K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q22006653%22%7D%2C%22Z29591K4%22%3A%22Z1002%22%7D]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 01:17, 17 May 2026 (UTC) 94cr8rcy0glwntvaitl16epfegh0uni 275734 275636 2026-05-17T09:59:25Z GrounderUK 50 /* Z29591 isn't working for me */ Reply 275734 wikitext text/x-wiki {{shortcut|[[WF:CHAT]]|[[WF:PC]]|[[WF:VP]]}} __NEWSECTIONLINK__ [[Category:Help]] <!-- please do not remove this line --> Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc. Other places to find help: * [[Wikifunctions:Administrators' noticeboard]] * [[Wikifunctions:Report a technical problem]] * [[Wikifunctions:FAQ]] {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |timeout=30 }} {{Archives|{{#tag:div|<br />{{Flatlist|{{Special:PrefixIndex/WF:Project chat/Archive/|stripprefix=1|hideredirects=1}} |class=mw-collapsible-content|style=font-size:92%;}}|class="mw-collapsible mw-collapsible-toggle mw-collapsed"}} |prefix=WF:Project chat/Archive/ }} == "language" argument for certain functions == Hello. I am relatively new to Wikifunctions. Recently, I tried to create functions for Chinese translation of {{Z|Z26570}} and {{Z|Z26095}} (which became [[Z32788]] and [[Z32900]]). During the creation of these functions, I was trying to take {{Z|Z32212}} as reference. And I realized that the defining role sentence function is taking <code>language</code> as an argument (and the test case of the Chinese-language function already contains two varieties of Chinese). This makes it possible to output monolingual text in <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code>, or any varieties of the language. I think for this reason, it is better to have <code>language</code> as arguments for the implementation of Z26570 and Z26095, and potentially more functions that require {{Z|Z14294}}, since it would output the varieties code instead of just saying <code>zh</code> for <code>zh-hant</code>, <code>zh-hans</code>, <code>zh-tw</code> in the output of type {{Z|Z11}}. I am not sure how the fallback mechanism works if one of the language (varieties) do not have a labels/lexemes, but to me, it is reasonable to have a <code>language</code> argument. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 09:38, 31 March 2026 (UTC) :The functions you mention do have a language argument. For Wikifunctions, the {{Z|Z60}} can be at a higher or lower level; whether a {{Z|Z11}} is for a language or a variant is determined by the function that constructs it. Please see {{Z|Z26565}} for an example and feel free to add test cases in Chinese. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:54, 11 April 2026 (UTC) ::Hello @[[User:GrounderUK|GrounderUK]], thanks for the answer. I understand that whether {{Z|Z11}} is for a language or a variant depends on the function. But that is exactly what I am asking for. It is true that [[Z26570]] and [[Z26095]] takes [[Z60]] as argument, but the language-specific functions in {{Z|Z29843}} and {{Z|Z26096}} don't. ::Let me give you an example: INPUT to [[Z26570]]: <code>entity</code>: Tokyo, <code>class</code>: city, <code>location</code>: Japan, <code>language</code>: zh-cn, the config would select [[Z33030]] (created after my previous comment by elseone) as the implementation, and it would RETURN 东京是日本的一个城市。(zh-hans), which is not zh-cn as requested in the INPUT. It would also be using the term not for the variant (when it is different) because it is hardcoded to use the term in zh-hans. However, if we have the implementation like [[Z32790]] (which was created by me but a natural language argument was added by elseone) or [[Z32213]] (that works in the defining role sentence function because of the extra argument), it could cater for different variant. ::If we don't have the language argument in the language-specific function, the desire for article creation on Abstract Wikipedia would be to create a function for every variant. Is it then better to create functions for every variant? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:18, 11 April 2026 (UTC) :::I forgot to mention that there are some hardcoding in {{Z|Z32790}} as well, but I cannot fix it because it is a connected function and I am not a functioneer. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:31, 11 April 2026 (UTC) ::::Okay, I think it’s safe to disconnect this one as the function is not yet configured for use on Abstract Wikipedia. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:04, 11 April 2026 (UTC) :::Ah, sorry… I misunderstood you. I agree that the called function should be able to accept the original language argument. That is simpler in theory than in practice, because the configured functions all have to have the same argument types, as I understand it. I’m not sure which the best approach is, really, but we probably want to avoid two levels of configuration. That suggests that all language-specific functions would need to accept the additional argument, which is unrewarding work for someone. @[[User:99of9|99of9]], @[[User:Jdforrester (WMF)|Jdforrester (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]] Any thoughts? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 18:57, 11 April 2026 (UTC) ::::I mean, we would need to modify all the functions in each language, which could take some time. But we are still in an early stage. If we don't fix it now and we want to fix it later, it would be a disaster. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 19:25, 11 April 2026 (UTC) :::::Agreed. And we probably want them converted to HTML too, with separate language spans for text in different languages. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 19:35, 11 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]: This sounds like a reasonable change to make. Note that (given these Functions are primarily for use on Abstract Wikipedia), altering/replacing them to return Z89/HTML fragments is already a desired but breaking change, so making a second breaking change at the same time is probably easiest for fixing things swiftly. That said, that's of course a decision for the Abstract Wikipedia and Wikifunctions communities, not me! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:43, 12 April 2026 (UTC) ::::@[[User:GrounderUK|GrounderUK]]@[[User:Sun8908|Sun8908]] to make it a non-breaking change, I've created {{Z|Z34039}} which allows a composition {{Z|Z34043}}. This way you can make functions which either need the specified variant or don't! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 05:52, 24 April 2026 (UTC) :I have now created {{Z|Z33465}}, which is an implementation of [[Z26570]]. Maybe we can migrate to use that function when more (language-specific) functions for it are ready? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:19, 14 April 2026 (UTC) == Actual difference between {{Z|Z26039}} and {{Z|Z26095}} == What is the actual difference between these two functions? I ask, since it seems to me that the current distinction is more or less that the first one doesn't use an indefinite article in English, while the second does. Which is not a good distinction in a project that should be language neutral. This doubt emerged from my use of the first one in [[abstract:Q124441]], which @[[User:Hogü-456|Hogü-456]] made me notice that is probably wrong. My question is: why is it wrong? How could we clarify the difference? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:46, 19 April 2026 (UTC) :I think the difference is if there is an indefinite article like a or an before the subject or not. In German there can be cases where a definite article is necessary before the subject. I looked at the functions and before the object both times an article is mentioned. As it depends on the language and the word what is the correct function to use I hope it will be clarified and it is an example of the necessity to have a human with understanding in a specific language check it. I hope there will be longer functions what generate more content about a specific kind of item. Then it is necessary to write one such function per language and it can be then applied to several items. It still requires checks and so maybe it is better to write down what item category needs what kind of introduction sentence function for what language. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:05, 19 April 2026 (UTC) ::The point of these two functions (and of the entire Abstract Wikipedia project) is that they should be defined in a purely language-independent way, so that the translation to actual language can be done automatically. This is the reason why these functions have been renamed; I think that this attempt was not succesful, since meaning is still unclear. My proposal to clarify them would be to invoke the concept of [[w:specificity (linguistics)|specificity]]: {{Z|Z26039}} should be named "specific subject is instance of (string)", and should be used only when the QID of the subject uniquely identifies a single thing; {{Z|Z26095}} should instead be renamed in "non-specific subject is kind of (Monolingual text)", and should be used when the QID refers to a multitude of real life items, and we are specifying the class that all these item belong to. This clarification would not still be enough, since it doesn't explain how mass nouns are handled (is water a unique thing? Does {{Q|Q7802}} refer to a single piece of bread or to the entirety of bread, like water?). This problem is very tricky, since mass noun are language-specific and blurry the line between these two functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 20:58, 19 April 2026 (UTC) :Simply put, one corresponds to P31 and the other to P279. Paris is an {{Q|P31}} a {{Q|Q1549591}} :whereas a {{Q|Q1549591}} is a {{Q|P279}} (alias “kind of”) {{Q|Q515}}. Whether the Wikidata knowledge representation will be sufficient to resolve into fluent natural language representations in all languages is, of course, a crucial question. Where it is not, the Abstract Wikipedia knowledge representation will need to supplement the Wikidata content with additional details about the relation between the participants or the participants themselves, and these details should be language-neutral, to the extent that this is practicable. The item {{Q|Q124441}} has no [[:d:Q124441#P31|P31]] statements; it has only [[:d:Q124441#P279|P279]]s, including one relating it to {{Q|Q212920}}, which suggests {{Z|Z26095}} is the appropriate choice here even if the rendering in some languages is the same. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:52, 19 April 2026 (UTC) ::Thanks for explaining it. I think that I'll change the implementation of {{Z|Z26095}}, so that in Italian it produces more or less the same output of {{Z|Z26039}} (both with the definite article). [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:24, 20 April 2026 (UTC) == Equivalent of Z6830 for lexemes == Is there an equivalent of {{Z|Z6830}} that enables retrieving all lexemes pointing to a particular lexeme using a specific property? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 21:06, 20 April 2026 (UTC) :There's {{Z|6831}} but I think that's slightly different again to what you're after. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 12:31, 21 April 2026 (UTC) ::Thanks for sharing that one, I did not know it existed. But you are right, it’s not quite what I am looking for. I want a function that would take a Wikidata property reference (like P5191, which is ‘derived from lexeme’) and a Wikidata lexeme reference, and return a list of lexemes that reference that lexeme using that property. [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 13:23, 21 April 2026 (UTC) == Storing huge datasets == It is not a necessity I suppose, but an idea came to me earlier to write a function that would give the corresponding [[en:Shavian alphabet|Shavian alphabet representation]] of an English word written with the Latin alphabet, or perhaps apply that operation to an entire sentence. However, just trying to guess as to what the IPA pronunciation of each word passed into it could be is is both not ideal (pronunciations obviously can and will vary widely between accents) and infeasible <s>(Wikidata lexemes don't really seem to account for pronunciation)</s>. It happens, though, that a comprehensive Shavian dictionary exists named the [https://readlex.pythonanywhere.com/ ''Read Lexicon''], which uses pronunciation and spelling similar to that used by the creator of the alphabet himself. This would be a good dataset to use in performing this translation in the function, but it appears that, all in all, the total size of the dictionary is [https://github.com/Shavian-info/readlex/blob/main/readlex.json ''nearly 26MB''] when formatted as JSON, which would certainly be larger when converted into a typed list. I am wondering if this will ever be feasible or admissible, or if there is really a way around this if importing such a large set of data is deemed impractical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 22:30, 20 April 2026 (UTC) :{{re|Theki}} "Wikidata lexemes don't really seem to account for pronunciation"" is patently untrue; not only does every Bokmål lexeme form have IPA attached to it (thanks to Jon Harald Søby), but there are lots of languages--including English--that have pronunciation information, whether through IPA or otherwise, indicated on their forms. The big issue of course is that adding this data is not always possible to perform efficiently--for instance, I'd love to have Yiddish pronunciation respellings from Paul Abelson's dictionary on as many English forms as possible, but this dictionary not being previously processed makes this difficult. The data set you have brought up, if a suitable reading of [[:m:Wikilegal/Lexicographical_Data]] allows it, could be added as {{P|7243}} statements on various English forms. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 23:20, 20 April 2026 (UTC) ::Well, sorry... I haven't witnessed these pronunciation statements before, I wasn't aware of their existence until you pointed it out. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 21 April 2026 (UTC) :I got 1,900,000 characters into [[Z33875]] before the UI gave up on me. I'm not sure what the limit is. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:21, 21 April 2026 (UTC) == Could not serialize input JS object: Number <small><small>[insert tested number here]</small></small> == I'm not one to throw my problems at others, but I have no idea how to fix this. Am implementing {{Z|Z24602}} in JavaScript, which requires returning a typed map. It now works for every type of value except numbers. Tried explicitly converting the numbers to float64, but either way it throws the error above. Would appreciate it if anyone could diagnose or fix the problem, as my knowledge of Wikifunctions is amateur at best. Thank you. [[User:Some helpful person|Some helpful person]] ([[User talk:Some helpful person|talk]]) 00:32, 23 April 2026 (UTC) :The quick answer is that like some list-related functions, code implementations returning typed maps are not possible unless the type of the objects in the map is specified in the function signature (e.g. if it was a map from Strings to Natural numbers only). So unfortunately, I think you've chosen a function that is not really possible at the moment. There are a few ideas of how we might address this, but for the moment, work on something else. Sorry! --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 13:21, 23 April 2026 (UTC) :Maybe explicitly using [[Z13518|natural numbers]] would work? I would try using <code>{ "Z1K1": "Z13518", "Z13518K1": "[number]" }</code> to represent numbers, perhaps, and seeing if that works. Of course, you would also probably have to adapt this for other types that cannot be serialized, and I'm not sure how easy that would be to generalize (assuming [[w:Don't repeat yourself|DRYness]] is desired). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:39, 23 April 2026 (UTC) == Help with creating a function for Abstract Wikipedia == Hello! I was inspired by {{Z|Z26570}} to create {{Z|Z33975}}, however I'm not sure how I add specific language implementations here. Can anybody help me? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 10:41, 23 April 2026 (UTC) : I think I figured it out, I created a new object with the language config type, added {{Z|Z14310}} to my implementation, and added a new function for English... At least I think that's how it works... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 13:16, 23 April 2026 (UTC) ::You have the right idea, as far as I know. I went ahead and connected the implementations you created as they appear to work fine for English, and added a test for {{Z|Z33975}} (which passes [[File:Twemoji 1f601.svg|24px]]). I also corrected an error you made on the config object where you appear to have accidentally connected English to {{Z|Z33975}} instead of {{Z|Z33977}}. Thank you for contributing! &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 13:45, 23 April 2026 (UTC) ::: {{re|Theki}} Thank you so much for you help! Could you please kindly also connect the implementations for {{Z|Z33986}} which I just made, which is going to be used for the Hebrew implementation of {{Z|Z33975}}. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:11, 23 April 2026 (UTC) ::::You seem to be returning the wrong type in both implementations. Functioneers should not connect implementations that don't work for non-functioneers. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:13, 23 April 2026 (UTC) ::::: {{re|Feeglgeef}} Oh thank you for pointing that out! I am still a bit new to this project and confused, so I need to read up some more about this. How do I return a monolingual text object? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:17, 23 April 2026 (UTC) ::::::I'm trying to fix it for you, the construction of ZObjects in code implementations is a bit difficult right now. Since the State origin using entity and class function will (presumably) be composition, perhaps {{Z|33975}} can be adjusted to return a string, using {{Z|26107}} and {{Z|26107}}? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:21, 23 April 2026 (UTC) :::::I did not notice any discrepancies from looking at the functions by themselves, and it seemed to work fine on my end. Is it bad practice for NLG functions to return the monolingual text type? I had assumed it was logical. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:24, 23 April 2026 (UTC) ::::::Both implementations are failing all three tests on my end. No consensus has been established as to whether monolingual texts or strings should be used, so it's like the [[w:War of the currents|war of the currents]] but for Wikifunctions. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:27, 23 April 2026 (UTC) :::::::Oh, you were referring to {{Z|Z33986}}. I assumed you were stating that something was wrong in the earlier English functions that I missed; I apologize for the misunderstanding. Has there been any centralized discussion on this string vs. monolingual text issue? &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:31, 23 April 2026 (UTC) ::::::::Not that I'm aware of, I've brought it up on the telegram twice before, though. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:49, 23 April 2026 (UTC) ::::::::The centralised discussion is at [[WT:Abstract Wikipedia/2025 fragment experiments#Proposed recommendation: Fragments should return Z11/monolingual strings]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:19, 24 April 2026 (UTC) ::::::: {{re|Theki|Feeglgeef}} Can only functioneers test implementations? For me I can't test it at all... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 14:32, 23 April 2026 (UTC) ::::::::AFAIK, test cases are only immediately testable during editing of a function if they are connected. This is one of my personal pain points with Wikifunctions, iterating on functions without exhaustive connected test cases makes debugging practically impossible for non-functioneers working on newly-created functions... I (or Feeglgeef) can quickly connect the tests you need for you if you want, although if they are not well-formed they may need to be disconnected again afterwards. Additionally, I could temporarily connect the implementation you are writing so that you can test it on the sidebar as you work, but I'm not sure if this is advisable. That functionality is also something that unfortunately only works when not disconnected. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:43, 23 April 2026 (UTC) :::::::::Yup, agree with you on all points, thanks. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:48, 23 April 2026 (UTC) == Please disconnect implementation == I think I've fixed my issue with {{Z|Z33986}}, but I can't edit an actively connected implementations with my rights. I must admit it is an AI-aided fix, I feel very strongly about disclosing that. Courtesy pinging [[User:Theki]] and [[User:Feeglgeef]]. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:51, 23 April 2026 (UTC) : Additionally, I think the JS might be working. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:52, 23 April 2026 (UTC) : Just to clarify, I mean disconnect the Python implementation please. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 18:53, 23 April 2026 (UTC) :{{Done}} I've disconnected the Python implementation. :I've also added a couple of tests. The rule is a bit more complicated than adding a maqaf before every character that is not a Hebrew letter. Unfortunately, I don't think I'll have time to fix the implementations any time soon. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:03, 23 April 2026 (UTC) :: Thank you! :: Also, for some reason I thought you put a maqaf before all gershayim, so thanks for correcting me. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:09, 23 April 2026 (UTC) :::No, that's not the rule. :::The rest of this reply is an [[:wikt:info-dump|infodump]], feel free to ignore it :) :::In [https://hebrew-academy.org.il/topic/hahlatot/punctuation/ the Academy's punctuation rules], the rule for adding a maqaf is written kind of badly: שמים מקף ברצף שיש בו שני סוגי גופנים, כגון אותיות ומספרים ("maqaf is added in a sequence in which there are two types of fonts, such as letters and numerals"). These are not different types of "fonts", but different types of characters, and I should email them about it. It gives the examples <span lang="he" dir="rtl">ה־12</span> and <span lang="he" dir="rtl">ב־DNA</span>. It doesn't say anything explicitly about quotation marks, but in other places on the same page, you have stuff like <span lang="he" dir="rtl">ב"הארץ"</span>, and from that I deduce that a maqaf is not needed before double quotes if there are Hebrew letters inside the double quotes. :::That said, a few people do think that there must be a maqaf before double quotes. I have a somewhat surprising example of somebody who always does it: translators of Scientology materials into Hebrew. At least that's what they did last time I looked at them, about ten years ago. Those people are certainly prolific, and they get points from me for consistency, but this not the prevalent standard. (And if I recall correctly, they use the minus and not the proper Hebrew maqaf, and they don't get any points from me for that!) :::Also, the name of the character is just "double quotes" and not "gershayim". Gershayim are mostly for abbreviations, although most people use the same character for them. I use ״ for gershayim, as do a few other nerds, but we're the minority. [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 19:35, 23 April 2026 (UTC) :::: {{re|Amire80}} Yeah, "font" is a weird choice of wording here by the Academy...<br> I think I'll follow your guidance and not use a maqaf for quotes beginning with Hebrew letters. <br> I should also add more tests for different types of quotes, like straight (", '), curly (“, ”, ‘, ’), gershayim (״, ׳), including single quotes.<br> P.S. gotta deduct points from Scientology for being a cult but that's neither here nor there [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:49, 23 April 2026 (UTC) :::: {{re|Amire80}} Courtesy ping because I mistyped your username on the last message. Anyways I'm also gonna do that tomorrow because I'm tired now... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:50, 23 April 2026 (UTC) == Connect implementations == Hello! I'm done with the implementations of {{Z|Z33986}} both in JS and Python, and all tests pass. Pinging @[[User:Amire80|Amire80]] to check if all the tests I've added are alright. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 15:24, 24 April 2026 (UTC) :Connected. It's possible that some more changes will be needed, but it looks OK now. :Another little comment: It should be called "clitic" and not "prefix". [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:56, 24 April 2026 (UTC) : {{re|Amire80}} Thanks for your comment! Luckily labels are easy to edit, so I'll get to it. : Currently I'm working on Bulgarian {{z|Z34072}} and {{z|Z34084}}, along with other Bulgarian functions. After I'm finished with those I'll take your advice. [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 16:01, 24 April 2026 (UTC) == Please connect my Bulgarian implementations == I recently created the following Bulgarian functions: * {{Z|Z34070}} (currently broken, I think because another function I built it upon is unimplemented) * {{Z|Z34088}} * {{Z|Z34105}} * {{Z|Z34072}} * {{Z|Z34084}} Can somebody please connect these functions, and perhaps suggest other functions I could localize? [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:03, 24 April 2026 (UTC) : Specifically, [[Z34070]] is based on [[Z34072]] [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 19:05, 24 April 2026 (UTC) :{{done}} for everything that passes, [[Z34070]] still does not work after purging WF's cache, though. For future reference, please request on the [[WF:Community portal|community portal]] instead of the project chat. Thank you for your work! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 20:03, 24 April 2026 (UTC) :: {{re|Feeglgeef}} Thank you for your help! I will keep in mind to go to the [[project: community portal| community portal]] in future instead for this. :: I still don't understand why {{Z|Z34070}} fails... It's implementation is almost completely identical to [[Z30399]] from {{Z|Z30397}}, unless I messed something up... [[User:QuickQuokka|QuickQuokka]] ([[User talk:QuickQuokka|talk]]) 20:11, 24 April 2026 (UTC) :::{{done}} No, it was mostly just timing out. It is better to use selective fetches where possible. One case is failing to match the expected results, but at least it is returning something. For all I know, it might even be acceptable! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 20:35, 24 April 2026 (UTC) :::: {{re|GrounderUK}} Thank you so much for your help! The one failed case is with a definite article, so I feel like that might be fixed in the future... <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:43, 24 April 2026 (UTC) == Editor experience suggestions == I'm a bit frustrated with the editing experience on Wikifunctions, and I have suggestions based on pain points I've had contributing to this project: * Adding a wizard to create functions, implementations, and tests in one flow, somewhat like Wikimedia Commons' upload wizard * A sandbox for experimenting without changing mainspace functions, and maybe letting non-functioneers connect implementations ([[Project: Sandbox]] doesn't seem to fit this) * We could have functions for creation based on the sandbox, like how Wikipedia has articles for creation and edit requests, * Maybe even another test instance of Wikifunctions, like how Wikidata has [[testwikidata:|Test Wikidata]] I really like this project and I don't mean to whine, but it certainly has a lot of pain points both for technical and non-technical people. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:41, 24 April 2026 (UTC) : It's also really complicated to localize functions, so maybe we should add another wizard for that, where you can choose a language, and then create the new function with the aforementioned function wizard, and it just automatically adds it to the related language configuration object of the related function. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 20:48, 24 April 2026 (UTC) :# Sounds good to me. :# A sandbox available is [[Z10119]], though an extension-provided sandbox that allows you to manipulate the types, code, and tests easily without interfering with the mainspace would be nice. :# [[WF:Suggest a function|This page]] works to some extent, though it's too messy in my opinion. :# We used to have a "beta cluster" but it [[phab:rOMWC5f625c5846b5f779473fa32c9a02d87e59215dfa|got shut down]] just over a year ago because it was broken. :[[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 21:07, 24 April 2026 (UTC) == Language parameters in language-specific functions == I think that an effort should be made to give the different natural language options corresponding to different English dialects, Chinese scripts, etc. more of a use (I added the test {{Z|Z34119}} to {{Z|Z26095}} and unsurprisingly it fails). There are two main problems with this approach that I can identify: * If you ask the majority of these functions to make a sentence in British English, much of the time it will give you an output with missing words, because it does not fallback to English labels in the case of a British English label for that item missing. The same applies for every other English dialect, British English is just an example here. * Uninformed editors will probably see the presence of a language parameter on these functions, consider it redundant, and remove it. [[Special:Diff/268074|I have made this mistake before]]. In my opinion, in a perfect world, all of these language generation functions would output monolingual text, and if the user asks for American English text, then American English text is what they'll get. If the user asks for Japanese text in hiragana specifically, then that's what they'll get in return. This is not as high-priority as just rendering text in the language plainly in the first place, but it's something that I feel is still worth devoting some effort to. Right now switching functions to use this paradigm is difficult because, on the one hand, I don't know if consensus tends towards this direction being ideal or advisable, and I don't want to make changes like this without at least notifying the wider community. In addition, all tests break once a parameter is added or removed, and the function editor does not recognize the change in number of parameters and therefore you have to remove the function call, re-add it along with all of its parameters it had previously (which is a tedious cut-and-paste job), and then it will work again. This is something that you can do in five seconds by just adding a few lines of JSON to the test source, but this is not directly editable from the Web browser. This tedium is largely what's preventing me from doing this on a larger scale, besides asking for comments first. If anyone has any insights or comments on this, then that would be appreciated. If a reference of functions with and without the support for language variants is needed, of course [[WF:NLG]] can be perused, but I've also my own list cataloged at [[User:Theki/functions#language]]... Of course, this thread has many similarities to [[#"language" argument for certain functions|the one above]], but this concerns me going out and making this consistent across these NLG functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:09, 24 April 2026 (UTC) :I've created {{Z|Z34122}} as an extension to {{Z|Z34039}} for larger functions. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:34, 24 April 2026 (UTC) :Just to confirm that I, for one, support a Natural language parameter for all natural-language functions. The concern about getting them all aligned is just that we haven’t finally settled on {{Z|Z11}} being preferred to {{Z|Z89}} or some other type that conserves the text’s provenance, so we risk having to change them all again. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:07, 25 April 2026 (UTC) == “Key not found ()”? == What am I doing wrong in {{Z|Z34137}}? [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 00:39, 25 April 2026 (UTC) :You were passing a [[Z6091]] to {{Z|32290}}, but it takes a [[Z6001]]. Fixed. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 07:10, 26 April 2026 (UTC) ::{{done|Thank you}}! [[User:Redmin|Redmin]] ([[User talk:Redmin|talk]]) 14:13, 26 April 2026 (UTC) == Why is my test failing? == Hello! I recently made {{Z|Z34139}} based on [[wikt:Module:bg-translit]], and the test case {{Z|Z34141}} is failing on both implementations, despite the expected output and actual output being the same as far as I can tell. I tried looking at the Unicode codepoints of the output, but those are also identical. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 06:21, 25 April 2026 (UTC) :Yes, it’s a tricky one. I’ve added a normalize step to the result validation in {{Z|Z34141}}, which confirms it is a normalization issue. It looks like it is in the code but I don’t know whether simply normalizing the result is the way to go. Logically, you would normalize both the input and the result. The implementations of {{Z|Z10384}} show you how to do this. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:41, 25 April 2026 (UTC) == Edit request == Hello! I have an edit request for {{Z|Z23752}} and {{Z|Z23414}}. Please replace all the "an/a" logic with <code>Z21739(Argument reference)</code>, both for readability and for more accuracy ("a university is an institution") <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:50, 25 April 2026 (UTC) :{{D}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:24, 25 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #245 is out: The Foundation's search for the perfect language == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-25|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we present an academic paper about Abstract Wikipedia, we discuss our latest Type created, and we take a look at the newest created functions. 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:54, 25 April 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=30325620 --> :@[[User:Sannita (WMF)|Sannita (WMF)]], @[[User:DVrandecic (WMF)|DVrandecic (WMF)]], technical meta-question: the newsletter quotes the article: ::the only way to contest its algorithm is to click 👍 or 👎 (Crawford and Gillespie 2016) :This quotation sounds sensible, but the article's [https://link.springer.com/article/10.1007/s00146-026-02899-w web version], and the PDF that is downloadable from the same page doesn't actually show the emojis. It rather shows text that looks lacking: ::the only way to contest its algorithm is to click or (Crawford and Gillespie [https://link.springer.com/article/10.1007/s00146-026-02899-w#ref-CR14 2016]) :Where did you get the emojis? Is it your (probably correct) guess or is there a version somewhere that actually shows the emojis? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:16, 25 April 2026 (UTC) ::Scratch that. I've found a version with correct emojis: https://wikihistories.github.io/wikilambda-the-ultimate/ [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 15:37, 25 April 2026 (UTC) == Requested deletion of test == Please delete {{Z|Z34143}}. this was never valid Bulgarian, I messed up. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:19, 25 April 2026 (UTC) :[[WF:RFD]] please. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 16:40, 25 April 2026 (UTC) == Request for comment (global AI policy) == <bdi lang="en" dir="ltr" class="mw-content-ltr"> A [[:m:Requests for comment/Artificial intelligence policy|request for comment]] is currently being held to decide on a global AI policy. {{int:Feedback-thanks-title}} [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|talk]]) 00:57, 26 April 2026 (UTC) </bdi> <!-- Message sent by User:Codename Noreste@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Distribution_list/Global_message_delivery&oldid=30424282 --> == Is it OK to connect the implementation? == Hello! I recently applied for functioneer on [[WF:RFG]], and I was wondering whether I could connect the implementation for {{Z|Z34165}} despite its dependency {{Z|Z34149}} being currently unimplemented. That is <em>if</em> I get accepted. I am planning on implementing it based on [[wikt:module:bg-nominal]], but am still having trouble figuring it out for now. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 09:04, 26 April 2026 (UTC) == Past tense function == Is there a function like {{Z|Z26039}}, but for the past tense (e.g. "Leo Tolstoy <em>was</em> a writer.")? If not, I will create it myself, I just want to make sure there's not a duplicate. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:10, 26 April 2026 (UTC) : {{Done}} with {{Z|Z34224}}, but I have a few kinks to work out with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:35, 26 April 2026 (UTC) :: I need to create some other similar functions for the past tense, I have some ideas: ::* {{Z|Z26095}} ::* {{Z|Z32643}} ::* {{Z|Z28016}} ::* {{Z|Z26570}} ::* {{Z|Z33975}} ::* {{Z|Z27243}} ::* <ins>{{Z|Z26627}}</ins> ::* <ins>{{Z|Z27627}}</ins> ::* <ins>{{Z|Z27173}}</ins> ::* <ins>{{Z|Z29591}}</ins> :: :: Are there any I have missed? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:57, 26 April 2026 (UTC) :I think that here we are starting to walk on dangerous waters: what does past mean? Is it a recent o a far past? Does it have ripercussions on the present or not? Is it just a thing that happened once, many times or for a continuative period of time? :Consider that various languages distinguish between many different types of past. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:38, 26 April 2026 (UTC) :: {{re|Dv103}} That is a fair point... :: How do we go about solving this problem though? I don't think having every sentence on Abstract Wikipedia be "X is a Y" is a very good idea. :: Maybe we have different functions for all these variations of past you mentioned that just map into "X was a Y." in English? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 13:31, 26 April 2026 (UTC) :::To properly solve this problem, we should use a more complete abstract content representation model, like for example the proposal of [[Wikifunctions:Type proposals/Semantic unit|Semantic units]] (look at [[Wikifunctions:Type proposals/Semantic unit/Douglas Adams|the example]] to see how times could be handled). For now, since we're still stuck with single fragment generation functions (that I hope will be slowly replaced with the complete represenation model, when available), we could just restrict your function to a very specific meaning, like "subject was an instance of, for most of its existence" (which means for example that it could be used to say "Douglas Adams was a writer", but not "Abraham Lincoln was a president", since he only was a president for 4 years). Probably my definition is still too vague, and this is why we need to go beyond these fragment generating functions. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:47, 26 April 2026 (UTC) ::Nitpick... I don't like that it outputs a string instead of monolingual text. With {{Z|Z26039}} it's used so much that I think it's unfixable in that case beyond deprecating it if people care that much, but {{Z|Z34224}} doesn't even have any connected implementations yet. Consider it, maybe? ::Nitpick 2... {{Z|Z34227}} is missing a language parameter. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:08, 26 April 2026 (UTC) ::: I will consider that! ::: I just did that because that's what {{Z|Z26039}} does, so I assumed I should follow suit with it. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 26 April 2026 (UTC) == Legacy functions == If and when more robust methods of abstractly representing and generating linguistic content come around, and more efficient ways of creating abstract content are devised and implemented, I suspect that our current methods will require some form of deprecation. This is a significant source of concern for me in relation to WF and AW, questioning how prone our current methods of doing things are and eventually will be prone to obsolescence, and how it will be worked around when it comes. We have over 1 250 articles on AW presently, and these are rather all over the place. I suspect the maintenance burden from keeping these articles up to code will eventually, err, creep up on us, I suppose, and some kind of major refactoring will be necessary. We are definitely in a period of experimentation and whatnot right now but eventually, like with enwiki, some sort of structure and rigor will form and I suspect it will start to become rather boring for me... I, for one, very much enjoy experimenting with new and better ways to do things here. I don't personally mind changing things to use a new and better paradigm if need be, that sort of thing highly excites me, but of course there will be things that are left behind, and I suspect maybe bots will be employed to deal with this? A lot of Wikipedia sister sites seem to do that, e.g. going and fixing up use of deprecated templates. Considering the nature of Wikifunctions and Abstract Wikipedia I suspect certain maintenance tasks will be made simpler or even trivial by the typical uniformity of our implementations. I guess I am just concerned if Wikifunctions or Abstract Wikipedia will ever accrue its own kind of "technical debt" with how we are plowing through things presently, and if there is a plan for how we will eventually seek to mitigate that. Maybe too early to ask this question, but I am a notoriously anxious person, so I thought it wouldn't hurt to raise the question regardless... &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 21:30, 26 April 2026 (UTC) :I very much agree, thank you for expressing my position so well. {{ping|Immanuelle}} has been using an AI-generated tool (well, they haven't edited in a week, perhaps it's a break or perhaps they don't wish to contribute to the project any more) to create a bunch of articles en masse, which I have warned them multiple times is a bad idea (on top of evolving functions, all of the articles are one-sentence-per-paragraph, [[abstract:Q12184|like so]]). That's why I've been avoiding creating articles recently, I'd say I have a good fourth (no data to support, rough guess) of the comments on the wiki, yet less than a percentage of the article count (only three, including the [[abstract:Q319|first article]], though, so perhaps I'm the next [[w:Special:Permalink/908493298|office.bomis.com]]). [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:41, 27 April 2026 (UTC) :: I feel that the overwhelming presence of these low-quality articles (which I admit I myself am [[abstract:Q1710970|guilty]]/[[abstract:Q7601858|of]]/[[abstract:Q39338|creating]], usually as testbeds) may incur a large maintenance burden. I do expect them to be easy to detect, however, as searching for the presence of "deprecated" NLG functions is trivial, and it is possible that replacing them with their future ''even abstracter&trade;'' counterparts could be done automatically since they all have the same signatures and can be expected to create the same form of sentence. If it needs to be done manually for a while or for certain delinquent instances, my hope is that it will be fun, at least for a while. :: I just hope that these hypothetical future waves of "this new and versatile way of abstractly representing linguistic content" obsoleting previous methods and requiring refactoring across all articles is only a one-time thing. We should strive to be as robust and flexible as possible from the outset as each brand new paradigm of abstraction is also a brand new maintenance burden for updating old articles. At the end of the day, at least ''some'' of these articles will still render to many different languages even if their methods of creating those sentences of theirs is completely outdated. Ergo, the time it takes for the switchover to be performed across our articles should not be a persistent inconvenience for users (as, of course, they will always still be able to read the content as it was before since these legacy functions aren't being deleted outright), and the increased availability that the new methods will bring about will likely act as motivation for them to join the effort in refactoring (&#x300C;You're telling me that if I rewrite this article in this cool Lisp-looking stuff then I can probably read it in [[abstract:Q9307|Galician]]?? COOL!&#x300D;). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 20:26, 27 April 2026 (UTC) :::Totally agree. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:54, 28 April 2026 (UTC) :::My vague plan is to implement a default function returning an {{Z|Z89}}, for each language-neutral function. A single function would convert any of these to a {{Z|Z11}}, so that a composition of the two can be implemented as the current default until such time as the language-neutral function is ready to return a [[Z89]]. We can already convert a [[Z11]] to a [[Z89]] so, although there is more to be done in this space, existing language-specific functions could be adapted to return a [[Z89]] quite mechanistically. :::Although we certainly could deliver parallel Z89 functions for each existing Z11 function, I don’t think we should assume that particular outcome. Provided the Z89 captures a lang attribute from the Z11’s language tag, the two representations should be largely interchangeable, although I am expecting a Z89 to carry additional attributes at the span level that would be lost on conversion to a Z11 (along with any higher-level tags and attributes). :::When I say there is “more to be done in this space”, I am referring to a new type that would allow HTML fragments to be represented as tractable Wikifunctions objects, but this is currently drafted only in my head! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:21, 29 April 2026 (UTC) == Filtering types of objects == Hello! I have tried to comb through my own edit history several times, but it's really hard to search for specifics because there's no differentiation between different types of objects (functions, implementations, tests, etc.) in the logs as far as I can tell. Am I missing anything? I want it to work sort of like how filtering by namespace works. <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:48, 27 April 2026 (UTC) :There is differentiation, it's just rather hard to look through. Since all ZObjects are just JSON data at their core, you can search for instances of <code>{ "Z1K1": "Z[type]"</code>. I haven't tried this so I'm not sure how well it would work and I know MediaWiki search syntax treats quotation marks as a special character, but I have seen Wikifunctions pages link to searches using this before. There is also [[Special:ListObjectsByType]] but it is sitewide rather than specific to your edit history in particular. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 18:59, 27 April 2026 (UTC) ::''[It doesn’t help directly here, but please see [[WF:Find]] for more details of how this works.]'' [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:24, 29 April 2026 (UTC) :See the feature requests [[phab:T399244]]/[[phab:T373735]]. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 06:06, 28 April 2026 (UTC) :The lack of filtering edits by namespace is exactly the problem that I was trying to solve with the [[User:Amire80/wikifunctionsanalytics]] tool. :I even kind of succeeded, but it has two major problems: :# It doesn't have any real frontend, so you have to know some SQL to use it (or ask other people who know SQL). :# It doesn't get information from the live site, but from the dump, which appears to be updated once a month. :I've made a [https://quarry.wmcloud.org/query/104794 sample query for you]. Unfortunately, it won't do anything at the moment because of the second problem—your edits started in April 2026, which isn't over yet, so the dump for it hasn't been processed. But I hope that early in May you'll be able to use the same query and see something useful. :(I plan to add support for recent edits, but I haven't done it yet. Now that I more or less figured out how to process Wikifunctions edits, I'm focused on trying to understand Abstract Wikipedia edits. Processing up-to-date edits from both sites will possibly be the next thing I work on, but if you know some Python and want to try doing it yourself, don't wait for me—[https://gitlab.wikimedia.org/toolforge-repos/wikifunctions-analytics Patches welcome].) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 18:51, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]], I've just updated the data until the end of April. Now the query to which I linked above gives some results. You can also try running other queries if you know SQL. (Or try asking for other queries if you don't.) [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 03:26, 3 May 2026 (UTC) == [[Z34213]] == I'm not quite sure why this implementation is failing. Could someone take a look? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 02:24, 28 April 2026 (UTC) :I've [https://phabricator.wikimedia.org/T419933#11863997 notified] the team that this is still occurring, the issue was marked as resolved. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 02:52, 28 April 2026 (UTC) :Some useful tips: :* create more testcases: sometimes it is a random error, so try to see how consistent it is between testcases :* your implementation is very inefficient, since it fetches items and lexemes a lot of times. Ideally, each item and each lexeme should be only fetched once in all the execution tree. :[[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 06:06, 28 April 2026 (UTC) ::Caching (''should?'') means that the lexeme and item data are cached, so the call doesn't actually execute multiple times. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 17:51, 28 April 2026 (UTC) :::Are lexemes and items actually cached within the same function execution? Even if they are only partially fetched and/or fetched in bulk? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 17:54, 28 April 2026 (UTC) ::::I don't have any evidence to prove that it works but that's definitely A. what's supposed to happen and B. the ideal behavior. This happens because the Z680X functions can be cached just like any other. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 18:02, 28 April 2026 (UTC) ::::It is unclear. In general, I believe identical branches are resolved only once in orchestration, but there is also independent caching of Wikidata fetches. ::::According to @[[User:DMartin (WMF)|DMartin (WMF)]] ([https://t.me/Wikifunctions/30374 on Telegram]): ::::<blockquote>Well, no. We have caching of Wikidata entities that have been retrieved, but not of the results of nested function calls. There is a proposal for doing this in the context of the V2 composition language, when it's a bit more mature, and it's regarded as a relatively high priority.</blockquote> ::::It’s hard to tell whether fetches in nested calls are, in fact, cached and available for other nested calls in the same call, since it is not generally the actual fetch that consumes the most resources. Rather (I believe), it is construction and transmission of the result object, which is currently repeated afresh in each nested call (unless it is in an identical branch). ::::I hope that’s clear, and I apologise in advance if it happens to be inaccurate! [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:16, 29 April 2026 (UTC) :::::Oh, I should clarify.  There is a lot of caching going on, in several different places.  Lexemes and items ''are'' cached by the orchestrator within the same function execution, even if they are only partially fetched and/or fetched in bulk.  When I said that we don't have caching of the results of nested function calls, I meant that's not happening in general, for all nested function calls in compositions.  But fetching of Wikidata entities gets special treatment, so yes, fetched content from Wikidata is cached, regardless if it was fetched by a top-level call or a nested call. :::::It is also true that the construction of a ZObject from the fetched JSON might happen more than once within the same function execution, depending on how a composition has been structured. However, the construction of the ZObject is actually very fast, compared to the elapsed time of getting the JSON from Wikidata. [[User:DMartin (WMF)|DMartin (WMF)]] ([[User talk:DMartin (WMF)|talk]]) 18:04, 1 May 2026 (UTC) == Question about cardinal numbers == I was about to edit {{Z|Z16435}} to add my function {{Z|Z34308}}, but I noticed that none of the other functions have a gender parameter. Should I create a new wrapper function "Bulgarian cardinal, neuter", or should I just remove the gender parameter and always return neuter? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 10:39, 28 April 2026 (UTC) :The “cardinal” functions should return the words used for “counting” numbers in the abstract. :We should consider converting them to return a {{Z|Z11}} rather than a {{Z|Z6}}. It may even be appropriate to return a {{Z|Z12}} to cater for language variants. Either way, I think that would be the approach to adopt for inflected forms, unless reference to specific lexeme-forms is required. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:52, 28 April 2026 (UTC) ::This. If a native of your language were to count up, which form would they be most likely to use? [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:29, 28 April 2026 (UTC) ::: {{re|GrounderUK|Feeglgeef}} Thanks for both your input! ::: I relabeled the aforementioned function to {{Z|Z34308}}, and created a new wrapper function {{Z|Z34457}}. ::: Should I specify that my old function is a monolingual text in parentheses? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 16:26, 28 April 2026 (UTC) ::::You don't have to, unless you think that is something that would require distinction when viewing the function in a list of search results &c. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:36, 28 April 2026 (UTC) == Optional/nullable function parameters == Hello! Recently, I was informed that Wikifunctions has no optional/nullable function parameters as of now. Are there any future plans to support this, and/or workarounds? Maybe create a union type system like "{{Z|6}} or {{Z|23}}". <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 17:53, 28 April 2026 (UTC) :What I do for this is use an "is empty" function corresponding to the type of the parameter in an If statement. If it isn't empty, the function works as intended. Otherwise, it does something else. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 17:58, 28 April 2026 (UTC) :Unions are not a thing (yet) on Wikifunctions, but you can always define an argument of type {{Z|Z1}}, which means that all types are allowed (I already did this for {{Z|Z26737}}; note that it is still a ugly workaround, don't use it for high level functions). Also, note that usually on Wikifunctions we use {{Z|Z24}} as the null value. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:00, 28 April 2026 (UTC) :: {{re|JJPMaster|Dv103}} Thanks for your help! :: @[[User:Dv103|Dv103]] told me a function call with a missing parameter is treated as an invalid function call, so how does the "is empty" function work with that? :: Also, setting the type to {{Z|1}} seems naive, like setting the type as <code>any</code> in TypeScript... :: Related question: Are there plans to add default values to parameters (outside of "if empty")? <span style="border-radius:99q;padding:0 7q;background:#103;border:3q solid #FBF">[[User:QuickQuokka|<span style="color:#FBF">'''QuickQuokka'''</span>]]</span> ^{[⁠[[User talk:QuickQuokka|talk]] • [[Special:Contribs/QuickQuokka|contribs]]]} 18:19, 28 April 2026 (UTC) :::Setting the type to {{Z|Z1}} is actually naive, and that's why I advised you to only use it for low-level functions. Currently there is nothing better. Sometimes, type correctness is not actually checked, so it might seem that nullable types are possible. But it is still an hack, and it could broke anytime since it is not intended behavior. :::I don't think that there are current plans to add default values (but correct me if I'm wrong). The closest thing that comes to my mind is that, if you incorporate Wikifunctions into Wikitext, you can leave empty some fields (only of some specific types) and Parsoid will replace them to their default value. This is done only depending on the type, and not on the functions. For example, {{Z|Z6091}} and {{Z|Z6001}} are assigned the QID associated to the page, and {{Z|Z20420}} is assigned the current date. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 18:56, 28 April 2026 (UTC) :::@[[User:QuickQuokka|QuickQuokka]]: At the very least, [[Z10008]] accepts a null input. Maybe that feature is unique to the String type—I am not sure. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 19:10, 28 April 2026 (UTC) ::::I think it's just not checked, but it shouldn't be intended. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:20, 28 April 2026 (UTC) ::::Strings and typed lists can be “empty” in the sense that their length can be zero. Typed pairs may also be “empty” in a degenerate sense, but such an object will not be returned from a code implementation. A typed map with no entries will also fail to be returned from code, although it is fine in compositions. ::::For a genuinely optional parameter, I prefer a properly typed list, which at least encourages an argument of the correct type. {{Z|Z813}} is also typically faster than {{Z|Z10008}}. Quite a good example of this approach is {{Z|Z23723}}, where it helps to resolve the type union (using [[Z1]]) for both Z6003K1 and Z6003K3. Of course, there’s nothing to prevent more than one element in the list, but additional elements are easily ignored. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:55, 28 April 2026 (UTC) :Pinging {{ping|Jdforrester (WMF)|prefix=|p=}}, I believe there are no current plans. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 19:02, 28 April 2026 (UTC) ::@[[User:QuickQuokka|QuickQuokka]]: I'm afraid there are no current plans to build out optional params, indeed; we would be happy to review this if a compelling case was made, but it'd be a lot of work to re-build the [[Wikifunctions:Function model|function model]] with that support and ensure we don't break (too many) things. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:11, 28 April 2026 (UTC) == Z6830 for Chinese == I was trying to use {{Z|Z6830}} for implementation in the Chinese-language. And turns out most of the Lexeme on Wikidata is using [[d:Q727694]] as the language instead of [[d:Q7850]]. This makes it impossible to use the mentioned function above, since Standard Chinese is not available (or did I miss something?). Is there a way to fetch lexemes with language=[[d:Q727694]] from item? [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 18:20, 30 April 2026 (UTC) :@[[User:Sun8908|Sun8908]] There is [[Z1006]] for Chinese and it has the language code zh. There is an overview of languages in [[Module:Wikifunctions label]] so you can search there for chinese versions and choose the one you need. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 20:53, 5 May 2026 (UTC) ::I know that. The problem is when using the function [[Z6830]], it cannot retrieve lexeme with language [[d:Q727694]] (but it is the "Chinese language" with the most current Wikidata lexemes, see [https://ordia.toolforge.org/language/ ordia]). I think it should be a Wikidata problem, I might fix it (possibly by creating the same lexemes with language code zh) on Wikidata. Thanks anyway. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 05:39, 6 May 2026 (UTC) :Could you provide an example of a Chinese lexeme that has a linked Wikidata item, or a Z6830 function call that fails to find such a lexeme where one exists? [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 07:55, 6 May 2026 (UTC) ::Here: [[d:Lexeme:L846083]]. I think that's a primary reason of me trying to look into this problem, as the label in zh for [[d:Q6256]] (country) is not a single phrase (see its talk page on WD for more information). This makes some Abstract Wikipedia articles very weird in Chinese when {{Z|Z26570}} is used, so lexeme could potentially fix that. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 10:33, 6 May 2026 (UTC) :::Thank you. It looks as though {{Z|Z6830}} [https://www.wikifunctions.org/view/en/Z6830?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z6830%22%2C%22Z6830K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q6256%22%7D%2C%22Z6830K2%22%3A%7B%22Z1K1%22%3A%22Z6092%22%2C%22Z6092K1%22%3A%22P5137%22%7D%2C%22Z6830K3%22%3A%7B%22Z1K1%22%3A%22Z60%22%2C%22Z60K1%22%3A%22cmn%22%2C%22Z60K2%22%3A%5B%22Z6%22%5D%7D%7D returns that lexeme for language tag "cmn"]. Perhaps that tag should be added into the helpers for {{Z|Z24144}}? If it is widely used for lexemes, perhaps it should have its own {{Z|Z60}}? In any event, improvements might be considered under [[:phab:T390563]] (or otherwise), including amending [[Z6830]] to also consider "cmn" (and "zho", "chi"…?) when requests are made for "zh-hans" or "zho-hant" (or others?) @[[User:Winston Sung|Winston Sung]] @[[User:DMartin (WMF)|DMartin (WMF)]] [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 17:22, 6 May 2026 (UTC) ::::If you go to [[d:Special:NewLexeme]] and put in [[d:Q727694]] as the language, it is going to tell you it has an unrecognized language code. So I believe "cmn" should not be a {{Z|Z60}} by default? I also started [[d:Wikidata:Project_chat#Lexemes_with_language_Standard_Chinese_(Q727694)|a discussion on WD]] regarding this. I guess we can still use it as a fallback language though if possible. [[User:Sun8908|Sun8908]] ([[User talk:Sun8908|talk]]) 03:43, 7 May 2026 (UTC) ::::We don't have a separated <code>cmn</code> BCP 47 language subtag in MediaWiki and Wikidata at the moment. <code>zho</code> and <code>chi</code> are ISO 639 language codes but not BCP 47 language subtags. ::::For Modern Standard Mandarin, please use <code>zh-*</code> language tags for now. -- [[User:Winston Sung|Winston Sung]] ([[User talk:Winston Sung|talk]]) 15:26, 8 May 2026 (UTC) == Key not found error == Is there a reason why I am getting key not found error for this [[Z34677|function]] {{Z|Z34677}}? All the underlying functions run and all the test cases work. The debug information does not give more details. Any pointers? Thanks in advance [[User:Jsamwrites|John Samuel]] 19:24, 1 May 2026 (UTC) :It was passing the [[Z6091]] to {{Z|34641}} when that takes a [[Z6001]]. I've fixed that, but there's some other problem with the logic, so I've left it disconnected. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 19:42, 1 May 2026 (UTC) ::@[[User:YoshiRulz|YoshiRulz]] Thanks a lot. [[User:Jsamwrites|John Samuel]] 20:21, 1 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #246 is out: Request for input: what should we count for Abstract Wikipedia == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-02|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we ask you what would be the relevant metrics for Abstract Wikipedia, we discuss our latest news on Composition Language v2, 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:21, 2 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=30325620 --> == Any formal process for deletion of pages == Does a formal process exist for the deletion of functions, implementations, and tests that includes a notification system for creators, analogous to Wikidata’s process, explaining the rationale behind the deletion (or proposal for deletion)? [[User:Jsamwrites|John Samuel]] 12:36, 3 May 2026 (UTC) :Does [[Wikifunctions:Requests for deletions]] work? [[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:00, 3 May 2026 (UTC) :Please see the discussion at [[Wikifunctions talk:Requests for deletions#Should we expect Objects' creators to get pinged on deletion proposals?]]. :As I see it, it is the proposer’s responsibility to consult appropriately before making a request and we expect our administrators to act only when satisfied that appropriate consultation has occurred. In many cases, no consultation is required. Administrators may delete their own contributions without making a request, but this is not a practice I would encourage. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:51, 3 May 2026 (UTC) == Implementation of rational number in JS doesn't match in Z19677 (Rational number) and Z28579 (RGBA colour) == In {{Z|19677}} it's <syntaxhighlight lang=js> { "K1": sign * numerator, "K2": denominator } </syntaxhighlight> but in {{Z|28579}} it's <syntaxhighlight lang=js> [ sign * numerator, denominator ] </syntaxhighlight> '''<span style="font-family:Iosevka,monospace">[[User:沈澄心|<span style="color:#9f3526">dring</span>]][[User talk:沈澄心|<span style="color:#534fa3">sim</span>]]</span>''' 05:15, 4 May 2026 (UTC) == Nested functions in compositions == I wish it will be easier to a add another function about a specific existing function in a function implementation based on a composition. When I write long functions in spreadsheets I usually stat with a small part and then I try to go further and after important steps I test if the output is as expected. I created [[Z34826]] to get the German gender specific occupation lexeme for a specific person based on their gender. I wanted to add a function around the existing one and it was not successful. It is not very easy to implement as it requires the possibily to move a part to another section but I think it can be helpful if it will be implemented. So far I spend more time as expected on the function. Describing it with words what the function needs to do is much easier than implementing it here in Wikifunctions. So I think there needs to be improvement to make Wikifunctions more accessible. [[User:Hogü-456|Hogü-456]] ([[User talk:Hogü-456|talk]]) 21:10, 5 May 2026 (UTC) :Have you tried to use the copy-paste functionality? It is very useful to move parts of composition arounn. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 07:12, 6 May 2026 (UTC) :I've also found the composition editor to be wholly unsuitable for any expressions more than a few levels deep. (Even with the <code>localStorage</code> clipboard, because of its overzealous type checks.) Compositions naturally grow out from the "leaves", the immediate operations on the inputs, while the interface really wants you to build from the "root". I mostly use the [https://yoshirulz.gitlab.io/WikiLambdaBlockly drag-and-drop block editor] which I made to smooth over some of the site's problems, so if you want to try that out and give me some feedback I'd appreciate it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 14:36, 6 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #247 is out: References from Wikidata now available == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-08|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we announce that is now possible to pass references in Wikidata statements, we introduce the [https://abstract-data.toolforge.org/ Abstract Data dashboard], we report you on the 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 [[: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/1778520600 May 11, 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]]) 11:16, 8 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=30325620 --> == RGBA colour, spelling... == Something that has always irked me a little bit is the spelling of [[Z28579|RGBA colour (Z28579)]]. I guess this is not unsurprising for me considering my use of US English but I think there is more to it than preference and I want to try to argue for it being changed to use American spelling. I know that this probably has a snowball's chance in hell of actually garnering any support, so I won't really be miffed if the spelling remains as it is, but I thought it wouldn't hurt to raise this regardless. The main issue I have with it is the spelling of the original proposal. When infernostars raised the [[Wikifunctions:Type proposals/RGBA color|type proposal]], the spelling was 「RGBA color」. Of the comments that mentioned the word 「colo[u]r」, two used British spelling while six used the American spelling as used in the proposal. The only thing that really pointed to the use of ''colour'' was the fact that the catalog page on color functions used that spelling already. For all intents and purposes, the spelling of the original proposal should have been maintained, but it was not; [[User:DVrandecic (WMF)|DVrandecic]], the eventual creator of the type, used a different spelling. It should be noted that there was really no reason for this to occur and while it is an undoubtedly minor issue I still believe it should be rolled back and the type should use the spelling of the original proposal and majority of editor comments. In [[abstract:Q936|OpenStreetMap]], there have been keyvalue proposals that have had the finalized spelling that gets put to use be in British English despite the original proposal being in American English; this has usually occurred with proposals relating to 「X center/centre」 tags. This makes sense on the surface, because OpenStreetMap is maintained by a UK organization, and still has close ties to Europe. The Wikimedia Foundation, however, is an ''American'' company. This is often brought up as a fallible argument when debating article spelling on the English Wikipedia, and I don't bring it up to support that 「RGBA color」 should be used for that exact reason, but rather to state that OpenStreetMap's general policy on tag names need not apply here. It appears to me that, at least initially, the majority of 「core contributors」 to Wikifunctions used British English; I can name YoshiRulz, 99of9, GrounderUK, and VIGNERON.<ref group="color">I'm avoiding linking to these folks because I don't think pinging them about this discussion is all too necessary unless they themselves want to be involved; I don't want to clutter their inboxes just to briefly mention them. I pinged Denny because, well, I'm asking him a question directly, but everyone else I would prefer to join this discussion by their own accord... not that I wish for this decision to be confused as me going 「these people use British English so they will probably oppose my idea, I won't invite them to the discussion because of that」...no, I promise you that is not the reason.</ref> I see (or saw) these people ''everywhere'', so it makes sense that British English has prevailed in some sorts on this website, but I don't think that indicates that it should be the ''preferred'' spelling across the website, at least not to the point where a proposal should have its name changed to match such a "consensus".<ref group="color">It could be argued that the front-and-center ''Function catalogue'' using 「catalogue」 is actually indicative of such a "consensus", but ''catalogue'' is in a similar position to the word ''grey'' where I live (that is, the US) in that it is used just as often as its American counterpart. Also, consider Wiktionary's ''Beer parlour'' project chat.</ref> The unnecessary modification of the original spelling is my main argument for changing it back... but of course, I must obligatorily state that on English Wikipedia, it is [[w:Color|Color]] and [[w:RGBA color model|RGBA color model]]; on Wikidata, it is [[d:Q1075|color]] and [[d:Q2325624|RGBA color space]]; in CSS (which typically uses hexadecimal triplets to specify RGBA values), the properties are <code>color</code>, <code>background-color</code>, etc.; bit of a weak jab, but on Schema.org it is [https://schema.org/color color], [https://schema.org/colorSwatch colorSwatch]; et cetera. {{Z|Z28580}} uses ''color'', so does {{Z|Z28591}} and its Python counterpart. Mr. Vrandečić, I have to ask, I'm rather confused... you created the color type using British English spelling, but you were also responsible for the creation of the equality function which uses the American English spelling. You also seem to be writing in American English for the status updates, judging by your use of -''ize'' over -''ise'' endings and use of ''program'' over ''programme'' in [[Wikifunctions:Status updates/2026-04-16]]. Is there something I'm missing or have you switched your preferred variant somewhere along the way? Anyways, do consider this if you wish... again, I don't suppose this will garner much support, it is the ''non-issuest'' of ''non-issues'', but it has irked me to the point where I want to ask about it to get some answers, if nothing else. I am not arguing for every other color function to have its name changed, just the type itself. <references group="color"></references> &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:04, 8 May 2026 (UTC) :This is a multilingual project; the <code>en</code> label is <code>RGBA colour</code> and the <code>en-us</code> label is <code>RGBA color</code>. Though I'm not able to switch to <code>en-us</code> via the language picker so that would need to be fixed.<!-- --><br>edit after reading your whole comment: The same is true of {{Q|1075}}, there are labels specified for multiple English variants. (In {{Q|2325624}} it's only an alias.) I agree that other websites' choices aren't binding on us, but from that, I conclude that the more widespread British/Commonwealth spellings should be used for the generic <code>en</code>. As for myself, I'm Aussie and I will continue to use the BrE spellings ([[w:en:Oxford_spelling#Language_tag_comparison|+ "routing"]], TIL) if only by muscle memory.<!-- --><br>[[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 17:42, 8 May 2026 (UTC) :: Your lattermost point would normally be fine in a perfect world. Wikipedia's <code>convert</code> function defaults to "international" English, which I don't personally take issue with because it happens that we here in America are actually outliers for saying and spelling things differently... err, or we were for a while at least, nowadays it seems like an even split (plus you have "yield" vs. "give way" which is effectively the logical opposite of US's use of "meter" over "metre"). :: However, this is not a perfect world, and I don't think <code>en</code> should correspond to any particular variant. It is too fragmented across all software at this point to impose such a requirement. The inability to switch to <code>en-us</code> on this website foregoes an easy and simple solution to this problem that makes everyone happy, because the yanks (such as myself) can't be happy because we can't see the labels in American English even if we wanted to, and the other folk can't switch either as far as I'm aware (and the en-CA and en-GB languages in the preferences page seems to be deprecated). My point being, <code>en</code> is abused to mean "en-UK" just as often as it is abused to mean <code>en-US</code>; I think a decision shouldn't be made on such an assumption of one "default". &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:48, 12 May 2026 (UTC) :Hi @[[User:Theki|rae]]! I have no opinion nor preference on this, and given my background, I am just entirely confused about my spelling preferences myself, as you can tell from my inconsistent usage. I learned British English in school and used that for maybe two decades or so, but moved to the US and lived there for more than a decade, enough to be naturalized, but now I am back in Europe and I am technically a professor at King's College London, soooo.... honestly, I do not know. I don't remember having put too much thought into it at the moment I created it. The good thing is that in Wikifunctions, just as in Wikidata, it is easy to change, without messing things up too much (unlike in Wikipedia), so my suggestion is, just make the change, see if anyone complains, and if they do, discuss it more. I don't know if there is a guideline already in Wikifunctions about the variants. I am happy either way, and honestly, I keep forgetting which variant is which most of the time. --[[User:DVrandecic (WMF)|DVrandecic (WMF)]] ([[User talk:DVrandecic (WMF)|talk]]) 18:16, 10 May 2026 (UTC) :: I can definitely understand this, although I am unfortunately rather passionate about any minutiae involving preferential minor differences in ''anything'', of which AmE vs. BrE chiefly is. So I dedicate a lot of headspace to it. More than I should. Not that I wish to imply that the comment above that I have wrote is of an irrational nature, or done out of spite or pure emotion and subjectivity; I do genuinely believe that ''RGBA color'' is beyond just a personal preference and is just logical. I may boldly go and change it, but for some reason I was expecting that changing the English label of a Type would require elevated permissions, and I also didn't want to do it only to get immediately reverted because it ''did'' strike a chord with someone, when I could instead see how apathetic, supportive, or in opposition interested people are beforehand and ''then'' act accordingly. I was not meaning to antagonize you over your spelling habits, I did actually use British English for a few years starting in 2020 before I went back to American English, so I'd be a hypocrite for me to decry you for not always sticking to some arbitrary standard of spelling words over the other. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:55, 12 May 2026 (UTC) :Although I spell it “colour”, I think it makes more sense to use “color” for the type, since that is almost always the required spelling when the string functions as a keyword. :More generally, though, Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en". This is unusual, in my experience, as "en" is widely misused in place of "en-US", where there are recorded spelling differences. :(I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere. Use of -ize rather than -ise is a matter of personal preference or house style, but regional autocorrect encourages -ise.) [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:00, 12 May 2026 (UTC) :: ''Wikidata’s lexicographic data happens to favour “colour” over “color” and (quite rightly, in my view) lacks a specific representation for "en"'' :: Definitely agreeing with you on the latter being a good choice. However, I suspect the favoring of "colour" over "color" may be because, in terms of language codes, when sorted alphabetically <code>en-us</code> actually comes ''after'' <code>en-gb</code>. Although, the frontend seems to be sorting <code>en-ca</code> after <code>en-gb</code>, so I don't actually know how correct that is. :: ''I would also say it is standard British English to use “program” in a programming context and “programme” elsewhere'' :: The context of the spelling was "''No program for the NLG SIG meeting for next Tuesday has been proposed''". In that usage context, I think it makes sense to assume that ''program'' is not being used to refer to a computer program, but to a ''program of events'' or similar, something that you would spell as a ''programme'' in British English. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:02, 12 May 2026 (UTC) :{{s}} this. I'm obviously biased but I believe American English is preferable generally, American dominance on the internet (our Department of Defen'''s'''e invented it!) and rapidly-increasing consumption of American media by international English speakers means that more people use American English's conventions, this is clear through for example [http://trends.google.com/explore?q=color%2Ccolour&date=all&geo=Worldwide search trends] (though they aren't particularly reliable). Perhaps this is a bit of a supremacist opinion, but we should have internal consistency, and if we must choose, American English should be our first choice (then Indian and then British English) [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:10, 12 May 2026 (UTC) :: This is rather flawed reasoning, though. I think probably any given British or Indian person would not agree on using that as the reasoning for this, not that you are necessarily ''completely wrong'', but if this is not a good enough reason for English Wikipedia's (admittedly extremely flawed) ''ENGVAR'' policy then I don't think it's likely it will pass here either. :: Although of note is that [https://books.google.com/ngrams/graph?content=color%2Ccolour&year_start=1800&year_end=2022&corpus=en&smoothing=3&case_insensitive=true Google ngrams] agree with you, but "color" vs. "colour" is an eternal holy war that will not be won by demonstrating that more books use US spelling over Commonwealth spelling. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:44, 12 May 2026 (UTC) :::You're probably right that it's not very sound. I'm biased in that other varieties of English irk me, and that's probably mutual for people who are used to other varieties of English when they read what I write! [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 14:56, 12 May 2026 (UTC) :I've decided to boldly [[Special:Permalink/274271|make the change]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:02, 12 May 2026 (UTC) :: Thank you. Considering both you and GrounderUK seem to consider it an okay change, I think this will do for now. :: I should note that the matter of whether to move [[Wikifunctions:Catalogue/Colour functions]] in response to this (however this discussion will ultimately turn out) is a whole other can of worms, in my view. I can't say I have an opinion on that at the moment, but I'm putting it out there regardless. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 15:06, 12 May 2026 (UTC) :::Personally, I'm in favor of moving the page and renaming all of the items on it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:10, 12 May 2026 (UTC) ::I don't like this (exactly because of the American hegemony you cited), but again, it shouldn't matter because the software is meant to be multilingual. Clearly there's a bug preventing you from picking an English variant/dialect as your display language. But the search bar and Function/Type autocompletion do check the English variants for matches. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 15:15, 12 May 2026 (UTC) == Proposals on the architecture of Abstract Content rendering == Starting from a discussion born on the Telegram chat, I've explained two different proposals on how the NLG on Abstract Wikipedia should be organized in the page [[abstract:User:Dv103/Abstract articles architectures]]. Please come to contribute to the discussion, or to propose alternatives. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 14:31, 11 May 2026 (UTC) :Thank you for dedicating your time to writing this, it is very informative. I will try to add input once I'm not in over my head with finals. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 16:27, 12 May 2026 (UTC) == Display function for HTML fragment == Currently, any collapsed Z89 literal appears as<blockquote>&lt;&gt; [[Z89|HTML fragment]]</blockquote>If I were to create a new Function which returned something like<blockquote>&lt;&gt; 123-byte HTML fragment <q><nowiki><td><span lang=</nowiki>&hellip;</q></blockquote>could that be connected to replace the collapsed form, or would it require changes to the Wikilambda software? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 16:14, 11 May 2026 (UTC) :It might work, but I doubt it. Those angled brackets suggest that the collapsed form is not simply defaulting to the type’s label. Looking at [[:phab:T410509]], I’ve concluded that enhancements to the collapsed form were never considered, rather than being actively rejected. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:12, 12 May 2026 (UTC) ::[[:Phab:T391985]] documents the original design. Note the fifth bullet point under “Acceptance criteria”. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:21, 12 May 2026 (UTC) :I'm not sure the byte-size is necessary, but the outer tag (or first outer tag, though generally I'd prefer most fragments use a wrapper tag if it needs multiple like JSX does, but that's a whole different topic) would be nice. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:51, 12 May 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #248 is out: A higher meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-05-15|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we discuss functions creating language fragments, we present our latest news in 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]]) 14:36, 15 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 --> == [[Z34510]] == This function, which determines if a Wikidata item for a {{q|5}} has an undeprecated {{p|21}} statement of {{q|6581097}}, returns false for {{q|173399}}, a transgender man. This is because his item assigns his P21 statement to {{q|2449503}}, not {{q|6581097}}. I'm not sure how to account for this discrepancy. Should {{z|34510}}: # Include {{q|2449503}} as a value that can lead to a true result, # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a man?") could return true for either "male" or "trans man", # Not include {{q|2449503}} as a value that can lead to a true result, while another function (e.g., "Q5 is a trans man?") could return true for "trans man", # Not exist at all? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 16:48, 16 May 2026 (UTC) :I can't think of a single use case where you would need to determine if a person is a cisgender man and nothing else. Functions are good for generalizing across multiple possibilities when they exist, so I think it would be best if trans men were considered a part of the criteria for returning a true value. If asking for specifically {{q|6581097}}s and ''nothing'' else was desired then the function name would be a misnomer as Elliot Page is inarguably a male (at least in the view of most reasonable and intelligent people). &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 19:03, 16 May 2026 (UTC) :You made the function in the first place; what were you planning on using it for? AW? Maybe it should return a {{Z|25501}} which can then be passed on to other NLG functions. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 May 2026 (UTC) == Lexeme from wikidata label, or "best" lexeme from wikidata item == I was looking into fixing [[Z28028]]. I found that I could add "requires grammatical feature: definite article" to "United Kingdom" (L8558). Now I'm stuck on how to get to that lexeme from {{Q|145}}. There's [[Z23471]], but that for very good reason gives you multiple lexemes with the same sense, and I just want the best one like how the label is always the best string. Is there a function that can do this? There's definitely the case of a Wikidata label that isn't a lexeme (most commonly multiple lexemes) but I'm only considering the case where it is one lexeme here. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 20:02, 16 May 2026 (UTC) :There is {{Z|Z27327}}, that tries to give the best lexeme through various heuristics. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 22:22, 16 May 2026 (UTC) :: Wonderful! I did stumble upon [[Z33818]] but this is perfect. [[User:Aaron Liu|Aaron Liu]] ([[User talk:Aaron Liu|talk]]) 00:25, 17 May 2026 (UTC) == [[Z29591]] isn't working for me == For instance, trying to manually put in the exact inputs for one of the test cases just returns an empty Monolingual text. See [https://www.wikifunctions.org/wiki/Z29591?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z29591%22%2C%22Z29591K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q3257809%22%7D%2C%22Z29591K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q21264361%22%7D%2C%22Z29591K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q22006653%22%7D%2C%22Z29591K4%22%3A%22Z1002%22%7D]. [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 01:17, 17 May 2026 (UTC) :You used [[:d:Q22006653]] rather than [[:d:Q1075]]. It looks like the [https://www.wikifunctions.org/wiki/Special:RunFunction?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z30784%22%2C%22Z30784K1%22%3A%7B%22Z1K1%22%3A%22Z11%22%2C%22Z11K1%22%3A%22Z1002%22%2C%22Z11K2%22%3A%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z21394%22%2C%22Z21394K1%22%3A%5B%22Z6%22%2C%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z22664%22%2C%22Z22664K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q22006653%22%7D%2C%22Z22664K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q21264361%22%7D%2C%22Z22664K3%22%3A%22Z1002%22%7D%5D%7D%7D%7D explanatory error] is suppressed by the [https://www.wikifunctions.org/view/en/Z30009?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z30009%22%2C%22Z30009K1%22%3A%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z30784%22%2C%22Z30784K1%22%3A%7B%22Z1K1%22%3A%22Z11%22%2C%22Z11K1%22%3A%22Z1002%22%2C%22Z11K2%22%3A%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z21394%22%2C%22Z21394K1%22%3A%5B%22Z6%22%2C%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z22664%22%2C%22Z22664K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q22006653%22%7D%2C%22Z22664K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q21264361%22%7D%2C%22Z22664K3%22%3A%22Z1002%22%7D%5D%7D%7D%7D%2C%22Z30009K2%22%3A%22Z801%22%7D final transformation]. The returned result is not actually empty; if you expand it, you can see that it is an unresolved function call. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 09:59, 17 May 2026 (UTC) rmk3m0cg7v1yw64yqux8o2a2hei9b74 4 1696 275509 274371 2026-05-16T12:14:56Z Ameisenigel 44 /* Z31462 */ new section 275509 wikitext text/x-wiki <noinclude>__NEWSECTIONLINK__ __FORCETOC__</noinclude> Functions or implementations or tests which do not work properly, do not meet notability criteria or are duplicates of another object can be deleted. Please nominate items for deletions under the "Requests for deletion" section below. If it is obvious vandalism, just report it in [[Wikifunctions:Report vandalism]], or ping an [[Special:ListAdmins|administrator]]. Contact can also be made with an administrator on [https://t.me/Wikifunctions Telegram] or IRC [irc://irc.libera.chat/wikipedia-abstract #wikipedia-abstract]. If it is a predefined object (its ZID is less than 10000), please see [[Wikifunctions:Report a technical problem]]. {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |level = 2 }} {{Archives|{{Special:PrefixIndex/Wikifunctions:Requests for deletions/Archive/|stripprefix=1}}}} = Requests for deletion = == [[Z18720]] == This kind of function is not supported, at least not in the way as it is currently implemented. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 20:24, 27 April 2026 (UTC) :CC @[[User:Ioaxxere|Ioaxxere]] <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> 12:27, 28 April 2026 (UTC) :Why isn't it supported? This function would be useful on Wiktionary itself if we could call it from a template. [[User:Ioaxxere|Ioaxxere]] ([[User talk:Ioaxxere|talk]]) 13:47, 28 April 2026 (UTC) ::Web requests are not technically supported, and the Abstract Wikipedia team has no plans to support it. Functions should be deterministic, which means that they cannot rely on web requests. The proper way to do this would be to use the templates feature, you can do something like <nowiki>{{:hello}}</nowiki> to bring the full page hello a function call. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:53, 28 April 2026 (UTC) == [[Z18771]] == Duplicate of [[Z10251]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 12:51, 3 May 2026 (UTC) :{{s}} deletion, unless {{ping|Jsamwrites}} has a comment to make. This is a relatively old one, but WhatLinksHere shows that nothing uses it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:44, 3 May 2026 (UTC) :Thanks for pointing this out. However, there are implementations and test cases that cover more interesting use cases. Also added a composition function making use of {{Z|Z10251}} [[User:Jsamwrites|John Samuel]] 17:01, 3 May 2026 (UTC) ::It is possible to move these from the duplicate to the original function. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 17:49, 7 May 2026 (UTC) == [[Z31462]] == Seems useless. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 12:14, 16 May 2026 (UTC) au2xjmqesmf5lkhnen04cexmsc8pv5r 275698 275509 2026-05-17T07:33:14Z Bunnypranav 9976 /* Z31462 */ Reply 275698 wikitext text/x-wiki <noinclude>__NEWSECTIONLINK__ __FORCETOC__</noinclude> Functions or implementations or tests which do not work properly, do not meet notability criteria or are duplicates of another object can be deleted. Please nominate items for deletions under the "Requests for deletion" section below. If it is obvious vandalism, just report it in [[Wikifunctions:Report vandalism]], or ping an [[Special:ListAdmins|administrator]]. Contact can also be made with an administrator on [https://t.me/Wikifunctions Telegram] or IRC [irc://irc.libera.chat/wikipedia-abstract #wikipedia-abstract]. If it is a predefined object (its ZID is less than 10000), please see [[Wikifunctions:Report a technical problem]]. {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |level = 2 }} {{Archives|{{Special:PrefixIndex/Wikifunctions:Requests for deletions/Archive/|stripprefix=1}}}} = Requests for deletion = == [[Z18720]] == This kind of function is not supported, at least not in the way as it is currently implemented. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 20:24, 27 April 2026 (UTC) :CC @[[User:Ioaxxere|Ioaxxere]] <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> 12:27, 28 April 2026 (UTC) :Why isn't it supported? This function would be useful on Wiktionary itself if we could call it from a template. [[User:Ioaxxere|Ioaxxere]] ([[User talk:Ioaxxere|talk]]) 13:47, 28 April 2026 (UTC) ::Web requests are not technically supported, and the Abstract Wikipedia team has no plans to support it. Functions should be deterministic, which means that they cannot rely on web requests. The proper way to do this would be to use the templates feature, you can do something like <nowiki>{{:hello}}</nowiki> to bring the full page hello a function call. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:53, 28 April 2026 (UTC) == [[Z18771]] == Duplicate of [[Z10251]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 12:51, 3 May 2026 (UTC) :{{s}} deletion, unless {{ping|Jsamwrites}} has a comment to make. This is a relatively old one, but WhatLinksHere shows that nothing uses it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:44, 3 May 2026 (UTC) :Thanks for pointing this out. However, there are implementations and test cases that cover more interesting use cases. Also added a composition function making use of {{Z|Z10251}} [[User:Jsamwrites|John Samuel]] 17:01, 3 May 2026 (UTC) ::It is possible to move these from the duplicate to the original function. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 17:49, 7 May 2026 (UTC) == [[Z31462]] == Seems useless. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 12:14, 16 May 2026 (UTC) :CC @[[User:Feeglgeef|Feeglgeef]] <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:33, 17 May 2026 (UTC) 6iib6mzf7tftr29rzmlhu2jwj116jfs 275724 275698 2026-05-17T09:05:12Z Ameisenigel 44 /* Z18771 */ Reply 275724 wikitext text/x-wiki <noinclude>__NEWSECTIONLINK__ __FORCETOC__</noinclude> Functions or implementations or tests which do not work properly, do not meet notability criteria or are duplicates of another object can be deleted. Please nominate items for deletions under the "Requests for deletion" section below. If it is obvious vandalism, just report it in [[Wikifunctions:Report vandalism]], or ping an [[Special:ListAdmins|administrator]]. Contact can also be made with an administrator on [https://t.me/Wikifunctions Telegram] or IRC [irc://irc.libera.chat/wikipedia-abstract #wikipedia-abstract]. If it is a predefined object (its ZID is less than 10000), please see [[Wikifunctions:Report a technical problem]]. {{Autoarchive resolved section |age = 1 |archive = ((FULLPAGENAME))/Archive/((year))/((month:##)) |level = 2 }} {{Archives|{{Special:PrefixIndex/Wikifunctions:Requests for deletions/Archive/|stripprefix=1}}}} = Requests for deletion = == [[Z18720]] == This kind of function is not supported, at least not in the way as it is currently implemented. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 20:24, 27 April 2026 (UTC) :CC @[[User:Ioaxxere|Ioaxxere]] <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> 12:27, 28 April 2026 (UTC) :Why isn't it supported? This function would be useful on Wiktionary itself if we could call it from a template. [[User:Ioaxxere|Ioaxxere]] ([[User talk:Ioaxxere|talk]]) 13:47, 28 April 2026 (UTC) ::Web requests are not technically supported, and the Abstract Wikipedia team has no plans to support it. Functions should be deterministic, which means that they cannot rely on web requests. The proper way to do this would be to use the templates feature, you can do something like <nowiki>{{:hello}}</nowiki> to bring the full page hello a function call. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 13:53, 28 April 2026 (UTC) == [[Z18771]] == Duplicate of [[Z10251]]. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 12:51, 3 May 2026 (UTC) :{{s}} deletion, unless {{ping|Jsamwrites}} has a comment to make. This is a relatively old one, but WhatLinksHere shows that nothing uses it. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 15:44, 3 May 2026 (UTC) :Thanks for pointing this out. However, there are implementations and test cases that cover more interesting use cases. Also added a composition function making use of {{Z|Z10251}} [[User:Jsamwrites|John Samuel]] 17:01, 3 May 2026 (UTC) ::It is possible to move these from the duplicate to the original function. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 17:49, 7 May 2026 (UTC) :::I have moved all the tests and implementations (except the one that is just using the older function) to Z10251. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 09:05, 17 May 2026 (UTC) == [[Z31462]] == Seems useless. --[[User:Ameisenigel|Ameisenigel]] ([[User talk:Ameisenigel|talk]]) 12:14, 16 May 2026 (UTC) :CC @[[User:Feeglgeef|Feeglgeef]] <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:33, 17 May 2026 (UTC) qilpuyhf34d7zi1emlz7hkkjyy8199z 1198 4301 275510 15249 2026-05-16T12:21:29Z Tensama0415 73696 Marked translation unit as no longer outdated with no changes 15248 wikitext text/x-wiki [[$fm|함수 모델]] 참조. igvwal3kp45a4dp78067xopx5rwrehr 1198 4318 275512 15309 2026-05-16T12:21:43Z Tensama0415 73696 275512 wikitext text/x-wiki "순수 함수형"의 줄임말로, 그러한 함수의 [[$evaluation|평가]]는 부작용이 없고 결정론적입니다. 즉, 항상 동일합니다; 위키백과의 [[w:en:Purely functional programming|순수 함수형 프로그래밍]] 참조; [[$fm|함수 모델]] 참조. mwlw2o6m530y05eaj0lj37x5mlhgr8n 1198 4599 275518 16125 2026-05-16T12:24:47Z Tensama0415 73696 275518 wikitext text/x-wiki 이 용어는 위키데이터와는 완전히 다른 의미를 가지고 있습니다. 위키백과의 [[w:en:Reference (computer science)|참조 (컴퓨터 과학)]] 참조. g9v5hzknweqkt69vnnj3i67gtjtp4np 1198 5054 275516 17461 2026-05-16T12:23:26Z Tensama0415 73696 275516 wikitext text/x-wiki 널리 사용되는 데이터 전송 형식; 위키백과의 [[w:en:JSON|JSON]]을 참조. ryesyzsz8ud0ch90vpcii9ojwo2b4sg 1198 5568 275514 18926 2026-05-16T12:22:12Z Tensama0415 73696 275514 wikitext text/x-wiki [[$function|함수]]를 실행하는 특별한 방법. 구현은 특정 프로그래밍 언어로 된 코드 조각일 수도 있고 [[$evaluator|평가자]]에 "내장 된" 기능을 참조하거나 다른 함수에 대한 호출을 결합할 수도 있습니다. 함수에는 많은 [[$composition|구현]]이 있을 수 있으며 모두 동일해야 합니다. "[[$ZFunction|Z함수]] 구현"의 약자입니다. fjk70a1vtdwb5i25tpty69luai7sr8t 4 5798 275511 257648 2026-05-16T12:21:29Z Tensama0415 73696 275511 wikitext text/x-wiki <noinclude><languages/> <!--<nowiki>(nowiki tags are so that the translate extension doesn't try to translate the TERM and DEFINITION in this boilerplate). Use this boilerplate for a new term: ; {{anchor|term|Term}} <translate>term</translate> {{English term|term}} : ''Definition verification needed'' : <translate>definition</translate> Notes: 1. Omit the "Definition verification" if you're sure that your definition is correct. 2. You can add several values for anchor, if it has spelling or capitalization variants; see the documentation for Template:Anchor and examples in other terms. </nowiki>--></noinclude> {{see also|wikt:en:Appendix:Glossary}} [[Wikifunctions talk:Glossary|토론 페이지]]에서 용어를 요청하거나 더 많은 용어를 추가하고 정의를 개선하세요. {|class="toccolours" style="margin:.2em auto;padding:.2em .5em;text-align:center" dir="ltr" lang="en" |- |style="padding:0;width:100%"|{{CompactTOC}} |} == A == ; {{anchor|abstract|Abstract}} 추상 {{English term|abstract}} : [[#natural_language|특정한 자연어]]가 아니라 그로부터의 추상화; 자연어 텍스트, 문장 또는 구의 의미에 대한 표기법을 제공하는 것을 목표로합니다. [[#concrete|구상]]의 반대. ; {{anchor|abstracttext|AbstractText}} AbstractText {{English term|AbstractText}} : [[#Wikifunctions|위키함수]] 아이디어의 프로토 타입 [https://github.com/google/abstracttext 구현]. ; {{anchor|abstract_article}} <span lang="en" dir="ltr" class="mw-content-ltr">Abstract Article</span> {{English term|abstract article}} : <span lang="en" dir="ltr" class="mw-content-ltr">A page in the main namespace of [[#abstract_Wikipedia|Abstract Wikipedia]]; a page that is similar to a Wikipedia article, but that is [[#abstract|abstract]]. The opposite of [[#concrete_article|concrete article]]. ("Abstract" is an adjective here; it ''doesn't'' mean "a summary of an article".)</span> ; {{anchor|abstract_content}} 추상 콘텐츠 {{English term|abstract content}} : [[#Content|콘텐츠]] 참조. ; {{anchor|abstract_Wikipedia|Abstract_Wikipedia}} 추상 위키백과 {{English term|Abstract Wikipedia}} : [[#local_Wikipedia|로컬 위키백과]]에서 [[#natural_language|자연어]]로 [[#article|문서]]를 [[#Renderer|렌더링]]하는 데 사용할 수 있는 모든 [[#Content|콘텐츠]]의 예비 이름; 현재 해당 [[#Item|항목]] 옆에 [[#Wikidata|위키데이터]]에 존재하도록 제안되었지만 [[#development_project|개발 프로젝트]]의 [[#Part_P2|Part P2]] 이전에 논의될 것입니다. ; {{anchor|alias}} 별칭 {{English term|alias}} : 객체를 찾는 데 가장 먼저 사용되는 객체의 대체 레이블입니다. ; {{anchor|argument}} 인수 {{English term|argument}} : <span lang="en" dir="ltr" class="mw-content-ltr">an input given to a [[#function call|function call]].</span> ; {{anchor|argument reference}} <span lang="en" dir="ltr" class="mw-content-ltr">argument reference</span> {{English term|argument reference}} : <span lang="en" dir="ltr" class="mw-content-ltr">a [[#reference|reference]] to one of the supplied arguments within a [[#composition|composition]].</span> ; {{anchor|array}} <span lang="en" dir="ltr" class="mw-content-ltr">array</span> {{English term|array}} : <span lang="en" dir="ltr" class="mw-content-ltr">Many programming languages have an "array" type. The counterparts in Wikifunctions are [[#list|list]] and [[#typed list|typed list]]. See also [[#Benjamin array|Benjamin array]].</span> ; {{anchor|article|Article}} 문서 {{English term|article}} : <span class="mw-translate-fuzzy">일반적으로 [[#Wikipedia|위키백과]]의 한 항목을 나타내는 위키백과의 기본 이름공간에 있는 문서.</span> == B == ; {{anchor|Benjamin array}} <span lang="en" dir="ltr" class="mw-content-ltr">Benjamin array</span> {{English term|Benjamin array}} : <span lang="en" dir="ltr" class="mw-content-ltr">a way to denote [[#typed list|typed list]] proposed by Benjamin Degenhart, where a typed list is stored as a JSON list whose first element denotes the type. This is in contrast with the previous proposed schema, which uses LISP-style singly-linked lists, in which the type must be stored once in each node.</span> ; {{anchor|boolean|Boolean}} <span lang="en" dir="ltr" class="mw-content-ltr">boolean</span> {{English term|boolean}} : <span lang="en" dir="ltr" class="mw-content-ltr">a value that can have 2 states, usually denoted true and false.</span> ; {{anchor|built-in|builtin}} 내장된 {{English term|built-in}} : 평가자가 제공하고 위키 인터페이스를 통해 편집할 수없는 함수의 기본 구현. == C == ; {{anchor|call}} 호출 {{English term|call}} : [[#function call|함수 호출]] 참조. 영어에서는 [[#invoke|인보크(invoke) 또는 인보케이션(invocation)]]이라는 용어도 사용할 수 있습니다. ; {{anchor|canonical|canonicalized|canonicalised}} 표준형의 {{English term|canonical, canonicalized, canonicalised}} : 구체적이고 덜 장황하며 따라서 [[#JSON|JSON]]으로 [[#ZObject|Z객체]]를 표현하는 더 읽기 쉬운 방법입니다. Z객체는 위키함수에 저장되는 일반적인 표현입니다. 이것은 [[#normal|정규형]]과 반대입니다. ; {{anchor|character}} 문자 {{English term|character}} : 문자열의 구성 요소인 유니 코드로 정의된 문자; 문자는 여러 바이트(또는 8진수)로 구성 될 수 있습니다. ; {{anchor|claim|Claim}} <span lang="en" dir="ltr" class="mw-content-ltr">claim</span> {{English term|claim}} : <span lang="en" dir="ltr" class="mw-content-ltr">In the [[:d:Special:MyLanguage/Wikidata:Glossary#Claim|Wikibase data model]], a claim is a main snak plus optional qualifiers, expressing an assertion about an entity (without references or rank).</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example: Entity: Albert Einstein</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Claim: Spouse = Mileva Marić, starting in 1903</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Main snak: P26 (spouse) → Q937 (Mileva Marić)</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Qualifier snak: P580 (start time) → 1903</span> : <span lang="en" dir="ltr" class="mw-content-ltr">→ “Albert Einstein’s spouse was Mileva Marić, starting in 1903.”</span> : <span lang="en" dir="ltr" class="mw-content-ltr">The claim can later be turned into a statement by adding a reference and rank.</span> ; {{anchor|composition}} 컴포지션 {{English term|composition}} : 다른 함수의 조합에 의해 구현이 제공되는 함수의 구현 형태; [[Special:MyLanguage/Wikifunctions:Function model#Composition|함수 모델]] 참조. ; {{anchor|composition notation}} 컴포지션 표기법 {{English term|composition notation}} : 컴포지션(composition)에 관한 읽기 쉬운 표기법; [[Special:MyLanguage/Wikifunctions:Function model#Composition|함수 모델]] 참조. ; {{anchor|concrete|Concrete}} 구상 {{English term|concrete}} : [[#natural_language|특정 자연어]]에서. [[#abstract|추상]]의 반대. ; {{anchor|concrete_article}} <span lang="en" dir="ltr" class="mw-content-ltr">concrete article</span> {{English term|concrete article}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#article|article]]. The opposite of [[#abstract_article|Abstract Article]].</span> ; {{anchor|cons}} 단점 {{English term|cons}} : 상단에 요소를 추가하여 새로운 리스트를 생성하는 함수; [[phab:T261474]]을 참조. 위키백과의 [[w:cons|단점]]을 참조하세요. ; {{anchor|constructor|Constructor}} 생성자 {{English term|constructor}} : <span class="mw-translate-fuzzy">[[#Content|콘텐츠]]의 [[#abstract|추상]] 빌딩 블록; 생성자는 단일 구문 또는 문장 구조의 의미를 포착하는 것을 목표로 하며 종종 다른 생성자를 취할 수있는 슬롯을 가지고 있으며 다른 생성자의 슬롯을 채우는 값으로 자체적으로 사용될 수 있습니다.</span> ; {{anchor|Content}}<!--do not add |content to the anchor, it is used by MediaWiki--> 콘텐츠, 추상 콘텐츠 {{English term|content, abstract content}} : [[#Constructor|생성자]]에서 조립된 텍스트 또는 텍스트 조각의 추상 표현. 기술적으로는 인스턴스화 된 생성자. 최상위 생성자는 전체 [[#article|문서]]를 나타내는 데 사용되며 [[#Abstract_Wikipedia|추상 위키백과]]에 저장되지만 내용은 문장이나 구에 대한 것일 수도 있습니다. 추상 콘텐츠라고도 합니다. ; {{anchor|curry}} curried, curry, currying {{English term|curried, curry, currying}} : 커리 함수는 여러 인수를 각각 단일 인수가 있는 일련의 함수로 변환한 함수입니다. 이 기술은 미국 수학자 [[:w:en:Haskell하스켈 카레]]의 이름을 따서 명명되었습니다. 위키백과의 [[:w:en:Currying|커링]]을 참조하세요. == D == ; {{anchor|deserialization|Deserialization|deserialisation|Deserialisation}} 역직렬화 {{English term|deserialization}} : [[#serialization|직렬화]]의 반대. ; {{anchor|development_project|Development_project}} 개발 프로젝트 {{English term|development project}} : [[#Wikifunctions|위키함수]] 및 [[#Abstract_Wikipedia|추상 위키백과]] 개발 프로젝트; [[:m:Special:MyLanguage/Abstract Wikipedia/Plan|추상 위키백과 계획]] 참조. ; {{anchor|display function}} <span lang="en" dir="ltr" class="mw-content-ltr">display function</span> {{English term|display function}} : <span lang="en" dir="ltr" class="mw-content-ltr">a synonym of [[#renderer|renderer]]. For example, a function that converts a [[#type|type]] into a string that users can understand, such as converting a Number 123456 to "123,456" in (International) English, "1,23,456" in Indian English, "123.456" in French, etc., or converting the Date '2024','03','12' to '2024-03-12', and so on.</span> ; {{anchor|documentation}} 문서화 {{English term|documentation}} : 사람이 읽을 수 있는 객체를 설명하는 텍스트. == E == ; {{anchor|eney|eneyjj}} eneyj {{English term|eneyj}} :# [[#Wikifunctions|위키함수]]의 프로토타입 모델; :# [[#abstracttext|abstracttext]]에 제공된 해당 모델의 [[#evaluator|평가자]]에 대한 자바 스크립트 구현. ; {{anchor|error|Error}} 에러 {{English term|error}} : <span class="mw-translate-fuzzy">인스턴스가 평가 또는 검증의 문제를 나타내는 유형; [[Special:MyLanguage/Wikifunctions:Function model#Z5/Errors|함수 모델]] 참조.</span> ; {{anchor|evaluation|Evaluation}} <span lang="en" dir="ltr" class="mw-content-ltr">evaluation</span> {{English term|evaluation}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#evaluator|evaluator]].</span> ; {{anchor|evaluator|Evaluator}} 평가자 {{English term|evaluator}} : [[#ZObject|Z객체]]를 가져와 평가하는 소프트웨어, 즉 [[#Function|함수]]를 실행하고 결과를 반환하는 소프트웨어. 우리는 여러 평가자의 개발을 계획합니다. 평가자는 브라우저와 [[#Wikimedia_Foundation|위키미디어 재단]]의 서버, 클라우드, 모바일 장치의 앱 또는 기타 장소에서 구현 및 실행할 수 있습니다. [[#executor|실행자]] 및 [[#orchestrator|오케스트레이터]]와 비교합니다. ; {{anchor|execution|Execution}} <span lang="en" dir="ltr" class="mw-content-ltr">execution</span> {{English term|execution}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#executor|executor]].</span> ; {{anchor|executor|Executor|executors|Executors}} 실행자 {{English term|executor}} : 대중에게 노출되지 않는 일련의 내부 서비스 중 하나. [[#Orchestrator|오케스트레이터]]에 의해서만 호출 될 수 있습니다. 특정 프로그래밍 언어로 네이티브 코드를 실행합니다. 루아에 대한 하나의 실행 프로그램, 자바 스크립트에 대한 실행 프로그램, 파이썬에 대한 실행 프로그램 등이 있습니다. [https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-evaluator#executors 서비스 문서]를 참조. [[#evaluator|평가자]] 및 [[#orchestrator|오케스트레이터]]와 비교합니다. == F == ; {{anchor|function|Function}} 함수 {{English term|function}} : 일부 입력을 받아 출력을 반환하는 계산에 관한 사양; 위키백과의 [[w:ko:함수 (프로그래밍)|함수 (프로그래밍)]] 참조. ; {{anchor|function call|Function call}} 함수 호출 {{English term|function call}} : 함수 호출은 함수와 함수에 필요한 인수로 구성된 Z객체이며 다른 Z객체로 평가 될 수 있습니다. 영어에서는 "인보크(invoke)"라는 용어도 사용할 수 있습니다. ; {{anchor|function evaluator}} <span lang="en" dir="ltr" class="mw-content-ltr">function evaluator</span> {{English term|function evaluator}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#evaluator|evaluator]].</span> ; {{anchor|function executor}} <span lang="en" dir="ltr" class="mw-content-ltr">function executor</span> {{English term|function executor}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#executor|executor]].</span> ; {{anchor|function model}} 함수 모델 {{English term|function model}} : [[Special:MyLanguage/Wikifunctions:Function model|함수 모델]] 참조. ; {{anchor|function orchestrator}} <span lang="en" dir="ltr" class="mw-content-ltr">function orchestrator</span> {{English term|function orchestrator}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#orchestrator|orchestrator]].</span> ; {{anchor|function schemata}} <span lang="en" dir="ltr" class="mw-content-ltr">function schemata</span> {{English term|function schemata}} : <span lang="en" dir="ltr" class="mw-content-ltr">a set of pre-defined ZObjects used in [[#orchestrator|orchestrator]] and [[#evaluator|evaluator]]. The [[#WikiLambda system|WikiLambda system account]] also populates pre-defined ZObjects on-wiki from function schemata.</span> ; {{anchor|functional}} 함수형 {{English term|functional}} : <span class="mw-translate-fuzzy">"순수 함수형"의 줄임말로, 그러한 함수의 평가는 부작용이 없고 결정론적입니다. 즉, 항상 동일합니다; 위키백과의 [[w:en:Purely functional programming|순수 함수형 프로그래밍]] 참조; [[Special:MyLanguage/Wikifunctions:Function model#non-functional|함수 모델]] 참조.</span> == G == ; {{anchor|generic type}} 제네릭 유형 {{English term|generic type}} : 함수 호출의 [[#evaluation|평가]]에 의해 생성 된 유형. == I == ; {{anchor|identity|Identity}} 식별 {{English term|identity}} : 유형의 식별은 유형으로 평가되는 (특정) 함수의 인스턴스입니다. 단순 유형의 경우, 유형 자체에 대한 참조입니다. ; {{anchor|implementation|Implementation}} 구현 {{English term|implementation}} : <span class="mw-translate-fuzzy">[[#function|함수]]를 실행하는 특별한 방법. 구현은 특정 프로그래밍 언어로 된 코드 조각일 수도 있고 [[#evaluator|평가자]]에 "내장 된" 기능을 참조하거나 다른 함수에 대한 호출을 결합할 수도 있습니다. 함수에는 많은 구현이있을 수 있으며 모두 동일해야합니다. "[[#ZFunction|Z함수]] 구현"의 약자입니다.</span> ; {{anchor|instance}} 인스턴스 {{English term|instance}} : 모든 Z객체는 해당 유형의 인스턴스입니다. ; {{anchor|invoke}} 인보크 {{English term|invoke}} : 영어로 [[#call|호출]]의 동의어. [[#function call|함수 호출]]을 참조하세요. ; {{anchor|item|Item}} 항목 {{English term|item}} : [[#Wikidata|위키데이터]]의 지식 기반에 있는 항목; 위키데이터 용어집의 [[:d:Wikidata:Glossary#Item|항목]] 참조. == J == ; {{anchor|JSON}} JSON {{English term|JSON}} : <span class="mw-translate-fuzzy">널리 사용되는 데이터 직렬화; 위키백과의 [[w:en:JSON|JSON]]을 참조.</span> == K == ; {{anchor|key|Key}} 키 {{English term|key}} : 문자 K와 자연수로 끝나고 선택적으로 앞에 [[#ZID|ZID]]가 오는 문자열. 키는 일반적으로 [[#Type|유형]] 또는 [[#Function|함수]]에 대한 [[#Wikifunctions|위키함수]]에서 정의되며 [[#ZObject|Z객체]]를 강화하는 데 사용됩니다. == L == ; {{anchor|label}} 레이블 {{English term|label}} : Z객체를 식별하기 위해 주어지는 이름. 일반 텍스트만 가능. ; {{anchor|lexeme|Lexeme}} 어휘소 {{English term|lexeme}} : 대략적인 단어에 대한 사전 지식을 저장하는 [[#Wikidata|위키데이터]]의 항목; 위키데이터 용어집의 [[d:Wikidata:Glossary#Lexeme|어휘소]] 항목 참조. ; {{anchor|linearizer|Linearizer}} linearizer {{English term|linearizer}} : <span class="mw-translate-fuzzy">Z객체를 문자열로 변환하는 함수. [[$parser|파서]]의 반대입니다.</span> ; {{anchor|list|List}} 리스트 {{English term|list}} : 정렬된 엔티티에서 임의의 수의 인스턴스를 그룹화하는 데이터 유형; 위키백과의 [[w:en:List (abstract data type)|리스트 (추상 데이터 유형)]]을 참조하세요. ; {{anchor|literal}} 리터럴 {{English term|literal}} : Z객체가 아닌 값. 현재 유일하게 허용되는 리터럴은 문자열입니다. ; {{anchor|local_Wikipedia|Local_Wikipedia}} 로컬 위키백과 {{English term|local Wikipedia}} : 히브리어 위키백과, 일본어 위키백과 또는 이탈리아어 위키백과와 같은 특정 언어로 된 [[#Wikipedia|위키백과]]. == M == ; {{anchor|Multlingual_Wikipedia|multilingual_Wikipedia}} 다국어 위키백과 {{English term|multilingual Wikipedia}} : [[#local_Wikipedia|로컬 위키백과]]가 [[#Abstract_Wikipedia|추상 위키백과]]의 [[#Content|콘텐츠]]를 [[#Renderer|렌더링]]하여 자신의 언어로 더 포괄적이고 최신이며 알맞은 위키백과를 가질 수 있도록하는 구조; [[:m:Special:MyLanguage/Abstract Wikipedia/Architecture|추상 위키백과 구조]] 참조. == N == ; {{anchor|natural_language|Natural_language}} 자연어 {{English term|natural language}} : 영어와 타갈로그어 또는 스와힐리어와 같은 넓은 의미의 특정 자연어; 위키백과의 [[w:en:Natural language|자연어]]를 참조하세요. ; {{anchor|normal|Normal|normalized|Normalized|normalised}} 정규형의, 정규형 {{English term|normal}} : [[#JSON|JSON]]으로 [[#ZObject|Z객체]]를 표현하는 확장되고 쉽게 처리 가능하며 매우 균일한 방법입니다. 이것은 [[#canonical|표준형]]과 반대입니다. ; {{anchor|nothing|Nothing}} nothing {{English term|nothing}} : 인스턴스를 가질 수 없는 데이터 유형; 위키백과의 [[w:en:Bottom type|바닥 유형]] 참조. == O == ; {{anchor|object|Object}} 객체 {{English term|object}} :# 자바 스크립트 또는 JSON에서 객체는 기본적으로 연관 배열입니다. 위키백과의 [[w:ko:연관 배열|연관 배열]]을 참조하세요. :# <span lang="en" dir="ltr" class="mw-content-ltr">In Wikifunctions, synonym of [[#ZObject|ZObject]].</span> ; {{anchor|orchestration|Orchestration}} <span lang="en" dir="ltr" class="mw-content-ltr">orchestration</span> {{English term|orchestration}} :<span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#orchestrator|orchestrator]].</span> ; {{anchor|orchestrator|Orchestrator}} 오케스트레이터 {{English term|orchestrator}} : <span class="mw-translate-fuzzy">[[#ZObject|Z객체]]를 가져와 [[#Evaluator|평가]]된 버전을 반환하는 서비스입니다. 이를 위해 필요한 다른 Z객체, 일부 함수 호출을 평가하기위한 [[#Executor|실행자]] 및 [[#Wikidata|위키데이터]]와 같은 기타 서비스에 대한 위키를 호출합니다. [https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-orchestrator#wikifunctions-function-orchestrator 서비스 문서]를 참조하세요. [[#evaluator|평가자]] 및 [[#executor|실행자]]와 비교합니다.</span> == P == ; {{anchor|page|Page}} 문서 {{English term|page}} : <span class="mw-translate-fuzzy">[[#wiki|위키]]는 독립적으로 편집할 수 있는 여러 개별 페이지로 구성됩니다.</span> ; {{anchor|parser|Parser}} 파서 {{English term|parser}} : <span class="mw-translate-fuzzy">문자열을 Z객체로 변환하는 함수. [[$linearizer|linearizer]]의 반대.</span> ; {{anchor|pair|Pair}} 짝 {{English term|pair}} : 특정 (임의의) 유형의 두 Z객체를 포함하는 복합 Z객체. ; {{anchor|part_P1|Part_P1}} 파트 P1 {{English term|Part P1}} : [[#Wikifunctions|위키함수]] 생성을 다루는 [[#development_project|개발 프로젝트]]의 일부입니다. 그것은 프로젝트의 시작 부분에서 시작하여 평생 동안 계속됩니다. [[:m:Special:MyLanguage/Abstract Wikipedia/Tasks#Part P1: Wikifunctions|파트 P1: 위키함수]]를 참조하세요. ; {{anchor|part_P2|Part_P2}} 파트 P2 {{English term|Part P2}} : [[#Abstract_Wikipedia|추상 위키백과]] 생성을 다루는 [[#development_project|개발 프로젝트]]의 일부입니다. 프로젝트에서 약 1년 후에 시작되어 이 기간의 후반기 동안 계속됩니다. [[:m:Special:MyLanguage/Abstract Wikipedia/Tasks#Part P2: Abstract Wikipedia|파트 P2: 추상 위키백과]] 참조. ; {{anchor|persistent|Persistent}} 영속적, 영속 {{English term|persistent}} : [[#ZID|ZID]]가 있고 위키의 자체 페이지가 있는 [[#ZObject|Z객체]] 대부분의 영속 Z객체에는 ZID가 없는 Z객체인 [[#value|값]]이 포함되어 있으므로 영속적이지 않습니다. ; {{anchor|property|Property}} 속성 {{English term|property}} : [[#Wikidata|위키데이터]]의 지식 기반에서 [[#Item|항목]]에 대해 [[#Statement|서술]]하는 데 사용됩니다. 위키데이터 용어집에서 [[:d:Wikidata:Glossary#Property|속성]] 참조. == Q == ; {{anchor|quote|Quote}} 인용 {{English term|quote}} : 평가되지는 않지만 그대로 유지되는 데이터 구조. ; {{anchor|QID}} QID {{English term|QID}} : [[#Wikidata|위키데이터]] 항목의 식별자로, 문자 "Q" 뒤에 정수가 오는 것으로 구성됩니다. == R == ; {{anchor|reading function}} <span lang="en" dir="ltr" class="mw-content-ltr">reading function</span> {{English term|reading function}} : <span lang="en" dir="ltr" class="mw-content-ltr">a synonym of [[#parser|parser]]. A function that converts user text input from a string into a given Type. For example, converting the String "123456" to the Number '123456', or the string "2024-03-12" to the Date '2024', '03', '12'.</span> ; {{anchor|reference|Reference}} 참조 {{English term|reference}} : 기본 객체를 나타내는 ID입니다. 예를 들어, 문자열 "Z11"은 유형 Z11/단어 언어 텍스트를 나타냅니다. : {{TakeNote}}이 용어는 위키데이터와는 완전히 다른 의미를 가지고 있습니다. 위키백과의 [[w:en:Reference (computer science)|참조 (컴컴퓨터 과학)]] 참조. ; {{anchor|renderer|Renderer}} 렌더러 {{English term|renderer}} (1) : <span lang="en" dir="ltr" class="mw-content-ltr">a function to convert a ZObject to a string. The opposite of [[#parser|parser]]. (formerly called "linearizer")</span> ; <span lang="en" dir="ltr" class="mw-content-ltr">renderer</span> {{English term|renderer}} (2) : [[#natural_language|자연어]]에 대한 [[#Content|콘텐츠]]와 식별자를 입력으로 가져오고 해당 자연어의 텍스트를 출력으로 반환하고, [[#Lexeme|어휘소]]의 지식을 사용하여 콘텐츠를 구체적인 텍스트로 나타내는 [[#Function|함수]]입니다. : {{TakeNote}}<span lang="en" dir="ltr" class="mw-content-ltr">This is a future feature, and the meaning of the term "renderer" in the {{Pg|:m:Abstract Wikipedia/Historic proposal|original proposal}}; this term collides with the current usage of "renderer", so it may be renamed in the future.</span> ; {{anchor|reify}} 구체화 {{English term|reify}} : 객체를 구성 부분으로 분해하여 부분에 개별적으로 접근할 수 있도록 하는 함수; 위키백과에서 [[w:en:Reification (computer science)|구체화]] 참조; [[phab:T261474]] 참조. ; {{anchor|REPL}} REPL {{English term|REPL}} : Read / Eval / Print - Loop, 입력을 받아 평가하고 결과를 표시하는 명령 줄 인터페이스; 위키백과의 [[w:ko:REPL|REPL]] 참조; [[Special:MyLanguage/Wikifunctions:Function model#REPL|함수 모델]] 참조. == S == ; {{anchor|schemata}} <span lang="en" dir="ltr" class="mw-content-ltr">schemata</span> {{English term|schemata}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#function schemata|function schemata]].</span> ; {{anchor|serialization|Serialization|serialisation|Serialisation}} 직렬화 {{English term|serialization}} : [[#JSON|JSON]]에서 Z객체를 표현하는 방법; [[#canonical|표준형]], [[#normal|정규형]]도 참조. ; {{anchor|snak|Snak}}<span lang="en" dir="ltr" class="mw-content-ltr">snak</span> {{English term|snak}} : <span lang="en" dir="ltr" class="mw-content-ltr">In the [[:mw:Special:MyLanguage/Wikibase/DataModel|Wikibase data model]], a snak is the smallest unit of a statement, linking a property to either a value, “no value”, or “some value.”</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example [[#statement|statement]] for {{Q|Q937}} with 3 snaks:</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Main snak:</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P26}} → Value: {{Q|Q76346}}</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Qualifier snak (adds context):</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P580}} → Value: 1903</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Reference snak (supports the claim):</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P248}} → Value: {{Q|Q23833686}}</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Resulting statement (in words): “Albert Einstein’s spouse was Mileva Marić, starting in 1903, as stated in the Catalog of the German National Library.”</span> ; {{anchor|statement|Statement}} 서술 {{English term|statement}} : <span class="mw-translate-fuzzy">[[#Wikidata|위키데이터]]의 지식 기반에서 [[#Item|항목]]에 대한 지식을 제공하는 데 사용됩니다. 위키데이터 용어집의 [[:d:Special:MyLanguage/Wikidata:Glossary#Statement|서술]] 참조.</span> ; {{anchor|string}} 문자열 {{English term|string}} : 일련의 문자. ; {{anchor|sum type|Sum type}} 합계 유형 {{English term|sum type}} : 구성 유형의 인스턴스를 가질 수 있는 유형; 위키백과의 [[w:en:Sum type|집계 유형]] 참조. [[Special:MyLanguage/Wikifunctions:Function model#Zx/Sum_types|함수 모델]] 참조. == T == ; {{anchor|template}} 틀 {{English term|template}} : <span class="mw-translate-fuzzy">[[#renderer|렌더러]]를 자리 표시자가 산재된 텍스트 또는 "슬롯"으로 지정하는 방법은 [[#constructor|생성자]]의 데이터, 함수 계산 또는 다른 틀의 내용으로 채울 수 있습니다. 틀 구문에 대한 자세한 내용은 [[:m:Special:MyLanguage/Abstract Wikipedia/Template Language for Wikifunctions|위키함수용 틀 언어]] 문서를 참조하세요.</span> ; {{anchor|tester|Tester}} 테스터 {{English term|tester}} : 주어진 [[#ZFunction|Z함수]]가 정확하게 일을 하고 있는지 자동으로 결정하는 방법. [[#function|함수]]에는 일반적으로 여러 테스터가 있으며, 각 테스터는 함수에 대한 일부 입력을 지정하고 주어진 입력에 대한 출력이 충족되어야합니다. 예를 들어, "케이스 제목(title case)" 함수의 테스터에는 다음이 포함될 수 있습니다: "abc"는 "Abc"가 되어야합니다; "war and peace"는 "War and Peace"가 되어야합니다; "война и мир"는 "Война и мир"가 되어야합니다; "123"은 "123"으로 유지되어야합니다. ; {{anchor|transient|Transient}} 일시적 {{English term|transient}} : [[#persistent|영속적]]의 반대. ; {{anchor|type|Type}} 유형 {{English term|type}} : 객체의 유형은 주어진 객체를 해석하고 이해하는 방법과 객체로 수행할 수 있는 작업을 알려줍니다. 예를 들어 값이 "2023"인 객체가 있는 경우 유형이 정수인지, 연도인지 또는 문자열인지에 따라 해당 객체를 다르게 이해합니다. 모든 객체는 "실제 세계에 있는 것"을 나타냅니다. 정수 2023은 2023년과 다릅니다. 유형은 주어진 객체를 해석하는 방법을 알려주므로 실제 세계에서 어떤 것을 참조하는지 알 수 있습니다. 기술적으로는 해당 유형의 객체가 구성되는 방식과 해당 유형의 유효한 객체가 되기 위해 충족해야 하는 조건을 정의합니다. 유형은 Z객체의 유효성을 검사하는 [[#Function|함수]]를 제공하여 [[#ZObject|Z객체]]가 이 유형의 유효한 인스턴스가 되는 조건을 정의합니다. 유형은 Z객체 자체이므로 [[#Wikifunctions|위키함수]]의 기여자는 새로운 유형을 만들 수 있습니다. ; {{anchor|type converter}} <span lang="en" dir="ltr" class="mw-content-ltr">type converter</span> {{English term|type converter}} : <span lang="en" dir="ltr" class="mw-content-ltr">A script written in some programming language (such as JavaScript), taking a native object (such as BigInt), and returning a JSON object representing the corresponding ZObject; or ''vice versa''.</span> ; {{anchor|typed list|Typed List}} <span lang="en" dir="ltr" class="mw-content-ltr">typed list</span> {{English term|typed list}} : <span lang="en" dir="ltr" class="mw-content-ltr">A typed list is a [[#list|list]] in which all members of the list are of a specific, predefined [[#type|type]]. For example, a typed list of [[#string|strings]] is a list in which all members of the list are strings. A typed list takes one argument: the type that all the members of the list have to be an instance of. Typed lists are probably the most widely used [[#generic type|generic type]].</span> == V == ; {{anchor|value}} 값 {{English term|value}} : 다른 Z객체의 [[#key|키]]와 연관된 문자열 또는 [[#ZObject|Z객체]]. ; {{anchor|validation|Validation}} <span lang="en" dir="ltr" class="mw-content-ltr">validation</span> {{English term|validation}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#validator|validator]].</span> ; {{anchor|validator|Validator}} 검증자 {{English term|validator}} : <span class="mw-translate-fuzzy">Z객체를 인수로 사용하고 발견된 오류 목록을 반환하는 함수.</span> == W == ; {{anchor|wiki|Wiki}} 위키 {{English term|wiki}} : [[#page|페이지]]를 쉽고 공동으로 편집 할 수 있는 웹 사이트. ; {{anchor|Wikidata}} 위키데이터 {{English term|Wikidata}} : 공동으로 편집된 자유 지식 기반인 [[#Wikimedia_Foundation|위키미디어 재단]]의 프로젝트; [[:m:Special:MyLanguage/Wikidata|위키데이터]] 참조. ; {{anchor|Wikifunctions}}{{anchor|Wikilambda}} 위키함수 {{English term|Wikifunctions}} : [[#Wikimedia_Foundation|위키미디어 재단]]의 새로운 프로젝트; 무료이고 공동으로 개발하며 유지 관리하는 [[#Function|함수]] 카탈로그. {{Pg|:m:Abstract Wikipedia/Historic proposal|원래 제안}}에서 처음에는 위키람다로 알려졌습니다(이 이름은 현재 위키람다 확장에 사용됨). ; {{anchor|WikiLambda}} 위키람다 {{English term|WikiLambda}} : 프로젝트를 구동하는 데 사용되는 소프트웨어, [[mw:Special:MyLanguage/Extension:WikiLambda|확장:위키람다]]. ; {{anchor|WikiLambda system}} 위키람다 시스템 {{English term|WikiLambda system}} : <span lang="en" dir="ltr" class="mw-content-ltr">an automated system account that is a key part of the WikiLambda extension. See [[User:WikiLambda system]] for its current function.</span> ; {{anchor|WMF|Wikimedia_Foundation}} 위키미디어 재단 {{English term|Wikimedia Foundation}} : 위키미디어 운동을 지원하는 조직; [[:m:Special:MyLanguage/Wikimedia Foundation|위키미디어 재단]] 참조. ; {{anchor|Wikipedia}} 위키백과 {{English term|Wikipedia}} : [[#Wikimedia_Foundation|위키미디어 재단]]의 프로젝트, 공동으로 편집하는 자유 백과사전, [[:m:Special:MyLanguage/Wikipedia|위키백과]] 참조. ; 위키백과, 추상 {{English term|Wikipedia, Abstract}} : [[#Abstract_Wikipedia|추상 위키백과]] 참조. ; 위키백과, 다국어 {{English term|Wikipedia, multilingual}} : [[#multilingual_Wikipedia|다국어 위키백과]] 참조. == Z == ; {{anchor|ZID|ZIDs}} ZID {{English term|ZID}} : 문자 Z로 시작하고 뒤에 자연수가 오는 ID. [[#persistent|영구]] [[#ZObject|Z객체]]를 식별하는 데 사용됩니다. ; {{anchor|zfunction|ZFunction}} Z함수 {{English term|ZFunction}} : [[#evaluator|평가자]]를 통해 사용할 수 있는 특정 [[#function|함수]]를 설명하는 [[#Wikifunctions|위키함수]]의 위키 문서입니다. 각 Z함수는 하나 이상의 [[#implementation|구현]]에 의해 코드에서 실현 될 수 있으며, 상기 구현은 하나 이상의 [[#tester|테스터]] Z함수에 의해 올바른 것으로 검증될 수 있습니다. ; {{anchor|ZKey}} Z키 {{English term|ZKey}} : 특정 [[#type |유형]]에 대한 [[#key|키]]를 정의하는 [[#ZObject|Z객체]]. ; {{anchor|ZList}} Z리스트 {{English term|ZList}} : 다른 Z객체의 순서가 지정된 시퀀스에 대한 [[#ZObject|Z객체]]. ; {{anchor|ZObject}} Z객체 {{English term|ZObject}} : [[#Wikifunctions|위키함수]]의 모든 항목은 Z객체입니다. 위키함수에 저장된 Z객체는 [[#ZID|ZID]]를 가지며 [[#Constructor|생성자]]와 [[#Function|함수]], [[#Type|유형]] 등과 같은 다양한 유형이 될 수 있습니다. Z객체는 [[#Key|키]]/[[#Value|값]] 쌍 집합으로 구성되며 각 키는 Z객체 당 한 번만 나타나고 값은 Z객체입니다. ; {{anchor|ZUnit}} ZUnit {{English term|ZUnit}} : [[:w:en:Unit type|단위 유형]]을 나타내는 [[#ZObject|ZObject]]입니다. [[Category:Glossary| {{#translation:}}]] 4j07u696ttprjxn0aqrpep3njtbqaw5 275513 275511 2026-05-16T12:21:44Z Tensama0415 73696 275513 wikitext text/x-wiki <noinclude><languages/> <!--<nowiki>(nowiki tags are so that the translate extension doesn't try to translate the TERM and DEFINITION in this boilerplate). Use this boilerplate for a new term: ; {{anchor|term|Term}} <translate>term</translate> {{English term|term}} : ''Definition verification needed'' : <translate>definition</translate> Notes: 1. Omit the "Definition verification" if you're sure that your definition is correct. 2. You can add several values for anchor, if it has spelling or capitalization variants; see the documentation for Template:Anchor and examples in other terms. </nowiki>--></noinclude> {{see also|wikt:en:Appendix:Glossary}} [[Wikifunctions talk:Glossary|토론 페이지]]에서 용어를 요청하거나 더 많은 용어를 추가하고 정의를 개선하세요. {|class="toccolours" style="margin:.2em auto;padding:.2em .5em;text-align:center" dir="ltr" lang="en" |- |style="padding:0;width:100%"|{{CompactTOC}} |} == A == ; {{anchor|abstract|Abstract}} 추상 {{English term|abstract}} : [[#natural_language|특정한 자연어]]가 아니라 그로부터의 추상화; 자연어 텍스트, 문장 또는 구의 의미에 대한 표기법을 제공하는 것을 목표로합니다. [[#concrete|구상]]의 반대. ; {{anchor|abstracttext|AbstractText}} AbstractText {{English term|AbstractText}} : [[#Wikifunctions|위키함수]] 아이디어의 프로토 타입 [https://github.com/google/abstracttext 구현]. ; {{anchor|abstract_article}} <span lang="en" dir="ltr" class="mw-content-ltr">Abstract Article</span> {{English term|abstract article}} : <span lang="en" dir="ltr" class="mw-content-ltr">A page in the main namespace of [[#abstract_Wikipedia|Abstract Wikipedia]]; a page that is similar to a Wikipedia article, but that is [[#abstract|abstract]]. The opposite of [[#concrete_article|concrete article]]. ("Abstract" is an adjective here; it ''doesn't'' mean "a summary of an article".)</span> ; {{anchor|abstract_content}} 추상 콘텐츠 {{English term|abstract content}} : [[#Content|콘텐츠]] 참조. ; {{anchor|abstract_Wikipedia|Abstract_Wikipedia}} 추상 위키백과 {{English term|Abstract Wikipedia}} : [[#local_Wikipedia|로컬 위키백과]]에서 [[#natural_language|자연어]]로 [[#article|문서]]를 [[#Renderer|렌더링]]하는 데 사용할 수 있는 모든 [[#Content|콘텐츠]]의 예비 이름; 현재 해당 [[#Item|항목]] 옆에 [[#Wikidata|위키데이터]]에 존재하도록 제안되었지만 [[#development_project|개발 프로젝트]]의 [[#Part_P2|Part P2]] 이전에 논의될 것입니다. ; {{anchor|alias}} 별칭 {{English term|alias}} : 객체를 찾는 데 가장 먼저 사용되는 객체의 대체 레이블입니다. ; {{anchor|argument}} 인수 {{English term|argument}} : <span lang="en" dir="ltr" class="mw-content-ltr">an input given to a [[#function call|function call]].</span> ; {{anchor|argument reference}} <span lang="en" dir="ltr" class="mw-content-ltr">argument reference</span> {{English term|argument reference}} : <span lang="en" dir="ltr" class="mw-content-ltr">a [[#reference|reference]] to one of the supplied arguments within a [[#composition|composition]].</span> ; {{anchor|array}} <span lang="en" dir="ltr" class="mw-content-ltr">array</span> {{English term|array}} : <span lang="en" dir="ltr" class="mw-content-ltr">Many programming languages have an "array" type. The counterparts in Wikifunctions are [[#list|list]] and [[#typed list|typed list]]. See also [[#Benjamin array|Benjamin array]].</span> ; {{anchor|article|Article}} 문서 {{English term|article}} : <span class="mw-translate-fuzzy">일반적으로 [[#Wikipedia|위키백과]]의 한 항목을 나타내는 위키백과의 기본 이름공간에 있는 문서.</span> == B == ; {{anchor|Benjamin array}} <span lang="en" dir="ltr" class="mw-content-ltr">Benjamin array</span> {{English term|Benjamin array}} : <span lang="en" dir="ltr" class="mw-content-ltr">a way to denote [[#typed list|typed list]] proposed by Benjamin Degenhart, where a typed list is stored as a JSON list whose first element denotes the type. This is in contrast with the previous proposed schema, which uses LISP-style singly-linked lists, in which the type must be stored once in each node.</span> ; {{anchor|boolean|Boolean}} <span lang="en" dir="ltr" class="mw-content-ltr">boolean</span> {{English term|boolean}} : <span lang="en" dir="ltr" class="mw-content-ltr">a value that can have 2 states, usually denoted true and false.</span> ; {{anchor|built-in|builtin}} 내장된 {{English term|built-in}} : 평가자가 제공하고 위키 인터페이스를 통해 편집할 수없는 함수의 기본 구현. == C == ; {{anchor|call}} 호출 {{English term|call}} : [[#function call|함수 호출]] 참조. 영어에서는 [[#invoke|인보크(invoke) 또는 인보케이션(invocation)]]이라는 용어도 사용할 수 있습니다. ; {{anchor|canonical|canonicalized|canonicalised}} 표준형의 {{English term|canonical, canonicalized, canonicalised}} : 구체적이고 덜 장황하며 따라서 [[#JSON|JSON]]으로 [[#ZObject|Z객체]]를 표현하는 더 읽기 쉬운 방법입니다. Z객체는 위키함수에 저장되는 일반적인 표현입니다. 이것은 [[#normal|정규형]]과 반대입니다. ; {{anchor|character}} 문자 {{English term|character}} : 문자열의 구성 요소인 유니 코드로 정의된 문자; 문자는 여러 바이트(또는 8진수)로 구성 될 수 있습니다. ; {{anchor|claim|Claim}} <span lang="en" dir="ltr" class="mw-content-ltr">claim</span> {{English term|claim}} : <span lang="en" dir="ltr" class="mw-content-ltr">In the [[:d:Special:MyLanguage/Wikidata:Glossary#Claim|Wikibase data model]], a claim is a main snak plus optional qualifiers, expressing an assertion about an entity (without references or rank).</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example: Entity: Albert Einstein</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Claim: Spouse = Mileva Marić, starting in 1903</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Main snak: P26 (spouse) → Q937 (Mileva Marić)</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Qualifier snak: P580 (start time) → 1903</span> : <span lang="en" dir="ltr" class="mw-content-ltr">→ “Albert Einstein’s spouse was Mileva Marić, starting in 1903.”</span> : <span lang="en" dir="ltr" class="mw-content-ltr">The claim can later be turned into a statement by adding a reference and rank.</span> ; {{anchor|composition}} 컴포지션 {{English term|composition}} : 다른 함수의 조합에 의해 구현이 제공되는 함수의 구현 형태; [[Special:MyLanguage/Wikifunctions:Function model#Composition|함수 모델]] 참조. ; {{anchor|composition notation}} 컴포지션 표기법 {{English term|composition notation}} : 컴포지션(composition)에 관한 읽기 쉬운 표기법; [[Special:MyLanguage/Wikifunctions:Function model#Composition|함수 모델]] 참조. ; {{anchor|concrete|Concrete}} 구상 {{English term|concrete}} : [[#natural_language|특정 자연어]]에서. [[#abstract|추상]]의 반대. ; {{anchor|concrete_article}} <span lang="en" dir="ltr" class="mw-content-ltr">concrete article</span> {{English term|concrete article}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#article|article]]. The opposite of [[#abstract_article|Abstract Article]].</span> ; {{anchor|cons}} 단점 {{English term|cons}} : 상단에 요소를 추가하여 새로운 리스트를 생성하는 함수; [[phab:T261474]]을 참조. 위키백과의 [[w:cons|단점]]을 참조하세요. ; {{anchor|constructor|Constructor}} 생성자 {{English term|constructor}} : <span class="mw-translate-fuzzy">[[#Content|콘텐츠]]의 [[#abstract|추상]] 빌딩 블록; 생성자는 단일 구문 또는 문장 구조의 의미를 포착하는 것을 목표로 하며 종종 다른 생성자를 취할 수있는 슬롯을 가지고 있으며 다른 생성자의 슬롯을 채우는 값으로 자체적으로 사용될 수 있습니다.</span> ; {{anchor|Content}}<!--do not add |content to the anchor, it is used by MediaWiki--> 콘텐츠, 추상 콘텐츠 {{English term|content, abstract content}} : [[#Constructor|생성자]]에서 조립된 텍스트 또는 텍스트 조각의 추상 표현. 기술적으로는 인스턴스화 된 생성자. 최상위 생성자는 전체 [[#article|문서]]를 나타내는 데 사용되며 [[#Abstract_Wikipedia|추상 위키백과]]에 저장되지만 내용은 문장이나 구에 대한 것일 수도 있습니다. 추상 콘텐츠라고도 합니다. ; {{anchor|curry}} curried, curry, currying {{English term|curried, curry, currying}} : 커리 함수는 여러 인수를 각각 단일 인수가 있는 일련의 함수로 변환한 함수입니다. 이 기술은 미국 수학자 [[:w:en:Haskell하스켈 카레]]의 이름을 따서 명명되었습니다. 위키백과의 [[:w:en:Currying|커링]]을 참조하세요. == D == ; {{anchor|deserialization|Deserialization|deserialisation|Deserialisation}} 역직렬화 {{English term|deserialization}} : [[#serialization|직렬화]]의 반대. ; {{anchor|development_project|Development_project}} 개발 프로젝트 {{English term|development project}} : [[#Wikifunctions|위키함수]] 및 [[#Abstract_Wikipedia|추상 위키백과]] 개발 프로젝트; [[:m:Special:MyLanguage/Abstract Wikipedia/Plan|추상 위키백과 계획]] 참조. ; {{anchor|display function}} <span lang="en" dir="ltr" class="mw-content-ltr">display function</span> {{English term|display function}} : <span lang="en" dir="ltr" class="mw-content-ltr">a synonym of [[#renderer|renderer]]. For example, a function that converts a [[#type|type]] into a string that users can understand, such as converting a Number 123456 to "123,456" in (International) English, "1,23,456" in Indian English, "123.456" in French, etc., or converting the Date '2024','03','12' to '2024-03-12', and so on.</span> ; {{anchor|documentation}} 문서화 {{English term|documentation}} : 사람이 읽을 수 있는 객체를 설명하는 텍스트. == E == ; {{anchor|eney|eneyjj}} eneyj {{English term|eneyj}} :# [[#Wikifunctions|위키함수]]의 프로토타입 모델; :# [[#abstracttext|abstracttext]]에 제공된 해당 모델의 [[#evaluator|평가자]]에 대한 자바 스크립트 구현. ; {{anchor|error|Error}} 에러 {{English term|error}} : <span class="mw-translate-fuzzy">인스턴스가 평가 또는 검증의 문제를 나타내는 유형; [[Special:MyLanguage/Wikifunctions:Function model#Z5/Errors|함수 모델]] 참조.</span> ; {{anchor|evaluation|Evaluation}} <span lang="en" dir="ltr" class="mw-content-ltr">evaluation</span> {{English term|evaluation}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#evaluator|evaluator]].</span> ; {{anchor|evaluator|Evaluator}} 평가자 {{English term|evaluator}} : [[#ZObject|Z객체]]를 가져와 평가하는 소프트웨어, 즉 [[#Function|함수]]를 실행하고 결과를 반환하는 소프트웨어. 우리는 여러 평가자의 개발을 계획합니다. 평가자는 브라우저와 [[#Wikimedia_Foundation|위키미디어 재단]]의 서버, 클라우드, 모바일 장치의 앱 또는 기타 장소에서 구현 및 실행할 수 있습니다. [[#executor|실행자]] 및 [[#orchestrator|오케스트레이터]]와 비교합니다. ; {{anchor|execution|Execution}} <span lang="en" dir="ltr" class="mw-content-ltr">execution</span> {{English term|execution}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#executor|executor]].</span> ; {{anchor|executor|Executor|executors|Executors}} 실행자 {{English term|executor}} : 대중에게 노출되지 않는 일련의 내부 서비스 중 하나. [[#Orchestrator|오케스트레이터]]에 의해서만 호출 될 수 있습니다. 특정 프로그래밍 언어로 네이티브 코드를 실행합니다. 루아에 대한 하나의 실행 프로그램, 자바 스크립트에 대한 실행 프로그램, 파이썬에 대한 실행 프로그램 등이 있습니다. [https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-evaluator#executors 서비스 문서]를 참조. [[#evaluator|평가자]] 및 [[#orchestrator|오케스트레이터]]와 비교합니다. == F == ; {{anchor|function|Function}} 함수 {{English term|function}} : 일부 입력을 받아 출력을 반환하는 계산에 관한 사양; 위키백과의 [[w:ko:함수 (프로그래밍)|함수 (프로그래밍)]] 참조. ; {{anchor|function call|Function call}} 함수 호출 {{English term|function call}} : 함수 호출은 함수와 함수에 필요한 인수로 구성된 Z객체이며 다른 Z객체로 평가 될 수 있습니다. 영어에서는 "인보크(invoke)"라는 용어도 사용할 수 있습니다. ; {{anchor|function evaluator}} <span lang="en" dir="ltr" class="mw-content-ltr">function evaluator</span> {{English term|function evaluator}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#evaluator|evaluator]].</span> ; {{anchor|function executor}} <span lang="en" dir="ltr" class="mw-content-ltr">function executor</span> {{English term|function executor}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#executor|executor]].</span> ; {{anchor|function model}} 함수 모델 {{English term|function model}} : [[Special:MyLanguage/Wikifunctions:Function model|함수 모델]] 참조. ; {{anchor|function orchestrator}} <span lang="en" dir="ltr" class="mw-content-ltr">function orchestrator</span> {{English term|function orchestrator}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#orchestrator|orchestrator]].</span> ; {{anchor|function schemata}} <span lang="en" dir="ltr" class="mw-content-ltr">function schemata</span> {{English term|function schemata}} : <span lang="en" dir="ltr" class="mw-content-ltr">a set of pre-defined ZObjects used in [[#orchestrator|orchestrator]] and [[#evaluator|evaluator]]. The [[#WikiLambda system|WikiLambda system account]] also populates pre-defined ZObjects on-wiki from function schemata.</span> ; {{anchor|functional}} 함수형 {{English term|functional}} : "순수 함수형"의 줄임말로, 그러한 함수의 [[#evaluation|평가]]는 부작용이 없고 결정론적입니다. 즉, 항상 동일합니다; 위키백과의 [[w:en:Purely functional programming|순수 함수형 프로그래밍]] 참조; [[Special:MyLanguage/Wikifunctions:Function model#non-functional|함수 모델]] 참조. == G == ; {{anchor|generic type}} 제네릭 유형 {{English term|generic type}} : 함수 호출의 [[#evaluation|평가]]에 의해 생성 된 유형. == I == ; {{anchor|identity|Identity}} 식별 {{English term|identity}} : 유형의 식별은 유형으로 평가되는 (특정) 함수의 인스턴스입니다. 단순 유형의 경우, 유형 자체에 대한 참조입니다. ; {{anchor|implementation|Implementation}} 구현 {{English term|implementation}} : <span class="mw-translate-fuzzy">[[#function|함수]]를 실행하는 특별한 방법. 구현은 특정 프로그래밍 언어로 된 코드 조각일 수도 있고 [[#evaluator|평가자]]에 "내장 된" 기능을 참조하거나 다른 함수에 대한 호출을 결합할 수도 있습니다. 함수에는 많은 구현이있을 수 있으며 모두 동일해야합니다. "[[#ZFunction|Z함수]] 구현"의 약자입니다.</span> ; {{anchor|instance}} 인스턴스 {{English term|instance}} : 모든 Z객체는 해당 유형의 인스턴스입니다. ; {{anchor|invoke}} 인보크 {{English term|invoke}} : 영어로 [[#call|호출]]의 동의어. [[#function call|함수 호출]]을 참조하세요. ; {{anchor|item|Item}} 항목 {{English term|item}} : [[#Wikidata|위키데이터]]의 지식 기반에 있는 항목; 위키데이터 용어집의 [[:d:Wikidata:Glossary#Item|항목]] 참조. == J == ; {{anchor|JSON}} JSON {{English term|JSON}} : <span class="mw-translate-fuzzy">널리 사용되는 데이터 직렬화; 위키백과의 [[w:en:JSON|JSON]]을 참조.</span> == K == ; {{anchor|key|Key}} 키 {{English term|key}} : 문자 K와 자연수로 끝나고 선택적으로 앞에 [[#ZID|ZID]]가 오는 문자열. 키는 일반적으로 [[#Type|유형]] 또는 [[#Function|함수]]에 대한 [[#Wikifunctions|위키함수]]에서 정의되며 [[#ZObject|Z객체]]를 강화하는 데 사용됩니다. == L == ; {{anchor|label}} 레이블 {{English term|label}} : Z객체를 식별하기 위해 주어지는 이름. 일반 텍스트만 가능. ; {{anchor|lexeme|Lexeme}} 어휘소 {{English term|lexeme}} : 대략적인 단어에 대한 사전 지식을 저장하는 [[#Wikidata|위키데이터]]의 항목; 위키데이터 용어집의 [[d:Wikidata:Glossary#Lexeme|어휘소]] 항목 참조. ; {{anchor|linearizer|Linearizer}} linearizer {{English term|linearizer}} : <span class="mw-translate-fuzzy">Z객체를 문자열로 변환하는 함수. [[$parser|파서]]의 반대입니다.</span> ; {{anchor|list|List}} 리스트 {{English term|list}} : 정렬된 엔티티에서 임의의 수의 인스턴스를 그룹화하는 데이터 유형; 위키백과의 [[w:en:List (abstract data type)|리스트 (추상 데이터 유형)]]을 참조하세요. ; {{anchor|literal}} 리터럴 {{English term|literal}} : Z객체가 아닌 값. 현재 유일하게 허용되는 리터럴은 문자열입니다. ; {{anchor|local_Wikipedia|Local_Wikipedia}} 로컬 위키백과 {{English term|local Wikipedia}} : 히브리어 위키백과, 일본어 위키백과 또는 이탈리아어 위키백과와 같은 특정 언어로 된 [[#Wikipedia|위키백과]]. == M == ; {{anchor|Multlingual_Wikipedia|multilingual_Wikipedia}} 다국어 위키백과 {{English term|multilingual Wikipedia}} : [[#local_Wikipedia|로컬 위키백과]]가 [[#Abstract_Wikipedia|추상 위키백과]]의 [[#Content|콘텐츠]]를 [[#Renderer|렌더링]]하여 자신의 언어로 더 포괄적이고 최신이며 알맞은 위키백과를 가질 수 있도록하는 구조; [[:m:Special:MyLanguage/Abstract Wikipedia/Architecture|추상 위키백과 구조]] 참조. == N == ; {{anchor|natural_language|Natural_language}} 자연어 {{English term|natural language}} : 영어와 타갈로그어 또는 스와힐리어와 같은 넓은 의미의 특정 자연어; 위키백과의 [[w:en:Natural language|자연어]]를 참조하세요. ; {{anchor|normal|Normal|normalized|Normalized|normalised}} 정규형의, 정규형 {{English term|normal}} : [[#JSON|JSON]]으로 [[#ZObject|Z객체]]를 표현하는 확장되고 쉽게 처리 가능하며 매우 균일한 방법입니다. 이것은 [[#canonical|표준형]]과 반대입니다. ; {{anchor|nothing|Nothing}} nothing {{English term|nothing}} : 인스턴스를 가질 수 없는 데이터 유형; 위키백과의 [[w:en:Bottom type|바닥 유형]] 참조. == O == ; {{anchor|object|Object}} 객체 {{English term|object}} :# 자바 스크립트 또는 JSON에서 객체는 기본적으로 연관 배열입니다. 위키백과의 [[w:ko:연관 배열|연관 배열]]을 참조하세요. :# <span lang="en" dir="ltr" class="mw-content-ltr">In Wikifunctions, synonym of [[#ZObject|ZObject]].</span> ; {{anchor|orchestration|Orchestration}} <span lang="en" dir="ltr" class="mw-content-ltr">orchestration</span> {{English term|orchestration}} :<span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#orchestrator|orchestrator]].</span> ; {{anchor|orchestrator|Orchestrator}} 오케스트레이터 {{English term|orchestrator}} : <span class="mw-translate-fuzzy">[[#ZObject|Z객체]]를 가져와 [[#Evaluator|평가]]된 버전을 반환하는 서비스입니다. 이를 위해 필요한 다른 Z객체, 일부 함수 호출을 평가하기위한 [[#Executor|실행자]] 및 [[#Wikidata|위키데이터]]와 같은 기타 서비스에 대한 위키를 호출합니다. [https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-orchestrator#wikifunctions-function-orchestrator 서비스 문서]를 참조하세요. [[#evaluator|평가자]] 및 [[#executor|실행자]]와 비교합니다.</span> == P == ; {{anchor|page|Page}} 문서 {{English term|page}} : <span class="mw-translate-fuzzy">[[#wiki|위키]]는 독립적으로 편집할 수 있는 여러 개별 페이지로 구성됩니다.</span> ; {{anchor|parser|Parser}} 파서 {{English term|parser}} : <span class="mw-translate-fuzzy">문자열을 Z객체로 변환하는 함수. [[$linearizer|linearizer]]의 반대.</span> ; {{anchor|pair|Pair}} 짝 {{English term|pair}} : 특정 (임의의) 유형의 두 Z객체를 포함하는 복합 Z객체. ; {{anchor|part_P1|Part_P1}} 파트 P1 {{English term|Part P1}} : [[#Wikifunctions|위키함수]] 생성을 다루는 [[#development_project|개발 프로젝트]]의 일부입니다. 그것은 프로젝트의 시작 부분에서 시작하여 평생 동안 계속됩니다. [[:m:Special:MyLanguage/Abstract Wikipedia/Tasks#Part P1: Wikifunctions|파트 P1: 위키함수]]를 참조하세요. ; {{anchor|part_P2|Part_P2}} 파트 P2 {{English term|Part P2}} : [[#Abstract_Wikipedia|추상 위키백과]] 생성을 다루는 [[#development_project|개발 프로젝트]]의 일부입니다. 프로젝트에서 약 1년 후에 시작되어 이 기간의 후반기 동안 계속됩니다. [[:m:Special:MyLanguage/Abstract Wikipedia/Tasks#Part P2: Abstract Wikipedia|파트 P2: 추상 위키백과]] 참조. ; {{anchor|persistent|Persistent}} 영속적, 영속 {{English term|persistent}} : [[#ZID|ZID]]가 있고 위키의 자체 페이지가 있는 [[#ZObject|Z객체]] 대부분의 영속 Z객체에는 ZID가 없는 Z객체인 [[#value|값]]이 포함되어 있으므로 영속적이지 않습니다. ; {{anchor|property|Property}} 속성 {{English term|property}} : [[#Wikidata|위키데이터]]의 지식 기반에서 [[#Item|항목]]에 대해 [[#Statement|서술]]하는 데 사용됩니다. 위키데이터 용어집에서 [[:d:Wikidata:Glossary#Property|속성]] 참조. == Q == ; {{anchor|quote|Quote}} 인용 {{English term|quote}} : 평가되지는 않지만 그대로 유지되는 데이터 구조. ; {{anchor|QID}} QID {{English term|QID}} : [[#Wikidata|위키데이터]] 항목의 식별자로, 문자 "Q" 뒤에 정수가 오는 것으로 구성됩니다. == R == ; {{anchor|reading function}} <span lang="en" dir="ltr" class="mw-content-ltr">reading function</span> {{English term|reading function}} : <span lang="en" dir="ltr" class="mw-content-ltr">a synonym of [[#parser|parser]]. A function that converts user text input from a string into a given Type. For example, converting the String "123456" to the Number '123456', or the string "2024-03-12" to the Date '2024', '03', '12'.</span> ; {{anchor|reference|Reference}} 참조 {{English term|reference}} : 기본 객체를 나타내는 ID입니다. 예를 들어, 문자열 "Z11"은 유형 Z11/단어 언어 텍스트를 나타냅니다. : {{TakeNote}}이 용어는 위키데이터와는 완전히 다른 의미를 가지고 있습니다. 위키백과의 [[w:en:Reference (computer science)|참조 (컴컴퓨터 과학)]] 참조. ; {{anchor|renderer|Renderer}} 렌더러 {{English term|renderer}} (1) : <span lang="en" dir="ltr" class="mw-content-ltr">a function to convert a ZObject to a string. The opposite of [[#parser|parser]]. (formerly called "linearizer")</span> ; <span lang="en" dir="ltr" class="mw-content-ltr">renderer</span> {{English term|renderer}} (2) : [[#natural_language|자연어]]에 대한 [[#Content|콘텐츠]]와 식별자를 입력으로 가져오고 해당 자연어의 텍스트를 출력으로 반환하고, [[#Lexeme|어휘소]]의 지식을 사용하여 콘텐츠를 구체적인 텍스트로 나타내는 [[#Function|함수]]입니다. : {{TakeNote}}<span lang="en" dir="ltr" class="mw-content-ltr">This is a future feature, and the meaning of the term "renderer" in the {{Pg|:m:Abstract Wikipedia/Historic proposal|original proposal}}; this term collides with the current usage of "renderer", so it may be renamed in the future.</span> ; {{anchor|reify}} 구체화 {{English term|reify}} : 객체를 구성 부분으로 분해하여 부분에 개별적으로 접근할 수 있도록 하는 함수; 위키백과에서 [[w:en:Reification (computer science)|구체화]] 참조; [[phab:T261474]] 참조. ; {{anchor|REPL}} REPL {{English term|REPL}} : Read / Eval / Print - Loop, 입력을 받아 평가하고 결과를 표시하는 명령 줄 인터페이스; 위키백과의 [[w:ko:REPL|REPL]] 참조; [[Special:MyLanguage/Wikifunctions:Function model#REPL|함수 모델]] 참조. == S == ; {{anchor|schemata}} <span lang="en" dir="ltr" class="mw-content-ltr">schemata</span> {{English term|schemata}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#function schemata|function schemata]].</span> ; {{anchor|serialization|Serialization|serialisation|Serialisation}} 직렬화 {{English term|serialization}} : [[#JSON|JSON]]에서 Z객체를 표현하는 방법; [[#canonical|표준형]], [[#normal|정규형]]도 참조. ; {{anchor|snak|Snak}}<span lang="en" dir="ltr" class="mw-content-ltr">snak</span> {{English term|snak}} : <span lang="en" dir="ltr" class="mw-content-ltr">In the [[:mw:Special:MyLanguage/Wikibase/DataModel|Wikibase data model]], a snak is the smallest unit of a statement, linking a property to either a value, “no value”, or “some value.”</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example [[#statement|statement]] for {{Q|Q937}} with 3 snaks:</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Main snak:</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P26}} → Value: {{Q|Q76346}}</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Qualifier snak (adds context):</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P580}} → Value: 1903</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Reference snak (supports the claim):</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P248}} → Value: {{Q|Q23833686}}</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Resulting statement (in words): “Albert Einstein’s spouse was Mileva Marić, starting in 1903, as stated in the Catalog of the German National Library.”</span> ; {{anchor|statement|Statement}} 서술 {{English term|statement}} : <span class="mw-translate-fuzzy">[[#Wikidata|위키데이터]]의 지식 기반에서 [[#Item|항목]]에 대한 지식을 제공하는 데 사용됩니다. 위키데이터 용어집의 [[:d:Special:MyLanguage/Wikidata:Glossary#Statement|서술]] 참조.</span> ; {{anchor|string}} 문자열 {{English term|string}} : 일련의 문자. ; {{anchor|sum type|Sum type}} 합계 유형 {{English term|sum type}} : 구성 유형의 인스턴스를 가질 수 있는 유형; 위키백과의 [[w:en:Sum type|집계 유형]] 참조. [[Special:MyLanguage/Wikifunctions:Function model#Zx/Sum_types|함수 모델]] 참조. == T == ; {{anchor|template}} 틀 {{English term|template}} : <span class="mw-translate-fuzzy">[[#renderer|렌더러]]를 자리 표시자가 산재된 텍스트 또는 "슬롯"으로 지정하는 방법은 [[#constructor|생성자]]의 데이터, 함수 계산 또는 다른 틀의 내용으로 채울 수 있습니다. 틀 구문에 대한 자세한 내용은 [[:m:Special:MyLanguage/Abstract Wikipedia/Template Language for Wikifunctions|위키함수용 틀 언어]] 문서를 참조하세요.</span> ; {{anchor|tester|Tester}} 테스터 {{English term|tester}} : 주어진 [[#ZFunction|Z함수]]가 정확하게 일을 하고 있는지 자동으로 결정하는 방법. [[#function|함수]]에는 일반적으로 여러 테스터가 있으며, 각 테스터는 함수에 대한 일부 입력을 지정하고 주어진 입력에 대한 출력이 충족되어야합니다. 예를 들어, "케이스 제목(title case)" 함수의 테스터에는 다음이 포함될 수 있습니다: "abc"는 "Abc"가 되어야합니다; "war and peace"는 "War and Peace"가 되어야합니다; "война и мир"는 "Война и мир"가 되어야합니다; "123"은 "123"으로 유지되어야합니다. ; {{anchor|transient|Transient}} 일시적 {{English term|transient}} : [[#persistent|영속적]]의 반대. ; {{anchor|type|Type}} 유형 {{English term|type}} : 객체의 유형은 주어진 객체를 해석하고 이해하는 방법과 객체로 수행할 수 있는 작업을 알려줍니다. 예를 들어 값이 "2023"인 객체가 있는 경우 유형이 정수인지, 연도인지 또는 문자열인지에 따라 해당 객체를 다르게 이해합니다. 모든 객체는 "실제 세계에 있는 것"을 나타냅니다. 정수 2023은 2023년과 다릅니다. 유형은 주어진 객체를 해석하는 방법을 알려주므로 실제 세계에서 어떤 것을 참조하는지 알 수 있습니다. 기술적으로는 해당 유형의 객체가 구성되는 방식과 해당 유형의 유효한 객체가 되기 위해 충족해야 하는 조건을 정의합니다. 유형은 Z객체의 유효성을 검사하는 [[#Function|함수]]를 제공하여 [[#ZObject|Z객체]]가 이 유형의 유효한 인스턴스가 되는 조건을 정의합니다. 유형은 Z객체 자체이므로 [[#Wikifunctions|위키함수]]의 기여자는 새로운 유형을 만들 수 있습니다. ; {{anchor|type converter}} <span lang="en" dir="ltr" class="mw-content-ltr">type converter</span> {{English term|type converter}} : <span lang="en" dir="ltr" class="mw-content-ltr">A script written in some programming language (such as JavaScript), taking a native object (such as BigInt), and returning a JSON object representing the corresponding ZObject; or ''vice versa''.</span> ; {{anchor|typed list|Typed List}} <span lang="en" dir="ltr" class="mw-content-ltr">typed list</span> {{English term|typed list}} : <span lang="en" dir="ltr" class="mw-content-ltr">A typed list is a [[#list|list]] in which all members of the list are of a specific, predefined [[#type|type]]. For example, a typed list of [[#string|strings]] is a list in which all members of the list are strings. A typed list takes one argument: the type that all the members of the list have to be an instance of. Typed lists are probably the most widely used [[#generic type|generic type]].</span> == V == ; {{anchor|value}} 값 {{English term|value}} : 다른 Z객체의 [[#key|키]]와 연관된 문자열 또는 [[#ZObject|Z객체]]. ; {{anchor|validation|Validation}} <span lang="en" dir="ltr" class="mw-content-ltr">validation</span> {{English term|validation}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#validator|validator]].</span> ; {{anchor|validator|Validator}} 검증자 {{English term|validator}} : <span class="mw-translate-fuzzy">Z객체를 인수로 사용하고 발견된 오류 목록을 반환하는 함수.</span> == W == ; {{anchor|wiki|Wiki}} 위키 {{English term|wiki}} : [[#page|페이지]]를 쉽고 공동으로 편집 할 수 있는 웹 사이트. ; {{anchor|Wikidata}} 위키데이터 {{English term|Wikidata}} : 공동으로 편집된 자유 지식 기반인 [[#Wikimedia_Foundation|위키미디어 재단]]의 프로젝트; [[:m:Special:MyLanguage/Wikidata|위키데이터]] 참조. ; {{anchor|Wikifunctions}}{{anchor|Wikilambda}} 위키함수 {{English term|Wikifunctions}} : [[#Wikimedia_Foundation|위키미디어 재단]]의 새로운 프로젝트; 무료이고 공동으로 개발하며 유지 관리하는 [[#Function|함수]] 카탈로그. {{Pg|:m:Abstract Wikipedia/Historic proposal|원래 제안}}에서 처음에는 위키람다로 알려졌습니다(이 이름은 현재 위키람다 확장에 사용됨). ; {{anchor|WikiLambda}} 위키람다 {{English term|WikiLambda}} : 프로젝트를 구동하는 데 사용되는 소프트웨어, [[mw:Special:MyLanguage/Extension:WikiLambda|확장:위키람다]]. ; {{anchor|WikiLambda system}} 위키람다 시스템 {{English term|WikiLambda system}} : <span lang="en" dir="ltr" class="mw-content-ltr">an automated system account that is a key part of the WikiLambda extension. See [[User:WikiLambda system]] for its current function.</span> ; {{anchor|WMF|Wikimedia_Foundation}} 위키미디어 재단 {{English term|Wikimedia Foundation}} : 위키미디어 운동을 지원하는 조직; [[:m:Special:MyLanguage/Wikimedia Foundation|위키미디어 재단]] 참조. ; {{anchor|Wikipedia}} 위키백과 {{English term|Wikipedia}} : [[#Wikimedia_Foundation|위키미디어 재단]]의 프로젝트, 공동으로 편집하는 자유 백과사전, [[:m:Special:MyLanguage/Wikipedia|위키백과]] 참조. ; 위키백과, 추상 {{English term|Wikipedia, Abstract}} : [[#Abstract_Wikipedia|추상 위키백과]] 참조. ; 위키백과, 다국어 {{English term|Wikipedia, multilingual}} : [[#multilingual_Wikipedia|다국어 위키백과]] 참조. == Z == ; {{anchor|ZID|ZIDs}} ZID {{English term|ZID}} : 문자 Z로 시작하고 뒤에 자연수가 오는 ID. [[#persistent|영구]] [[#ZObject|Z객체]]를 식별하는 데 사용됩니다. ; {{anchor|zfunction|ZFunction}} Z함수 {{English term|ZFunction}} : [[#evaluator|평가자]]를 통해 사용할 수 있는 특정 [[#function|함수]]를 설명하는 [[#Wikifunctions|위키함수]]의 위키 문서입니다. 각 Z함수는 하나 이상의 [[#implementation|구현]]에 의해 코드에서 실현 될 수 있으며, 상기 구현은 하나 이상의 [[#tester|테스터]] Z함수에 의해 올바른 것으로 검증될 수 있습니다. ; {{anchor|ZKey}} Z키 {{English term|ZKey}} : 특정 [[#type |유형]]에 대한 [[#key|키]]를 정의하는 [[#ZObject|Z객체]]. ; {{anchor|ZList}} Z리스트 {{English term|ZList}} : 다른 Z객체의 순서가 지정된 시퀀스에 대한 [[#ZObject|Z객체]]. ; {{anchor|ZObject}} Z객체 {{English term|ZObject}} : [[#Wikifunctions|위키함수]]의 모든 항목은 Z객체입니다. 위키함수에 저장된 Z객체는 [[#ZID|ZID]]를 가지며 [[#Constructor|생성자]]와 [[#Function|함수]], [[#Type|유형]] 등과 같은 다양한 유형이 될 수 있습니다. Z객체는 [[#Key|키]]/[[#Value|값]] 쌍 집합으로 구성되며 각 키는 Z객체 당 한 번만 나타나고 값은 Z객체입니다. ; {{anchor|ZUnit}} ZUnit {{English term|ZUnit}} : [[:w:en:Unit type|단위 유형]]을 나타내는 [[#ZObject|ZObject]]입니다. [[Category:Glossary| {{#translation:}}]] rwh3jeo4lazk6knu9ui6bnsbagxutyt 275515 275513 2026-05-16T12:22:13Z Tensama0415 73696 275515 wikitext text/x-wiki <noinclude><languages/> <!--<nowiki>(nowiki tags are so that the translate extension doesn't try to translate the TERM and DEFINITION in this boilerplate). Use this boilerplate for a new term: ; {{anchor|term|Term}} <translate>term</translate> {{English term|term}} : ''Definition verification needed'' : <translate>definition</translate> Notes: 1. Omit the "Definition verification" if you're sure that your definition is correct. 2. You can add several values for anchor, if it has spelling or capitalization variants; see the documentation for Template:Anchor and examples in other terms. </nowiki>--></noinclude> {{see also|wikt:en:Appendix:Glossary}} [[Wikifunctions talk:Glossary|토론 페이지]]에서 용어를 요청하거나 더 많은 용어를 추가하고 정의를 개선하세요. {|class="toccolours" style="margin:.2em auto;padding:.2em .5em;text-align:center" dir="ltr" lang="en" |- |style="padding:0;width:100%"|{{CompactTOC}} |} == A == ; {{anchor|abstract|Abstract}} 추상 {{English term|abstract}} : [[#natural_language|특정한 자연어]]가 아니라 그로부터의 추상화; 자연어 텍스트, 문장 또는 구의 의미에 대한 표기법을 제공하는 것을 목표로합니다. [[#concrete|구상]]의 반대. ; {{anchor|abstracttext|AbstractText}} AbstractText {{English term|AbstractText}} : [[#Wikifunctions|위키함수]] 아이디어의 프로토 타입 [https://github.com/google/abstracttext 구현]. ; {{anchor|abstract_article}} <span lang="en" dir="ltr" class="mw-content-ltr">Abstract Article</span> {{English term|abstract article}} : <span lang="en" dir="ltr" class="mw-content-ltr">A page in the main namespace of [[#abstract_Wikipedia|Abstract Wikipedia]]; a page that is similar to a Wikipedia article, but that is [[#abstract|abstract]]. The opposite of [[#concrete_article|concrete article]]. ("Abstract" is an adjective here; it ''doesn't'' mean "a summary of an article".)</span> ; {{anchor|abstract_content}} 추상 콘텐츠 {{English term|abstract content}} : [[#Content|콘텐츠]] 참조. ; {{anchor|abstract_Wikipedia|Abstract_Wikipedia}} 추상 위키백과 {{English term|Abstract Wikipedia}} : [[#local_Wikipedia|로컬 위키백과]]에서 [[#natural_language|자연어]]로 [[#article|문서]]를 [[#Renderer|렌더링]]하는 데 사용할 수 있는 모든 [[#Content|콘텐츠]]의 예비 이름; 현재 해당 [[#Item|항목]] 옆에 [[#Wikidata|위키데이터]]에 존재하도록 제안되었지만 [[#development_project|개발 프로젝트]]의 [[#Part_P2|Part P2]] 이전에 논의될 것입니다. ; {{anchor|alias}} 별칭 {{English term|alias}} : 객체를 찾는 데 가장 먼저 사용되는 객체의 대체 레이블입니다. ; {{anchor|argument}} 인수 {{English term|argument}} : <span lang="en" dir="ltr" class="mw-content-ltr">an input given to a [[#function call|function call]].</span> ; {{anchor|argument reference}} <span lang="en" dir="ltr" class="mw-content-ltr">argument reference</span> {{English term|argument reference}} : <span lang="en" dir="ltr" class="mw-content-ltr">a [[#reference|reference]] to one of the supplied arguments within a [[#composition|composition]].</span> ; {{anchor|array}} <span lang="en" dir="ltr" class="mw-content-ltr">array</span> {{English term|array}} : <span lang="en" dir="ltr" class="mw-content-ltr">Many programming languages have an "array" type. The counterparts in Wikifunctions are [[#list|list]] and [[#typed list|typed list]]. See also [[#Benjamin array|Benjamin array]].</span> ; {{anchor|article|Article}} 문서 {{English term|article}} : <span class="mw-translate-fuzzy">일반적으로 [[#Wikipedia|위키백과]]의 한 항목을 나타내는 위키백과의 기본 이름공간에 있는 문서.</span> == B == ; {{anchor|Benjamin array}} <span lang="en" dir="ltr" class="mw-content-ltr">Benjamin array</span> {{English term|Benjamin array}} : <span lang="en" dir="ltr" class="mw-content-ltr">a way to denote [[#typed list|typed list]] proposed by Benjamin Degenhart, where a typed list is stored as a JSON list whose first element denotes the type. This is in contrast with the previous proposed schema, which uses LISP-style singly-linked lists, in which the type must be stored once in each node.</span> ; {{anchor|boolean|Boolean}} <span lang="en" dir="ltr" class="mw-content-ltr">boolean</span> {{English term|boolean}} : <span lang="en" dir="ltr" class="mw-content-ltr">a value that can have 2 states, usually denoted true and false.</span> ; {{anchor|built-in|builtin}} 내장된 {{English term|built-in}} : 평가자가 제공하고 위키 인터페이스를 통해 편집할 수없는 함수의 기본 구현. == C == ; {{anchor|call}} 호출 {{English term|call}} : [[#function call|함수 호출]] 참조. 영어에서는 [[#invoke|인보크(invoke) 또는 인보케이션(invocation)]]이라는 용어도 사용할 수 있습니다. ; {{anchor|canonical|canonicalized|canonicalised}} 표준형의 {{English term|canonical, canonicalized, canonicalised}} : 구체적이고 덜 장황하며 따라서 [[#JSON|JSON]]으로 [[#ZObject|Z객체]]를 표현하는 더 읽기 쉬운 방법입니다. Z객체는 위키함수에 저장되는 일반적인 표현입니다. 이것은 [[#normal|정규형]]과 반대입니다. ; {{anchor|character}} 문자 {{English term|character}} : 문자열의 구성 요소인 유니 코드로 정의된 문자; 문자는 여러 바이트(또는 8진수)로 구성 될 수 있습니다. ; {{anchor|claim|Claim}} <span lang="en" dir="ltr" class="mw-content-ltr">claim</span> {{English term|claim}} : <span lang="en" dir="ltr" class="mw-content-ltr">In the [[:d:Special:MyLanguage/Wikidata:Glossary#Claim|Wikibase data model]], a claim is a main snak plus optional qualifiers, expressing an assertion about an entity (without references or rank).</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example: Entity: Albert Einstein</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Claim: Spouse = Mileva Marić, starting in 1903</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Main snak: P26 (spouse) → Q937 (Mileva Marić)</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Qualifier snak: P580 (start time) → 1903</span> : <span lang="en" dir="ltr" class="mw-content-ltr">→ “Albert Einstein’s spouse was Mileva Marić, starting in 1903.”</span> : <span lang="en" dir="ltr" class="mw-content-ltr">The claim can later be turned into a statement by adding a reference and rank.</span> ; {{anchor|composition}} 컴포지션 {{English term|composition}} : 다른 함수의 조합에 의해 구현이 제공되는 함수의 구현 형태; [[Special:MyLanguage/Wikifunctions:Function model#Composition|함수 모델]] 참조. ; {{anchor|composition notation}} 컴포지션 표기법 {{English term|composition notation}} : 컴포지션(composition)에 관한 읽기 쉬운 표기법; [[Special:MyLanguage/Wikifunctions:Function model#Composition|함수 모델]] 참조. ; {{anchor|concrete|Concrete}} 구상 {{English term|concrete}} : [[#natural_language|특정 자연어]]에서. [[#abstract|추상]]의 반대. ; {{anchor|concrete_article}} <span lang="en" dir="ltr" class="mw-content-ltr">concrete article</span> {{English term|concrete article}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#article|article]]. The opposite of [[#abstract_article|Abstract Article]].</span> ; {{anchor|cons}} 단점 {{English term|cons}} : 상단에 요소를 추가하여 새로운 리스트를 생성하는 함수; [[phab:T261474]]을 참조. 위키백과의 [[w:cons|단점]]을 참조하세요. ; {{anchor|constructor|Constructor}} 생성자 {{English term|constructor}} : <span class="mw-translate-fuzzy">[[#Content|콘텐츠]]의 [[#abstract|추상]] 빌딩 블록; 생성자는 단일 구문 또는 문장 구조의 의미를 포착하는 것을 목표로 하며 종종 다른 생성자를 취할 수있는 슬롯을 가지고 있으며 다른 생성자의 슬롯을 채우는 값으로 자체적으로 사용될 수 있습니다.</span> ; {{anchor|Content}}<!--do not add |content to the anchor, it is used by MediaWiki--> 콘텐츠, 추상 콘텐츠 {{English term|content, abstract content}} : [[#Constructor|생성자]]에서 조립된 텍스트 또는 텍스트 조각의 추상 표현. 기술적으로는 인스턴스화 된 생성자. 최상위 생성자는 전체 [[#article|문서]]를 나타내는 데 사용되며 [[#Abstract_Wikipedia|추상 위키백과]]에 저장되지만 내용은 문장이나 구에 대한 것일 수도 있습니다. 추상 콘텐츠라고도 합니다. ; {{anchor|curry}} curried, curry, currying {{English term|curried, curry, currying}} : 커리 함수는 여러 인수를 각각 단일 인수가 있는 일련의 함수로 변환한 함수입니다. 이 기술은 미국 수학자 [[:w:en:Haskell하스켈 카레]]의 이름을 따서 명명되었습니다. 위키백과의 [[:w:en:Currying|커링]]을 참조하세요. == D == ; {{anchor|deserialization|Deserialization|deserialisation|Deserialisation}} 역직렬화 {{English term|deserialization}} : [[#serialization|직렬화]]의 반대. ; {{anchor|development_project|Development_project}} 개발 프로젝트 {{English term|development project}} : [[#Wikifunctions|위키함수]] 및 [[#Abstract_Wikipedia|추상 위키백과]] 개발 프로젝트; [[:m:Special:MyLanguage/Abstract Wikipedia/Plan|추상 위키백과 계획]] 참조. ; {{anchor|display function}} <span lang="en" dir="ltr" class="mw-content-ltr">display function</span> {{English term|display function}} : <span lang="en" dir="ltr" class="mw-content-ltr">a synonym of [[#renderer|renderer]]. For example, a function that converts a [[#type|type]] into a string that users can understand, such as converting a Number 123456 to "123,456" in (International) English, "1,23,456" in Indian English, "123.456" in French, etc., or converting the Date '2024','03','12' to '2024-03-12', and so on.</span> ; {{anchor|documentation}} 문서화 {{English term|documentation}} : 사람이 읽을 수 있는 객체를 설명하는 텍스트. == E == ; {{anchor|eney|eneyjj}} eneyj {{English term|eneyj}} :# [[#Wikifunctions|위키함수]]의 프로토타입 모델; :# [[#abstracttext|abstracttext]]에 제공된 해당 모델의 [[#evaluator|평가자]]에 대한 자바 스크립트 구현. ; {{anchor|error|Error}} 에러 {{English term|error}} : <span class="mw-translate-fuzzy">인스턴스가 평가 또는 검증의 문제를 나타내는 유형; [[Special:MyLanguage/Wikifunctions:Function model#Z5/Errors|함수 모델]] 참조.</span> ; {{anchor|evaluation|Evaluation}} <span lang="en" dir="ltr" class="mw-content-ltr">evaluation</span> {{English term|evaluation}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#evaluator|evaluator]].</span> ; {{anchor|evaluator|Evaluator}} 평가자 {{English term|evaluator}} : [[#ZObject|Z객체]]를 가져와 평가하는 소프트웨어, 즉 [[#Function|함수]]를 실행하고 결과를 반환하는 소프트웨어. 우리는 여러 평가자의 개발을 계획합니다. 평가자는 브라우저와 [[#Wikimedia_Foundation|위키미디어 재단]]의 서버, 클라우드, 모바일 장치의 앱 또는 기타 장소에서 구현 및 실행할 수 있습니다. [[#executor|실행자]] 및 [[#orchestrator|오케스트레이터]]와 비교합니다. ; {{anchor|execution|Execution}} <span lang="en" dir="ltr" class="mw-content-ltr">execution</span> {{English term|execution}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#executor|executor]].</span> ; {{anchor|executor|Executor|executors|Executors}} 실행자 {{English term|executor}} : 대중에게 노출되지 않는 일련의 내부 서비스 중 하나. [[#Orchestrator|오케스트레이터]]에 의해서만 호출 될 수 있습니다. 특정 프로그래밍 언어로 네이티브 코드를 실행합니다. 루아에 대한 하나의 실행 프로그램, 자바 스크립트에 대한 실행 프로그램, 파이썬에 대한 실행 프로그램 등이 있습니다. [https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-evaluator#executors 서비스 문서]를 참조. [[#evaluator|평가자]] 및 [[#orchestrator|오케스트레이터]]와 비교합니다. == F == ; {{anchor|function|Function}} 함수 {{English term|function}} : 일부 입력을 받아 출력을 반환하는 계산에 관한 사양; 위키백과의 [[w:ko:함수 (프로그래밍)|함수 (프로그래밍)]] 참조. ; {{anchor|function call|Function call}} 함수 호출 {{English term|function call}} : 함수 호출은 함수와 함수에 필요한 인수로 구성된 Z객체이며 다른 Z객체로 평가 될 수 있습니다. 영어에서는 "인보크(invoke)"라는 용어도 사용할 수 있습니다. ; {{anchor|function evaluator}} <span lang="en" dir="ltr" class="mw-content-ltr">function evaluator</span> {{English term|function evaluator}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#evaluator|evaluator]].</span> ; {{anchor|function executor}} <span lang="en" dir="ltr" class="mw-content-ltr">function executor</span> {{English term|function executor}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#executor|executor]].</span> ; {{anchor|function model}} 함수 모델 {{English term|function model}} : [[Special:MyLanguage/Wikifunctions:Function model|함수 모델]] 참조. ; {{anchor|function orchestrator}} <span lang="en" dir="ltr" class="mw-content-ltr">function orchestrator</span> {{English term|function orchestrator}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#orchestrator|orchestrator]].</span> ; {{anchor|function schemata}} <span lang="en" dir="ltr" class="mw-content-ltr">function schemata</span> {{English term|function schemata}} : <span lang="en" dir="ltr" class="mw-content-ltr">a set of pre-defined ZObjects used in [[#orchestrator|orchestrator]] and [[#evaluator|evaluator]]. The [[#WikiLambda system|WikiLambda system account]] also populates pre-defined ZObjects on-wiki from function schemata.</span> ; {{anchor|functional}} 함수형 {{English term|functional}} : "순수 함수형"의 줄임말로, 그러한 함수의 [[#evaluation|평가]]는 부작용이 없고 결정론적입니다. 즉, 항상 동일합니다; 위키백과의 [[w:en:Purely functional programming|순수 함수형 프로그래밍]] 참조; [[Special:MyLanguage/Wikifunctions:Function model#non-functional|함수 모델]] 참조. == G == ; {{anchor|generic type}} 제네릭 유형 {{English term|generic type}} : 함수 호출의 [[#evaluation|평가]]에 의해 생성 된 유형. == I == ; {{anchor|identity|Identity}} 식별 {{English term|identity}} : 유형의 식별은 유형으로 평가되는 (특정) 함수의 인스턴스입니다. 단순 유형의 경우, 유형 자체에 대한 참조입니다. ; {{anchor|implementation|Implementation}} 구현 {{English term|implementation}} : [[#function|함수]]를 실행하는 특별한 방법. 구현은 특정 프로그래밍 언어로 된 코드 조각일 수도 있고 [[#evaluator|평가자]]에 "내장 된" 기능을 참조하거나 다른 함수에 대한 호출을 결합할 수도 있습니다. 함수에는 많은 [[#composition|구현]]이 있을 수 있으며 모두 동일해야 합니다. "[[#ZFunction|Z함수]] 구현"의 약자입니다. ; {{anchor|instance}} 인스턴스 {{English term|instance}} : 모든 Z객체는 해당 유형의 인스턴스입니다. ; {{anchor|invoke}} 인보크 {{English term|invoke}} : 영어로 [[#call|호출]]의 동의어. [[#function call|함수 호출]]을 참조하세요. ; {{anchor|item|Item}} 항목 {{English term|item}} : [[#Wikidata|위키데이터]]의 지식 기반에 있는 항목; 위키데이터 용어집의 [[:d:Wikidata:Glossary#Item|항목]] 참조. == J == ; {{anchor|JSON}} JSON {{English term|JSON}} : <span class="mw-translate-fuzzy">널리 사용되는 데이터 직렬화; 위키백과의 [[w:en:JSON|JSON]]을 참조.</span> == K == ; {{anchor|key|Key}} 키 {{English term|key}} : 문자 K와 자연수로 끝나고 선택적으로 앞에 [[#ZID|ZID]]가 오는 문자열. 키는 일반적으로 [[#Type|유형]] 또는 [[#Function|함수]]에 대한 [[#Wikifunctions|위키함수]]에서 정의되며 [[#ZObject|Z객체]]를 강화하는 데 사용됩니다. == L == ; {{anchor|label}} 레이블 {{English term|label}} : Z객체를 식별하기 위해 주어지는 이름. 일반 텍스트만 가능. ; {{anchor|lexeme|Lexeme}} 어휘소 {{English term|lexeme}} : 대략적인 단어에 대한 사전 지식을 저장하는 [[#Wikidata|위키데이터]]의 항목; 위키데이터 용어집의 [[d:Wikidata:Glossary#Lexeme|어휘소]] 항목 참조. ; {{anchor|linearizer|Linearizer}} linearizer {{English term|linearizer}} : <span class="mw-translate-fuzzy">Z객체를 문자열로 변환하는 함수. [[$parser|파서]]의 반대입니다.</span> ; {{anchor|list|List}} 리스트 {{English term|list}} : 정렬된 엔티티에서 임의의 수의 인스턴스를 그룹화하는 데이터 유형; 위키백과의 [[w:en:List (abstract data type)|리스트 (추상 데이터 유형)]]을 참조하세요. ; {{anchor|literal}} 리터럴 {{English term|literal}} : Z객체가 아닌 값. 현재 유일하게 허용되는 리터럴은 문자열입니다. ; {{anchor|local_Wikipedia|Local_Wikipedia}} 로컬 위키백과 {{English term|local Wikipedia}} : 히브리어 위키백과, 일본어 위키백과 또는 이탈리아어 위키백과와 같은 특정 언어로 된 [[#Wikipedia|위키백과]]. == M == ; {{anchor|Multlingual_Wikipedia|multilingual_Wikipedia}} 다국어 위키백과 {{English term|multilingual Wikipedia}} : [[#local_Wikipedia|로컬 위키백과]]가 [[#Abstract_Wikipedia|추상 위키백과]]의 [[#Content|콘텐츠]]를 [[#Renderer|렌더링]]하여 자신의 언어로 더 포괄적이고 최신이며 알맞은 위키백과를 가질 수 있도록하는 구조; [[:m:Special:MyLanguage/Abstract Wikipedia/Architecture|추상 위키백과 구조]] 참조. == N == ; {{anchor|natural_language|Natural_language}} 자연어 {{English term|natural language}} : 영어와 타갈로그어 또는 스와힐리어와 같은 넓은 의미의 특정 자연어; 위키백과의 [[w:en:Natural language|자연어]]를 참조하세요. ; {{anchor|normal|Normal|normalized|Normalized|normalised}} 정규형의, 정규형 {{English term|normal}} : [[#JSON|JSON]]으로 [[#ZObject|Z객체]]를 표현하는 확장되고 쉽게 처리 가능하며 매우 균일한 방법입니다. 이것은 [[#canonical|표준형]]과 반대입니다. ; {{anchor|nothing|Nothing}} nothing {{English term|nothing}} : 인스턴스를 가질 수 없는 데이터 유형; 위키백과의 [[w:en:Bottom type|바닥 유형]] 참조. == O == ; {{anchor|object|Object}} 객체 {{English term|object}} :# 자바 스크립트 또는 JSON에서 객체는 기본적으로 연관 배열입니다. 위키백과의 [[w:ko:연관 배열|연관 배열]]을 참조하세요. :# <span lang="en" dir="ltr" class="mw-content-ltr">In Wikifunctions, synonym of [[#ZObject|ZObject]].</span> ; {{anchor|orchestration|Orchestration}} <span lang="en" dir="ltr" class="mw-content-ltr">orchestration</span> {{English term|orchestration}} :<span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#orchestrator|orchestrator]].</span> ; {{anchor|orchestrator|Orchestrator}} 오케스트레이터 {{English term|orchestrator}} : <span class="mw-translate-fuzzy">[[#ZObject|Z객체]]를 가져와 [[#Evaluator|평가]]된 버전을 반환하는 서비스입니다. 이를 위해 필요한 다른 Z객체, 일부 함수 호출을 평가하기위한 [[#Executor|실행자]] 및 [[#Wikidata|위키데이터]]와 같은 기타 서비스에 대한 위키를 호출합니다. [https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-orchestrator#wikifunctions-function-orchestrator 서비스 문서]를 참조하세요. [[#evaluator|평가자]] 및 [[#executor|실행자]]와 비교합니다.</span> == P == ; {{anchor|page|Page}} 문서 {{English term|page}} : <span class="mw-translate-fuzzy">[[#wiki|위키]]는 독립적으로 편집할 수 있는 여러 개별 페이지로 구성됩니다.</span> ; {{anchor|parser|Parser}} 파서 {{English term|parser}} : <span class="mw-translate-fuzzy">문자열을 Z객체로 변환하는 함수. [[$linearizer|linearizer]]의 반대.</span> ; {{anchor|pair|Pair}} 짝 {{English term|pair}} : 특정 (임의의) 유형의 두 Z객체를 포함하는 복합 Z객체. ; {{anchor|part_P1|Part_P1}} 파트 P1 {{English term|Part P1}} : [[#Wikifunctions|위키함수]] 생성을 다루는 [[#development_project|개발 프로젝트]]의 일부입니다. 그것은 프로젝트의 시작 부분에서 시작하여 평생 동안 계속됩니다. [[:m:Special:MyLanguage/Abstract Wikipedia/Tasks#Part P1: Wikifunctions|파트 P1: 위키함수]]를 참조하세요. ; {{anchor|part_P2|Part_P2}} 파트 P2 {{English term|Part P2}} : [[#Abstract_Wikipedia|추상 위키백과]] 생성을 다루는 [[#development_project|개발 프로젝트]]의 일부입니다. 프로젝트에서 약 1년 후에 시작되어 이 기간의 후반기 동안 계속됩니다. [[:m:Special:MyLanguage/Abstract Wikipedia/Tasks#Part P2: Abstract Wikipedia|파트 P2: 추상 위키백과]] 참조. ; {{anchor|persistent|Persistent}} 영속적, 영속 {{English term|persistent}} : [[#ZID|ZID]]가 있고 위키의 자체 페이지가 있는 [[#ZObject|Z객체]] 대부분의 영속 Z객체에는 ZID가 없는 Z객체인 [[#value|값]]이 포함되어 있으므로 영속적이지 않습니다. ; {{anchor|property|Property}} 속성 {{English term|property}} : [[#Wikidata|위키데이터]]의 지식 기반에서 [[#Item|항목]]에 대해 [[#Statement|서술]]하는 데 사용됩니다. 위키데이터 용어집에서 [[:d:Wikidata:Glossary#Property|속성]] 참조. == Q == ; {{anchor|quote|Quote}} 인용 {{English term|quote}} : 평가되지는 않지만 그대로 유지되는 데이터 구조. ; {{anchor|QID}} QID {{English term|QID}} : [[#Wikidata|위키데이터]] 항목의 식별자로, 문자 "Q" 뒤에 정수가 오는 것으로 구성됩니다. == R == ; {{anchor|reading function}} <span lang="en" dir="ltr" class="mw-content-ltr">reading function</span> {{English term|reading function}} : <span lang="en" dir="ltr" class="mw-content-ltr">a synonym of [[#parser|parser]]. A function that converts user text input from a string into a given Type. For example, converting the String "123456" to the Number '123456', or the string "2024-03-12" to the Date '2024', '03', '12'.</span> ; {{anchor|reference|Reference}} 참조 {{English term|reference}} : 기본 객체를 나타내는 ID입니다. 예를 들어, 문자열 "Z11"은 유형 Z11/단어 언어 텍스트를 나타냅니다. : {{TakeNote}}이 용어는 위키데이터와는 완전히 다른 의미를 가지고 있습니다. 위키백과의 [[w:en:Reference (computer science)|참조 (컴컴퓨터 과학)]] 참조. ; {{anchor|renderer|Renderer}} 렌더러 {{English term|renderer}} (1) : <span lang="en" dir="ltr" class="mw-content-ltr">a function to convert a ZObject to a string. The opposite of [[#parser|parser]]. (formerly called "linearizer")</span> ; <span lang="en" dir="ltr" class="mw-content-ltr">renderer</span> {{English term|renderer}} (2) : [[#natural_language|자연어]]에 대한 [[#Content|콘텐츠]]와 식별자를 입력으로 가져오고 해당 자연어의 텍스트를 출력으로 반환하고, [[#Lexeme|어휘소]]의 지식을 사용하여 콘텐츠를 구체적인 텍스트로 나타내는 [[#Function|함수]]입니다. : {{TakeNote}}<span lang="en" dir="ltr" class="mw-content-ltr">This is a future feature, and the meaning of the term "renderer" in the {{Pg|:m:Abstract Wikipedia/Historic proposal|original proposal}}; this term collides with the current usage of "renderer", so it may be renamed in the future.</span> ; {{anchor|reify}} 구체화 {{English term|reify}} : 객체를 구성 부분으로 분해하여 부분에 개별적으로 접근할 수 있도록 하는 함수; 위키백과에서 [[w:en:Reification (computer science)|구체화]] 참조; [[phab:T261474]] 참조. ; {{anchor|REPL}} REPL {{English term|REPL}} : Read / Eval / Print - Loop, 입력을 받아 평가하고 결과를 표시하는 명령 줄 인터페이스; 위키백과의 [[w:ko:REPL|REPL]] 참조; [[Special:MyLanguage/Wikifunctions:Function model#REPL|함수 모델]] 참조. == S == ; {{anchor|schemata}} <span lang="en" dir="ltr" class="mw-content-ltr">schemata</span> {{English term|schemata}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#function schemata|function schemata]].</span> ; {{anchor|serialization|Serialization|serialisation|Serialisation}} 직렬화 {{English term|serialization}} : [[#JSON|JSON]]에서 Z객체를 표현하는 방법; [[#canonical|표준형]], [[#normal|정규형]]도 참조. ; {{anchor|snak|Snak}}<span lang="en" dir="ltr" class="mw-content-ltr">snak</span> {{English term|snak}} : <span lang="en" dir="ltr" class="mw-content-ltr">In the [[:mw:Special:MyLanguage/Wikibase/DataModel|Wikibase data model]], a snak is the smallest unit of a statement, linking a property to either a value, “no value”, or “some value.”</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example [[#statement|statement]] for {{Q|Q937}} with 3 snaks:</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Main snak:</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P26}} → Value: {{Q|Q76346}}</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Qualifier snak (adds context):</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P580}} → Value: 1903</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Reference snak (supports the claim):</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P248}} → Value: {{Q|Q23833686}}</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Resulting statement (in words): “Albert Einstein’s spouse was Mileva Marić, starting in 1903, as stated in the Catalog of the German National Library.”</span> ; {{anchor|statement|Statement}} 서술 {{English term|statement}} : <span class="mw-translate-fuzzy">[[#Wikidata|위키데이터]]의 지식 기반에서 [[#Item|항목]]에 대한 지식을 제공하는 데 사용됩니다. 위키데이터 용어집의 [[:d:Special:MyLanguage/Wikidata:Glossary#Statement|서술]] 참조.</span> ; {{anchor|string}} 문자열 {{English term|string}} : 일련의 문자. ; {{anchor|sum type|Sum type}} 합계 유형 {{English term|sum type}} : 구성 유형의 인스턴스를 가질 수 있는 유형; 위키백과의 [[w:en:Sum type|집계 유형]] 참조. [[Special:MyLanguage/Wikifunctions:Function model#Zx/Sum_types|함수 모델]] 참조. == T == ; {{anchor|template}} 틀 {{English term|template}} : <span class="mw-translate-fuzzy">[[#renderer|렌더러]]를 자리 표시자가 산재된 텍스트 또는 "슬롯"으로 지정하는 방법은 [[#constructor|생성자]]의 데이터, 함수 계산 또는 다른 틀의 내용으로 채울 수 있습니다. 틀 구문에 대한 자세한 내용은 [[:m:Special:MyLanguage/Abstract Wikipedia/Template Language for Wikifunctions|위키함수용 틀 언어]] 문서를 참조하세요.</span> ; {{anchor|tester|Tester}} 테스터 {{English term|tester}} : 주어진 [[#ZFunction|Z함수]]가 정확하게 일을 하고 있는지 자동으로 결정하는 방법. [[#function|함수]]에는 일반적으로 여러 테스터가 있으며, 각 테스터는 함수에 대한 일부 입력을 지정하고 주어진 입력에 대한 출력이 충족되어야합니다. 예를 들어, "케이스 제목(title case)" 함수의 테스터에는 다음이 포함될 수 있습니다: "abc"는 "Abc"가 되어야합니다; "war and peace"는 "War and Peace"가 되어야합니다; "война и мир"는 "Война и мир"가 되어야합니다; "123"은 "123"으로 유지되어야합니다. ; {{anchor|transient|Transient}} 일시적 {{English term|transient}} : [[#persistent|영속적]]의 반대. ; {{anchor|type|Type}} 유형 {{English term|type}} : 객체의 유형은 주어진 객체를 해석하고 이해하는 방법과 객체로 수행할 수 있는 작업을 알려줍니다. 예를 들어 값이 "2023"인 객체가 있는 경우 유형이 정수인지, 연도인지 또는 문자열인지에 따라 해당 객체를 다르게 이해합니다. 모든 객체는 "실제 세계에 있는 것"을 나타냅니다. 정수 2023은 2023년과 다릅니다. 유형은 주어진 객체를 해석하는 방법을 알려주므로 실제 세계에서 어떤 것을 참조하는지 알 수 있습니다. 기술적으로는 해당 유형의 객체가 구성되는 방식과 해당 유형의 유효한 객체가 되기 위해 충족해야 하는 조건을 정의합니다. 유형은 Z객체의 유효성을 검사하는 [[#Function|함수]]를 제공하여 [[#ZObject|Z객체]]가 이 유형의 유효한 인스턴스가 되는 조건을 정의합니다. 유형은 Z객체 자체이므로 [[#Wikifunctions|위키함수]]의 기여자는 새로운 유형을 만들 수 있습니다. ; {{anchor|type converter}} <span lang="en" dir="ltr" class="mw-content-ltr">type converter</span> {{English term|type converter}} : <span lang="en" dir="ltr" class="mw-content-ltr">A script written in some programming language (such as JavaScript), taking a native object (such as BigInt), and returning a JSON object representing the corresponding ZObject; or ''vice versa''.</span> ; {{anchor|typed list|Typed List}} <span lang="en" dir="ltr" class="mw-content-ltr">typed list</span> {{English term|typed list}} : <span lang="en" dir="ltr" class="mw-content-ltr">A typed list is a [[#list|list]] in which all members of the list are of a specific, predefined [[#type|type]]. For example, a typed list of [[#string|strings]] is a list in which all members of the list are strings. A typed list takes one argument: the type that all the members of the list have to be an instance of. Typed lists are probably the most widely used [[#generic type|generic type]].</span> == V == ; {{anchor|value}} 값 {{English term|value}} : 다른 Z객체의 [[#key|키]]와 연관된 문자열 또는 [[#ZObject|Z객체]]. ; {{anchor|validation|Validation}} <span lang="en" dir="ltr" class="mw-content-ltr">validation</span> {{English term|validation}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#validator|validator]].</span> ; {{anchor|validator|Validator}} 검증자 {{English term|validator}} : <span class="mw-translate-fuzzy">Z객체를 인수로 사용하고 발견된 오류 목록을 반환하는 함수.</span> == W == ; {{anchor|wiki|Wiki}} 위키 {{English term|wiki}} : [[#page|페이지]]를 쉽고 공동으로 편집 할 수 있는 웹 사이트. ; {{anchor|Wikidata}} 위키데이터 {{English term|Wikidata}} : 공동으로 편집된 자유 지식 기반인 [[#Wikimedia_Foundation|위키미디어 재단]]의 프로젝트; [[:m:Special:MyLanguage/Wikidata|위키데이터]] 참조. ; {{anchor|Wikifunctions}}{{anchor|Wikilambda}} 위키함수 {{English term|Wikifunctions}} : [[#Wikimedia_Foundation|위키미디어 재단]]의 새로운 프로젝트; 무료이고 공동으로 개발하며 유지 관리하는 [[#Function|함수]] 카탈로그. {{Pg|:m:Abstract Wikipedia/Historic proposal|원래 제안}}에서 처음에는 위키람다로 알려졌습니다(이 이름은 현재 위키람다 확장에 사용됨). ; {{anchor|WikiLambda}} 위키람다 {{English term|WikiLambda}} : 프로젝트를 구동하는 데 사용되는 소프트웨어, [[mw:Special:MyLanguage/Extension:WikiLambda|확장:위키람다]]. ; {{anchor|WikiLambda system}} 위키람다 시스템 {{English term|WikiLambda system}} : <span lang="en" dir="ltr" class="mw-content-ltr">an automated system account that is a key part of the WikiLambda extension. See [[User:WikiLambda system]] for its current function.</span> ; {{anchor|WMF|Wikimedia_Foundation}} 위키미디어 재단 {{English term|Wikimedia Foundation}} : 위키미디어 운동을 지원하는 조직; [[:m:Special:MyLanguage/Wikimedia Foundation|위키미디어 재단]] 참조. ; {{anchor|Wikipedia}} 위키백과 {{English term|Wikipedia}} : [[#Wikimedia_Foundation|위키미디어 재단]]의 프로젝트, 공동으로 편집하는 자유 백과사전, [[:m:Special:MyLanguage/Wikipedia|위키백과]] 참조. ; 위키백과, 추상 {{English term|Wikipedia, Abstract}} : [[#Abstract_Wikipedia|추상 위키백과]] 참조. ; 위키백과, 다국어 {{English term|Wikipedia, multilingual}} : [[#multilingual_Wikipedia|다국어 위키백과]] 참조. == Z == ; {{anchor|ZID|ZIDs}} ZID {{English term|ZID}} : 문자 Z로 시작하고 뒤에 자연수가 오는 ID. [[#persistent|영구]] [[#ZObject|Z객체]]를 식별하는 데 사용됩니다. ; {{anchor|zfunction|ZFunction}} Z함수 {{English term|ZFunction}} : [[#evaluator|평가자]]를 통해 사용할 수 있는 특정 [[#function|함수]]를 설명하는 [[#Wikifunctions|위키함수]]의 위키 문서입니다. 각 Z함수는 하나 이상의 [[#implementation|구현]]에 의해 코드에서 실현 될 수 있으며, 상기 구현은 하나 이상의 [[#tester|테스터]] Z함수에 의해 올바른 것으로 검증될 수 있습니다. ; {{anchor|ZKey}} Z키 {{English term|ZKey}} : 특정 [[#type |유형]]에 대한 [[#key|키]]를 정의하는 [[#ZObject|Z객체]]. ; {{anchor|ZList}} Z리스트 {{English term|ZList}} : 다른 Z객체의 순서가 지정된 시퀀스에 대한 [[#ZObject|Z객체]]. ; {{anchor|ZObject}} Z객체 {{English term|ZObject}} : [[#Wikifunctions|위키함수]]의 모든 항목은 Z객체입니다. 위키함수에 저장된 Z객체는 [[#ZID|ZID]]를 가지며 [[#Constructor|생성자]]와 [[#Function|함수]], [[#Type|유형]] 등과 같은 다양한 유형이 될 수 있습니다. Z객체는 [[#Key|키]]/[[#Value|값]] 쌍 집합으로 구성되며 각 키는 Z객체 당 한 번만 나타나고 값은 Z객체입니다. ; {{anchor|ZUnit}} ZUnit {{English term|ZUnit}} : [[:w:en:Unit type|단위 유형]]을 나타내는 [[#ZObject|ZObject]]입니다. [[Category:Glossary| {{#translation:}}]] o5yuij0creifl626ijs6fx6knfw1tpz 275517 275515 2026-05-16T12:23:27Z Tensama0415 73696 275517 wikitext text/x-wiki <noinclude><languages/> <!--<nowiki>(nowiki tags are so that the translate extension doesn't try to translate the TERM and DEFINITION in this boilerplate). Use this boilerplate for a new term: ; {{anchor|term|Term}} <translate>term</translate> {{English term|term}} : ''Definition verification needed'' : <translate>definition</translate> Notes: 1. Omit the "Definition verification" if you're sure that your definition is correct. 2. You can add several values for anchor, if it has spelling or capitalization variants; see the documentation for Template:Anchor and examples in other terms. </nowiki>--></noinclude> {{see also|wikt:en:Appendix:Glossary}} [[Wikifunctions talk:Glossary|토론 페이지]]에서 용어를 요청하거나 더 많은 용어를 추가하고 정의를 개선하세요. {|class="toccolours" style="margin:.2em auto;padding:.2em .5em;text-align:center" dir="ltr" lang="en" |- |style="padding:0;width:100%"|{{CompactTOC}} |} == A == ; {{anchor|abstract|Abstract}} 추상 {{English term|abstract}} : [[#natural_language|특정한 자연어]]가 아니라 그로부터의 추상화; 자연어 텍스트, 문장 또는 구의 의미에 대한 표기법을 제공하는 것을 목표로합니다. [[#concrete|구상]]의 반대. ; {{anchor|abstracttext|AbstractText}} AbstractText {{English term|AbstractText}} : [[#Wikifunctions|위키함수]] 아이디어의 프로토 타입 [https://github.com/google/abstracttext 구현]. ; {{anchor|abstract_article}} <span lang="en" dir="ltr" class="mw-content-ltr">Abstract Article</span> {{English term|abstract article}} : <span lang="en" dir="ltr" class="mw-content-ltr">A page in the main namespace of [[#abstract_Wikipedia|Abstract Wikipedia]]; a page that is similar to a Wikipedia article, but that is [[#abstract|abstract]]. The opposite of [[#concrete_article|concrete article]]. ("Abstract" is an adjective here; it ''doesn't'' mean "a summary of an article".)</span> ; {{anchor|abstract_content}} 추상 콘텐츠 {{English term|abstract content}} : [[#Content|콘텐츠]] 참조. ; {{anchor|abstract_Wikipedia|Abstract_Wikipedia}} 추상 위키백과 {{English term|Abstract Wikipedia}} : [[#local_Wikipedia|로컬 위키백과]]에서 [[#natural_language|자연어]]로 [[#article|문서]]를 [[#Renderer|렌더링]]하는 데 사용할 수 있는 모든 [[#Content|콘텐츠]]의 예비 이름; 현재 해당 [[#Item|항목]] 옆에 [[#Wikidata|위키데이터]]에 존재하도록 제안되었지만 [[#development_project|개발 프로젝트]]의 [[#Part_P2|Part P2]] 이전에 논의될 것입니다. ; {{anchor|alias}} 별칭 {{English term|alias}} : 객체를 찾는 데 가장 먼저 사용되는 객체의 대체 레이블입니다. ; {{anchor|argument}} 인수 {{English term|argument}} : <span lang="en" dir="ltr" class="mw-content-ltr">an input given to a [[#function call|function call]].</span> ; {{anchor|argument reference}} <span lang="en" dir="ltr" class="mw-content-ltr">argument reference</span> {{English term|argument reference}} : <span lang="en" dir="ltr" class="mw-content-ltr">a [[#reference|reference]] to one of the supplied arguments within a [[#composition|composition]].</span> ; {{anchor|array}} <span lang="en" dir="ltr" class="mw-content-ltr">array</span> {{English term|array}} : <span lang="en" dir="ltr" class="mw-content-ltr">Many programming languages have an "array" type. The counterparts in Wikifunctions are [[#list|list]] and [[#typed list|typed list]]. See also [[#Benjamin array|Benjamin array]].</span> ; {{anchor|article|Article}} 문서 {{English term|article}} : <span class="mw-translate-fuzzy">일반적으로 [[#Wikipedia|위키백과]]의 한 항목을 나타내는 위키백과의 기본 이름공간에 있는 문서.</span> == B == ; {{anchor|Benjamin array}} <span lang="en" dir="ltr" class="mw-content-ltr">Benjamin array</span> {{English term|Benjamin array}} : <span lang="en" dir="ltr" class="mw-content-ltr">a way to denote [[#typed list|typed list]] proposed by Benjamin Degenhart, where a typed list is stored as a JSON list whose first element denotes the type. This is in contrast with the previous proposed schema, which uses LISP-style singly-linked lists, in which the type must be stored once in each node.</span> ; {{anchor|boolean|Boolean}} <span lang="en" dir="ltr" class="mw-content-ltr">boolean</span> {{English term|boolean}} : <span lang="en" dir="ltr" class="mw-content-ltr">a value that can have 2 states, usually denoted true and false.</span> ; {{anchor|built-in|builtin}} 내장된 {{English term|built-in}} : 평가자가 제공하고 위키 인터페이스를 통해 편집할 수없는 함수의 기본 구현. == C == ; {{anchor|call}} 호출 {{English term|call}} : [[#function call|함수 호출]] 참조. 영어에서는 [[#invoke|인보크(invoke) 또는 인보케이션(invocation)]]이라는 용어도 사용할 수 있습니다. ; {{anchor|canonical|canonicalized|canonicalised}} 표준형의 {{English term|canonical, canonicalized, canonicalised}} : 구체적이고 덜 장황하며 따라서 [[#JSON|JSON]]으로 [[#ZObject|Z객체]]를 표현하는 더 읽기 쉬운 방법입니다. Z객체는 위키함수에 저장되는 일반적인 표현입니다. 이것은 [[#normal|정규형]]과 반대입니다. ; {{anchor|character}} 문자 {{English term|character}} : 문자열의 구성 요소인 유니 코드로 정의된 문자; 문자는 여러 바이트(또는 8진수)로 구성 될 수 있습니다. ; {{anchor|claim|Claim}} <span lang="en" dir="ltr" class="mw-content-ltr">claim</span> {{English term|claim}} : <span lang="en" dir="ltr" class="mw-content-ltr">In the [[:d:Special:MyLanguage/Wikidata:Glossary#Claim|Wikibase data model]], a claim is a main snak plus optional qualifiers, expressing an assertion about an entity (without references or rank).</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example: Entity: Albert Einstein</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Claim: Spouse = Mileva Marić, starting in 1903</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Main snak: P26 (spouse) → Q937 (Mileva Marić)</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Qualifier snak: P580 (start time) → 1903</span> : <span lang="en" dir="ltr" class="mw-content-ltr">→ “Albert Einstein’s spouse was Mileva Marić, starting in 1903.”</span> : <span lang="en" dir="ltr" class="mw-content-ltr">The claim can later be turned into a statement by adding a reference and rank.</span> ; {{anchor|composition}} 컴포지션 {{English term|composition}} : 다른 함수의 조합에 의해 구현이 제공되는 함수의 구현 형태; [[Special:MyLanguage/Wikifunctions:Function model#Composition|함수 모델]] 참조. ; {{anchor|composition notation}} 컴포지션 표기법 {{English term|composition notation}} : 컴포지션(composition)에 관한 읽기 쉬운 표기법; [[Special:MyLanguage/Wikifunctions:Function model#Composition|함수 모델]] 참조. ; {{anchor|concrete|Concrete}} 구상 {{English term|concrete}} : [[#natural_language|특정 자연어]]에서. [[#abstract|추상]]의 반대. ; {{anchor|concrete_article}} <span lang="en" dir="ltr" class="mw-content-ltr">concrete article</span> {{English term|concrete article}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#article|article]]. The opposite of [[#abstract_article|Abstract Article]].</span> ; {{anchor|cons}} 단점 {{English term|cons}} : 상단에 요소를 추가하여 새로운 리스트를 생성하는 함수; [[phab:T261474]]을 참조. 위키백과의 [[w:cons|단점]]을 참조하세요. ; {{anchor|constructor|Constructor}} 생성자 {{English term|constructor}} : <span class="mw-translate-fuzzy">[[#Content|콘텐츠]]의 [[#abstract|추상]] 빌딩 블록; 생성자는 단일 구문 또는 문장 구조의 의미를 포착하는 것을 목표로 하며 종종 다른 생성자를 취할 수있는 슬롯을 가지고 있으며 다른 생성자의 슬롯을 채우는 값으로 자체적으로 사용될 수 있습니다.</span> ; {{anchor|Content}}<!--do not add |content to the anchor, it is used by MediaWiki--> 콘텐츠, 추상 콘텐츠 {{English term|content, abstract content}} : [[#Constructor|생성자]]에서 조립된 텍스트 또는 텍스트 조각의 추상 표현. 기술적으로는 인스턴스화 된 생성자. 최상위 생성자는 전체 [[#article|문서]]를 나타내는 데 사용되며 [[#Abstract_Wikipedia|추상 위키백과]]에 저장되지만 내용은 문장이나 구에 대한 것일 수도 있습니다. 추상 콘텐츠라고도 합니다. ; {{anchor|curry}} curried, curry, currying {{English term|curried, curry, currying}} : 커리 함수는 여러 인수를 각각 단일 인수가 있는 일련의 함수로 변환한 함수입니다. 이 기술은 미국 수학자 [[:w:en:Haskell하스켈 카레]]의 이름을 따서 명명되었습니다. 위키백과의 [[:w:en:Currying|커링]]을 참조하세요. == D == ; {{anchor|deserialization|Deserialization|deserialisation|Deserialisation}} 역직렬화 {{English term|deserialization}} : [[#serialization|직렬화]]의 반대. ; {{anchor|development_project|Development_project}} 개발 프로젝트 {{English term|development project}} : [[#Wikifunctions|위키함수]] 및 [[#Abstract_Wikipedia|추상 위키백과]] 개발 프로젝트; [[:m:Special:MyLanguage/Abstract Wikipedia/Plan|추상 위키백과 계획]] 참조. ; {{anchor|display function}} <span lang="en" dir="ltr" class="mw-content-ltr">display function</span> {{English term|display function}} : <span lang="en" dir="ltr" class="mw-content-ltr">a synonym of [[#renderer|renderer]]. For example, a function that converts a [[#type|type]] into a string that users can understand, such as converting a Number 123456 to "123,456" in (International) English, "1,23,456" in Indian English, "123.456" in French, etc., or converting the Date '2024','03','12' to '2024-03-12', and so on.</span> ; {{anchor|documentation}} 문서화 {{English term|documentation}} : 사람이 읽을 수 있는 객체를 설명하는 텍스트. == E == ; {{anchor|eney|eneyjj}} eneyj {{English term|eneyj}} :# [[#Wikifunctions|위키함수]]의 프로토타입 모델; :# [[#abstracttext|abstracttext]]에 제공된 해당 모델의 [[#evaluator|평가자]]에 대한 자바 스크립트 구현. ; {{anchor|error|Error}} 에러 {{English term|error}} : <span class="mw-translate-fuzzy">인스턴스가 평가 또는 검증의 문제를 나타내는 유형; [[Special:MyLanguage/Wikifunctions:Function model#Z5/Errors|함수 모델]] 참조.</span> ; {{anchor|evaluation|Evaluation}} <span lang="en" dir="ltr" class="mw-content-ltr">evaluation</span> {{English term|evaluation}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#evaluator|evaluator]].</span> ; {{anchor|evaluator|Evaluator}} 평가자 {{English term|evaluator}} : [[#ZObject|Z객체]]를 가져와 평가하는 소프트웨어, 즉 [[#Function|함수]]를 실행하고 결과를 반환하는 소프트웨어. 우리는 여러 평가자의 개발을 계획합니다. 평가자는 브라우저와 [[#Wikimedia_Foundation|위키미디어 재단]]의 서버, 클라우드, 모바일 장치의 앱 또는 기타 장소에서 구현 및 실행할 수 있습니다. [[#executor|실행자]] 및 [[#orchestrator|오케스트레이터]]와 비교합니다. ; {{anchor|execution|Execution}} <span lang="en" dir="ltr" class="mw-content-ltr">execution</span> {{English term|execution}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#executor|executor]].</span> ; {{anchor|executor|Executor|executors|Executors}} 실행자 {{English term|executor}} : 대중에게 노출되지 않는 일련의 내부 서비스 중 하나. [[#Orchestrator|오케스트레이터]]에 의해서만 호출 될 수 있습니다. 특정 프로그래밍 언어로 네이티브 코드를 실행합니다. 루아에 대한 하나의 실행 프로그램, 자바 스크립트에 대한 실행 프로그램, 파이썬에 대한 실행 프로그램 등이 있습니다. [https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-evaluator#executors 서비스 문서]를 참조. [[#evaluator|평가자]] 및 [[#orchestrator|오케스트레이터]]와 비교합니다. == F == ; {{anchor|function|Function}} 함수 {{English term|function}} : 일부 입력을 받아 출력을 반환하는 계산에 관한 사양; 위키백과의 [[w:ko:함수 (프로그래밍)|함수 (프로그래밍)]] 참조. ; {{anchor|function call|Function call}} 함수 호출 {{English term|function call}} : 함수 호출은 함수와 함수에 필요한 인수로 구성된 Z객체이며 다른 Z객체로 평가 될 수 있습니다. 영어에서는 "인보크(invoke)"라는 용어도 사용할 수 있습니다. ; {{anchor|function evaluator}} <span lang="en" dir="ltr" class="mw-content-ltr">function evaluator</span> {{English term|function evaluator}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#evaluator|evaluator]].</span> ; {{anchor|function executor}} <span lang="en" dir="ltr" class="mw-content-ltr">function executor</span> {{English term|function executor}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#executor|executor]].</span> ; {{anchor|function model}} 함수 모델 {{English term|function model}} : [[Special:MyLanguage/Wikifunctions:Function model|함수 모델]] 참조. ; {{anchor|function orchestrator}} <span lang="en" dir="ltr" class="mw-content-ltr">function orchestrator</span> {{English term|function orchestrator}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#orchestrator|orchestrator]].</span> ; {{anchor|function schemata}} <span lang="en" dir="ltr" class="mw-content-ltr">function schemata</span> {{English term|function schemata}} : <span lang="en" dir="ltr" class="mw-content-ltr">a set of pre-defined ZObjects used in [[#orchestrator|orchestrator]] and [[#evaluator|evaluator]]. The [[#WikiLambda system|WikiLambda system account]] also populates pre-defined ZObjects on-wiki from function schemata.</span> ; {{anchor|functional}} 함수형 {{English term|functional}} : "순수 함수형"의 줄임말로, 그러한 함수의 [[#evaluation|평가]]는 부작용이 없고 결정론적입니다. 즉, 항상 동일합니다; 위키백과의 [[w:en:Purely functional programming|순수 함수형 프로그래밍]] 참조; [[Special:MyLanguage/Wikifunctions:Function model#non-functional|함수 모델]] 참조. == G == ; {{anchor|generic type}} 제네릭 유형 {{English term|generic type}} : 함수 호출의 [[#evaluation|평가]]에 의해 생성 된 유형. == I == ; {{anchor|identity|Identity}} 식별 {{English term|identity}} : 유형의 식별은 유형으로 평가되는 (특정) 함수의 인스턴스입니다. 단순 유형의 경우, 유형 자체에 대한 참조입니다. ; {{anchor|implementation|Implementation}} 구현 {{English term|implementation}} : [[#function|함수]]를 실행하는 특별한 방법. 구현은 특정 프로그래밍 언어로 된 코드 조각일 수도 있고 [[#evaluator|평가자]]에 "내장 된" 기능을 참조하거나 다른 함수에 대한 호출을 결합할 수도 있습니다. 함수에는 많은 [[#composition|구현]]이 있을 수 있으며 모두 동일해야 합니다. "[[#ZFunction|Z함수]] 구현"의 약자입니다. ; {{anchor|instance}} 인스턴스 {{English term|instance}} : 모든 Z객체는 해당 유형의 인스턴스입니다. ; {{anchor|invoke}} 인보크 {{English term|invoke}} : 영어로 [[#call|호출]]의 동의어. [[#function call|함수 호출]]을 참조하세요. ; {{anchor|item|Item}} 항목 {{English term|item}} : [[#Wikidata|위키데이터]]의 지식 기반에 있는 항목; 위키데이터 용어집의 [[:d:Wikidata:Glossary#Item|항목]] 참조. == J == ; {{anchor|JSON}} JSON {{English term|JSON}} : 널리 사용되는 데이터 전송 형식; 위키백과의 [[w:en:JSON|JSON]]을 참조. == K == ; {{anchor|key|Key}} 키 {{English term|key}} : 문자 K와 자연수로 끝나고 선택적으로 앞에 [[#ZID|ZID]]가 오는 문자열. 키는 일반적으로 [[#Type|유형]] 또는 [[#Function|함수]]에 대한 [[#Wikifunctions|위키함수]]에서 정의되며 [[#ZObject|Z객체]]를 강화하는 데 사용됩니다. == L == ; {{anchor|label}} 레이블 {{English term|label}} : Z객체를 식별하기 위해 주어지는 이름. 일반 텍스트만 가능. ; {{anchor|lexeme|Lexeme}} 어휘소 {{English term|lexeme}} : 대략적인 단어에 대한 사전 지식을 저장하는 [[#Wikidata|위키데이터]]의 항목; 위키데이터 용어집의 [[d:Wikidata:Glossary#Lexeme|어휘소]] 항목 참조. ; {{anchor|linearizer|Linearizer}} linearizer {{English term|linearizer}} : <span class="mw-translate-fuzzy">Z객체를 문자열로 변환하는 함수. [[$parser|파서]]의 반대입니다.</span> ; {{anchor|list|List}} 리스트 {{English term|list}} : 정렬된 엔티티에서 임의의 수의 인스턴스를 그룹화하는 데이터 유형; 위키백과의 [[w:en:List (abstract data type)|리스트 (추상 데이터 유형)]]을 참조하세요. ; {{anchor|literal}} 리터럴 {{English term|literal}} : Z객체가 아닌 값. 현재 유일하게 허용되는 리터럴은 문자열입니다. ; {{anchor|local_Wikipedia|Local_Wikipedia}} 로컬 위키백과 {{English term|local Wikipedia}} : 히브리어 위키백과, 일본어 위키백과 또는 이탈리아어 위키백과와 같은 특정 언어로 된 [[#Wikipedia|위키백과]]. == M == ; {{anchor|Multlingual_Wikipedia|multilingual_Wikipedia}} 다국어 위키백과 {{English term|multilingual Wikipedia}} : [[#local_Wikipedia|로컬 위키백과]]가 [[#Abstract_Wikipedia|추상 위키백과]]의 [[#Content|콘텐츠]]를 [[#Renderer|렌더링]]하여 자신의 언어로 더 포괄적이고 최신이며 알맞은 위키백과를 가질 수 있도록하는 구조; [[:m:Special:MyLanguage/Abstract Wikipedia/Architecture|추상 위키백과 구조]] 참조. == N == ; {{anchor|natural_language|Natural_language}} 자연어 {{English term|natural language}} : 영어와 타갈로그어 또는 스와힐리어와 같은 넓은 의미의 특정 자연어; 위키백과의 [[w:en:Natural language|자연어]]를 참조하세요. ; {{anchor|normal|Normal|normalized|Normalized|normalised}} 정규형의, 정규형 {{English term|normal}} : [[#JSON|JSON]]으로 [[#ZObject|Z객체]]를 표현하는 확장되고 쉽게 처리 가능하며 매우 균일한 방법입니다. 이것은 [[#canonical|표준형]]과 반대입니다. ; {{anchor|nothing|Nothing}} nothing {{English term|nothing}} : 인스턴스를 가질 수 없는 데이터 유형; 위키백과의 [[w:en:Bottom type|바닥 유형]] 참조. == O == ; {{anchor|object|Object}} 객체 {{English term|object}} :# 자바 스크립트 또는 JSON에서 객체는 기본적으로 연관 배열입니다. 위키백과의 [[w:ko:연관 배열|연관 배열]]을 참조하세요. :# <span lang="en" dir="ltr" class="mw-content-ltr">In Wikifunctions, synonym of [[#ZObject|ZObject]].</span> ; {{anchor|orchestration|Orchestration}} <span lang="en" dir="ltr" class="mw-content-ltr">orchestration</span> {{English term|orchestration}} :<span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#orchestrator|orchestrator]].</span> ; {{anchor|orchestrator|Orchestrator}} 오케스트레이터 {{English term|orchestrator}} : <span class="mw-translate-fuzzy">[[#ZObject|Z객체]]를 가져와 [[#Evaluator|평가]]된 버전을 반환하는 서비스입니다. 이를 위해 필요한 다른 Z객체, 일부 함수 호출을 평가하기위한 [[#Executor|실행자]] 및 [[#Wikidata|위키데이터]]와 같은 기타 서비스에 대한 위키를 호출합니다. [https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-orchestrator#wikifunctions-function-orchestrator 서비스 문서]를 참조하세요. [[#evaluator|평가자]] 및 [[#executor|실행자]]와 비교합니다.</span> == P == ; {{anchor|page|Page}} 문서 {{English term|page}} : <span class="mw-translate-fuzzy">[[#wiki|위키]]는 독립적으로 편집할 수 있는 여러 개별 페이지로 구성됩니다.</span> ; {{anchor|parser|Parser}} 파서 {{English term|parser}} : <span class="mw-translate-fuzzy">문자열을 Z객체로 변환하는 함수. [[$linearizer|linearizer]]의 반대.</span> ; {{anchor|pair|Pair}} 짝 {{English term|pair}} : 특정 (임의의) 유형의 두 Z객체를 포함하는 복합 Z객체. ; {{anchor|part_P1|Part_P1}} 파트 P1 {{English term|Part P1}} : [[#Wikifunctions|위키함수]] 생성을 다루는 [[#development_project|개발 프로젝트]]의 일부입니다. 그것은 프로젝트의 시작 부분에서 시작하여 평생 동안 계속됩니다. [[:m:Special:MyLanguage/Abstract Wikipedia/Tasks#Part P1: Wikifunctions|파트 P1: 위키함수]]를 참조하세요. ; {{anchor|part_P2|Part_P2}} 파트 P2 {{English term|Part P2}} : [[#Abstract_Wikipedia|추상 위키백과]] 생성을 다루는 [[#development_project|개발 프로젝트]]의 일부입니다. 프로젝트에서 약 1년 후에 시작되어 이 기간의 후반기 동안 계속됩니다. [[:m:Special:MyLanguage/Abstract Wikipedia/Tasks#Part P2: Abstract Wikipedia|파트 P2: 추상 위키백과]] 참조. ; {{anchor|persistent|Persistent}} 영속적, 영속 {{English term|persistent}} : [[#ZID|ZID]]가 있고 위키의 자체 페이지가 있는 [[#ZObject|Z객체]] 대부분의 영속 Z객체에는 ZID가 없는 Z객체인 [[#value|값]]이 포함되어 있으므로 영속적이지 않습니다. ; {{anchor|property|Property}} 속성 {{English term|property}} : [[#Wikidata|위키데이터]]의 지식 기반에서 [[#Item|항목]]에 대해 [[#Statement|서술]]하는 데 사용됩니다. 위키데이터 용어집에서 [[:d:Wikidata:Glossary#Property|속성]] 참조. == Q == ; {{anchor|quote|Quote}} 인용 {{English term|quote}} : 평가되지는 않지만 그대로 유지되는 데이터 구조. ; {{anchor|QID}} QID {{English term|QID}} : [[#Wikidata|위키데이터]] 항목의 식별자로, 문자 "Q" 뒤에 정수가 오는 것으로 구성됩니다. == R == ; {{anchor|reading function}} <span lang="en" dir="ltr" class="mw-content-ltr">reading function</span> {{English term|reading function}} : <span lang="en" dir="ltr" class="mw-content-ltr">a synonym of [[#parser|parser]]. A function that converts user text input from a string into a given Type. For example, converting the String "123456" to the Number '123456', or the string "2024-03-12" to the Date '2024', '03', '12'.</span> ; {{anchor|reference|Reference}} 참조 {{English term|reference}} : 기본 객체를 나타내는 ID입니다. 예를 들어, 문자열 "Z11"은 유형 Z11/단어 언어 텍스트를 나타냅니다. : {{TakeNote}}이 용어는 위키데이터와는 완전히 다른 의미를 가지고 있습니다. 위키백과의 [[w:en:Reference (computer science)|참조 (컴컴퓨터 과학)]] 참조. ; {{anchor|renderer|Renderer}} 렌더러 {{English term|renderer}} (1) : <span lang="en" dir="ltr" class="mw-content-ltr">a function to convert a ZObject to a string. The opposite of [[#parser|parser]]. (formerly called "linearizer")</span> ; <span lang="en" dir="ltr" class="mw-content-ltr">renderer</span> {{English term|renderer}} (2) : [[#natural_language|자연어]]에 대한 [[#Content|콘텐츠]]와 식별자를 입력으로 가져오고 해당 자연어의 텍스트를 출력으로 반환하고, [[#Lexeme|어휘소]]의 지식을 사용하여 콘텐츠를 구체적인 텍스트로 나타내는 [[#Function|함수]]입니다. : {{TakeNote}}<span lang="en" dir="ltr" class="mw-content-ltr">This is a future feature, and the meaning of the term "renderer" in the {{Pg|:m:Abstract Wikipedia/Historic proposal|original proposal}}; this term collides with the current usage of "renderer", so it may be renamed in the future.</span> ; {{anchor|reify}} 구체화 {{English term|reify}} : 객체를 구성 부분으로 분해하여 부분에 개별적으로 접근할 수 있도록 하는 함수; 위키백과에서 [[w:en:Reification (computer science)|구체화]] 참조; [[phab:T261474]] 참조. ; {{anchor|REPL}} REPL {{English term|REPL}} : Read / Eval / Print - Loop, 입력을 받아 평가하고 결과를 표시하는 명령 줄 인터페이스; 위키백과의 [[w:ko:REPL|REPL]] 참조; [[Special:MyLanguage/Wikifunctions:Function model#REPL|함수 모델]] 참조. == S == ; {{anchor|schemata}} <span lang="en" dir="ltr" class="mw-content-ltr">schemata</span> {{English term|schemata}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#function schemata|function schemata]].</span> ; {{anchor|serialization|Serialization|serialisation|Serialisation}} 직렬화 {{English term|serialization}} : [[#JSON|JSON]]에서 Z객체를 표현하는 방법; [[#canonical|표준형]], [[#normal|정규형]]도 참조. ; {{anchor|snak|Snak}}<span lang="en" dir="ltr" class="mw-content-ltr">snak</span> {{English term|snak}} : <span lang="en" dir="ltr" class="mw-content-ltr">In the [[:mw:Special:MyLanguage/Wikibase/DataModel|Wikibase data model]], a snak is the smallest unit of a statement, linking a property to either a value, “no value”, or “some value.”</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example [[#statement|statement]] for {{Q|Q937}} with 3 snaks:</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Main snak:</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P26}} → Value: {{Q|Q76346}}</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Qualifier snak (adds context):</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P580}} → Value: 1903</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Reference snak (supports the claim):</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P248}} → Value: {{Q|Q23833686}}</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Resulting statement (in words): “Albert Einstein’s spouse was Mileva Marić, starting in 1903, as stated in the Catalog of the German National Library.”</span> ; {{anchor|statement|Statement}} 서술 {{English term|statement}} : <span class="mw-translate-fuzzy">[[#Wikidata|위키데이터]]의 지식 기반에서 [[#Item|항목]]에 대한 지식을 제공하는 데 사용됩니다. 위키데이터 용어집의 [[:d:Special:MyLanguage/Wikidata:Glossary#Statement|서술]] 참조.</span> ; {{anchor|string}} 문자열 {{English term|string}} : 일련의 문자. ; {{anchor|sum type|Sum type}} 합계 유형 {{English term|sum type}} : 구성 유형의 인스턴스를 가질 수 있는 유형; 위키백과의 [[w:en:Sum type|집계 유형]] 참조. [[Special:MyLanguage/Wikifunctions:Function model#Zx/Sum_types|함수 모델]] 참조. == T == ; {{anchor|template}} 틀 {{English term|template}} : <span class="mw-translate-fuzzy">[[#renderer|렌더러]]를 자리 표시자가 산재된 텍스트 또는 "슬롯"으로 지정하는 방법은 [[#constructor|생성자]]의 데이터, 함수 계산 또는 다른 틀의 내용으로 채울 수 있습니다. 틀 구문에 대한 자세한 내용은 [[:m:Special:MyLanguage/Abstract Wikipedia/Template Language for Wikifunctions|위키함수용 틀 언어]] 문서를 참조하세요.</span> ; {{anchor|tester|Tester}} 테스터 {{English term|tester}} : 주어진 [[#ZFunction|Z함수]]가 정확하게 일을 하고 있는지 자동으로 결정하는 방법. [[#function|함수]]에는 일반적으로 여러 테스터가 있으며, 각 테스터는 함수에 대한 일부 입력을 지정하고 주어진 입력에 대한 출력이 충족되어야합니다. 예를 들어, "케이스 제목(title case)" 함수의 테스터에는 다음이 포함될 수 있습니다: "abc"는 "Abc"가 되어야합니다; "war and peace"는 "War and Peace"가 되어야합니다; "война и мир"는 "Война и мир"가 되어야합니다; "123"은 "123"으로 유지되어야합니다. ; {{anchor|transient|Transient}} 일시적 {{English term|transient}} : [[#persistent|영속적]]의 반대. ; {{anchor|type|Type}} 유형 {{English term|type}} : 객체의 유형은 주어진 객체를 해석하고 이해하는 방법과 객체로 수행할 수 있는 작업을 알려줍니다. 예를 들어 값이 "2023"인 객체가 있는 경우 유형이 정수인지, 연도인지 또는 문자열인지에 따라 해당 객체를 다르게 이해합니다. 모든 객체는 "실제 세계에 있는 것"을 나타냅니다. 정수 2023은 2023년과 다릅니다. 유형은 주어진 객체를 해석하는 방법을 알려주므로 실제 세계에서 어떤 것을 참조하는지 알 수 있습니다. 기술적으로는 해당 유형의 객체가 구성되는 방식과 해당 유형의 유효한 객체가 되기 위해 충족해야 하는 조건을 정의합니다. 유형은 Z객체의 유효성을 검사하는 [[#Function|함수]]를 제공하여 [[#ZObject|Z객체]]가 이 유형의 유효한 인스턴스가 되는 조건을 정의합니다. 유형은 Z객체 자체이므로 [[#Wikifunctions|위키함수]]의 기여자는 새로운 유형을 만들 수 있습니다. ; {{anchor|type converter}} <span lang="en" dir="ltr" class="mw-content-ltr">type converter</span> {{English term|type converter}} : <span lang="en" dir="ltr" class="mw-content-ltr">A script written in some programming language (such as JavaScript), taking a native object (such as BigInt), and returning a JSON object representing the corresponding ZObject; or ''vice versa''.</span> ; {{anchor|typed list|Typed List}} <span lang="en" dir="ltr" class="mw-content-ltr">typed list</span> {{English term|typed list}} : <span lang="en" dir="ltr" class="mw-content-ltr">A typed list is a [[#list|list]] in which all members of the list are of a specific, predefined [[#type|type]]. For example, a typed list of [[#string|strings]] is a list in which all members of the list are strings. A typed list takes one argument: the type that all the members of the list have to be an instance of. Typed lists are probably the most widely used [[#generic type|generic type]].</span> == V == ; {{anchor|value}} 값 {{English term|value}} : 다른 Z객체의 [[#key|키]]와 연관된 문자열 또는 [[#ZObject|Z객체]]. ; {{anchor|validation|Validation}} <span lang="en" dir="ltr" class="mw-content-ltr">validation</span> {{English term|validation}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#validator|validator]].</span> ; {{anchor|validator|Validator}} 검증자 {{English term|validator}} : <span class="mw-translate-fuzzy">Z객체를 인수로 사용하고 발견된 오류 목록을 반환하는 함수.</span> == W == ; {{anchor|wiki|Wiki}} 위키 {{English term|wiki}} : [[#page|페이지]]를 쉽고 공동으로 편집 할 수 있는 웹 사이트. ; {{anchor|Wikidata}} 위키데이터 {{English term|Wikidata}} : 공동으로 편집된 자유 지식 기반인 [[#Wikimedia_Foundation|위키미디어 재단]]의 프로젝트; [[:m:Special:MyLanguage/Wikidata|위키데이터]] 참조. ; {{anchor|Wikifunctions}}{{anchor|Wikilambda}} 위키함수 {{English term|Wikifunctions}} : [[#Wikimedia_Foundation|위키미디어 재단]]의 새로운 프로젝트; 무료이고 공동으로 개발하며 유지 관리하는 [[#Function|함수]] 카탈로그. {{Pg|:m:Abstract Wikipedia/Historic proposal|원래 제안}}에서 처음에는 위키람다로 알려졌습니다(이 이름은 현재 위키람다 확장에 사용됨). ; {{anchor|WikiLambda}} 위키람다 {{English term|WikiLambda}} : 프로젝트를 구동하는 데 사용되는 소프트웨어, [[mw:Special:MyLanguage/Extension:WikiLambda|확장:위키람다]]. ; {{anchor|WikiLambda system}} 위키람다 시스템 {{English term|WikiLambda system}} : <span lang="en" dir="ltr" class="mw-content-ltr">an automated system account that is a key part of the WikiLambda extension. See [[User:WikiLambda system]] for its current function.</span> ; {{anchor|WMF|Wikimedia_Foundation}} 위키미디어 재단 {{English term|Wikimedia Foundation}} : 위키미디어 운동을 지원하는 조직; [[:m:Special:MyLanguage/Wikimedia Foundation|위키미디어 재단]] 참조. ; {{anchor|Wikipedia}} 위키백과 {{English term|Wikipedia}} : [[#Wikimedia_Foundation|위키미디어 재단]]의 프로젝트, 공동으로 편집하는 자유 백과사전, [[:m:Special:MyLanguage/Wikipedia|위키백과]] 참조. ; 위키백과, 추상 {{English term|Wikipedia, Abstract}} : [[#Abstract_Wikipedia|추상 위키백과]] 참조. ; 위키백과, 다국어 {{English term|Wikipedia, multilingual}} : [[#multilingual_Wikipedia|다국어 위키백과]] 참조. == Z == ; {{anchor|ZID|ZIDs}} ZID {{English term|ZID}} : 문자 Z로 시작하고 뒤에 자연수가 오는 ID. [[#persistent|영구]] [[#ZObject|Z객체]]를 식별하는 데 사용됩니다. ; {{anchor|zfunction|ZFunction}} Z함수 {{English term|ZFunction}} : [[#evaluator|평가자]]를 통해 사용할 수 있는 특정 [[#function|함수]]를 설명하는 [[#Wikifunctions|위키함수]]의 위키 문서입니다. 각 Z함수는 하나 이상의 [[#implementation|구현]]에 의해 코드에서 실현 될 수 있으며, 상기 구현은 하나 이상의 [[#tester|테스터]] Z함수에 의해 올바른 것으로 검증될 수 있습니다. ; {{anchor|ZKey}} Z키 {{English term|ZKey}} : 특정 [[#type |유형]]에 대한 [[#key|키]]를 정의하는 [[#ZObject|Z객체]]. ; {{anchor|ZList}} Z리스트 {{English term|ZList}} : 다른 Z객체의 순서가 지정된 시퀀스에 대한 [[#ZObject|Z객체]]. ; {{anchor|ZObject}} Z객체 {{English term|ZObject}} : [[#Wikifunctions|위키함수]]의 모든 항목은 Z객체입니다. 위키함수에 저장된 Z객체는 [[#ZID|ZID]]를 가지며 [[#Constructor|생성자]]와 [[#Function|함수]], [[#Type|유형]] 등과 같은 다양한 유형이 될 수 있습니다. Z객체는 [[#Key|키]]/[[#Value|값]] 쌍 집합으로 구성되며 각 키는 Z객체 당 한 번만 나타나고 값은 Z객체입니다. ; {{anchor|ZUnit}} ZUnit {{English term|ZUnit}} : [[:w:en:Unit type|단위 유형]]을 나타내는 [[#ZObject|ZObject]]입니다. [[Category:Glossary| {{#translation:}}]] rzjzy5f0te9pq9lpfpmwti3skwlc6nv 275519 275517 2026-05-16T12:24:47Z Tensama0415 73696 275519 wikitext text/x-wiki <noinclude><languages/> <!--<nowiki>(nowiki tags are so that the translate extension doesn't try to translate the TERM and DEFINITION in this boilerplate). Use this boilerplate for a new term: ; {{anchor|term|Term}} <translate>term</translate> {{English term|term}} : ''Definition verification needed'' : <translate>definition</translate> Notes: 1. Omit the "Definition verification" if you're sure that your definition is correct. 2. You can add several values for anchor, if it has spelling or capitalization variants; see the documentation for Template:Anchor and examples in other terms. </nowiki>--></noinclude> {{see also|wikt:en:Appendix:Glossary}} [[Wikifunctions talk:Glossary|토론 페이지]]에서 용어를 요청하거나 더 많은 용어를 추가하고 정의를 개선하세요. {|class="toccolours" style="margin:.2em auto;padding:.2em .5em;text-align:center" dir="ltr" lang="en" |- |style="padding:0;width:100%"|{{CompactTOC}} |} == A == ; {{anchor|abstract|Abstract}} 추상 {{English term|abstract}} : [[#natural_language|특정한 자연어]]가 아니라 그로부터의 추상화; 자연어 텍스트, 문장 또는 구의 의미에 대한 표기법을 제공하는 것을 목표로합니다. [[#concrete|구상]]의 반대. ; {{anchor|abstracttext|AbstractText}} AbstractText {{English term|AbstractText}} : [[#Wikifunctions|위키함수]] 아이디어의 프로토 타입 [https://github.com/google/abstracttext 구현]. ; {{anchor|abstract_article}} <span lang="en" dir="ltr" class="mw-content-ltr">Abstract Article</span> {{English term|abstract article}} : <span lang="en" dir="ltr" class="mw-content-ltr">A page in the main namespace of [[#abstract_Wikipedia|Abstract Wikipedia]]; a page that is similar to a Wikipedia article, but that is [[#abstract|abstract]]. The opposite of [[#concrete_article|concrete article]]. ("Abstract" is an adjective here; it ''doesn't'' mean "a summary of an article".)</span> ; {{anchor|abstract_content}} 추상 콘텐츠 {{English term|abstract content}} : [[#Content|콘텐츠]] 참조. ; {{anchor|abstract_Wikipedia|Abstract_Wikipedia}} 추상 위키백과 {{English term|Abstract Wikipedia}} : [[#local_Wikipedia|로컬 위키백과]]에서 [[#natural_language|자연어]]로 [[#article|문서]]를 [[#Renderer|렌더링]]하는 데 사용할 수 있는 모든 [[#Content|콘텐츠]]의 예비 이름; 현재 해당 [[#Item|항목]] 옆에 [[#Wikidata|위키데이터]]에 존재하도록 제안되었지만 [[#development_project|개발 프로젝트]]의 [[#Part_P2|Part P2]] 이전에 논의될 것입니다. ; {{anchor|alias}} 별칭 {{English term|alias}} : 객체를 찾는 데 가장 먼저 사용되는 객체의 대체 레이블입니다. ; {{anchor|argument}} 인수 {{English term|argument}} : <span lang="en" dir="ltr" class="mw-content-ltr">an input given to a [[#function call|function call]].</span> ; {{anchor|argument reference}} <span lang="en" dir="ltr" class="mw-content-ltr">argument reference</span> {{English term|argument reference}} : <span lang="en" dir="ltr" class="mw-content-ltr">a [[#reference|reference]] to one of the supplied arguments within a [[#composition|composition]].</span> ; {{anchor|array}} <span lang="en" dir="ltr" class="mw-content-ltr">array</span> {{English term|array}} : <span lang="en" dir="ltr" class="mw-content-ltr">Many programming languages have an "array" type. The counterparts in Wikifunctions are [[#list|list]] and [[#typed list|typed list]]. See also [[#Benjamin array|Benjamin array]].</span> ; {{anchor|article|Article}} 문서 {{English term|article}} : <span class="mw-translate-fuzzy">일반적으로 [[#Wikipedia|위키백과]]의 한 항목을 나타내는 위키백과의 기본 이름공간에 있는 문서.</span> == B == ; {{anchor|Benjamin array}} <span lang="en" dir="ltr" class="mw-content-ltr">Benjamin array</span> {{English term|Benjamin array}} : <span lang="en" dir="ltr" class="mw-content-ltr">a way to denote [[#typed list|typed list]] proposed by Benjamin Degenhart, where a typed list is stored as a JSON list whose first element denotes the type. This is in contrast with the previous proposed schema, which uses LISP-style singly-linked lists, in which the type must be stored once in each node.</span> ; {{anchor|boolean|Boolean}} <span lang="en" dir="ltr" class="mw-content-ltr">boolean</span> {{English term|boolean}} : <span lang="en" dir="ltr" class="mw-content-ltr">a value that can have 2 states, usually denoted true and false.</span> ; {{anchor|built-in|builtin}} 내장된 {{English term|built-in}} : 평가자가 제공하고 위키 인터페이스를 통해 편집할 수없는 함수의 기본 구현. == C == ; {{anchor|call}} 호출 {{English term|call}} : [[#function call|함수 호출]] 참조. 영어에서는 [[#invoke|인보크(invoke) 또는 인보케이션(invocation)]]이라는 용어도 사용할 수 있습니다. ; {{anchor|canonical|canonicalized|canonicalised}} 표준형의 {{English term|canonical, canonicalized, canonicalised}} : 구체적이고 덜 장황하며 따라서 [[#JSON|JSON]]으로 [[#ZObject|Z객체]]를 표현하는 더 읽기 쉬운 방법입니다. Z객체는 위키함수에 저장되는 일반적인 표현입니다. 이것은 [[#normal|정규형]]과 반대입니다. ; {{anchor|character}} 문자 {{English term|character}} : 문자열의 구성 요소인 유니 코드로 정의된 문자; 문자는 여러 바이트(또는 8진수)로 구성 될 수 있습니다. ; {{anchor|claim|Claim}} <span lang="en" dir="ltr" class="mw-content-ltr">claim</span> {{English term|claim}} : <span lang="en" dir="ltr" class="mw-content-ltr">In the [[:d:Special:MyLanguage/Wikidata:Glossary#Claim|Wikibase data model]], a claim is a main snak plus optional qualifiers, expressing an assertion about an entity (without references or rank).</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example: Entity: Albert Einstein</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Claim: Spouse = Mileva Marić, starting in 1903</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Main snak: P26 (spouse) → Q937 (Mileva Marić)</span> :* <span lang="en" dir="ltr" class="mw-content-ltr">Qualifier snak: P580 (start time) → 1903</span> : <span lang="en" dir="ltr" class="mw-content-ltr">→ “Albert Einstein’s spouse was Mileva Marić, starting in 1903.”</span> : <span lang="en" dir="ltr" class="mw-content-ltr">The claim can later be turned into a statement by adding a reference and rank.</span> ; {{anchor|composition}} 컴포지션 {{English term|composition}} : 다른 함수의 조합에 의해 구현이 제공되는 함수의 구현 형태; [[Special:MyLanguage/Wikifunctions:Function model#Composition|함수 모델]] 참조. ; {{anchor|composition notation}} 컴포지션 표기법 {{English term|composition notation}} : 컴포지션(composition)에 관한 읽기 쉬운 표기법; [[Special:MyLanguage/Wikifunctions:Function model#Composition|함수 모델]] 참조. ; {{anchor|concrete|Concrete}} 구상 {{English term|concrete}} : [[#natural_language|특정 자연어]]에서. [[#abstract|추상]]의 반대. ; {{anchor|concrete_article}} <span lang="en" dir="ltr" class="mw-content-ltr">concrete article</span> {{English term|concrete article}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#article|article]]. The opposite of [[#abstract_article|Abstract Article]].</span> ; {{anchor|cons}} 단점 {{English term|cons}} : 상단에 요소를 추가하여 새로운 리스트를 생성하는 함수; [[phab:T261474]]을 참조. 위키백과의 [[w:cons|단점]]을 참조하세요. ; {{anchor|constructor|Constructor}} 생성자 {{English term|constructor}} : <span class="mw-translate-fuzzy">[[#Content|콘텐츠]]의 [[#abstract|추상]] 빌딩 블록; 생성자는 단일 구문 또는 문장 구조의 의미를 포착하는 것을 목표로 하며 종종 다른 생성자를 취할 수있는 슬롯을 가지고 있으며 다른 생성자의 슬롯을 채우는 값으로 자체적으로 사용될 수 있습니다.</span> ; {{anchor|Content}}<!--do not add |content to the anchor, it is used by MediaWiki--> 콘텐츠, 추상 콘텐츠 {{English term|content, abstract content}} : [[#Constructor|생성자]]에서 조립된 텍스트 또는 텍스트 조각의 추상 표현. 기술적으로는 인스턴스화 된 생성자. 최상위 생성자는 전체 [[#article|문서]]를 나타내는 데 사용되며 [[#Abstract_Wikipedia|추상 위키백과]]에 저장되지만 내용은 문장이나 구에 대한 것일 수도 있습니다. 추상 콘텐츠라고도 합니다. ; {{anchor|curry}} curried, curry, currying {{English term|curried, curry, currying}} : 커리 함수는 여러 인수를 각각 단일 인수가 있는 일련의 함수로 변환한 함수입니다. 이 기술은 미국 수학자 [[:w:en:Haskell하스켈 카레]]의 이름을 따서 명명되었습니다. 위키백과의 [[:w:en:Currying|커링]]을 참조하세요. == D == ; {{anchor|deserialization|Deserialization|deserialisation|Deserialisation}} 역직렬화 {{English term|deserialization}} : [[#serialization|직렬화]]의 반대. ; {{anchor|development_project|Development_project}} 개발 프로젝트 {{English term|development project}} : [[#Wikifunctions|위키함수]] 및 [[#Abstract_Wikipedia|추상 위키백과]] 개발 프로젝트; [[:m:Special:MyLanguage/Abstract Wikipedia/Plan|추상 위키백과 계획]] 참조. ; {{anchor|display function}} <span lang="en" dir="ltr" class="mw-content-ltr">display function</span> {{English term|display function}} : <span lang="en" dir="ltr" class="mw-content-ltr">a synonym of [[#renderer|renderer]]. For example, a function that converts a [[#type|type]] into a string that users can understand, such as converting a Number 123456 to "123,456" in (International) English, "1,23,456" in Indian English, "123.456" in French, etc., or converting the Date '2024','03','12' to '2024-03-12', and so on.</span> ; {{anchor|documentation}} 문서화 {{English term|documentation}} : 사람이 읽을 수 있는 객체를 설명하는 텍스트. == E == ; {{anchor|eney|eneyjj}} eneyj {{English term|eneyj}} :# [[#Wikifunctions|위키함수]]의 프로토타입 모델; :# [[#abstracttext|abstracttext]]에 제공된 해당 모델의 [[#evaluator|평가자]]에 대한 자바 스크립트 구현. ; {{anchor|error|Error}} 에러 {{English term|error}} : <span class="mw-translate-fuzzy">인스턴스가 평가 또는 검증의 문제를 나타내는 유형; [[Special:MyLanguage/Wikifunctions:Function model#Z5/Errors|함수 모델]] 참조.</span> ; {{anchor|evaluation|Evaluation}} <span lang="en" dir="ltr" class="mw-content-ltr">evaluation</span> {{English term|evaluation}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#evaluator|evaluator]].</span> ; {{anchor|evaluator|Evaluator}} 평가자 {{English term|evaluator}} : [[#ZObject|Z객체]]를 가져와 평가하는 소프트웨어, 즉 [[#Function|함수]]를 실행하고 결과를 반환하는 소프트웨어. 우리는 여러 평가자의 개발을 계획합니다. 평가자는 브라우저와 [[#Wikimedia_Foundation|위키미디어 재단]]의 서버, 클라우드, 모바일 장치의 앱 또는 기타 장소에서 구현 및 실행할 수 있습니다. [[#executor|실행자]] 및 [[#orchestrator|오케스트레이터]]와 비교합니다. ; {{anchor|execution|Execution}} <span lang="en" dir="ltr" class="mw-content-ltr">execution</span> {{English term|execution}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#executor|executor]].</span> ; {{anchor|executor|Executor|executors|Executors}} 실행자 {{English term|executor}} : 대중에게 노출되지 않는 일련의 내부 서비스 중 하나. [[#Orchestrator|오케스트레이터]]에 의해서만 호출 될 수 있습니다. 특정 프로그래밍 언어로 네이티브 코드를 실행합니다. 루아에 대한 하나의 실행 프로그램, 자바 스크립트에 대한 실행 프로그램, 파이썬에 대한 실행 프로그램 등이 있습니다. [https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-evaluator#executors 서비스 문서]를 참조. [[#evaluator|평가자]] 및 [[#orchestrator|오케스트레이터]]와 비교합니다. == F == ; {{anchor|function|Function}} 함수 {{English term|function}} : 일부 입력을 받아 출력을 반환하는 계산에 관한 사양; 위키백과의 [[w:ko:함수 (프로그래밍)|함수 (프로그래밍)]] 참조. ; {{anchor|function call|Function call}} 함수 호출 {{English term|function call}} : 함수 호출은 함수와 함수에 필요한 인수로 구성된 Z객체이며 다른 Z객체로 평가 될 수 있습니다. 영어에서는 "인보크(invoke)"라는 용어도 사용할 수 있습니다. ; {{anchor|function evaluator}} <span lang="en" dir="ltr" class="mw-content-ltr">function evaluator</span> {{English term|function evaluator}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#evaluator|evaluator]].</span> ; {{anchor|function executor}} <span lang="en" dir="ltr" class="mw-content-ltr">function executor</span> {{English term|function executor}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#executor|executor]].</span> ; {{anchor|function model}} 함수 모델 {{English term|function model}} : [[Special:MyLanguage/Wikifunctions:Function model|함수 모델]] 참조. ; {{anchor|function orchestrator}} <span lang="en" dir="ltr" class="mw-content-ltr">function orchestrator</span> {{English term|function orchestrator}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#orchestrator|orchestrator]].</span> ; {{anchor|function schemata}} <span lang="en" dir="ltr" class="mw-content-ltr">function schemata</span> {{English term|function schemata}} : <span lang="en" dir="ltr" class="mw-content-ltr">a set of pre-defined ZObjects used in [[#orchestrator|orchestrator]] and [[#evaluator|evaluator]]. The [[#WikiLambda system|WikiLambda system account]] also populates pre-defined ZObjects on-wiki from function schemata.</span> ; {{anchor|functional}} 함수형 {{English term|functional}} : "순수 함수형"의 줄임말로, 그러한 함수의 [[#evaluation|평가]]는 부작용이 없고 결정론적입니다. 즉, 항상 동일합니다; 위키백과의 [[w:en:Purely functional programming|순수 함수형 프로그래밍]] 참조; [[Special:MyLanguage/Wikifunctions:Function model#non-functional|함수 모델]] 참조. == G == ; {{anchor|generic type}} 제네릭 유형 {{English term|generic type}} : 함수 호출의 [[#evaluation|평가]]에 의해 생성 된 유형. == I == ; {{anchor|identity|Identity}} 식별 {{English term|identity}} : 유형의 식별은 유형으로 평가되는 (특정) 함수의 인스턴스입니다. 단순 유형의 경우, 유형 자체에 대한 참조입니다. ; {{anchor|implementation|Implementation}} 구현 {{English term|implementation}} : [[#function|함수]]를 실행하는 특별한 방법. 구현은 특정 프로그래밍 언어로 된 코드 조각일 수도 있고 [[#evaluator|평가자]]에 "내장 된" 기능을 참조하거나 다른 함수에 대한 호출을 결합할 수도 있습니다. 함수에는 많은 [[#composition|구현]]이 있을 수 있으며 모두 동일해야 합니다. "[[#ZFunction|Z함수]] 구현"의 약자입니다. ; {{anchor|instance}} 인스턴스 {{English term|instance}} : 모든 Z객체는 해당 유형의 인스턴스입니다. ; {{anchor|invoke}} 인보크 {{English term|invoke}} : 영어로 [[#call|호출]]의 동의어. [[#function call|함수 호출]]을 참조하세요. ; {{anchor|item|Item}} 항목 {{English term|item}} : [[#Wikidata|위키데이터]]의 지식 기반에 있는 항목; 위키데이터 용어집의 [[:d:Wikidata:Glossary#Item|항목]] 참조. == J == ; {{anchor|JSON}} JSON {{English term|JSON}} : 널리 사용되는 데이터 전송 형식; 위키백과의 [[w:en:JSON|JSON]]을 참조. == K == ; {{anchor|key|Key}} 키 {{English term|key}} : 문자 K와 자연수로 끝나고 선택적으로 앞에 [[#ZID|ZID]]가 오는 문자열. 키는 일반적으로 [[#Type|유형]] 또는 [[#Function|함수]]에 대한 [[#Wikifunctions|위키함수]]에서 정의되며 [[#ZObject|Z객체]]를 강화하는 데 사용됩니다. == L == ; {{anchor|label}} 레이블 {{English term|label}} : Z객체를 식별하기 위해 주어지는 이름. 일반 텍스트만 가능. ; {{anchor|lexeme|Lexeme}} 어휘소 {{English term|lexeme}} : 대략적인 단어에 대한 사전 지식을 저장하는 [[#Wikidata|위키데이터]]의 항목; 위키데이터 용어집의 [[d:Wikidata:Glossary#Lexeme|어휘소]] 항목 참조. ; {{anchor|linearizer|Linearizer}} linearizer {{English term|linearizer}} : <span class="mw-translate-fuzzy">Z객체를 문자열로 변환하는 함수. [[$parser|파서]]의 반대입니다.</span> ; {{anchor|list|List}} 리스트 {{English term|list}} : 정렬된 엔티티에서 임의의 수의 인스턴스를 그룹화하는 데이터 유형; 위키백과의 [[w:en:List (abstract data type)|리스트 (추상 데이터 유형)]]을 참조하세요. ; {{anchor|literal}} 리터럴 {{English term|literal}} : Z객체가 아닌 값. 현재 유일하게 허용되는 리터럴은 문자열입니다. ; {{anchor|local_Wikipedia|Local_Wikipedia}} 로컬 위키백과 {{English term|local Wikipedia}} : 히브리어 위키백과, 일본어 위키백과 또는 이탈리아어 위키백과와 같은 특정 언어로 된 [[#Wikipedia|위키백과]]. == M == ; {{anchor|Multlingual_Wikipedia|multilingual_Wikipedia}} 다국어 위키백과 {{English term|multilingual Wikipedia}} : [[#local_Wikipedia|로컬 위키백과]]가 [[#Abstract_Wikipedia|추상 위키백과]]의 [[#Content|콘텐츠]]를 [[#Renderer|렌더링]]하여 자신의 언어로 더 포괄적이고 최신이며 알맞은 위키백과를 가질 수 있도록하는 구조; [[:m:Special:MyLanguage/Abstract Wikipedia/Architecture|추상 위키백과 구조]] 참조. == N == ; {{anchor|natural_language|Natural_language}} 자연어 {{English term|natural language}} : 영어와 타갈로그어 또는 스와힐리어와 같은 넓은 의미의 특정 자연어; 위키백과의 [[w:en:Natural language|자연어]]를 참조하세요. ; {{anchor|normal|Normal|normalized|Normalized|normalised}} 정규형의, 정규형 {{English term|normal}} : [[#JSON|JSON]]으로 [[#ZObject|Z객체]]를 표현하는 확장되고 쉽게 처리 가능하며 매우 균일한 방법입니다. 이것은 [[#canonical|표준형]]과 반대입니다. ; {{anchor|nothing|Nothing}} nothing {{English term|nothing}} : 인스턴스를 가질 수 없는 데이터 유형; 위키백과의 [[w:en:Bottom type|바닥 유형]] 참조. == O == ; {{anchor|object|Object}} 객체 {{English term|object}} :# 자바 스크립트 또는 JSON에서 객체는 기본적으로 연관 배열입니다. 위키백과의 [[w:ko:연관 배열|연관 배열]]을 참조하세요. :# <span lang="en" dir="ltr" class="mw-content-ltr">In Wikifunctions, synonym of [[#ZObject|ZObject]].</span> ; {{anchor|orchestration|Orchestration}} <span lang="en" dir="ltr" class="mw-content-ltr">orchestration</span> {{English term|orchestration}} :<span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#orchestrator|orchestrator]].</span> ; {{anchor|orchestrator|Orchestrator}} 오케스트레이터 {{English term|orchestrator}} : <span class="mw-translate-fuzzy">[[#ZObject|Z객체]]를 가져와 [[#Evaluator|평가]]된 버전을 반환하는 서비스입니다. 이를 위해 필요한 다른 Z객체, 일부 함수 호출을 평가하기위한 [[#Executor|실행자]] 및 [[#Wikidata|위키데이터]]와 같은 기타 서비스에 대한 위키를 호출합니다. [https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-orchestrator#wikifunctions-function-orchestrator 서비스 문서]를 참조하세요. [[#evaluator|평가자]] 및 [[#executor|실행자]]와 비교합니다.</span> == P == ; {{anchor|page|Page}} 문서 {{English term|page}} : <span class="mw-translate-fuzzy">[[#wiki|위키]]는 독립적으로 편집할 수 있는 여러 개별 페이지로 구성됩니다.</span> ; {{anchor|parser|Parser}} 파서 {{English term|parser}} : <span class="mw-translate-fuzzy">문자열을 Z객체로 변환하는 함수. [[$linearizer|linearizer]]의 반대.</span> ; {{anchor|pair|Pair}} 짝 {{English term|pair}} : 특정 (임의의) 유형의 두 Z객체를 포함하는 복합 Z객체. ; {{anchor|part_P1|Part_P1}} 파트 P1 {{English term|Part P1}} : [[#Wikifunctions|위키함수]] 생성을 다루는 [[#development_project|개발 프로젝트]]의 일부입니다. 그것은 프로젝트의 시작 부분에서 시작하여 평생 동안 계속됩니다. [[:m:Special:MyLanguage/Abstract Wikipedia/Tasks#Part P1: Wikifunctions|파트 P1: 위키함수]]를 참조하세요. ; {{anchor|part_P2|Part_P2}} 파트 P2 {{English term|Part P2}} : [[#Abstract_Wikipedia|추상 위키백과]] 생성을 다루는 [[#development_project|개발 프로젝트]]의 일부입니다. 프로젝트에서 약 1년 후에 시작되어 이 기간의 후반기 동안 계속됩니다. [[:m:Special:MyLanguage/Abstract Wikipedia/Tasks#Part P2: Abstract Wikipedia|파트 P2: 추상 위키백과]] 참조. ; {{anchor|persistent|Persistent}} 영속적, 영속 {{English term|persistent}} : [[#ZID|ZID]]가 있고 위키의 자체 페이지가 있는 [[#ZObject|Z객체]] 대부분의 영속 Z객체에는 ZID가 없는 Z객체인 [[#value|값]]이 포함되어 있으므로 영속적이지 않습니다. ; {{anchor|property|Property}} 속성 {{English term|property}} : [[#Wikidata|위키데이터]]의 지식 기반에서 [[#Item|항목]]에 대해 [[#Statement|서술]]하는 데 사용됩니다. 위키데이터 용어집에서 [[:d:Wikidata:Glossary#Property|속성]] 참조. == Q == ; {{anchor|quote|Quote}} 인용 {{English term|quote}} : 평가되지는 않지만 그대로 유지되는 데이터 구조. ; {{anchor|QID}} QID {{English term|QID}} : [[#Wikidata|위키데이터]] 항목의 식별자로, 문자 "Q" 뒤에 정수가 오는 것으로 구성됩니다. == R == ; {{anchor|reading function}} <span lang="en" dir="ltr" class="mw-content-ltr">reading function</span> {{English term|reading function}} : <span lang="en" dir="ltr" class="mw-content-ltr">a synonym of [[#parser|parser]]. A function that converts user text input from a string into a given Type. For example, converting the String "123456" to the Number '123456', or the string "2024-03-12" to the Date '2024', '03', '12'.</span> ; {{anchor|reference|Reference}} 참조 {{English term|reference}} : 기본 객체를 나타내는 ID입니다. 예를 들어, 문자열 "Z11"은 유형 Z11/단어 언어 텍스트를 나타냅니다. : {{TakeNote}}이 용어는 위키데이터와는 완전히 다른 의미를 가지고 있습니다. 위키백과의 [[w:en:Reference (computer science)|참조 (컴퓨터 과학)]] 참조. ; {{anchor|renderer|Renderer}} 렌더러 {{English term|renderer}} (1) : <span lang="en" dir="ltr" class="mw-content-ltr">a function to convert a ZObject to a string. The opposite of [[#parser|parser]]. (formerly called "linearizer")</span> ; <span lang="en" dir="ltr" class="mw-content-ltr">renderer</span> {{English term|renderer}} (2) : [[#natural_language|자연어]]에 대한 [[#Content|콘텐츠]]와 식별자를 입력으로 가져오고 해당 자연어의 텍스트를 출력으로 반환하고, [[#Lexeme|어휘소]]의 지식을 사용하여 콘텐츠를 구체적인 텍스트로 나타내는 [[#Function|함수]]입니다. : {{TakeNote}}<span lang="en" dir="ltr" class="mw-content-ltr">This is a future feature, and the meaning of the term "renderer" in the {{Pg|:m:Abstract Wikipedia/Historic proposal|original proposal}}; this term collides with the current usage of "renderer", so it may be renamed in the future.</span> ; {{anchor|reify}} 구체화 {{English term|reify}} : 객체를 구성 부분으로 분해하여 부분에 개별적으로 접근할 수 있도록 하는 함수; 위키백과에서 [[w:en:Reification (computer science)|구체화]] 참조; [[phab:T261474]] 참조. ; {{anchor|REPL}} REPL {{English term|REPL}} : Read / Eval / Print - Loop, 입력을 받아 평가하고 결과를 표시하는 명령 줄 인터페이스; 위키백과의 [[w:ko:REPL|REPL]] 참조; [[Special:MyLanguage/Wikifunctions:Function model#REPL|함수 모델]] 참조. == S == ; {{anchor|schemata}} <span lang="en" dir="ltr" class="mw-content-ltr">schemata</span> {{English term|schemata}} : <span lang="en" dir="ltr" class="mw-content-ltr">See [[#function schemata|function schemata]].</span> ; {{anchor|serialization|Serialization|serialisation|Serialisation}} 직렬화 {{English term|serialization}} : [[#JSON|JSON]]에서 Z객체를 표현하는 방법; [[#canonical|표준형]], [[#normal|정규형]]도 참조. ; {{anchor|snak|Snak}}<span lang="en" dir="ltr" class="mw-content-ltr">snak</span> {{English term|snak}} : <span lang="en" dir="ltr" class="mw-content-ltr">In the [[:mw:Special:MyLanguage/Wikibase/DataModel|Wikibase data model]], a snak is the smallest unit of a statement, linking a property to either a value, “no value”, or “some value.”</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Example [[#statement|statement]] for {{Q|Q937}} with 3 snaks:</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Main snak:</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P26}} → Value: {{Q|Q76346}}</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Qualifier snak (adds context):</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P580}} → Value: 1903</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Reference snak (supports the claim):</span> :  <span lang="en" dir="ltr" class="mw-content-ltr">Property: {{Q|P248}} → Value: {{Q|Q23833686}}</span> : <span lang="en" dir="ltr" class="mw-content-ltr">Resulting statement (in words): “Albert Einstein’s spouse was Mileva Marić, starting in 1903, as stated in the Catalog of the German National Library.”</span> ; {{anchor|statement|Statement}} 서술 {{English term|statement}} : <span class="mw-translate-fuzzy">[[#Wikidata|위키데이터]]의 지식 기반에서 [[#Item|항목]]에 대한 지식을 제공하는 데 사용됩니다. 위키데이터 용어집의 [[:d:Special:MyLanguage/Wikidata:Glossary#Statement|서술]] 참조.</span> ; {{anchor|string}} 문자열 {{English term|string}} : 일련의 문자. ; {{anchor|sum type|Sum type}} 합계 유형 {{English term|sum type}} : 구성 유형의 인스턴스를 가질 수 있는 유형; 위키백과의 [[w:en:Sum type|집계 유형]] 참조. [[Special:MyLanguage/Wikifunctions:Function model#Zx/Sum_types|함수 모델]] 참조. == T == ; {{anchor|template}} 틀 {{English term|template}} : <span class="mw-translate-fuzzy">[[#renderer|렌더러]]를 자리 표시자가 산재된 텍스트 또는 "슬롯"으로 지정하는 방법은 [[#constructor|생성자]]의 데이터, 함수 계산 또는 다른 틀의 내용으로 채울 수 있습니다. 틀 구문에 대한 자세한 내용은 [[:m:Special:MyLanguage/Abstract Wikipedia/Template Language for Wikifunctions|위키함수용 틀 언어]] 문서를 참조하세요.</span> ; {{anchor|tester|Tester}} 테스터 {{English term|tester}} : 주어진 [[#ZFunction|Z함수]]가 정확하게 일을 하고 있는지 자동으로 결정하는 방법. [[#function|함수]]에는 일반적으로 여러 테스터가 있으며, 각 테스터는 함수에 대한 일부 입력을 지정하고 주어진 입력에 대한 출력이 충족되어야합니다. 예를 들어, "케이스 제목(title case)" 함수의 테스터에는 다음이 포함될 수 있습니다: "abc"는 "Abc"가 되어야합니다; "war and peace"는 "War and Peace"가 되어야합니다; "война и мир"는 "Война и мир"가 되어야합니다; "123"은 "123"으로 유지되어야합니다. ; {{anchor|transient|Transient}} 일시적 {{English term|transient}} : [[#persistent|영속적]]의 반대. ; {{anchor|type|Type}} 유형 {{English term|type}} : 객체의 유형은 주어진 객체를 해석하고 이해하는 방법과 객체로 수행할 수 있는 작업을 알려줍니다. 예를 들어 값이 "2023"인 객체가 있는 경우 유형이 정수인지, 연도인지 또는 문자열인지에 따라 해당 객체를 다르게 이해합니다. 모든 객체는 "실제 세계에 있는 것"을 나타냅니다. 정수 2023은 2023년과 다릅니다. 유형은 주어진 객체를 해석하는 방법을 알려주므로 실제 세계에서 어떤 것을 참조하는지 알 수 있습니다. 기술적으로는 해당 유형의 객체가 구성되는 방식과 해당 유형의 유효한 객체가 되기 위해 충족해야 하는 조건을 정의합니다. 유형은 Z객체의 유효성을 검사하는 [[#Function|함수]]를 제공하여 [[#ZObject|Z객체]]가 이 유형의 유효한 인스턴스가 되는 조건을 정의합니다. 유형은 Z객체 자체이므로 [[#Wikifunctions|위키함수]]의 기여자는 새로운 유형을 만들 수 있습니다. ; {{anchor|type converter}} <span lang="en" dir="ltr" class="mw-content-ltr">type converter</span> {{English term|type converter}} : <span lang="en" dir="ltr" class="mw-content-ltr">A script written in some programming language (such as JavaScript), taking a native object (such as BigInt), and returning a JSON object representing the corresponding ZObject; or ''vice versa''.</span> ; {{anchor|typed list|Typed List}} <span lang="en" dir="ltr" class="mw-content-ltr">typed list</span> {{English term|typed list}} : <span lang="en" dir="ltr" class="mw-content-ltr">A typed list is a [[#list|list]] in which all members of the list are of a specific, predefined [[#type|type]]. For example, a typed list of [[#string|strings]] is a list in which all members of the list are strings. A typed list takes one argument: the type that all the members of the list have to be an instance of. Typed lists are probably the most widely used [[#generic type|generic type]].</span> == V == ; {{anchor|value}} 값 {{English term|value}} : 다른 Z객체의 [[#key|키]]와 연관된 문자열 또는 [[#ZObject|Z객체]]. ; {{anchor|validation|Validation}} <span lang="en" dir="ltr" class="mw-content-ltr">validation</span> {{English term|validation}} : <span lang="en" dir="ltr" class="mw-content-ltr">The action performed by the [[#validator|validator]].</span> ; {{anchor|validator|Validator}} 검증자 {{English term|validator}} : <span class="mw-translate-fuzzy">Z객체를 인수로 사용하고 발견된 오류 목록을 반환하는 함수.</span> == W == ; {{anchor|wiki|Wiki}} 위키 {{English term|wiki}} : [[#page|페이지]]를 쉽고 공동으로 편집 할 수 있는 웹 사이트. ; {{anchor|Wikidata}} 위키데이터 {{English term|Wikidata}} : 공동으로 편집된 자유 지식 기반인 [[#Wikimedia_Foundation|위키미디어 재단]]의 프로젝트; [[:m:Special:MyLanguage/Wikidata|위키데이터]] 참조. ; {{anchor|Wikifunctions}}{{anchor|Wikilambda}} 위키함수 {{English term|Wikifunctions}} : [[#Wikimedia_Foundation|위키미디어 재단]]의 새로운 프로젝트; 무료이고 공동으로 개발하며 유지 관리하는 [[#Function|함수]] 카탈로그. {{Pg|:m:Abstract Wikipedia/Historic proposal|원래 제안}}에서 처음에는 위키람다로 알려졌습니다(이 이름은 현재 위키람다 확장에 사용됨). ; {{anchor|WikiLambda}} 위키람다 {{English term|WikiLambda}} : 프로젝트를 구동하는 데 사용되는 소프트웨어, [[mw:Special:MyLanguage/Extension:WikiLambda|확장:위키람다]]. ; {{anchor|WikiLambda system}} 위키람다 시스템 {{English term|WikiLambda system}} : <span lang="en" dir="ltr" class="mw-content-ltr">an automated system account that is a key part of the WikiLambda extension. See [[User:WikiLambda system]] for its current function.</span> ; {{anchor|WMF|Wikimedia_Foundation}} 위키미디어 재단 {{English term|Wikimedia Foundation}} : 위키미디어 운동을 지원하는 조직; [[:m:Special:MyLanguage/Wikimedia Foundation|위키미디어 재단]] 참조. ; {{anchor|Wikipedia}} 위키백과 {{English term|Wikipedia}} : [[#Wikimedia_Foundation|위키미디어 재단]]의 프로젝트, 공동으로 편집하는 자유 백과사전, [[:m:Special:MyLanguage/Wikipedia|위키백과]] 참조. ; 위키백과, 추상 {{English term|Wikipedia, Abstract}} : [[#Abstract_Wikipedia|추상 위키백과]] 참조. ; 위키백과, 다국어 {{English term|Wikipedia, multilingual}} : [[#multilingual_Wikipedia|다국어 위키백과]] 참조. == Z == ; {{anchor|ZID|ZIDs}} ZID {{English term|ZID}} : 문자 Z로 시작하고 뒤에 자연수가 오는 ID. [[#persistent|영구]] [[#ZObject|Z객체]]를 식별하는 데 사용됩니다. ; {{anchor|zfunction|ZFunction}} Z함수 {{English term|ZFunction}} : [[#evaluator|평가자]]를 통해 사용할 수 있는 특정 [[#function|함수]]를 설명하는 [[#Wikifunctions|위키함수]]의 위키 문서입니다. 각 Z함수는 하나 이상의 [[#implementation|구현]]에 의해 코드에서 실현 될 수 있으며, 상기 구현은 하나 이상의 [[#tester|테스터]] Z함수에 의해 올바른 것으로 검증될 수 있습니다. ; {{anchor|ZKey}} Z키 {{English term|ZKey}} : 특정 [[#type |유형]]에 대한 [[#key|키]]를 정의하는 [[#ZObject|Z객체]]. ; {{anchor|ZList}} Z리스트 {{English term|ZList}} : 다른 Z객체의 순서가 지정된 시퀀스에 대한 [[#ZObject|Z객체]]. ; {{anchor|ZObject}} Z객체 {{English term|ZObject}} : [[#Wikifunctions|위키함수]]의 모든 항목은 Z객체입니다. 위키함수에 저장된 Z객체는 [[#ZID|ZID]]를 가지며 [[#Constructor|생성자]]와 [[#Function|함수]], [[#Type|유형]] 등과 같은 다양한 유형이 될 수 있습니다. Z객체는 [[#Key|키]]/[[#Value|값]] 쌍 집합으로 구성되며 각 키는 Z객체 당 한 번만 나타나고 값은 Z객체입니다. ; {{anchor|ZUnit}} ZUnit {{English term|ZUnit}} : [[:w:en:Unit type|단위 유형]]을 나타내는 [[#ZObject|ZObject]]입니다. [[Category:Glossary| {{#translation:}}]] 5r9jj0effzh2fpoqh95igornumkthdl 0 8459 275709 247340 2026-05-17T08:49:55Z Ameisenigel 44 Added Z18774, Z22986 und Z22987 to the approved list of test cases 275709 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z10251" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z10251K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "value" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Wert" }, { "Z1K1": "Z11", "Z11K1": "Z1014", "Z11K2": "String 1" }, { "Z1K1": "Z11", "Z11K1": "Z1013", "Z11K2": "darajar" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "valore" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "वैल्यू" } ] } } ], "Z8K2": "Z6", "Z8K3": [ "Z20", "Z10252", "Z10253", "Z10255", "Z10256", "Z18774", "Z22986", "Z22987" ], "Z8K4": [ "Z14", "Z10254" ], "Z8K5": "Z10251" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Title Case" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "タイトルケースに変換" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "in großen Anfangsbuchstaben" }, { "Z1K1": "Z11", "Z11K1": "Z1014", "Z11K2": "Na Aha ikpe" }, { "Z1K1": "Z11", "Z11K1": "Z1013", "Z11K2": "Zuwa Harkar Take" }, { "Z1K1": "Z11", "Z11K1": "Z1186", "Z11K2": "לרישיות כותרת" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "converti in Title Case" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "शीर्षक केस में बदलें" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "to title case", "to titlecase" ] }, { "Z1K1": "Z31", "Z31K1": "Z1186", "Z31K2": [ "Z6", "רישיות כותרת" ] }, { "Z1K1": "Z31", "Z31K1": "Z1787", "Z31K2": [ "Z6", "prima lettera maiuscola" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "文字列をタイトルケースに変換する" }, { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "converts a string to title case" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "wandelt eine Zeichenkette in die Schreibweise mit großen Anfangsbuchstaben um" }, { "Z1K1": "Z11", "Z11K1": "Z1014", "Z11K2": "Na-atụgharị eriri gaa na ikpe aha" }, { "Z1K1": "Z11", "Z11K1": "Z1013", "Z11K2": "Yana canza kirtani zuwa shari'ar take" }, { "Z1K1": "Z11", "Z11K1": "Z1186", "Z11K2": "המרת מחרוזת אל רישיות כותרת" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "Rende maiuscola la prima lettera di ogni parola e rende minusole tutte le altre lettere" } ] } } f6v58qjin2j5s0qma1xo62pdbfs0gsa 275713 275709 2026-05-17T08:56:29Z Ameisenigel 44 Added Z15865 und Z18773 to the approved list of implementations 275713 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z10251" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z10251K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "value" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Wert" }, { "Z1K1": "Z11", "Z11K1": "Z1014", "Z11K2": "String 1" }, { "Z1K1": "Z11", "Z11K1": "Z1013", "Z11K2": "darajar" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "valore" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "वैल्यू" } ] } } ], "Z8K2": "Z6", "Z8K3": [ "Z20", "Z10252", "Z10253", "Z10255", "Z10256", "Z18774", "Z22986", "Z22987" ], "Z8K4": [ "Z14", "Z10254", "Z15865", "Z18773" ], "Z8K5": "Z10251" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Title Case" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "タイトルケースに変換" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "in großen Anfangsbuchstaben" }, { "Z1K1": "Z11", "Z11K1": "Z1014", "Z11K2": "Na Aha ikpe" }, { "Z1K1": "Z11", "Z11K1": "Z1013", "Z11K2": "Zuwa Harkar Take" }, { "Z1K1": "Z11", "Z11K1": "Z1186", "Z11K2": "לרישיות כותרת" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "converti in Title Case" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "शीर्षक केस में बदलें" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "to title case", "to titlecase" ] }, { "Z1K1": "Z31", "Z31K1": "Z1186", "Z31K2": [ "Z6", "רישיות כותרת" ] }, { "Z1K1": "Z31", "Z31K1": "Z1787", "Z31K2": [ "Z6", "prima lettera maiuscola" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "文字列をタイトルケースに変換する" }, { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "converts a string to title case" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "wandelt eine Zeichenkette in die Schreibweise mit großen Anfangsbuchstaben um" }, { "Z1K1": "Z11", "Z11K1": "Z1014", "Z11K2": "Na-atụgharị eriri gaa na ikpe aha" }, { "Z1K1": "Z11", "Z11K1": "Z1013", "Z11K2": "Yana canza kirtani zuwa shari'ar take" }, { "Z1K1": "Z11", "Z11K1": "Z1186", "Z11K2": "המרת מחרוזת אל רישיות כותרת" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "Rende maiuscola la prima lettera di ogni parola e rende minusole tutte le altre lettere" } ] } } e2ol0a164r1dy7m3zumrbstgta1j4vp 275720 275713 2026-05-17T09:02:50Z Ameisenigel 44 Added Z22985 to the approved list of implementations 275720 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z10251" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z10251K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "value" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Wert" }, { "Z1K1": "Z11", "Z11K1": "Z1014", "Z11K2": "String 1" }, { "Z1K1": "Z11", "Z11K1": "Z1013", "Z11K2": "darajar" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "valore" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "वैल्यू" } ] } } ], "Z8K2": "Z6", "Z8K3": [ "Z20", "Z10252", "Z10253", "Z10255", "Z10256", "Z18774", "Z22986", "Z22987" ], "Z8K4": [ "Z14", "Z10254", "Z15865", "Z18773", "Z22985" ], "Z8K5": "Z10251" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Title Case" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "タイトルケースに変換" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "in großen Anfangsbuchstaben" }, { "Z1K1": "Z11", "Z11K1": "Z1014", "Z11K2": "Na Aha ikpe" }, { "Z1K1": "Z11", "Z11K1": "Z1013", "Z11K2": "Zuwa Harkar Take" }, { "Z1K1": "Z11", "Z11K1": "Z1186", "Z11K2": "לרישיות כותרת" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "converti in Title Case" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "शीर्षक केस में बदलें" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "to title case", "to titlecase" ] }, { "Z1K1": "Z31", "Z31K1": "Z1186", "Z31K2": [ "Z6", "רישיות כותרת" ] }, { "Z1K1": "Z31", "Z31K1": "Z1787", "Z31K2": [ "Z6", "prima lettera maiuscola" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "文字列をタイトルケースに変換する" }, { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "converts a string to title case" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "wandelt eine Zeichenkette in die Schreibweise mit großen Anfangsbuchstaben um" }, { "Z1K1": "Z11", "Z11K1": "Z1014", "Z11K2": "Na-atụgharị eriri gaa na ikpe aha" }, { "Z1K1": "Z11", "Z11K1": "Z1013", "Z11K2": "Yana canza kirtani zuwa shari'ar take" }, { "Z1K1": "Z11", "Z11K1": "Z1186", "Z11K2": "המרת מחרוזת אל רישיות כותרת" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "Rende maiuscola la prima lettera di ogni parola e rende minusole tutte le altre lettere" } ] } } bwh8chyr2am56xjb7zxykfwn8b0pf31 0 18014 275748 69559 2026-05-17T10:18:04Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275748 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1913" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mnc-mong" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Manchu (Mongolian script)" }, { "Z1K1": "Z11", "Z11K1": "Z1913", "Z11K2": "ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "満洲語（蒙古文字）" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Mandschurisch (mongolische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "mandchou en écriture mongole" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 1qj4jega57704fxfld2a63dce1rl7p2 0 18015 275749 69560 2026-05-17T10:18:18Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275749 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1914" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mnc-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Manchu (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1914", "Z11K2": "manju gisun" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "満洲語（ラテン文字）" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Mandschurisch (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "mandchou en écriture latine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 5644kx8f5mtas89py2grci7um33hxyo 0 23034 275684 79748 2026-05-17T06:30:29Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275684 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1816" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "kge" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Komering" }, { "Z1K1": "Z11", "Z11K1": "Z1816", "Z11K2": "Basa Kumoring" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Komering" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "komering" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 45ue53h66gmsal7ygtm7yek1ks7jctt 4 24478 275621 270479 2026-05-17T02:42:28Z YoshiRulz 10156 Add sitelink and word order 275621 wikitext text/x-wiki <languages/>{{Technical documentation navbox}} <translate> <!--T:1--> Every Object in Wikifunctions belongs to a Type. Types decide how Objects of that Type are structured, and what they mean. Types are also used to specify the Arguments of a Function, and what a Function returns. <!--T:2--> Currently, there are <tvar name="1">{{NUMBEROFTYPES}}</tvar> Types that are available for specifying the Arguments and the return Type of a Function: </translate> * {{Z+|Z1}} * {{Z+|Z4}} * {{Z+|Z8}} * {{Z+|Z23}} * {{Z+|Z21}} * {{Z+|Z40}} * {{Z+|Z22112}} * {{Z+|Z881}} (<translate><!--T:14--> this is parameterised i.e. it is a Function which returns a Type</translate>) * {{Z+|Z882}} (<translate><!--T:15--> parameterised</translate>) * {{Z+|Z883}} (<translate><!--T:16--> parameterised</translate>) * {{Z+|Z6884}} (<translate><!--T:17--> parameterised, used for defining [[<tvar name="1">Special:MyLanguage/WF:Function_model#Lightweight_enumerations</tvar>|lightweight enumeration types]]</translate>) <translate> === Numeric types === <!--T:6--> </translate> * {{Z+|Z80}} * {{Z+|Z13518}} * {{Z+|Z16659}} * {{Z+|Z16683}} * {{Z+|Z19677}} * {{Z+|Z20825}} * {{Z+|Z20838}} * {{Z+|Z33198}} <translate> === Language and text types === <!--T:18--> </translate> * {{Z+|Z86}} * {{Z+|Z6}} * {{Z+|Z60}} * {{Z+|Z11}} * {{Z+|Z31}} * {{Z+|Z12}} * {{Z+|Z32}} * {{Z+|Z89}} * {{Z+|Z14293}} * {{Z+|Z14294}} <translate> ==== Grammatical feature enums ==== <!--T:19--> </translate> * {{Z+|Z28516}} (<translate><!--T:20--> lightweight enum</translate>) * {{Z+|Z28519}} (<translate><!--T:21--> lightweight enum</translate>) * {{Z+|Z25502}} (<translate><!--T:22--> lightweight enum</translate>) * {{Z+|Z25340}} (<translate><!--T:23--> lightweight enum</translate>) * {{Z+|Z25501}} (<translate><!--T:24--> lightweight enum</translate>) * {{Z+|Z26935}} (<translate><!--T:25--> lightweight enum</translate>) * {{Z+|Z26934}} (<translate><!--T:26--> lightweight enum</translate>) * {{Z+|Z28215}} (<translate><!--T:27--> lightweight enum</translate>) * {{Z+|Z28515}} (<translate><!--T:28--> lightweight enum</translate>) * {{Z+|Z28517}} (<translate><!--T:29--> lightweight enum</translate>) * {{Z+|Z32792}} (<translate><!--T:43--> lightweight enum</translate>) * {{Z+|Z32789}} (<translate><!--T:44--> lightweight enum</translate>) * {{Z+|Z27970}} (<translate><!--T:30--> lightweight enum</translate>) * {{Z+|Z28518}} (<translate><!--T:31--> lightweight enum</translate>) * {{Z+|Z28520}} (<translate><!--T:32--> lightweight enum</translate>) * {{Z+|Z33568}} (<translate>lightweight enum</translate>) * {{Z+|Z27971}} (<translate><!--T:33--> lightweight enum</translate>) <translate> === Calendar types === <!--T:7--> ==== Gregorian calendar ==== <!--T:8--> </translate> * {{Z+|Z17402}} * {{Z+|Z16098}} * {{Z+|Z17813}} * {{Z+|Z20159}} * {{Z+|Z20342}} * {{Z+|Z20420}} <translate> ==== Hijri (Islamic) calendar ==== <!--T:34--> </translate> * {{Z+|Z26582}} (<translate><!--T:35--> lightweight enum</translate>) <translate> ==== Igbo calendar ==== <!--T:9--> </translate> * {{Z+|Z16927}} <translate> === Wikidata types === <!--T:10--> </translate> {{see also|Help:Wikidata#Statement model}} * {{Z+|Z6030}} <translate> ==== Wikidata entities ==== <!--T:11--> </translate> * {{Z+|Z6001}} * {{Z+|Z6002}} * {{Z+|Z6004}} * {{Z+|Z6005}} * {{Z+|Z6006}} <translate> ==== Wikidata references ==== <!--T:12--> </translate> * {{Z+|Z6091}} * {{Z+|Z6092}} * {{Z+|Z6094}} * {{Z+|Z6095}} * {{Z+|Z6096}} <translate> ==== Wikidata statements ==== <!--T:13--> </translate> * {{Z+|Z6020}} * {{Z+|Z6007}} * {{Z+|Z6003}} * {{Z+|Z6040}} * {{Z+|Z6008}} * {{Z+|Z6039}} <translate> ==== Wikidata datatypes ==== <!--T:36--> </translate> * {{Z+|Z6010}} * {{Z+|Z6011}} * {{Z+|Z6060}} * {{Z+|Z6061}} * {{Z+|Z6062}} (<translate><!--T:37--> lightweight enum</translate>) * {{Z+|Z6063}} (<translate><!--T:38--> lightweight enum</translate>) * {{Z+|Z6064}} <translate> === Miscellaneous === <!--T:39--> </translate> * {{Z+|Z27951}} (<translate><!--T:40--> lightweight enum</translate>) * {{Z+|Z28579}} * {{Z+|Z33827}} (<translate><!--T:45--> lightweight enum</translate>) <translate> === WikiLambda structure === <!--T:41--> </translate> * {{Z+|Z2}} * {{Z+|Z9}} * {{Z+|Z3}} * {{Z+|Z39}} * {{Z+|Z46}} * {{Z+|Z64}} * {{Z+|Z17}} * {{Z+|Z18}} * {{Z+|Z20}} * {{Z+|Z14}} * {{Z+|Z16}} * {{Z+|Z61}} <translate> ==== Evaluation ==== <!--T:42--> </translate> * {{Z+|Z7}} * {{Z+|Z22}} * {{Z+|Z5}} * {{Z+|Z50}} * {{Z+|Z99}} <translate> <!--T:3--> Other types can be used but there may be bugs. For a list of all types, see [[<tvar name="1">Special:ListObjectsByType/Z4</tvar>|the list of all types]] (though that does not include [[<tvar name="2">Special:ListObjectsByType/Z7</tvar>|persistent calls]] which return types, such as the lightweight enums, nor parameterised types such as <tvar name="3">{{Z|881}}</tvar>). <!--T:4--> New Types can be proposed on <tvar name="1">[[Wikifunctions:Type proposals]]</tvar>. == See also == <!--T:5--> </translate> * {{ll|Wikifunctions:Function model}} [[Category:Technical documentation{{#translation:}}|Type]] smitlfh8dcscc6wzcsnft5vm9bghox5 275626 275621 2026-05-17T03:01:05Z YoshiRulz 10156 Update the count (and use formatnum) 275626 wikitext text/x-wiki <languages/>{{Technical documentation navbox}} <translate> <!--T:1--> Every Object in Wikifunctions belongs to a Type. Types decide how Objects of that Type are structured, and what they mean. Types are also used to specify the Arguments of a Function, and what a Function returns. <!--T:2--> Currently, there are <tvar name="1"><del>{{formatnum:{{NUMBEROFTYPES}}}}</del> ~{{formatnum:100}}</tvar> Types that are available for specifying the Arguments and the return Type of a Function: </translate> * {{Z+|Z1}} * {{Z+|Z4}} * {{Z+|Z8}} * {{Z+|Z23}} * {{Z+|Z21}} * {{Z+|Z40}} * {{Z+|Z22112}} * {{Z+|Z881}} (<translate><!--T:14--> this is parameterised i.e. it is a Function which returns a Type</translate>) * {{Z+|Z882}} (<translate><!--T:15--> parameterised</translate>) * {{Z+|Z883}} (<translate><!--T:16--> parameterised</translate>) * {{Z+|Z6884}} (<translate><!--T:17--> parameterised, used for defining [[<tvar name="1">Special:MyLanguage/WF:Function_model#Lightweight_enumerations</tvar>|lightweight enumeration types]]</translate>) <translate> === Numeric types === <!--T:6--> </translate> * {{Z+|Z80}} * {{Z+|Z13518}} * {{Z+|Z16659}} * {{Z+|Z16683}} * {{Z+|Z19677}} * {{Z+|Z20825}} * {{Z+|Z20838}} * {{Z+|Z33198}} <translate> === Language and text types === <!--T:18--> </translate> * {{Z+|Z86}} * {{Z+|Z6}} * {{Z+|Z60}} * {{Z+|Z11}} * {{Z+|Z31}} * {{Z+|Z12}} * {{Z+|Z32}} * {{Z+|Z89}} * {{Z+|Z14293}} * {{Z+|Z14294}} <translate> ==== Grammatical feature enums ==== <!--T:19--> </translate> * {{Z+|Z28516}} (<translate><!--T:20--> lightweight enum</translate>) * {{Z+|Z28519}} (<translate><!--T:21--> lightweight enum</translate>) * {{Z+|Z25502}} (<translate><!--T:22--> lightweight enum</translate>) * {{Z+|Z25340}} (<translate><!--T:23--> lightweight enum</translate>) * {{Z+|Z25501}} (<translate><!--T:24--> lightweight enum</translate>) * {{Z+|Z26935}} (<translate><!--T:25--> lightweight enum</translate>) * {{Z+|Z26934}} (<translate><!--T:26--> lightweight enum</translate>) * {{Z+|Z28215}} (<translate><!--T:27--> lightweight enum</translate>) * {{Z+|Z28515}} (<translate><!--T:28--> lightweight enum</translate>) * {{Z+|Z28517}} (<translate><!--T:29--> lightweight enum</translate>) * {{Z+|Z32792}} (<translate><!--T:43--> lightweight enum</translate>) * {{Z+|Z32789}} (<translate><!--T:44--> lightweight enum</translate>) * {{Z+|Z27970}} (<translate><!--T:30--> lightweight enum</translate>) * {{Z+|Z28518}} (<translate><!--T:31--> lightweight enum</translate>) * {{Z+|Z28520}} (<translate><!--T:32--> lightweight enum</translate>) * {{Z+|Z33568}} (<translate>lightweight enum</translate>) * {{Z+|Z27971}} (<translate><!--T:33--> lightweight enum</translate>) <translate> === Calendar types === <!--T:7--> ==== Gregorian calendar ==== <!--T:8--> </translate> * {{Z+|Z17402}} * {{Z+|Z16098}} * {{Z+|Z17813}} * {{Z+|Z20159}} * {{Z+|Z20342}} * {{Z+|Z20420}} <translate> ==== Hijri (Islamic) calendar ==== <!--T:34--> </translate> * {{Z+|Z26582}} (<translate><!--T:35--> lightweight enum</translate>) <translate> ==== Igbo calendar ==== <!--T:9--> </translate> * {{Z+|Z16927}} <translate> === Wikidata types === <!--T:10--> </translate> {{see also|Help:Wikidata#Statement model}} * {{Z+|Z6030}} <translate> ==== Wikidata entities ==== <!--T:11--> </translate> * {{Z+|Z6001}} * {{Z+|Z6002}} * {{Z+|Z6004}} * {{Z+|Z6005}} * {{Z+|Z6006}} <translate> ==== Wikidata references ==== <!--T:12--> </translate> * {{Z+|Z6091}} * {{Z+|Z6092}} * {{Z+|Z6094}} * {{Z+|Z6095}} * {{Z+|Z6096}} <translate> ==== Wikidata statements ==== <!--T:13--> </translate> * {{Z+|Z6020}} * {{Z+|Z6007}} * {{Z+|Z6003}} * {{Z+|Z6040}} * {{Z+|Z6008}} * {{Z+|Z6039}} <translate> ==== Wikidata datatypes ==== <!--T:36--> </translate> * {{Z+|Z6010}} * {{Z+|Z6011}} * {{Z+|Z6060}} * {{Z+|Z6061}} * {{Z+|Z6062}} (<translate><!--T:37--> lightweight enum</translate>) * {{Z+|Z6063}} (<translate><!--T:38--> lightweight enum</translate>) * {{Z+|Z6064}} <translate> === Miscellaneous === <!--T:39--> </translate> * {{Z+|Z27951}} (<translate><!--T:40--> lightweight enum</translate>) * {{Z+|Z28579}} * {{Z+|Z33827}} (<translate><!--T:45--> lightweight enum</translate>) <translate> === WikiLambda structure === <!--T:41--> </translate> * {{Z+|Z2}} * {{Z+|Z9}} * {{Z+|Z3}} * {{Z+|Z39}} * {{Z+|Z46}} * {{Z+|Z64}} * {{Z+|Z17}} * {{Z+|Z18}} * {{Z+|Z20}} * {{Z+|Z14}} * {{Z+|Z16}} * {{Z+|Z61}} <translate> ==== Evaluation ==== <!--T:42--> </translate> * {{Z+|Z7}} * {{Z+|Z22}} * {{Z+|Z5}} * {{Z+|Z50}} * {{Z+|Z99}} <translate> <!--T:3--> Other types can be used but there may be bugs. For a list of all types, see [[<tvar name="1">Special:ListObjectsByType/Z4</tvar>|the list of all types]] (though that does not include [[<tvar name="2">Special:ListObjectsByType/Z7</tvar>|persistent calls]] which return types, such as the lightweight enums, nor parameterised types such as <tvar name="3">{{Z|881}}</tvar>). <!--T:4--> New Types can be proposed on <tvar name="1">[[Wikifunctions:Type proposals]]</tvar>. == See also == <!--T:5--> </translate> * {{ll|Wikifunctions:Function model}} [[Category:Technical documentation{{#translation:}}|Type]] 1d8ipbtwmin93r8vy28sbn3cq0ybpty 0 30483 275750 274507 2026-05-17T10:20:42Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275750 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1922" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nan-latn-tailo", "Z60K2": [ "Z6", "nan-hntl-tailo" ] }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Minnan (Tâi-lô)" }, { "Z1K1": "Z11", "Z11K1": "Z1922", "Z11K2": "Bân-lâm-gú (Tâi-lô)" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "閩南語（臺羅）" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "闽南语（台罗）" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Nan (Tâi-lô)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "minnan en Tâi-lô" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 9p2vl3p2g6qkrw8ox9y0c4afega292b 0 33716 275752 200157 2026-05-17T10:25:36Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275752 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1924" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "isv-cyrl" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Interslavic (Cyrillic script)" }, { "Z1K1": "Z11", "Z11K1": "Z1924", "Z11K2": "меджусловјанскы" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Interslawisch (kyrillische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1181", "Z11K2": "међусловенски (ћирилица)" }, { "Z1K1": "Z11", "Z11K1": "Z1394", "Z11K2": "međuslovenski (ćirilica)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "interslave en écriture cyrillique" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ap89yongt9rnu5ii64yup9u1437qc77 0 33721 275754 132381 2026-05-17T10:29:46Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275754 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1929" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "abr" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Abron" }, { "Z1K1": "Z11", "Z11K1": "Z1929", "Z11K2": "Abron" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Abron" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "abron" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Bono", "Brong", "Bono Twi" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } som5m3dxenns947ta64mjeajrq6b6df 0 33722 275753 117309 2026-05-17T10:29:01Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275753 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1930" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "aii" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Suret" }, { "Z1K1": "Z11", "Z11K1": "Z1930", "Z11K2": "ܣܘܪܝܬ" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Assyrisch-neuaramäischer Dialekt" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "néo-araméen du Nord-Est" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Assyrian Neo-Aramaic" ] }, { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "soureth" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } c6l2oa64qzi2eqh4ejepmm4ane27fr7 0 34759 275755 118926 2026-05-17T10:30:30Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275755 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1932" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "hak-hans" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Hakka (Simplified Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z1932", "Z11K2": "客家语（简体）" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Hakka (vereinfachtes Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "hakka en sinogrammes simplifiés" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 20g22yi06qmd9ig2lzv6zdsalem4k2s 0 34760 275756 118927 2026-05-17T10:30:51Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275756 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1933" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "hak-hant" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Hakka (Traditional Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z1933", "Z11K2": "客家語（繁體）" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Hakka (traditionelles Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "hakka en sinogrammes traditionnels" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ajygt1hxmwbbsbl8r8vr6d76sbe4f7s 0 34761 275757 118928 2026-05-17T10:31:15Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275757 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1934" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "hak-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Hakka (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1934", "Z11K2": "Hak-kâ-ngî (Pha̍k-fa-sṳ)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Hakka (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "hakka en écriture latine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 2cn0osbnpyx7isv8we18i6w7f3x6g2y 0 37189 275705 219312 2026-05-17T08:47:25Z Ameisenigel 44 Removed Z18774, Z22986 und Z22987 from the approved list of test cases 275705 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18771" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z18771K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "value" } ] } } ], "Z8K2": "Z6", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14", "Z22985", "Z18773" ], "Z8K5": "Z18771" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Headline Case" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "convert a string to Headline Case" } ] } } 6w05r84fr4xk4gj4l1c2b6x20ciz9mj 275711 275705 2026-05-17T08:52:54Z Ameisenigel 44 Removed Z18773 und Z22985 from the approved list of implementations 275711 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18771" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z18771K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "value" } ] } } ], "Z8K2": "Z6", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z18771" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Headline Case" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "convert a string to Headline Case" } ] } } htr8hlflb8gfx9vzkpzx5x1rze3ihkc 0 37191 275710 170950 2026-05-17T08:52:12Z Ameisenigel 44 move to [[Z10251]] 275710 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18773" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z10251", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z600", "Z16K2": "function Z10251( Z10251K1 ) {\n return Z10251K1.split(' ').map(word =\u003E word.charAt(0).toUpperCase() + word.slice(1).toLowerCase()).join(' ');\n}" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Headline Case, javascript" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } dsf4an2sdclxe8i9qnet8u58v8rwu2f 275721 275710 2026-05-17T09:03:07Z Ameisenigel 44 de 275721 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18773" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z10251", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z600", "Z16K2": "function Z10251( Z10251K1 ) {\n return Z10251K1.split(' ').map(word =\u003E word.charAt(0).toUpperCase() + word.slice(1).toLowerCase()).join(' ');\n}" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Headline Case, javascript" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "in großen Anfangsbuchstaben in JavaScript" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 884eugfevz8qujowtfpfoou5k27arot 0 37192 275706 203391 2026-05-17T08:47:56Z Ameisenigel 44 move to [[Z10251]] 275706 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18774" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z10251", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z18771", "Z18771K1": "the quick brown fox jumps over the lazy dog" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K2": "The Quick Brown Fox Jumps Over The Lazy Dog" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "the quick brown fox ..." } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 21id2q9muqkvn0z5l6535zivwlomipy 275714 275706 2026-05-17T08:57:51Z Ameisenigel 44 de 275714 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18774" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z10251", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z18771", "Z18771K1": "the quick brown fox jumps over the lazy dog" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K2": "The Quick Brown Fox Jumps Over The Lazy Dog" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "the quick brown fox ..." }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "the quick brown fox... in großen Anfangsbuchstaben" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 2ieipgs5k83ucd9o3c30jkeyx013qjs 275719 275714 2026-05-17T09:02:31Z Ameisenigel 44 275719 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18774" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z10251", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z10251", "Z10251K1": "the quick brown fox jumps over the lazy dog" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K2": "The Quick Brown Fox Jumps Over The Lazy Dog" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "the quick brown fox ..." }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "the quick brown fox... in großen Anfangsbuchstaben" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } eik8g9ca2i25xji7ec7u1sh1ngvkmqs 0 38320 275700 125387 2026-05-17T08:38:36Z Ameisenigel 44 de 275700 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18901" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z18898", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z18898", "Z18898K1": "Replace this!", "Z18898K2": "Replace this!", "Z18898K3": "This is the replacement." }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K2": "This is the replacement." } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "replace an identical string" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Replace this!, Ersatz: This is the replacement." } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ilrd4ydlyar2ecoslt0kf140rvqhnwg 0 38321 275701 125389 2026-05-17T08:38:58Z Ameisenigel 44 de 275701 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18902" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z18898", "Z14K2": { "Z1K1": "Z7", "Z7K1": "Z802", "Z802K1": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K1": { "Z1K1": "Z18", "Z18K1": "Z18898K1" }, "Z866K2": { "Z1K1": "Z18", "Z18K1": "Z18898K2" } }, "Z802K2": { "Z1K1": "Z18", "Z18K1": "Z18898K3" }, "Z802K3": { "Z1K1": "Z18", "Z18K1": "Z18898K1" } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "echo or replace, composition" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Zeichenketten-Echo mit Ersetzung als Komposition" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } gjk6adlcwfa5de177muuhc3due1jkui 0 38322 275702 125391 2026-05-17T08:39:29Z Ameisenigel 44 de 275702 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18903" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z18898", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z610", "Z16K2": "def Z18898(Z18898K1, Z18898K2, Z18898K3):\n\tif Z18898K1==Z18898K2: return Z18898K3\n\treturn Z18898K1" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "echo or replace, python" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Zeichenketten-Echo mit Ersetzung in Python" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } q39ougtl1tzv5qswcdwneyaagap1dqb 0 38323 275703 125393 2026-05-17T08:39:52Z Ameisenigel 44 de 275703 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18904" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z18898", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z600", "Z16K2": "function Z18898( Z18898K1, Z18898K2, Z18898K3 ) {\n\tif (Z18898K1==Z18898K2) return(Z18898K3);\n\treturn(Z18898K1);\n}" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "echo or replace, javascript" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Zeichenketten-Echo mit Ersetzung in JavaScript" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 9xk6zipssi1yvibdqi8klfdo229lxoz 0 38443 275704 125936 2026-05-17T08:41:29Z Ameisenigel 44 de 275704 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z18910" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z13558", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z13558", "Z13558K1": [ "Z13518", { "Z1K1": "Z13518", "Z13518K1": "2" }, { "Z1K1": "Z13518", "Z13518K1": "3" }, { "Z1K1": "Z13518", "Z13518K1": "5" }, { "Z1K1": "Z13518", "Z13518K1": "7" }, { "Z1K1": "Z13518", "Z13518K1": "11" }, { "Z1K1": "Z13518", "Z13518K1": "13" }, { "Z1K1": "Z13518", "Z13518K1": "17" }, { "Z1K1": "Z13518", "Z13518K1": "19" }, { "Z1K1": "Z13518", "Z13518K1": "23" }, { "Z1K1": "Z13518", "Z13518K1": "29" } ] }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z13522", "Z13522K2": { "Z1K1": "Z13518", "Z13518K1": "6469693230" } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "product of primes \u003C 30" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Produkt von [2,3,5,7,11,13,17,19,23,29]" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 909joq4rybe207075ddemqaboccjryj 0 40363 275751 131027 2026-05-17T10:21:36Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275751 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1938" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "bgc-arab" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Haryanvi (Arabic script)" }, { "Z1K1": "Z11", "Z11K1": "Z1938", "Z11K2": "ہریانوی" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Haryanvi (arabische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "haryanvi en écriture arabe" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 0g3gf726gsxqqva1kixsnwhhg3y0o8u 4 41955 275553 266642 2026-05-16T19:49:03Z YoshiRulz 10156 Overhaul with new bespoke categorisation 275553 wikitext text/x-wiki * {{Z+|Z881}} == Properties == <!-- type --> * {{Z+|Z18636}} <!-- length --> * {{Z+|Z12681}} ** {{Z+|Z30164}} *** {{Z+|Z813}} **** {{Z+|Z23120}} **** {{Z+|Z30075}} *** {{Z+|Z32302}} *** {{Z+|Z12755}} *** {{Z+|Z12759}} *** {{Z+|Z12864}} **** {{Z+|Z13310}} **** {{Z+|Z21212}} **** {{Z+|Z12851}} ** {{Z+|Z31612}} ** {{Z+|Z31605}} * {{Z+|Z31592}} <!-- contains --> * {{Z+|Z12696}} ** {{Z+|Z34367}} ** {{Z+|Z12738}} *** {{Z+|Z13752}} *** {{Z+|Z12698}} ** {{Z+|Z12735}} *** {{Z+|Z12684}} ** {{Z+|Z34378}} ** {{Z+|Z12846}} *** {{Z+|Z34380}} *** {{Z+|Z12741}} <!-- equals --> * {{Z+|Z889}} ** {{Z+|Z18646}} *** {{Z+|Z24166}} ** {{Z+|Z34273}} ** {{Z+|Z31013}} *** {{Z+|Z31019}} *** {{Z+|Z10393}} *** {{Z+|Z31026}} <!-- count --> * {{Z+|Z29413}} ** {{Z+|Z31600}} ** {{Z+|Z22874}} ** {{Z+|Z34793}} *** {{Z+|Z29409}} <!-- indexOf --> * {{Z+|Z13708}} ** {{Z+|Z28715}} ** {{Z+|Z19536}} ** {{Z+|Z31575}} *** {{Z+|Z31583}} <!-- startsWith --> * {{Z+|Z21613}} ** {{Z+|Z31294}} ** {{Z+|Z30975}} *** {{Z+|Z30977}} *** {{Z+|Z31002}} <!-- endsWith --> * {{Z+|Z31758}} ** {{Z+|Z31763}} ** {{Z+|Z30976}} *** {{Z+|Z30978}} *** {{Z+|Z31003}} == Indexing/slicing == <!-- first --> * {{Z+|Z811}} ** {{Z+|Z22839}} ** {{Z+|Z13366}} *** {{Z+|Z24203}} * {{Z+|Z29446}} ** {{Z+|Z16360}} <!-- last --> * {{Z+|Z12964}} ** {{Z+|Z13362}} <!-- nth --> * {{Z+|Z13397}} ** {{Z+|Z26904}} ** {{Z+|Z30282}} *** {{Z+|Z31587}} ** {{Z+|Z26556}} ** {{Z+|Z31809}} *** {{Z+|Z28735}} <!-- dropFirst --> * {{Z+|Z812}} ** {{Z+|Z13369}} *** {{Z+|Z31874}} <!-- dropLast --> * {{Z+|Z12967}} ** {{Z+|Z13373}} ** {{Z|Z18284}} == Removal/filtering == <!-- remove --> * {{Z+|Z12856}} ** {{Z+|Z13081}} *** {{Z|Z18291}} ** {{Z+|Z22865}} ** {{Z+|Z34538}} ** {{Z+|Z19205}} *** {{Z+|Z13078}} *** {{Z+|Z19202}} ** {{Z+|Z31874}} <!-- removeAt --> * {{Z+|Z31364}} ** {{Z+|Z13429}} ** {{Z+|Z13369}} ** {{Z+|Z13373}} ** {{Z+|Z29400}} *** {{Z+|Z18194}} <!-- filter with predicate --> * {{Z+|Z872}} ** {{Z+|Z33453}} ** {{Z+|Z21809}} ** {{Z+|Z28316}} <!-- filter by key --> * {{Z+|Z27413}} ** {{Z+|Z33105}} *** {{Z+|Z24849}} **** {{Z+|Z24855}} == Substitution/transformation == <!-- un/type --> * {{Z|Z15142}} (no-op) * {{Z+|Z18729}} ** {{Z+|Z18475}} ** {{Z+|Z17895}} *** {{Z+|Z28691}} <!-- substituteAt --> * {{Z+|Z31369}} <!-- map --> * {{Z+|Z873}} ** {{Z+|Z24846}} ** {{Z+|Z32453}} ** {{Z+|Z32806}} == Insertion == <!-- prepend --> * {{Z+|Z810}} ** {{Z+|Z24285}} ** {{Z+|Z31721}} <!-- append --> * {{Z+|Z18597}} ** {{Z+|Z12961}} *** {{Z+|Z24150}} *** {{Z|Z18276}} ** {{Z+|Z34519}} ** {{Z+|Z24655}} ** {{Z+|Z33720}} <!-- insert --> * {{Z+|Z31345}} ** {{Z+|Z31340}} ** {{Z+|Z33646}} <!-- concat --> * {{Z+|Z12767}} ** {{Z+|Z18755}} *** {{Z|Z18288}} ** {{Z+|Z27665}} ** {{Z+|Z34538}} == Generation == <!-- list from element --> * {{Z+|Z14046}} ** {{Z+|Z27685}} ** {{Z+|Z24291}} ** {{Z+|Z21389}} <!-- from range --> * {{Z+|Z21821}} ** {{Z+|Z23921}} *** {{Z+|Z24387}} *** {{Z+|Z24382}} <!-- product of lists --> * {{Z+|Z29286}} ** {{Z+|Z29324}} <!-- power set --> * {{Z+|Z18194}} == Ordering and grouping == <!-- reverse --> * {{Z+|Z18759}} ** {{Z+|Z12668}} ** {{Z+|Z18479}} ** {{Z|Z17770}} ** {{Z|Z17774}} ** {{Z|Z17778}} * {{Z+|Z24176}} <!-- cycle --> * {{Z+|Z31355}} ** {{Z+|Z25526}} ** {{Z+|Z22179}} <!-- sort by key --> * {{Z+|Z29725}} * {{Z+|Z19510}} <!-- sort with comparator --> * {{Z+|Z27612}} ** {{Z+|Z17873}} *** {{Z+|Z29429}} ** {{Z+|Z17869}} ** {{Z+|Z12671}} ** {{Z+|Z18281}} <!-- shuffle --> * {{Z+|Z29400}} * {{Z+|Z13247}} <!-- group --> * {{Z+|Z30157}} ** {{Z+|Z32585}} * {{Z+|Z34790}} ** {{Z+|Z30865}} <!-- chunk --> * {{Z+|Z29795}} * {{Z+|Z13224}} <!-- reduce --> * {{Z|Z876}} (actually left-associative ''fold'') ** {{Z|Z12781}} (actually left-associative ''reduce'') *** {{Z|Z20089}} w/ initial empty check ** {{Z|Z12753}} (actually right-associative ''reduce'') <!-- flatten --> * {{Z+|Z12676}} ** {{Z+|Z23606}} ** {{Z+|Z27665}} *** {{Z+|Z32453}} ** {{Z+|Z13155}} == Matrix math == Since we don't have specific types for vectors or matrices, vectors are represented as a list and matrices as a list of lists (to be interpreted as a list of rows). <!-- properties --> * {{Z+|Z31747}} ** {{Z+|Z31752}} * {{Z+|Z24166}} ** {{Z+|Z24171}} <!-- indexing --> * {{Z+|Z31587}} ** {{Z+|Z31585}} <!-- removal --> <!-- transformation --> * {{Z+|Z32806}} * {{Z+|Z31818}} * {{Z+|Z24055}} ** {{Z+|Z17670}} *** {{Z+|Z17675}} ** {{Z+|Z24162}} * {{Z+|Z24060}} ** {{Z+|Z24436}} * {{Z+|Z24185}} ** {{Z+|Z20659}} * {{Z+|Z21903}} * {{Z+|Z24239}} ** {{Z+|Z31749}} * {{Z+|Z24346}} ** {{Z+|Z24342}} * {{Z+|Z14046}} ** {{Z+|Z24177}} * {{Z+|Z29301}} ** {{Z+|Z24182}} * {{Z+|Z24191}} * {{Z+|Z24236}} * {{Z+|Z29308}} <!-- insertion --> * {{Z+|Z810}} ** {{Z+|Z24285}} ** {{Z+|Z24299}} * {{Z+|Z18597}} <!-- ordering --> * {{Z+|Z18759}} * {{Z+|Z24176}} <!-- generation --> * {{Z+|Z24291}} (useful for creating 1x1 matrixes) ** {{Z+|Z24251}} * {{Z+|Z24290}} * {{Z+|Z29286}} ** {{Z+|Z29324}} == Functions expecting a list argument == * [[Special:Search/: "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1"|Complete list of functions]] ** [[Special:Search/: "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1" !"Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1"| Functions specifying a “properly typed” list argument]] ** [[Special:Search/: "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1"|Functions not specifying the type for their list argument (Z1-typed or “untyped”)]] == Functions with list outputs == *[[Special:Search/: "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1"|Complete list of functions]] **[[Special:Search/: "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1" !"Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1|Functions specifying a “properly typed” output list]] **[[Special:Search/: "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1"|Functions not specifying the type for the output list (Z1-typed or “untyped”)]] # If a function specifies an output list with a type other than [[Z1]] (that is, it specifies a "properly typed" list), mismatched elements cause an error if the implementation is in code. # If all objects in an output list have the same type, the list takes that type instead of being Z1-typed. This only happens if the implementation is in code. For compositions, you can use {{Z|Z18475}} to get the same result. #If a code implementation needs custom-converted objects (provided by a {{Z|Z46}}), any list input must be properly typed (objects in a Z1-typed list are not converted). Similarly, any list output must be properly typed (not [[Z1]] in the function specification) or else conversion into a Wikifunctions object will fail. #If a code implementation does not need converted objects, you can use {{Z|Z28691}} to convert a properly typed list to Z1-typed (but this is [[Wikifunctions:Project_chat/Archive/2024/07#Typed_lists_now_open_beyond_Booleans_and_Strings|not officially supported]]). (The list will remain properly typed if there are no custom converters to code. Use {{Z|Z17895}} to make the list Z1-typed unconditionally.) [[Category:Lists of functions]] fwwb1wst7ejp5malnuhza9he9qcgfj7 4 41957 275530 274796 2026-05-16T16:23:05Z YoshiRulz 10156 /* Floating point functions */ Add some predicate functions 275530 wikitext text/x-wiki == Numeric Characteristics == * {{Z+|Z15818}} * {{Z+|Z23883}} * {{Z+|Z12427}} * {{Z+|Z14953}} * {{Z+|Z14961}} * {{Z+|Z15190}} * {{Z+|Z15276}} * {{Z+|Z15735}} * {{Z+|Z15741}} * {{Z+|Z15251}} * {{Z+|Z14933}} * {{Z+|Z14999}} * {{Z+|Z14980}} * {{Z+|Z14966}} * {{Z+|Z15265}} * {{Z+|Z13726}} * {{Z+|Z15007}} * {{Z+|Z12636}} * {{Z+|Z14683}} * {{Z+|Z15757}} * {{Z+|Z14783}} * {{Z+|Z15617}} * {{Z+|Z15282}} * {{Z+|Z14792}} * {{Z+|Z15201}} * {{Z+|Z14815}} * {{Z+|Z14810}} * {{Z+|Z14976}} * {{Z+|Z15031}} * {{Z+|Z14971}} * {{Z+|Z15151}} * {{Z+|Z15127}} * {{Z+|Z14924}} * {{Z+|Z15443}} * {{Z+|Z14946}} * {{Z+|Z14938}} * {{Z+|Z15018}} * {{Z+|Z15241}} * {{Z+|Z15218}} * {{Z+|Z15013}} * {{Z+|Z15121}} * {{Z+|Z15050}} * {{Z+|Z15055}} * {{Z+|Z15186}} * {{Z+|Z15224}} * {{Z+|Z14958}} * {{Z+|Z15195}} * {{Z+|Z15228}} * {{Z+|Z14991}} ===Comparisons=== * {{Z+|Z13522}} ** {{Z+|Z15849}} * {{Z+|Z13676}} * {{Z+|Z13682}} * {{Z+|Z13689}} * {{Z+|Z13695}} * {{Z+|Z16731}} * {{Z+|Z13701}} * {{Z+|Z13740}} * {{Z+|Z20266}} * {{Z+|Z13555}} * {{Z+|Z34353}} * {{Z+|Z16773}} * {{Z+|Z17628}} * {{Z+|Z27811}} ** {{Z+|Z27815}} ===Selections=== * {{Z+|Z13630}} * {{Z+|Z13633}} * {{Z+|Z19509}} * {{Z+|Z29429}} ==== Arithmetic Functions ==== * {{Z+|Z12971}} * {{Z+|Z12975}} * {{Z+|Z13521}} * {{Z+|Z13578}} * {{Z+|Z13539}} ** [[Z15107]] * {{Z+|Z13546}} ** [[Z15111]] * {{Z+|Z13551}} * {{Z+|Z13576}} * {{Z+|Z13569}} * {{Z+|Z17315}} * {{Z+|Z13582}} * {{Z+|Z13612}} * {{Z+|Z13660}} * {{Z+|Z13647}} ** [[Z13663]], [[Z13977]], [[Z13979]], [[Z13809]], [[Z13644]], [[Z13948]], [[Z13963]], [[Z13969]] * {{Z+|Z15257}} * {{Z+|Z15256}} * {{Z+|Z14732}} * {{Z+|Z13667}} * {{Z+|Z15143}} * {{Z+|Z15163}} * {{Z+|Z13995}} ** {{Z+|Z13997}} * {{Z+|Z13818}} * {{Z+|Z13822}} * {{Z+|Z13848}} ** {{Z+|Z14007}} * {{Z+|Z13854}} * {{Z+|Z16762}} * {{Z+|Z15108}} * {{Z+|Z14742}} * {{Z+|Z14860}} * {{Z+|Z15318}} * {{Z+|Z14894}} * {{Z+|Z15341}} * {{Z+|Z14900}} * {{Z+|Z14905}} * {{Z+|Z14847}} * {{Z+|Z15075}} * {{Z+|Z15085}} * {{Z+|Z13831}} ** {{Z+|Z14209}} ==== Natural number sequences and unary natural number functions ==== See [[Wikifunctions:OEIS]] * {{Z+|Z12636}} * {{Z+|Z13561}} * {{Z+|Z14058}} * {{Z+|Z14066}} * {{Z+|Z13857}} * {{Z+|Z15044}} * {{Z+|Z13957}} * {{Z+|Z13955}} * {{Z+|Z15302}} * {{Z+|Z14629}} * {{Z+|Z14917}} * {{Z+|Z15119}} * {{Z+|Z15232}} * {{Z+|Z14871}} * {{Z+|Z15075}} * {{Z+|Z15085}} * {{Z+|Z15080}} * {{Z+|Z15061}} * {{Z+|Z14876}} * {{Z+|Z13843}} * {{Z+|Z15386}} * {{Z+|Z15047}} * {{Z+|Z14888}} * {{Z+|Z14864}} * {{Z+|Z13989}} * {{Z+|Z15157}} * {{Z+|Z13735}} ==== Bitwise Functions ==== * {{Z+|Z13651}} * {{Z+|Z13652}} * {{Z+|Z13653}} * {{Z+|Z13812}} * {{Z+|Z13813}} * {{Z+|Z13860}} * {{Z+|Z13928}} ==== Number conversions ==== ===== By base ===== * {{Z+|Z12982}} * {{Z+|Z12987}} * {{Z+|Z13779}} * {{Z+|Z13780}} * {{Z+|Z13781}} * {{Z+|Z15671}} * {{Z+|Z13782}} * {{Z+|Z13783}} * {{Z+|Z13784}} * {{Z+|Z13797}} * {{Z+|Z13798}} * {{Z+|Z13799}} * {{Z+|Z13806}} * {{Z+|Z31177}} ===== By system ===== * {{Z+|Z17065}} * {{Z+|Z11022}} * {{Z+|Z11023}} * {{Z+|Z18515}} * {{Z+|Z18489}} * {{Z+|Z18504}} * {{Z+|Z14018}} * {{Z+|Z22294}} * {{Z+|Z22649}} * {{Z+|Z22285}} * {{Z+|Z22288}} * {{Z+|Z22291}} == Integer functions == {{Help:Type deconstruction table/Integer}} {{Help:Type conversion table/Integer}} * {{Z+|Z16688}} * {{Z+|Z17249}} * {{Z+|Z17254}} * {{Z+|Z17186}} * {{Z+|Z17153}} * {{Z+|Z17160}} * {{Z+|Z16693}} * {{Z+|Z17111}} * {{Z+|Z17120}} * {{Z+|Z15844}} * {{Z+|Z17105}} * {{Z+|Z17204}} * {{Z+|Z17239}} * {{Z+|Z12480}} * {{Z+|Z12429}} * {{Z+|Z17215}} * {{Z+|Z17229}} * {{Z+|Z17132}} * {{Z+|Z17173}} * {{Z+|Z17140}} * {{Z+|Z17363}} * {{Z+|Z16700}} ** {{Z+|Z25073}} * {{Z+|Z17151}} * {{Z+|Z17128}} * {{Z+|Z17101}} * {{Z+|Z17267}} * {{Z+|Z17144}} * {{Z+|Z17167}} ** {{Z+|Z25196}} ** {{Z+|Z26858}} * {{Z+|Z32261}} * {{Z+|Z17263}} * {{Z+|Z17376}} * {{Z+|Z17380}} ===Integer functions using set-theoretic representation with pairs of natural numbers=== see [[w:Integer#Equivalence classes of ordered pairs]] * {{Z|Z17307}} * {{Z|Z17301}} * {{Z|Z17321}} * {{Z|Z17326}} * {{Z|Z17330}} * {{Z|Z17340}} * {{Z|Z17469}} * {{z|Z17345}} ===Integer sequence and unary integer functions=== See [[Wikifunctions:OEIS]] * {{Z|Z17386}} * {{z|Z17394}} * {{Z+|Z31619}} ===Search for=== [[Special:Search/: "Z8K2 Z16683" OR "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z16683" OR "Z17K1 Z16683" OR "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z16683"|Functions expecting or returning an explicit Integer object, singly or in a list]] * [[Special:Search/: "Z8K2 Z16683"|Functions returning an explicit Integer object]] ** [[Special:Search/: "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z16683"|or a list of them]] * [[Special:Search/: "Z17K1 Z16683"|Functions expecting an explicit Integer object]] ** [[Special:Search/: "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z16683"|or a list of them]] * [[Special:Search/: "Z8K2 Z16683" "Z17K1 Z16683"|Functions expecting and returning explicit Integer objects (but not in a list)]] * [[Special:Search/: "Z8K2 Z16683" !"Z17K1 Z16683"|Functions with no Integer object inputs (unless in a list) returning an explicit Integer object (not in a list)]] ==Rational number functions== {{Help:Type deconstruction table/Rational}} === Comparison === * {{Z+|Z19686}} * {{Z+|Z24506}} * {{Z+|Z19751}} * {{Z+|Z19752}} * {{Z+|Z19753}} * {{Z+|Z19754}} * {{Z+|Z24403}} * {{Z+|Z19806}} ===Properties=== * {{Z+|Z20065}} * {{Z+|Z21702}} * {{Z+|Z19922}} * {{Z+|Z21714}} * {{Z+|Z21721}} * {{Z+|Z19583}} * {{Z+|Z25642}} ** {{Z+|Z25647}} === Transformation and conversion === {{Help:Type conversion table/Rational}} * {{Z+|Z19694}} * {{Z+|Z19711}} * {{Z+|Z19717}} * {{Z+|Z19722}} * {{Z+|Z19733}} * {{Z+|Z19724}} * {{Z+|Z19744}} * {{Z+|Z19848}} * {{Z+|Z20584}} * {{Z+|Z27232}} * {{Z+|Z24382}} * {{Z+|Z25445}} * {{Z+|Z25656}} ** {{Z+|Z25636}} ** {{Z+|Z25639}} ** {{Z+|Z29116}} * {{Z+|Z27737}} === Rounding === {{Help:Rounding_function_table/Rational}} === Operations === * {{Z+|Z19679}} * {{Z+|Z19699}} * {{Z+|Z19706}} * {{Z+|Z19708}} * {{Z+|Z21320}} * {{Z+|Z24487}} * {{Z+|Z19682}} ** {{Z+|Z25432}} * {{Z+|Z20032}} * {{Z+|Z20053}} * {{Z+|Z31523}} ** {{Z+|Z19736}} * {{Z+|Z31522}} ** {{Z+|Z19740}} * {{Z+|Z19800}} * {{Z+|Z27705}} ** {{Z+|Z27719}} ** {{Z+|Z19814}} ** {{Z+|Z19841}} ** {{Z+|Z12606}} * {{Z+|Z19826}} * {{Z+|Z19833}} ** {{Z+|Z33933}} * {{Z+|Z20856}} * {{Z+|Z20863}} * {{Z+|Z20870}} * {{Z+|Z20877}} * {{Z+|Z24081}} * {{Z+|Z20902}} * {{Z+|Z21692}} * {{Z+|Z23899}} * {{Z+|Z23882}} * {{Z+|Z24372}} * {{Z+|Z24374}} * {{Z+|Z24376}} ==== Operations with custom precision ==== * {{Z+|Z24505}} * {{Z+|Z24681}} * {{Z+|Z24698}} ===Probability Operations=== * {{Z+|Z19967}} * {{Z+|Z20000}} * {{Z+|Z20226}} ====Probability mass functions==== * {{Z+|Z21294}} * {{Z+|Z20094}} * {{Z+|Z21312}} ==Floating point functions== ===Properties=== *{{Z+|Z21136}} *{{Z+|Z21139}} *{{Z+|Z21142}} *{{Z+|Z21145}} *{{Z+|Z22636}} *{{Z+|Z33615}} *{{Z+|Z34827}} ===Conversions=== *{{Z+|Z20854}} *{{Z+|Z21148}} *{{Z+|Z20915}} *{{Z+|Z21642}} *{{Z+|Z21925}} *{{Z+|Z21163}} *{{Z+|Z20844}} *{{Z+|Z21679}} *{{Z+|Z20936}} *{{Z+|Z20937}} *{{Z+|Z21071}} *{{Z+|Z21070}} ===Comparisons=== *{{Z+|Z20850}} *{{Z+|Z20924}} *{{Z+|Z20940}} *{{Z+|Z20941}} *{{Z+|Z20943}} *{{Z+|Z20944}} *{{Z+|Z20945}} ===Rounding=== {{Help:Rounding_function_table/float64}} ===Operations=== *{{Z+|Z20849}} *{{Z+|Z21031}} *{{Z+|Z21032}} *{{Z+|Z21033}} *{{Z+|Z16463}} *{{Z+|Z12473}} *{{Z+|Z16475}} *{{Z+|Z20954}} *{{Z+|Z20955}} *{{Z+|Z20956}} *{{Z+|Z12505}} *{{Z+|Z12497}} *{{Z+|Z20959}} *{{Z+|Z20960}} *{{Z+|Z20961}} *{{Z+|Z20962}} *{{Z+|Z20963}} *{{Z+|Z20964}} *{{Z+|Z20965}} *{{Z+|Z20966}} *{{Z+|Z20967}} *{{Z+|Z20968}} *{{Z+|Z12509}} *{{Z+|Z12500}} *{{Z+|Z20971}} *{{Z+|Z20972}} *{{Z+|Z20973}} *{{Z+|Z20974}} *{{Z+|Z21000}} *{{Z+|Z21001}} *{{Z+|Z21003}} *{{Z+|Z21004}} *{{Z+|Z21005}} *{{Z+|Z21005}} *{{Z+|Z21007}} *{{Z+|Z21008}} *{{Z+|Z21009}} *{{Z+|Z21010}} *{{Z+|Z21012}} *{{Z+|Z21013}} *{{Z+|Z29125}} *{{Z+|Z21028}} *{{Z+|Z21037}} *{{Z+|Z21041}} *{{Z+|Z34780}} *{{Z+|Z20841}} *{{Z+|Z21043}} *{{Z+|Z21047}} **{{Z+|Z26304}} ***{{Z+|Z26315}} *{{Z+|Z21775}} *{{Z+|Z23902}} * {{Z+|Z31079}} === Search for === [[Special:Search/ : "Z8K2 Z20838" OR "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z20838" OR "Z17K1 Z20838" OR "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z20838"| Functions expecting or returning an explicit Float64 object, singly or in a list]] * [[Special:Search/ : "Z8K2 Z20838"|Functions returning an explicit Float64 object]] ** [[Special:Search/ : "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z20838"|or a list of them]] * [[Special:Search/ : "Z17K1 Z20838"|Functions expecting an explicit Float64 object]] ** [[Special:Search/ : "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z20838"|or a list of them]] * [[Special:Search/ : "Z8K2 Z20838" "Z17K1 Z20838"| Functions expecting and returning an explicit Float64 object]] ** [[Special:Search/ : "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z20838" "Z17K1 Z20838"| or returning a list]] ** [[Special:Search/ : "Z8K2 Z20838" "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z20838"|or expecting a list]] ** [[Special:Search/ : "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z20838" "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z20838"|or expecting and returning a list]] == Complex numbers == Type: {{Z+|Z33198}} {{Help:Type deconstruction table/complex128}} === Constructor and deconstructors === * {{Z+|Z33227}} * {{Z+|Z33304}} * {{Z+|Z33214}} * {{Z+|Z33221}} * {{Z+|Z33499}} ** {{Z+|Z33713}} * {{Z+|Z33610}} === Comparison === * {{Z+|Z33202}} * {{Z+|Z33506}} === Arithmetics === * {{Z+|Z33201}} * {{Z+|Z33366}} * {{Z+|Z33700}} ** {{Z+|Z35072}} * {{Z+|Z33708}} ** {{Z+|Z35073}} * {{Z+|Z33372}} * {{Z+|Z33679}} == Number operations requiring type conversion == === Numeric Characteristics === * {{Z+|Z10603}} === Arithmetic Functions === * {{Z+|Z11235}} * {{Z+|Z12522}} * {{Z+|Z12476}} * {{Z+|Z10862}} * {{Z+|Z12720}} === Trigonometric Functions === * {{Z+|Z12497}} * {{Z+|Z12500}} * {{Z+|Z12505}} * {{Z+|Z12509}} * {{Z+|Z12473}} * {{Z+|Z14446}} === Health Functions === * {{Z+|Z12526}} * {{Z+|Z12572}} === Geometric Functions === * {{Z+|Z13341}} === Climate related functions === These would benefit from a float type. * {{Z+|Z18421}} * {{Z+|Z18391}} * {{Z+|Z18364}} * {{Z+|Z18406}} * {{Z+|Z18409}} * {{Z+|Z18412}} * {{Z+|Z18415}} * {{Z+|Z18418}} === Distance functions === * {{Z+|Z18428}} * {{Z+|Z18431}} * {{Z+|Z18362}} === Physics functions === * {{Z+|Z12910}} === Randomness === {{main|Wikifunctions:Determinism}} ''Reminder that Wikifunctions does not support randomness for now. We always expect all functions to return functional, deterministic results, only dependent on the input. This is in order to allow for aggressive caching.'' see [[Wikifunctions:Project_chat/Archive/2023/09#Help_please]]. * {{Z+|Z13148}} * {{Z+|Z19441}} * {{Z+|Z19460}} [[Category:Lists of functions]] frfxyal5qn8o8c712hs9jtv4akcftbo 0 43993 275759 143723 2026-05-17T10:33:10Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275759 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1952" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "bax-bamu" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Bamun (Bamu script)" }, { "Z1K1": "Z11", "Z11K1": "Z1952", "Z11K2": "ꚶꛉ꛰꛲ꚫꛦꚳ" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Bamun (Bamun-Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "bamoun en écriture bamoun" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } i9pl4h5itvv9mfomci1kef4qwb2ab85 0 43995 275758 275484 2026-05-17T10:31:43Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275758 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1954" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "cdo-hant" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Mindong (Traditional Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z1954", "Z11K2": "閩東語（傳統漢字）" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Dong (traditionelle Han-Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "閩東語（傳統漢字）" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "闽东语（传统汉字）" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "मिन-दोंग (पारंपरिक हान लिपि)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "mindong en sinogrammes traditionnels" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } pvxw0by5rg0fj7w0xgmu2rl4ul8quee 0 43996 275735 237257 2026-05-17T10:04:40Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275735 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1955" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "cdo-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Mindong (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1955", "Z11K2": "Mìng-dĕ̤ng-ngṳ̄ (Bàng-uâ-cê)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Dong (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1672", "Z11K2": "閩東語（平話字）" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "闽东语（平话字）" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "मिन-दोंग (लातिन लिपि)" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Mindong (aksara Latin)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "mindong en écriture latine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "Mindong (aksara Latin)" } ] } } 2nezmd21aiprf7iine0uqzgg6qtf7e0 2 44040 275637 209463 2026-05-17T04:27:32Z Jérémy-Günther-Heinz Jähnick 6055 /* 3° : Functions */ 275637 wikitext text/x-wiki {{#babel:fr-N|en-2}} [[File:Merksem (Antwerpen) - Antwerpse Havenpijl, zondag 9 augustus 2015 (B27).jpg|thumb]] == Translations == === 1° : Babel === <code><nowiki>{{#babel:fr-N|en-2}}</nowiki></code> === 2° : Texts === * {{Z|Z1}} • {{Z|Z2}} • {{Z|Z3}} • {{Z|Z4}} • {{Z|Z5}} • {{Z|Z6}} • {{Z|Z7}} • {{Z|Z8}} • {{Z|Z9}} • {{Z|Z11}} • {{Z|Z12}} • {{Z|Z14}} • ... === 3° : Functions === * [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z0000|Z0000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z1000|Z1000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z2000|Z2000]] • <!--[[User:Jérémy-Günther-Heinz Jähnick/Translations/Z3000|Z3000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z4000|Z4000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z5000|Z5000]] • -->[[User:Jérémy-Günther-Heinz Jähnick/Translations/Z6000|Z6000]] • <!--[[User:Jérémy-Günther-Heinz Jähnick/Translations/Z7000|Z7000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z8000|Z8000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z9000|Z9000]] • -->[[User:Jérémy-Günther-Heinz Jähnick/Translations/Z10000|Z10000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z11000|Z11000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z12000|Z12000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z13000|Z13000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z14000|Z14000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z15000|Z15000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z16000|Z16000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z17000|Z17000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z18000|Z18000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z19000|Z19000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z20000|Z20000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z21000|Z21000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z22000|Z22000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z23000|Z23000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z24000|Z24000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z25000|Z25000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z26000|Z26000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z27000|Z27000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z28000|Z28000]] • [[User:Jérémy-Günther-Heinz Jähnick/Translations/Z29000|Z29000]] === 4° : Wikidata properties === * [[:d:User:Jérémy-Günther-Heinz Jähnick/Translations/P1 → P4999|P1 → P4999]] • [[:d:User:Jérémy-Günther-Heinz Jähnick/Translations/P5000 → P9999|P5000 → P9999]] • [[:d:User:Jérémy-Günther-Heinz Jähnick/Translations/P10000 → P14999|P10000 → P14999]] == Ideas == * Develop shared infoboxes useable by different Wikipedias, for persons, places, sports... * Develop shared tables for populations, lists of mayors, twin cities... 9d7irgaf1hp09o8h721g3q68jj97267 0 45506 275657 267637 2026-05-17T05:29:18Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275657 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z20838" }, "Z2K2": { "Z1K1": "Z4", "Z4K1": "Z20838", "Z4K2": [ "Z3", { "Z1K1": "Z3", "Z3K1": "Z16659", "Z3K2": "Z20838K1", "Z3K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "sign" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "signe" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "চিহ্ন" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Vorzeichen" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "segno" }, { "Z1K1": "Z11", "Z11K1": "Z1181", "Z11K2": "знак" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "tanda" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "चिह्न" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "teken" } ] }, "Z3K4": { "Z1K1": "Z40", "Z40K1": "Z42" } }, { "Z1K1": "Z3", "Z3K1": "Z16683", "Z3K2": "Z20838K2", "Z3K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "exponent" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "exposant" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "সূচক" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Exponent" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "esponente" }, { "Z1K1": "Z11", "Z11K1": "Z1181", "Z11K2": "експонент" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "eksponen" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "घातांक" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "exponent" } ] }, "Z3K4": { "Z1K1": "Z40", "Z40K1": "Z42" } }, { "Z1K1": "Z3", "Z3K1": "Z13518", "Z3K2": "Z20838K3", "Z3K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "significand (fractional part)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "signifiant" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "সহগ" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Mantisse" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "mantissa" }, { "Z1K1": "Z11", "Z11K1": "Z1181", "Z11K2": "фракција" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "mantisa" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "गुणांक" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "mantisse " } ] }, "Z3K4": { "Z1K1": "Z40", "Z40K1": "Z42" } }, { "Z1K1": "Z3", "Z3K1": "Z20825", "Z3K2": "Z20838K4", "Z3K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "special value" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "valeur spéciale" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "বিশেষ মান" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "spezieller Wert" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "valore speciale" }, { "Z1K1": "Z11", "Z11K1": "Z1181", "Z11K2": "посебна вредност" }, { "Z1K1": "Z11", "Z11K1": "Z1078", "Z11K2": "nilai khusus" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "विशेष मान" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "speciale waarde" } ] }, "Z3K4": { "Z1K1": "Z40", "Z40K1": "Z42" } } ], "Z4K3": "Z101", "Z4K4": "Z20850", "Z4K5": "Z21956", "Z4K6": "Z21925", "Z4K7": [ "Z46", "Z28867", "Z28865" ], "Z4K8": [ "Z64", "Z28866", "Z28845" ] }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "float64" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "nombre à virgule flottante double précision " }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "ফ্লোট" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Float64" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "float64" }, { "Z1K1": "Z11", "Z11K1": "Z1181", "Z11K2": "број са покретним зарезом" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "float64" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "64-bits zwevendekommagetal " }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "float64" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "64位浮点数" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "float", "decimal", "double", "FP64", "binary64", "f64", "DOUBLE-FLOAT", "real64", "floating point" ] }, { "Z1K1": "Z31", "Z31K1": "Z1011", "Z31K2": [ "Z6", "ফ্লোট৬৪", "ভাসমান বিন্দু সংখ্যা", "দশমিক", "ভগ্নাংশ" ] }, { "Z1K1": "Z31", "Z31K1": "Z1430", "Z31K2": [ "Z6", "doppelte Genauigkeit" ] }, { "Z1K1": "Z31", "Z31K1": "Z1181", "Z31K2": [ "Z6", "број са плутајућом тачком", "број са покретном тачком", "флоат", "број у покретном зарезу", "број са плутајућим зарезом", "IEEE754" ] }, { "Z1K1": "Z31", "Z31K1": "Z1157", "Z31K2": [ "Z6", "64-bits drijvendekommagetal" ] }, { "Z1K1": "Z31", "Z31K1": "Z1830", "Z31K2": [ "Z6", "フロート64", "倍精度浮動小数点数" ] }, { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "float64" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Representation of a number in 64 bits, under IEEE 754, with a floating radix point." }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "représentation d'un nombre en 64 bits, selon la norme IEEE 754, avec une virgule flottante.; nommé également float64" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Darstellung einer Gleitkommazahl in 64 Bits" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "Rappresentazione di un numero a 64 bit, in formato IEEE 754, con virgola mobile" }, { "Z1K1": "Z11", "Z11K1": "Z1181", "Z11K2": "Репрезентација броја у 64 бита, по IEEE 754 стандарду, са покретним зарезом" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "एक संख्या का IEEE 754 के अतंर्गत 64 बिट्स में प्रतिनिधित्व, एक फ़्लोटिंग पॉइंट के साथ।" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "representatie van een getal in 64 bits, volgens IEEE 754, met een drijvende-kommapunt" }, { "Z1K1": "Z11", "Z11K1": "Z1830", "Z11K2": "IEEE 754規格に準拠した、64ビット形式の浮動小数点数による数値表現" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "据IEEE 754标准以浮动小数点于64位元表示之数" } ] } } 96zqyd1zfcw0q9z9y3tpygw0tpqh928 0 50861 275524 271714 2026-05-16T13:07:54Z 物灵 49367 翻译 275524 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z22571" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z22571K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Latin" }, { "Z1K1": "Z11", "Z11K1": "Z1762", "Z11K2": "nimi pi sitelen Lasina" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "拉丁字母" } ] } } ], "Z8K2": "Z11", "Z8K3": [ "Z20", "Z22573", "Z22574", "Z22575", "Z22945", "Z34447", "Z34685", "Z34686", "Z34687" ], "Z8K4": [ "Z14", "Z22572" ], "Z8K5": "Z22571" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Toki Pona Latin to Sitelen Pona" }, { "Z1K1": "Z11", "Z11K1": "Z1762", "Z11K2": "sitelen Lasina kama sitelen pona" }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "道本语拉丁字母转道本图" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Latin to sitelen pona" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Converts Toki Pona text in the Latin script to Sitelen Pona glyphs as defined in the Under-ConScript Unicode Registry. Text can be entered with or without spaces (except where needed for clarity)." }, { "Z1K1": "Z11", "Z11K1": "Z1762", "Z11K2": "sina ken kepeken e nimi mute." }, { "Z1K1": "Z11", "Z11K1": "Z1645", "Z11K2": "转换拉丁字母书写之道本语至道本图，依下位构造文字Unicode注册表（Under-ConScript Unicode Registry）编码。输入文本空格可有可无（除非歧义）。" } ] } } 830av74w7k8yit5f24zb7v7i4wpuqt1 0 51648 275712 170951 2026-05-17T08:56:02Z Ameisenigel 44 move to [[Z10251]] 275712 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z22985" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z10251", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z610", "Z16K2": "def Z10251(Z10251K1):\n return ' '.join(word.capitalize() for word in Z10251K1.split(' '))" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Headline Case, python" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 0jx5wclzauvo4zfh14la6s3q08qunif 275722 275712 2026-05-17T09:03:27Z Ameisenigel 44 de 275722 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z22985" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z10251", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z610", "Z16K2": "def Z10251(Z10251K1):\n return ' '.join(word.capitalize() for word in Z10251K1.split(' '))" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Headline Case, python" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "in großen Anfangsbuchstaben in Python" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 6sgokpv7r0hs2dhrz0fviamdv6rvcis 0 51649 275707 170953 2026-05-17T08:48:47Z Ameisenigel 44 move to [[Z10251]] 275707 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z22986" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z10251", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z18771", "Z18771K1": "mIxEd CaSe" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K2": "Mixed Case" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to headline: mIxEd CaSe" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } cusijel8uwe9r7pu21roq817q0bqlkh 275715 275707 2026-05-17T08:58:32Z Ameisenigel 44 de 275715 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z22986" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z10251", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z18771", "Z18771K1": "mIxEd CaSe" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K2": "Mixed Case" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to headline: mIxEd CaSe" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "mIxEd CaSe in großen Anfangsbuchstaben" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } t6mcz6ab4a0qriz67yhx3je1bbunpjj 275718 275715 2026-05-17T09:01:54Z Ameisenigel 44 275718 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z22986" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z10251", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z10251", "Z10251K1": "mIxEd CaSe" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K2": "Mixed Case" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to headline: mIxEd CaSe" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "mIxEd CaSe in großen Anfangsbuchstaben" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 931z8mddoncei8bdlepl3r3yp5163px 0 51650 275708 170954 2026-05-17T08:49:31Z Ameisenigel 44 move to [[Z10251]] 275708 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z22987" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z10251", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z18771", "Z18771K1": "TEST CASES" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K2": "Test Cases" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Headline Case: TEST CASES" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 3xfh98a8bh5yxeclpwehk0tofum82p7 275716 275708 2026-05-17T08:59:24Z Ameisenigel 44 de 275716 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z22987" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z10251", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z18771", "Z18771K1": "TEST CASES" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K2": "Test Cases" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Headline Case: TEST CASES" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "TEST CASES in großen Anfangsbuchstaben" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } kx8fw0mpe2obzmb6uojfqa865zsqr8u 275717 275716 2026-05-17T09:01:02Z Ameisenigel 44 275717 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z22987" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z10251", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z10251", "Z10251K1": "TEST CASES" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K2": "Test Cases" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "to Headline Case: TEST CASES" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "TEST CASES in großen Anfangsbuchstaben" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ocvpgcsvws02cmecnh9iwmf7xeqnzml 0 54554 275762 181053 2026-05-17T10:39:02Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275762 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1968" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "hav" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Havu" }, { "Z1K1": "Z11", "Z11K1": "Z1968", "Z11K2": "Kihavu" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Havu" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "havu" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "haavu" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } eg8tnz9kgguh6azucxhem8q47ccuydp 0 56304 275763 186197 2026-05-17T10:39:54Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275763 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1969" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "hoc-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Ho (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1969", "Z11K2": "Ho" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Ho (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "ho en écriture latine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } piq2gn0c1r9no70ias9cmxh5vmpulha 0 56617 275764 187599 2026-05-17T10:40:35Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275764 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1971" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "crg" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Michif" }, { "Z1K1": "Z11", "Z11K1": "Z1971", "Z11K2": "Michif" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Michif" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "métchif" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "mitchif" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } apnfq6mhg1lr0h0k3higfovoh3qn1xd 0 56620 275656 260380 2026-05-17T05:26:47Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275656 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z6884" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z4", "Z17K2": "Z6884K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Wikidata reference type" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Wikidata-Referenz-Typ" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "tipo dei riferimenti Wikidata" }, { "Z1K1": "Z11", "Z11K1": "Z1272", "Z11K2": "vrst upućivanja" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "উইকিউপাত্ত উল্লেখের ধরণ" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "विकिडेटा संदर्भ का प्रकार" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "Wikidata-referentietype" }, { "Z1K1": "Z11", "Z11K1": "Z1062", "Z11K2": "typ referencí na Wikidata" } ] } }, { "Z1K1": "Z17", "Z17K1": { "Z1K1": "Z7", "Z7K1": "Z881", "Z881K1": "Z1" }, "Z17K2": "Z6884K2", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "list of Wikidata references" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Liste von Wikidata-Referenzen" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "lista di riferimenti Wikidata" }, { "Z1K1": "Z11", "Z11K1": "Z1272", "Z11K2": "nabroj" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "liste de références Wikidata" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "উইকিউপাত্ত উল্লেখসমূহের তালিকা" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "विकिडेटा संदर्भों की सूची" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "lijst met Wikidata-referenties" }, { "Z1K1": "Z11", "Z11K1": "Z1062", "Z11K2": "seznam referencí na Wikidata" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z6884K3", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "ZID of result type (assigned by WikiLambda)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "ZID des resultierenden Typs" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "ZID del tipo risultante (assegnato da WikiLambda)" }, { "Z1K1": "Z11", "Z11K1": "Z1272", "Z11K2": "ZID tipa (automatski napunjeno)" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "ফলাফলের ধরনের ZID (উইকিল্যাম্বডা দ্বারানির্ধারিত)" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "परिणाम के प्रकार का ZID" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "ZID van het resultaattype (toegewezen door WikiLam" }, { "Z1K1": "Z11", "Z11K1": "Z1062", "Z11K2": "ZID výsledného typu (přiřazuje WikiLambda)" } ] } } ], "Z8K2": "Z4", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14", "Z6984" ], "Z8K5": "Z6884" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Typed enum of Wikidata references" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "typisierte Aufzählung von Wikidata-Referenzen" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "Enumerazione tipizzata di riferimenti Wikidata" }, { "Z1K1": "Z11", "Z11K1": "Z1272", "Z11K2": "nabroj upućivanja na Wikipodatci" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "énumération typée de références Wikidata" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "উইকিউপাত্ত উল্লেখসমূহের ধরনযুক্ত এনাম" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "विकिडेटा संदर्भों की प्रकारयुक्त सूची" }, { "Z1K1": "Z11", "Z11K1": "Z1157", "Z11K2": "getypeerde opsomming van Wikidata-referenties" }, { "Z1K1": "Z11", "Z11K1": "Z1062", "Z11K2": "Výčtový typ referencí na Wikidata" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "lightweight enum", "enumerate type", "enumerated type", "type from enumerated values" ] }, { "Z1K1": "Z31", "Z31K1": "Z1062", "Z31K2": [ "Z6", "typ z vyjmenovaných hodnot" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1062", "Z11K2": "Generický typ pro výčtové typy, jejichž možné hodnoty jsou definované seznamem referencí na položky Wikidat" } ] } } o39hi3hnts9vt4pqpnj1gcro8obv5l1 0 57545 275760 191022 2026-05-17T10:36:17Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275760 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1970" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "qxp" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Puno Quechua" }, { "Z1K1": "Z11", "Z11K1": "Z1970", "Z11K2": "Punu qhichwa" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Puno Quechua" }, { "Z1K1": "Z11", "Z11K1": "Z1381", "Z11K2": "quíchua punenho" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "quechua de Puno" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 9m6ncpc72i2ef962y4k1id8ms7g14dt 0 58405 275761 194209 2026-05-17T10:36:36Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275761 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1972" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "yua" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Yucatec Maya" }, { "Z1K1": "Z11", "Z11K1": "Z1972", "Z11K2": "maaya t’aan" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Mayathan" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "maya yucatèque" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ht0zkxsj3hf4nl1g83bfpsrtqr8dd9q 0 58406 275765 216213 2026-05-17T10:45:28Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275765 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1973" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "dlg" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Dolgan" }, { "Z1K1": "Z11", "Z11K1": "Z1973", "Z11K2": "долган тыла" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Dolganisch" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "दोल्गान" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "dolgane" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } logl4158zz6sg2pbos2wn77ytkdmo3j 0 61254 275766 204119 2026-05-17T10:45:57Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275766 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1974" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "agr" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Aguaruna" }, { "Z1K1": "Z11", "Z11K1": "Z1974", "Z11K2": "Awajún" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Aguaruna" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "aguaruna" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ecr723yq8escvq8q34xt9qulnzywzk7 0 61256 275767 216025 2026-05-17T10:53:59Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275767 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1976" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "ayh" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Hadhrami Arabic" }, { "Z1K1": "Z11", "Z11K1": "Z1976", "Z11K2": "الحضرمية" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Hadrami-Arabisch" }, { "Z1K1": "Z11", "Z11K1": "Z1820", "Z11K2": "हद्रामी अरबी" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "arabe hadhrami" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } j58sv03t0mshuwg26e25ddwqt28318e 0 62677 275620 260381 2026-05-17T01:49:53Z YoshiRulz 10156 Use sentence case for en label 275620 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z26935" }, "Z2K2": { "Z1K1": "Z7", "Z7K1": "Z6884", "Z6884K1": "Z6091", "Z6884K2": [ "Z6091", { "Z1K1": "Z6091", "Z6091K1": "Q51927507" }, { "Z1K1": "Z6091", "Z6091K1": "Q51927539" } ], "Z6884K3": { "Z1K1": "Z6", "Z6K1": "Z26935" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Grammatical animacy (animate / inanimate)" }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "Livello di animazione grammaticale (a/i)" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "grammatikalische Belebtheit (belebt/unbelebt)" }, { "Z1K1": "Z11", "Z11K1": "Z1011", "Z11K2": "ব্যাকরণগত সজীবতা (প্রাণিবাচক / অপ্রাণিবাচক)" }, { "Z1K1": "Z11", "Z11K1": "Z1062", "Z11K2": "Životnost (životné/neživotné)" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1787", "Z31K2": [ "Z6", "a/i", "genere grammaticale (animato / inanimato)", "animato/inanimato", "genere grammaticale (a/i)", "livello di animazione grammaticale (animato / inanimato)" ] }, { "Z1K1": "Z31", "Z31K1": "Z1062", "Z31K2": [ "Z6", "Gramatická životnost" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1062", "Z11K2": "Výčtový typ pro gramatickou životnost" } ] } } eza1of9wmusv6g2l7zir3ght8swu2lt 3 63554 275541 275136 2026-05-16T17:37:21Z HenkvD 1290 /* Thanks and need some more help */ Reply 275541 wikitext text/x-wiki {{Welcome/lang|user=NikolasKHF|welcominguser=99of9|1=}} --[[User:99of9|99of9]] ([[User talk:99of9|talk]]) 23:49, 10 August 2025 (UTC) == Test == halo kak, @[[User:NikolasKHF|NikolasKHF]] saya baru saja membuat fungsi serta implementasinya https://www.wikifunctions.org/view/en/Z30774 , untuk membuat test apakah implementasinya harus diconnect dulu ya? Jika iya, tolong hubungkan implementasinya 🙏🙏 terimakasih. [[User:Muufii|Muufii]] ([[User talk:Muufii|talk]]) 01:30, 21 December 2025 (UTC) :Tidak perlu, kak. Sebelumnya, saya mau memastikan, kak, kira-kira rumus yang dipakai apa, ya untuk fungsinya? :Saya lihat sepertinya semacam <math>a + (n - 1)b</math>, ya? [[User:NikolasKHF|NikolasKHF]] ([[User talk:NikolasKHF|talk]]) 02:01, 21 December 2025 (UTC) ::Betul kak itu fungsinya. Tapi saya coba test gagal. Nah itu saya gapaham kenapa. [[User:Muufii|Muufii]] ([[User talk:Muufii|talk]]) 02:02, 21 December 2025 (UTC) :::Kalau saya lihat karena {{Z|506}}, kak. Itu karena fungsi yang dipakai di implementasi ({{Z|Z19699}} dan {{Z|Z19706}}) punya jenis input {{Z|19677}}, sementara jenis input dari fungsi yang dibuat adalah {{Z|20838}} dan {{Z|13518}}. Saran saya, pakai fungsi dengan jenis masukan yang sama, misalnya {{Z|21032}}, {{Z|21031}}, dan {{Z|20849}}. :::Selain itu, karena masukan untuk <code>n</code> itu {{Z|13518}}, saran saya konversi dulu ke {{Z|20838}} pakai {{Z|20936}} atau langsung pakai jenis {{Z|20838}} sekalian. [[User:NikolasKHF|NikolasKHF]] ([[User talk:NikolasKHF|talk]]) 02:36, 21 December 2025 (UTC) :::Halo Kak @[[User:Muufii|Muufii]], mohon maaf terlambat. Fungsinya sudah saya perbaiki, dan komposisi dengan kasus uji sudah saya hubungkan. Terima kasih! [[User:NikolasKHF|NikolasKHF]] ([[User talk:NikolasKHF|talk]]) 03:48, 3 January 2026 (UTC) ::::Wah terimakasih banyak kak. [[User:Muufii|Muufii]] ([[User talk:Muufii|talk]]) 03:49, 3 January 2026 (UTC) == Thanks and need some more help == Hi OwlyKnight. thank for helping me with via [[Wikifunctions:Requests for connection and disconnection|this request page]]. I need some more help with the Dutch/nl {{Z|28016}}. The test "Amsterdam is de hoofdstad van Nederland." is partly working, but I don't understand that I get the default translation. I am confused. Has it to do with Dutch versus nl? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 15:43, 15 May 2026 (UTC) :Hi! When I tested it, it gave the correct results, even with the [[Z28032|failing implementation]]. I believe the implementation is failing because of cache from the server that cannot call the correct function on the configuration. I tested using the default function at it gets the same results ("Amsterdam hoofdstad Nederland"): [https://www.wikifunctions.org/view/id/Z28019?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z28019%22%2C%22Z28019K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q727%22%7D%2C%22Z28019K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q5119%22%7D%2C%22Z28019K3%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q55%22%7D%2C%22Z28019K4%22%3A%22Z1157%22%7D test]. I am not sure why [[Z28034]] gets the correct results, though. Perhaps, we can wait for the cache of the server to be refreshed. :As for the Dutch and nl, I don't think it makes any different, as both refer to the same ZID: [[Z1157]]. [[User:OwlyKnight|OwlyKnight]] ([[User talk:OwlyKnight|talk]]) 17:33, 15 May 2026 (UTC) ::Hi OwlyKnight. It looks better now. On [https://abstract.wikipedia.org/wiki/Q90 Abstractwiki Q90] the text in Dutch now reads correctly "Parijs is een stad. Parijs is de hoofdstad van Frankrijk.", although one of the implementations still fails. Could you connect the test {{Z|35054}}? [[User:HenkvD|HenkvD]] ([[User talk:HenkvD|talk]]) 17:37, 16 May 2026 (UTC) anb5zc13z5f49rjg0hpvrcmc4rg7fa6 0 66139 275772 221151 2026-05-17T11:16:21Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275772 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1978" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "rhg-rohg" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Rohingya (Hanifi script)" }, { "Z1K1": "Z11", "Z11K1": "Z1978", "Z11K2": "𐴌𐴟𐴇𐴥𐴝𐴚𐴒𐴙𐴝" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Rohingya (Hanifi-Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "rohingya en écriture hanifi" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } k5mw5ollg16lt8tcyw43yi4e4o6dipi 0 66140 275771 221152 2026-05-17T11:15:24Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275771 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1979" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "rhg-arab" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Rohingya (Arabic script)" }, { "Z1K1": "Z11", "Z11K1": "Z1979", "Z11K2": "رُحَ࣪ڠۡگَ࣪ࢬ عَرࣤبِي لࣦكَ࣪" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Rohingya (Arabische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "rohingya en écriture arabe" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } dqvy97p3uc1wk9a5a0wszsb2qq2ouk3 0 68312 275770 229377 2026-05-17T11:13:15Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275770 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1982" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "sxr" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Saaroa" }, { "Z1K1": "Z11", "Z11K1": "Z1982", "Z11K2": "Hla'alua" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Saaroa" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "saaroa" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 46ilsa9kiprqp4qk2ooaisu3rqfx25t 0 69084 275773 235154 2026-05-17T11:19:00Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275773 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1983" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "sgh" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Shughni" }, { "Z1K1": "Z11", "Z11K1": "Z1983", "Z11K2": "Xuɣ̌nůni" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Shughni" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "shughni" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } iubt58a8yk831rc0vinglit8clnoc4u 275774 275773 2026-05-17T11:19:25Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275774 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1983" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "sgh" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Shughni" }, { "Z1K1": "Z11", "Z11K1": "Z1983", "Z11K2": "Xuɣ̌nůni" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Shughni" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "shughni" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "chougnan" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 5vf2t0fx1liis1p0bt1rp8obdbjirld 4 69531 275532 273691 2026-05-16T16:26:02Z YoshiRulz 10156 /* Tables */ Add td/th helper 275532 wikitext text/x-wiki Functions that are directly related to [[Help:HTML_fragments|HTML fragments]]. ==Comparison and evaluation== * {{Z+|Z877}} * {{Z+|Z29045}} * {{Z+|Z29572}} ** {{Z+|Z29576}} ==Conversion== * {{Z+|Z27854}} * {{Z+|Z27861}} * {{Z+|Z33470}} ** {{Z+|Z27868}} ** {{Z+|Z19384}} ==Transformation== ===Concatenation=== * {{Z+|Z27849}} ** {{Z+|Z27926}} ** {{Z+|Z32149}} *{{Z+|Z32234}} ===Tag wrapping=== * {{Z+|Z27873}} ** {{Z+|Z33470}} *** {{Z+|Z33457}} ** {{Z+|Z35049}} * {{Z+|Z30058}} * {{Z+|Z29582}} ===Text and element styling=== * {{Z+|Z29052}} * {{Z+|Z28914}} * {{Z+|Z31729}} * {{Z+|Z32925}} ===Other=== * {{Z+|Z27932}} ==Page elements== ===Headers and sections=== * {{Z+|Z31465}} ** {{Z+|Z32145}} ===Paragraphs and lists=== *{{Z+|Z32123}} ** {{Z+|Z32163}} * {{Z+|Z32179}} * {{Z+|Z32180}} ** {{Z+|Z32215}} ===Links and buttons=== * {{Z+|Z30016}} * {{Z+|Z31697}} ** {{Z+|Z29588}} * {{Z+|Z28904}} * {{Z+|Z30954}} === References and citations === {{Seealso|Wikifunctions:Catalogue/Wikidata_operations/Item#Citations}} * {{Z+|Z31906}} * {{Z+|Z31917}} * {{Z+|Z31921}} * {{Z+|Z32053}} ===Tables=== * {{Z+|Z35017}} * {{Z+|Z27878}} * {{Z+|Z23293}} * {{Z+|Z29580}} ==Linguistic applications== * {{Z+|Z26333}} * {{Z+|Z29055}} * {{Z+|Z28602}} ** {{Z+|Z28928}} * {{Z+|Z29488}} **{{Z+|Z29557}} * {{Z+|Z29186}} ==Sentence and fragment generation== * {{Z+|Z32962}} [[Category:Lists of functions]] t473uk4e54b5tjvcnrw42ni375o92fx 275548 275532 2026-05-16T18:57:58Z Theki 2389 /* Paragraphs and lists */ 275548 wikitext text/x-wiki Functions that are directly related to [[Help:HTML_fragments|HTML fragments]]. ==Comparison and evaluation== * {{Z+|Z877}} * {{Z+|Z29045}} * {{Z+|Z29572}} ** {{Z+|Z29576}} ==Conversion== * {{Z+|Z27854}} * {{Z+|Z27861}} * {{Z+|Z33470}} ** {{Z+|Z27868}} ** {{Z+|Z19384}} ==Transformation== ===Concatenation=== * {{Z+|Z27849}} ** {{Z+|Z27926}} ** {{Z+|Z32149}} *{{Z+|Z32234}} ===Tag wrapping=== * {{Z+|Z27873}} ** {{Z+|Z33470}} *** {{Z+|Z33457}} ** {{Z+|Z35049}} * {{Z+|Z30058}} * {{Z+|Z29582}} ===Text and element styling=== * {{Z+|Z29052}} * {{Z+|Z28914}} * {{Z+|Z31729}} * {{Z+|Z32925}} ===Other=== * {{Z+|Z27932}} ==Page elements== ===Headers and sections=== * {{Z+|Z31465}} ** {{Z+|Z32145}} ===Paragraphs and lists=== *{{Z+|Z32123}} ** {{Z+|Z32163}} ** {{Z+|Z33068}} * {{Z+|Z32179}} * {{Z+|Z32180}} ** {{Z+|Z32215}} ===Links and buttons=== * {{Z+|Z30016}} * {{Z+|Z31697}} ** {{Z+|Z29588}} * {{Z+|Z28904}} * {{Z+|Z30954}} === References and citations === {{Seealso|Wikifunctions:Catalogue/Wikidata_operations/Item#Citations}} * {{Z+|Z31906}} * {{Z+|Z31917}} * {{Z+|Z31921}} * {{Z+|Z32053}} ===Tables=== * {{Z+|Z35017}} * {{Z+|Z27878}} * {{Z+|Z23293}} * {{Z+|Z29580}} ==Linguistic applications== * {{Z+|Z26333}} * {{Z+|Z29055}} * {{Z+|Z28602}} ** {{Z+|Z28928}} * {{Z+|Z29488}} **{{Z+|Z29557}} * {{Z+|Z29186}} ==Sentence and fragment generation== * {{Z+|Z32962}} [[Category:Lists of functions]] kv8m7d0bas1kr85kj7f5knvtec34dk3 1 69716 275630 234756 2026-05-17T03:05:08Z YoshiRulz 10156 Add auto-generated docs 275630 wikitext text/x-wiki {{type documentation|Z882|Typed pair}} == Problems making use of this Type == These use cases are blocked by [[Z882]]-related issues: * {{Z|17534}} all tests failing * {{Z|21356}} ([[Z21358|implementation]] calls [[Z17534]]) * {{Z|21350}} (returns list of pairs; [[Z21355|implementation]] calls [[Z17534]]) * {{Z|24665}} single test failing * [[Talk:Z15796#Testing_constraints|Apparently]] writing tests for {{Z|805}} * Possibly {{Z|29094}}, not sure what's going on there However, these use cases seem to work just fine: * {{Z|19586}}, all tests passing * {{Z|821}}/{{Z|822}}, former has weird tests, but latter is thoroughly tested and passes all ** Presumably {{Z|21347}} would be implemented as <code>sortBy(Z821, pairs)</code> * {{Z|27915}} single test passing * {{Z|24649}} single test passing * {{Z|24606}} single test passing <hr> {{phab|T384104}} The ticket linked here is requesting a custom UI component for pairs. That might unblock some of the above cases by circumventing {{Z|17534}}, though judging by [[Z24666]] which doesn't use it, that's not the problem. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 16:31, 2 December 2025 (UTC) :There are still problems with {{Z|Z17534}}, it is true, but the main problem is that the only available implementation is in Python, and [[:phab:T406848#11419629|Python is broken]]. I think any code implementations will need to be wrapped in a composition, because we need a Reference to be de-referenced in order to extract its type. Currently (when it works at all), returning a Reference in a ZPair will set the corresponding Type to Reference, which is not generally appropriate. I don’t think we can simply implement as a composition, however, because the function calls to extract the Types are simply incorporated into the pair specification without being evaluated first. The objects should also be quoted to avoid conversion (because a converted object loses its specific typing) and there are [[:phab:T409229|issues with that too]]. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:44, 3 December 2025 (UTC) :Meanwhile… I’ve implemented a [[Z30388|JavaScript version]] of {{Z|Z17534}}, and the Python implementation is now succeeding. Objects with custom conversion need to be quoted, and [[:phab:T409229]] relates to issues there. The workaround is to use {{Z|Z16575}}. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 11:34, 9 December 2025 (UTC) ::I’ve now wrapped [[Z17534]] and [[Z24665]] as implementations of {{Z|Z30414}}, with {{Z|Z30396}} as a new implementation of Z24665. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 22:36, 9 December 2025 (UTC) ::Thank you so much! Is it possible to convert [[Z21809]] to using pairs now? Is {{Z|19586}} a suitable replacement for [[Z889]] in the tests? [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:20, 10 December 2025 (UTC) :::Yes, but you might be better off making a new function, as changing the return type invalidates all the test cases. Z19586 works for pairs of lists but (unlike Z889) the typing of corresponding lists has to be the same, if custom conversion applies, as otherwise {{Z|Z29294}} will fail to match converted objects (in a properly typed list) with unconverted objects (in an untyped list). In theory, you can just use [[Z29294]] instead, like {{Z|Z30457}}, but I’d like to see some more complex tests before connecting that. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 10:13, 10 December 2025 (UTC) gx3o0awsm709frnkyh7n7dia5i1c1zz 0 69884 275601 235024 2026-05-17T01:22:15Z Amire80 113 translating label from Italian 275601 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z30176" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z27327", "Z14K2": { "Z1K1": "Z7", "Z7K1": "Z27332", "Z27332K1": { "Z1K1": "Z7", "Z7K1": "Z30172", "Z30172K1": { "Z1K1": "Z7", "Z7K1": "Z6820", "Z6820K1": { "Z1K1": "Z7", "Z7K1": "Z6830", "Z6830K1": { "Z1K1": "Z18", "Z18K1": "Z27327K1" }, "Z6830K2": { "Z1K1": "Z18", "Z18K1": "Z27327K2" }, "Z6830K3": { "Z1K1": "Z18", "Z18K1": "Z27327K3" } }, "Z6820K2": [ "Z6030" ], "Z6820K3": [ "Z60" ], "Z6820K4": [ "Z6092" ] } }, "Z27332K2": { "Z1K1": "Z18", "Z18K1": "Z27327K1" } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "🔄 miglior lessema, con unico fetch" }, { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "best lexeme with one fetch" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Could cause an infinite loop." }, { "Z1K1": "Z11", "Z11K1": "Z1787", "Z11K2": "Potrebbe causare loop infinito." } ] } } ln9k1dyncj6nbswp8p6vhzn3eli8fhv 0 74435 275776 254883 2026-05-17T11:20:31Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275776 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1987" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "jax" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Jambi Malay" }, { "Z1K1": "Z11", "Z11K1": "Z1987", "Z11K2": "Jambi" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Jambi-Malaiisch" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "malais jambi" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Bahaso Jambi" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 7wdcuuqtysdslzvsw9ibezdsg54nh5h 0 74436 275775 248226 2026-05-17T11:20:09Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275775 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1988" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "xnb" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Kanakanavu" }, { "Z1K1": "Z11", "Z11K1": "Z1988", "Z11K2": "Kanakanavu" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Kanakanabu" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "kanakanabu" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } hdmf81fq5o0g5idssfbkg6ygmwooorf 5 75190 275555 254874 2026-05-16T19:51:23Z YoshiRulz 10156 /* Redesign */ Reply 275555 wikitext text/x-wiki == Redesign == This page has grown organically and it's not really good for looking up functions anymore. We might need to start over. I thought of this categorisation, not based on anything: * list properties (length, equality, all true, etc.) * sort/flatten operations * indexing/slice operations * deletion/filter operations * substitution/map operations * insertion operations * list/matrix generation * matrix math [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 01:22, 3 February 2026 (UTC) :[[User:YoshiRulz/Catalogue/List_operations|Made a draft]]. :I did first have a look for an existing {{Q|5962346}} for algorithms that we could follow, but the closest I found was the {{Q|24534}} and the Taxonomy supplement to the {{Q|113673155}}. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 18:21, 18 February 2026 (UTC) ::Also searched external software and mathematics catalogues in Mix'n'match, still nothing. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 22:55, 21 February 2026 (UTC) :Since no-one seems to care, I've BOLDly copied over the version from my User page which I've been maintaining in parallel. I double-checked and every function either remains in the list or was replaced with its duplicate. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 19:51, 16 May 2026 (UTC) ph4u931g3vxgsapjp0pnzu4tqokqvwn 0 76046 275768 255787 2026-05-17T10:56:33Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275768 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1989" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "tlh-piqd" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Klingon (Klingon script)" }, { "Z1K1": "Z11", "Z11K1": "Z1989", "Z11K2": " " }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Klingonisch (klingonische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "klingon en écriture klingon" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Klingon (pIqaD)", "Klingon in pIqaD" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } iyzyx94dn3juqm18x2ls6fht2v0zyxz 0 76047 275769 251838 2026-05-17T10:56:47Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275769 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1990" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "tlh-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Klingon (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z1990", "Z11K2": "tlhIngan Hol" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Klingonisch (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "klingon en écriture latine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } livofnnxu189ki3lbs1hqp8b35xy3ss 2 76975 275550 266643 2026-05-16T19:07:36Z YoshiRulz 10156 275550 wikitext text/x-wiki * {{Z+|Z881}} == Properties == <!-- type --> * {{Z+|Z18636}} <!-- length --> * {{Z+|Z12681}} ** {{Z+|Z30164}} *** {{Z+|Z813}} **** {{Z+|Z23120}} **** {{Z+|Z30075}} *** {{Z+|Z32302}} *** {{Z+|Z12755}} *** {{Z+|Z12759}} *** {{Z+|Z12864}} **** {{Z+|Z13310}} **** {{Z+|Z21212}} **** {{Z+|Z12851}} ** {{Z+|Z31612}} ** {{Z+|Z31605}} * {{Z+|Z31592}} <!-- contains --> * {{Z+|Z12696}} ** {{Z+|Z34367}} ** {{Z+|Z12738}} *** {{Z+|Z13752}} *** {{Z+|Z12698}} ** {{Z+|Z12735}} *** {{Z+|Z12684}} ** {{Z+|Z34378}} ** {{Z+|Z12846}} *** {{Z+|Z34380}} *** {{Z+|Z12741}} <!-- equals --> * {{Z+|Z889}} ** {{Z+|Z18646}} *** {{Z+|Z24166}} ** {{Z+|Z34273}} ** {{Z+|Z31013}} *** {{Z+|Z31019}} *** {{Z+|Z10393}} *** {{Z+|Z31026}} <!-- count --> * {{Z+|Z29413}} ** {{Z+|Z31600}} ** {{Z+|Z22874}} ** {{Z+|Z34793}} *** {{Z+|Z29409}} <!-- indexOf --> * {{Z+|Z13708}} ** {{Z+|Z28715}} ** {{Z+|Z19536}} ** {{Z+|Z31575}} *** {{Z+|Z31583}} <!-- startsWith --> * {{Z+|Z21613}} ** {{Z+|Z31294}} ** {{Z+|Z30975}} *** {{Z+|Z30977}} *** {{Z+|Z31002}} <!-- endsWith --> * {{Z+|Z31758}} ** {{Z+|Z31763}} ** {{Z+|Z30976}} *** {{Z+|Z30978}} *** {{Z+|Z31003}} == Indexing/slicing == <!-- first --> * {{Z+|Z811}} ** {{Z+|Z22839}} ** {{Z+|Z13366}} *** {{Z+|Z24203}} * {{Z+|Z29446}} ** {{Z+|Z16360}} <!-- last --> * {{Z+|Z12964}} ** {{Z+|Z13362}} <!-- nth --> * {{Z+|Z13397}} ** {{Z+|Z26904}} ** {{Z+|Z30282}} *** {{Z+|Z31587}} ** {{Z+|Z26556}} ** {{Z+|Z31809}} *** {{Z+|Z28735}} <!-- dropFirst --> * {{Z+|Z812}} ** {{Z+|Z13369}} *** {{Z+|Z31874}} <!-- dropLast --> * {{Z+|Z12967}} ** {{Z+|Z13373}} ** {{Z|Z18284}} == Removal/filtering == <!-- remove --> * {{Z+|Z12856}} ** {{Z+|Z13081}} *** {{Z|Z18291}} ** {{Z+|Z22865}} ** {{Z+|Z34538}} ** {{Z+|Z19205}} *** {{Z+|Z13078}} *** {{Z+|Z19202}} ** {{Z+|Z31874}} <!-- removeAt --> * {{Z+|Z31364}} ** {{Z+|Z13429}} ** {{Z+|Z13369}} ** {{Z+|Z13373}} ** {{Z+|Z29400}} *** {{Z+|Z18194}} <!-- filter with predicate --> * {{Z+|Z872}} ** {{Z+|Z33453}} ** {{Z+|Z21809}} ** {{Z+|Z28316}} <!-- filter by key --> * {{Z+|Z27413}} ** {{Z+|Z33105}} *** {{Z+|Z24849}} **** {{Z+|Z24855}} == Substitution/transformation == <!-- un/type --> * {{Z|Z15142}} (no-op) * {{Z+|Z18729}} ** {{Z+|Z18475}} ** {{Z+|Z17895}} *** {{Z+|Z28691}} <!-- substituteAt --> * {{Z+|Z31369}} <!-- map --> * {{Z+|Z873}} ** {{Z+|Z24846}} ** {{Z+|Z32453}} ** {{Z+|Z32806}} == Insertion == <!-- prepend --> * {{Z+|Z810}} ** {{Z+|Z24285}} ** {{Z+|Z31721}} <!-- append --> * {{Z+|Z18597}} ** {{Z+|Z12961}} *** {{Z+|Z24150}} *** {{Z|Z18276}} ** {{Z+|Z34519}} ** {{Z+|Z24655}} ** {{Z+|Z33720}} <!-- insert --> * {{Z+|Z31345}} ** {{Z+|Z31340}} ** {{Z+|Z33646}} <!-- concat --> * {{Z+|Z12767}} ** {{Z+|Z18755}} *** {{Z|Z18288}} ** {{Z+|Z27665}} ** {{Z+|Z34538}} == Generation == <!-- list from element --> * {{Z+|Z14046}} ** {{Z+|Z27685}} ** {{Z+|Z24291}} ** {{Z+|Z21389}} <!-- from range --> * {{Z+|Z21821}} ** {{Z+|Z23921}} *** {{Z+|Z24387}} *** {{Z+|Z24382}} <!-- product of lists --> * {{Z+|Z29286}} ** {{Z+|Z29324}} <!-- power set --> * {{Z+|Z18194}} == Ordering and grouping == <!-- reverse --> * {{Z+|Z18759}} ** {{Z+|Z12668}} ** {{Z+|Z18479}} ** {{Z|Z17770}} ** {{Z|Z17774}} ** {{Z|Z17778}} * {{Z+|Z24176}} <!-- cycle --> * {{Z+|Z31355}} ** {{Z+|Z25526}} ** {{Z+|Z22179}} <!-- sort by key --> * {{Z+|Z29725}} * {{Z+|Z19510}} <!-- sort with comparator --> * {{Z+|Z27612}} ** {{Z+|Z17873}} *** {{Z+|Z29429}} ** {{Z+|Z17869}} ** {{Z+|Z12671}} ** {{Z+|Z18281}} <!-- shuffle --> * {{Z+|Z29400}} * {{Z+|Z13247}} <!-- group --> * {{Z+|Z30157}} ** {{Z+|Z32585}} * {{Z+|Z34790}} <!-- chunk --> * {{Z+|Z29795}} * {{Z+|Z13224}} <!-- reduce --> * {{Z|Z876}} (actually left-associative ''fold'') ** {{Z|Z12781}} (actually left-associative ''reduce'') *** {{Z|Z20089}} w/ initial empty check ** {{Z|Z12753}} (actually right-associative ''reduce'') <!-- flatten --> * {{Z+|Z12676}} ** {{Z+|Z23606}} ** {{Z+|Z27665}} *** {{Z+|Z32453}} ** {{Z+|Z13155}} == Matrix math == Since we don't have specific types for vectors or matrices, vectors are represented as a list and matrices as a list of lists (to be interpreted as a list of rows). <!-- properties --> * {{Z+|Z31747}} ** {{Z+|Z31752}} * {{Z+|Z24166}} ** {{Z+|Z24171}} <!-- indexing --> * {{Z+|Z31587}} ** {{Z+|Z31585}} <!-- removal --> <!-- transformation --> * {{Z+|Z32806}} * {{Z+|Z31818}} * {{Z+|Z24055}} ** {{Z+|Z17670}} *** {{Z+|Z17675}} ** {{Z+|Z24162}} * {{Z+|Z24060}} ** {{Z+|Z24436}} * {{Z+|Z24185}} ** {{Z+|Z20659}} * {{Z+|Z21903}} * {{Z+|Z24239}} ** {{Z+|Z31749}} * {{Z+|Z24346}} ** {{Z+|Z24342}} * {{Z+|Z14046}} ** {{Z+|Z24177}} * {{Z+|Z29301}} ** {{Z+|Z24182}} * {{Z+|Z24191}} * {{Z+|Z24236}} * {{Z+|Z29308}} <!-- insertion --> * {{Z+|Z810}} ** {{Z+|Z24285}} ** {{Z+|Z24299}} * {{Z+|Z18597}} <!-- ordering --> * {{Z+|Z18759}} * {{Z+|Z24176}} <!-- generation --> * {{Z+|Z24291}} (useful for creating 1x1 matrixes) ** {{Z+|Z24251}} * {{Z+|Z24290}} * {{Z+|Z29286}} ** {{Z+|Z29324}} == Functions expecting a list argument == * [[Special:Search/: "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1"|Complete list of functions]] ** [[Special:Search/: "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1" !"Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1"| Functions specifying a “properly typed” list argument]] ** [[Special:Search/: "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1"|Functions not specifying the type for their list argument (Z1-typed or “untyped”)]] == Functions with list outputs == *[[Special:Search/: "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1"|Complete list of functions]] **[[Special:Search/: "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1" !"Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1|Functions specifying a “properly typed” output list]] **[[Special:Search/: "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1"|Functions not specifying the type for the output list (Z1-typed or “untyped”)]] # If a function specifies an output list with a type other than [[Z1]] (that is, it specifies a "properly typed" list), mismatched elements cause an error if the implementation is in code. # If all objects in an output list have the same type, the list takes that type instead of being Z1-typed. This only happens if the implementation is in code. For compositions, you can use {{Z|Z18475}} to get the same result. #If a code implementation needs custom-converted objects (provided by a {{Z|Z46}}), any list input must be properly typed (objects in a Z1-typed list are not converted). Similarly, any list output must be properly typed (not [[Z1]] in the function specification) or else conversion into a Wikifunctions object will fail. #If a code implementation does not need converted objects, you can use {{Z|Z28691}} to convert a properly typed list to Z1-typed (but this is [[Wikifunctions:Project_chat/Archive/2024/07#Typed_lists_now_open_beyond_Booleans_and_Strings|not officially supported]]). (The list will remain properly typed if there are no custom converters to code. Use {{Z|Z17895}} to make the list Z1-typed unconditionally.) [[Category:Lists of functions]] mrvdjfzhwpqpa3lfh1pwog7t8hd910j 275551 275550 2026-05-16T19:12:02Z YoshiRulz 10156 275551 wikitext text/x-wiki * {{Z+|Z881}} == Properties == <!-- type --> * {{Z+|Z18636}} <!-- length --> * {{Z+|Z12681}} ** {{Z+|Z30164}} *** {{Z+|Z813}} **** {{Z+|Z23120}} **** {{Z+|Z30075}} *** {{Z+|Z32302}} *** {{Z+|Z12755}} *** {{Z+|Z12759}} *** {{Z+|Z12864}} **** {{Z+|Z13310}} **** {{Z+|Z21212}} **** {{Z+|Z12851}} ** {{Z+|Z31612}} ** {{Z+|Z31605}} * {{Z+|Z31592}} <!-- contains --> * {{Z+|Z12696}} ** {{Z+|Z34367}} ** {{Z+|Z12738}} *** {{Z+|Z13752}} *** {{Z+|Z12698}} ** {{Z+|Z12735}} *** {{Z+|Z12684}} ** {{Z+|Z34378}} ** {{Z+|Z12846}} *** {{Z+|Z34380}} *** {{Z+|Z12741}} <!-- equals --> * {{Z+|Z889}} ** {{Z+|Z18646}} *** {{Z+|Z24166}} ** {{Z+|Z34273}} ** {{Z+|Z31013}} *** {{Z+|Z31019}} *** {{Z+|Z10393}} *** {{Z+|Z31026}} <!-- count --> * {{Z+|Z29413}} ** {{Z+|Z31600}} ** {{Z+|Z22874}} ** {{Z+|Z34793}} *** {{Z+|Z29409}} <!-- indexOf --> * {{Z+|Z13708}} ** {{Z+|Z28715}} ** {{Z+|Z19536}} ** {{Z+|Z31575}} *** {{Z+|Z31583}} <!-- startsWith --> * {{Z+|Z21613}} ** {{Z+|Z31294}} ** {{Z+|Z30975}} *** {{Z+|Z30977}} *** {{Z+|Z31002}} <!-- endsWith --> * {{Z+|Z31758}} ** {{Z+|Z31763}} ** {{Z+|Z30976}} *** {{Z+|Z30978}} *** {{Z+|Z31003}} == Indexing/slicing == <!-- first --> * {{Z+|Z811}} ** {{Z+|Z22839}} ** {{Z+|Z13366}} *** {{Z+|Z24203}} * {{Z+|Z29446}} ** {{Z+|Z16360}} <!-- last --> * {{Z+|Z12964}} ** {{Z+|Z13362}} <!-- nth --> * {{Z+|Z13397}} ** {{Z+|Z26904}} ** {{Z+|Z30282}} *** {{Z+|Z31587}} ** {{Z+|Z26556}} ** {{Z+|Z31809}} *** {{Z+|Z28735}} <!-- dropFirst --> * {{Z+|Z812}} ** {{Z+|Z13369}} *** {{Z+|Z31874}} <!-- dropLast --> * {{Z+|Z12967}} ** {{Z+|Z13373}} ** {{Z|Z18284}} == Removal/filtering == <!-- remove --> * {{Z+|Z12856}} ** {{Z+|Z13081}} *** {{Z|Z18291}} ** {{Z+|Z22865}} ** {{Z+|Z34538}} ** {{Z+|Z19205}} *** {{Z+|Z13078}} *** {{Z+|Z19202}} ** {{Z+|Z31874}} <!-- removeAt --> * {{Z+|Z31364}} ** {{Z+|Z13429}} ** {{Z+|Z13369}} ** {{Z+|Z13373}} ** {{Z+|Z29400}} *** {{Z+|Z18194}} <!-- filter with predicate --> * {{Z+|Z872}} ** {{Z+|Z33453}} ** {{Z+|Z21809}} ** {{Z+|Z28316}} <!-- filter by key --> * {{Z+|Z27413}} ** {{Z+|Z33105}} *** {{Z+|Z24849}} **** {{Z+|Z24855}} == Substitution/transformation == <!-- un/type --> * {{Z|Z15142}} (no-op) * {{Z+|Z18729}} ** {{Z+|Z18475}} ** {{Z+|Z17895}} *** {{Z+|Z28691}} <!-- substituteAt --> * {{Z+|Z31369}} <!-- map --> * {{Z+|Z873}} ** {{Z+|Z24846}} ** {{Z+|Z32453}} ** {{Z+|Z32806}} == Insertion == <!-- prepend --> * {{Z+|Z810}} ** {{Z+|Z24285}} ** {{Z+|Z31721}} <!-- append --> * {{Z+|Z18597}} ** {{Z+|Z12961}} *** {{Z+|Z24150}} *** {{Z|Z18276}} ** {{Z+|Z34519}} ** {{Z+|Z24655}} ** {{Z+|Z33720}} <!-- insert --> * {{Z+|Z31345}} ** {{Z+|Z31340}} ** {{Z+|Z33646}} <!-- concat --> * {{Z+|Z12767}} ** {{Z+|Z18755}} *** {{Z|Z18288}} ** {{Z+|Z27665}} ** {{Z+|Z34538}} == Generation == <!-- list from element --> * {{Z+|Z14046}} ** {{Z+|Z27685}} ** {{Z+|Z24291}} ** {{Z+|Z21389}} <!-- from range --> * {{Z+|Z21821}} ** {{Z+|Z23921}} *** {{Z+|Z24387}} *** {{Z+|Z24382}} <!-- product of lists --> * {{Z+|Z29286}} ** {{Z+|Z29324}} <!-- power set --> * {{Z+|Z18194}} == Ordering and grouping == <!-- reverse --> * {{Z+|Z18759}} ** {{Z+|Z12668}} ** {{Z+|Z18479}} ** {{Z|Z17770}} ** {{Z|Z17774}} ** {{Z|Z17778}} * {{Z+|Z24176}} <!-- cycle --> * {{Z+|Z31355}} ** {{Z+|Z25526}} ** {{Z+|Z22179}} <!-- sort by key --> * {{Z+|Z29725}} * {{Z+|Z19510}} <!-- sort with comparator --> * {{Z+|Z27612}} ** {{Z+|Z17873}} *** {{Z+|Z29429}} ** {{Z+|Z17869}} ** {{Z+|Z12671}} ** {{Z+|Z18281}} <!-- shuffle --> * {{Z+|Z29400}} * {{Z+|Z13247}} <!-- group --> * {{Z+|Z30157}} ** {{Z+|Z32585}} * {{Z+|Z34790}} ** {{Z+|Z30865}} <!-- chunk --> * {{Z+|Z29795}} * {{Z+|Z13224}} <!-- reduce --> * {{Z|Z876}} (actually left-associative ''fold'') ** {{Z|Z12781}} (actually left-associative ''reduce'') *** {{Z|Z20089}} w/ initial empty check ** {{Z|Z12753}} (actually right-associative ''reduce'') <!-- flatten --> * {{Z+|Z12676}} ** {{Z+|Z23606}} ** {{Z+|Z27665}} *** {{Z+|Z32453}} ** {{Z+|Z13155}} == Matrix math == Since we don't have specific types for vectors or matrices, vectors are represented as a list and matrices as a list of lists (to be interpreted as a list of rows). <!-- properties --> * {{Z+|Z31747}} ** {{Z+|Z31752}} * {{Z+|Z24166}} ** {{Z+|Z24171}} <!-- indexing --> * {{Z+|Z31587}} ** {{Z+|Z31585}} <!-- removal --> <!-- transformation --> * {{Z+|Z32806}} * {{Z+|Z31818}} * {{Z+|Z24055}} ** {{Z+|Z17670}} *** {{Z+|Z17675}} ** {{Z+|Z24162}} * {{Z+|Z24060}} ** {{Z+|Z24436}} * {{Z+|Z24185}} ** {{Z+|Z20659}} * {{Z+|Z21903}} * {{Z+|Z24239}} ** {{Z+|Z31749}} * {{Z+|Z24346}} ** {{Z+|Z24342}} * {{Z+|Z14046}} ** {{Z+|Z24177}} * {{Z+|Z29301}} ** {{Z+|Z24182}} * {{Z+|Z24191}} * {{Z+|Z24236}} * {{Z+|Z29308}} <!-- insertion --> * {{Z+|Z810}} ** {{Z+|Z24285}} ** {{Z+|Z24299}} * {{Z+|Z18597}} <!-- ordering --> * {{Z+|Z18759}} * {{Z+|Z24176}} <!-- generation --> * {{Z+|Z24291}} (useful for creating 1x1 matrixes) ** {{Z+|Z24251}} * {{Z+|Z24290}} * {{Z+|Z29286}} ** {{Z+|Z29324}} == Functions expecting a list argument == * [[Special:Search/: "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1"|Complete list of functions]] ** [[Special:Search/: "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1" !"Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1"| Functions specifying a “properly typed” list argument]] ** [[Special:Search/: "Z17K1 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1"|Functions not specifying the type for their list argument (Z1-typed or “untyped”)]] == Functions with list outputs == *[[Special:Search/: "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1"|Complete list of functions]] **[[Special:Search/: "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1" !"Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1|Functions specifying a “properly typed” output list]] **[[Special:Search/: "Z8K2 Z1K1 Z7 Z7K1 Z881 Z881K1 Z1"|Functions not specifying the type for the output list (Z1-typed or “untyped”)]] # If a function specifies an output list with a type other than [[Z1]] (that is, it specifies a "properly typed" list), mismatched elements cause an error if the implementation is in code. # If all objects in an output list have the same type, the list takes that type instead of being Z1-typed. This only happens if the implementation is in code. For compositions, you can use {{Z|Z18475}} to get the same result. #If a code implementation needs custom-converted objects (provided by a {{Z|Z46}}), any list input must be properly typed (objects in a Z1-typed list are not converted). Similarly, any list output must be properly typed (not [[Z1]] in the function specification) or else conversion into a Wikifunctions object will fail. #If a code implementation does not need converted objects, you can use {{Z|Z28691}} to convert a properly typed list to Z1-typed (but this is [[Wikifunctions:Project_chat/Archive/2024/07#Typed_lists_now_open_beyond_Booleans_and_Strings|not officially supported]]). (The list will remain properly typed if there are no custom converters to code. Use {{Z|Z17895}} to make the list Z1-typed unconditionally.) [[Category:Lists of functions]] fwwb1wst7ejp5malnuhza9he9qcgfj7 0 77913 275777 271302 2026-05-17T11:23:19Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275777 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1991" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "pwo" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Western Pwo" }, { "Z1K1": "Z11", "Z11K1": "Z1991", "Z11K2": "ဖျိၩ့ၡိ" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Westliches Pwo" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "pwo de l'Ouest" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "pwo occidental" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } pxdkvb2ro55u7melhoxvanhbr3iz6ee 0 78003 275778 271303 2026-05-17T11:23:44Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275778 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1992" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "juk" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Wapan" }, { "Z1K1": "Z11", "Z11K1": "Z1992", "Z11K2": "Nene Wapan" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Wapan" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "wapan" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } iuka02rmwfkr6j1lu9vk5ljupd62nmj 0 78297 275547 260942 2026-05-16T18:57:40Z Theki 2389 275547 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z32163" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": { "Z1K1": "Z7", "Z7K1": "Z881", "Z881K1": "Z89" }, "Z17K2": "Z32163K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "list of sentences (HTML fragments)" } ] } } ], "Z8K2": "Z89", "Z8K3": [ "Z20", "Z32165" ], "Z8K4": [ "Z14", "Z32164" ], "Z8K5": "Z32163" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "paragraph from list of sentences, space separated" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "join HTML fragments with spaces, into paragraph" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Encloses a list of HTML fragments, separated by spaces, in paragraph tags. Consider using Z33068 (paragraph from sentences) instead." } ] } } h35eqpc7pgvdwlwy1o3fiag1u0nypwt 4 79606 275525 265331 2026-05-16T15:59:52Z Dv103 11127 /* Comments */ Reply 275525 wikitext text/x-wiki ''This is one of a few type proposals based on the Ninai/Udiron project, and thus should be considered alongside others similarly marked.'' == Summary == This type holds a syntactic unit that holds a base word/stem of some kind, with links to any dependents (as construed in [[:w:en:dependency grammar]]s). For more on this particular construct (named 'Catena' in my own work), see the first paragraph of Section 2.2, and the first part of section 4.2.1, of {{Q|130478475}}, as well as [https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py?ref_type=heads#L49 the implementation of this construct in Udiron]. == Uses == * This is one of two fundamental data structures (and a few less fundamental but still important others) that will become necessary for abstract content to truly be abstract. Rather than process lists/sets of strings in assembling a sentence, these units can be manipulated [https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/rendering.py and then rendered] according to functions that can be defined per language. * Many of the instance methods listed in the Udiron implementation linked above would need to be defined as functions here for this to work. * This is intended to correspond with the notion of a '[[:w:en:Catena (linguistics)|catena]]' in dependency grammar, and more specifically to a unit used in [https://universaldependencies.org Universal Dependencies] ([[:d:Wikidata:Lexicographical data/Universal Dependencies|with a mapping to Wikidata here]]). (To help make this just a little less mysterious for this mostly non-linguistic audience, however, I've named this type proposal 'syntactic unit'.) == Structure == * lexeme: The lexeme which this syntactic unit represents. ** See the note under 'sense' below. * language: The language to be applied when this syntactic unit is rendered. ** Note that languages in Ninai/Udiron are pairs of language item and language code; this requires that https://phabricator.wikimedia.org/T344170 be resolved. * sense: The specific meaning of the lexeme which this syntactic unit represents. ** The lexeme and the sense are both included separately because details present at both levels will be needed downstream; as but mere examples, the grammatical gender of a lexeme does not reside on its senses, and if a particular grammatical feature is required when using a particular sense then that feature won't be marked on the lexeme level. ** This and 'lexeme' are not references simply because this unit does not have to represent something that is on wikidata.org; if a custom lexeme/sense were created by some other function, that should be usable here as well. * inflections: The inflections to be applied in rendering this syntactic unit. ** This was inspired by the lists of grammatical features on Wikidata lexeme forms, though the values present in this list do not have to be actual such features on a form of the lexeme. * config: Specific settings for rendering this syntactic unit may be applied here, potentially altering every aspect of the rendering process. ** The current implementation of such a configuration object (introduced because it is not clear whether the Python notion of 'keyword arguments' will be replicated in Wikifunctions) is found [https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/functionconfig.py on this page]. ** This object could be a dedicated configuration type, or it could be a typed map from strings to objects as given in the example below. * left_dependents: The dependents of this syntactic unit that are ''logically'' preceding this one, each with some relationship to this unit. * right_dependents: The dependents of this syntactic unit that are ''logically'' following this one, each with some relationship to this unit. ** For example, in a phrase like "the little old lady who lived in a shoe", the root of this phrase is "lady" (since that phrase at its core denotes a lady). ** Since "the", "little", and "old" precede "lady" when spoken, those words are considered left dependents (''not a single functional unit'', since those words are but a determiner and two adjectives). ** Since "who lived in a shoe" follows "lady" when spoken, those words (forming a single functional unit—a relative clause) are considered a ''single'' right dependent. *** That right dependent has its own structure: its root is "live", its left dependent is "who", and its right dependent is "in a shoe". *** ''That'' right dependent has a root "shoe" and two left dependents "in" and "a". ** Udiron currently groups these into a tuple of lists 'dependents'. * id: A unique identifier for the syntactic unit. ** This was introduced in Udiron (and maintained simply by having a counter that is incremented each time a new syntactic unit is created) in order to deal with the consequences of all objects being immutable in Wikifunctions; if this did not exist, then any time any of the other fields of this syntactic unit was modified, its internal identifier and that of other equally immutable objects that would also need to be modified (such as other syntactic units that have this syntactic unit as a dependent) and comparisons between objects before and after a modification would become considerably more complicated and difficult to track. === Example values === The English phrase "he saw me" (without punctuation!) would consist of three syntactic units whose fields are defined below: * [[:d:Lexeme:L485|L485]], Z1002, [[:d:Lexeme:L485#S1|L485-S1]], ({{Q|131105}}), {}, [], [], "theseentitiesneedsomesortofidscheme" * [[:d:Lexeme:L185|L185]], Z1002, [[:d:Lexeme:L185#S1|L185-S1]], ({{Q|1392475}}, {{Q|21714344}}, {{Q|110786}}), {}, [(''bullet point above'', {{Q|164573}})], [(''bullet point below'', {{Q|2990574}})], "comeupwithanidschemeforthesethings" * [[:d:Lexeme:L485|L487]], Z1002, [[:d:Lexeme:L487#S1|L487-S1]], ({{Q|1233197}}), {}, [], [], "someidschemethatneedstobecomeupwith" {|class="wikitable" style="margin:.6em 1.6em" |- | <syntaxhighlight lang="json" line="line">{   "type": "syntactic unit", "lexeme": "Wikidata lexeme", "language": "language", "sense": "Wikidata lexeme sense", "inflections": "typed list(Wikidata item reference)", "config": "typed map(string, object)", "left_dependents": "typed list(typed pair(syntactic unit, Wikidata item reference))", "right_dependents": "typed list(typed pair(syntactic unit, Wikidata item reference))", "id": "string", }</syntaxhighlight> | <syntaxhighlight lang="json">{   "Z1K1": "Zxyz", "ZxyzK1": "Z6005", "ZxyzK2": "Z60", "ZxyzK3": "Z6006", "ZxyzK4": "Z881(Z6091)", "ZxyzK5": "Z883(Z60, Z1)", "ZxyzK6": "Z881(Z882(syntactic unit, Z6091))", "ZxyzK7": "Z881(Z882(syntactic unit, Z6091))", "ZxyzK8": "Z6", }</syntaxhighlight> |} == Validator == The validator ensures that the lexeme, language, and sense are all valid realizations of those types, all inflections in the inflection set are Wikidata item IDs, and the configuration and dependents lists are well-formed according to their type definitions. == Identity == Equality between syntactic units implies that the components all compare equal, per https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py?ref_type=heads#L126 . (Note that the "id" value is ''not'' considered as part of this check.) == Converting to code == === Python === Ideally this would be directly portable from https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py , since it has been designed to make such a transfer easier, although due to lack of confirmation from the Abstract Wikipedia team of the points of section 2.4 of {{Q|130478475}} this degree of easiness has not been made certain. == Display function == Perhaps something similar to the 'abbr' function at https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py?ref_type=heads#L365 could be used. == Read function == No one should be inputting these as strings; they should be created exclusively by other functions that seek to generate language and perform syntactic manipulations. == Comments == *{{S}}. A question: what is the difference between left and righ dependencies? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:23, 12 April 2026 (UTC) *:@[[User:Mahir256|Mahir256]] [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:23, 12 April 2026 (UTC) *:{{re|Dv103}} I added a hopefully more illustrative example above. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 21:47, 12 April 2026 (UTC) *::Thanks. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 05:31, 13 April 2026 (UTC) * @[[User:Mahir256|Mahir256]] Another question: how do you encode syntactic units without a lexeme? (Like a person's name, the title of a book...) [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:00, 14 April 2026 (UTC) *:{{re|Dv103}} I sort of allude to this in the notes under the 'lexeme' and 'sense' members: "if a custom lexeme/sense were created by some other function, that should be usable here as well". As such proper names would need to be wrapped by functions in 'pseudo-lexemes' before they could be included in any syntactic structure. (An example of a function that assembles a lexeme for downstream use in the syntactic tree is one [https://gitlab.com/mahir256/ninai/-/blob/main/ninai/graph/__init__.py#L28 that assembles a person's name from the 'given name' and 'surname' items linked to it].) [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 15:29, 14 April 2026 (UTC) *::@[[User:Mahir256|Mahir256]] Another question: why put an entire lexeme sense, instead of a lexeme sense reference? The lexeme already contains the sense, so it would be duplicate information. *::Even for "on-the-fly lexemes", the ID fields need to be filled, so we just could just insert the sense in the lexeme, assign it an ID, and then just reference it in the "sense" key of this type. *::I'm asking this because on Wikifunctions, moving around duplicate information means that there is an additional cost in the convertion of the values every time an implementation is called. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:59, 16 May 2026 (UTC) qxpb9tqsbx01w108vpvc4v0duhdp3gu 275528 275525 2026-05-16T16:16:51Z Mahir256 38 /* Comments */ 275528 wikitext text/x-wiki ''This is one of a few type proposals based on the Ninai/Udiron project, and thus should be considered alongside others similarly marked.'' == Summary == This type holds a syntactic unit that holds a base word/stem of some kind, with links to any dependents (as construed in [[:w:en:dependency grammar]]s). For more on this particular construct (named 'Catena' in my own work), see the first paragraph of Section 2.2, and the first part of section 4.2.1, of {{Q|130478475}}, as well as [https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py?ref_type=heads#L49 the implementation of this construct in Udiron]. == Uses == * This is one of two fundamental data structures (and a few less fundamental but still important others) that will become necessary for abstract content to truly be abstract. Rather than process lists/sets of strings in assembling a sentence, these units can be manipulated [https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/rendering.py and then rendered] according to functions that can be defined per language. * Many of the instance methods listed in the Udiron implementation linked above would need to be defined as functions here for this to work. * This is intended to correspond with the notion of a '[[:w:en:Catena (linguistics)|catena]]' in dependency grammar, and more specifically to a unit used in [https://universaldependencies.org Universal Dependencies] ([[:d:Wikidata:Lexicographical data/Universal Dependencies|with a mapping to Wikidata here]]). (To help make this just a little less mysterious for this mostly non-linguistic audience, however, I've named this type proposal 'syntactic unit'.) == Structure == * lexeme: The lexeme which this syntactic unit represents. ** See the note under 'sense' below. * language: The language to be applied when this syntactic unit is rendered. ** Note that languages in Ninai/Udiron are pairs of language item and language code; this requires that https://phabricator.wikimedia.org/T344170 be resolved. * sense: The specific meaning of the lexeme which this syntactic unit represents. ** The lexeme and the sense are both included separately because details present at both levels will be needed downstream; as but mere examples, the grammatical gender of a lexeme does not reside on its senses, and if a particular grammatical feature is required when using a particular sense then that feature won't be marked on the lexeme level. ** This and 'lexeme' are not references simply because this unit does not have to represent something that is on wikidata.org; if a custom lexeme/sense were created by some other function, that should be usable here as well. * inflections: The inflections to be applied in rendering this syntactic unit. ** This was inspired by the lists of grammatical features on Wikidata lexeme forms, though the values present in this list do not have to be actual such features on a form of the lexeme. * config: Specific settings for rendering this syntactic unit may be applied here, potentially altering every aspect of the rendering process. ** The current implementation of such a configuration object (introduced because it is not clear whether the Python notion of 'keyword arguments' will be replicated in Wikifunctions) is found [https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/functionconfig.py on this page]. ** This object could be a dedicated configuration type, or it could be a typed map from strings to objects as given in the example below. * left_dependents: The dependents of this syntactic unit that are ''logically'' preceding this one, each with some relationship to this unit. * right_dependents: The dependents of this syntactic unit that are ''logically'' following this one, each with some relationship to this unit. ** For example, in a phrase like "the little old lady who lived in a shoe", the root of this phrase is "lady" (since that phrase at its core denotes a lady). ** Since "the", "little", and "old" precede "lady" when spoken, those words are considered left dependents (''not a single functional unit'', since those words are but a determiner and two adjectives). ** Since "who lived in a shoe" follows "lady" when spoken, those words (forming a single functional unit—a relative clause) are considered a ''single'' right dependent. *** That right dependent has its own structure: its root is "live", its left dependent is "who", and its right dependent is "in a shoe". *** ''That'' right dependent has a root "shoe" and two left dependents "in" and "a". ** Udiron currently groups these into a tuple of lists 'dependents'. * id: A unique identifier for the syntactic unit. ** This was introduced in Udiron (and maintained simply by having a counter that is incremented each time a new syntactic unit is created) in order to deal with the consequences of all objects being immutable in Wikifunctions; if this did not exist, then any time any of the other fields of this syntactic unit was modified, its internal identifier and that of other equally immutable objects that would also need to be modified (such as other syntactic units that have this syntactic unit as a dependent) and comparisons between objects before and after a modification would become considerably more complicated and difficult to track. === Example values === The English phrase "he saw me" (without punctuation!) would consist of three syntactic units whose fields are defined below: * [[:d:Lexeme:L485|L485]], Z1002, [[:d:Lexeme:L485#S1|L485-S1]], ({{Q|131105}}), {}, [], [], "theseentitiesneedsomesortofidscheme" * [[:d:Lexeme:L185|L185]], Z1002, [[:d:Lexeme:L185#S1|L185-S1]], ({{Q|1392475}}, {{Q|21714344}}, {{Q|110786}}), {}, [(''bullet point above'', {{Q|164573}})], [(''bullet point below'', {{Q|2990574}})], "comeupwithanidschemeforthesethings" * [[:d:Lexeme:L485|L487]], Z1002, [[:d:Lexeme:L487#S1|L487-S1]], ({{Q|1233197}}), {}, [], [], "someidschemethatneedstobecomeupwith" {|class="wikitable" style="margin:.6em 1.6em" |- | <syntaxhighlight lang="json" line="line">{   "type": "syntactic unit", "lexeme": "Wikidata lexeme", "language": "language", "sense": "Wikidata lexeme sense", "inflections": "typed list(Wikidata item reference)", "config": "typed map(string, object)", "left_dependents": "typed list(typed pair(syntactic unit, Wikidata item reference))", "right_dependents": "typed list(typed pair(syntactic unit, Wikidata item reference))", "id": "string", }</syntaxhighlight> | <syntaxhighlight lang="json">{   "Z1K1": "Zxyz", "ZxyzK1": "Z6005", "ZxyzK2": "Z60", "ZxyzK3": "Z6006", "ZxyzK4": "Z881(Z6091)", "ZxyzK5": "Z883(Z60, Z1)", "ZxyzK6": "Z881(Z882(syntactic unit, Z6091))", "ZxyzK7": "Z881(Z882(syntactic unit, Z6091))", "ZxyzK8": "Z6", }</syntaxhighlight> |} == Validator == The validator ensures that the lexeme, language, and sense are all valid realizations of those types, all inflections in the inflection set are Wikidata item IDs, and the configuration and dependents lists are well-formed according to their type definitions. == Identity == Equality between syntactic units implies that the components all compare equal, per https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py?ref_type=heads#L126 . (Note that the "id" value is ''not'' considered as part of this check.) == Converting to code == === Python === Ideally this would be directly portable from https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py , since it has been designed to make such a transfer easier, although due to lack of confirmation from the Abstract Wikipedia team of the points of section 2.4 of {{Q|130478475}} this degree of easiness has not been made certain. == Display function == Perhaps something similar to the 'abbr' function at https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py?ref_type=heads#L365 could be used. == Read function == No one should be inputting these as strings; they should be created exclusively by other functions that seek to generate language and perform syntactic manipulations. == Comments == *{{S}}. A question: what is the difference between left and righ dependencies? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:23, 12 April 2026 (UTC) *:@[[User:Mahir256|Mahir256]] [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:23, 12 April 2026 (UTC) *:{{re|Dv103}} I added a hopefully more illustrative example above. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 21:47, 12 April 2026 (UTC) *::Thanks. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 05:31, 13 April 2026 (UTC) * @[[User:Mahir256|Mahir256]] Another question: how do you encode syntactic units without a lexeme? (Like a person's name, the title of a book...) [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:00, 14 April 2026 (UTC) *:{{re|Dv103}} I sort of allude to this in the notes under the 'lexeme' and 'sense' members: "if a custom lexeme/sense were created by some other function, that should be usable here as well". As such proper names would need to be wrapped by functions in 'pseudo-lexemes' before they could be included in any syntactic structure. (An example of a function that assembles a lexeme for downstream use in the syntactic tree is one [https://gitlab.com/mahir256/ninai/-/blob/main/ninai/graph/__init__.py#L28 that assembles a person's name from the 'given name' and 'surname' items linked to it].) [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 15:29, 14 April 2026 (UTC) *::@[[User:Mahir256|Mahir256]] Another question: why put an entire lexeme sense, instead of a lexeme sense reference? The lexeme already contains the sense, so it would be duplicate information. *::Even for "on-the-fly lexemes", the ID fields need to be filled, so we just could just insert the sense in the lexeme, assign it an ID, and then just reference it in the "sense" key of this type. *::I'm asking this because on Wikifunctions, moving around duplicate information means that there is an additional cost in the convertion of the values every time an implementation is called. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:59, 16 May 2026 (UTC) *:::{{re|Dv103}} The main reason for this is when a calque needs to be constructed from another lexeme, or when the parts of a compound lexeme need to be moved to discontinuous places (requiring that a lexeme be split based on its {{P|5238}} statements), some features noted on the original lexeme's senses may be needed. (Some examples I have in mind include {{P|9971}} values when calquing a verb, handling separable verbs in Germanic languages, or the inflection of idioms with fixed complements.) [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 16:16, 16 May 2026 (UTC) 77lusdlasgg8wr2jhlpfn1x6kvnuj6e 275533 275528 2026-05-16T16:34:27Z Dv103 11127 /* Comments */ Reply 275533 wikitext text/x-wiki ''This is one of a few type proposals based on the Ninai/Udiron project, and thus should be considered alongside others similarly marked.'' == Summary == This type holds a syntactic unit that holds a base word/stem of some kind, with links to any dependents (as construed in [[:w:en:dependency grammar]]s). For more on this particular construct (named 'Catena' in my own work), see the first paragraph of Section 2.2, and the first part of section 4.2.1, of {{Q|130478475}}, as well as [https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py?ref_type=heads#L49 the implementation of this construct in Udiron]. == Uses == * This is one of two fundamental data structures (and a few less fundamental but still important others) that will become necessary for abstract content to truly be abstract. Rather than process lists/sets of strings in assembling a sentence, these units can be manipulated [https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/rendering.py and then rendered] according to functions that can be defined per language. * Many of the instance methods listed in the Udiron implementation linked above would need to be defined as functions here for this to work. * This is intended to correspond with the notion of a '[[:w:en:Catena (linguistics)|catena]]' in dependency grammar, and more specifically to a unit used in [https://universaldependencies.org Universal Dependencies] ([[:d:Wikidata:Lexicographical data/Universal Dependencies|with a mapping to Wikidata here]]). (To help make this just a little less mysterious for this mostly non-linguistic audience, however, I've named this type proposal 'syntactic unit'.) == Structure == * lexeme: The lexeme which this syntactic unit represents. ** See the note under 'sense' below. * language: The language to be applied when this syntactic unit is rendered. ** Note that languages in Ninai/Udiron are pairs of language item and language code; this requires that https://phabricator.wikimedia.org/T344170 be resolved. * sense: The specific meaning of the lexeme which this syntactic unit represents. ** The lexeme and the sense are both included separately because details present at both levels will be needed downstream; as but mere examples, the grammatical gender of a lexeme does not reside on its senses, and if a particular grammatical feature is required when using a particular sense then that feature won't be marked on the lexeme level. ** This and 'lexeme' are not references simply because this unit does not have to represent something that is on wikidata.org; if a custom lexeme/sense were created by some other function, that should be usable here as well. * inflections: The inflections to be applied in rendering this syntactic unit. ** This was inspired by the lists of grammatical features on Wikidata lexeme forms, though the values present in this list do not have to be actual such features on a form of the lexeme. * config: Specific settings for rendering this syntactic unit may be applied here, potentially altering every aspect of the rendering process. ** The current implementation of such a configuration object (introduced because it is not clear whether the Python notion of 'keyword arguments' will be replicated in Wikifunctions) is found [https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/functionconfig.py on this page]. ** This object could be a dedicated configuration type, or it could be a typed map from strings to objects as given in the example below. * left_dependents: The dependents of this syntactic unit that are ''logically'' preceding this one, each with some relationship to this unit. * right_dependents: The dependents of this syntactic unit that are ''logically'' following this one, each with some relationship to this unit. ** For example, in a phrase like "the little old lady who lived in a shoe", the root of this phrase is "lady" (since that phrase at its core denotes a lady). ** Since "the", "little", and "old" precede "lady" when spoken, those words are considered left dependents (''not a single functional unit'', since those words are but a determiner and two adjectives). ** Since "who lived in a shoe" follows "lady" when spoken, those words (forming a single functional unit—a relative clause) are considered a ''single'' right dependent. *** That right dependent has its own structure: its root is "live", its left dependent is "who", and its right dependent is "in a shoe". *** ''That'' right dependent has a root "shoe" and two left dependents "in" and "a". ** Udiron currently groups these into a tuple of lists 'dependents'. * id: A unique identifier for the syntactic unit. ** This was introduced in Udiron (and maintained simply by having a counter that is incremented each time a new syntactic unit is created) in order to deal with the consequences of all objects being immutable in Wikifunctions; if this did not exist, then any time any of the other fields of this syntactic unit was modified, its internal identifier and that of other equally immutable objects that would also need to be modified (such as other syntactic units that have this syntactic unit as a dependent) and comparisons between objects before and after a modification would become considerably more complicated and difficult to track. === Example values === The English phrase "he saw me" (without punctuation!) would consist of three syntactic units whose fields are defined below: * [[:d:Lexeme:L485|L485]], Z1002, [[:d:Lexeme:L485#S1|L485-S1]], ({{Q|131105}}), {}, [], [], "theseentitiesneedsomesortofidscheme" * [[:d:Lexeme:L185|L185]], Z1002, [[:d:Lexeme:L185#S1|L185-S1]], ({{Q|1392475}}, {{Q|21714344}}, {{Q|110786}}), {}, [(''bullet point above'', {{Q|164573}})], [(''bullet point below'', {{Q|2990574}})], "comeupwithanidschemeforthesethings" * [[:d:Lexeme:L485|L487]], Z1002, [[:d:Lexeme:L487#S1|L487-S1]], ({{Q|1233197}}), {}, [], [], "someidschemethatneedstobecomeupwith" {|class="wikitable" style="margin:.6em 1.6em" |- | <syntaxhighlight lang="json" line="line">{   "type": "syntactic unit", "lexeme": "Wikidata lexeme", "language": "language", "sense": "Wikidata lexeme sense", "inflections": "typed list(Wikidata item reference)", "config": "typed map(string, object)", "left_dependents": "typed list(typed pair(syntactic unit, Wikidata item reference))", "right_dependents": "typed list(typed pair(syntactic unit, Wikidata item reference))", "id": "string", }</syntaxhighlight> | <syntaxhighlight lang="json">{   "Z1K1": "Zxyz", "ZxyzK1": "Z6005", "ZxyzK2": "Z60", "ZxyzK3": "Z6006", "ZxyzK4": "Z881(Z6091)", "ZxyzK5": "Z883(Z60, Z1)", "ZxyzK6": "Z881(Z882(syntactic unit, Z6091))", "ZxyzK7": "Z881(Z882(syntactic unit, Z6091))", "ZxyzK8": "Z6", }</syntaxhighlight> |} == Validator == The validator ensures that the lexeme, language, and sense are all valid realizations of those types, all inflections in the inflection set are Wikidata item IDs, and the configuration and dependents lists are well-formed according to their type definitions. == Identity == Equality between syntactic units implies that the components all compare equal, per https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py?ref_type=heads#L126 . (Note that the "id" value is ''not'' considered as part of this check.) == Converting to code == === Python === Ideally this would be directly portable from https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py , since it has been designed to make such a transfer easier, although due to lack of confirmation from the Abstract Wikipedia team of the points of section 2.4 of {{Q|130478475}} this degree of easiness has not been made certain. == Display function == Perhaps something similar to the 'abbr' function at https://gitlab.com/mahir256/udiron/-/blob/main/udiron/base/catena.py?ref_type=heads#L365 could be used. == Read function == No one should be inputting these as strings; they should be created exclusively by other functions that seek to generate language and perform syntactic manipulations. == Comments == *{{S}}. A question: what is the difference between left and righ dependencies? [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:23, 12 April 2026 (UTC) *:@[[User:Mahir256|Mahir256]] [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 19:23, 12 April 2026 (UTC) *:{{re|Dv103}} I added a hopefully more illustrative example above. [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 21:47, 12 April 2026 (UTC) *::Thanks. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 05:31, 13 April 2026 (UTC) * @[[User:Mahir256|Mahir256]] Another question: how do you encode syntactic units without a lexeme? (Like a person's name, the title of a book...) [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:00, 14 April 2026 (UTC) *:{{re|Dv103}} I sort of allude to this in the notes under the 'lexeme' and 'sense' members: "if a custom lexeme/sense were created by some other function, that should be usable here as well". As such proper names would need to be wrapped by functions in 'pseudo-lexemes' before they could be included in any syntactic structure. (An example of a function that assembles a lexeme for downstream use in the syntactic tree is one [https://gitlab.com/mahir256/ninai/-/blob/main/ninai/graph/__init__.py#L28 that assembles a person's name from the 'given name' and 'surname' items linked to it].) [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 15:29, 14 April 2026 (UTC) *::@[[User:Mahir256|Mahir256]] Another question: why put an entire lexeme sense, instead of a lexeme sense reference? The lexeme already contains the sense, so it would be duplicate information. *::Even for "on-the-fly lexemes", the ID fields need to be filled, so we just could just insert the sense in the lexeme, assign it an ID, and then just reference it in the "sense" key of this type. *::I'm asking this because on Wikifunctions, moving around duplicate information means that there is an additional cost in the convertion of the values every time an implementation is called. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 15:59, 16 May 2026 (UTC) *:::{{re|Dv103}} The main reason for this is when a calque needs to be constructed from another lexeme, or when the parts of a compound lexeme need to be moved to discontinuous places (requiring that a lexeme be split based on its {{P|5238}} statements), some features noted on the original lexeme's senses may be needed. (Some examples I have in mind include {{P|9971}} values when calquing a verb, handling separable verbs in Germanic languages, or the inflection of idioms with fixed complements.) [[User:Mahir256|Mahir256]] ([[User talk:Mahir256|talk]]) 16:16, 16 May 2026 (UTC) *::::Makes sense. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 16:34, 16 May 2026 (UTC) 1b7v89212bzxm5tb4bg8lzgaghqgkil 4 80104 275635 274175 2026-05-17T03:08:09Z SpBot 978 archiving 1 section from [[Wikifunctions:Project chat]] (after section [[Wikifunctions:Project chat/Archive/2026/04#No_place_to_ask_to_activate_a_function?|No_place_to_ask_to_activate_a_function?]]) 275635 wikitext text/x-wiki {{Talkarchive}} == Wikifunctions & Abstract Wikipedia Newsletter #242 is out: Request for Discussion: Syntactic tables == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-02|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 [[: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/1776101400 April 13, 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]]) 13:37, 3 April 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=30325620 --> :<small>This section was archived on a request by: [[User:Mdktb|Mdktb]] ([[User talk:Mdktb|talk]]) 17:13, 10 April 2026 (UTC)</small> == Special:CreateObject doesn't let me create a typed list == Hello. I tried to create a typed list with all English varieties on Wikifunctions, to create consistency between different configs, but [[Special:CreateObject]] doesn't show typed list as an option for creating. Is this a bug or an intentional restriction? [[User:ChaoticVermillion|ChaoticVermillion]] ([[User talk:ChaoticVermillion|talk]]) 08:24, 2 April 2026 (UTC) :@[[User:ChaoticVermillion|ChaoticVermillion]]: A typed list is an instance of a function call, which is prohibited as a persisted Object. Maybe you want an enum? See [[Wikifunctions:Type proposals]] for the process for creating such a thing. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 12:01, 2 April 2026 (UTC) ::I don't want any sort of enum for this, I just want a list of English varieties (English, American English, Australian English, etc.) as an object that I can put in configs. I tried making an object as a function call, but apparently I have to be a member of the staff to do it. [[User:ChaoticVermillion|ChaoticVermillion]] ([[User talk:ChaoticVermillion|talk]]) 12:07, 2 April 2026 (UTC) :::I’ve started this with {{Z|Z33034}}. I’m guessing you were trying to create an object of type {{Z|Z7}} rather than an object whose type is a [[Z7]]. There’s a subtle but important difference. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 12:29, 2 April 2026 (UTC) ::::How do you create a object whose type is a [[Z7]] then? I can't see any option to do this. [[User:ChaoticVermillion|ChaoticVermillion]] ([[User talk:ChaoticVermillion|talk]]) 12:32, 2 April 2026 (UTC) :::::When you are creating an object you must specify its type. By default, the UI expects you to provide a reference to the type, so you can just type in the selector box and click the type you want. For an object like a typed list, the type is specified as a function call, so you click the menu dots beside “type” and choose “function call” instead of “reference”. The selector now allows you to search for functions that can return a type object. You start entering “typed list” and select it in the normal way. Then the UI will allow you to specify the argument to the function call, which is the type shared by all elements in the list. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 13:12, 2 April 2026 (UTC) == Unable to use the Z32643 function. == I'm trying to use the [[Z32643]] (Article-less multi instantiating fragment) function to edit an article in Abstract Wikipedia, but it looks like it's missing connected implementations, and it looks like i don't have the permissions to connect the function with the implementation and use it in ab.wiki. Since i'm not familiar with Wikifunctions, i would like to get help for this specific problem. Thanks. --[[User:Mattiz6276|Mattiz6276]] ([[User talk:Mattiz6276|talk]]) 13:50, 2 April 2026 (UTC) :@[[User:Mattiz6276|Mattiz6276]]: Hey there, it looks like that's a work-in-progress by @[[User:MetalBreaksAndBends|MetalBreaksAndBends]]. There's only a fall-back implementation, Z32652, which fails its own test for a second item. I can connect the items together but it might not work as you expect? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 14:06, 2 April 2026 (UTC) ::Maybe… I don’t think functions without implementations should be appearing on AW so I have amended the label to avoid giving the impression that this function is available. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 14:23, 2 April 2026 (UTC) == Being able to use edit summaries == I have wanted to use edit summaries a few times when connecting or disconnecting implementations or tests, and I have found that the only way to do that is to use the [[:User:%D7%9E%D7%A7%D7%A3/wikilambda_editsource.js|wikilambda editsource]] tool. I feel like it would be a lot more convenient to be able to make these edit summaries without having to use that tool. [[User:ChaoticVermillion|ChaoticVermillion]] ([[User talk:ChaoticVermillion|talk]]) 08:40, 3 April 2026 (UTC) == Definite forms == [[Talk:Z32162|I've noticed an incomplete implementation and would like to work on fixing it, but need advice.]] [[User:Ijon|Ijon]] ([[User talk:Ijon|talk]]) 21:05, 3 April 2026 (UTC) == Wikifunctions & Abstract Wikipedia Newsletter #243 is out: Community proposals for capturing meaning == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-10|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 [[: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/1776101400 April 13, 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]]) 15:35, 10 April 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=30325620 --> :<small>This section was archived on a request by: [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:12, 3 May 2026 (UTC)</small> == Wikifunctions & Abstract Wikipedia Newsletter #244 is out: Milestones; Some major issues hopefully resolved == There is [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-04-16|a new update]] for Abstract Wikipedia and Wikifunctions. Please, come and read it! In this issue, we celebrate 4000 functions on Wikifunctions and 1000 abstract articles on Abstract Wikipedia, we announce that we should have fixed some major issues with the websites, we inform you on 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:22, 17 April 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=30325620 --> :<small>This section was archived on a request by: [[User:Sannita (WMF)|Sannita (WMF)]] ([[User talk:Sannita (WMF)|talk]]) 13:12, 3 May 2026 (UTC)</small> == Help me understand why test passes but running function with same input errors == I've been working on a function that I thought I had working correctly: {{Z+|Z31108}}. It has a test which is passing, but when I enter the same Wikidata item as the test uses (or any other relevant item that it ought to work for), it errors. I can't figure out what's wrong (and the function itself seemed to be working as expected the last time worked on it, a month ago), and I don't know how to interpret the error info. The error output is: <code> Error type: Unspecified error Error data: error information: "cannot read property 'Z6003K4' of undefined" Execution debug logs: Z12696K2 (find this) ==> ZObject<Z1K1:{'Z1K1': 'Z9', 'Z9K1': 'Z6007'},Z6007K1:ZObject<Z1K1:{'Z1K1': 'Z9', 'Z9K1': 'Z6092'},Z6092K1:P3831>,Z6007K2:ZObject<Z1K1:{'Z1K1': 'Z9', 'Z9K1': 'Z6091'},Z6091K1:Q7380503>,Z6007K3:ZReference<Z6021>> </code> -- [[User:Ragesoss|Ragesoss]] ([[User talk:Ragesoss|talk]]) 18:02, 10 April 2026 (UTC) :Hmm… I’ve had a quick look and found a comparable error with {{Z|Z29937}}, which was passing “4 months ago”. The debug comes from {{Z|Z12863}}, after it fails to find a match. This is probably because Z6007K3 is ZReference("Z6021") rather than a Z6020 object, as it appears in the debug logs for your test “28 days ago”: :"Z6007K3":{"Z1K1":{"Z1K1":"Z9","Z9K1":"Z6020"},"Z6020K1":{"Z9K1":"Z6021"}} :This means it’s probably a bug introduced by a recent software change. I’ll take a closer look over the weekend, but the actual error for your test case now is: :Unspecified error (error information: "cannot read property 'Z6003K4' of undefined") :I’m guessing that’s from there being no guard against an empty array in {{Z|Z23681}}, but we’ll see. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 23:22, 10 April 2026 (UTC) :I tracked down the bug to [[Z29869]] and fixed that, but the tests for [[Z31659]] are still failing. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 05:44, 11 April 2026 (UTC) ::Thanks. I’ve re-implemented {{Z|Z23680}} with {{Z|Z33331}} so we at least get a meaningful error in {{Z|Z31108}}. The new implementation explicitly caters for the alternative representation of {{Z|Z6040}} and errors on the empty list it gets from {{Z|Z31659}}. ::I also made a [[Z33332|simple Python implementation]], which seems to work. [[User:GrounderUK|GrounderUK]] ([[User talk:GrounderUK|talk]]) 16:29, 11 April 2026 (UTC) == No place to ask to activate a function? == I just discovered the {{Z|Z11390}} function and decided to make an overarching language-selecting function for it. After some fiddling around and studying how {{Z|Z32321}} and its set works, I now have {{Z|Z33439}} which has a config object ({{Z|Z33441}}) that selects between the two preexisting language-specific versions I found (English and Malayalam) and the new one I created for my other native language, {{Z|Z33440}}. Except I can't get these to work, because, from what I understand, only [[Wikifunctions:Functioneers|functioneers]] can activate newly created functions and implementations? So where do I apply for the {{Z|Z33439}} and {{Z|Z33440}} functions to be activated? Perhaps we should have a place to ask for it, a la [[w:WP:NPP]] — call it [[Project:New Functions Patrol|New Functions Patrol]] if you will. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] ([[User talk:UndueMarmot|talk]]) 08:58, 14 April 2026 (UTC) :There's [[Wikifunctions:Community portal]] for this. By the way, {{Z|Z33445}} doesn't work because all the code must be inside the main function in Python code. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 09:19, 14 April 2026 (UTC) ::Huh. How could I have missed that? ::But anyway, I've moved the code in {{Z|Z33445}} into inside the main function block. ::Is there any reason why WF decided not to simply allow anyone to write functions? After all, that's how it works with wikitext templates, and these functions are fundamentally serving the same purposes as templates, just written in a different way. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 11:25, 14 April 2026 (UTC) :::I've fixed a couple of technical issues, but tests still fail. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:28, 14 April 2026 (UTC) ::::The tests pass now after some more changes to the code: [[Special:Diff/265232/cur]]. —[[User:UndueMarmot|<span style="color:#705ccb;">Undue</span><span style="color:#cfdfa3;background-color:#705ccb;">Marmot</span>]] <small>([[User talk:UndueMarmot|talk]])</small> 12:01, 14 April 2026 (UTC) :::::{{D|Connected}} [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 12:02, 14 April 2026 (UTC) :::I think it's a security issue, since Wikifunctions implementations could teoretically be malicious. [[User:Dv103|Dv103]] ([[User talk:Dv103|talk]]) 11:29, 14 April 2026 (UTC) ::::This ^^^. We're very lenient, though, once you've created a few working functions you can apply for the right, per [[WF:Functioneer]]. [[User:Feeglgeef|Feeglgeef]] ([[User talk:Feeglgeef|talk]]) 12:26, 14 April 2026 (UTC) ::::That explanation [[phab:T343559#11421293|doesn't add up]]. A reason to limit ''connection powers'' to Functioneers might be to prevent vandalism, considering Functions can be used across wikis. But user-provided code is already being executed even without a Functioneer connecting it. [[User:YoshiRulz|YoshiRulz]] ([[User talk:YoshiRulz|talk]]) 20:01, 16 April 2026 (UTC) k6ev7nqtnk2tix13zjs82o1kmfz712y 3 80884 275600 267423 2026-05-17T01:20:17Z JJPMaster 6409 /* Z32702 */ new section 275600 wikitext text/x-wiki == nasin nanpa pona function == The function you recently created, {{Z|Z33151}}, is a duplicate of {{Z|Z24721}}. I ported over your implementation to the older function ({{Z|Z24725}}). Not sure what to do in this sort of situation, so I just decided to raise the issue on the function's talk page. I hope this is not an inconvenience to you. Thank you for contributing. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:20, 21 April 2026 (UTC) == [[Z32702]] == Do you have any plans to make additional language versions of [[Z32702]]? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 01:20, 17 May 2026 (UTC) 2bu02qlj0957z26ok6swxdi6m0iwi2i 275622 275600 2026-05-17T02:45:05Z ChaoticV 31127 /* Z32702 */ Reply 275622 wikitext text/x-wiki == nasin nanpa pona function == The function you recently created, {{Z|Z33151}}, is a duplicate of {{Z|Z24721}}. I ported over your implementation to the older function ({{Z|Z24725}}). Not sure what to do in this sort of situation, so I just decided to raise the issue on the function's talk page. I hope this is not an inconvenience to you. Thank you for contributing. &mdash; [[User:Theki|rae^5e]] &lt;[[User talk:Theki|talk]]&gt; 14:20, 21 April 2026 (UTC) == [[Z32702]] == Do you have any plans to make additional language versions of [[Z32702]]? [[User:JJPMaster|JJP]]_{[[User talk:JJPMaster|Mas]]_{[[Special:Contributions/JJPMaster|ter]]}} ([[wikt:she|she]]/[[wikt:they|they]]) 01:20, 17 May 2026 (UTC) :This function was originally an English function but I think someone changed it to be multilingual. I don't have any plans to add languages to it but feel free to add some. [[User:ChaoticV|ChaoticV]] ([[User talk:ChaoticV|talk]]) 02:45, 17 May 2026 (UTC) n07xp4hqdfskpnjinwahk4ip1yhrzcc 2 81186 275543 275409 2026-05-16T17:39:13Z HenkvD 1290 275543 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;" | | colspan="10" | <div class="plainlinks"><center>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>Gebruiker:HenkvD op [[commons:Template talk:Sisterlinks|zusterprojecten]]:&nbsp;&nbsp;&nbsp;&nbsp;</b><small>[http://nl.wikipedia.org/w/index.php?title=Gebruiker:HenkvD/Categorie%C3%ABn&action=edit (bewerk)]</div></small></center> |- | 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 id="cat" 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 id="cat" 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 id="cat" class="plainlinks">[http://strategy.wikimedia.org/wiki/User:HenkvD Strategy]<br><div id="cat" class="plainlinks">'''[http://nl.wikimedia.org/wiki/Gebruiker:HenkvD nl:]''' </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>'''Wikifunctions''' <br>[[abstract:User:HenkvD|AbstractWiki]] |} My name is Henk, from the Netherlands ([[:nl:Gebruiker:HenkvD]]). I am interested in Abstract Wikipedia functionality and have general knowledge if the Dutch language (as native speaker). As most other the 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, but can't actually program them, except minor adjustments.<br> I will try to analyse Wikifunction, Wikidata, lexemes and add Wikifunction tests if needed. {{#babel:nl|en-3|de-1}} Usefull pages: * [[Wikifunctions:Status updates]] * [[Wikifunctions:Requests for connection and disconnection]] * [[Wikifunctions:Requests for user groups]] * [[:Category:Natural language generation functions]] 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 ] {| class="wikitable" ! Function !! English !! Z1157 Nederlands !! 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}} |} dhfsim7xdklk0tyn3d6faxe9dcsl635 0 81432 275746 270677 2026-05-17T10:17:22Z Sun8908 9804 Added Z35260 to the approved list of test cases 275746 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z34212" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z34212K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "pinyin" } ] } } ], "Z8K2": { "Z1K1": "Z7", "Z7K1": "Z881", "Z881K1": "Z6" }, "Z8K3": [ "Z20", "Z34217", "Z34216", "Z34220", "Z34477", "Z35260" ], "Z8K4": [ "Z14", "Z34215" ], "Z8K5": "Z34212" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "standard pinyin to list of single character pinyin" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Hanyu Pinyin to list of single character pinyin", "single character pinyin from standard pinyin" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Extract a list of single character pinyin from a standard pinyin" } ] } } gbrqf6owpm3xt23lzozve4e17al6xxo 275747 275746 2026-05-17T10:17:25Z Sun8908 9804 Added Z35259 to the approved list of implementations 275747 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z34212" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z34212K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "pinyin" } ] } } ], "Z8K2": { "Z1K1": "Z7", "Z7K1": "Z881", "Z881K1": "Z6" }, "Z8K3": [ "Z20", "Z34217", "Z34216", "Z34220", "Z34477", "Z35260" ], "Z8K4": [ "Z14", "Z34215", "Z35259" ], "Z8K5": "Z34212" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "standard pinyin to list of single character pinyin" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Hanyu Pinyin to list of single character pinyin", "single character pinyin from standard pinyin" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Extract a list of single character pinyin from a standard pinyin" } ] } } 0caw5qmytkr55vhdounoi2zjgwjmgf9 0 81437 275699 269300 2026-05-17T08:32:02Z Sun8908 9804 275699 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z34215" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z34212", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z610", "Z16K2": "def Z34212(Z34212K1):\n\timport re\n\t\n\tVOWEL = \"AaĀāÁáǍǎÀàEeĒēÉéĚěÈèIiĪīÍíǏǐÌìOoŌōÓóǑǒÒòUuŪūÚúǓǔÙùÜüǕǖǗǘǙǚǛǜÊêÊ̄ê̄ẾếÊ̌ê̌Ềề\"\n\tlist_pinyin = re.split(r\"['\\s\\-]+\", Z34212K1)\n\t\n\tsingle_char_pattern = rf\"([BbCcDdGgHhJjKkLlMmNnPpQqRrSsTtWwXxYyZz]{{0,2}}[{VOWEL}]+)(n(?![{VOWEL}]))?(g(?![{VOWEL}]))?(r(?![{VOWEL}]))?\" # fuzzy match, suffice as only valid pinyin is considered\n\t\n\tlist_single_char_pinyin = []\n\tfor py in list_pinyin:\n\t\tmatches = re.finditer(single_char_pattern, py)\n\t\tfor m in matches:\n\t\t\tsyl = m.group(0)\n\t\t\tif syl:\n\t\t\t\tlist_single_char_pinyin.append(syl)\n\t\n\treturn list_single_char_pinyin" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "pinyin to list of single pinyin, python hardcoded" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "pinyin to list of single character pinyin, python hardcoded" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } dgtnrrgap6658wxmniuh9ozi6oucg4t 0 81941 275534 270943 2026-05-16T16:38:01Z JJPMaster 6409 undeprecated 275534 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z34511" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z34510", "Z14K2": { "Z1K1": "Z7", "Z7K1": "Z802", "Z802K1": { "Z1K1": "Z7", "Z7K1": "Z32663", "Z32663K1": { "Z1K1": "Z18", "Z18K1": "Z34510K1" } }, "Z802K2": { "Z1K1": "Z7", "Z7K1": "Z802", "Z802K1": { "Z1K1": "Z7", "Z7K1": "Z34542", "Z34542K1": { "Z1K1": "Z7", "Z7K1": "Z23756", "Z23756K1": { "Z1K1": "Z18", "Z18K1": "Z34510K1" } }, "Z34542K2": { "Z1K1": "Z6092", "Z6092K1": "P21" }, "Z34542K3": { "Z1K1": "Z6091", "Z6091K1": "Q6581097" } }, "Z802K2": { "Z1K1": "Z40", "Z40K1": "Z41" }, "Z802K3": { "Z1K1": "Z40", "Z40K1": "Z42" } }, "Z802K3": { "Z1K1": "Z40", "Z40K1": "Z42" } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Q5 is male?, comp" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ek7jjmod9nbjd5w11gampb11hx1xjy4 0 81977 275527 271022 2026-05-16T16:16:16Z JJPMaster 6409 Added Z35234 to the approved list of implementations 275527 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z34542" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6091", "Z17K2": "Z34542K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "subject" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z6092", "Z17K2": "Z34542K2", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "property" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z1", "Z17K2": "Z34542K3", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "value" } ] } } ], "Z8K2": "Z40", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14", "Z35234" ], "Z8K5": "Z34542" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "item has undeprecated statement with value" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Companion to Z32433 that accounts for rank." } ] } } afxtgsku4rteesrvqz5s1zd4xggnpom 0 82699 275537 272933 2026-05-16T17:28:02Z Jsamwrites 938 Removed Z34939 from the approved list of implementations 275537 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z34938" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6091", "Z17K2": "Z34938K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "entity" } ] } }, { "Z1K1": "Z17", "Z17K1": { "Z1K1": "Z7", "Z7K1": "Z883", "Z883K1": "Z6091", "Z883K2": "Z1" }, "Z17K2": "Z34938K2", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "reference context" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z60", "Z17K2": "Z34938K3", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "language" } ] } } ], "Z8K2": "Z11", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z34938" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "appropriate referential form for entity" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 2ydzebzaqbqimw3eeph066lga6os9gn 275538 275537 2026-05-16T17:28:06Z Jsamwrites 938 275538 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z34938" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6091", "Z17K2": "Z34938K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "entity" } ] } }, { "Z1K1": "Z17", "Z17K1": { "Z1K1": "Z7", "Z7K1": "Z883", "Z883K1": "Z6091", "Z883K2": "Z6091" }, "Z17K2": "Z34938K2", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "reference context" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z60", "Z17K2": "Z34938K3", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "language" } ] } } ], "Z8K2": "Z11", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z34938" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "appropriate referential form for entity" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } pog0ynmg8k6l7kz5f37b42yd0uce523 275539 275538 2026-05-16T17:28:12Z Jsamwrites 938 Added Z34939 to the approved list of implementations 275539 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z34938" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6091", "Z17K2": "Z34938K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "entity" } ] } }, { "Z1K1": "Z17", "Z17K1": { "Z1K1": "Z7", "Z7K1": "Z883", "Z883K1": "Z6091", "Z883K2": "Z6091" }, "Z17K2": "Z34938K2", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "reference context" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z60", "Z17K2": "Z34938K3", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "language" } ] } } ], "Z8K2": "Z11", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14", "Z34939" ], "Z8K5": "Z34938" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "appropriate referential form for entity" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } b5e7nbdykztasm2on7qaqg3s5k0roor 0 82700 275540 272934 2026-05-16T17:35:05Z Jsamwrites 938 275540 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z34939" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z34938", "Z14K2": { "Z1K1": "Z7", "Z7K1": "Z802", "Z802K1": { "Z1K1": "Z7", "Z7K1": "Z13522", "Z13522K1": { "Z1K1": "Z7", "Z7K1": "Z30737", "Z30737K1": { "Z1K1": "Z18", "Z18K1": "Z34938K2" } }, "Z13522K2": { "Z1K1": "Z13518", "Z13518K1": "0" } }, "Z802K2": { "Z1K1": "Z7", "Z7K1": "Z26107", "Z26107K1": { "Z1K1": "Z18", "Z18K1": "Z34938K3" }, "Z26107K2": { "Z1K1": "Z7", "Z7K1": { "Z1K1": "Z7", "Z7K1": "Z24766" } } }, "Z802K3": { "Z1K1": "Z7", "Z7K1": "Z802", "Z802K1": { "Z1K1": "Z7", "Z7K1": "Z19316", "Z19316K1": { "Z1K1": "Z7", "Z7K1": "Z35004", "Z35004K1": { "Z1K1": "Z18", "Z18K1": "Z34938K2" }, "Z35004K2": { "Z1K1": "Z6091", "Z6091K1": "Q28314507" } }, "Z19316K2": { "Z1K1": "Z6091", "Z6091K1": "Q5432619" } }, "Z802K2": { "Z1K1": "Z7", "Z7K1": "Z26107", "Z26107K1": { "Z1K1": "Z18", "Z18K1": "Z34938K3" }, "Z26107K2": { "Z1K1": "Z7", "Z7K1": { "Z1K1": "Z7", "Z7K1": "Z24766" } } }, "Z802K3": { "Z1K1": "Z11", "Z11K1": { "Z1K1": "Z18", "Z18K1": "Z34938K3" }, "Z11K2": "" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "appropriate referential form for entity, comp" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 82emxgdyycqpxszjhuyjsvevo9n1d6x 0 83274 275779 275436 2026-05-17T11:24:02Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275779 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1993" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "ahr" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Ahirani" }, { "Z1K1": "Z11", "Z11K1": "Z1993", "Z11K2": "अहिराणी" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Ahirani" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "ahirani" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } sgosigmziphh2c5715h7p09lcwjvlqg 0 83275 275780 275437 2026-05-17T11:24:41Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275780 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1994" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "ajg" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Aja" }, { "Z1K1": "Z11", "Z11K1": "Z1994", "Z11K2": "ajagbe" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Aja" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "aja-gbe" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "aja" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 15tjx7rvf95hb7s6oriuto1e3gn3zew 0 83277 275781 275439 2026-05-17T11:25:25Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275781 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1996" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "atv" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Northern Altay" }, { "Z1K1": "Z11", "Z11K1": "Z1996", "Z11K2": "тÿндÿк алтай" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Nördliches Altaisch" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "altaï du Nord" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "altaï septentrional" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } k01627b2p70hgtcd0095xof3rsptefz 0 83278 275782 275440 2026-05-17T11:25:52Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275782 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1997" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "bfa" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Bari" }, { "Z1K1": "Z11", "Z11K1": "Z1997", "Z11K2": "bari" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Bari" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "bari" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 66kcu6waec6dr5t6q39vacrulo5826a 0 83279 275783 275441 2026-05-17T11:26:26Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275783 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1998" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "bft" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Balti" }, { "Z1K1": "Z11", "Z11K1": "Z1998", "Z11K2": "بلتی" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Balti" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "balti" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } fxrgcgbl732v7t1mugxbz7lgpexxaog 0 83280 275784 275442 2026-05-17T11:27:44Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275784 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z1999" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "blc" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Nuxalk" }, { "Z1K1": "Z11", "Z11K1": "Z1999", "Z11K2": "ItNuxalkmc" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Nuxalk" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "nuxalk" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } d08ug2in58nm1ulcmyt4zq11of5wbkw 0 83281 275641 275443 2026-05-17T05:01:15Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275641 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2000" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "bwr" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Bura" }, { "Z1K1": "Z11", "Z11K1": "Z2000", "Z11K2": "bura" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Bura" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "babur" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } kccxhzjb3lrmbk32oyq8pz5spiiw8zh 0 83282 275640 275445 2026-05-17T04:54:40Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275640 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2001" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "bzj" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Belizean Creole" }, { "Z1K1": "Z11", "Z11K1": "Z2001", "Z11K2": "Bileez Kriol" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Belize-Kreolisch" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "créole bélizien" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } kezc8zvilguyxxsfsnbx6j52p4o1nol 0 83283 275642 275446 2026-05-17T05:01:46Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275642 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2002" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "elm" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Eleme" }, { "Z1K1": "Z11", "Z11K1": "Z2002", "Z11K2": "Eleme" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Eleme" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "eleme" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } il0m8vf14lwyvfv44pm04a9dyx21a0l 0 83284 275643 275447 2026-05-17T05:02:20Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275643 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2003" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "fax" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Fala" }, { "Z1K1": "Z11", "Z11K1": "Z2003", "Z11K2": "Fala" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Fala" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "fala" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } cba9d4arcypvck4q5it7rldy9zjj9zb 0 83285 275644 275448 2026-05-17T05:04:09Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275644 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2004" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "gah" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Alekano" }, { "Z1K1": "Z11", "Z11K1": "Z2004", "Z11K2": "Alekano" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Alekano" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "alekano" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } mjck4o65ombmx6ctixqbkmiplog21zn 0 83286 275645 275449 2026-05-17T05:04:39Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275645 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2005" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "gbm" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Garhwali" }, { "Z1K1": "Z11", "Z11K1": "Z2005", "Z11K2": "गढ़वळि" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Garhwali" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "garhwali" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 2v5eehrzc9i4j1lq1gwcdkmsaq4071q 0 83287 275646 275450 2026-05-17T05:05:32Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275646 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2006" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "gum" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Guambiano" }, { "Z1K1": "Z11", "Z11K1": "Z2006", "Z11K2": "Namtrik" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Guambiano" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "guambiano" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 4viv7g1vrlfw7lhbid72geofsle0mwc 0 83288 275647 275451 2026-05-17T05:16:34Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275647 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2007" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "hne" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Chhattisgarhi" }, { "Z1K1": "Z11", "Z11K1": "Z2007", "Z11K2": "छत्तीसगढ़ी" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Chhattisgarhi" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "chhattisgarhi" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } qsxobeswg0d6nb5vm8kaulk7wnp6bjl 0 83289 275648 275452 2026-05-17T05:17:11Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275648 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2008" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "ish" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Esan" }, { "Z1K1": "Z11", "Z11K1": "Z2008", "Z11K2": "awain" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Esan" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "esan" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ntbkn4ixohmyjn98lbjvjdx75925tau 0 83290 275649 275453 2026-05-17T05:17:30Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275649 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2009" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "jje" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Jeju" }, { "Z1K1": "Z11", "Z11K1": "Z2009", "Z11K2": "제주말" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Jeju" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "jeju" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 7dumyy8n9kt77ydvcvp3080eaq99o6m 0 83291 275650 275455 2026-05-17T05:17:51Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275650 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2010" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "kck" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Kalanga" }, { "Z1K1": "Z11", "Z11K1": "Z2010", "Z11K2": "tjikalanga" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Kalanga" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "kalanga" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 8tdae0n1b0orasbqz30c65gwue18tet 0 83292 275651 275457 2026-05-17T05:18:12Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275651 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2011" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mey" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Hassaniya" }, { "Z1K1": "Z11", "Z11K1": "Z2011", "Z11K2": "الحسانية" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Hassania" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "hassanya" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } rnryqqj18o81hlk08cxsc278n2srglm 0 83293 275652 275458 2026-05-17T05:18:34Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275652 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2012" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "miq" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Miskito" }, { "Z1K1": "Z11", "Z11K1": "Z2012", "Z11K2": "Mískitu" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Miskito" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "miskito" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ji62qftel4tun4wrjx7vwu5bhw7wabo 0 83294 275653 275459 2026-05-17T05:18:56Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275653 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2013" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mrv" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Mangareva" }, { "Z1K1": "Z11", "Z11K1": "Z2013", "Z11K2": "Magareva" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Mangarevanisch" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "mangarévien" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 11w37dfv8bsmp4b4m51bptngjkwmwle 0 83295 275664 275460 2026-05-17T05:47:44Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275664 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2014" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mvf" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Southern Mongolian" }, { "Z1K1": "Z11", "Z11K1": "Z2014", "Z11K2": "ᠮᠣᠩᠭᠣᠯ" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Südliches Mongolisch" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "mongol de Chine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "mongol de Mongolie-Intérieure" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } oph7jjkdut0epz5j2gxjmw0x4mbxl7s 0 83296 275661 275462 2026-05-17T05:31:40Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275661 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2015" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "oka" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Okanagan Salish" }, { "Z1K1": "Z11", "Z11K1": "Z2015", "Z11K2": "n̓səl̓xcin̓" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Okanagan" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "colville-okanagan" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ntqqes7o4udqzoqseohfk47lg38c2ag 0 83297 275658 275463 2026-05-17T05:29:43Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275658 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2016" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "osi" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Osing" }, { "Z1K1": "Z11", "Z11K1": "Z2016", "Z11K2": "Using" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Osing" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "osing" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } r7682pbsfob4711wdn33pf7fgswdxil 0 83298 275665 275464 2026-05-17T05:48:46Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275665 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2017" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "ovd" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Övdalian" }, { "Z1K1": "Z11", "Z11K1": "Z2017", "Z11K2": "övdalsk" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Älvdalisch" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "elfdalien" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "dalécarlien" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } jqvnu9ykolgq9q05v94oh5y6ct3byih 0 83299 275666 275465 2026-05-17T05:49:31Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275666 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2018" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "pbb" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Páez" }, { "Z1K1": "Z11", "Z11K1": "Z2018", "Z11K2": "Nasa Yuwe" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Paez" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "paez" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "nasa yuwe" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } iu48vzm3pig6jb997qsskg4s9y17yl4 0 83300 275667 275466 2026-05-17T05:51:20Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275667 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2019" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "phr" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Pothwari" }, { "Z1K1": "Z11", "Z11K1": "Z2019", "Z11K2": "پوٹھواری" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Pothwari" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "pahari-pothwari" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 7tz1ib2qm1si0bnlx93s5f78ryyh1ye 0 83301 275670 275467 2026-05-17T05:54:59Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275670 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2020" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "pis" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Solomon Islands Pijin" }, { "Z1K1": "Z11", "Z11K1": "Z2020", "Z11K2": "Solomon Aelan Pijin" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Pijin" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "pidgin des Îles Salomon" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "pijin" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } fzvre6eww8ncyt4coqzfqsykef76pyw 275671 275670 2026-05-17T05:55:39Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275671 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2020" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "pis" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Solomon Islands Pijin" }, { "Z1K1": "Z11", "Z11K1": "Z2020", "Z11K2": "Solomon Aelan Pijin" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Pijin" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "pidgin des îles Salomon" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "pijin" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } sgaarnwh4ywi6nv020hen1b3ojenwc2 0 83302 275668 275468 2026-05-17T05:52:20Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275668 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2021" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "pko" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Pökoot" }, { "Z1K1": "Z11", "Z11K1": "Z2021", "Z11K2": "Pökoot" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Pökoot" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "pökot" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } jgr4ejdcwja7hcds4au4oylf2i7mp4s 0 83303 275655 275469 2026-05-17T05:25:15Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275655 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2022" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "pov" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Guinea-Bissau Creole" }, { "Z1K1": "Z11", "Z11K1": "Z2022", "Z11K2": "guinensi" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Guineabissauisches Kreol" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "créole de Guinée-Bissau" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } n5gealjcreut7pqllgzacjyslevg190 0 83304 275654 275470 2026-05-17T05:19:50Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275654 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2023" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "qwh" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Huaylas Quechua" }, { "Z1K1": "Z11", "Z11K1": "Z2023", "Z11K2": "anqash qichwa" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Huaylas-Quechua" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "quechua ancash de Huaylas" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } h30i6aue4a6yummtiybmnkj9q9bf7hq 0 83305 275669 275471 2026-05-17T05:53:20Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275669 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2024" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "rag" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Logooli" }, { "Z1K1": "Z11", "Z11K1": "Z2024", "Z11K2": "Lologooli" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Logooli" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "logooli" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "ragoli" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } pvjk8ju63qkoaj8p377m6wpqfg2w9dj 0 83306 275662 275472 2026-05-17T05:38:24Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275662 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2025" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "rcf" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Réunion Creole French" }, { "Z1K1": "Z11", "Z11K1": "Z2025", "Z11K2": "Kreol Réyoné" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Réunion-Kreolisch" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "créole réunionnais" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } k6jl3axu4zk7yem7i7p31oz8qg85e7c 0 83307 275663 275474 2026-05-17T05:46:13Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275663 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2026" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "rej" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Rejang" }, { "Z1K1": "Z11", "Z11K1": "Z2026", "Z11K2": "Jang" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Rejang" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "rejang" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } tipwtkrwlj81esiyo9bv54ixxsyrssg 0 83308 275659 275475 2026-05-17T05:30:33Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275659 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2027" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "slr" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Salar" }, { "Z1K1": "Z11", "Z11K1": "Z2027", "Z11K2": "Salırça" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Salarisch" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "salar" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } bxudw3a73zpljiykvo7ypctupekxbhs 0 83309 275639 275476 2026-05-17T04:53:34Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275639 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2028" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "sxu" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Upper Saxon" }, { "Z1K1": "Z11", "Z11K1": "Z2028", "Z11K2": "Säggssch" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Obersächsisch" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "haut-saxon" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } gqlbqwt7eorv0txm086q7p87v836v7m 0 83310 275672 275477 2026-05-17T05:56:49Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275672 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2029" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "trp" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Kokborok" }, { "Z1K1": "Z11", "Z11K1": "Z2029", "Z11K2": "Kokborok" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Kokborok" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "borok" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "kokborok", "tripuri" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } mphml429lvsc3ov7lyq9j5mh2k70svz 0 83311 275673 275478 2026-05-17T05:57:20Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275673 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2030" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "twd" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Twents" }, { "Z1K1": "Z11", "Z11K1": "Z2030", "Z11K2": "Tweants" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Twents" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "twents" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } b2afnkl42htzppj9wngxp4y5z7xrlyj 0 83312 275674 275479 2026-05-17T05:58:22Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275674 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2031" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "yoi" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Yonaguni" }, { "Z1K1": "Z11", "Z11K1": "Z2031", "Z11K2": "与那国物言" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Yonaguni" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "yonaguni" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } k3s7gwqp7rc0xu02jjvsnex7kk6156m 0 83313 275660 275481 2026-05-17T05:31:06Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275660 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2032" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "yrk" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Nenets" }, { "Z1K1": "Z11", "Z11K1": "Z2032", "Z11K2": "ненэцяʼ вада" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Nenzisch" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "nénètse" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "Nenets languages" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } h7vwuj19z7xpnod7ytusy463fkf7ldz 0 83314 275677 275482 2026-05-17T06:05:33Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275677 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2033" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "ale-cyrl" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Aleut (Cyrillic script)" }, { "Z1K1": "Z11", "Z11K1": "Z2033", "Z11K2": "унаӈам тунуу" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Aleutisch (kyrillische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "aléoute en écriture cyrillique" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ngrs3l7to0tzbxuwgujmnna8uza3hj5 0 83315 275681 275485 2026-05-17T06:29:13Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275681 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2034" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "cdo-hani" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Mindong (Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z2034", "Z11K2": "閩東語（漢字）" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Dong (Han-Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "mindong en sinogrammes" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } iedbhqfu2g6mykuq64r5cosexb04blh 0 83316 275682 275486 2026-05-17T06:29:18Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275682 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2035" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "cdo-hans" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Mindong (Simplified Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z2035", "Z11K2": "闽东语（简化汉字）" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Dong (vereinfachte Han-Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "mindong en sinogrammes simplifiés" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 992cdpks493clzsjppzip30hghd7cz3 0 83317 275676 275487 2026-05-17T06:00:25Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275676 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2036" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "cnr-cyrl" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Montenegrin (Cyrillic script)" }, { "Z1K1": "Z11", "Z11K1": "Z2036", "Z11K2": "црногорски" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Montenegrinisch (kyrillische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "monténégrin en écriture cyrillique" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } e54ezddy7wv0xphskz7d4mviii2ve66 0 83318 275675 275489 2026-05-17T06:00:10Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275675 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2037" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "cnr-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Montenegrin (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z2037", "Z11K2": "crnogorski" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Montenegrinisch (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "monténégrin en écriture latine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 7xdpvgq0ibsp2c1i8f7m052sz0en1pp 0 83319 275678 275491 2026-05-17T06:14:18Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275678 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2038" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "hif-deva" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Fiji Hindi (Devanagari script)" }, { "Z1K1": "Z11", "Z11K1": "Z2038", "Z11K2": "फ़ीजी हिन्दी" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Fidschi-Hindi (Devanagari-Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "hindi des Fidji en écriture devanagari" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 7lbll376a3qpcmcuam27792f2dw27zs 0 83320 275679 275492 2026-05-17T06:16:10Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275679 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2039" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "jdt" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Judeo-Tat" }, { "Z1K1": "Z11", "Z11K1": "Z2039", "Z11K2": "жугьури" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Judäo-Tatisch" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "juhuri" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 3zx8os2wexby9mbo6do3s0hr5zdscwo 0 83321 275680 275493 2026-05-17T06:16:26Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275680 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2040" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "jdt-cyrl" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Judeo-Tat (Cyrillic script)" }, { "Z1K1": "Z11", "Z11K1": "Z2040", "Z11K2": "жугьури" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Judäo-Tatisch (kyrillische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "juhuri en écriture cyrillique" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 70fszchx9vbgrd4g82ay5tthlnukwk0 0 83322 275683 275494 2026-05-17T06:30:04Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275683 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2041" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "kge-arab" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Komering (Arabic script)" }, { "Z1K1": "Z11", "Z11K1": "Z2041", "Z11K2": "كوموريڠ" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Komering (arabische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "komering en écriture arabe" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 8oqsdk01euup1ttv6wr3oe91hy5xcd9 0 83323 275495 274499 2026-05-16T11:59:19Z Ameisenigel 44 de 275495 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2042" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "lad-hebr" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Ladino (Hebrew script)" }, { "Z1K1": "Z11", "Z11K1": "Z2042", "Z11K2": "לאדינו" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Ladino (hebräische Schrift)" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 0id8ynu774ev5azhnpoenkigv9irhh1 275685 275495 2026-05-17T06:34:07Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275685 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2042" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "lad-hebr" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Ladino (Hebrew script)" }, { "Z1K1": "Z11", "Z11K1": "Z2042", "Z11K2": "לאדינו" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Ladino (hebräische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "judéo-espagnol en écriture hébraïque" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ofvmlxnu2rygy9ic5fcyaul0ltbwb92 0 83324 275496 274500 2026-05-16T12:00:11Z Ameisenigel 44 de 275496 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2043" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mak-bugi" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Makasar (Lontara script)" }, { "Z1K1": "Z11", "Z11K1": "Z2043", "Z11K2": "ᨆᨀᨔᨑ" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Makassar (Lontara-Schrift)" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } arpgalugi1awd1jxk422jpkj8vz4mqq 275689 275496 2026-05-17T06:39:57Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275689 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2043" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mak-bugi" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Makasar (Lontara script)" }, { "Z1K1": "Z11", "Z11K1": "Z2043", "Z11K2": "ᨆᨀᨔᨑ" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Makassar (Lontara-Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "makassar en écriture lontara" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } qwa1nydxw1184dlinlfqfxgqd9aay1z 0 83325 275498 274501 2026-05-16T12:01:51Z Ameisenigel 44 de 275498 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2044" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mww" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Hmong Daw" }, { "Z1K1": "Z11", "Z11K1": "Z2044", "Z11K2": "Hmoob Dawb" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Hmong Daw" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } cfwpt6nf1nkqr1c1zfoj1ncm6ywv68v 275687 275498 2026-05-17T06:37:06Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275687 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2044" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mww" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Hmong Daw" }, { "Z1K1": "Z11", "Z11K1": "Z2044", "Z11K2": "Hmoob Dawb" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Hmong Daw" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "hmong daw" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } q5u0xkce5z94ehi1drttfnsrdf6y1bg 0 83326 275499 274502 2026-05-16T12:02:22Z Ameisenigel 44 de 275499 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2045" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mww-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Hmong Daw (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z2045", "Z11K2": "Hmoob Dawb" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Hmong Daw (lateinische Schrift)" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 8qssscmw9d5czej96htwh6ersepj6k2 275686 275499 2026-05-17T06:37:00Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275686 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2045" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "mww-latn" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Hmong Daw (Latin script)" }, { "Z1K1": "Z11", "Z11K1": "Z2045", "Z11K2": "Hmoob Dawb" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Hmong Daw (lateinische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "hmong daw en écriture latine" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } o8erpj03wkj7x0g3evonq9sx9ntk45o 0 83327 275500 274503 2026-05-16T12:03:33Z Ameisenigel 44 de 275500 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2046" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nod-thai" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Northern Thai (Thai script)" }, { "Z1K1": "Z11", "Z11K1": "Z2046", "Z11K2": "คำเมือง" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Lanna (thailändische Schrift)" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 22hdof8wzz226y7y4ya0ckfosvnzlyu 275693 275500 2026-05-17T06:47:10Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275693 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2046" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nod-thai" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Northern Thai (Thai script)" }, { "Z1K1": "Z11", "Z11K1": "Z2046", "Z11K2": "คำเมือง" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Lanna (thailändische Schrift)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "thaï du Nord en écriture thaïe" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } djfr0z6jnidg79hol8nsjooay2n07a9 0 83328 275504 274504 2026-05-16T12:09:26Z Ameisenigel 44 de 275504 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2047" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nan-hans" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Minnan (Simplified Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z2047", "Z11K2": "闽南语（简化汉字）" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Nan (vereinfachtes Han)" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } albkztq7bylzgasx1r6p16e1dw2vm5o 275690 275504 2026-05-17T06:43:38Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275690 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2047" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nan-hans" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Minnan (Simplified Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z2047", "Z11K2": "闽南语（简化汉字）" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Nan (vereinfachtes Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "minnan en sinogrammes simplifiés" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } pcqyk9ekouyrh3glyyfmudrkl68arty 275692 275690 2026-05-17T06:45:38Z Jérémy-Günther-Heinz Jähnick 6055 Traduction en français (fr) 275692 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z2047" }, "Z2K2": { "Z1K1": "Z60", "Z60K1": "nan-hans" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "Minnan (Simplified Han script)" }, { "Z1K1": "Z11", "Z11K1": "Z2047", "Z11K2": "闽南语（简化汉字）" }, { "Z1K1": "Z11", "Z11K1": "Z1430", "Z11K2": "Min Nan (vereinfachtes Han)" }, { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "minnan en sinogrammes simplifiés" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "min méridional en sinogrammes simplifiés", "sud-foukiénois en sinogrammes simplifiés" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } bpl6eh8lkmroqj94269kujbmr8538vg 2 83367 275572 275313 2026-05-16T21:16:48Z YoshiRulz 10156 Add related types param 275572 wikitext text/x-wiki <onlyinclude><includeonly>== Documentation == {{#ifeq:{{NAMESPACENUMBER}}|1|[[Category:Types]]}} {| class="wikitable" | <div style="float: inline-end; text-align: end;"> layout: {{mini navbar|User:YoshiRulz/Type documentation}} <br>data: {{mini navbar|{{{1|{{PAGENAME}}}}}|point-at-data=y}} </div> '''{{#wikifunctionlabeldesc:{{{1|{{PAGENAME}}}}}}}''' |- | {| <!-- -->{{#if:{{item linked to mainspace object|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}}|<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Wikidata Item (sitelink) {{!}} {{item linked to mainspace object|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}} }}<!-- -->{{#switch:{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}} |Z80|Z13518|Z16683|Z19677|Z20838|Z33198=<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Numeric type hierarchy {{!}} [[Talk:Z80|GF(256)]] &sub; [[Talk:Z13518|&Nopf;]] &sub; [[Talk:Z16683|&Zopf;]] &sub; [[Talk:Z19677|&Qopf;]] &sub; &Ropf; ([[Talk:Z20838|f64]]) &sub; &Copf; ([[Talk:Z33198|f64&times;f64]]) }}<!-- -->{{#if:{{{related types|}}}|<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Related types {{!}} {{{related types}}} }}<!-- -->{{#switch:{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}} |Z6062|Z6063|Z25340|Z25501|Z25502|Z26582|Z26934|Z26935|Z27951|Z27970|Z27971|Z28215|Z28515|Z28516|Z28517|Z28518|Z28519|Z28520|Z32789|Z32792|Z33568|Z33827 |Z21|Z40|Z60|Z61|Z6020|Z6030|Z6040|Z16098|Z16659|Z16927|Z17402|Z17813|Z20825|Z22112=<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Enumeration members/options {{!}} {{enum member list|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}} }}<!-- --> |} |} <!-- -->{{#ifexist:Help:Type_deconstruction_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Type_deconstruction_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Fetching_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Fetching_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Type_conversion_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Type_conversion_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Rounding_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Rounding_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- --> {{#ifexist:Help:{{{1|{{PAGENAME}}}}} |{{clear}}'''Explanations''' [<nowiki/>[[Special:MyLanguage/Help:{{{1|{{PAGENAME}}}}}|{{int:edit}}]]<nowiki/>] {{TNT|Help:{{{1|{{PAGENAME}}}}}|uselang={{USERLANGUAGE}}}} |<div dir="{{#dir}}">[<nowiki/><span class="plainlinks">[{{fullurl:Help:{{{1|{{PAGENAME}}}}}|action=edit&preload={{urlencode:User:YoshiRulz/Type documentation/help page template}}}} Create]</span> translatable long-form documentation to be included here<nowiki/>]</div> }} {{#ifeq:{{NAMESPACENUMBER}}|1|{{DEFAULTSORT:Talk:Z{{padleft:{{#invoke:String|sub|{{{1|{{PAGENAME}}}}}|2}}|5}}}}}}</includeonly></onlyinclude> {{documentation}} {{ {{FULLPAGENAME}}|Z16683|Integer |related types= * {{Z+|Z16659}} }} {{ {{FULLPAGENAME}}|Z6060|Time of day |related types= * {{Z+|Z6061}} * {{Z+|Z20420}} }} {{ {{FULLPAGENAME}}|Z16659|Sign |related types= * {{Z+|Z16683}} * {{Z+|Z19677}} }} 3at6x4dd0hfokplryvnbn4prchp0i8z 275623 275572 2026-05-17T02:54:07Z YoshiRulz 10156 Use subcat for enum types 275623 wikitext text/x-wiki <onlyinclude><includeonly>== Documentation == {| class="wikitable" | <div style="float: inline-end; text-align: end;"> layout: {{mini navbar|User:YoshiRulz/Type documentation}} <br>data: {{mini navbar|{{{1|{{PAGENAME}}}}}|point-at-data=y}} </div> '''{{#wikifunctionlabeldesc:{{{1|{{PAGENAME}}}}}}}''' |- | {| <!-- -->{{#if:{{item linked to mainspace object|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}}|<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Wikidata Item (sitelink) {{!}} {{item linked to mainspace object|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}} }}<!-- -->{{#switch:{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}} |Z80|Z13518|Z16683|Z19677|Z20838|Z33198=<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Numeric type hierarchy {{!}} [[Talk:Z80|GF(256)]] &sub; [[Talk:Z13518|&Nopf;]] &sub; [[Talk:Z16683|&Zopf;]] &sub; [[Talk:Z19677|&Qopf;]] &sub; &Ropf; ([[Talk:Z20838|f64]]) &sub; &Copf; ([[Talk:Z33198|f64&times;f64]]) }}<!-- -->{{#if:{{{related types|}}}|<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Related types {{!}} {{{related types}}} }}<!-- -->{{#switch:{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}} |Z6062|Z6063|Z25340|Z25501|Z25502|Z26582|Z26934|Z26935|Z27951|Z27970|Z27971|Z28215|Z28515|Z28516|Z28517|Z28518|Z28519|Z28520|Z32789|Z32792|Z33568|Z33827 |Z21|Z40|Z60|Z61|Z6020|Z6030|Z6040|Z16098|Z16659|Z16927|Z17402|Z17813|Z20825|Z22112=<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Enumeration members/options {{!}} {{enum member list|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}} {{#ifeq:{{NAMESPACENUMBER}}|1|[[Category:Enumeration_types]]}} |#default=[[Category:Types]] }}<!-- --> |} |} <!-- -->{{#ifexist:Help:Type_deconstruction_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Type_deconstruction_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Fetching_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Fetching_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Type_conversion_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Type_conversion_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Rounding_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Rounding_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- --> {{#ifexist:Help:{{{1|{{PAGENAME}}}}} |{{clear}}'''Explanations''' [<nowiki/>[[Special:MyLanguage/Help:{{{1|{{PAGENAME}}}}}|{{int:edit}}]]<nowiki/>] {{TNT|Help:{{{1|{{PAGENAME}}}}}|uselang={{USERLANGUAGE}}}} |<div dir="{{#dir}}">[<nowiki/><span class="plainlinks">[{{fullurl:Help:{{{1|{{PAGENAME}}}}}|action=edit&preload={{urlencode:User:YoshiRulz/Type documentation/help page template}}}} Create]</span> translatable long-form documentation to be included here<nowiki/>]</div> }} {{#ifeq:{{NAMESPACENUMBER}}|1|{{DEFAULTSORT:Talk:Z{{padleft:{{#invoke:String|sub|{{{1|{{PAGENAME}}}}}|2}}|5}}}}}}</includeonly></onlyinclude> {{documentation}} {{ {{FULLPAGENAME}}|Z16683|Integer |related types= * {{Z+|Z16659}} }} {{ {{FULLPAGENAME}}|Z6060|Time of day |related types= * {{Z+|Z6061}} * {{Z+|Z20420}} }} {{ {{FULLPAGENAME}}|Z16659|Sign |related types= * {{Z+|Z16683}} * {{Z+|Z19677}} }} pn2bnrtm58kgtxpf7ikzw5ktk7xsq95 275624 275623 2026-05-17T02:54:52Z YoshiRulz 10156 Forgot the namespace check 275624 wikitext text/x-wiki <onlyinclude><includeonly>== Documentation == {| class="wikitable" | <div style="float: inline-end; text-align: end;"> layout: {{mini navbar|User:YoshiRulz/Type documentation}} <br>data: {{mini navbar|{{{1|{{PAGENAME}}}}}|point-at-data=y}} </div> '''{{#wikifunctionlabeldesc:{{{1|{{PAGENAME}}}}}}}''' |- | {| <!-- -->{{#if:{{item linked to mainspace object|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}}|<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Wikidata Item (sitelink) {{!}} {{item linked to mainspace object|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}} }}<!-- -->{{#switch:{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}} |Z80|Z13518|Z16683|Z19677|Z20838|Z33198=<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Numeric type hierarchy {{!}} [[Talk:Z80|GF(256)]] &sub; [[Talk:Z13518|&Nopf;]] &sub; [[Talk:Z16683|&Zopf;]] &sub; [[Talk:Z19677|&Qopf;]] &sub; &Ropf; ([[Talk:Z20838|f64]]) &sub; &Copf; ([[Talk:Z33198|f64&times;f64]]) }}<!-- -->{{#if:{{{related types|}}}|<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Related types {{!}} {{{related types}}} }}<!-- -->{{#switch:{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}} |Z6062|Z6063|Z25340|Z25501|Z25502|Z26582|Z26934|Z26935|Z27951|Z27970|Z27971|Z28215|Z28515|Z28516|Z28517|Z28518|Z28519|Z28520|Z32789|Z32792|Z33568|Z33827 |Z21|Z40|Z60|Z61|Z6020|Z6030|Z6040|Z16098|Z16659|Z16927|Z17402|Z17813|Z20825|Z22112=<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Enumeration members/options {{!}} {{enum member list|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}} {{#ifeq:{{NAMESPACENUMBER}}|1|[[Category:Enumeration_types]]}} |#default={{#ifeq:{{NAMESPACENUMBER}}|1|[[Category:Types]]}} }}<!-- --> |} |} <!-- -->{{#ifexist:Help:Type_deconstruction_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Type_deconstruction_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Fetching_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Fetching_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Type_conversion_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Type_conversion_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Rounding_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Rounding_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- --> {{#ifexist:Help:{{{1|{{PAGENAME}}}}} |{{clear}}'''Explanations''' [<nowiki/>[[Special:MyLanguage/Help:{{{1|{{PAGENAME}}}}}|{{int:edit}}]]<nowiki/>] {{TNT|Help:{{{1|{{PAGENAME}}}}}|uselang={{USERLANGUAGE}}}} |<div dir="{{#dir}}">[<nowiki/><span class="plainlinks">[{{fullurl:Help:{{{1|{{PAGENAME}}}}}|action=edit&preload={{urlencode:User:YoshiRulz/Type documentation/help page template}}}} Create]</span> translatable long-form documentation to be included here<nowiki/>]</div> }} {{#ifeq:{{NAMESPACENUMBER}}|1|{{DEFAULTSORT:Talk:Z{{padleft:{{#invoke:String|sub|{{{1|{{PAGENAME}}}}}|2}}|5}}}}}}</includeonly></onlyinclude> {{documentation}} {{ {{FULLPAGENAME}}|Z16683|Integer |related types= * {{Z+|Z16659}} }} {{ {{FULLPAGENAME}}|Z6060|Time of day |related types= * {{Z+|Z6061}} * {{Z+|Z20420}} }} {{ {{FULLPAGENAME}}|Z16659|Sign |related types= * {{Z+|Z16683}} * {{Z+|Z19677}} }} 6w07m6hr0c7lrv2y68ou5cm8zkrc2f3 275627 275624 2026-05-17T03:02:26Z YoshiRulz 10156 Use subcat for parameterised types 275627 wikitext text/x-wiki <onlyinclude><includeonly>== Documentation == {| class="wikitable" | <div style="float: inline-end; text-align: end;"> layout: {{mini navbar|User:YoshiRulz/Type documentation}} <br>data: {{mini navbar|{{{1|{{PAGENAME}}}}}|point-at-data=y}} </div> '''{{#wikifunctionlabeldesc:{{{1|{{PAGENAME}}}}}}}''' |- | {| <!-- -->{{#if:{{item linked to mainspace object|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}}|<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Wikidata Item (sitelink) {{!}} {{item linked to mainspace object|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}} }}<!-- -->{{#switch:{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}} |Z80|Z13518|Z16683|Z19677|Z20838|Z33198=<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Numeric type hierarchy {{!}} [[Talk:Z80|GF(256)]] &sub; [[Talk:Z13518|&Nopf;]] &sub; [[Talk:Z16683|&Zopf;]] &sub; [[Talk:Z19677|&Qopf;]] &sub; &Ropf; ([[Talk:Z20838|f64]]) &sub; &Copf; ([[Talk:Z33198|f64&times;f64]]) }}<!-- -->{{#if:{{{related types|}}}|<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Related types {{!}} {{{related types}}} }}<!-- -->{{#switch:{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}} |Z6062|Z6063|Z25340|Z25501|Z25502|Z26582|Z26934|Z26935|Z27951|Z27970|Z27971|Z28215|Z28515|Z28516|Z28517|Z28518|Z28519|Z28520|Z32789|Z32792|Z33568|Z33827 |Z21|Z40|Z60|Z61|Z6020|Z6030|Z6040|Z16098|Z16659|Z16927|Z17402|Z17813|Z20825|Z22112=<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Enumeration members/options {{!}} {{enum member list|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}} {{#ifeq:{{NAMESPACENUMBER}}|1|[[Category:Enumeration_types]]}} |#default={{#ifeq:{{NAMESPACENUMBER}}|1|{{#switch: |Z881|Z882|Z883|Z6884=[[Category:Parameterised_types]] |#default=[[Category:Types]] }}}} }}<!-- --> |} |} <!-- -->{{#ifexist:Help:Type_deconstruction_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Type_deconstruction_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Fetching_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Fetching_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Type_conversion_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Type_conversion_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Rounding_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Rounding_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- --> {{#ifexist:Help:{{{1|{{PAGENAME}}}}} |{{clear}}'''Explanations''' [<nowiki/>[[Special:MyLanguage/Help:{{{1|{{PAGENAME}}}}}|{{int:edit}}]]<nowiki/>] {{TNT|Help:{{{1|{{PAGENAME}}}}}|uselang={{USERLANGUAGE}}}} |<div dir="{{#dir}}">[<nowiki/><span class="plainlinks">[{{fullurl:Help:{{{1|{{PAGENAME}}}}}|action=edit&preload={{urlencode:User:YoshiRulz/Type documentation/help page template}}}} Create]</span> translatable long-form documentation to be included here<nowiki/>]</div> }} {{#ifeq:{{NAMESPACENUMBER}}|1|{{DEFAULTSORT:Talk:Z{{padleft:{{#invoke:String|sub|{{{1|{{PAGENAME}}}}}|2}}|5}}}}}}</includeonly></onlyinclude> {{documentation}} {{ {{FULLPAGENAME}}|Z16683|Integer |related types= * {{Z+|Z16659}} }} {{ {{FULLPAGENAME}}|Z6060|Time of day |related types= * {{Z+|Z6061}} * {{Z+|Z20420}} }} {{ {{FULLPAGENAME}}|Z16659|Sign |related types= * {{Z+|Z16683}} * {{Z+|Z19677}} }} jbypho658kf0rs2vokrz1pgtqnmzzm3 275629 275627 2026-05-17T03:04:55Z YoshiRulz 10156 Forgot to fill in ZID, but also why have a duplicate switch block, merge into the outer one 275629 wikitext text/x-wiki <onlyinclude><includeonly>== Documentation == {| class="wikitable" | <div style="float: inline-end; text-align: end;"> layout: {{mini navbar|User:YoshiRulz/Type documentation}} <br>data: {{mini navbar|{{{1|{{PAGENAME}}}}}|point-at-data=y}} </div> '''{{#wikifunctionlabeldesc:{{{1|{{PAGENAME}}}}}}}''' |- | {| <!-- -->{{#if:{{item linked to mainspace object|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}}|<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Wikidata Item (sitelink) {{!}} {{item linked to mainspace object|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}} }}<!-- -->{{#switch:{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}} |Z80|Z13518|Z16683|Z19677|Z20838|Z33198=<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Numeric type hierarchy {{!}} [[Talk:Z80|GF(256)]] &sub; [[Talk:Z13518|&Nopf;]] &sub; [[Talk:Z16683|&Zopf;]] &sub; [[Talk:Z19677|&Qopf;]] &sub; &Ropf; ([[Talk:Z20838|f64]]) &sub; &Copf; ([[Talk:Z33198|f64&times;f64]]) }}<!-- -->{{#if:{{{related types|}}}|<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Related types {{!}} {{{related types}}} }}<!-- -->{{#switch:{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}} |Z6062|Z6063|Z25340|Z25501|Z25502|Z26582|Z26934|Z26935|Z27951|Z27970|Z27971|Z28215|Z28515|Z28516|Z28517|Z28518|Z28519|Z28520|Z32789|Z32792|Z33568|Z33827 |Z21|Z40|Z60|Z61|Z6020|Z6030|Z6040|Z16098|Z16659|Z16927|Z17402|Z17813|Z20825|Z22112=<nowiki/> {{!}}- ! style="text-align: start;" {{!}} Enumeration members/options {{!}} {{enum member list|{{SUBJECTPAGENAME:{{{1|{{PAGENAME}}}}}}}}} {{#ifeq:{{NAMESPACENUMBER}}|1|[[Category:Enumeration_types]]}} |Z881|Z882|Z883|Z6884={{#ifeq:{{NAMESPACENUMBER}}|1|[[Category:Parameterised_types]]}} |#default={{#ifeq:{{NAMESPACENUMBER}}|1|[[Category:Types]]}} }}<!-- --> |} |} <!-- -->{{#ifexist:Help:Type_deconstruction_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Type_deconstruction_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Fetching_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Fetching_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Type_conversion_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Type_conversion_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- -->{{#ifexist:Help:Rounding_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}} |{{Help:Rounding_function_table/{{{2|{{#function:Z34802|en|{{{1|{{PAGENAME}}}}}}}}}}}}}}<!-- --> {{#ifexist:Help:{{{1|{{PAGENAME}}}}} |{{clear}}'''Explanations''' [<nowiki/>[[Special:MyLanguage/Help:{{{1|{{PAGENAME}}}}}|{{int:edit}}]]<nowiki/>] {{TNT|Help:{{{1|{{PAGENAME}}}}}|uselang={{USERLANGUAGE}}}} |<div dir="{{#dir}}">[<nowiki/><span class="plainlinks">[{{fullurl:Help:{{{1|{{PAGENAME}}}}}|action=edit&preload={{urlencode:User:YoshiRulz/Type documentation/help page template}}}} Create]</span> translatable long-form documentation to be included here<nowiki/>]</div> }} {{#ifeq:{{NAMESPACENUMBER}}|1|{{DEFAULTSORT:Talk:Z{{padleft:{{#invoke:String|sub|{{{1|{{PAGENAME}}}}}|2}}|5}}}}}}</includeonly></onlyinclude> {{documentation}} {{ {{FULLPAGENAME}}|Z16683|Integer |related types= * {{Z+|Z16659}} }} {{ {{FULLPAGENAME}}|Z6060|Time of day |related types= * {{Z+|Z6061}} * {{Z+|Z20420}} }} {{ {{FULLPAGENAME}}|Z16659|Sign |related types= * {{Z+|Z16683}} * {{Z+|Z19677}} }} 9h8x7d6dkndc2wzna0rwnm6mg71pqh8 2 83368 275573 275253 2026-05-16T21:47:08Z YoshiRulz 10156 Document related types param 275573 wikitext text/x-wiki Used on a Type's talk page to provide links to related Functions in a standard<!-- and translatable--> layout, and optionally including long-form documentation. Usage example: <syntaxhighlight lang="wikitext"> {{type documentation|Z16683|Integer |related types= * {{Z+|Z16659}} }} </syntaxhighlight> This and a couple other examples are shown rendered at the bottom of [[Template:Type_documentation#Documentation|the template page]]. Compare [[Special:EditPage/User:YoshiRulz/Type_documentation|their Wikitext source]] (though it's mostly empty because everything is automatic). == Parameters == All parameters are optional. Unless specified, all parameters are Wikitext, and you can pass a bullet-point list when this Type relates to multiple Functions in the same way. The template will display data in the below order regardless of the order arguments are given in. === <code>related types</code> === <syntaxhighlight lang="wikitext"> {{function documentation |related types={{Z+|Z13518}} }} </syntaxhighlight> The value for this parameter should be a link to a persistent {{Z|4}}. A Type which is used for similar purposes as this one, or which is the counterpart to this one. <br>There's no need to list the Types which are components (Keys) of this one, since you can make a [[Help:Type deconstruction table]] to be included below the main table. == Tables of related functions == Below the main table, the relevant subpage of [[Help:Type deconstruction table]] will be shown, if it exists, followed by the relevant subpages of [[Help:Fetching function table]], [[Help:Type conversion table]], and [[Help:Rounding function table]]. 2x11z90peqj1782hej8x6p5q18r5vnl 275634 275573 2026-05-17T03:07:42Z YoshiRulz 10156 Document categorisation 275634 wikitext text/x-wiki Used on a Type's talk page to provide links to related Functions in a standard<!-- and translatable--> layout, and optionally including long-form documentation. <br>It will also put the containing Talk page into [[:Category:Types]] or one of its subcategories. Usage example: <syntaxhighlight lang="wikitext"> {{type documentation|Z16683|Integer |related types= * {{Z+|Z16659}} }} </syntaxhighlight> This and a couple other examples are shown rendered at the bottom of [[Template:Type_documentation#Documentation|the template page]]. Compare [[Special:EditPage/User:YoshiRulz/Type_documentation|their Wikitext source]] (though it's mostly empty because everything is automatic). == Parameters == All parameters are optional. Unless specified, all parameters are Wikitext, and you can pass a bullet-point list when this Type relates to multiple Functions in the same way. The template will display data in the below order regardless of the order arguments are given in. === <code>related types</code> === <syntaxhighlight lang="wikitext"> {{function documentation |related types={{Z+|Z13518}} }} </syntaxhighlight> The value for this parameter should be a link to a persistent {{Z|4}}. A Type which is used for similar purposes as this one, or which is the counterpart to this one. <br>There's no need to list the Types which are components (Keys) of this one, since you can make a [[Help:Type deconstruction table]] to be included below the main table. == Tables of related functions == Below the main table, the relevant subpage of [[Help:Type deconstruction table]] will be shown, if it exists, followed by the relevant subpages of [[Help:Fetching function table]], [[Help:Type conversion table]], and [[Help:Rounding function table]]. cr30t053xcwss2c8i6anvfcnxeb7ugl 4 83526 275565 275399 2026-05-16T20:48:35Z Ameisenigel 44 Created page with "Diese Woche haben wir in Wikifunctions die Unterstützung für mehrere Dutzend natürliche Sprachen hinzugefügt, die bereits von [$1 TranslateWiki.net] unterstützt (und für die Übersetzung von Wikimedia-Software verwendet) wurden, aber noch nicht von Wikifunctions unterstützt wurden. Außerdem haben wir Abstrakte Seiten so aktualisiert, dass neben dem Seitentitel nun eine kopierbare QID angezeigt wird. Dadurch lässt sich die entsprechende Wikidata-QID schneller kop..." 275565 wikitext text/x-wiki <languages/> {{Wikifunctions updates | prevlabel = Vorheriges Update | prev = 2026-05-08 | nextlabel = Nächstes Update | next = }} <span id="A_higher_meaning"></span> === Eine höhere Bedeutung === Eine der zentralen Fragen zur Abstrakten Wikipedia lautet: Wie viele [[Special:MyLanguage/Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Funktionen zur Konstruktion von Textfragmenten]] benötigen wir? Denn wenn diese Zahl groß ist, bedeutet das nicht, dass wir viele Funktionen benötigen, die diese Fragmente in vielen Sprachen implementieren? Und das würde den Aufwand für jede Sprache erhöhen und wäre es nicht irgendwann einfacher, die Texte einfach zu übersetzen und die Übersetzungen zu validieren, anstatt all diese Funktionen zu erstellen? Wir wissen nicht, wie groß diese Zahl sein wird. Aber heute möchte ich einen Grund dafür erörtern, warum ich glaube, dass sie begrenzt bleiben wird: Nicht jedes Fragment muss durch sprachspezifische Funktionen implementiert werden. Wie wäre das der Fall? Müssen wir nicht jedes Fragment mit einer sprachspezifischen Funktion in jeder Sprache implementieren, die wir unterstützen wollen? Prinzipiell schon, aber manchmal können diese Implementierungen Kompositionen anderer abstrakter Funktionen sein! Hier ein konkretes Beispiel: {{Z|Z28436}} erstellt einen Satz aus einer Aussage mit einer Eigenschaft Zeitpunkt. Zum Beispiel ein Satz wie “Die Einwohnerzahl von North Epping lag 2021 bei 4657.” oder "Die Einwohnerzahl von Donji Humac lag 2011 bei 157." Die Funktion Z28436 wird mithilfe eines Konfigurationsobjekts implementiert, derzeit mit Implementierungen in Englisch und Bengalisch. Betrachten wir nun die Funktion {{Z|Z28445}}. Anstatt ein Objekt und eine Aussage entgegenzunehmen, erwartet sie ein Objekt und eine Eigenschaft und gibt den Wert der Aussage für diese Eigenschaft mit dem aktuellsten Zeitpunkt zurück. Wenn wir diese Funktion also für Donji Humac und die Einwohnerzahl ausführen, erhalten wir das Ergebnis: "Die Einwohnerzahl von Donji Humac lag 2021 bei 173." Dies ist die aktuellste Einwohnerzahlangabe, die wir in Wikidata für Donji Humac haben. Betrachten wir nun die Implementierung von Z28445, so sehen wir keine Konfiguration. Stattdessen sehen wir eine Funktion, die aus der obigen Funktion, Z28436, und {{Z|Z28446}} besteht. Nichts an dieser Implementierung ist sprachspezifisch. Die Sprache wird vielmehr an die zugrundeliegende Funktion weitergegeben. Wir sehen hier also eine abstrakte Funktion, die eine vollständig abstrakte Implementierung besitzt. Dies ist ein allgemeines Muster, das wiederverwendet werden kann: Wenn wir über eine solide Grundlage verfügen, ist es hoffentlich oft möglich, "höhere" abstrakte Funktionen auf fundamentaleren Funktionen zu gründen, die dennoch abstrakt sind. Betrachten wir beispielsweise die folgenden Sätze * “Die Hunnen griffen das Römische Reich im 5. Jahrhundert an.” * “John Wilkes Booth ermordete Abraham Lincoln am 14. April 1865.” * “John Lennon traf Yoko Ono am 7. November 1966.” * “Leonard Cohen schrieb ‘Hallelujah’ im Jahr 1984.” * “Microsoft brachte Windows 3.1 am 24. August 1995 auf den Markt.” * “Hubble entdeckte Osiris am 28. November 2001.” Sie beschreiben zwar sehr unterschiedliche Ereignisse, aber im Grunde haben sie alle im Englischen eine sehr ähnliche Struktur: Sie bestehen aus Prädikat, Subjekt, direktem Objekt und einem mehr oder weniger genauen Zeitpunkt. Alle diese Sätze könnten im Englischen durch eine einzige Funktion gebildet werden. Vielleicht stellt sich heraus, dass sich all diese Sätze in mehreren Sprachen durch eine einzige abstrakte Funktion erzeugen lassen. Nennen wir diese Funktion eine Basisfunktion. Und nun könnten wir mehrere übergeordnete Funktionen haben, die durch solche Basisfunktionen implementiert werden, und wir müssen nur noch das richtige Prädikat auswählen. Das funktioniert nicht immer. Der Vorteil ist jedoch, dass wir, wenn wir diese übergeordneten Funktionen haben, versuchen können, die Ausnahme auf dieser Ebene abzufangen, sie an die entsprechende Sprache weiterzuleiten und andernfalls das richtige Prädikat auszuwählen und einfach die Basisfunktion zu verwenden. Zum Beispiel würden wir auf Deutsch normalerweise sagen * “Goldie Hawn brachte Kate Hudson am 19. April 1979 zur Welt.” Das ist eine etwas andere grammatikalische Struktur als die obige. Die obige grammatikalische Struktur würde zu “Goldie Hawn gebar Kate Hudson am 19. April 1979.” führen – was im Deutschen ein ungewöhnlicher Satz wäre, aber in einigen anderen Sprachen, z. B. im Kroatischen, problemlos funktioniert. Eine Funktion, die diesen Satz erzeugt, könnte für diesen Anwendungsfall eine andere Basisfunktion wählen oder sogar eine einmalige Implementierung für Deutsch und andere Sprachen haben, in denen die oben eingeführte Basisfunktion nicht funktionieren würde, und für die anderen Sprachen die Basisfunktion verwenden. Ein solches Muster könnte die Anzahl der für das Funktionieren der Abstrakten Wikipedia erforderlichen sprachspezifischen Implementierungen erheblich reduzieren und unser Ziel somit realistischer machen. <span id="Recent_Changes_in_the_software"></span> === Letzte Änderungen an der Software === Diese Woche haben wir in Wikifunctions die Unterstützung für mehrere Dutzend natürliche Sprachen hinzugefügt, die bereits von [https://translatewiki.net/ TranslateWiki.net] unterstützt (und für die Übersetzung von Wikimedia-Software verwendet) wurden, aber noch nicht von Wikifunctions unterstützt wurden. Außerdem haben wir Abstrakte Seiten so aktualisiert, dass neben dem Seitentitel nun eine kopierbare QID angezeigt wird. Dadurch lässt sich die entsprechende Wikidata-QID schneller kopieren, ähnlich der kopierbaren ZID, die neben den Titeln in Wikifunctions angezeigt wird ([[:phab:T423651|T423651]], [[:phab:T424265|T424265]]). <div lang="en" dir="ltr" class="mw-content-ltr"> === News in Types: way forward for natural language generation types === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> I have been reading and thinking about the [[Special:MyLanguage/Wikifunctions:Status updates/2026-04-10|currently open proposals and their discussion for types supporting natural language generation]] for a while, and I am honestly not sure about the best approach forward. But I am getting the feeling that figuring out the best answer might be getting in the way of moving forward. Given that, I would suggest that within the next two weeks we get the following three types specific enough to implement them, then actually implement them, then use them, and learn from their usage: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikifunctions:Type proposals/Semantic unit|Semantic Unit]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikifunctions:Type proposals/Syntactic unit|Syntactic Unit]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikifunctions:Type proposals/Syntactic table|Syntactic table]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All three proposals have garnered some, but not unanimous approval, and I think they all have advantages and disadvantages. But I wonder if instead of thinking through these in detail, we just try them out, and see what works. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If anyone has better proposals moving forward, I am all ears. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Recording of the May 11 Volunteers’ Corner === </div> [[File:Abstract Wikipedia Volunteer Corner 2026-05.webm|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Recording of May Volunteers' Corner</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> This [[:c:File:Abstract Wikipedia Volunteer Corner 2026-05.webm|Monday’s volunteer’s corner (11 May 2026) is now available as a recording on Commons]]. Thank you for the lively conversation, and for the well-attended meeting. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Fresh Functions weekly: 40 new Functions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This week we had 40 new functions. Here is an incomplete list of functions with implementations and passing tests to get a taste of what functions have been created. Thanks everybody for contributing! </div> * {{Z|Z34780}} * {{Z|Z34790}} * {{Z|Z34793}} * {{Z|Z34797}} * {{Z|Z34802}} * {{Z|Z34804}} * {{Z|Z34810}} * {{Z|Z34827}} * {{Z|Z832}} * {{Z|Z862}} * {{Z|Z34899}} * {{Z|Z34902}} * {{Z|Z34914}} * {{Z|Z34927}} * {{Z|Z34943}} * {{Z|Z34947}} * {{Z|Z34953}} * {{Z|Z34993}} * {{Z|Z34999}} * {{Z|Z35004}} * {{Z|Z35010}} * {{Z|Z35013}} * {{Z|Z35017}} * {{Z|Z35018}} * {{Z|Z35022}} * {{Z|Z35023}} * {{Z|Z35031}} * {{Z|Z35049}} <div lang="en" dir="ltr" class="mw-content-ltr"> A [https://www.wikifunctions.org/wiki/Special:ListObjectsByType?type=Z8&orderby=latest complete list of all functions sorted by when they were created] is available. </div> [[Category:Status updates{{#translation:}}|2026-05-15]] nh51fyldjpxpmwga43web1zod5kubiw 275567 275565 2026-05-16T20:49:43Z Ameisenigel 44 Created page with "=== Neuigkeiten zu Typen: Weg nach vorn für Typen zur Generierung natürlicher Sprache ===" 275567 wikitext text/x-wiki <languages/> {{Wikifunctions updates | prevlabel = Vorheriges Update | prev = 2026-05-08 | nextlabel = Nächstes Update | next = }} <span id="A_higher_meaning"></span> === Eine höhere Bedeutung === Eine der zentralen Fragen zur Abstrakten Wikipedia lautet: Wie viele [[Special:MyLanguage/Wikifunctions:Abstract Wikipedia/2025 fragment experiments|Funktionen zur Konstruktion von Textfragmenten]] benötigen wir? Denn wenn diese Zahl groß ist, bedeutet das nicht, dass wir viele Funktionen benötigen, die diese Fragmente in vielen Sprachen implementieren? Und das würde den Aufwand für jede Sprache erhöhen und wäre es nicht irgendwann einfacher, die Texte einfach zu übersetzen und die Übersetzungen zu validieren, anstatt all diese Funktionen zu erstellen? Wir wissen nicht, wie groß diese Zahl sein wird. Aber heute möchte ich einen Grund dafür erörtern, warum ich glaube, dass sie begrenzt bleiben wird: Nicht jedes Fragment muss durch sprachspezifische Funktionen implementiert werden. Wie wäre das der Fall? Müssen wir nicht jedes Fragment mit einer sprachspezifischen Funktion in jeder Sprache implementieren, die wir unterstützen wollen? Prinzipiell schon, aber manchmal können diese Implementierungen Kompositionen anderer abstrakter Funktionen sein! Hier ein konkretes Beispiel: {{Z|Z28436}} erstellt einen Satz aus einer Aussage mit einer Eigenschaft Zeitpunkt. Zum Beispiel ein Satz wie “Die Einwohnerzahl von North Epping lag 2021 bei 4657.” oder "Die Einwohnerzahl von Donji Humac lag 2011 bei 157." Die Funktion Z28436 wird mithilfe eines Konfigurationsobjekts implementiert, derzeit mit Implementierungen in Englisch und Bengalisch. Betrachten wir nun die Funktion {{Z|Z28445}}. Anstatt ein Objekt und eine Aussage entgegenzunehmen, erwartet sie ein Objekt und eine Eigenschaft und gibt den Wert der Aussage für diese Eigenschaft mit dem aktuellsten Zeitpunkt zurück. Wenn wir diese Funktion also für Donji Humac und die Einwohnerzahl ausführen, erhalten wir das Ergebnis: "Die Einwohnerzahl von Donji Humac lag 2021 bei 173." Dies ist die aktuellste Einwohnerzahlangabe, die wir in Wikidata für Donji Humac haben. Betrachten wir nun die Implementierung von Z28445, so sehen wir keine Konfiguration. Stattdessen sehen wir eine Funktion, die aus der obigen Funktion, Z28436, und {{Z|Z28446}} besteht. Nichts an dieser Implementierung ist sprachspezifisch. Die Sprache wird vielmehr an die zugrundeliegende Funktion weitergegeben. Wir sehen hier also eine abstrakte Funktion, die eine vollständig abstrakte Implementierung besitzt. Dies ist ein allgemeines Muster, das wiederverwendet werden kann: Wenn wir über eine solide Grundlage verfügen, ist es hoffentlich oft möglich, "höhere" abstrakte Funktionen auf fundamentaleren Funktionen zu gründen, die dennoch abstrakt sind. Betrachten wir beispielsweise die folgenden Sätze * “Die Hunnen griffen das Römische Reich im 5. Jahrhundert an.” * “John Wilkes Booth ermordete Abraham Lincoln am 14. April 1865.” * “John Lennon traf Yoko Ono am 7. November 1966.” * “Leonard Cohen schrieb ‘Hallelujah’ im Jahr 1984.” * “Microsoft brachte Windows 3.1 am 24. August 1995 auf den Markt.” * “Hubble entdeckte Osiris am 28. November 2001.” Sie beschreiben zwar sehr unterschiedliche Ereignisse, aber im Grunde haben sie alle im Englischen eine sehr ähnliche Struktur: Sie bestehen aus Prädikat, Subjekt, direktem Objekt und einem mehr oder weniger genauen Zeitpunkt. Alle diese Sätze könnten im Englischen durch eine einzige Funktion gebildet werden. Vielleicht stellt sich heraus, dass sich all diese Sätze in mehreren Sprachen durch eine einzige abstrakte Funktion erzeugen lassen. Nennen wir diese Funktion eine Basisfunktion. Und nun könnten wir mehrere übergeordnete Funktionen haben, die durch solche Basisfunktionen implementiert werden, und wir müssen nur noch das richtige Prädikat auswählen. Das funktioniert nicht immer. Der Vorteil ist jedoch, dass wir, wenn wir diese übergeordneten Funktionen haben, versuchen können, die Ausnahme auf dieser Ebene abzufangen, sie an die entsprechende Sprache weiterzuleiten und andernfalls das richtige Prädikat auszuwählen und einfach die Basisfunktion zu verwenden. Zum Beispiel würden wir auf Deutsch normalerweise sagen * “Goldie Hawn brachte Kate Hudson am 19. April 1979 zur Welt.” Das ist eine etwas andere grammatikalische Struktur als die obige. Die obige grammatikalische Struktur würde zu “Goldie Hawn gebar Kate Hudson am 19. April 1979.” führen – was im Deutschen ein ungewöhnlicher Satz wäre, aber in einigen anderen Sprachen, z. B. im Kroatischen, problemlos funktioniert. Eine Funktion, die diesen Satz erzeugt, könnte für diesen Anwendungsfall eine andere Basisfunktion wählen oder sogar eine einmalige Implementierung für Deutsch und andere Sprachen haben, in denen die oben eingeführte Basisfunktion nicht funktionieren würde, und für die anderen Sprachen die Basisfunktion verwenden. Ein solches Muster könnte die Anzahl der für das Funktionieren der Abstrakten Wikipedia erforderlichen sprachspezifischen Implementierungen erheblich reduzieren und unser Ziel somit realistischer machen. <span id="Recent_Changes_in_the_software"></span> === Letzte Änderungen an der Software === Diese Woche haben wir in Wikifunctions die Unterstützung für mehrere Dutzend natürliche Sprachen hinzugefügt, die bereits von [https://translatewiki.net/ TranslateWiki.net] unterstützt (und für die Übersetzung von Wikimedia-Software verwendet) wurden, aber noch nicht von Wikifunctions unterstützt wurden. Außerdem haben wir Abstrakte Seiten so aktualisiert, dass neben dem Seitentitel nun eine kopierbare QID angezeigt wird. Dadurch lässt sich die entsprechende Wikidata-QID schneller kopieren, ähnlich der kopierbaren ZID, die neben den Titeln in Wikifunctions angezeigt wird ([[:phab:T423651|T423651]], [[:phab:T424265|T424265]]). <span id="News_in_Types:_way_forward_for_natural_language_generation_types"></span> === Neuigkeiten zu Typen: Weg nach vorn für Typen zur Generierung natürlicher Sprache === <div lang="en" dir="ltr" class="mw-content-ltr"> I have been reading and thinking about the [[Special:MyLanguage/Wikifunctions:Status updates/2026-04-10|currently open proposals and their discussion for types supporting natural language generation]] for a while, and I am honestly not sure about the best approach forward. But I am getting the feeling that figuring out the best answer might be getting in the way of moving forward. Given that, I would suggest that within the next two weeks we get the following three types specific enough to implement them, then actually implement them, then use them, and learn from their usage: </div> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikifunctions:Type proposals/Semantic unit|Semantic Unit]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikifunctions:Type proposals/Syntactic unit|Syntactic Unit]]</span> * <span lang="en" dir="ltr" class="mw-content-ltr">[[Wikifunctions:Type proposals/Syntactic table|Syntactic table]]</span> <div lang="en" dir="ltr" class="mw-content-ltr"> All three proposals have garnered some, but not unanimous approval, and I think they all have advantages and disadvantages. But I wonder if instead of thinking through these in detail, we just try them out, and see what works. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If anyone has better proposals moving forward, I am all ears. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Recording of the May 11 Volunteers’ Corner === </div> [[File:Abstract Wikipedia Volunteer Corner 2026-05.webm|thumb|<span lang="en" dir="ltr" class="mw-content-ltr">Recording of May Volunteers' Corner</span>]] <div lang="en" dir="ltr" class="mw-content-ltr"> This [[:c:File:Abstract Wikipedia Volunteer Corner 2026-05.webm|Monday’s volunteer’s corner (11 May 2026) is now available as a recording on Commons]]. Thank you for the lively conversation, and for the well-attended meeting. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Fresh Functions weekly: 40 new Functions === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> This week we had 40 new functions. Here is an incomplete list of functions with implementations and passing tests to get a taste of what functions have been created. Thanks everybody for contributing! </div> * {{Z|Z34780}} * {{Z|Z34790}} * {{Z|Z34793}} * {{Z|Z34797}} * {{Z|Z34802}} * {{Z|Z34804}} * {{Z|Z34810}} * {{Z|Z34827}} * {{Z|Z832}} * {{Z|Z862}} * {{Z|Z34899}} * {{Z|Z34902}} * {{Z|Z34914}} * {{Z|Z34927}} * {{Z|Z34943}} * {{Z|Z34947}} * {{Z|Z34953}} * {{Z|Z34993}} * {{Z|Z34999}} * {{Z|Z35004}} * {{Z|Z35010}} * {{Z|Z35013}} * {{Z|Z35017}} * {{Z|Z35018}} * {{Z|Z35022}} * {{Z|Z35023}} * {{Z|Z35031}} * {{Z|Z35049}} <div lang="en" dir="ltr" class="mw-content-ltr"> A [https://www.wikifunctions.org/wiki/Special:ListObjectsByType?type=Z8&orderby=latest complete list of all functions sorted by when they were created] is available. </div> [[Category:Status updates{{#translation:}}|2026-05-15]] 9e9ydkvj1v0g98gbr2vzfjtauh0xtvu 1 83563 275610 275265 2026-05-17T01:48:02Z YoshiRulz 10156 Add links to related types 275610 wikitext text/x-wiki {{type documentation|Z25340|Grammatical gender (m/f) |related types={{type documentation/related types/grammatical feature enums}} }} jqdtykt0f4dsjibsk7z50rivjb97d7x 1 83564 275611 275266 2026-05-17T01:48:12Z YoshiRulz 10156 Add links to related types 275611 wikitext text/x-wiki {{type documentation|Z25501|Grammatical gender (m/f/n) |related types={{type documentation/related types/grammatical feature enums}} }} k23fqpvhy7jqodbvt510ngckjtpqcrl 1 83565 275609 275267 2026-05-17T01:47:56Z YoshiRulz 10156 Add links to related types 275609 wikitext text/x-wiki {{type documentation|Z25502|Grammatical gender (c/n) |related types={{type documentation/related types/grammatical feature enums}} }} j6bl5kdm9gurw636uq9ak0h168ve86y 1 83566 275614 275269 2026-05-17T01:48:24Z YoshiRulz 10156 Add links to related types 275614 wikitext text/x-wiki {{type documentation|Z26934|Grammatical number (sing./pl.) |related types={{type documentation/related types/grammatical feature enums}} }} qm5fn2egkx7agebzzyd6b5bvps1rwld 1 83567 275605 275270 2026-05-17T01:47:37Z YoshiRulz 10156 Add links to related types 275605 wikitext text/x-wiki {{type documentation|Z26935|Grammatical animacy (animate/inanimate) |related types={{type documentation/related types/grammatical feature enums}} }} m6qx93ha4q5u97nqakppf7rm0atelmu 1 83569 275615 275272 2026-05-17T01:48:28Z YoshiRulz 10156 Add links to related types 275615 wikitext text/x-wiki {{type documentation|Z27970|Grammatical person (3) |related types={{type documentation/related types/grammatical feature enums}} }} mp6al89b31ljlzc1334b6gdh3nrghn7 1 83570 275604 275273 2026-05-17T01:47:19Z YoshiRulz 10156 Add links to related types 275604 wikitext text/x-wiki {{type documentation|Z27971|Celtic mutation |related types={{type documentation/related types/grammatical feature enums}} }} p6s79nz9juwmczjtxnpp35oxq7g22uw 1 83571 275612 275274 2026-05-17T01:48:16Z YoshiRulz 10156 Add links to related types 275612 wikitext text/x-wiki {{type documentation|Z28215|Grammatical number (sing./dual/pl.) |related types={{type documentation/related types/grammatical feature enums}} }} kcgtnl339sfsoyziilagun4b6if0pb8 1 83572 275613 275275 2026-05-17T01:48:20Z YoshiRulz 10156 Add links to related types 275613 wikitext text/x-wiki {{type documentation|Z28515|Grammatical number (sing./paucal/multal) |related types={{type documentation/related types/grammatical feature enums}} }} lb10t5gkfc8xrt47iabue7fp75774gc 1 83573 275607 275276 2026-05-17T01:47:46Z YoshiRulz 10156 Add links to related types 275607 wikitext text/x-wiki {{type documentation|Z28516|Grammatical definiteness |related types={{type documentation/related types/grammatical feature enums}} }} ebhz6nfomrg8rjvhit7f9vapap0j8as 1 83574 275619 275277 2026-05-17T01:48:46Z YoshiRulz 10156 Add links to related types 275619 wikitext text/x-wiki {{type documentation|Z28517|Grammatical voice (active/passive) |related types={{type documentation/related types/grammatical feature enums}} }} c14893be3svhnw16f4g1l0sw34p0foe 1 83575 275616 275278 2026-05-17T01:48:32Z YoshiRulz 10156 Add links to related types 275616 wikitext text/x-wiki {{type documentation|Z28518|Grammatical polarity (affirmative/negation) |related types={{type documentation/related types/grammatical feature enums}} }} m9w79bu2ia28suipf6ed343sm9yt1pn 1 83576 275606 275279 2026-05-17T01:47:42Z YoshiRulz 10156 Add links to related types 275606 wikitext text/x-wiki {{type documentation|Z28519|Grammatical case (Nom/Gen/Dat/Acc) |related types={{type documentation/related types/grammatical feature enums}} }} fqfb87a26xm1jdjogrc6zpi481jl7it 1 83577 275608 275280 2026-05-17T01:47:52Z YoshiRulz 10156 Add links to related types 275608 wikitext text/x-wiki {{type documentation|Z28520|Grammatical degree of comparison (pos/comp/super) |related types={{type documentation/related types/grammatical feature enums}} }} dnwbamlw0ggbdkna60qch1fqu5kbqpd 1 83578 275618 275281 2026-05-17T01:48:41Z YoshiRulz 10156 Add links to related types 275618 wikitext text/x-wiki {{type documentation|Z32789|Grammatical voice (active/middle/passive) |related types={{type documentation/related types/grammatical feature enums}} }} 0e7s6rre2cgyrkzzeqxgzxkgb0zowz3 1 83602 275617 275309 2026-05-17T01:48:36Z YoshiRulz 10156 Add links to related types 275617 wikitext text/x-wiki {{type documentation|Z32792|Grammatical voice (active/mediopassive) |related types={{type documentation/related types/grammatical feature enums}} }} 5nfxjrt4z2vjjmb6maprmoy2g7tj4tt 0 83636 275546 275431 2026-05-16T18:09:12Z Poro26 1521 Correction du type 275546 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35223" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z19677", "Z17K2": "Z35223K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "aire de base" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z19677", "Z17K2": "Z35223K2", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "aire latérale " } ] } } ], "Z8K2": "Z19677", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z35223" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "Calculer l'aire totale d'un prisme droit" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "Aire totale d'un prisme droit" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "aire totale d'un prisme droit est égal à 2 fois l'aire de base plus l'aire latérale " } ] } } t530fzfed02etrjh6pi1qubmkrmdh32 0 83637 275497 275456 2026-05-16T12:01:04Z Néhémienathan 35027 #WikiHackCiv2026 modification du type de données 275497 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35224" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z20838", "Z17K2": "Z35224K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "volume" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z13518", "Z17K2": "Z35224K2", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "temps ou durée (en seconde)" } ] } } ], "Z8K2": "Z20838", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z35224" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "calculer le débit moyen" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "débit moyen " ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "fonction permettant de calculer le volume total d'eau ayant coulé pendant une période précise" } ] } } 34dqaugcwdgzs9zxfhz7667nm0fy98d 275522 275497 2026-05-16T12:39:20Z Néhémienathan 35027 #WikiHackCiv2026 modification du type de données 275522 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35224" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z20838", "Z17K2": "Z35224K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "volume" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z20838", "Z17K2": "Z35224K2", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "temps ou durée (en seconde)" } ] } } ], "Z8K2": "Z20838", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z35224" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "calculer le débit moyen" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "débit moyen " ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "fonction permettant de calculer le volume total d'eau ayant coulé pendant une période précise" } ] } } 4h32zup20hfhjzl56yp99rq47ugx0zb 0 83643 275581 275488 2026-05-17T00:20:23Z Poro26 1521 #WikiHackCiv2026 Correction du libellé 275581 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35230" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35219", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35219", "Z35219K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "8" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "4292493394837504" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35219K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "4" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1125899906842624" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "4" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "2533274790395904" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "500 kg et 20 dm³ → 25 kg/dm³" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } g6jshyxtajdzpryqsvwvlpzw73smf06 0 83644 275505 2026-05-16T12:10:03Z Tways2017 70210 #WikiHackCiv2026 premier test de la fonction calcul de la vitesse moyenne 275505 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35231" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35221", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35221", "Z35221K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "6" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "2533274790395904" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35221K2": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "5" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "4" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1125899906842624" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "100Km et 5h → 20Km/h" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } euwqu25mai85u5vea9rsvl30wyi4tql 275575 275505 2026-05-17T00:07:43Z Poro26 1521 #WikiHackCiv2026 Correction 275575 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35231" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35221", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35221", "Z35221K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "6" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "2533274790395904" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35221K2": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "5" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "4" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1125899906842624" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "100km et 5h → 20km/h" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ppql376hnxw673wzxq218k1h1uwotzs 0 83645 275506 2026-05-16T12:10:06Z Néhémienathan 35027 #WikiHackCiv2026 ajout de test 1 275506 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35232" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35224", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35224", "Z35224K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "4" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1407374883553280" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35224K2": { "Z1K1": "Z13518", "Z13518K1": "300" } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "2" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "3377699720527872" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "21 m3 et 300 secondes → 0.07 m3/s" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ao7cv6mv7f32x5160ho96kihs6oba8m 275520 275506 2026-05-16T12:30:55Z Néhémienathan 35027 #WikiHackCiv2026 275520 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35232" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35224", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35224", "Z35224K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "3" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1407374883553280" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35224K2": { "Z1K1": "Z13518", "Z13518K1": "300" } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "2" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "3377699720527872" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "21 m3 et 300 secondes → 0.07 m3/s" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 30std4iqy12ip6lvlkdzy28mvom0h07 275521 275520 2026-05-16T12:33:12Z Néhémienathan 35027 #WikiHackCiv2026 275521 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35232" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35224", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35224", "Z35224K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "4" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1407374883553280" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35224K2": { "Z1K1": "Z13518", "Z13518K1": "300" } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "2" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "3377699720527872" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "21 m3 et 300 secondes → 0.07 m3/s" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ao7cv6mv7f32x5160ho96kihs6oba8m 275523 275521 2026-05-16T12:41:21Z Néhémienathan 35027 275523 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35232" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35224", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35224", "Z35224K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "4" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1407374883553280" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35224K2": { "Z1K1": "Z13518", "Z13518K1": "300" } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z21956", "Z21956K2": "Z1004" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "21 m3 et 300 secondes → 0.07 m3/s" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 4h0nt1fpwuvgao8lhgxtvrvnat10gbb 0 83646 275508 2026-05-16T12:11:19Z PenScribe 73650 #WikiHackCiv2026 ajout de test a la fonction 275508 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35233" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35223", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35223", "Z35223K1": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "15" } }, "Z35223K2": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "130" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z16688", "Z16688K2": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "160" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "15 cm2 et 130 cm2 → 160 cm2" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 3yzyp2eq0hnpbvpbn3g7cefk5o6te9j 275536 275508 2026-05-16T17:19:17Z Poro26 1521 #WikiHackCiv2026 Correction du libellé 275536 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35233" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35223", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35223", "Z35223K1": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "15" } }, "Z35223K2": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "130" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z16688", "Z16688K2": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "160" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "15 cm² et 130 cm² → 160 cm²" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } llr8bz241usvz4cfwkchoy2vmc770nj 0 83647 275526 2026-05-16T16:16:03Z JJPMaster 6409 adapted from [[Z32433]] and [[Z23502]] 275526 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35234" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z34542", "Z14K2": { "Z1K1": "Z7", "Z7K1": "Z802", "Z802K1": { "Z1K1": "Z7", "Z7K1": "Z813", "Z813K1": { "Z1K1": "Z7", "Z7K1": "Z23502", "Z23502K1": { "Z1K1": "Z7", "Z7K1": "Z22220", "Z22220K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z34542K1" }, "Z30120K2": [ "Z6030", "Z6036" ], "Z30120K3": [ "Z60" ], "Z30120K4": [ "Z6092", { "Z1K1": "Z18", "Z18K1": "Z34542K2" } ] } } } }, "Z802K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z802K3": { "Z1K1": "Z7", "Z7K1": "Z12696", "Z12696K1": { "Z1K1": "Z7", "Z7K1": "Z22978", "Z22978K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z34542K1" }, "Z30120K2": [ "Z6030", "Z6036" ], "Z30120K3": [ "Z60" ], "Z30120K4": [ "Z6092", { "Z1K1": "Z18", "Z18K1": "Z34542K2" } ] }, "Z22978K2": { "Z1K1": "Z18", "Z18K1": "Z34542K2" } }, "Z12696K2": { "Z1K1": "Z18", "Z18K1": "Z34542K3" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } a7kyys7fut2q41grsou2tt8a64eyz25 275529 275526 2026-05-16T16:21:43Z JJPMaster 6409 correct implementation of false condition 275529 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35234" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z34542", "Z14K2": { "Z1K1": "Z7", "Z7K1": "Z802", "Z802K1": { "Z1K1": "Z7", "Z7K1": "Z813", "Z813K1": { "Z1K1": "Z7", "Z7K1": "Z23502", "Z23502K1": { "Z1K1": "Z7", "Z7K1": "Z22220", "Z22220K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z34542K1" }, "Z30120K2": [ "Z6030", "Z6036" ], "Z30120K3": [ "Z60" ], "Z30120K4": [ "Z6092", { "Z1K1": "Z18", "Z18K1": "Z34542K2" } ] } } } }, "Z802K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z802K3": { "Z1K1": "Z7", "Z7K1": "Z12696", "Z12696K1": { "Z1K1": "Z7", "Z7K1": "Z873", "Z873K1": "Z19308", "Z873K2": { "Z1K1": "Z7", "Z7K1": "Z23502", "Z23502K1": { "Z1K1": "Z7", "Z7K1": "Z22220", "Z22220K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z34542K1" }, "Z30120K2": [ "Z6030", "Z6036" ], "Z30120K3": [ "Z60" ], "Z30120K4": [ "Z6092", { "Z1K1": "Z18", "Z18K1": "Z34542K2" } ] } } } }, "Z12696K2": { "Z1K1": "Z18", "Z18K1": "Z34542K3" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } exqf02bdr258l2bvlqwmlhw6dekvc88 275531 275529 2026-05-16T16:24:46Z JJPMaster 6409 275531 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35234" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z34542", "Z14K2": { "Z1K1": "Z7", "Z7K1": "Z802", "Z802K1": { "Z1K1": "Z7", "Z7K1": "Z813", "Z813K1": { "Z1K1": "Z7", "Z7K1": "Z23502", "Z23502K1": { "Z1K1": "Z7", "Z7K1": "Z22220", "Z22220K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z34542K1" }, "Z30120K2": [ "Z6030", "Z6036" ], "Z30120K3": [ "Z60" ], "Z30120K4": [ "Z6092", { "Z1K1": "Z18", "Z18K1": "Z34542K2" } ] } } } }, "Z802K2": { "Z1K1": "Z40", "Z40K1": "Z42" }, "Z802K3": { "Z1K1": "Z7", "Z7K1": "Z12696", "Z12696K1": { "Z1K1": "Z7", "Z7K1": "Z873", "Z873K1": "Z19308", "Z873K2": { "Z1K1": "Z7", "Z7K1": "Z23502", "Z23502K1": { "Z1K1": "Z7", "Z7K1": "Z22220", "Z22220K1": { "Z1K1": "Z7", "Z7K1": "Z30120", "Z30120K1": { "Z1K1": "Z18", "Z18K1": "Z34542K1" }, "Z30120K2": [ "Z6030", "Z6036" ], "Z30120K3": [ "Z60" ], "Z30120K4": [ "Z6092", { "Z1K1": "Z18", "Z18K1": "Z34542K2" } ] } } } }, "Z12696K2": { "Z1K1": "Z18", "Z18K1": "Z34542K3" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "item has undeprecated statement with value, comp" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 90v7rjgq7n6em0pfckr4eyc35pwagcl 0 83648 275542 2026-05-16T17:38:10Z Jsamwrites 938 275542 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35235" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z34938", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z34938", "Z34938K1": { "Z1K1": "Z6091", "Z6091K1": "Q90" }, "Z34938K2": { "Z1K1": { "Z1K1": "Z7", "Z7K1": "Z883", "Z883K1": "Z6091", "Z883K2": "Z6091" }, "K1": [ { "Z1K1": "Z7", "Z7K1": "Z882", "Z882K1": "Z6091", "Z882K2": "Z6091" } ] }, "Z34938K3": "Z1002" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z14392", "Z14392K2": { "Z1K1": "Z7", "Z7K1": "Z26107", "Z26107K1": "Z1002", "Z26107K2": { "Z1K1": "Z7", "Z7K1": "Z24766", "Z24766K1": { "Z1K1": "Z6091", "Z6091K1": "Q90" }, "Z24766K2": "Z1002" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "appropriate referential - empty reference context" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } t882g99majqtzm0zf5n43fpftad6kkc 275544 275542 2026-05-16T17:42:08Z Jsamwrites 938 275544 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35235" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z34938", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z34938", "Z34938K1": { "Z1K1": "Z6091", "Z6091K1": "Q90" }, "Z34938K2": { "Z1K1": { "Z1K1": "Z7", "Z7K1": "Z883", "Z883K1": "Z6091", "Z883K2": "Z6091" }, "K1": [ { "Z1K1": "Z7", "Z7K1": "Z882", "Z882K1": "Z6091", "Z882K2": "Z6091" }, { "Z1K1": { "Z1K1": "Z7", "Z7K1": "Z882", "Z882K1": "Z6091", "Z882K2": "Z6091" }, "K1": { "Z1K1": "Z6091", "Z6091K1": "Q28314507" }, "K2": { "Z1K1": "Z6091", "Z6091K1": "Q5432619" } } ] }, "Z34938K3": "Z1002" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z14392", "Z14392K2": { "Z1K1": "Z7", "Z7K1": "Z26107", "Z26107K1": "Z1002", "Z26107K2": { "Z1K1": "Z7", "Z7K1": "Z24766", "Z24766K1": { "Z1K1": "Z6091", "Z6091K1": "Q90" }, "Z24766K2": "Z1002" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "appropriate referential - not recurring" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } heyyqti1skjror2zrkoosjnwzh8m0aw 0 83649 275545 2026-05-16T18:06:08Z Poro26 1521 #WikiHackCiv2026 Ajout de test 275545 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35236" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35223", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35223", "Z35223K1": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "2" } }, "Z35223K2": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "11" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z16688", "Z16688K2": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "15" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "2 cm² et 11 cm² → 15 cm²" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } g94lya1jkumpabd8rj6lp4uxgvcq713 0 83650 275552 2026-05-16T19:48:26Z Aaron Liu 2395 add test case where subject needs a definite article; previously we only tested dependency 275552 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35237" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z28026", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z28026", "Z28026K1": { "Z1K1": "Z6091", "Z6091K1": "Q928949" }, "Z28026K2": { "Z1K1": "Z6091", "Z6091K1": "Q1346215" }, "Z28026K3": { "Z1K1": "Z6091", "Z6091K1": "Q733" }, "Z28026K4": "Z1002" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z14392", "Z14392K2": { "Z1K1": "Z11", "Z11K1": { "Z1K1": "Z9", "Z9K1": "" }, "Z11K2": "The Colorado Party is the ruling party of Paraguay." } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "The Colorado Party is the ruling party of Paraguay" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } pung971e0elq23bjbfq0tsubtrlumi9 275554 275552 2026-05-16T19:49:54Z Aaron Liu 2395 add language to monolingual text 275554 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35237" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z28026", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z28026", "Z28026K1": { "Z1K1": "Z6091", "Z6091K1": "Q928949" }, "Z28026K2": { "Z1K1": "Z6091", "Z6091K1": "Q1346215" }, "Z28026K3": { "Z1K1": "Z6091", "Z6091K1": "Q733" }, "Z28026K4": "Z1002" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z14392", "Z14392K2": { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "The Colorado Party is the ruling party of Paraguay." } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "The Colorado Party is the ruling party of Paraguay" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ic12knvvno3huqslkbrmssm2874ihyc 0 83651 275556 2026-05-16T19:58:40Z Modalya 73649 #WikiHackCiv2026 Ajout de test 275556 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35238" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35222", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35222", "Z35222K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "4" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1125899906842624" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35222K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "6" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "2533274790395904" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z24582", "Z24582K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "7" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "2533274790395904" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "20cm et 10cm → 200cm²" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 7tyxqeeqcnpv2yxwku8xj1ky4t4bgfc 0 83652 275559 2026-05-16T20:18:36Z Poro26 1521 #WikiHackCiv2026 Ajout de test 275559 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35239" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35223", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35223", "Z35223K1": { "Z1K1": "Z19677", "Z19677K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z19677K2": { "Z1K1": "Z13518", "Z13518K1": "10" }, "Z19677K3": { "Z1K1": "Z13518", "Z13518K1": "1" } }, "Z35223K2": { "Z1K1": "Z19677", "Z19677K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z19677K2": { "Z1K1": "Z13518", "Z13518K1": "120" }, "Z19677K3": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z19686", "Z19686K2": { "Z1K1": "Z19677", "Z19677K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z19677K2": { "Z1K1": "Z13518", "Z13518K1": "140" }, "Z19677K3": { "Z1K1": "Z13518", "Z13518K1": "1" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "10 cm² et 120 cm² → 140 cm²" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 746dffzu5vm6scdur050ubtqwto8o72 0 83653 275560 2026-05-16T20:24:41Z Poro26 1521 #WikiHackCiv2026 Ajout de test 275560 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35240" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35223", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35223", "Z35223K1": { "Z1K1": "Z19677", "Z19677K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z19677K2": { "Z1K1": "Z13518", "Z13518K1": "2" }, "Z19677K3": { "Z1K1": "Z13518", "Z13518K1": "1" } }, "Z35223K2": { "Z1K1": "Z19677", "Z19677K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z19677K2": { "Z1K1": "Z13518", "Z13518K1": "15" }, "Z19677K3": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z19686", "Z19686K2": { "Z1K1": "Z19677", "Z19677K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z19677K2": { "Z1K1": "Z13518", "Z13518K1": "19" }, "Z19677K3": { "Z1K1": "Z13518", "Z13518K1": "1" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "2 cm² et 15 cm² → 19 cm²" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } h6043tlzw60pv06u31828spphtlzd5d 0 83654 275561 2026-05-16T20:35:51Z Tways2017 70210 #WikiHackCiv2026 ajout de fonction calcul de l'autonomie bouteille ARI 275561 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35241" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z16683", "Z17K2": "Z35241K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "volume" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z20838", "Z17K2": "Z35241K2", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "pression" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z16683", "Z17K2": "Z35241K3", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "débit" } ] } } ], "Z8K2": "Z20838", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z35241" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "autonomie d'un bouteille d'ARI" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "autonomie bouteille ARI" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "Calcul de l'autonomie (unité généralement en minute) d'une bouteille d'ARI (Appareil Respiratoire Isolant) en fonction de débit (unité généralement en L/min) de consommation " } ] } } h2f227tejqyrg16bkz237k56fdcr98c 0 83655 275562 2026-05-16T20:39:12Z Poro26 1521 #WikiHackCiv2026 Ajout de test 275562 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35242" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35223", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35223", "Z35223K1": { "Z1K1": "Z19677", "Z19677K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z19677K2": { "Z1K1": "Z13518", "Z13518K1": "100" }, "Z19677K3": { "Z1K1": "Z13518", "Z13518K1": "1" } }, "Z35223K2": { "Z1K1": "Z19677", "Z19677K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z19677K2": { "Z1K1": "Z13518", "Z13518K1": "400" }, "Z19677K3": { "Z1K1": "Z13518", "Z13518K1": "1" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z19686", "Z19686K2": { "Z1K1": "Z19677", "Z19677K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z19677K2": { "Z1K1": "Z13518", "Z13518K1": "600" }, "Z19677K3": { "Z1K1": "Z13518", "Z13518K1": "1" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "100 m² et 400 m² → 600 m²" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 9e8roh8sbzaloc2iqkc4egk7gljllne 0 83656 275563 2026-05-16T20:40:55Z Tways2017 70210 #WikiHackCiv2026 ajout d'implémentation de la fonction de calcul de l'autonomie d'une bouteille d'ARI 275563 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35243" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z35241", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z610", "Z16K2": "def Z35241(Z35241K1, Z35241K2, Z35241K3):\n\treturn(Z35241K1*Z35241K2)/Z35241K3" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "calcul de l'autonomie d'une bouteille d'ARI" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "Calcul de l'autonomie d'une bouteille d'ARI en fonction du debit de consommation de l'utilisateur" } ] } } 6d1pvja9t37399v7suxou502rhz5wss 1198 83657 275564 2026-05-16T20:48:34Z Ameisenigel 44 Created page with "Diese Woche haben wir in Wikifunctions die Unterstützung für mehrere Dutzend natürliche Sprachen hinzugefügt, die bereits von [$1 TranslateWiki.net] unterstützt (und für die Übersetzung von Wikimedia-Software verwendet) wurden, aber noch nicht von Wikifunctions unterstützt wurden. Außerdem haben wir Abstrakte Seiten so aktualisiert, dass neben dem Seitentitel nun eine kopierbare QID angezeigt wird. Dadurch lässt sich die entsprechende Wikidata-QID schneller kop..." 275564 wikitext text/x-wiki Diese Woche haben wir in Wikifunctions die Unterstützung für mehrere Dutzend natürliche Sprachen hinzugefügt, die bereits von [$1 TranslateWiki.net] unterstützt (und für die Übersetzung von Wikimedia-Software verwendet) wurden, aber noch nicht von Wikifunctions unterstützt wurden. Außerdem haben wir Abstrakte Seiten so aktualisiert, dass neben dem Seitentitel nun eine kopierbare QID angezeigt wird. Dadurch lässt sich die entsprechende Wikidata-QID schneller kopieren, ähnlich der kopierbaren ZID, die neben den Titeln in Wikifunctions angezeigt wird ($2). 7u7z6vun2z2muhlf7td3yem0r6qaocl 1198 83658 275566 2026-05-16T20:49:42Z Ameisenigel 44 Created page with "=== Neuigkeiten zu Typen: Weg nach vorn für Typen zur Generierung natürlicher Sprache ===" 275566 wikitext text/x-wiki === Neuigkeiten zu Typen: Weg nach vorn für Typen zur Generierung natürlicher Sprache === ir6n3epewneeyngrzt1yf12qocsr1nh 0 83659 275568 2026-05-16T20:50:11Z Poro26 1521 #WikiHackCiv2026 Ajout d'implémentation en Javascript 275568 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35244" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z35223", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z600", "Z16K2": "function Z35223( Z35223K1, Z35223K2 ) {\n\n\treturn (2*Z35223K1)+Z35223K2;\n}" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "aire totale d'un prisme droit, Javascript" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } q3yxr8m4jir809kx9sxl2qab1kxeid6 0 83660 275569 2026-05-16T20:53:16Z Tways2017 70210 #WikiHackCiv2026 ajout de test de calcul d'autonomie de la bouteille d'ARI 275569 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35245" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35241", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35241", "Z35241K1": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z9", "Z9K1": "" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "6" } }, "Z35241K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "8" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "774056185954304" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35241K3": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z9", "Z9K1": "" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "12" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "7" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "774056185954304" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "6L, 300Bars et 12L/min →150min" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "une bouteille de 6L confléa à 300Bars avec une consommation de 12L.min donne 150min d'autonomie " } ] } } p5fu2lr4nr7x07vvh5pjzmd021isw0p 275570 275569 2026-05-16T20:56:34Z Tways2017 70210 #WikiHackCiv2026 verification Test 275570 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35245" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35241", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35241", "Z35241K1": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z9", "Z9K1": "" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "6" } }, "Z35241K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "8" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "774056185954304" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35241K3": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z9", "Z9K1": "" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "12" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "7" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "774056185954304" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "6 L, 300 Bar et 12 L/min →150min" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "une bouteille de 6L confléa à 300Bars avec une consommation de 12L.min donne 150min d'autonomie " } ] } } dnvhz7qrq10oe3ys63hhwqz0op1ddca 275571 275570 2026-05-16T21:03:37Z Tways2017 70210 #WikiHackCiv2026 verification Test autonomie Bouteille d'ARi 275571 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35245" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35241", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35241", "Z35241K1": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "6" } }, "Z35241K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "8" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "774056185954304" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35241K3": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "12" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "7" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "774056185954304" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "6 L, 300 Bar et 12 L/min →150min" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "une bouteille de 6L confléa à 300Bars avec une consommation de 12L.min donne 150min d'autonomie " } ] } } iwijp1dtp0km2uqzu2ras7qrrurti8c 0 83661 275576 2026-05-17T00:12:10Z Poro26 1521 #WikiHackCiv2026 Ajout d'implémentation en Javascript 275576 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35246" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z35221", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z600", "Z16K2": "function Z35221( Z35221K1, Z35221K2 ) {\n\treturn Z35221K1/Z35221K2;\n}" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "calcul de la vitesse moyenne, Javascript" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "calcul de la vitesse moyenne avec le langage Javascript" } ] } } hj0l3322ledclgr82whkf4xduc5b30q 0 83662 275577 2026-05-17T00:15:05Z Poro26 1521 #WikiHackCiv2026 Ajout de test 275577 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35247" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35221", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35221", "Z35221K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "5" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "2533274790395904" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35221K2": { "Z1K1": "Z16683", "Z16683K1": "Z16660", "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "10" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "2" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1125899906842624" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "50m et 10s → 5m/s" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } togbpj856phxyfx3taqk0h053ojm4t9 0 83663 275578 2026-05-17T00:15:45Z JJPMaster 6409 275578 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35248" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z13518", "Z17K2": "Z35248K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "ID" } ] } } ], "Z8K2": "Z89", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z35248" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "generate Discogs link from artist ID" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ie54gfeiqmrlkuyahz2bh2o1yigghex 275580 275578 2026-05-17T00:18:03Z JJPMaster 6409 Added Z35249 to the approved list of implementations 275580 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35248" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z13518", "Z17K2": "Z35248K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "ID" } ] } } ], "Z8K2": "Z89", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14", "Z35249" ], "Z8K5": "Z35248" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "generate Discogs link from artist ID" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } nkkry9x2s0zud48dgy3v97gqctu4eik 275582 275580 2026-05-17T00:21:43Z JJPMaster 6409 Removed Z35249 from the approved list of implementations 275582 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35248" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z13518", "Z17K2": "Z35248K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "ID" } ] } } ], "Z8K2": "Z89", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z35248" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "generate Discogs link from artist ID" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ie54gfeiqmrlkuyahz2bh2o1yigghex 275583 275582 2026-05-17T00:21:45Z JJPMaster 6409 +label 275583 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35248" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z13518", "Z17K2": "Z35248K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "ID" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z35248K2", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "label" } ] } } ], "Z8K2": "Z89", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z35248" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "generate Discogs link from artist ID" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ouk4ti2nq8ie2j77ntr2fdbqpfbm552 275586 275583 2026-05-17T00:23:07Z JJPMaster 6409 Added Z35249 to the approved list of implementations 275586 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35248" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z13518", "Z17K2": "Z35248K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "ID" } ] } }, { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z35248K2", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "label" } ] } } ], "Z8K2": "Z89", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14", "Z35249" ], "Z8K5": "Z35248" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "generate Discogs link from artist ID" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } cd60vrn1q35sdjpfq902f4zmn7a26dn 0 83664 275579 2026-05-17T00:17:55Z JJPMaster 6409 275579 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35249" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z35248", "Z14K2": { "Z1K1": "Z7", "Z7K1": "Z30016", "Z30016K1": { "Z1K1": "Z7", "Z7K1": "Z10000", "Z10000K1": "https://www.discogs.com/artist/", "Z10000K2": { "Z1K1": "Z7", "Z7K1": "Z13713", "Z13713K1": { "Z1K1": "Z18", "Z18K1": "Z35248K1" } } }, "Z30016K2": "" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "generate Discogs link from artist ID, composition" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } m5knkjn2qfeg4u3apv8btxi01f7jgfs 275585 275579 2026-05-17T00:23:00Z JJPMaster 6409 +label 275585 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35249" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z35248", "Z14K2": { "Z1K1": "Z7", "Z7K1": "Z10638", "Z10638K1": { "Z1K1": "Z7", "Z7K1": "Z10000", "Z10000K1": "https://www.discogs.com/artist/", "Z10000K2": { "Z1K1": "Z7", "Z7K1": "Z13713", "Z13713K1": { "Z1K1": "Z18", "Z18K1": "Z35248K1" } } }, "Z10638K2": { "Z1K1": "Z18", "Z18K1": "Z35248K2" } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "generate Discogs link from artist ID, composition" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } f8wa02ykd8jyon4kwl71subb1ks6pp9 275592 275585 2026-05-17T00:39:18Z JJPMaster 6409 string problem 275592 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35249" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z35248", "Z14K2": { "Z1K1": "Z7", "Z7K1": "Z27861", "Z27861K1": { "Z1K1": "Z7", "Z7K1": "Z10638", "Z10638K1": { "Z1K1": "Z7", "Z7K1": "Z10000", "Z10000K1": "https://www.discogs.com/artist/", "Z10000K2": { "Z1K1": "Z7", "Z7K1": "Z13713", "Z13713K1": { "Z1K1": "Z18", "Z18K1": "Z35248K1" } } }, "Z10638K2": { "Z1K1": "Z18", "Z18K1": "Z35248K2" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "generate Discogs link from artist ID, composition" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } q1khfx0z2m59z6iejtvbsys1zhbnfz8 0 83665 275584 2026-05-17T00:22:07Z Poro26 1521 #WikiHackCiv2026 Ajout d'implémentation en Javascript 275584 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35250" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z35219", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z600", "Z16K2": "function Z35219( Z35219K1, Z35219K2 ) {\n\treturn Z35219K1/Z35219K2;\n}" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "masse volumique, Javascript" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ear5dtrtgpuq8kwe6b60nuf25hb7lb2 0 83666 275587 2026-05-17T00:25:25Z Poro26 1521 #WikiHackCiv2026 Ajout de test 275587 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35251" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35219", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35219", "Z35219K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "9" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "4292493394837504" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35219K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "3" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1125899906842624" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "6" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "2533274790395904" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "1000 g et 10 cm³ → 100 g/cm³" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } fd8cyok12vfzeti0yr5o6r02mltzdga 0 83667 275589 2026-05-17T00:30:14Z Poro26 1521 #WikiHackCiv2026 Ajout de test 275589 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35252" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35222", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35222", "Z35222K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "4" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1125899906842624" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35222K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "1" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "0" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "5" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1125899906842624" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "20 cm et 2 cm → 40 cm²" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 66e78c8u5g165umdkgu99f9icw302mh 0 83668 275590 2026-05-17T00:34:30Z Poro26 1521 #WikiHackCiv2026 Ajout d'implémentation en Javascript 275590 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35253" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z35222", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z600", "Z16K2": "function Z35222( Z35222K1, Z35222K2 ) {\n\treturn Z35222K1*Z35222K1;\n}" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "Aire latérale d'un prisme droit, Javascript" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "calcul de l'aire latérale d'un prisme droit avec le langage Javascript" } ] } } ry43t3l10051ix3sezs3f1pmahuymme 275591 275590 2026-05-17T00:35:56Z Poro26 1521 #WikiHackCiv2026 Correction 275591 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35253" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z35222", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z600", "Z16K2": "function Z35222( Z35222K1, Z35222K2 ) {\n\treturn Z35222K1*Z35222K2;\n}" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "Aire latérale d'un prisme droit, Javascript" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "calcul de l'aire latérale d'un prisme droit avec le langage Javascript" } ] } } ddjornfkiystp0r21ymyotvg4l7xkre 0 83669 275593 2026-05-17T00:40:03Z Poro26 1521 #WikiHackCiv2026 Ajout d'implémentation en Javascript 275593 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35254" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z35224", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z600", "Z16K2": "function Z35224( Z35224K1, Z35224K2 ) {\n\treturn Z35224K1/Z35224K2;\n}" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "débit moyen, Javascript" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } d5ctyri08wxwgjurazqjs8qjxyiaccf 0 83670 275594 2026-05-17T00:43:45Z Poro26 1521 #WikiHackCiv2026 Ajout de test 275594 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35255" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35224", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35224", "Z35224K1": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "8" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "4292493394837504" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } }, "Z35224K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "5" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "2533274790395904" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z20850", "Z20850K2": { "Z1K1": "Z20838", "Z20838K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z20838K2": { "Z1K1": "Z16683", "Z16683K1": { "Z1K1": "Z16659", "Z16659K1": "Z16660" }, "Z16683K2": { "Z1K1": "Z13518", "Z13518K1": "3" } }, "Z20838K3": { "Z1K1": "Z13518", "Z13518K1": "1125899906842624" }, "Z20838K4": { "Z1K1": "Z20825", "Z20825K1": "Z20837" } } } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "500m³ et 50s → 10m³/s" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 4begcaksbvakcgo30zm4qcii5mmt989 0 83671 275595 2026-05-17T00:50:44Z Poro26 1521 #WikiHackCiv2026 Création d'une fonction 275595 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35256" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z35256K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "ISBN brut" } ] } } ], "Z8K2": "Z6", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z35256" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "formater un ISBN-10" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "formater ISBN-10" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "Formate un ISBN de dix chiffres en ajoutant correctement les tirets selon la norme ISBN-10" } ] } } njcfkrq16oxskzgoiqkx1afxmgus2xo 275597 275595 2026-05-17T00:56:36Z Poro26 1521 #WikiHackCiv2026 Correction 275597 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35256" }, "Z2K2": { "Z1K1": "Z8", "Z8K1": [ "Z17", { "Z1K1": "Z17", "Z17K1": "Z6", "Z17K2": "Z35256K1", "Z17K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "ISBN-10 brut" } ] } } ], "Z8K2": "Z6", "Z8K3": [ "Z20" ], "Z8K4": [ "Z14" ], "Z8K5": "Z35256" }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "formater un ISBN-10" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1004", "Z31K2": [ "Z6", "formater ISBN-10" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "Formate un ISBN de dix chiffres en ajoutant correctement les tirets selon la norme ISBN-10" } ] } } 2scrh7xeybye22a7fjo7fon4fkqmu3a 0 83672 275596 2026-05-17T00:55:57Z Poro26 1521 #WikiHackCiv2026 Ajout d'une implémentation en Python 275596 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35257" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z35256", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z610", "Z16K2": "def Z35256(Z35256K1):\n # Supprimer les espaces et tirets\n Z35256K1 = Z35256K1.replace(\"-\", \"\").replace(\" \", \"\")\n\n # Vérifier la longueur\n if len(Z35256K1) != 10:\n return \"ISBN-10 invalide\"\n\n # Formatage simple\n return f\"{Z35256K1[0]}-{Z35256K1[1:4]}-{Z35256K1[4:9]}-{Z35256K1[9]}\"" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "formater un ISBN-10, Python" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } 4pz6p2plp2ytwq5lywcmuasn74a6zuv 0 83673 275598 2026-05-17T00:58:09Z Poro26 1521 #WikiHackCiv2026 Ajout d'un test 275598 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35258" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z35256", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z35256", "Z35256K1": "2212675374" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z866", "Z866K2": "2-212-67537-4" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1004", "Z11K2": "2212675374 → 2-212-67537-4" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } av1h6bn3tld8iw5c7t6xei79dl1vu7k 10 83674 275602 2026-05-17T01:41:14Z YoshiRulz 10156 Create template 275602 wikitext text/x-wiki {{#switch:<includeonly>{{SUBJECTPAGENAME}}</includeonly> ||#default= * unknown |<!-- --> |Z28516= * {{Z+|Z27970}} |Z27970= * {{Z+|Z28516}} |<!-- --> |Z26935= * {{Z+|Z25502}} * {{Z+|Z25340}} * {{Z+|Z25501}} |Z25502= * {{Z+|Z26935}} * {{Z+|Z25340}} * {{Z+|Z25501}} |Z25340= * {{Z+|Z26935}} * {{Z+|Z25502}} * {{Z+|Z25501}} |Z25501= * {{Z+|Z26935}} * {{Z+|Z25502}} * {{Z+|Z25340}} |<!-- --> |Z28215= * {{Z+|Z28515}} * {{Z+|Z26934}} |Z28515= * {{Z+|Z28215}} * {{Z+|Z26934}} |Z26934= * {{Z+|Z28215}} * {{Z+|Z28515}} |<!-- --> |Z32792= * {{Z+|Z32789}} * {{Z+|Z28517}} |Z32789= * {{Z+|Z32792}} * {{Z+|Z28517}} |Z28517= * {{Z+|Z32792}} * {{Z+|Z32789}} |<!-- --> |Z28520= * {{Z+|Z28518}} |Z28518= * {{Z+|Z28520}} |<!-- --> }} * Other [[Special:MyLanguage/WF:Type#Grammatical_feature_enums|grammatical feature enums]] 1akdptouz8jqqh9soq4oqt1vqw06mmw 275603 275602 2026-05-17T01:44:04Z YoshiRulz 10156 Need to include these as explicitly blank 275603 wikitext text/x-wiki {{#switch:<includeonly>{{SUBJECTPAGENAME}}</includeonly> ||#default= * unknown |<!-- --> |Z28516= * {{Z+|Z27970}} |Z27970= * {{Z+|Z28516}} |<!-- --> |Z26935= * {{Z+|Z25502}} * {{Z+|Z25340}} * {{Z+|Z25501}} |Z25502= * {{Z+|Z26935}} * {{Z+|Z25340}} * {{Z+|Z25501}} |Z25340= * {{Z+|Z26935}} * {{Z+|Z25502}} * {{Z+|Z25501}} |Z25501= * {{Z+|Z26935}} * {{Z+|Z25502}} * {{Z+|Z25340}} |<!-- --> |Z28215= * {{Z+|Z28515}} * {{Z+|Z26934}} |Z28515= * {{Z+|Z28215}} * {{Z+|Z26934}} |Z26934= * {{Z+|Z28215}} * {{Z+|Z28515}} |<!-- --> |Z32792= * {{Z+|Z32789}} * {{Z+|Z28517}} |Z32789= * {{Z+|Z32792}} * {{Z+|Z28517}} |Z28517= * {{Z+|Z32792}} * {{Z+|Z32789}} |<!-- --> |Z28520= * {{Z+|Z28518}} |Z28518= * {{Z+|Z28520}} |<!-- --> |Z27971|Z28519= }} * Other [[Special:MyLanguage/WF:Type#Grammatical_feature_enums|grammatical feature enums]] 4zy7m5c00bl4a4pvdhcqaigzesevpu1 14 83675 275625 2026-05-17T02:59:32Z YoshiRulz 10156 Create page 275625 wikitext text/x-wiki [[Category:Types]] {{see also|WF:Function model#Lightweight enumerations}} 5tby5hz3idp4tfhuevr8837lt4ydcgi 1 83676 275628 2026-05-17T03:02:47Z YoshiRulz 10156 Add auto-generated docs 275628 wikitext text/x-wiki {{type documentation|Z881|Typed list}} 6rwrmrd8r0epca554ddcnwc5u4atd0m 1 83677 275631 2026-05-17T03:05:16Z YoshiRulz 10156 Add auto-generated docs 275631 wikitext text/x-wiki {{type documentation|Z883|Typed map}} pbpwe5xp2rsv2vt7c596jtfhibru6t2 1 83678 275632 2026-05-17T03:05:20Z YoshiRulz 10156 Add auto-generated docs 275632 wikitext text/x-wiki {{type documentation|Z6884|Typed enum of Wikidata references}} h4ydwsi37zohpmenip1brrr9vrnv1ld 14 83679 275633 2026-05-17T03:06:45Z YoshiRulz 10156 Create page 275633 wikitext text/x-wiki [[Category:Types]] n48d7yaex28b62qlqbo974na6jnn7xa 2 83680 275638 2026-05-17T04:40:35Z Jérémy-Günther-Heinz Jähnick 6055 Created page with "== Z2000 → Z2099 == {{Z|2000}} {{Z|2001}} {{Z|2002}} {{Z|2003}} {{Z|2004}} {{Z|2005}} {{Z|2006}} {{Z|2007}} {{Z|2008}} {{Z|2009}} {{Z|2010}} {{Z|2011}} {{Z|2012}} {{Z|2013}} {{Z|2014}} {{Z|2015}} {{Z|2016}} {{Z|2017}} {{Z|2018}} {{Z|2019}} {{Z|2020}} {{Z|2021}} {{Z|2022}} {{Z|2023}} {{Z|2024}} {{Z|2025}} {{Z|2026}} {{Z|2027}} {{Z|2028}} {{Z|2029}} {{Z|2030}} {{Z|2031}} {{Z|2032}} {{Z|2033}} {{Z|2034}} {{Z|2035}} {{Z|2036}} {{Z|2037}} {{Z|2038}} {{Z|2039}} {{Z|2040}..." 275638 wikitext text/x-wiki == Z2000 → Z2099 == {{Z|2000}} {{Z|2001}} {{Z|2002}} {{Z|2003}} {{Z|2004}} {{Z|2005}} {{Z|2006}} {{Z|2007}} {{Z|2008}} {{Z|2009}} {{Z|2010}} {{Z|2011}} {{Z|2012}} {{Z|2013}} {{Z|2014}} {{Z|2015}} {{Z|2016}} {{Z|2017}} {{Z|2018}} {{Z|2019}} {{Z|2020}} {{Z|2021}} {{Z|2022}} {{Z|2023}} {{Z|2024}} {{Z|2025}} {{Z|2026}} {{Z|2027}} {{Z|2028}} {{Z|2029}} {{Z|2030}} {{Z|2031}} {{Z|2032}} {{Z|2033}} {{Z|2034}} {{Z|2035}} {{Z|2036}} {{Z|2037}} {{Z|2038}} {{Z|2039}} {{Z|2040}} {{Z|2041}} {{Z|2042}} {{Z|2043}} {{Z|2044}} {{Z|2045}} {{Z|2046}} {{Z|2047}} {{Z|2048}} {{Z|2049}} {{Z|2050}} {{Z|2051}} {{Z|2052}} {{Z|2053}} {{Z|2054}} {{Z|2055}} {{Z|2056}} {{Z|2057}} {{Z|2058}} {{Z|2059}} {{Z|2060}} {{Z|2061}} {{Z|2062}} {{Z|2063}} {{Z|2064}} {{Z|2065}} {{Z|2066}} {{Z|2067}} {{Z|2068}} {{Z|2069}} {{Z|2070}} {{Z|2071}} {{Z|2072}} {{Z|2073}} {{Z|2074}} {{Z|2075}} {{Z|2076}} {{Z|2077}} {{Z|2078}} {{Z|2079}} {{Z|2080}} {{Z|2081}} {{Z|2082}} {{Z|2083}} {{Z|2084}} {{Z|2085}} {{Z|2086}} {{Z|2087}} {{Z|2088}} {{Z|2089}} {{Z|2090}} {{Z|2091}} {{Z|2092}} {{Z|2093}} {{Z|2094}} {{Z|2095}} {{Z|2096}} {{Z|2097}} {{Z|2098}} {{Z|2099}} == Z2100 → Z2199 == {{Z|2100}} {{Z|2101}} {{Z|2102}} {{Z|2103}} {{Z|2104}} {{Z|2105}} {{Z|2106}} {{Z|2107}} {{Z|2108}} {{Z|2109}} {{Z|2110}} {{Z|2111}} {{Z|2112}} {{Z|2113}} {{Z|2114}} {{Z|2115}} {{Z|2116}} {{Z|2117}} {{Z|2118}} {{Z|2119}} {{Z|2120}} {{Z|2121}} {{Z|2122}} {{Z|2123}} {{Z|2124}} {{Z|2125}} {{Z|2126}} {{Z|2127}} {{Z|2128}} {{Z|2129}} {{Z|2130}} {{Z|2131}} {{Z|2132}} {{Z|2133}} {{Z|2134}} {{Z|2135}} {{Z|2136}} {{Z|2137}} {{Z|2138}} {{Z|2139}} {{Z|2140}} {{Z|2141}} {{Z|2142}} {{Z|2143}} {{Z|2144}} {{Z|2145}} {{Z|2146}} {{Z|2147}} {{Z|2148}} {{Z|2149}} {{Z|2150}} {{Z|2151}} {{Z|2152}} {{Z|2153}} {{Z|2154}} {{Z|2155}} {{Z|2156}} {{Z|2157}} {{Z|2158}} {{Z|2159}} {{Z|2160}} {{Z|2161}} {{Z|2162}} {{Z|2163}} {{Z|2164}} {{Z|2165}} {{Z|2166}} {{Z|2167}} {{Z|2168}} {{Z|2169}} {{Z|2170}} {{Z|2171}} {{Z|2172}} {{Z|2173}} {{Z|2174}} {{Z|2175}} {{Z|2176}} {{Z|2177}} {{Z|2178}} {{Z|2179}} {{Z|2180}} {{Z|2181}} {{Z|2182}} {{Z|2183}} {{Z|2184}} {{Z|2185}} {{Z|2186}} {{Z|2187}} {{Z|2188}} {{Z|2189}} {{Z|2190}} {{Z|2191}} {{Z|2192}} {{Z|2193}} {{Z|2194}} {{Z|2195}} {{Z|2196}} {{Z|2197}} {{Z|2198}} {{Z|2199}} == Z2200 → Z2299 == {{Z|2200}} {{Z|2201}} {{Z|2202}} {{Z|2203}} {{Z|2204}} {{Z|2205}} {{Z|2206}} {{Z|2207}} {{Z|2208}} {{Z|2209}} {{Z|2210}} {{Z|2211}} {{Z|2212}} {{Z|2213}} {{Z|2214}} {{Z|2215}} {{Z|2216}} {{Z|2217}} {{Z|2218}} {{Z|2219}} {{Z|2220}} {{Z|2221}} {{Z|2222}} {{Z|2223}} {{Z|2224}} {{Z|2225}} {{Z|2226}} {{Z|2227}} {{Z|2228}} {{Z|2229}} {{Z|2230}} {{Z|2231}} {{Z|2232}} {{Z|2233}} {{Z|2234}} {{Z|2235}} {{Z|2236}} {{Z|2237}} {{Z|2238}} {{Z|2239}} {{Z|2240}} {{Z|2241}} {{Z|2242}} {{Z|2243}} {{Z|2244}} {{Z|2245}} {{Z|2246}} {{Z|2247}} {{Z|2248}} {{Z|2249}} {{Z|2240}} {{Z|2250}} {{Z|2251}} {{Z|2252}} {{Z|2253}} {{Z|2254}} {{Z|2255}} {{Z|2256}} {{Z|2257}} {{Z|2258}} {{Z|2259}} {{Z|2260}} {{Z|2261}} {{Z|2262}} {{Z|2263}} {{Z|2264}} {{Z|2265}} {{Z|2266}} {{Z|2267}} {{Z|2268}} {{Z|2269}} {{Z|2270}} {{Z|2271}} {{Z|2272}} {{Z|2273}} {{Z|2274}} {{Z|2275}} {{Z|2276}} {{Z|2277}} {{Z|2278}} {{Z|2279}} {{Z|2280}} {{Z|2281}} {{Z|2282}} {{Z|2283}} {{Z|2284}} {{Z|2285}} {{Z|2286}} {{Z|2287}} {{Z|2288}} {{Z|2289}} {{Z|2290}} {{Z|2291}} {{Z|2292}} {{Z|2293}} {{Z|2294}} {{Z|2295}} {{Z|2296}} {{Z|2297}} {{Z|2298}} {{Z|2299}} == Z2300 → Z2399 == {{Z|2300}} {{Z|2301}} {{Z|2302}} {{Z|2303}} {{Z|2304}} {{Z|2305}} {{Z|2306}} {{Z|2307}} {{Z|2308}} {{Z|2309}} {{Z|2310}} {{Z|2311}} {{Z|2312}} {{Z|2313}} {{Z|2314}} {{Z|2315}} {{Z|2316}} {{Z|2317}} {{Z|2318}} {{Z|2319}} {{Z|2320}} {{Z|2321}} {{Z|2322}} {{Z|2323}} {{Z|2324}} {{Z|2325}} {{Z|2326}} {{Z|2327}} {{Z|2328}} {{Z|2329}} {{Z|2330}} {{Z|2331}} {{Z|2332}} {{Z|2333}} {{Z|2334}} {{Z|2335}} {{Z|2336}} {{Z|2337}} {{Z|2338}} {{Z|2339}} {{Z|2340}} {{Z|2341}} {{Z|2342}} {{Z|2343}} {{Z|2344}} {{Z|2345}} {{Z|2346}} {{Z|2347}} {{Z|2348}} {{Z|2349}} {{Z|2350}} {{Z|2351}} {{Z|2352}} {{Z|2353}} {{Z|2354}} {{Z|2355}} {{Z|2356}} {{Z|2357}} {{Z|2358}} {{Z|2359}} {{Z|2360}} {{Z|2361}} {{Z|2362}} {{Z|2363}} {{Z|2364}} {{Z|2365}} {{Z|2366}} {{Z|2367}} {{Z|2368}} {{Z|2369}} {{Z|2370}} {{Z|2371}} {{Z|2372}} {{Z|2373}} {{Z|2374}} {{Z|2375}} {{Z|2376}} {{Z|2377}} {{Z|2378}} {{Z|2379}} {{Z|2380}} {{Z|2381}} {{Z|2382}} {{Z|2383}} {{Z|2384}} {{Z|2385}} {{Z|2386}} {{Z|2387}} {{Z|2388}} {{Z|2389}} {{Z|2390}} {{Z|2391}} {{Z|2392}} {{Z|2393}} {{Z|2394}} {{Z|2395}} {{Z|2396}} {{Z|2397}} {{Z|2398}} {{Z|2399}} == Z2400 → Z2499 == {{Z|2400}} {{Z|2401}} {{Z|2402}} {{Z|2403}} {{Z|2404}} {{Z|2405}} {{Z|2406}} {{Z|2407}} {{Z|2408}} {{Z|2409}} {{Z|2410}} {{Z|2411}} {{Z|2412}} {{Z|2413}} {{Z|2414}} {{Z|2415}} {{Z|2416}} {{Z|2417}} {{Z|2418}} {{Z|2419}} {{Z|2420}} {{Z|2421}} {{Z|2422}} {{Z|2423}} {{Z|2424}} {{Z|2425}} {{Z|2426}} {{Z|2427}} {{Z|2428}} {{Z|2429}} {{Z|2430}} {{Z|2431}} {{Z|2432}} {{Z|2433}} {{Z|2434}} {{Z|2435}} {{Z|2436}} {{Z|2437}} {{Z|2438}} {{Z|2439}} {{Z|2440}} {{Z|2441}} {{Z|2442}} {{Z|2443}} {{Z|2444}} {{Z|2445}} {{Z|2446}} {{Z|2447}} {{Z|2448}} {{Z|2449}} {{Z|2450}} {{Z|2451}} {{Z|2452}} {{Z|2453}} {{Z|2454}} {{Z|2455}} {{Z|2456}} {{Z|2457}} {{Z|2458}} {{Z|2459}} {{Z|2460}} {{Z|2461}} {{Z|2462}} {{Z|2463}} {{Z|2464}} {{Z|2465}} {{Z|2466}} {{Z|2467}} {{Z|2468}} {{Z|2469}} {{Z|2470}} {{Z|2471}} {{Z|2472}} {{Z|2473}} {{Z|2474}} {{Z|2475}} {{Z|2476}} {{Z|2477}} {{Z|2478}} {{Z|2479}} {{Z|2480}} {{Z|2481}} {{Z|2482}} {{Z|2483}} {{Z|2484}} {{Z|2485}} {{Z|2486}} {{Z|2487}} {{Z|2488}} {{Z|2489}} {{Z|2490}} {{Z|2491}} {{Z|2492}} {{Z|2493}} {{Z|2494}} {{Z|2495}} {{Z|2496}} {{Z|2497}} {{Z|2498}} {{Z|2499}} == Z2500 → Z2599 == {{Z|2500}} {{Z|2501}} {{Z|2502}} {{Z|2503}} {{Z|2504}} {{Z|2505}} {{Z|2506}} {{Z|2507}} {{Z|2508}} {{Z|2509}} {{Z|2510}} {{Z|2511}} {{Z|2512}} {{Z|2513}} {{Z|2514}} {{Z|2515}} {{Z|2516}} {{Z|2517}} {{Z|2518}} {{Z|2519}} {{Z|2520}} {{Z|2521}} {{Z|2522}} {{Z|2523}} {{Z|2524}} {{Z|2525}} {{Z|2526}} {{Z|2527}} {{Z|2528}} {{Z|2529}} {{Z|2530}} {{Z|2531}} {{Z|2532}} {{Z|2533}} {{Z|2534}} {{Z|2535}} {{Z|2536}} {{Z|2537}} {{Z|2538}} {{Z|2539}} {{Z|2540}} {{Z|2541}} {{Z|2542}} {{Z|2543}} {{Z|2544}} {{Z|2545}} {{Z|2546}} {{Z|2547}} {{Z|2548}} {{Z|2549}} {{Z|2550}} {{Z|2551}} {{Z|2552}} {{Z|2553}} {{Z|2554}} {{Z|2555}} {{Z|2556}} {{Z|2557}} {{Z|2558}} {{Z|2559}} {{Z|2560}} {{Z|2561}} {{Z|2562}} {{Z|2563}} {{Z|2564}} {{Z|2565}} {{Z|2566}} {{Z|2567}} {{Z|2568}} {{Z|2569}} {{Z|2570}} {{Z|2571}} {{Z|2572}} {{Z|2573}} {{Z|2574}} {{Z|2575}} {{Z|2576}} {{Z|2577}} {{Z|2578}} {{Z|2579}} {{Z|2580}} {{Z|2581}} {{Z|2582}} {{Z|2583}} {{Z|2584}} {{Z|2585}} {{Z|2586}} {{Z|2587}} {{Z|2588}} {{Z|2589}} {{Z|2590}} {{Z|2591}} {{Z|2592}} {{Z|2593}} {{Z|2594}} {{Z|2595}} {{Z|2596}} {{Z|2597}} {{Z|2598}} {{Z|2599}} == Z2600 → Z2699 == {{Z|2600}} {{Z|2601}} {{Z|2602}} {{Z|2603}} {{Z|2604}} {{Z|2605}} {{Z|2606}} {{Z|2607}} {{Z|2608}} {{Z|2609}} {{Z|2610}} {{Z|2611}} {{Z|2612}} {{Z|2613}} {{Z|2614}} {{Z|2615}} {{Z|2616}} {{Z|2617}} {{Z|2618}} {{Z|2619}} {{Z|2620}} {{Z|2621}} {{Z|2622}} {{Z|2623}} {{Z|2624}} {{Z|2625}} {{Z|2626}} {{Z|2627}} {{Z|2628}} {{Z|2629}} {{Z|2630}} {{Z|2631}} {{Z|2632}} {{Z|2633}} {{Z|2634}} {{Z|2635}} {{Z|2636}} {{Z|2637}} {{Z|2638}} {{Z|2639}} {{Z|2640}} {{Z|2641}} {{Z|2642}} {{Z|2643}} {{Z|2644}} {{Z|2645}} {{Z|2646}} {{Z|2647}} {{Z|2648}} {{Z|2649}} {{Z|2650}} {{Z|2651}} {{Z|2652}} {{Z|2653}} {{Z|2654}} {{Z|2655}} {{Z|2656}} {{Z|2657}} {{Z|2658}} {{Z|2659}} {{Z|2660}} {{Z|2661}} {{Z|2662}} {{Z|2663}} {{Z|2664}} {{Z|2665}} {{Z|2666}} {{Z|2667}} {{Z|2668}} {{Z|2669}} {{Z|2670}} {{Z|2671}} {{Z|2672}} {{Z|2673}} {{Z|2674}} {{Z|2675}} {{Z|2676}} {{Z|2677}} {{Z|2678}} {{Z|2679}} {{Z|2680}} {{Z|2681}} {{Z|2682}} {{Z|2683}} {{Z|2684}} {{Z|2685}} {{Z|2686}} {{Z|2687}} {{Z|2688}} {{Z|2689}} {{Z|2690}} {{Z|2691}} {{Z|2692}} {{Z|2693}} {{Z|2694}} {{Z|2695}} {{Z|2696}} {{Z|2697}} {{Z|2698}} {{Z|2699}} == Z2700 → Z2799 == {{Z|2700}} {{Z|2701}} {{Z|2702}} {{Z|2703}} {{Z|2704}} {{Z|2705}} {{Z|2706}} {{Z|2707}} {{Z|2708}} {{Z|2709}} {{Z|2710}} {{Z|2711}} {{Z|2712}} {{Z|2713}} {{Z|2714}} {{Z|2715}} {{Z|2716}} {{Z|2717}} {{Z|2718}} {{Z|2719}} {{Z|2720}} {{Z|2721}} {{Z|2722}} {{Z|2723}} {{Z|2724}} {{Z|2725}} {{Z|2726}} {{Z|2727}} {{Z|2728}} {{Z|2729}} {{Z|2730}} {{Z|2731}} {{Z|2732}} {{Z|2733}} {{Z|2734}} {{Z|2735}} {{Z|2736}} {{Z|2737}} {{Z|2738}} {{Z|2739}} {{Z|2740}} {{Z|2741}} {{Z|2742}} {{Z|2743}} {{Z|2744}} {{Z|2745}} {{Z|2746}} {{Z|2747}} {{Z|2748}} {{Z|2749}} {{Z|2750}} {{Z|2751}} {{Z|2752}} {{Z|2753}} {{Z|2754}} {{Z|2755}} {{Z|2756}} {{Z|2757}} {{Z|2758}} {{Z|2759}} {{Z|2760}} {{Z|2761}} {{Z|2762}} {{Z|2763}} {{Z|2764}} {{Z|2765}} {{Z|2766}} {{Z|2767}} {{Z|2768}} {{Z|2769}} {{Z|2770}} {{Z|2771}} {{Z|2772}} {{Z|2773}} {{Z|2774}} {{Z|2775}} {{Z|2776}} {{Z|2777}} {{Z|2778}} {{Z|2779}} {{Z|2780}} {{Z|2781}} {{Z|2782}} {{Z|2783}} {{Z|2784}} {{Z|2785}} {{Z|2786}} {{Z|2787}} {{Z|2788}} {{Z|2789}} {{Z|2790}} {{Z|2791}} {{Z|2792}} {{Z|2793}} {{Z|2794}} {{Z|2795}} {{Z|2796}} {{Z|2797}} {{Z|2798}} {{Z|2799}} == Z2800 → Z2899 == {{Z|2800}} {{Z|2801}} {{Z|2802}} {{Z|2803}} {{Z|2804}} {{Z|2805}} {{Z|2806}} {{Z|2807}} {{Z|2808}} {{Z|2809}} {{Z|2810}} {{Z|2811}} {{Z|2812}} {{Z|2813}} {{Z|2814}} {{Z|2815}} {{Z|2816}} {{Z|2817}} {{Z|2818}} {{Z|2819}} {{Z|2820}} {{Z|2821}} {{Z|2822}} {{Z|2823}} {{Z|2824}} {{Z|2825}} {{Z|2826}} {{Z|2827}} {{Z|2828}} {{Z|2829}} {{Z|2830}} {{Z|2831}} {{Z|2832}} {{Z|2833}} {{Z|2834}} {{Z|2835}} {{Z|2836}} {{Z|2837}} {{Z|2838}} {{Z|2839}} {{Z|2840}} {{Z|2841}} {{Z|2842}} {{Z|2843}} {{Z|2844}} {{Z|2845}} {{Z|2846}} {{Z|2847}} {{Z|2848}} {{Z|2849}} {{Z|2850}} {{Z|2851}} {{Z|2852}} {{Z|2853}} {{Z|2854}} {{Z|2855}} {{Z|2856}} {{Z|2857}} {{Z|2858}} {{Z|2859}} {{Z|2860}} {{Z|2861}} {{Z|2862}} {{Z|2863}} {{Z|2864}} {{Z|2865}} {{Z|2866}} {{Z|2867}} {{Z|2868}} {{Z|2869}} {{Z|2870}} {{Z|2871}} {{Z|2872}} {{Z|2873}} {{Z|2874}} {{Z|2875}} {{Z|2876}} {{Z|2877}} {{Z|2878}} {{Z|2879}} {{Z|2880}} {{Z|2881}} {{Z|2882}} {{Z|2883}} {{Z|2884}} {{Z|2885}} {{Z|2886}} {{Z|2887}} {{Z|2888}} {{Z|2889}} {{Z|2890}} {{Z|2891}} {{Z|2892}} {{Z|2893}} {{Z|2894}} {{Z|2895}} {{Z|2896}} {{Z|2897}} {{Z|2898}} {{Z|2899}} == Z2900 → Z2999 == {{Z|2900}} {{Z|2901}} {{Z|2902}} {{Z|2903}} {{Z|2904}} {{Z|2905}} {{Z|2906}} {{Z|2907}} {{Z|2908}} {{Z|2909}} {{Z|2910}} {{Z|2911}} {{Z|2912}} {{Z|2913}} {{Z|2914}} {{Z|2915}} {{Z|2916}} {{Z|2917}} {{Z|2918}} {{Z|2919}} {{Z|2920}} {{Z|2921}} {{Z|2922}} {{Z|2923}} {{Z|2924}} {{Z|2925}} {{Z|2926}} {{Z|2927}} {{Z|2928}} {{Z|2929}} {{Z|2930}} {{Z|2931}} {{Z|2932}} {{Z|2933}} {{Z|2934}} {{Z|2935}} {{Z|2936}} {{Z|2937}} {{Z|2938}} {{Z|2939}} {{Z|2940}} {{Z|2941}} {{Z|2942}} {{Z|2943}} {{Z|2944}} {{Z|2945}} {{Z|2946}} {{Z|2947}} {{Z|2948}} {{Z|2949}} {{Z|2950}} {{Z|2951}} {{Z|2952}} {{Z|2953}} {{Z|2954}} {{Z|2955}} {{Z|2956}} {{Z|2957}} {{Z|2958}} {{Z|2959}} {{Z|2960}} {{Z|2961}} {{Z|2962}} {{Z|2963}} {{Z|2964}} {{Z|2965}} {{Z|2966}} {{Z|2967}} {{Z|2968}} {{Z|2969}} {{Z|2970}} {{Z|2971}} {{Z|2972}} {{Z|2973}} {{Z|2974}} {{Z|2975}} {{Z|2976}} {{Z|2977}} {{Z|2978}} {{Z|2979}} {{Z|2980}} {{Z|2981}} {{Z|2982}} {{Z|2983}} {{Z|2984}} {{Z|2985}} {{Z|2986}} {{Z|2987}} {{Z|2988}} {{Z|2989}} {{Z|2990}} {{Z|2991}} {{Z|2992}} {{Z|2993}} {{Z|2994}} {{Z|2995}} {{Z|2996}} {{Z|2997}} {{Z|2998}} {{Z|2999}} 9psxzosn2x7iecpyilv7at68771rdy0 0 83681 275740 2026-05-17T10:13:28Z Sun8908 9804 275740 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35259" }, "Z2K2": { "Z1K1": "Z14", "Z14K1": "Z34212", "Z14K3": { "Z1K1": "Z16", "Z16K1": "Z610", "Z16K2": "def Z34212(Z34212K1):\n\timport unicodedata\n\timport re\n\t\n\tnormalized = unicodedata.normalize('NFD', Z34212K1)\n\tlist_pinyin = re.split(r\"['\\s\\-]+\", normalized)\n\t\n\tVOWEL_BASES = \"AaEeIiOoUu\"\n\tVOWEL_PATTERN = rf\"[{VOWEL_BASES}][\\u0300-\\u036f]*\"\n\tsingle_char_pattern = (rf\"([BbCcDdGgHhJjKkLlMmNnPpQqRrSsTtWwXxYyZz]{{0,2}}(?:{VOWEL_PATTERN})+)(n(?![{VOWEL_BASES}]))?(g(?![{VOWEL_BASES}]))?(r(?![{VOWEL_BASES}]))?\")\n\t\n\t\t\n\tlist_single_char_pinyin = []\n\tfor py in list_pinyin:\n\t\tmatches = re.finditer(single_char_pattern, py)\n\t\tfor m in matches:\n\t\t\tsyl = m.group(0)\n\t\t\tif syl:\n\t\t\t\tclean_syl = unicodedata.normalize('NFC', syl)\n\t\t\t\tlist_single_char_pinyin.append(clean_syl)\n\t\n\treturn list_single_char_pinyin" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "pinyin to list of single pinyin,python unicodedata" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31", { "Z1K1": "Z31", "Z31K1": "Z1002", "Z31K2": [ "Z6", "pinyin to list of single character pinyin, python unicodedata" ] } ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } ktvodkhj9l4fmx4m5whw9vrs8zbgv3d 0 83682 275745 2026-05-17T10:17:04Z Sun8908 9804 275745 zobject text/plain { "Z1K1": "Z2", "Z2K1": { "Z1K1": "Z6", "Z6K1": "Z35260" }, "Z2K2": { "Z1K1": "Z20", "Z20K1": "Z34212", "Z20K2": { "Z1K1": "Z7", "Z7K1": "Z34212", "Z34212K1": "xùnǚ" }, "Z20K3": { "Z1K1": "Z7", "Z7K1": "Z889", "Z889K2": [ "Z6", "xù", "nǚ" ], "Z889K3": "Z866" } }, "Z2K3": { "Z1K1": "Z12", "Z12K1": [ "Z11", { "Z1K1": "Z11", "Z11K1": "Z1002", "Z11K2": "xùnǚ to [\"xù\",\"nǚ\"]" } ] }, "Z2K4": { "Z1K1": "Z32", "Z32K1": [ "Z31" ] }, "Z2K5": { "Z1K1": "Z12", "Z12K1": [ "Z11" ] } } d2eg4g7ke1uxyqzhoqgepwi5kv6xg0i