Using ja-def plus ja-see edit

Hello, Fish bowl. You commented at おかま, "using {ja-def} affects the display on the relevant page (オカマ) and (thus?) is the right way to do this as i understand it". That doesn't seem right to me, though. If you look at オカマ you will see the katakana bolded (because it is transcluding itself?) and all of the other senses there without boldface katakana. If you look at お釜, neither of the katakana senses with ja-def appear at all. These do not seem like desired outcomes, do they? Cnilep (talk) 00:53, 12 September 2023 (UTC)Reply

@Cnilep: Oh, hm. That's what I expected on お釜, but on オカマ I expected the opposite where only the marked senses would appear. I guess it only works when all senses have {{ja-def}} (as on 沸く)? —Fish bowl (talk) 01:00, 12 September 2023 (UTC)Reply

Surprised and Astonished edit

Even after being such an experienced and great editor, you are still not an administrator! Shall i vote for you कालमैत्री (talk) 05:00, 23 October 2023 (UTC)Reply

:3c —Fish bowl (talk) 21:28, 23 October 2023 (UTC)Reply
? कालमैत्री (talk) 02:58, 24 October 2023 (UTC) :(Reply
It is because this guy hates Dubeolsik–QWERTY, the best Korean romanization system of the world. 118.68.238.167 20:14, 25 October 2023 (UTC)Reply
nice to hear from ya babe, get a better hobby instead of thinking about me <3 —Fish bowl (talk) 20:21, 25 October 2023 (UTC)Reply

Kyoto and Kagoshima edit

Are you able to program Kyoto and Kagoshima accent pattern into Module:ja-pron? I have extracted the Kagoshima and Kyoto accent patterns from Zenkoku Akusento Jiten:

Kagoshima accent is divided into two groups: A and B (ordered by syllable count; also the dashes followed by accent is a particle)

A class accent (the only accented mora is on the penultimate mora):

  • 1. F-L
  • 2. HL-L
  • 3. LHL-L
  • 4. LLHL-L
  • B class accent (the only accented mora is on the final mora):
  • 1. H-L
  • 2. LH-L
  • 3. LLH-L
  • 4. LLLH-L

There are no Kyoto monosyllables. All monosyllables in the standard Japanese lengthen into disyllables in Kyoto.

The accent is even more complex for Kyoto; there are accent patterns that differ with and without a particle.

Kyoto disyllables:

  • 0. HH-H
  • 1. LH ~ LL-H
  • 1:25. LF ~ LH-L
  • 2. HL-L
  • Kyoto trisyllables:
  • 0. HHH-H
  • 1. LLH ~ LLL-H
  • 1:35. LLF ~ LLH-L
  • 1:3. LHL-L
  • 3. HHL-L
  • 2. HLL-L

Quadrosyllables:

  • 0. HHHH-H
  • 1. LLLH ~ LLLL-H
  • 1:4. LLHL-L
  • 1:3. LHLL-L
  • 4. HHHL-L
  • 3. HHLL-L
  • 2. HLLL-L

Chuterix (talk) 01:00, 28 December 2023 (UTC)Reply

@Chuterix: Sorry, I don't think I have the time to work on this. —Fish bowl (talk) 02:38, 28 December 2023 (UTC)Reply
OK. Chuterix (talk) 02:38, 28 December 2023 (UTC)Reply

Sources for Chinese Dialectal Synonyms and Dialectal Pronunciation? edit

Hey! I'm wondering, where are the Chinese dialectal synonyms and pronunciation modules sourced from? Respectively they are Module:zh/data/dial-syn and Module:zh/data/dial-pron. Suspecting the latter is from zhongguoyuyan.cn, but I can't find anything online for the first one. I'd love to do some research on them. Thanks! 74.101.125.9 03:15, 31 December 2023 (UTC)Reply

Redundant / duplicate template parameters edit

Hello Fish bowl (talk). I saw that you edited my own vocab list template call and also the newly still in development marathi noun declension template and removed the duplicate (numbered and named) template parameters. But they were there for a reason to slowly and gradually switch template calls from one syntax to another. I would suggest to keep them for further data migration and to make these new templates suitable to test them first with new syntax and then use them in the old structure until everything is migrated there. Can you maybe leave them in that state for a while because I first promised to develop a Lua Module for declension and also promised to adapt the transliteration Marathi module to be suitable for two different scenarios (as a helper module for IPA transcription and on the other hand in the declination / conjugation tables for the expected ISO transliterations there). If you have some experience with these kind of tasks some help is highly welcomed, but behaviour / test expectation wise have a close contact with the natives or at least Marathi well enough knowing people who are involved there. I am still working on a test driven approach to get the expectations (from the linguistic point of view) on the modules clear. — This unsigned comment was added by Undekagon30 (talkcontribs).

@Undekagon30: Thank you for the feedback; this is why I send notifications to people during such tasks (clearing Category:Pages using duplicate arguments in template calls).
On Template:mr-decl-noun/basic/documentation: I removed those because (1) |1=test1 conflicted with |mr-decl-noun/basic (which is also |1=, but implied; hence |1=test1 should have been |2=test1, and so on), (2) because it did not match the previous actual template call, (3) because instructions to simultaneously fill in named and numbered parameters would produce redundancy, and (4) because Template:mr-decl-noun/basic does not presently have any support for numbered items; those instructions would not be effective, either.
I would suggest implementing the numbered parameters first, and then introducing them separately in the documentation, with a note that the named parameters are now obsolete (and keeping in mind that |1=test1 should have been |2=test1, or even |test1 for simplicity).
As for User:Undekagon30/vocab/Marathi 1, DirectSingular was paired with DirectPluralTR, and DirectPlural was also paired with DirectPluralTR; to resolve the duplicate argument I made the judgement to repair the first one to DirectSingularTR.
Fish bowl (talk) 22:20, 6 February 2024 (UTC)Reply

Please stop and revert your deletion of i=1 in instances of Template:taxon edit

You are wrong to rely on membership in the category without understanding what is going on. This is what I have been afraid of: uninformed use of these as cleanup categories. I can mostly blame others, but you should stop. In particular, removal of "i=1" from {{taxon}} is wrong. The parameter exists to allow italicization of parameter 3 in {{taxon}}, which is needed for taxa in kingdoms Archaea, Bacteria, and Virus. I wasn't sure that that parameter was the cause of the miscategorization, but didn't think that anyone took those categories seriously. DCDuring (talk) 02:18, 29 February 2024 (UTC)Reply
@DCDuring: As noted in the edit summary, I was undertaking maintenance work; please see the description written at Category:Pages using duplicate arguments in template calls. Namely: # {{taxon|class|phylum|{{taxlink|Mycoplasmatota|phylum}}|i=1|[[bacteria]] that lack a [[cell wall]]|i=1}}. i=1 was already there. —Fish bowl (talk) 02:21, 29 February 2024 (UTC)Reply
Yes. You are correct and thank you. I didn't see that the "i=1" was at the end of the templated content, because it has been my practice, at least lately, to put it next to the item being italicized. I appreciate being pinged when these changes are made, so that I can avoid that kind of oversight. DCDuring (talk) 02:48, 29 February 2024 (UTC)Reply
I'll make sure to keep i=1 in that position if it comes across my radar again.
I always ping during this to avoid making a bad correction; sometimes I end up pinging people multiple times in a row, so I'm relieved to hear that you appreciate it. —Fish bowl (talk) 23:09, 29 February 2024 (UTC)Reply

天和 and others edit

Just noting I added 天和, 夢天‎ and 問天‎ as Skylab, Alpha, and others was also already on the site, so hopefully it passes WT:WWIN. Kungming2 (talk) 19:56, 13 April 2024 (UTC)Reply