User talk:CodeCat

Definition from Wiktionary, the free dictionary
Jump to: navigation, search
Archives: 2009-2010 · 2011 · 2012
Start a new discussion


Thread titleRepliesLast modified
Module:jdt-translit errors519:37, 27 May 2015
Reducing impact from Module:parameters problems215:36, 24 May 2015
Category:zh:Medicine in traditional script111:30, 23 May 2015
A Heads-Up112:34, 22 May 2015
Category:Malay term requests212:53, 21 May 2015
“Alternative forms are no longer categorised per a previous discussion.”222:46, 20 May 2015
Wiktionary:Beer_parlour/2015/January004:15, 20 May 2015
Appendix:Proto-Indo-European/mark-008:52, 19 May 2015
Edit on seillean has been reverted512:04, 15 May 2015
Missing plurals011:41, 15 May 2015
OHG fust < *funstiz300:02, 15 May 2015
Proto-Germanic Pronunciation Template016:39, 13 May 2015
Fixing the category201:31, 10 May 2015
Germanic nerdism123:44, 6 May 2015
Could I get you to look at this?401:58, 6 May 2015
Module:links/templates420:24, 5 May 2015
Dan Polansky's block1321:54, 3 May 2015
兒科015:45, 2 May 2015
Glosses in Templates302:54, 2 May 2015
Editing 'spiritus'113:35, 22 April 2015
First page
First page
Previous page
Previous page
Last page
Last page

What am I doing wrong here: ḩəsb?

WikiTiki8918:16, 27 May 2015

"lang" is nil.

CodeCat18:26, 27 May 2015

Ok. So what's the point of having the lang and sc arguments to the tr function if nothing is even passed to them?

WikiTiki8918:29, 27 May 2015

And what's wrong now that lang is not nil?

WikiTiki8918:32, 27 May 2015

I figured it out. Transliteration functions receive strings for lang and sc. So you need to retrieve the language and script objects first.

This really shouldn't be this way though. It was left like this because trying to change it would have broken the transliteration modules for a while until everything was updated.

CodeCat19:28, 27 May 2015

Ok thanks!

WikiTiki8919:37, 27 May 2015

Reducing impact from Module:parameters problems

There's nothing anyone can do about all the "remove_holes" module errors, but the parameter-based ones are still popping up all the time, and many are no-brainer bot fodder. These are the ones I'm seeing the most of:

  • {{l|...|lang= / {{m|...|lang= / {{label=|...|lang=
  • |}} and other empty parameters with no positional parameters following.
  • Sc= / SC=
  • |ланг=сч and other parameters with names in the wrong script (my personal favorite: |сц=Латинх ).
  • sg= instead of head=
  • pl= in {{head}} instead of plural|

Getting rid of those should lighten the load of module errors by dozens a day, and leave mostly the quick ones that just need a null edit to clear.

Chuck Entz (talk)02:54, 24 May 2015

I have been checking and fixing these during the day. But I can't do it when I'm asleep, so that's when they build up.

CodeCat11:21, 24 May 2015

No, I was talking about a preemptive bot run based on the dumps, to get them before the edit queue gets to them. These have been here for years, so we don't need to worry about the dumps being out of date. This is a parameter change, just like any number of ones that you've had MewBot implement- it's just not a specific one. It would be nice to not have these continue to dribble in even after the remove_holes ones have run their course.

Chuck Entz (talk)15:36, 24 May 2015

Re: diff. I thought we had stopped creating script-specific topical categories, since the catboilers can't handle them (at least, I've never been able to get such categories to work, and a search for "in traditional script" in categories shows nothing successfully using them). Besides which, the Chinese entries are now supposed to be set up to have everything in the traditional-script version and a soft redirect in the simplified-script version.

Chuck Entz (talk)03:31, 23 May 2015

I just fixed the parameter, I don't really follow all the changes for Chinese.

CodeCat11:30, 23 May 2015

A Heads-Up

You might want to take a look at the newly created {{MongolUnicode}} which seems to be ported from WP, and is being added to Mongolian templates. I don't know enough to tell if it's compatible with our system of templates, modules and js- but I have my doubts.

Chuck Entz (talk)06:10, 22 May 2015

We probably don't want it because it replaces our own Mongolian script codes. But at the same time, this seems to support vertical writing, which our templates don't. So I'm a bit reluctant to remove it altogether. Maybe this should go to the Grease Pit?

CodeCat12:34, 22 May 2015

These seem to be all due to a recent edit of yours to {{ms-noun}}

Chuck Entz (talk)07:05, 21 May 2015

I take that back. Module:headword/templates seems to be the more likely culprit

Chuck Entz (talk)07:17, 21 May 2015

Fixed now.

CodeCat12:53, 21 May 2015

“Alternative forms are no longer categorised per a previous discussion.”

Please provide me with a link to this discussion.

 — I.S.M.E.T.A.21:18, 21 September 2014

Wiktionary:Beer parlour/2013/December#How useful is Category:Alternative forms by language?. Following that discussion, {{alternative form of}}, {{alternative spelling of}} and {{alternative capitalization of}} no longer categorise. It would be rather strange if {{alternative typography of}} did categorise.

CodeCat21:22, 21 September 2014

How about {{medieval spelling of}}?

 — I.S.M.E.T.A.22:46, 20 May 2015

Look, I believe that user comments shouldn't be refactored, except in cases of vandalism. User comments are not like entries and there's no need to fix them because templates are deprecated.

Purplebackpack8904:14, 20 May 2015

Mr. Blaschke just had bis days :) thats all...

Hirabutor (talk)08:51, 19 May 2015

Edit on seillean has been reverted

Hi. Can you please explain why you reverted my edit on seillean?

Kibi78704 (talk)22:44, 8 May 2015

We're trying to eliminate the l/ templates.

CodeCat23:02, 8 May 2015

Ahh, OK. That makes sense. Thank you.

Kibi78704 (talk)23:15, 8 May 2015

BTW - I found documentation for the l/ templates at Template:link/documentation. Had I not seen it there, I would not have known of it.

Kibi78704 (talk)15:33, 10 May 2015

Who is "we". Only a few weeks ago I was advised to favor l-template by a prominent user, I don't remember whom.

Hekaheka (talk)04:40, 15 May 2015

l/la and l/de are being discussed at WT:RFDO right now. In those discussions, some people seem to be treating them like obvious junk, but to be fair it has been brought up that when these templates were created they would serve as a non-expensive alternative to l|la and l|de in huge pages like water. If they serve any other purpose is beyond me.

--Daniel12:01, 15 May 2015

Missing plurals

Hi CC. Could you edit the Module:en-headword so that missing plurals can be located? The idea I put on the talkpage was what I had in mind, but almost certainly it will be wrong, as the module is supercomplicated.

Type56op9 (talk)11:41, 15 May 2015

OHG fust < *funstiz

Our entry for *funstiz mentions OHG fûst as a descendant. So nasal spirant law. Do you have enough knowledge about Old High German to confirm that or can send me to someone who has? German has one or two examples of -unst from PGM sources and even Saxon, on average, didn't denasalise.

Korn (talk)23:30, 14 May 2015

It is a bit unusual, but even Dutch has vuist, also without a nasal. However, there may be an explanation. This word is often thought to derive from the Indo-European root for "five", or from a root *pewg-, and in that case the expected Germanic term would actually *funhstiz. And in that case, the nasal would have been lost in all Germanic languages. But the change of nh > ¯h is a very late change in Proto-Germanic, and thus the loss of -h- in this word must have been later still. And yet, it happened in all dialects?

CodeCat23:36, 14 May 2015

Dat bringt uns de frag': In that case, is it reasonable to keep the entry at *funstiz in the first place?

Korn (talk)00:02, 15 May 2015

I can't make that judgement on my own.

CodeCat00:02, 15 May 2015

Proto-Germanic Pronunciation Template

I notice many of the Proto-Germanic entries include pronunciations. A template for pronunciation might make entries easier and less prone to error e.g. in the entry *mildijaz, I was not aware that the phoneme /d/ was also pronounced [d] after /l/ in addition to being thus pronounced after /m/, /n/, /z/ and when doubled. Could a template for Proto-Germanic pronunciation be made similar to the ones already made for Ancient Greek and Latin?

Nayrb Rellimer (talk)16:39, 13 May 2015

Fixing the category

Hello. I made Template:present active participle of a while ago. (It is based on Template:present passive participle of.) I don't know how to replace the categories with Templates and modules needing documentation and Conjugation form-of templates? Thank you.

KoreanQuoter (talk)16:57, 9 May 2015

I created the documentation page. Is that what you meant?

CodeCat19:13, 9 May 2015

Yes, correct. (Just don't know how to express it.)

KoreanQuoter (talk)01:31, 10 May 2015

Germanic nerdism

Bit of a long shot, but you're the one person that comes to my mind that might know something about this topic. PGM *ne survies into Middle Low German and Dutch, also with metathesis, giving the written forms en, ne, enne, ene. I'm somewhat convinced the last two are just hypercorrectisms in dialects which have already lost /ə/. Do you have any knowledge or educated guess on how they would be pronounced? Of couse we can assume <e> to be [ə] in unstressed positions, but at least in GML monosyllables always also have a stressed form.

Korn (talk)23:17, 6 May 2015

I'm not actually sure if en reflects metathesis. What seems more likely to me is that it's an orthographic representation of syllabic /n/, with the schwa apocopated. Perhaps followed by epenthesis. I don't know about en(n)e.

CodeCat23:44, 6 May 2015

Could I get you to look at this?

Hello again! Could I get you to look at *gʷʰer- and its derived terms?

JohnC506:03, 5 May 2015

I think that it may be better if separate entries are not created for present, aorist and perfect forms, but to list them and their descendants on the main page of the root.

CodeCat14:48, 5 May 2015

Sorry for the delay. I have always been a bit unclear about that. Is it that we need a critical mass of attested forms before we create a subpage for a verb or noun form? And if we put the inflected forms back under the root, would we still retain the conjugation tables?
Also, what became of your idea to split reconstructions into their own namespace?

JohnC501:46, 6 May 2015

In the past I created entries for the three verb aspects, but I'm now thinking it wasn't such a good idea. It makes it impractical to list verbs because generally the aspects all combine into one verb in the descendant languages. Furthermore, some languages don't really have as many distinct classes anymore. For example, Germanic root verbs are something like 95% thematic verbs, but that doesn't mean their ancestors were. So it's better to keep them together on the same page.

CodeCat01:49, 6 May 2015

But...but...I like making extra pages and having the different aspects categorized... :(

JohnC501:58, 6 May 2015

Your workaround is good for now, but keep in mind that when I decide that we need an {{l-bold/he}} or something like that, I'll just revert it back. A simpler general solution is always better than a hard-coded hack.

WikiTiki8920:02, 5 May 2015

The "fakeargs" parameter is exactly a hard-coded hack.

CodeCat20:04, 5 May 2015

In case you don't know what "hard-coded" means, adding a separate if-block for each possible value of face= (instead of just passing along all given parameters) is the hard-coded hack and defies the principle of code-reuse.

WikiTiki8920:17, 5 May 2015

That's easily fixed of course.

CodeCat20:19, 5 May 2015

Apparently not, since you couldn't do it.

WikiTiki8920:24, 5 May 2015

Dan Polansky's block

To be fair to Dan Polansky, I have been disruptive on English wikipedia and have trolled there. I'm not doing that here, but I understand why he is concerned. I do not think blocking him is justified. I do not agree with him that I should be blocked, but I can see why he was concerned, and although he had an agenda with his posts, I think that he had legitimate concerns. I have taken down some of the funny sentences I inserted into to show him that I'm not going to be trolling anymore. But I just wanted to give my viewpoint that he should be unblocked, although I felt kind of harassed by his questions, he had legitimate reasons for asking them.

PaulBustion88 (talk)14:47, 3 May 2015

He's been doing this for a long time now, not just with you. You said "And that you are trying to get me to talk to use my words against me, like a police officer does.", he does that with other people as well, including me. But what grinds me even more is that he's openly calling for you to be blocked, on your own talk page which is meant to be for messages directed to you, but directed towards others instead (he refers to you in third person). That counts as harassment to me. It's completely unconstructive and doesn't help except to intimidate and demean you. I think if he really did want you blocked, he should have posted that message in a more appropriate place like the Beer Parlour.

So this doesn't have anything to do with whether he's right about your editing (he kind of is). It's about how he acts. I find his behaviour aggressive, discouraging and unconstructive.

CodeCat15:24, 3 May 2015

So are you saying you agree with him that I should be blocked?

PaulBustion88 (talk)15:28, 3 May 2015

No, not at all. What I agree with is maybe that some of your edits, like those usage examples, are a bit over the top. But you recognise that too already, calling for a block is way too much. I'm not going to call you a troll either, hopefully I can be more constructive than that.

CodeCat15:31, 3 May 2015

Well, I definitely trolled sometimes on English wikipedia, but I have not done that here at all. So I can see why Polansky would think I'm doing that here, even though I'm not.

PaulBustion88 (talk)15:32, 3 May 2015

He's making assumptions based on your Wikipedia record, and then drawing unwarranted conclusions as if it were a criminal record. And he treats you like a criminal. That's just not on.

CodeCat15:34, 3 May 2015

I’ve been considering making a Beer Parlour thread requesting for D.P. to be permablocked. He’s persistently troublesome and you people just let him walk all over everybody. It’s extremely improbable that he’ll become a better person in the future, so a permanent ban is perfectly appropriate.

Look, even if he were an expert on every language in existence, we shouldn’t tolerate persistent misbehaviour. If he were banned, we might actually have more contributors. Stop being a bunch of pushovers and get rid of him already!

Romanophile (talk)21:33, 3 May 2015

There's a formatting/visual issue in 兒科. It's caused by the ordering of the Wikipedia template.

WikiWinters (talk)15:45, 2 May 2015

Glosses in Templates

Edited by author.
Last edit: 02:32, 2 May 2015

Hi ! I notice that the glosses in templates term and m are not working: chore (piece of work); however, unless you explicitly 'gloss' them: chore (piece of work) Leasnam (talk) 02:30, 2 May 2015 (UTC)

Leasnam (talk)02:30, 2 May 2015

Oh, that's a bug then.

CodeCat02:30, 2 May 2015


CodeCat02:35, 2 May 2015

Thank you ! Leasnam (talk) 02:54, 2 May 2015 (UTC)

Leasnam (talk)02:54, 2 May 2015

Editing 'spiritus'

Hello, CodeCat! I tried to edit the page for spiritus by adding that the Greek word for 'match' σπίρτο is also a descendant. I didn't know the language code during the process but have since found the Wiktionary language-code page. May I try to edit the page again?

Alaedious (talk)13:33, 22 April 2015

But is it really a descendant? I don't immediately see a connection between "match" and "spirit".

CodeCat13:35, 22 April 2015
First page
First page
Previous page
Previous page
Last page
Last page