User talk:YoshiRulz

Japanese plural for a rabbit is "兎" (Z24368)

Thank you for adding this test. Would it be correct to add "grammatical features" (e.g. plural (Q146786)) on wikidata:Lexeme:L1319680#F1? --99of9 (talk) 00:24, 2 May 2025 (UTC)

I'm not familiar enough with Wikidata's schema to say, but I'd imagine not. Most nouns in Japanese aren't inflected for number (enwiki). (I was considering adding another test with one of the exceptions, "友達" = "friends", but decided against it because it could be considered the informal option as opposed to "友人", and per the note on enwiki there it's also singular.) YoshiRulz (talk) 03:46, 2 May 2025 (UTC)

That's an interesting challenge. Perhaps (for Japanese at least) we should just infer that the lexeme form is allowed as a plural from the absence of an explicitly marked "singular"? Also, if the function returned ラビット, would that also be correct? --99of9 (talk) 06:32, 2 May 2025 (UTC)

For a function intended to be used in NLG you'd want it to return non-singular to cover languages like Japanese, but I've just noticed the description which says it returns the first plural form (if any), so maybe not? d:WD:Lexicographical data/Documentation/Languages/ja/modeling doesn't mention singular (Q110786) or plural (Q146786).

As for 'ラビット', I'll defer to jawiki and say that it would be understood to be an English word. YoshiRulz (talk) 20:05, 2 May 2025 (UTC)

Infoboxes

Tbanks for changing the colouring for infoboxes. If I understand correctly this work better for dark mode too. Do you by change also have a solution for aligning the box left for Arabic and other rtl languages. This is specified in Z33328 with float:right. On the internet I found float:end but I could not get that working. HenkvD (talk) 14:08, 20 July 2026 (UTC)

inline-end, per my comment here. YoshiRulz (talk) 14:14, 20 July 2026 (UTC)

Thanks that work perfect. HenkvD (talk) 12:10, 21 July 2026 (UTC)

Big thanks for composition implementations

So I'm on one of those times where I briefly return to Wikifunctions, make a function, and then leave for another long period of time. I came back to make an accumulated cyclone energy calculation function (here), and I see you have added composition implementations to my previous two functions, so I just want to give a big thanks for expanding on those. CasualCycloneTracker180897 (talk) 04:59, 23 July 2026 (UTC)

Thank you for giving me non-trivial example functions! I cleaned up and connected your new function :) YoshiRulz (talk) 10:52, 23 July 2026 (UTC)

It would seem that Wikifunctions uses an outdated version of JavaScript, and the BigInt(number) conversion doesn't work. I had to replace it with a slower count system, but I cannot edit implementations that are already connected to functions, but I have pasted the code here so that you can make the edit:

function Z38095( Z38095K1 ) {
::	let sum = 0n;
::	for (let i = 0; i < Z38095K1.length; i++) {
::		let value = 0n;
::		let count = Number(Z38095K1[i]);
::		while (count > 0) {
::			value += 5n;
::			count -= 5;
::		}
::	if (value > 34n) { sum += value ** 2n; }
::}
::return { K1: sum, K2: 10000n };
::}

Please ignore the colons in the syntax highlighting, colons are added for indentation in talk pages (unless they only show up in the source preview which would be annoying). CasualCycloneTracker180897 (talk) 14:28, 23 July 2026 (UTC)

The JS implementation is working, those test failures are cached. phab:T422300 YoshiRulz (talk) 14:58, 23 July 2026 (UTC)

unit conversions in specific value of WD

Thanks for your work on these. Although there's further to go, I can already see great progress. Sorry I can't get involved much at the moment, so feel free to take it where you think it should go, and I'll muck around with it later if I see remaining gaps/overshoots. PS are you on Telegram/IRC? It would be great to have you involved in all kinds of dynamic AW/WF discussion over there. --99of9 (talk) 01:27, 24 August 2026 (UTC)

No Telegram, and I don't feel like setting up an IRC client sorry. Too many notifications and feeds already. YoshiRulz (talk) 05:24, 24 August 2026 (UTC)

NLG default text

YoshiRulz, I would like to comment on you change on NLG default text (HTML) composition (Z36910). Thanks for changing the input to HTML. That was indeed intended. Your change to add ❌≪ and ≫❌in NOT OK, as the intention of all NLG functions it to show the default texts in purple. Adding ❌≪ and ≫❌ to the string function (and monolingual function) is an intremediate step as string cannot use HTLM text. SO please remove the ❌≪ and ≫❌ from Z36910 and its HTML tests. HenkvD (talk) 21:04, 2 September 2026 (UTC)

Does this address your concerns? YoshiRulz (talk) 21:19, 2 September 2026 (UTC)

No that was not what I meant. I reverted your changes. I hope you agree. HenkvD (talk) 07:58, 3 September 2026 (UTC)

Then I'm afraid I don't understand what the problem is with using ❌≪≫❌ in HTML. Can you create more Test cases to demonstrate, either on that Function or one of the Functions which calls it? YoshiRulz (talk) 12:30, 3 September 2026 (UTC)

The aim for default text is to indicate the text with <span lang="mul" style="color: #FF00FF;">....</span>. That is enough. But if you would upt this in a string it will be converted to HTML as <nowiki><span lang="mul" style="color: #FF00FF;">....</span>/nowiki>. That will NOT show the text in a color. Therfore we add ❌≪ and ≫❌ to stings which will be removed by NLG string to HTML fragment with span for defaults (Z37493) and change it to HTML span. HenkvD (talk) 15:57, 3 September 2026 (UTC)

Barnstar

		The Wikifunctions Barnstar
		For your tireless contributions to the fundamentals of Wikifunctions. --99of9 (talk) 12:24, 19 September 2026 (UTC)

Questions at the Project chat

I wanted you to know that I saw your comments and questions at the Project Chat, and I shared them with the team. We're a bit behind with answering your feedback, but answers will come. Thank you for your patience, and your work to make Wikifunctions better! Sannita (WMF) (talk) 16:58, 29 September 2026 (UTC)