Wiktionary:Grease pit/2022/June: difference between revisions

From Wiktionary, the free dictionary
Jump to navigation Jump to search
Content deleted Content added
Line 152: Line 152:


{{ping|Fish bowl|RichardW57m|Theknightwho|This, that and the other|70.172.194.25}} & all: I would like to add two transliteration systems to [[Template:borrowed]] (or similar) which would "fall under" Mandarin (<code>cmn</code>): one called "<code>wg</code>" (or similar) ([[Wade-Giles]]) and one called "<code>hp</code>" (or similar) ([[Hanyu Pinyin]]). See the last three posts in [[Talk:Kuomintang]] for discussion of this issue. See the first half of the Etymology section of '[[Xizhi]]' for a potential example of what this might look like if implemented: "From the [[Hanyu Pinyin]] romanization of [[Mandarin]]{{...}}". On the Xizhi page, you would hypothetically write "From the <code><nowiki>{{bor|en|hp|-}}</nowiki></code>" and produce that text (or similar), and all the attendant categorization, etc that <code>cmn</code> would normally produce.<br>(NOTE: As can be seen from the discussion at [[Wiktionary:Grease_pit/2022/May#Transliteration_Systems_in_Etymologies]], this is a complex issue that leads into many fun questions that can be talked about endlessly around the campfire, which is EXACTLY how NOTHING got done the first time. There are complex issues that absolutely cannot be solved ahead of time. The only way forward is for "something" to be created. Once "something" is created (regardless of how ugly, stupid, wrong, un-academic, whatever), I will implement it immediately. That will get the attention of the big boys, who will want to comment. At that point, the long, meaningful discussions can lead to wonderful tweaking and modulation of the final form. But for now, please don't discuss new categories, different transliteration schemes, etc. yet. All I'd like to see is a functional system where "Hanyu Pinyin" and/or "Wade-Giles" appears automatically. God bless.) --[[User:Geographyinitiative|Geographyinitiative]] ([[User talk:Geographyinitiative|talk]]) 15:48, 20 June 2022 (UTC)
{{ping|Fish bowl|RichardW57m|Theknightwho|This, that and the other|70.172.194.25}} & all: I would like to add two transliteration systems to [[Template:borrowed]] (or similar) which would "fall under" Mandarin (<code>cmn</code>): one called "<code>wg</code>" (or similar) ([[Wade-Giles]]) and one called "<code>hp</code>" (or similar) ([[Hanyu Pinyin]]). See the last three posts in [[Talk:Kuomintang]] for discussion of this issue. See the first half of the Etymology section of '[[Xizhi]]' for a potential example of what this might look like if implemented: "From the [[Hanyu Pinyin]] romanization of [[Mandarin]]{{...}}". On the Xizhi page, you would hypothetically write "From the <code><nowiki>{{bor|en|hp|-}}</nowiki></code>" and produce that text (or similar), and all the attendant categorization, etc that <code>cmn</code> would normally produce.<br>(NOTE: As can be seen from the discussion at [[Wiktionary:Grease_pit/2022/May#Transliteration_Systems_in_Etymologies]], this is a complex issue that leads into many fun questions that can be talked about endlessly around the campfire, which is EXACTLY how NOTHING got done the first time. There are complex issues that absolutely cannot be solved ahead of time. The only way forward is for "something" to be created. Once "something" is created (regardless of how ugly, stupid, wrong, un-academic, whatever), I will implement it immediately. That will get the attention of the big boys, who will want to comment. At that point, the long, meaningful discussions can lead to wonderful tweaking and modulation of the final form. But for now, please don't discuss new categories, different transliteration schemes, etc. yet. All I'd like to see is a functional system where "Hanyu Pinyin" and/or "Wade-Giles" appears automatically. God bless.) --[[User:Geographyinitiative|Geographyinitiative]] ([[User talk:Geographyinitiative|talk]]) 15:48, 20 June 2022 (UTC)

: Just to add that I support this.

:; What needs adding based on the previous discussion
: In [[Module:etymology languages/data]]:

: <code>m["cmn-hp"] = {</code><br>
: <code> canonicalName = "Hanyu Pinyin",</code><br>
: <code> aliases = {"Pinyin"},</code><br>
: <code> parent = "cmn",</code><br>
: <code> wikidata_item = 42222,</code><br>
: <code>}</code><br>
: <code></code><br>
: <code>m["cmn-wg"] = {</code><br>
: <code> canonicalName = "Wade–Giles",</code><br>
: <code> aliases = {"Wade-Giles", "Wade Giles"},</code><br>
: <code> parent = "cmn",</code><br>
: <code> wikidata_item = 208442,</code><br>
: <code>}</code><br>

:[[User:Theknightwho|Theknightwho]] ([[User talk:Theknightwho|talk]]) 16:21, 20 June 2022 (UTC)

Revision as of 16:21, 20 June 2022


The site thinks that my edits are harmful

I'm just manually adding inflected forms, I won't harm this site --ConjugationMan (talk) 13:39, 4 June 2022 (UTC)[reply]

It stopped complaining, which is useful for me (I only edit in good faith) --ConjugationMan (talk) 14:28, 4 June 2022 (UTC)[reply]
The filter that you triggered is a safety valve: vandals tend to create new accounts, then do as much damage as possible before they're discovered and blocked. Most new editors don't edit fast enough to set this off, so it's only rarely a problem. Chuck Entz (talk) 15:23, 4 June 2022 (UTC)[reply]

Hey all- I tried to use url2 in quote-journal, and the parameter journal2= did not display (everything else worked) see: diff. Let me know if I'm doing it wrong. --Geographyinitiative (talk) 13:47, 4 June 2022 (UTC)[reply]

@Geographyinitiative As you know, Template:quote-journal takes the parameters journal and title. But under the hood, these are passed to Module:quote as title and chapter, respectively. So Module:quote doesn't know anything about the parameter journal, and as a result it doesn't look for journal2 (the code a("journal") does not appear in the module's source). As a workaround, I changed the citation to use title2 and chapter2 instead: diff. If anyone wants to edit the module code to handle this situation properly, that would be even better. 70.172.194.25 00:05, 7 June 2022 (UTC)[reply]
This workaround works; not sure if there was a theory-based rationale for not having journal2. Might be good to have it. The situation in question is the oldest known cites for the word on Wiktionary, so it does seem important/valuable to move beyond work-around level (if this holds as the oldest known usage, this is valuable cultural heritage that can ring out throughout the internet; undignified to have a work-around in it). --Geographyinitiative (talk) 00:15, 7 June 2022 (UTC)[reply]
I think the reason is that it was the easiest way to let all the quote templates customize their labels for the individual work (chapter) and containing work (title). For example:
Anyway, the displayed "workaround" output is exactly as it should be; only the parameter names are different. 70.172.194.25 00:39, 7 June 2022 (UTC)[reply]

How about a Finnish impersonal verb conjugation template?

I've already made one myself, as a subpage of my userpage. (It's here.) The template has full conjugation for the finite verb forms, and automatically adds transcluding pages into the impersonal verb category.

Here is an example of the template: [Redacted]

Let me know what y'all think! :) --ConjugationMan (talk) 14:45, 4 June 2022 (UTC)[reply]

I think this can be automated with a Lua module, but other than that it's a sound idea. I don't know whether we should have it in all entries that have monopersonal meanings, even if they also have personal ones (like pelottaa), or only to entries that solely have monopersonal meanings (like täytyä). — SURJECTION / T / C / L / 20:03, 4 June 2022 (UTC)[reply]
Another issue is that sometimes the "subject" is in genitive case (täytyä), other times in partitive (pelottaa), sometimes even in other cases (adessive case for olla (to have))... — SURJECTION / T / C / L / 21:01, 4 June 2022 (UTC)[reply]
@ConjugationMan: I commented out your template because its module invocation returns nothing but an error. Feel free to restore it when you have the module working. Chuck Entz (talk) 20:29, 5 June 2022 (UTC)[reply]

Ostensibly Lua-Free Declension Tables with Omissions

My preferred way of producing inflection tables is to add manual overrides to a Lua module that generates a regular inflection table. However, the Indian Indic community seems to prefer 'simple' templates that use nothing more(?) complicated than the parser extensions. @AryamanA, Svartava, Kutchkutch, Bhagadatta. To that end I have modified {{pmh-decl-noun-irregular}} to {{psu-decl-noun-irregular}} to have the following features:

  1. When the output table is displayed when viewing the template page, the contents of each cell is displayed in a form such as {{{7}}}.
  2. When a value is specified for a cell, it is displayed using {{l-self}}, as is common practice in inflection tables.
  3. If no value is specified for a cell, it is displayed as an em dash. The nature of Prakrit (e.g. the absence of dative plurals) and the incompleteness(!) of the attestation may lead to gaps in the table.

I'm wondering if I have missed some tricks in my coding. If so, could someone please advise me what they are? I do want the code to be maintainable by others.

I have lengthy coding for a single cell such as:

|{{#if:{{{7|<noinclude>f</noinclude>}}}|{{l-self|inc-pra|{{{7}}}}}|—}}

This may make it difficult to elaborate the display, e.g. to better display alternative forms. Currently I would use for a parameter something like |7=पुत्तण ''or '' पुत्तणं, which yields:

Lua error in Module:parameters at line 360: Parameter 1 should be a valid language or etymology language code; the value "inc-pra" is not valid. See WT:LOL and WT:LOL/E.

That's not the best of formats, neither for display nor for input. (I feel a kinder input would be |inss1=पुत्तण|inss2=पुत्तणं.)

Is there some way of abbreviating <noinclude>f</noinclude>? --RichardW57 (talk) 20:44, 5 June 2022 (UTC)[reply]

Lua memory errors again

@Surjection, Chuck Entz, Erutuon Suddenly we are back to the old situation with 26 pages with memory errors. What happened? Something must have changed around May 30 or May 31, when I first saw this. It was not a change I made. Maybe someone added a bunch more languages? I was able to eliminate the memory errors on maybe 8 pages using {{multitrans}}, but the remainder can't be fixed this way. Maybe we should resurrect the old ideas of splitting some of the Module:languages/data3 submodules, and/or implementing a generalization of {{multitrans}} that handles {{l}}, {{m}}, {{head}} and other common templates. Benwing2 (talk) 23:12, 5 June 2022 (UTC)[reply]

@Benwing2 This really started earlier: I first noticed it May 23, when there were suddenly 17 entries in CAT:E. @Surjection managed to clear those, but now they're back- with a few friends. When I looked at the transclusion list for bar on the 23rd, the there were only a few modules with changes in the previous few days. We can ignore your edit to a French module because it's not transcluded in the Chinese-character entries, and @Fish bowl also edited one of the CJK modules, but it didn't seem like the kind of thing that would radically change memory usage. There were substantial additions to Module:zh/data/st and Module:zh/data/ts- substantial, percentagewise, but those modules are still only about 90k in file size. I don't know if that would make a difference if multiplied by the number of transclusions in the Chinese-character entries (every link in the Chinese entry seems to use them). I asked @Justinrleung and he saw nothing wrong with them.
I can't use the "what changed" technique anymore because Surjection went through a lot of the Chinese modules on May 27 and worked on memory-related aspects of the code. It wouldn't hurt to check whether there were any problems with those edits, just to be safe, but I have no reason to believe they did anything but help.
I should mention that right now we're going through a minor wave of false positives that clear with a null edit, so I think someone made and quickly corrected an error in some widely-transcluded module. There's still a core of 28 memory errors once those are cleared.
As for your suggestions: such techniques are hard to apply to the Chinese-character entries due to the sheer number of data modules transcluded, and the other entries have dozens of language sections that link to almost everything at least once. Beyond that, this is all over my head. Chuck Entz (talk) 14:33, 6 June 2022 (UTC)[reply]

I think that copying over Module:cmn-pron/sandbox to Module:cmn-pron would help as a stopgap measure, saving about 1,500,000 bytes per invocation of {{zh-pron}}. (I divided Module:zh/data/cmn-hom into /1, ... /4 subpages. I figure nobody minds this much, probably, as long as it works.). 70.172.194.25 01:57, 7 June 2022 (UTC)[reply]

@Chuck Entz I made a suggestion awhile ago to compress some of the Chinese data modules into one big string rather than a bunch of tables, and index into the string appropriately. I think this would make a big difference for the bigger data modules but requires some effort. Let me try the IP's suggestion and see what happens. Benwing2 (talk) 02:29, 7 June 2022 (UTC)[reply]
OK, I went ahead and did that. It seems to have helped on "rì" but not on "xīn" or "wǒ". Benwing2 (talk) 02:37, 7 June 2022 (UTC)[reply]
After some null edits and assorted minor tinkering (also reverting to fix one caused by a rather strange misuse of {{ja-pos}}), we're down to 4 entries as opposed to 28 as of my last post. I would say that's a definite improvement. Even those 4 now get all the way to the bottom of the page before they run out of memory. Chuck Entz (talk) 04:07, 7 June 2022 (UTC)[reply]

Translations of staticity

https://www.greek-language.gr/greekLang/modern_greek/tools/corpora/corpora/search.html?lq=%CF%83%CF%84%CE%B1%CF%84%CE%B9%CE%BA%CF%8C%CF%84%CE%B7%CF%84%CE%B1

Quotations from Anthologies and Samplers

When I started adding Pali quotations to Wiktionary, I thought the details in {{quote-web}} were to help others find the quotation. Consequently, when quoting what, for my purposes, are anthologies, it looked as though the author of the anthology were the the author of the quotation. I am now trying to fix this problem. I have a few problems, though.

1) Is there an alternative to triggering of |location2=. That doesn't really feel suitable for web documents, though it doesn't look too bad in ᨷᩤᨭᩥᨾᩮᩣᨠ᩠ᨡ (pāṭimokkha), which uses quotation template {{RQ:pi:N3207}}. What is a problem is the word 'republished as'. If the new work is an anthology, it may neither republish the whole work nor essential consist of it. The simplest catch-all replacement I can think of is '(partly) republished in'.

2) The author keywords for the anthology only allow for one author, though they do allow for an author link.

3) Is the date of a work the date it was composed, first written down, or when the spelling was decided? A concrete example I have in mind is a single sutta composed in India, first written down in Sri Lanka a few generations later, and typeset in Burma (or just possibly Thailand) over a millennium and a half later, when glyph choices (subsequently confirmed as character choices) that didn't exist a thousand years earlier had to be made, and a picture of the printed text then published in a book, possibly a few decades later. --RichardW57m (talk) 11:57, 10 June 2022 (UTC)[reply]

HotCat Wiktionary fork testing

There have long been plans to fork HotCat to better support English Wiktionary templates (such as {{C}}). I've now started work on such a fork and would like more testers to check whether the changes are working correctly. Automatic saving is disabled to let users review markup and such changes which is important for ensuring the gadget works correctly. Once sufficiently tested, the en.wiktionary gadget will be migrated over.

To test this version of HotCat, first go to Special:Preferences, Gadgets and disable HotCat. Then go to your common.js and add importScript("User:Surjection/HotCat.js"); into your list of imports. If you do not have a common.js, it should be enough to place that line on the page and nothing else. (To revert, remove the line from your common.js, possibly leaving it empty, and then re-enable HotCat from Gadgets under your preferences.) — SURJECTION / T / C / L / 12:44, 11 June 2022 (UTC)[reply]

Having tested it on many different kinds of pages (with many/singular L2's) and adding either singular or multiple categories, it works as expected. Vininn126 (talk) 11:53, 12 June 2022 (UTC)[reply]
@Surjection Thank you for this. It looks like your version uses {{C}} and {{cln}}, which is also what my templatize_categories.py script standardizes on; this is good. You should add a couple more aliases to the list of topical category templates; the full list I currently have is {{C}}, {{c}}, {{top}}, {{topic}}, {{topics}} and {{catlangcode}}. It's unfortunate we have so many aliases; I would eliminate some of them but they all seem to be used on more than 1000 pages, which is usually my threshold for when a template should be kept and deprecated vs. just deleted. Maybe though we should still consider deprecating some of them, esp. {{catlangcode}}, which is long and has a non-obvious name. BTW there's a third set of category templates, which is {{categorize}}/{{cat}}; these are for categories not preceded by a language name or code, e.g. Category:Verlan; it still can be useful to write e.g. {{cat|fr|Verlan}} instead of just a raw category link so that the sort code gets generated correctly. Benwing2 (talk) 21:22, 12 June 2022 (UTC)[reply]
D'oh. I tried getting all of the aliases, but I suppose I missed some. I do know about {{categorize}}, but the issue is that it's harder to check what language those categories are for (in case one wants to add them). I think the gadget would have to fetch the category data from a Lua module, or at least in the case of Category:Verlan, fetch the category page and check which categories it belongs to. It might be doable, but I don't know if it's possible to make the logic entirely foolproof. — SURJECTION / T / C / L / 05:37, 13 June 2022 (UTC)[reply]

If we really want these, can someone update the appropriate template(s)/module(s) to get {{auto cat}} to work with this? User: The Ice Mage talk to meh 11:12, 12 June 2022 (UTC)[reply]

Whitelist the Twitter search page

It's currently not possible to link to a Twitter search (only to individual tweets) because the twitter search page is globally spam-blacklisted. Can we MediaWiki:Spam-whitelist (cf w:MediaWiki:Spam-whitelist) it? I've run into the block a few times, and it came up again at Wiktionary:Requests for verification/English#waffle_stomp. (It's possible to whitelist things for use only on specific pages, but whitelisting it for use only on WT:RFVE and WT:RFVN would mean the threads would fail to be archivable; if we could whitelist it for use on any Wiktionary: or Talk: namespaces, that should cover anywhere it'd be needed. Alternatively, generally whitelist it and use an edit filter to block new users from adding links to it if it actually becomes a problem that people spam links to it.) - -sche (discuss) 04:27, 15 June 2022 (UTC)[reply]

I don't even see how the Twitter search page is any more abusable by spammers than linking to Twitter accounts or individual Tweets. There must be something I'm missing. 98.170.164.88 04:39, 15 June 2022 (UTC)[reply]
It does seem weird that the search page is blocked, though I suppose if we were blocking particular accounts or tweets it could be used to link to them anyway via search query. - TheDaveRoss 12:12, 15 June 2022 (UTC)[reply]
I don't want to give anyone BEANS-y ideas but, my guess is that the rationale is partly, as you say, the ability to evade tweet-/account-specific blocks, and partly that if a spammer tweets a link to their malware / phishing site / whatever, either the specific site or the specific tweet can be taken down, but if they link to a twitter search for some unique string, they can create tweets linking to their sites and using that string, and whenever one tweet or site gets taken down, create another tweet. (Ah, I see it's being discussed here, prior discussion here.) - -sche (discuss) 19:29, 15 June 2022 (UTC)[reply]
(But I think we should try whitelisting it, and see if we actually get spammed or not — I doubt it, we don't seem to be getting spammed with any other links to Twitter — at which point we could add an edit filter or un-whitelist it if necessary.) - -sche (discuss) 00:09, 16 June 2022 (UTC)[reply]

Hinduphobia

i wanted to edit some details in a blank page of hinduphobia , but the automatic word recognition system of wikipedia finds some words inappropriate , ex-racist , killing , plaese review it and help Uksinghrana (talk) 00:26, 17 June 2022 (UTC)[reply]

(Looking at the AbuseLog, I see that this user added a long text to Hindu Phobia which was appropriately deleted, then got some automatic warnings for bad edits to Hinduphobia, which Fytcha appropriated reverted. I'm not seeing any edits which were actually stopped by edit filters, let alone incorrectly stopped. No objections if someone wants to just roll this whole section back.) - -sche (discuss) 20:48, 17 June 2022 (UTC)[reply]

Archives: recent on top?

Would you consider reversing the sequence of years at archives (the right hand contents) placing the more recent on top? Thank you ‑‑Sarri.greek  I 20:49, 17 June 2022 (UTC)[reply]

Templates movedto and movedfrom

I don't know why I've never noticed this, but the parameters are reversed, with |1= as the display parameter when there are two parameters. I'm not sure how many of the 528 (combined) transclusions use the second parameter, but it would be a good idea to think this through before fixing things Chuck Entz (talk) 21:12, 17 June 2022 (UTC)[reply]

Singulatives

Should {{singulative of}} add the page to a relevant category, such as Category:English singulatives (which currently holds but one entry)? This is already the case with {{clipping of}}, {{misspelling of}} and probably some other templates too. brittletheories (talk) 11:05, 19 June 2022 (UTC)[reply]

Μάγια

The entry for μάγια seems to be a bit confused; it gives only one definition, which it classes as a feminine noun meaning "spell (magic and witchcraft)". As the Greek Wiktionary makes clear, though, of the three definitions given there, the feminine singular noun is the name of a type of dance; the two definitions concerning magic, witchcraft, etc., involve μάγια as a neuter noun always used in the plural. I don't have the expertise (yet) to make the requisite changes. Could someone either make them, or help me to learn? Thanks. --Bibliosporias (talk) 16:38, 19 June 2022 (UTC)[reply]

Thank you @Bibliosporias for spotting the mistake: it is neuter (n). I can add the extra definitions as in el:μάγια: the language, and the leotard worn by dancers. ‑‑Sarri.greek  I 09:24, 20 June 2022 (UTC)[reply]
Many thanks! --Bibliosporias (talk) 09:52, 20 June 2022 (UTC)[reply]

Armenian entries that lack a pronunciation

On English Wiktionary, there are around 16K Armenian lemmas. Most of them have a pronunciation entry like գրել. It seems there's 15k such entries with a pronunciation. So at least 1K words lack a pronunciation like ակն ընդ ական. Is there a way retrieve a list of Armenian entries that lack a pronunciation? If so, I can then manually add pronunciations to the leftovers. Hovsepig (talk) 09:54, 20 June 2022 (UTC)[reply]

Here you go! Vininn126 (talk) 10:16, 20 June 2022 (UTC)[reply]

Transliteration Systems in Etymologies 2

@Fish bowl, RichardW57m, Theknightwho, This, that and the other, 70.172.194.25 & all: I would like to add two transliteration systems to Template:borrowed (or similar) which would "fall under" Mandarin (cmn): one called "wg" (or similar) (Wade-Giles) and one called "hp" (or similar) (Hanyu Pinyin). See the last three posts in Talk:Kuomintang for discussion of this issue. See the first half of the Etymology section of 'Xizhi' for a potential example of what this might look like if implemented: "From the Hanyu Pinyin romanization of Mandarin [] ". On the Xizhi page, you would hypothetically write "From the {{bor|en|hp|-}}" and produce that text (or similar), and all the attendant categorization, etc that cmn would normally produce.
(NOTE: As can be seen from the discussion at Wiktionary:Grease_pit/2022/May#Transliteration_Systems_in_Etymologies, this is a complex issue that leads into many fun questions that can be talked about endlessly around the campfire, which is EXACTLY how NOTHING got done the first time. There are complex issues that absolutely cannot be solved ahead of time. The only way forward is for "something" to be created. Once "something" is created (regardless of how ugly, stupid, wrong, un-academic, whatever), I will implement it immediately. That will get the attention of the big boys, who will want to comment. At that point, the long, meaningful discussions can lead to wonderful tweaking and modulation of the final form. But for now, please don't discuss new categories, different transliteration schemes, etc. yet. All I'd like to see is a functional system where "Hanyu Pinyin" and/or "Wade-Giles" appears automatically. God bless.) --Geographyinitiative (talk) 15:48, 20 June 2022 (UTC)[reply]

Just to add that I support this.
What needs adding based on the previous discussion
In Module:etymology languages/data:
m["cmn-hp"] = {
canonicalName = "Hanyu Pinyin",
aliases = {"Pinyin"},
parent = "cmn",
wikidata_item = 42222,
}

m["cmn-wg"] = {
canonicalName = "Wade–Giles",
aliases = {"Wade-Giles", "Wade Giles"},
parent = "cmn",
wikidata_item = 208442,
}
Theknightwho (talk) 16:21, 20 June 2022 (UTC)[reply]