User talk:Kephir

Definition from Wiktionary, the free dictionary
Jump to: navigation, search
Start a new discussion


Thread titleRepliesLast modified
Kraków‎201:27, 16 April 2017
Cannot use MediaWiki:Gadget-PatrollingEnhancements.js011:44, 5 February 2016
Exclude the Wiktionary:Sandbox from Special:AbuseFilter/33023:16, 22 January 2016
Module:inflection/data/ru-noun/testcases/m-cdef101:45, 21 August 2015
Module:character info318:57, 10 July 2015
Help with pronunciation modules1116:56, 5 July 2015
edit filter111:43, 4 July 2015
Appendix:Unicode subpage links are gone/broken520:14, 25 June 2015
Module:Unicode data and Unicode 8119:00, 21 June 2015
<tt><nowiki>{{acronym-old}}</nowiki></tt>113:06, 20 May 2015
Gadgets and cross-origin resource sharing014:48, 25 March 2015
Flagged for vandalism?018:02, 24 March 2015
Noun and adjectival phrase template220:15, 11 February 2015
Unflood119:34, 1 February 2015
Ejakulacija edit300:40, 27 January 2015
hi-noun and ur-noun420:35, 22 January 2015
Template talk:ms-adj010:58, 20 January 2015
Kucing200:37, 18 January 2015
User:SuperWonderbot218:15, 17 January 2015
Transliteration modules for some Indic and African languages410:38, 9 January 2015
First page
First page
Previous page
Previous page
Last page
Last page

Thanks for that. Can you also explain the -ów‎ bit, if possible, please?

 — I.S.M.E.T.A.

20:35, 12 June 2014

w:Kraków#Etymology calls this an "archaic possessive form". Given this vagueness and weak sourcing, I would take it with a grain of salt (note, however, *-ovъ). In modern language, -ów is a common genitive plural suffix (genitive case fulfilling the possessive role), hence it can be understood as "[the town] of the Kraks (servants/descendants/etc. of Krak)". In our Proto-Slavic noun declension tables, however, the genitive plural suffix tends to be *-ъ (and the genitive dual *-u). I would love to see why this is so, how it compares to other contemporary Slavic languages, and how -ów came into being.

I have been hardly seeing you lately. Busy in real life? Fine by me if you do not want to elaborate on it too much, just wondering whether you expect to keep coming here.


21:29, 12 June 2014

Sorry I missed your response from nearly three years ago. I forgot about liquid threads. You haven't been around since September last year, so I don't expect to see you very much. :-(

 — I.S.M.E.T.A.

01:27, 16 April 2017

It returns an error saying "missingparam: One of the parameters rcid, revid is required".

11:44, 5 February 2016

Perhaps you should exclude the sandbox from Special:AbuseFilter/33 "Bad Unicode".

23:16, 22 January 2016

...and a few other testcases pages are in Category:Pages with module errors, although there's language in MediaWiki:Scribunto-common-error-category that puts most testcases pages into the hidden subcategory. Can you figure out how to exclude these pages, too? Thanks.

01:13, 21 August 2015

I think those may be a different type of module error than the ones normally found in testcases pages: User:Vitalik changed the directory structure without bothering to change the "require" statements to point to the new locations. I fixed a batch of them, but got tired of it. You would think that someone doing extended heavy module-programming work would check Category:Pages with module errors every once in a while, but I guess they would rather let us do it for them...

01:45, 21 August 2015

I could be wrong, but it looks like about 340 of the 373 entries in Category:Pages with module errors are there due to your edits to this module a couple of days ago. Could you look into it? Thanks!

02:05, 9 July 2015

You were not. Fixed for now. Though I have run into some entries like [[]] or [[]] that might need to be revisited by someone more knowledgeable in Korean. Specifically, the jamo decompositions may need to be checked.


11:31, 9 July 2015

Thank you! I was, however, right about being wrong: there were 4 Polish entries in that count that were actually due to edits to Module:pl-noun by Tweenk. I just left a message on his talk page.

18:06, 10 July 2015

Well, that depends on how you define about. Almost all sometimes means "all except finitely many".


18:57, 10 July 2015

Help with pronunciation modules

Hi. Can you look at why the ['кь'] = 'ḳ̍' rule is ignored in the headword line of ажакьа? The addition of a stress sign plays a role.

12:58, 28 June 2015

"к" is the third letter from the start. The mw.ustring.gsub(text, '..', tt) line takes successive pairs of characters and substitutes them according to the mapping; here, they are "аж", "ак", and "ьа". Since "кь" is on an odd position, it is not matched. I vaguely remember some other module being bitten by the same problem before.

My solution cheats a bit; it just restricts the pattern to pairs which start with consonants that have entries in the table. If you ever need to process overlapping pairs, or ones with some other consonant letters, it will no longer work.


13:46, 28 June 2015

I see, thanks.

14:01, 28 June 2015

Some languages are written in multiple scripts. Assume we have an automatic transliteration module for each script. Is there a way to make, for example, Ossetian to be transliterated with Module:os-translit when written in Cyrl and with Module:Geor-translit, when written in Geor? I understand that I can copy the content of the latter into the former, but that would lead to duplication and dis-synchronization over time.

09:23, 5 July 2015

That is what require is for. Just check whether the script is "Geor", and if so then return require("Module:Geor-translit").tr(text, lang, sc). Is that something you are actually trying to do?


09:55, 5 July 2015

Yes, I am trying to do it. I would like to start with Kipchak (Module:qwm-translit), which can be written in Latin and Armenian. How would the code look like if I want to skip transliteration if it's Latn, and forward to Module:Armn-translit, if it's Armn. There are many more languages in the pipeline.

11:03, 5 July 2015

edit filter

FYI I commented with a suggestion on the PAM filter.

05:15, 4 July 2015

Thanks, but I somewhat doubt the condition you proposed is feasible to implement. (Dropping conditions may help, actually…)


11:43, 4 July 2015

Appendix:Unicode subpage links are gone/broken

I noticed after you edited Module:character info and Module:character list, the character links in the subpages of Appendix:Unicode are broken (as they no longer show up as links but just as displayed glyphs). Was this the intended behavior of those changes? Just curious.

18:58, 25 June 2015

Yes, it was indeed intentional. I have done it, in fact, after I noticed you creating entries for Unicode code points, giving the Unicode character name as the definition. I think such entries should not be created, and other editors have agreed with me in a few discussions about the topic: Talk:⦰ and Wiktionary:Beer parlour/2015/January#Is documenting all Unicode characters within the scope of Wiktionary?; although there was some disagreement about what should be put in their stead.

I am of the opinion that:

  • Wiktionary is a project that documents natural languages, not any particular computer encoding of them. There are already many websites presenting the Unicode character database in human-readable form, and there no real benefit to creating poor competition to them.
  • Unicode code point names do poorly as definitions of glyphs they represent, and should not be remotely treated as such. They are as just as much of technical artefacts as the code point numbers, combining classes, bidirectional classes, etc.
  • Emoji, dingbats and other symbols should be subject to the same attestation criteria as any other lexical item. It is better to be incomplete than unreliable.


19:15, 25 June 2015

So you also think it's reasonable to simply break linking with *everything* in Appendix:Unicode, even though it also contains single-character words such as in the CJK Unified Ideographs range? Then really, why have such an appendix at all if there is no individual character linking? I'm not really following your line of reasoning entirely.

19:23, 25 June 2015

If I tried the equivalent of {{#ifexist:X|[[X]]|X}}, it would run into expensive function limits quite quickly and fail to render. So it really is either all or nothing.

I have no idea why you would like to browse CJK characters through the Unicode appendix anyway; it is not like it is the most convenient way to do it, given their pretty much random placement.


19:31, 25 June 2015

Just because one person finds a method inconvenient doesn't mean everyone does. Unicode is a standard, and its ordering matters to things like CJKV characters; also, the placement is in radical-stroke order, not "pretty much random" as you attest. Perhaps you don't know as much about these things as you think you do?

19:34, 25 June 2015

Okay, I admit that I made that statement based on an extrapolation from my observations about placement of letters in Latin and Cyrillic scripts, which at this point are decided on a "wherever it fits" basis. I realise the analogy may not carry through completely, and Unicode Inc. may even attempt to maintain some sane ordering within individual allocation ranges. I can grant you that. (Even though you cannot rely on this property on a large scale: U+20000 has fewer strokes than U+4684. From that perspective, the placement really is random.)

On the other hand, this is still not the most convenient way to browse CJK characters, given that you only have a meaningless number next to the character itself in a smallish font, and a completely nondescriptive character name of the "CJK UNIFIED IDEOGRAPH-XXXXX"…

Anyway, there are some other reasons why I decided removing all links from that appendix was an overkill after all. I restored the links in Appendix:Unicode. Still, in the future please do not create entries of the kind that I mentioned.


20:14, 25 June 2015

Module:Unicode data and Unicode 8

I was just looking at the listings at Appendix:Unicode and it looks like Module:Unicode data needs to be updated to include the new Unicode ranges (including CJK Unified Ideographs Extension E). The new ranges are listed at . Cheers!

10:10, 21 June 2015

Done. (You could have done it yourself… I left every ingredient here.)


19:00, 21 June 2015


Re your edit summary, it's to remove pages from Special:WhatLinksHere/Template:acronym-old, per the post-deletion instructions.

 — I.S.M.E.T.A.

07:56, 14 May 2015

Fix those instructions then. A redlink to a template can be clicked to reveal the deletion log, which saves some time (compared to typing the template name in the address bar).

Now, redlinks to deleted dictionary entries should be removed, sure. But that is because readers are generally not interested in log entries.


13:37, 15 May 2015

Gadgets and cross-origin resource sharing

I'd like to build a gadget similar to Quiet Quentin which would allow an editor to automatically import usage examples from (short description here: Tatoeba-gadget). How can I build a gadget which makes cross-site requests? Is there a process for whitelisting? I guess it needs the Access-Control-Allow-Origin header set.

14:48, 25 March 2015

Flagged for vandalism?

Hi, I am trying to wikify the list here since the edits require modifying 1000 words at a time, the system is flagging me for vandalism. May I receive some help and or guidance on how to proceed from here?

18:02, 24 March 2015

Noun and adjectival phrase template

I made {{pl-decl-phrase}}. Let me know whether the input format is acceptable.

19:53, 3 February 2015

Dobre na początek, choć mnie przyszło do głowy co innego. Raz, w tabelce dobrze byłoby linkować całe odmienione formy, a nie tylko pojedyncze wyrazy. Dwa, formy odchylające się od wzorca można podawać jako parametry całego szablonu przecież, a nie samej odmieniarki (|vocs=Słodka Aniu, nie f!A!ni!vocs=Aniu).

Zastanawiam się też, czy nie dałoby się zrobić, żeby wzorzec deklinacji rzeczownika był wyznaczany przez moduł automatycznie. Pełnego automatu, jak z przymiotnikami, raczej się nie zrobi, i oczywiście wyjątki się będą trafiać wcale nierzadko, ale wydaje mi się, że rzeczownik w mianowniku wraz z rodzajem-ożywionością (m-pr, m-an, m-in, f, n, i osobny znacznik dla przymiotników, bo w końcu sarnasarny, ale ciężarnaciężarnej) powinien w większości przypadków wyznaczać jednoznacznie wzorzec odmiany. Wtedy można by zrobić jeden szablon, który może odmienić wszystko, i któremu podawałoby się całe wyrazy. Wtedy wszystko byłoby prostsze i bardziej czytelne.


16:49, 9 February 2015

Wyszukiwarka jest w stanie znaleźć formy występujące w tabelce z odmianą, np. po wpisaniu "elektrycznych zespołów trakcyjnych" w wynikach pojawia się "elektryczny zespół trakcyjny", więc nie wiem, czy tworzenie stron dla tych form jest sensowne.

Jeśli chodzi o formy oboczne, to można całość napisać tak, żeby parametry typu |vocs= były obsługiwane zarówno dla poszczególnych składowych jak i dla całego wyrażenia. Często jest tak, że np. w wyrażeniu przymiotnik-rzeczownik tylko rzeczownik ma formy oboczne - wtedy używając form obocznych dla składowych można zaoszczędzić sobie pisania.

Kwestia 'bardziej automatycznej' deklinacji rzeczowników jest niezależna od samego pl-decl-phrase. Pierwszy parametr to jest po prostu nazwa wzorca deklinacji (elementu tablicy patterns) w Module:pl-noun, więc jeśli wymyślimy jakiś bardziej ogólny wzorzec, to od razu będzie można go użyć w pl-decl-phrase. Natomiast można zrobić coś w tym rodzaju:


Dla takich parametrów szablon mógłby sam zgadywać, że przymiotnik powinien mieć żeńską odmianę, bo w wyrażeniu występuje rzeczownik rodzaju żeńskiego.

20:15, 11 February 2015

Hi. You can unflood-flag me again if you fancy. Regards

19:30, 1 February 2015

Yes check.svg Done. Cheers.

19:34, 1 February 2015

Ejakulacija edit

Kephir, your bot reverted my edit. The language is Slovene not Serbo-Croatian and I also added a correct definition. Please revert the definition page to include my adds.


22:49, 26 January 2015

No, the entry is for Serbo-Croatian. If it also exists in Slovene then there should be a separate entry for that, you shouldn't just go around removing stuff.

22:56, 26 January 2015

I'm not "just going around changing stuff" as you put it. The Slovene translation link sent me to the wrong page, which isn't immediately obvious in the Wiktionary Android App. Only after using a web browser is it obvious. I will create a Slovene page and I assume the translation link will then work.

00:40, 27 January 2015

I'm not "just going around changing stuff" as you put it. The Slovene translation link sent me to the wrong page, which isn't immediately obvious in the Wiktionary Android App. Only after using a web browser is it obvious. I will create a Slovene page and I assume the translation link will then work.

00:40, 27 January 2015

That was no bot, and you are on the way to being blocked for edit warring.

The definition was not in English, and you destroyed a valid language header. To add a definition in another language, add a new header.


22:58, 26 January 2015

hi-noun and ur-noun

Hey! Sorry, for the last revert. For some reason, the Urdu spelling in hi-noun didn't take the Urdu font specifications and it looked really odd and blocky. Now it looks better, however it's bolded and so is the Hindi spelling in Urdu entries. It makes it hard to read (we intentionally increased the size of Urdu and Hindi font specifications so that they are more legible, but making them bold makes both hard to read). Can you make the text regular and not bold?

09:05, 21 January 2015


17:22, 21 January 2015

That's not exactly what I had in mind and your edit only worked on Arabic language and Devanagari script. What I meant was that in the actual templates themselves, when the spelling in the other script is provided, it shouldn't be bolded when it is wikified. Otherwise, as a headword, it's fine to be bolded.

03:29, 22 January 2015

I do not get it. If emboldening hurts legibility, why allow it anywhere? And if it does not, why make an exception for script variants?


07:40, 22 January 2015

I'm sorry if I confused you. I think it was just my browser that's been acting funny the last few days.

20:35, 22 January 2015

Care to lend a hand?

10:58, 20 January 2015

Could you move back Kucing to kucing. Someone moved it and I don't know how xx --Malaysiaboy (talk) 01:18, 17 January 2015 (UTC)

01:18, 17 January 2015

Done. (I have also edited a few related entries which apparently mischaracterised relations between these variously spelled words.)


10:21, 17 January 2015

Thanks a lot for helping!

00:37, 18 January 2015

I don't want to go pointing fingers, but I think User:Type56op9 may be ban evading. The content looks near-identical, and SuperWonderbot started about where (and when) Type56 left off. As a more experienced user, and the one who banned Type56 in the first place, I'll defer judgement to you.

19:26, 23 December 2014

Just fyi, this is Wonderfool, aka several hundred other aliases. At times he's a conscientious and prolific editor, at times a shoddy and irresponsible one, but he never should be taken at face value. He's been banned many, many times for very good reasons, but he's very persistent. At one point it was decided to tolerate him as long as he behaves, and block him when he doesn't.

14:57, 24 December 2014

Well, per his admission, I've blocked him for a week. I hope this will give more experienced janitors the time to sort this out.

23:03, 24 December 2014

Transliteration modules for some Indic and African languages


I wonder if you're willing to help with transliteration modules for a variety languages. Don't freak out, you don't need to learn any new script, you would need to work with the resulting romanisation. I'm almost sure this could be an easy task for you. Besides, you don't have to work on all modules, if you make one work, the logic can be copied to other modules, assuming the rules for dropping the inherent vowels are identical.

The help required is for removing inherent vowels "a" (Hindi, Gujarati, etc.), "ô" (Bengali, Oriya, etc.), "ə" (Amharic, Tigrinya, etc.), which is dropped in certain positions. All these languages are 99% phonetic, the only problem is, we need to drop the vowels (as per standard transliterations), e.g. देवनागरी (devnāgrī). Although it's spelled "devanāgarī", the inherent vowel "a" is dropped in certain positions. We can write test cases and describe some rules for you.

See one case in Module:hi-translit/testcases and a discussion in User_talk:DerekWinters#Bengali_transliteration_module.

Let me know if you're interested. Fixing this problem will cover a large number of scripts for languages with a large number of speakers! Isn't it exciting? If you say no, it's OK, I'll ask someone else. :)

There are other, less urgent issues, like displaying nasalazations, which is dependent on what follows the anusvara symbol. We have a temp solution, which may become a permanent one.

23:54, 7 January 2015

It does look interesting, but I am not sure if I can afford the time. And right now I see no good way to approach it. If you could add some more material, please do. I will take a look… eventually.


21:07, 8 January 2015

Thanks, User:DerekWinters has described some scenarios for Hindi on his talk page but if you prefer to work with test cases, as in Module:hi-translit/testcases we can make them better. No rush, of course. Let me or DerekWinters know if you need any clarifications

22:26, 8 January 2015

Schwa deletion in Indo-Aryan languages has some more info on schwa syncope, although the transliteration they use is not standard. Various dictionaries handle somewhat differently some corner cases but we can choose one approach.

00:13, 9 January 2015

Not at this point. I need to know what the rules are, not what the exceptions are.


10:38, 9 January 2015
First page
First page
Previous page
Previous page
Last page
Last page