Hello, you have come here looking for the meaning of the word User talk:Liliana-60/archive2. In DICTIOUS you will not only get to know all the dictionary meanings for the word User talk:Liliana-60/archive2, but we will also tell you about its etymology, its characteristics and you will know how to say User talk:Liliana-60/archive2 in singular and plural. Everything you need to know about the word User talk:Liliana-60/archive2 you have here. The definition of the word User talk:Liliana-60/archive2 will help you to be more precise and correct when speaking or writing your texts. Knowing the definition ofUser talk:Liliana-60/archive2, as well as those of other words, enriches your vocabulary and provides you with more and better linguistic resources.
Unprotecting Beer parlour
Latest comment: 13 years ago7 comments2 people in discussion
Please unprotect BP that you have now protected. I will no longer respond to MG in that discussion, but I want to be able to post to BP. I admit to being unyielding but so has been Martin Gardner. --Dan Polansky14:47, 22 March 2011 (UTC)Reply
The offer of the block is ridiculous. Above all, the thing in BP is clearly a bear fight in which any party can give in, whether me or MG, but you have chosen me as your target. (One assymetry is that MG is producing fallacious arguments whereas I am stubbornly refusing to leave them unobjected.) After all, you have not responded to my "Prince Kassad, you are making a blank accusation of my incivility. Do you care to provide a diff or two that shows what you consider my incivility?"
There is very little doubt that you are biased against me and favor MG.
Disclaimer: If you do not want me to talk to you on your talk page, please say so. If you want to block me, please say "stop talking to me or I will block you". --Dan Polansky15:11, 22 March 2011 (UTC)Reply
I am expecting MG to stop as well. The BP is clearly not the right place for such a discussion to take place. I do welcome opinions from unbiased people, but mindless bitchering is not the right way to go on. -- Prince Kassad15:15, 22 March 2011 (UTC)Reply
I do not think that my arguments were mindless at all, but I admit that the bear fight is of no interest to most people and that I should have tried to end it earlier. I promise that I will try hard to no longer respond in that thread in BP. The only reason why I do not want to make a wholly unconditional promise is that there could be actions by MG that would warrant a response nonetheless.
Your accusation of my incivility is still unbased. You should better retract it or provide the diffs, I think.
I admit that my accusation was very likely wrong. However, the user in question was already accused of Wonderfoolery by several other people. When you are accused of being Wonderfool, removing that accusation from your talk page is the last thing you should do. Removing these sorts of accusations was what Wonderfool actually was doing, and what has helped me discover him under one of his accounts. I think I was justified in reverting the removal given the evidence at hand. I have ceased reverting after msh210 has explained to me that the accusation is probably wrong. In this case, I cannot confirm anything uncivil. --Dan Polansky16:43, 22 March 2011 (UTC)Reply
Latest comment: 13 years ago3 comments3 people in discussion
Any chance KassadBot could be modified to switch simple ] links in derived terms sections and synonyms sections and such to use {{l}}, to link to the correct language sections? I think it would be very helpful. --Yair rand04:49, 5 April 2011 (UTC)Reply
Short answer is yes, I don't know how, but it seems to be possible. Second point; the bot might remove the only links on the page in doing so, so afterwards it might have to add {{count page}} (see section below this one). Mglovesfun (talk) 15:46, 13 April 2011 (UTC)Reply
It;s undesirable IMO when he linked-to entry is English or Translingual (so the link goes to the top of the page anyway, and without using {{l}} we save a template call) or its page has and is likely to remain with only one language section.—msh210℠ (talk) 15:49, 13 April 2011 (UTC)Reply
Statistics
Latest comment: 13 years ago3 comments2 people in discussion
Someone just undid an KassadBot edit, where the bot converting ===Statistics=== to ====Statistics====. Is there an agreement over what level it should be? Mglovesfun (talk) 12:48, 7 April 2011 (UTC)Reply
The bot seems to be a bit confused when there are multiple etymologies. I am checking what's causing it, don't have any strong clues yet. -- Prince Kassad12:57, 7 April 2011 (UTC)Reply
Latest comment: 13 years ago4 comments3 people in discussion
As you could have guessed, my removing your vote in the poll has been an inadvertent effect of my response to Ruakh (diff). I am sorry for the removal. However, you cannot possibly believe that I wanted to remove your vote as part of my comment, and hope for it to go unnoticed, right? Accidental removal of things as part of responses in Beer parlour has happened several times to various people. Furthermore, why don't you talk to me about it instead of blocking me? It seems like some sort of punitive block, which is frowned upon in Wiktionary; you should check WT:BLOCK. --Dan Polansky13:26, 7 April 2011 (UTC)Reply
Accidental removal of things as part of responses certainly happens several times; it's very easy to assume they are mistakes, and very hard to assume they are malicious manipulations of discussions, even if the subject of alteration is a vote. Kassad, please don't block people for that reason again. --Daniel.13:40, 7 April 2011 (UTC)Reply
Verständiger einwand in der frage zur namensgebung von der stadt balchasch. Der typ is deutscher klugscheißer der seine aussagn ausm internet kopiert hat. Ich bin august 90 in der stadt balchasch geboren und hab den besseren standpunkt
That was before {{Xyzy}} failed RFDO, which actually surprised me. (I assumed we would find some kind of replacement until then) That RfD on Template:None should probably be closed as keep. -- Prince Kassad20:44, 27 April 2011 (UTC)Reply
Well, {{Latn}} has the span tag mention-Latn, which by default sets the word in italics. This is apparently not wanted for non-Latin scripts (especially Cyrillic which has vastly different italic forms). -- Prince Kassad20:46, 27 April 2011 (UTC)Reply
Well, use Latn but specify the script for non Latin entries. I think in any event, these are interim solutions until one of the solutions previously suggested at WT:GP gains a majority over the other. Which is why I brought the topic up again today. Mglovesfun (talk) 20:51, 27 April 2011 (UTC)Reply
Stop!
Latest comment: 13 years ago5 comments4 people in discussion
Prince Kassad, must you throw the toys out of the pram when anyone opposes you? It's really, really annoying. Ruakh at the very least has a valid point. Mglovesfun (talk) 20:59, 30 April 2011 (UTC)Reply
Latest comment: 13 years ago2 comments2 people in discussion
Does KassadBot remove {{count page}} when it's no longer necessary, like autoformat used to do? I've noticed a bunch of edits where it formatted other stuff but left the template alone even though the page had links. --Yair rand10:50, 12 May 2011 (UTC)Reply
Latest comment: 13 years ago3 comments2 people in discussion
To get things moving, I would right now create a vote "Attestation of extinct languages 2", which drops the "mention" part to get voter acceptance. If I create the vote, I will also omit the "Extinct language" section altogether, leaving only the modification to "Attestation" section. What spurs me to want to do it is the current result of the running vote Wiktionary:Votes/pl-2010-12/Attestation_of_extinct_languages, which is 0-3-2. If the currently running vote turns out to change into support, the new vote can be canceled.
I would now go and create the follow-up vote myself, but I want to give you a chance to create the vote yourself, as it is your initiative, and a good one. Please let me know what you think. --Dan Polansky08:36, 19 May 2011 (UTC)Reply
It would be a much better idea to create a vote on what was suggested on the talk page, i. e. delegating language-specific CFI issues to the (currently underused) About pages. Even though I'm still not happy with that, it would have a much higher chance of success. -- Prince Kassad09:44, 19 May 2011 (UTC)Reply
I am unenthusiastic about delegating language-specific CFI to about pages of languages: the pages are not locked from editing without voting, and this method allows proliferation of disparate language-specific CFIs when a more compact CFI ranging across languages is possible. I am enthusiastic about creating a follow-up vote worded similarly to the current vote. I am going to create the follow-up tomorrow or later, to give you the opportunity to create it yourself. --Dan Polansky09:50, 19 May 2011 (UTC)Reply
Punctuation marks
Latest comment: 13 years ago3 comments2 people in discussion
I think it's the bot getting confused when there is an erroneous level 3 header occuring above the references section (such as Anagrams). Since it cannot find a valid part of speech in this case, it tags the page accordingly. -- Prince Kassad03:48, 15 June 2011 (UTC)Reply
Something your bot did
Latest comment: 13 years ago4 comments2 people in discussion
Ah! I can tell why. The bot goes by its own list, User:AutoFormat/Languages, and that one does not have Low German, only Low Saxon. Robert Ullmann had a bot that would refresh this list semi-automatically, but now, it's been dormant for months. We'd need a bot to regenerate it again. -- Prince Kassad16:24, 19 June 2011 (UTC)Reply
Do note that with the current code, the language list is loaded at once on runtime, this could prove to be a bit difficult with 7,000+ subtemplates. Changing the functionality is difficult, and it might take me some time. -- Prince Kassad16:51, 19 June 2011 (UTC)Reply
Are you a boy or girl?
Latest comment: 13 years ago2 comments2 people in discussion
Latest comment: 13 years ago2 comments2 people in discussion
I can't see the difference between this and the link to version. Is it an encoding issue? A deprecated Unicode character or something? Thanks in advance, --Mglovesfun (talk) 18:25, 17 July 2011 (UTC)Reply
That one took me a while to figure out. As it seems, the entry marked for deletion used a soft hyphen, which shouldn't really appear in page titles (it's only there to faciliate line breaking, which is useless for headings). -- Liliana•18:43, 17 July 2011 (UTC)Reply
AF job involving Anagrams
Latest comment: 13 years ago5 comments3 people in discussion
Sorry, not sure if I should post this here, or at User:KassadBot. After WT:Votes/pl-2009-12/Modify anagram section of ELE, Conrad has his bot updating the anagram layout (to be horizontal) whenever the anagram "set" get updated. This doesn't happen that often, which means that even given 1.5 years, most haven't been converted (and some are still quite long, cf narteci). Would you be able to have your AF bot update the anagram layouts if it was already going to edit the page (which should be much more frequent)? Thanks. --Bequw→τ14:01, 18 July 2011 (UTC)Reply
There's a bit of a problem with that; {{alphagram}} is now blank (by design) but the vote still says to use it followed by a colon, which simply created a colon before the list of anagrams. I guess the vote ignores the fact that {{alphagram}} can be modified. --Mglovesfun (talk) 20:35, 18 July 2011 (UTC)Reply
I was not suggesting Liliana's AF bot modify the alphagrams portion, just replace "\n*" with "," in vertical listing of anagrams (that are after the alphagram, if present). Does this side-step the issue sufficiently? Fixing up the alphagrams, if that's needed, can be a separate issue. --Bequw→τ12:16, 20 July 2011 (UTC)Reply
I think it's more because it somehow interprets {{subst:xx}} as {{sub}}. Of course, the former only actually appears on any page when someone tries to subst a nonexistent template. -- Liliana•05:41, 26 July 2011 (UTC)Reply
Latest comment: 13 years ago3 comments2 people in discussion
Your bot is unlinking this language name in Translation sections. Was there a decision to unlink all language names? It would be a bad idea to unlink this one, in part because there are actually two very different regions in Europe called Galicia in English, and Galician is only spoken in one of them. --EncycloPetey02:36, 26 July 2011 (UTC)Reply
It only does this on the entry on the language name itself. It can't link to itself in this case, so the link is removed. -- Liliana•03:49, 26 July 2011 (UTC)Reply
Ah, understood. Thanks for explaining that. And, by the way, thanks for all the important bot work you've been doing for the past few months. --EncycloPetey04:47, 26 July 2011 (UTC)Reply
Latest comment: 13 years ago3 comments2 people in discussion
Hi Liliana,
I'm not a regular contributor to Wiktionary, but I notice two entries I contributed to were nominated for deleted. I know the nominator from Wikipedia, where we clash on the same topics of the two entries. It looks like he followed me here when Wiktionary was mentioned in a discussion on Wikipedia. One was Anglo-Celtic Isles, which was kept. The other was Britain and Ireland, which was deleted.
I'm not surprised it was deleted. The first entry was simply that the term might refer to the islands of Britain and Ireland (individually). The second entry was more fitting and was that the term is a synonym to British Isles. That might be surprising, but there are plenty of references to support it being so. For example:
"Some of the Irish dislike the 'British' in 'British Isles', while a minority of the Welsh and Scottish are not keen on 'Great Britain'. … In response to these difficulties, 'Britain and Ireland' is becoming preferred official usage if not in the vernacular, although there is a growing trend amongst some critics to refer to Britain and Ireland as 'the archipelago'." (Davies, Alistair; Sinfield, Alan (2000), British Culture of the Postwar: An Introduction to Literature and Society, 1945-1999, Routledge, p. 9, →ISBN
"At the outset, it should be stated that while the expression 'The British Isles' is evidently still commonly employed, its intermittent use throughout this work is only in the geographic sense, in so far as that is acceptable. Since the early twentieth century, that nomenclature has been regarded by some as increasingly less usable. It has been perceived as cloaking the idea of a 'greater England', or an extended south-eastern English imperium, under a common Crown since 1603 onwards. … Nowadays, however, 'Britain and Ireland' is the more favoured expression, though there are problems with that too. … There is no consensus on the matter, inevitably. It is unlikely that the ultimate in non-partisanship that has recently appeared the (East) 'Atlantic Archipelago' will have any appeal beyond captious scholars." (Hazlett, Ian (2003). The Reformation in Britain and Ireland: an introduction. Continuum International Publishing Group. p. 17. →ISBN.)
I'm not familiar with practice on Wiktionary but I don't want to simply re-create a deleted entry. So, I am wondering what the usual process is for re-creating a deleted entry or re-opening an RfD? --Rannpháirtí anaithnid17:48, 26 July 2011 (UTC)Reply
In the deletion discussion, people expressed concern that this entry is "sum of parts", i. e. that knowing the terms Britain and Ireland is sufficient to understand this compound. We don't really have any kind of procedure for overturning deletion discussions - my best suggestion is to start up a discussion on the Tea room, people there are likely to help you. -- Liliana•03:52, 27 July 2011 (UTC)Reply
Ironcially, some opposition to the expression (including comments voiced during the RFD) is that it is not the sum of it's parts (i.e. that the British Isles contains more places than Britain and Ireland).
Latest comment: 13 years ago2 comments1 person in discussion
Hi Liliana-60
ich sah, dass du was auf meiner Diskussions-Seite geschrieben hast. Danke für die Info. Da hatte ich nicht zu viele Zeit geschweige denn dass ich darauf antworten konnte, da ich für einige Zeit inaktiv gewesen war.
Du hast mir vorgesclagen mich hier einzutragen, und das habe ich bereits getan, aber es sind leider wenige Leute da, die das billigen. Daran war ich und bin noch interessiert und werde immer...Es sind, glaube ich zumindest, wenige Befürworter da und solange es wenige Zustimmer gibt, dann gibt es kein wikisource.ku, das kann ich mir vorstellen.
Ich danke dir vielmals, dass du dieses Projekt unterstützt.Dass mit dem Kurdischen, da werde ich Vieles da eintragen und es ist ein anderes Gefühl dafür mich aucch, wenn da auch ein wikisource.ku gibt. Liebe Grüße und tausen Dank an dir.George Animal08:36, 27 August 2011 (UTC)Reply
PS:Warum kann ich mich als George Animal nicht einloggen.Ich dachte daran, ein account zu erstellen namens George Animal, aber es wurde nicht akzeptiert, oder es erschein dass der Name schon vorhanden ist. Dann gab mein Passwort, mit ich mich überall in allen anderen Projekte wie wiktionary, wikipedia, dann und ich bekomme eine Warnung, dass das Passwort nicht stimmt. Was kann ich tun?George Animal08:36, 27 August 2011 (UTC)Reply
rfc-auto
Latest comment: 13 years ago3 comments3 people in discussion
There's some strange problem that appeared recently that causes it to quit very often, which makes it a real pain to keep the bot running. Of course I can still try, but it's very bothersome. -- Liliana•12:15, 27 August 2011 (UTC)Reply
Do you think you could try running it from time to time (perhaps weekly?) and not restarting it between times if it stops? Even that would doubtless help quite a bit. Thanks for your consideration.—msh210℠ (talk) 20:50, 14 September 2011 (UTC)Reply
standard precautions
Latest comment: 13 years ago1 comment1 person in discussion
Latest comment: 13 years ago1 comment1 person in discussion
Thanks for restoring my Ge'ez entry. Now I know a little bit better how to add words. I will continue with a few more, and also include latin transliterations. /Leos Friend21:17, 25 September 2011 (UTC)Reply
protecting pages
Latest comment: 13 years ago6 comments2 people in discussion
Hi,
It may be wrong to protect pages because of one user but can you suggest anything else? I've been trying not just revert everything he does but fix and use some of the positive information he adds. It's hard though. He is very productive and inventive as far as avoiding blocks goes and his whole activity is about to show that Mandarin can be written in Roman letters, proving his point and edit-warring. --Anatoli05:35, 4 October 2011 (UTC)Reply
I thought you knew this guy. ;) Heard about abc123? The problem is, he was blocked many times but he reincarnates himself as someone else and generates IP addresses in any range (range block does bother him). At times he behaves civilly, so there was no big pressure to do something radical by the community. --Anatoli06:10, 4 October 2011 (UTC)Reply
When I say "him" (I'm almost sure it's a male), I mean all the IP addresses he generated automatically, most of them were blocked. He is easily recognsable by his pinyin entries , noone does it so eagerly. Recently he added mixed English-Chinese combinations or entire English words in Mandarin. --Anatoli06:14, 4 October 2011 (UTC)Reply
The problem is that by fully protecting this page, you also prevent legitimate editors from editing the page. If you weed out his alternate accounts, and semi-protect affected pages to wall off his IPs, you at least give other people a chance to contribute. I think this is a more user-friendly way of dealing with him. -- Liliana•12:55, 4 October 2011 (UTC)Reply
Latest comment: 13 years ago5 comments2 people in discussion
Do we have a language code for this family? I see you created the phylum Category:Mataco-Guaicuru languages qfa-mgc, but several languages are specifically Matacoan. At the moment I've used Template:etyl:Matacoan, modelled on other etyl: templates that are names not codes, but it seems nonstandard. Is there a list of these family codes somewhere? Thanks for your help and for refining my categorisations like mqm! - -sche(discuss)05:55, 6 October 2011 (UTC)Reply
Latest comment: 13 years ago3 comments2 people in discussion
What is the current state of the functionality previously delivered by Autoformat? For a time Kassadbot was delivering it I thought. I have seen mention of other bots, but haven't seen evidence in the cleanup categories that any of them are now working, at least on English entries, but also on structure for all entries. DCDuringTALK14:29, 14 October 2011 (UTC)Reply
Latest comment: 13 years ago2 comments2 people in discussion
This entry was not intended as a joke; even if was regarded as sum-of-parts it would be useful as a way to find translations in other languages. I would appreciate the chance to get the community's input on this. Fugyoo22:00, 19 October 2011 (UTC)Reply
I know it wasn't intended as a joke, but I don't see how this would be useful as a translation entry, given that all other languages I know translate it the same (German: und sieh, French: et vois). Feel free to discuss this to your heart's content at WT:RFD#and see, though. -- Liliana•22:04, 19 October 2011 (UTC)Reply
imperative
Latest comment: 13 years ago3 comments2 people in discussion
Hi. When your bot creates pages, he doesn't add all the imperatives: see bezieh for example. Any reason? Can the imperative be added? I assume it would be simple. --Rockpilot18:35, 21 October 2011 (UTC)Reply
Latest comment: 13 years ago1 comment1 person in discussion
Robert Ullman's version of AF put Latin terms into a subcategory of the rfc-structure category because contributors of Latin terms seem to use Pronunciation as a L3 header and Etymology as an L4 header regularly, apparently for good reasons. DCDuringTALK02:35, 24 October 2011 (UTC)Reply
more regulars
Latest comment: 13 years ago4 comments2 people in discussion
Regarding the -eln ones, are there always 3 possibilities for first-person singular, like at babbeln? I'm probably not going to be able to spot any strong verbs among them all. --Rockpilot14:22, 25 October 2011 (UTC)Reply
Yeah, those three possibilities are always attestable. There are no strong verbs among them, but as always, there may be separable ones. -- Liliana•14:25, 25 October 2011 (UTC)Reply
flood flag
Latest comment: 13 years ago1 comment1 person in discussion
Latest comment: 13 years ago3 comments2 people in discussion
Thank you; the thing I just can't understand is why the person who deleted all those dozens of Mandarin categories, then never restored them, won't clean up after his/her mess. Don't we all feel a sense of responsibility at this project? Personally, I wouldn't delete a category (let alone deleting dozens of well-populated categories in a single day) without being prepared to move all the entries to the new categories they have been replaced with. Can we get some action on this? It's really an embarrassment that the most widely spoken language in the world has only red categories for the various subjects such as Astronomy, Music, Plants, etc. 71.66.97.22807:55, 2 November 2011 (UTC)Reply
We're currently in the process of moving all the Chinese categories to a new system, so in the time being, there may be a bit of a mess. I wish I could help, but I am myself unfamiliar with the new system used. -- Liliana•10:29, 2 November 2011 (UTC)Reply
The new categories seem to be in place, but 99% of them are redlinked. There shouldn't be a delay like that and the editors who redlinked the categories (the same ones who don't answer any discussion page comments or questions about this issue) shouldn't be doing other editing (presumably on more fun or exciting things) before this is taken care of. 71.66.97.22823:02, 2 November 2011 (UTC)Reply
Ɛ, ɛ deleted in error
Latest comment: 13 years ago2 comments1 person in discussion
My bad, sorry. I was rushing, and thought I was deleting some incorrect redirects I had just created. I'm back online now and will undelete them at once. --Enginear09:04, 2 November 2011 (UTC)Reply
Yup. We do not create entries for any adjective forms that are compared using more/most, and the fact they were linked was a mere mistake. You can easily figure out the meaning if you know what more/most means. -- Liliana•12:53, 9 November 2011 (UTC)Reply
Latest comment: 13 years ago3 comments3 people in discussion
Hi, I was wondering if I could ask KassadBot to recognize the header "Adjectival noun" which has been agreed upon recently for Japanese at BP:Proper label for Japanese "quasi-adjectives". Thanks Haplology13:41, 10 November 2011 (UTC)Reply
Latest comment: 13 years ago6 comments3 people in discussion
Hello Liliana --
I just noticed in this edit that KassadBot has been adding * before {{ja-readings}}. This is completely superfluous, as the template ignores any * earlier in the line. I've been stripping it out whenever I edit readings, in part since it's superfluous, and in part since I find it makes it harder for me to visually parse the wikicode. Would you be so kind as to tweak the bot's code? -- Cheers, Eiríkr Útlendi │ Tala við mig20:06, 14 November 2011 (UTC)Reply
Actually, it is doing this for consistency purposes since it does the same for other templates such as {{IPA}} or {{R:Webster 1913}}. It would not make sense to change it for one template and leave it as is for the others. You would have to gain consensus to change the practice for all affected templates. -- Liliana•00:06, 15 November 2011 (UTC)Reply
Okay. I'm assuming this has to do with the details of how the bot works? The {{IPA}} and {{R:Webster 1913}} templates are inline, and adding a bullet beforehand makes sense. The issue with {{ja-readings}} is that the template provides its own bulleted list. Quick sample with a leading * mark:
Interesting. Just as for {{ja-readings}}, {{Han ref}} ignores any leading asterisks or hash marks.
I'm curious -- what is the criterion the bot uses to determine if it should add a leading asterisk? From your initial comment, it sounds like there is a particular class of template that it uses? (And just in case it's at all unclear, none of this is criticism, I'm just interested in learning how bots work in the hopes of possibly making my own at some point. :) -- Cheers, 205.166.76.1517:25, 15 November 2011 (UTC)Reply
Mmh, I don't know, I'm just using a script which does nothing else but remove the template - of course that also means it runs really fast, as you may have noticed. -- Liliana•09:11, 22 November 2011 (UTC)Reply
If you think they need to be discussed anywhere, I'd be happy to open up a discussion on the GP. At least the first one should be uncontroversial, I added it in response to many IPs erroneously creating pages from the various archives search boxes (which always contain "prefix:" in some form). -- Liliana•18:04, 23 November 2011 (UTC)Reply
I think they need to be discussed, yes. Even a small change to MediaWiki:Titleblacklist is a huge change to Wiktionary: it creates a whole class of entries (and non-mainspace pages) that will silently be prevented from existing, with a good chance that we'll never even know if someone tries to create a valid one. —RuakhTALK18:12, 23 November 2011 (UTC)Reply
Latest comment: 13 years ago3 comments2 people in discussion
Could you add this to the list of "standard headers" so Kassadbot will leave it alone? Below is my comment from the recent BP discussion which doesn't seem to be that interesting to people lol. (Forgive the typo(s), I'm leaving the quote intact as it was there.) — — 14:44, 28 November 2011 (UTC)Reply
Category:Arabic verbal nouns should be left alone. It's a separate grammatical category in Arabic grammar, where noun a noun is an اسم(ism) and a verbal noun is a مصدر(maṣdar). — — 15:49, 27 November 2011 (UTC)
Latest comment: 12 years ago1 comment1 person in discussion
Could the bot be modified so that it corrects any instances of a bolded headword, replacing them with {{head}} with the current language as the only parameter? This would be preferred because it adds the script template as well as the lang= XHTML attribute to the text. —CodeCat15:07, 6 January 2012 (UTC)Reply
subst
Latest comment: 12 years ago1 comment1 person in discussion
I think it didn't work because it was inside <includeonly> tags. That would prevent the parser from evaluating anything inside it until the template is transcluded. —CodeCat18:10, 21 January 2012 (UTC)Reply
Proto and conlang language templates
Latest comment: 12 years ago5 comments2 people in discussion
The one you linked there was I think the only conlang template with a link, since none of the others do from a quick glance. The etymology templates work differently, they link to Wikipedia, should they be unlinked as well? -- Liliana•15:23, 22 January 2012 (UTC)Reply
Though in the Beer Parlour, I didn't support this. I merely supported removing wikilinks from language templates, not having a bot de-link language names in translation tables. A wholly different thing. Just saying y'know. Mglovesfun (talk) 17:27, 22 January 2012 (UTC)Reply
Thanks for that link. But I was wondering where you got the idea that we don't cite letters, while removing a citation from u.
That discussion was interesting and potentially useful, but not conclusive; in fact, there are arguments in support of having citations of letters, including "I'd like to see earliest citation of J/j - middle ages from Spain I think". --Daniel17:36, 24 January 2012 (UTC)Reply
Historical citations might be interesting, but certainly not ones from a modern book. Everyone knows how the letter u is used today. -- Liliana•17:42, 24 January 2012 (UTC)Reply
Latest comment: 12 years ago27 comments3 people in discussion
I haven't seen very many items appearing on the cleanup lists that I usually work: entries without inflection templates, translation table errors, structure errors. Have we eradicated all such error-making in the entries being edited? Are they no longer being sought? Is Kassadbot not running? DCDuringTALK22:28, 9 February 2012 (UTC)Reply
I can make it ignore pages containing the list template, but that would get kind of annoying if the template becomes widespread. -- Liliana•22:59, 9 February 2012 (UTC)Reply
I haven't seen much from Kassadbot lately. Is it running? If not, are there too many instances of {{list}} or is there some other problem? Can it be made to ignore {{list}}? I wish I could help. DCDuringTALK23:50, 19 April 2012 (UTC)Reply
If this is indeed related to the problem with patrol-tokens that admins have seen while trying to use the patrolling enhancements, then the problem is probably intermittent. Liliana, can you try again? —RuakhTALK13:59, 25 April 2012 (UTC)Reply
Yup. And as I've noticed, the saving bug still seems to be there, but the developers are already aware of it, now I just need to hope they'll get it fixed soon. -- Liliana•22:17, 30 April 2012 (UTC)Reply
Or you could use something like {{{1|Template:DUMMY}}}/script, to redirect such cases to a dummy template. This would allow the use of Whatlinkshere to fix erroneous usage. -- Liliana•15:56, 15 February 2012 (UTC) (addendum: there should be no language templates without corresponding script template, should there? )Reply
No, there shouldn't be, which is why {{Xyzy}} uses a convenient {{Eror}} template to make it simple to track down such cases. Using {{head}} without a {{{1}}} parameter is acceptable usage, so I don't see how causing those cases to link to Template:DUMMY/script would be helpful. --Yair rand16:05, 15 February 2012 (UTC)Reply
As a replacement for Xyzy? (I'm assuming that it's just the same as Xyzy without transcluding the langprefix.) That seems kind of unnecessary, and {{head}} technically is used in the exact situations where langprefix is required, I think. (Whatever happened to that proposal to get rid langprefixes entirely?) --Yair rand16:21, 15 February 2012 (UTC)Reply
Oh no, there's {{inflx}} (which should be renamed to headx, I suppose) for cases where langscript is required. And about that proposal to get rid of langprefixes, it got nowhere, as nobody was brave enough to actually get something started. -- Liliana•16:25, 15 February 2012 (UTC)Reply
For English entries that don't need the headline template to categorize or anything, having the language code added wouldn't do anything. --Yair rand20:26, 15 February 2012 (UTC)Reply
Latest comment: 12 years ago5 comments5 people in discussion
Barnstar
For taking care of a huge amount of the bot work, building up the largest page on Wiktionary, improving Wiktionary's templates an enormous amount, improving policies, and of course adding and fixing loads of content, I award you this long overdue Barnstar. --Yair rand01:57, 16 February 2012 (UTC)Reply
Congratulations! You deserve it! You managed to unblock yourself earlier today before I got worried enough to unblock you. Side note, I think it's bizarre that, even when a person is blocked, they can access enough controls to unblock themselves. - -sche(discuss)02:20, 16 February 2012 (UTC)Reply
It kind of depends on what operating system you use. I cannot see that from here. -- Liliana•23:53, 3 March 2012 (UTC) (also, just if you're able too, mind checking out WT:IRC to make the discussion easier?)Reply
Eh, for Windows all you need to do is follow the link provided and download the Windows Installer and run it. It cannot really get any easier. (Just make sure you pick the 2.x version!) -- Liliana•23:56, 3 March 2012 (UTC)Reply
Plautdietsch
Latest comment: 12 years ago3 comments3 people in discussion
Hallo Liliana... hab' wieder was bemerkt. Das Plautdietsche ({{pdt}}) ist schon in einigen Einträgen, wie ], als eine plattdeutsche (also {{nds}}) Mundart betrachtet worden. Dafür spricht, dass es eine plattdeutsche Mundart ist, und dass es kein Category:Plautdietsch language gibt. Dagegen spricht, dass Lekte, die ISO-Kürzel besitzen, normalerweise eigene ==L2-Headers== haben. Gibt's eine Policy? Should Template:pdt have its own ==Sections==? Bleifrei (talk) 05:49, 4 March 2012 (UTC)Reply
Es hat einen eigenen Code, also wird es erstmal als eigene Sprache betrachtet, solange nichts anderweitiges diskutiert wurde. -- Liliana•14:45, 4 March 2012 (UTC)Reply
Ok, thank you. I've modelled Template:etyl:qfa-fur for the Fur language family (not to be confused with the Fur language) on that. I'm creating language names (A-Pucikwar, etc), most of which derive from the languages named, thus I'm creating new etyl cats and it's necessitating the creation of family codes we've never had before. - -sche(discuss)20:30, 2 April 2012 (UTC)Reply
We want to bring 100-150 people together, including lots of people who have not attended such events before. User scripts, gadgets, API use, Toolserver, Wikimedia Labs, mobile, structured data, templates -- if you are into any of these things, we want you to come!
I also thought you might want to know about other upcoming events where you can learn more about MediaWiki customization and development, how to best use the web API for bots, and various upcoming features and changes. We'd love to have power users, bot maintainers and writers, and template makers at these events so we can all learn from each other and chat about what needs doing.
Latest comment: 12 years ago4 comments2 people in discussion
Several of our entries currently speak of Yolngu in their etymologies or translations sections (e.g. yidaki, east), but I can't find a code for that language, and Ethnologue seems to consider Yolngu (Yolngu-Matha) a family. Should we create a code for Yolngu, or recategorise (how?) the Yolngu terms we currently have? - -sche(discuss)04:04, 18 April 2012 (UTC)Reply
Good grief, I haven't ventured into the world of Australian languages before... it's basically one huge mess. The best way to deal with it, I think, would be to create a family code for Yolngu languages, and to use that in the etymology sections for now. -- Liliana•04:50, 18 April 2012 (UTC)Reply
Latest comment: 12 years ago2 comments2 people in discussion
I think I named this correctly, for use by {{aad/family}}: "iwm" for "Iwam", "paa" for Papuan. Papuan isn't a genetic family, but it's a family-of-convenience we also use for paa-msk, paa-etf and paa-kag. Iwam isn't a top-level division of Papuan, but the family it is a division of, Sepik, is only hypothetical. So, did I get it right? I am determined to learn our naming system. - -sche(discuss)21:26, 26 April 2012 (UTC)Reply
Latest comment: 12 years ago3 comments2 people in discussion
Hi. The bot is incorrectly adding ": " directly after "Serbo" in "Serbo-Croatian" and that yields "Serbo: -Croatian". See for example: this diff or this diff! I think it parses "Serbo" as a language of its own, but you will know better. Just wanted to let you know so you make the necessary adjustments to bot's code. I say necessary since I believe they are - editors might make the same mistakes as I did and omit the ":" after language names such as "Serbo-Croatian" is. Cheers, --BiblbroXдискашн10:35, 5 May 2012 (UTC)Reply
Latest comment: 12 years ago5 comments2 people in discussion
Hi Liliana, KassadBot is putting the Mutation header at L4 (e.g. here, but it makes more sense at L3, since the mutations apply to all parts of speech. If we put them at L4, we'd have to put them separately under Verb and Noun, which would be redundant since they're identical. Can we promote Mutation to L3? —Angr21:18, 13 May 2012 (UTC)Reply
Hi, it's still changing the Mutation header to L4 whenever an entry has two etymologies. But as far as I can tell, it doesn't do that for other spelling-dependent headings like Anagrams. At User:AutoFormat/Headers the settings for Anagrams and Mutation look the same to me, but the bot thinks Mutation depends on etymology but knows that Anagrams don't. Why? —Angr07:34, 5 June 2012 (UTC)Reply
Latest comment: 12 years ago9 comments3 people in discussion
Are you sure it's katakana? The only example I've ever seen of this is in the first sentence of its article on 'pedia, where its name is clearly written in hiragana. Do you have evidence otherwise? --Μετάknowledgediscuss/deeds19:09, 6 June 2012 (UTC)Reply
I have no direct knowledge of the Yaeyama dialect, but ツブリ (tsuburi) is also an alternate word for head in regular Japanese, generally spelled 頭 in kanji and つぶり in hiragana, deriving from つぶ(tsubu), which is both a noun meaning "small round thing" and a verb meaning, variously, "to be round, to become round, to go bald (i.e. for one's head to become smooth and round)".
Interesting. I did some digging around, and it looks like the JA WP article on the Ryūkyūan languages at w:ja:琉球語 has this to say at w:ja:琉球語#.E6.96.87.E5.AD.97:
Modern Ryūkyūan (Ryūkyū dialects) are often written using the Japanese mixed kanji / kana notation, and there is no established orthography for Ryūkyūan (Ryūkyū dialects). Words that diverge substantially from Japanese notation are sometimes written using kanji of the corresponding meaning.
That last sentence describes how kanji came to be used for Japanese in the first place, which is how come you sometimes have a "single" word as written, but that actually has several different readings, all with independent etymologies and connotations. (See 食物 for one fun example.)
Latest comment: 12 years ago9 comments2 people in discussion
I noticed that KassadBot has rfc-header marked a bunch of words I created as a newbie, because I used the header 'Derivatives' instead of 'Derived terms'. So I don't have to fix these manually, can you get your bot to replace all 'Derivatives' headers with 'Derived terms', and remove the rfc-header line that it inserted below the headers? --Μετάknowledgediscuss/deeds18:43, 11 June 2012 (UTC)Reply
I'm a bit puzzled as to why it tags them - User:AutoFormat/Headers specifically lists a bunch of common mistakes for "derived terms", and the bot should catch them, but for some reason, it doesn't. Strange. -- Liliana•19:14, 11 June 2012 (UTC)Reply
Mmm... but I see that "Derivatives" was only added to the list in May, and all these were tagged before... and since the bot has no reason to come back to check old entries, they kind of linger there. -- Liliana•19:32, 11 June 2012 (UTC)Reply
That sounds like a good idea. Now that I've culled a bunch, there probably aren't more than a dozen such entries anyway, but I want a bot to do it just so I don't miss any. --Μετάknowledgediscuss/deeds20:26, 11 June 2012 (UTC)Reply
Latest comment: 12 years ago4 comments3 people in discussion
I've just noticed your bot has added {{defn}} to a number of word form pages in Latvian (e.g., ausi, ausīm). Since these are word forms, not lemmas / entries, I think there is no need for a definition: the main entry (to which the word form page is linked) provides the definition. If you agree, then would you mind removing {{defn}} from these pages? Thanks in advance! --Pereru (talk) 08:32, 13 June 2012 (UTC)Reply
They still need to be formatted like all other entries - i. e. use the hash, not the asterisk. If you use the asterisk, the bot can't recognize the definition and will think there is none. -- Liliana•11:19, 13 June 2012 (UTC)Reply
Latest comment: 12 years ago6 comments3 people in discussion
Why not have this? It is useful for English etymologies, distinguishing a separate path for derivations. It is not identical to Quebec French, either, AFAICT. DCDuringTALK16:28, 22 June 2012 (UTC)Reply
Canadian French has no ISO code. It does, however, have an etymology code, so you can use {{etyl|fr-CA}} to designate Canadian French derivations. -- Liliana•17:06, 22 June 2012 (UTC)Reply
Latest comment: 12 years ago2 comments2 people in discussion
Hullo. You said that un‐attestable Inflexions are permitted for living Languages if, for Example, at least the Infinitive is attestable, yes ? --Æ&Œ (talk) 00:15, 30 June 2012 (UTC)Reply
I wouldn't say that's a hard-and-fast rule, as there are some verbs in Dutch that don't seem to be used apart from the infinitive and maybe the participles. I would say that having a finite verb form would normally imply that the lemma form (which may be the infinitive) exists, though. —CodeCat01:20, 30 June 2012 (UTC)Reply
Adding lang=xx to IPA
Latest comment: 12 years ago5 comments2 people in discussion
Do you have permission to edit the page? If so, would you please add fa? And possibly a stupid question: where is "WP:AN" of this project and how should I request for edit here? --Z12:40, 12 July 2012 (UTC)Reply
My sources say: Austronesian -> Malayo-Polynesian -> Sunda-Sulawesi -> Malayo-Sumbawan -> Malayic. The Malayo-Sumbawan node is missing as of yet, and would have to be created. -- Liliana•14:38, 11 July 2012 (UTC)Reply
JA entries pose a bit of an organizational problem, as one lemma may have multiple etymologies and multiple readings and POSes. Various items that are usually L4 or lower according to WT:ELE, and would thus hierarchically only apply to the parent header, may actually apply to the whole entry. 今日, for instance, has three distinct etymologies, each with specific and readings. However, all three etyms have the same meaning, and the items listed under Coordinate terms apply equally to all three etyms.
The simplest way to indicate this would be to just have Coordinate terms at L3, on par with all of the etyms. However, this breaches WT:ELE and thus Kassadbot (and possibly other bots too) will demote the header (producing an entry that gives incorrect information) or mark the entry as needing attention.
Do you know of an elegant way to make this work? Should I bring this up at WT:GP or WT:BEER regarding making a change to WT:ELE? Or, since this seems to only affect JA (AFAIK), does this just require a tweak to Kassadbot?
Template:ckb/script should probably be ku-Arab, as it is a Kurdish variety. About pnb-Arab: it seems to exist, but it has no fonts defined, making it utterly useless. I'm not sure if ur-Arab is appropriate here. I'll do all the others. -- Liliana•22:07, 13 July 2012 (UTC)Reply
New language family insertion again
Latest comment: 12 years ago7 comments2 people in discussion
Okay, so I have come across another category on WantedCats that I remember well from the past when I was nowhere near bold enough to dabble in language category creation: Category:Kiput terms derived from Proto-North Sarawak. So, according to WP, we should have North Sarawakan as a subfamily of North Bornean? You were a great help with the creation of Malayic categories and such so I just wanted to ask if you could give a full layout (not including irrelevant individual languages of course) of the North Bornean branch so that I can fill any missing gaps. Thanks in advance. :) User: PalkiaX50 talk to meh13:29, 15 July 2012 (UTC)
P.S. Please suggest appropriate template codes for anything that is missing too, thanks.Reply
Hey, I got another case to sort out I believe. I was just about to create Category:Mvuba language, but I'd like some family confirmation and suggestions for any required etyl codes. So I guess the structure should be like this?
Do we need to go down that far? Central Sudanic is okay (and it already has a code, {{etyl:csu}}), but I'm not sure there is a need to differentiate between Western and Eastern, and even if the need arises later we can move the categories when that happens. -- Liliana•15:27, 16 July 2012 (UTC)Reply
Latest comment: 12 years ago4 comments4 people in discussion
Does KassadBot unlink indented language names in translations? I've noticed some trans tables that have no language-name links except in indented items. For example:
It could be done by regex (that is, by MglovesfunBot) if I/we can write a regex that won't interfere with anything outside of translation sections. I'd also need an unwikified list of entries that need treating. I seem to think I did something similar before for entries that use {{list}} and I haven't found any errors yet. Mglovesfun (talk) 15:03, 16 July 2012 (UTC)Reply
\n\{\{trans-top(\|.*)?}}\n((\*.*)\n)*({{trans-mid(?:\|.*)?}}\n)?((\*.*)\n)*{{trans-bottom(\|.*)?}}\n would seem to be a translation table in a context in which . isn't a newline. (Adjust for template redirects, I guess.)—msh210℠ (talk) 22:08, 22 July 2012 (UTC)Reply
New job for KassadBot
Latest comment: 12 years ago8 comments2 people in discussion
A bunch of entries (nearing 200) now use {{LDL}}, but many of them don't use the first (and only) parameter, which specifies a language code. Although this is not necessary, I think it would be much improved if they all did. So: can KassadBot extract the name of the language from the L2 header and use it to add the corresponding langcode as the first parameter to {{LDL}}? --Μετάknowledgediscuss/deeds19:01, 21 July 2012 (UTC)Reply
That's a pity. Ah well. One more thing: is/are KassadBot/you able to specifically categorise every page into category X that is already in a certain category Y and ends in the substring foo? --Μετάknowledgediscuss/deeds19:39, 22 July 2012 (UTC)Reply
Latest comment: 12 years ago2 comments2 people in discussion
I saw that some time ago you nominated the Hmong Daw lang cat for RFDO. However, I'm not sure if this is ok due to my lack of knowledge of the languages...we have 2 different codes for Hmong and Hmong Daw, per WP. WP says Hmong Daw is a dialect but should we be including it as such or as a separate L2? User: PalkiaX50 talk to meh23:20, 25 July 2012 (UTC)Reply
Latest comment: 12 years ago18 comments3 people in discussion
Hey again, these are some other problems I've come across while trawling through WantedCategories:
I was going to create Category:Ritarungo language but it seems that while we have a category for its family, we don't seem to have a code. Could you suggest one?
We have one English etymology listing Slavey as the source language. We have {{den}} for Slavey but...we already have a category for South Slavey. So does that mean we shouldn't really have an individual category for Slavey (no north-south differentiation)? Or is the opposite true? User: PalkiaX50 talk to meh02:28, 28 July 2012 (UTC)Reply
I'm not entirely sure on whether there is a need to differeniate between the Slavey dialects. Stephen might know, try asking him.
We're currently treating Khoisan as kind of a collective group, while it isn't anywhere close to linguistic it's very convenient this way to save us from having to create countless language family categories. -- Liliana•13:35, 28 July 2012 (UTC)Reply
I can see that, I mean we don't seem to have a code for the Yolngu Matha family.
Oh, I failed to realize the family has no code. Hmm. I think {{etyl:aus-you}} would be best. Hmm, Maasai sure has some strange etymologies. It shows one of the problems with the whole etymology category system; there's no end to them. Unsure what to do. Proto-Inupik? English Wikipedia doesn't know that language. What's it supposed to be? -- Liliana•18:05, 28 July 2012 (UTC)Reply
Slavey includes two main dialects, North Slavey (scs) and South Slavey (xsl). Slavey is like German, where there is a dialect continuum. North Slavey is made up of three main subdialects: K’áshogot’ıne (Hare), Sahtúgot’ıne (Bear Lake), and Shıhgot’ıne (Mountain). South Slavey also includes the subdialects known as Northern Alberta Slavey and Fort Nelson Slavey. They are all very closely related to Dogrib.
The difference in the Slavey dialects is in how five of the old Proto-Athabaskan consonants have come to be realized. The different dialects pronounce these sounds differently and each dialect has a different number and collection of consonants; South Slavey has one less vowel (no /ə/). This means that the dialects are very close to one another and they are not different languages, but each dialect spells words differently. However, I believe that is a Standardized Slavey (like High German), which can be studied, taught, and used to communicate with speakers of any of the dialects. —Stephen(Talk)19:58, 28 July 2012 (UTC)Reply
Ok then, so going by that, would it be best to just have the one Slavey category then, and indicate dialectal peculiarities within the one L2, similar to but indeed not quite the same as Serbo-Croatian? Or should they have separate L2's? User: PalkiaX50 talk to meh20:05, 28 July 2012 (UTC)Reply
It’s a difficult question. My feeling is that, at the moment, since we don’t have anyone who can speak Slavey to create entries and tables, we probably won’t be getting very many entries for Slavey, and those we get will probably come from printed sources that may not identify the dialect. So I think we should treat it as a single language for the moment, like we do with American and British English. In the future, if someone comes who wants to do a lot of work in Slavey, then he might want to separate it into North and South ... or he might not. —Stephen(Talk)20:26, 28 July 2012 (UTC)Reply
Hehe...fair enough, what would be a good code for it then? Also, are "Bantoid" and "Bantu" languages the same or what...? I'm getting confused about that. :/ If not, should we actually have a Bantoid category?
Bantoid is definitely missing and would have to be created. As for that Proto-Inupik, I still don't know what it is, and the present-day language of the same name isn't really helpful in determining that. Google Books returns one single hit for this language. Now if you could rfv etymologies... -- Liliana•16:37, 29 July 2012 (UTC)Reply
Well, there is the etymology scriptorium if that would be any help...so what would be an appropriate code for Bantoid? and Proto-Central New South Wales? Oh and what are your thoughts on adding or not adding divisions listed at the Eastern Nilotic languages WP page linked above? User: PalkiaX50 talk to meh18:28, 29 July 2012 (UTC)Reply
Latest comment: 12 years ago16 comments3 people in discussion
I noticed the edit summary to your recent edit of ].
How does specifying sc= in, say {{term}} (eg, lang=grc|sc=polytonic) improve the user experience over not specifying it? Does it speed up preparing the HTML? Does this also apply to ordinary Latin script or is Latin script a default for many languages that does not require lookup? DCDuringTALK19:14, 20 August 2012 (UTC)Reply
It saves one iteration of going through all of {{langprefix}}, thus it speeds up the page's loading process (if only marginally, but these savings can pile up!). It is not normally needed, but water is not a normal page. I have no idea if specifying sc=Latn directly has the same benefits. -- Liliana•19:30, 20 August 2012 (UTC)Reply
To satisfy my curiosity (and probably yours too), I performed a small test. Surprisingly, Latin is not assumed by default, meaning it iterates through the langprefix template for every language - even English. The difference, for only the English etymology section, is:
My speculation is that larger savings can be achieved by optimizing other sections like this - most notably the derived terms section. -- Liliana•20:00, 20 August 2012 (UTC)Reply
I'm not sure what you are comparing in the table. Is that processing an entire page, without specifying sc= ("before") vs with sc= ("after")?
Is it not true that {{t}} and {{l}} also use {{Xyzy}}?
For all English words without a translation table, but with an etymology section, it would seem feasible to completely eliminate the need to call {{Xyzy}}, by specifying "sc" for the few words using non-Latin script that are specified using {{term}} (or {{l}} ?) and making sure that lang=en (or blank) defaulted to Latin script.
Eliminating calls to a template also means that changing it is a bit less consequential. Our push to standardize, however desirable it may be in total, certainly increases our dependence on whatever feature of the MW software our templates depend on and on the technology adepts who grasp it all. DCDuringTALK20:38, 20 August 2012 (UTC)Reply
Yes, these are page statistics, before and after. {{t}} and {{l}} both also iterate through Xyzy. The latter always does this no matter what, it seems, but I've asked Ruakh about it: User_talk:Ruakh#.7B.7Bl.7D.7D. Unfortunately, like always, he is in a complete disagreement with me. -- Liliana•20:41, 20 August 2012 (UTC)Reply
But then you would lose the link to the English section. This is annoying especially for users who use the tabbed languages feature. -- Liliana•20:46, 20 August 2012 (UTC)Reply
But why doesn't that default to the English section, too. Defaults can be so economical when one kind of thing is much more common than any of the others. DCDuringTALK21:40, 20 August 2012 (UTC)Reply
This on the other hand might be worth discussing further, especially since it would solve a lot of problems relating to links, like us having plain links in definitions. -- Liliana•04:16, 21 August 2012 (UTC)Reply
I don't really understand how writing {{#if:{{{1|}}}|{{{1}}}|en}} instead of {{{1}}} inside {{l}} would be an improvement at all... —CodeCat10:06, 21 August 2012 (UTC)Reply
Isn't something that executes within a template very quick? How much burden is the extra length of code? Speeding up the rendering of the HTML for the longest entries would seem to be paramount. (] can serve as our miner's canary in this regard.) Most of the longest entries have very large English sections, which are being threatened with the burden of unlimited use of {{l}}. The fact coincides with the fact that English is the most common lang= parameter specified, often by lack of specification, in the templates that require script information. Thus there is some real potential benefit to exploiting the idea of a simple default assumption.
It seems to me that, if you want whatever advantages some users might get from tabbed languages and need {{l}} for that purpose or other purposes, it would behoove you to minimize the burden that {{l}} seems to impose. The baroque template system that we have for language codes and script codes requires an enormous number of templates (a number apparently beyond the normal assumptions about maintainability in the Mediawiki software) and an even more enormous number of instances of template use in entries. Some consideration of efficiency (and maintainability once those who have perpetrated the system have moved on) seems in order.
Frankly, if the "all languages" part of our slogan proves to be a bridge too far or is rendered obsolete by other developments in software, I hope that at least Wiktionary's coverage of the English language can survive in the new world to play a useful role for the broad population of human users interested in English or most comfortable in English. Limiting the dependence of the English portion of Wiktionary on a baroque template structure seems like a wise precaution. DCDuringTALK11:07, 21 August 2012 (UTC)Reply
I had been thinking more of a JS which appends #English to all links which do not link to any particular section in the main namespace. -- Liliana•14:31, 21 August 2012 (UTC)Reply
I'm not really happy with relying on JS so much. It doesn't work for everyone, and it's slow to run the scripts on the page. —CodeCat14:57, 21 August 2012 (UTC)Reply
Latest comment: 12 years ago4 comments2 people in discussion
KassadBot has been tagging ===Aspect==== with {{rfc-header}}, but it's a legitimate POS, at least in Tahitian. Can you fix it so that it doesn't do that (preferably only giving the exception to Tahitian)? Thanks! --Μετάknowledgediscuss/deeds02:09, 28 August 2012 (UTC)Reply
Eh... has ===Aspect=== been discussed in the BP or TR? If not, it should be. Hebrew also could have had a number of other headers, but it was decided (in very old discussions) to "equate" them to headers we already used. Of course, some of the editors who were most opposed to headers that were technically more accurate but less intelligble to commoners haven't edited in years (even though one still has checkuser rights...hmm, I need to start a BP discussion about that), so the community may be more receptive to adding parts of speech, now. - -sche(discuss)02:25, 28 August 2012 (UTC)Reply
Well, they're obviously not prefixes or suffixes (those have to be connected to the main word). Particle might be the best fit after all. I still think that aspect is the most accurate, but we don't have any real Tahitian speakers to weigh in (I can write a little, but only with a dictionary :). --Μετάknowledgediscuss/deeds02:52, 28 August 2012 (UTC)Reply
German R
Latest comment: 12 years ago1 comment1 person in discussion
Conrad was trying to discourage reference to other wiktionary namespaces, wikiprojects, or external links. Can we do so in a less counter-intuitive way and also without building yet another potentially widespread templates-calling-other-templates complex? I know text-parsing functions are considered too expensive. DCDuringTALK21:51, 2 September 2012 (UTC)Reply
Latest comment: 12 years ago3 comments2 people in discussion
I need to create proto templates for Proto-Nuclear-Polynesian (PNP) and Proto-Eastern-Polynesian (PEP), but I don't know if there's a naming tradition that I ought to follow or a reason that they haven't been created. Do you know? --Μετάknowledgediscuss/deeds01:21, 5 September 2012 (UTC)Reply
Yeah . . . I've had another idea, which I think maybe looks better. (And part of the ugliness before, I now realize, is that due a recent MediaWiki software change, the notes were now center-aligned, where before they had been left-aligned. I just had to modify the template to fix that aspect of it.) Thanks for your help. —RuakhTALK14:32, 23 September 2012 (UTC)Reply
special colon
Latest comment: 12 years ago2 comments2 people in discussion
I seem to recall you mentioning in the Grease Pit or Beer Parlour a while back that Unicode had encoded a special colon for languages which use the colon as a letter, and that this colon worked in entry titles, unlike ":". Is that letter-colon U+A789 "꞉"? If so, I'll update saguaro. - -sche(discuss)15:50, 23 September 2012 (UTC)Reply
Mandarin terms needing attention is hardcoded for all Han characters which are not identified as Japanese or Korean. I guess that needs to be changed. On top of that, User:AutoFormat/Languages is missing Goguryeo, which is why the bot failed to retrieve the language code. -- Liliana•19:41, 24 September 2012 (UTC)Reply
Latest comment: 12 years ago2 comments2 people in discussion
This person created some "Zazaki" content last week, using a language code that we have defined as "Southern Zazaki". You seem to be good at sorting out random obscure languages that no-one's ever heard of; do you think you could take a look?
Latest comment: 12 years ago3 comments2 people in discussion
I deleted ԓы̄ as RFV-failed. Skvodo also created a number of other yrk entries with those 'incorrect' characters, as well as some other dubious entries. Should the other yrk entries be RFVed, or would you prefer to just delete them as incorrect / no-usable content given? - -sche(discuss)03:06, 30 September 2012 (UTC)Reply
Done :) Category:North Bornean languages is now completely spilt into the North Sarawakan and and Sabahan subfamilies. User: PalkiaX50 talk to meh 16:03, 15 July 2012 (UTC)