Open main menu

Wiktionary β

Wiktionary:Grease pit/2017/February

< Wiktionary:Grease pit
discussion rooms: Tea roomEtym. scr.Info deskBeer parlourGrease pit ← January 2017 · February 2017 · March 2017 → · (current)

Contents

Table Templates concerning Playing Card SuitsEdit

Could "Template:table:suits" be renamed to "Template:table:French suits"? It's just so it could be distinguished from "Template:table:Spanish suits", which I believe ought to be renamed to "Template:table:Latin suits" per Pagat. (Speaking of table templates, there ought to be two table templates named as follows: "Template:table:German suits" and "Template:table:Swiss suits".) --Lo Ximiendo (talk) 18:57, 1 February 2017 (UTC)

Template:glossEdit

Template:gloss currently produces the following output: (this is an example). Does anyone have an objection to enclosing the gloss in quotation marks [(“this is an example”)] so that it matches other glosses generated by templates such as {{compound}} and {{m}}? (@IvanScrooge98.) —This unsigned comment was added by Smuconlaw (talkcontribs) at 18:24, 3 February 2017‎.

@Smuconlaw: Yes, I object, because {{gloss}} is most often used to provide a disambiguator rather than a true gloss. For example, the definition of njetopyŕ is given as "[[bat]] {{gloss|small flying mammal}}", but bat doesn't actually mean "small flying mammal". Instead, the {{gloss}} tag is there merely to indicate which sense of bat is being referred to. —Aɴɢʀ (talk) 17:19, 5 February 2017 (UTC)
Is that different from a "true gloss"? I wouldn't have thought that the placement of any gloss within quotation marks (as templates like {{m}} do) implies that the gloss is exhaustive. — SMUconlaw (talk) 17:29, 5 February 2017 (UTC)
I guess the crucial difference is that {{gloss}} is usually used after English words, while the t= parameter of templates like {{m}} is usually used after non-English words. In "{{m|dsb|njetopyŕ|t=bat}}", ‘bat’ is a full definition, a full translation, of the dsb word, while in "[[bat]] {{gloss|small flying mammal}}", ‘small flying mammal’ (and even more so in "[[bat]] {{gloss|animal}}"), the so-called gloss is really just providing enough info so the reader knows we're not talking about a baseball or cricket bat. —Aɴɢʀ (talk) 18:37, 5 February 2017 (UTC)

Template:IPA letters gives spurious error in previewEdit

Template:IPA letters seems to give an "invalid IPA character" error in preview mode, though the saved page works fine. I encountered this when editing BBC. Equinox 12:21, 4 February 2017 (UTC)

{{IPA letters}} uses {{IPA}}, which uses Module:IPA which has a function that finds invalid IPA characters, using the list of valid characters in Module:IPA/data/symbols. I recently added a preview-only message that lists the invalid characters. Till now, the entry would simply be tracked with Module:debug. I'm not sure why the space is being considered an invalid character, because space is in the list of valid characters. Oh, it's because the template uses the HTML entity. I've added a rule to remove the HTML entity, so now the preview message no longer appears. — Eru·tuon 20:16, 5 February 2017 (UTC)
It's now giving an error message for g - plain ordinary English g typed on a keyboard. I know there's a preferred IPA glyph for g, but ordinary typed g should translate into it automatically. --46.226.49.228 10:45, 8 February 2017 (UTC)
The ordinary g has always given an "invalid IPA character" message, and it should, because it shouldn't be used in IPA transcriptions. It should be changed to ɡ wherever encountered inside {{IPA}} or {{IPAchar}} or {{rhymes}}. —Aɴɢʀ (talk) 11:24, 8 February 2017 (UTC)
The module is showing the position of the nonstandard characters instead of showing the characters themselves (see geliştir in preview mode). The error is on lines 137 and 138, result should be replaced with symbol. Redboywild (talk) 12:20, 8 February 2017 (UTC)
At this point, it's showing both the position and the characters themselves. But I'm about to fix geliştir. —Aɴɢʀ (talk) 13:21, 8 February 2017 (UTC)
@Redboywild: Oops. You're right. I've gone and implemented your recommendation. — Eru·tuon 20:21, 8 February 2017 (UTC)
Actually, the solution was somewhat more complicated. But now it works. @Angr, the obsolete or nonstandard characters part of the error message was showing the position, while the invalid symbols error message was showing the characters. Now both show the characters. — Eru·tuon 20:41, 8 February 2017 (UTC)

superhabitable planetEdit

How does this term get into the category Category:English 7-syllable words? It isn't. SemperBlotto (talk) 18:30, 4 February 2017 (UTC)

I imagine it has something to do with the invalid IPA the creator provided. DTLHS (talk) 18:31, 4 February 2017 (UTC)
The IPA has been fixed by Angr. Erutuon has explained to me that syllables like /bl/ and /kl/ have to be indicated like /bl̩/ and /kl̩/ to be counted as a distinct syllable. — SMUconlaw (talk) 17:35, 5 February 2017 (UTC)

Arabic root catsEdit

I've made {{ar-root}} automatically categorize entries in categories for root, such as Category:Arabic terms belonging to the root ك ت ب. Now there are lots of redlinked categories in Arabic entries.

Is there a bot that could automatically create the categories? They simply need to have {{ar-root cat}} or {{auto cat}} placed in them. — Eru·tuon 04:58, 5 February 2017 (UTC)

Done. DTLHS (talk) 17:38, 5 February 2017 (UTC)

VectorbosonEdit

This German noun is a member of the category Category:German nouns with red links in their declension tables. Not true; the links are green. SemperBlotto (talk) 07:50, 5 February 2017 (UTC)

The links are green because of the entry creation tool. They're red links in the sense that there's no page there, I guess. — Eru·tuon 08:52, 5 February 2017 (UTC)

The “New title” text box in a renaming page disappearsEdit

I cannot easily rename pages probably because of JavaScript for years, only on English Wiktionary. I cannot see the “New title” text box after the renaming page is fully loaded. Why is that?… I always have to hit ESC at the right moment to see it. — TAKASUGI Shinji (talk) 15:51, 5 February 2017 (UTC)

Could you provide a screenshot? DTLHS (talk) 20:17, 5 February 2017 (UTC)
 
A screenshot of the Wiktionary move page, showing the invisibility of the namespace and title fields.
The same is happening to me. Here's a screenshot. — Eru·tuon 20:24, 5 February 2017 (UTC)
I do not see that (tried Chrome, Edge). Maybe it's different for administrators? What does the HTML say? DTLHS (talk) 21:00, 5 February 2017 (UTC)
<div class="oo-ui-fieldLayout-body"><div class="oo-ui-fieldLayout-header"><span class="oo-ui-labelElement-label">New title:</span></div><div class="oo-ui-fieldLayout-field"><div id="wpNewTitle" aria-disabled="false" class="oo-ui-widget oo-ui-widget-enabled mw-widget-complexTitleInputWidget" data-ooui="{&quot;_&quot;:&quot;mw.widgets.ComplexTitleInputWidget&quot;,&quot;namespace&quot;:{&quot;id&quot;:&quot;wpNewTitleNs&quot;,&quot;name&quot;:&quot;wpNewTitleNs&quot;,&quot;value&quot;:2,&quot;exclude&quot;:[-2,-1,2600]},&quot;title&quot;:{&quot;id&quot;:&quot;wpNewTitleMain&quot;,&quot;name&quot;:&quot;wpNewTitleMain&quot;,&quot;value&quot;:&quot;Erutuon\/sandbox2&quot;,&quot;suggestions&quot;:false}}"><input type="hidden" name="undefined" value="0"><div id="wpNewTitleMain" aria-disabled="false" class="oo-ui-widget oo-ui-widget-enabled oo-ui-inputWidget oo-ui-textInputWidget oo-ui-textInputWidget-type-text oo-ui-textInputWidget-php mw-widget-titleInputWidget"><span class="oo-ui-iconElement-icon"></span><span class="oo-ui-indicatorElement-indicator"></span></div></div></div></div>
Well, here's the HTML, I think, for the part that isn't showing. — Eru·tuon 21:09, 5 February 2017 (UTC)
Any potentially interfering gadgets turned on? --Yair rand (talk) 07:15, 7 February 2017 (UTC)
Doesn't happen for me. Tried disabling all third-party (non-wiki) settings like ad blockers, just in case? Equinox 09:46, 7 February 2017 (UTC)
I’ve confirmed that it doesn’t happen when I turn off JavaScript. — TAKASUGI Shinji (talk) 12:50, 7 February 2017 (UTC)

Problem solved. Thank you all. I turned off “When moving pages, use the namespace-qualified title in the title box, and remove the separate namespace list” in my preferences and it works fine now. (@Erutuon) — TAKASUGI Shinji (talk) 13:43, 7 February 2017 (UTC)

@TAKASUGI Shinji: Ahh, I had that gadget enabled as well. Now that I turned it off, the move page displays normally. — Eru·tuon 18:57, 7 February 2017 (UTC)

Could someone please remove that gadget from the list of preferences until the bug is fixed? I don’t know where the list is. — TAKASUGI Shinji (talk) 23:42, 7 February 2017 (UTC)

I know there are lists of gadgets at Special:Gadgets and MediaWiki:Gadgets-definition, but not sure how gadgets get added to or removed from the list. — Eru·tuon 00:45, 8 February 2017 (UTC)
Removed. — TAKASUGI Shinji (talk) 02:16, 8 February 2017 (UTC)

Anchor gadgetEdit

The anchor gadget (MediaWiki:Gadget-U2693.js) is useful, but could an admin add subst: to the templates so that I don't have to type that in? — Eru·tuon 19:01, 6 February 2017 (UTC)

@Erutuon: What templates are you talking about? You're a template editor, so presumably you can fix them yourself. —Μετάknowledgediscuss/deeds 07:25, 7 February 2017 (UTC)
@Metaknowledge: Actually, it's a (JavaScript) gadget, and template editors don't have the right to edit them. See the link. — Eru·tuon 07:30, 7 February 2017 (UTC)
Oh, that was confusing. What I mean is the gadget produces copyable template code ({{unsigned}}), but it doesn't include the subst: before the template names, so you have to do extra typing after copying the template code. 07:40, 7 February 2017 (UTC)
Makes more sense, but I'm still confused. Why are you subst:ing these templates anyway? AFAIK, that's unnecessary. (Also, I find it annoying that template editors can't edit things other than templates — is it worth making a vote and filing a bug report?) —Μετάknowledgediscuss/deeds 07:58, 7 February 2017 (UTC)
@Metaknowledge: Oh, I was under the impression it had to be substituted. Apparently not, according to the template documentation. Perhaps substituting it is a Wikipedia custom. As to whether template editors should have the privilege of editing JavaScript gadgets – I for one don't have that much JavaScript knowledge, so I'm not sure either way. — Eru·tuon 10:38, 7 February 2017 (UTC)

Languages using punctuation as characters (Nivkh transliteration)Edit

I've tried writing a Nivkh transliteration module today, but I've come across a problem with its (single quote) character used to denote aspiration, the problem is that our modules (translit, headword) treat it as a word divider causing it to link the two parts of the word separately in headword lines and transliterating the word part by part. Normally this wouldn't cause problems, but in the case of Cyrillic e we need to differentiate between positions following a consonant and beginning a word, as one should be written e and the other je.

Take for an example к’еӄ, its transliteration ought to be k’eq, yet our current setup together with my module can only produce k’jeq.

Does anyone have an idea of how we could achieve this (or a reason for why a solution could be impossible)

Crom daba (talk) 20:26, 7 February 2017 (UTC)

This is a long-running problem which needs a solution for many languages. Compare this diff (the problem can be solved with use of the head= parameter here, but it's still a terrible default for Hän). —Μετάknowledgediscuss/deeds 20:45, 7 February 2017 (UTC)
Yes: don't use the curly apostrophe (U+2019) as a letter. Anytime something apostrophe-looking is used as a letter (in any language, not just Nivkh), we should be using ʼ U+02BC (MO­DI­FI­ER LET­TER APOSTROPHE). If you move к’еӄ to кʼеӄ, it should transliterate correctly. —Aɴɢʀ (talk) 20:46, 7 February 2017 (UTC)
That's a bad solution. Why should we be using a character that people who actually write in the language don't use? —Μετάknowledgediscuss/deeds 20:49, 7 February 2017 (UTC)
Because that's what it's there for. Cases like this are exactly why Unicode has two separate characters, one for the punctuation mark and one for the letter. It's not our problem if other people use the characters incorrectly; we should still use them correctly. We can leave hard redirects from the spellings using the wrong character. —Aɴɢʀ (talk) 21:28, 7 February 2017 (UTC)
People who actually write in the language is a somewhat hypothetical category for Nivkh, I doubt that there's a standard, be it official or conventional, of how computer Nivkh should be encoded. If no one gives a better reason I'll go ahead and start moving pages. Crom daba (talk) 21:32, 7 February 2017 (UTC)


Well, it works now, I've replaced all the apostrophes per Angr's suggestion (thanks), however that wasn't even the problem it was

text = mw.ustring.gsub(text, "([^Ѐ-ӿ])Е","%1Je")

text = mw.ustring.gsub(text, "([^Ѐ-ӿ])е","%1je")

the function of which I don't understand. I've added

text = mw.ustring.gsub(text, "([ʼ’])Е","%1E")

text = mw.ustring.gsub(text, "([ʼ’])е","%1e")

before it and it works now for both apostrophes.

Crom daba (talk) 23:38, 8 February 2017 (UTC)

JavaScript error on search pagesEdit

Hello, this error happens on search pages:

TypeError: mainNode is undefined in MediaWiki:SpecialSearch.js

Looks like the search box has been redesigned recently. The script should be updated, and additional checks added to avoid breakage in case of future DOM changes.

Regards, Od1n (talk) 13:36, 8 February 2017 (UTC)

Here is a fixed version of the script : User:Od1n/MediaWiki:SpecialSearch.js (history). Would an admin deploy it, please? Od1n (talk) 14:28, 9 February 2017 (UTC)
  Done. --Yair rand (talk) 19:30, 9 February 2017 (UTC)

Deprecated ISO 639-3 codesEdit

It seems that this was missed this year. The following codes have been deprecated by SIL and need to be removed from our language modules:

  • Rennellese Sign Language [rsi]
  • Shinabo [snh]
  • Rien [rie]
  • Lua' [prb]
  • Pu Ko [puk]

As well, there have been several new languages; I'll leave it to interested people to find these out and add them if there's demand. -- Pedrianaplant (talk) 15:38, 8 February 2017 (UTC)

What have these been replaced by? Do you have a link? —Aɴɢʀ (talk) 16:47, 8 February 2017 (UTC)
They were deleted outright; these languages do not exist. The summary for 2016's changes is here: http://www-01.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2016_Summary.pdf -- Pedrianaplant (talk) 16:52, 8 February 2017 (UTC)
I don't believe any of these have any current use in Wiktionary, so they can simply be deleted without any cleanup needed. DTLHS (talk) 16:56, 8 February 2017 (UTC)
We should first see if there's any merit to that though. We may have a different opinion than SIL. —CodeCat 17:02, 8 February 2017 (UTC)
Looking at the first one, that was deleted because it's just a bunch of private signs developed by one deaf person that never managed to develop a grammar structure or a sufficient vocabulary to actually form a language on its own merit. The other four languages could not be discovered by researchers in their respecitve region and are thought to be spurious. -- Pedrianaplant (talk) 17:09, 8 February 2017 (UTC)
After reading the reasons for deprecation for all the languages mentioned, I've deleted all the codes from the language modules. —Aɴɢʀ (talk) 17:14, 8 February 2017 (UTC)

Special:Nuke ("mass delete") is no longer workingEdit

It now has an additional form prompting for the user name, etc. However, the resulting list contains new entries from all users, not just the one I typed in the name box. Equinox 13:06, 9 February 2017 (UTC)

phab:T156949. --Yair rand (talk) 19:33, 9 February 2017 (UTC)

Undo tweaking of Vector top sectionEdit

Hello, please undo this change (so basically the Vector.css can be blanked).

Principle of least astonishment (aka. wtf muscle memory I clicked at the wrong place), the top section should not be different from all the other wikis…

Od1n (talk) 15:24, 9 February 2017 (UTC)

I don't think reverting this would be a good idea. Losing the definitions below the fold is a real issue, and we shouldn't waste critical screen space just to keep consistency with other projects. --Yair rand (talk) 19:26, 9 February 2017 (UTC)
1em doesn't change much about the "above the fold" (and the TOC eats all the space, so…). But current tweaks make that top section really narrow.
If you don't want to undo the whole thing, how about changing the offset from 1em to 0.5em? We still gain a bit of space, and it really makes the top section less messy.
Od1n (talk) 19:52, 9 February 2017 (UTC)

Porting and debugging of moduleEdit

Hi, I'm trying to port the Module:character info and {{Template:character info/new}} to Swedish Wiktionary (sv:Modul:teckeninfo, sv:Mall:teckeninfo). And have a few questions:

  1. Is it possible to invoke a module from another language Wiktionary? It would be great to automatically get all the updates immediately propagated.
  2. Right now invoking the copied module results in a timeout (see sv:Modul:teckeninfo). Unfortunately I have no idea how to debug this. Any tips on how I can find the errors?

Have a nice day :) –dMoberg 08:42, 11 February 2017 (UTC)

@Moberg: Maybe check if the Swedish Wiktionary has the last version of Module:character info, Template:character info/new, Module:Unicode data and all its subpages, as well as Module:scripts and all its subpages, including Module:scripts/data.
I believe one Wiktionary can't use a module from another Wiktionary (I even tested a bit and failed), but it seems eventually we could move all character names and image links to wikidata:, which I believe can be accessed by other wikis. I don't know how to do that. --Daniel Carrero (talk) 01:50, 13 February 2017 (UTC)
We are missing all the subpages to Module:Unicode_data. How can I copy them? (It feels like loads of work duplication tho :( ) –dMoberg 17:22, 13 February 2017 (UTC)
@Moberg: Module:Unicode data currently has 69 subpages. At least the way the modules are currently implemented, I'm afraid someone really is going to have to copy all of them to other Wiktionaries to use them, like this: Module:Unicode data/images/000 to sv:Modul:Unicode data/images/000, and so on. I don't know if it's feasible to use a bot or AWB to copy these pages.
I agree that this feels like loads of work duplication. (especially as more and more Wiktionaries have to copy the modules, like the Thai Wiktionary already did: th:มอดูล:Unicode_data/images/001) Currently, it seems we didn't install Wikidata access on Wiktionary yet. I created Wiktionary:Beer parlour/2017/February#Proposal: Implementing Wikidata access to suggest installing it, which should make things easier in the future if accepted by the community. --Daniel Carrero (talk) 19:13, 13 February 2017 (UTC)
Yeah I dont really feel like manually copying that amount of pages, with the risk of not getting it to work. I'm rooting for wikidata! :) –dMoberg 21:59, 13 February 2017 (UTC)
Really you should never copy pages wholesale from another wiki, you should import them. That way the edit history is maintained as is required by the licenses. It also has the benefit of doing most of the work for you. - TheDaveRoss 22:05, 13 February 2017 (UTC)
Import seems like a better alternative (although not needed for history keeping?) but still too cumbersome unless there is some way to import all subpages for a page (scripting?). Another problem is overwriting previously imported pages. I really hope this can be moved to wikidata as soon as possible. :) –dMoberg 19:25, 14 February 2017 (UTC)

Category:cs:OlomoucEdit

Hi. I have founded Category:cs:Olomouc but it seems that a new label needs to be added to the template:topic cat. I would like to ask for help with this since I really have no idea how to do it. Thanks. --Jan Kameníček (talk) 12:08, 12 February 2017 (UTC)

Are you sure this needs to be a topic category? Do you want something like Category:New_York_English ? Crom daba (talk) 12:17, 12 February 2017 (UTC)
I was thinking about something like Category:en:London or Category:en:New York City. --Jan Kameníček (talk) 12:27, 12 February 2017 (UTC)
Alright, but I don't think you should make it for a handful of entries.
You'll need to add it at Module:category_tree/topic_cat/data/Earth. Crom daba (talk) 14:01, 12 February 2017 (UTC)
Thank you. I am planning to add more entries soon. --Jan Kameníček (talk) 16:38, 12 February 2017 (UTC)

Fixing category-creation text to mention {{auto cat}}Edit

@CodeCat CodeCat created {{auto cat}}, which is very handy but isn't mentioned currently in the text at the top of a new-category page. Instead there's a list of the older (non-auto) catboilers. Can someone point me to the relevant page where this text is held? I searched around in the MediaWiki namespace but couldn't find it. Benwing2 (talk) 19:33, 12 February 2017 (UTC)

@Benwing2: I believe you are looking for these pages:
--Daniel Carrero (talk) 02:21, 13 February 2017 (UTC)
@Daniel Carrero OK, thanks. I added {{auto cat}} to Template:categoryboiler. I'm still not sure where the text above it gets set, but I suppose it doesn't need changing. Benwing2 (talk) 02:31, 13 February 2017 (UTC)
Finally, I've been meaning to do this for some time now. Crom daba (talk) 03:11, 13 February 2017 (UTC)

A new Labs Tool to visually explore etymological relationships extracted from the English WiktionaryEdit

Hi all! I have developed a tool to visualize etymologies. Please check it out at tools.wmflabs.org/etytree. My work is funded by an IEG grant. Please leave your feedback on the interactive tool here. It will help improve it.

It's is impressive how well automatic extraction of data works. This is because Etymology Sections are written using well defined standars. I would like to get some feedback about some difficulties I have encountered while extracting data and some ideas I have about new templates. I wrote some notes here. Please add your comment there if you have any.

Looking forward to your comments! Epantaleo (talk) 16:19, 14 February 2017 (UTC)

This is very interesting. I wonder if you have a list of etymologies that you found were impossible to parse? DTLHS (talk) 16:25, 14 February 2017 (UTC)
@DTLH: I don't have a list but from the visualizations you can clearly see that some of the sections are incorrectly parsed. Some of those mistakes are due to bugs in the code, others are due to imprecise etymological definitions. Consider also that while debugging I have corrected many etymology sections (see my contributions) and after those contributions I still have not updated the database. I still use a database extracted from the December 20, 2016 dump. Epantaleo (talk) 17:01, 14 February 2017 (UTC)
(answered also there in Meta) Awesome. Coincidentally and recently and unknowingly I have just tried to do that with GraphViz and Gephi, but introducing the data by myself. I just tried the uncreated en:wikt:Reconstruction:Proto-Indo-European/paw- (see What links here) < en:wikt:pavor (in order to get data, create the article and fill the gaps). My results are so alike... and you got what I sought so much. I'll try to have some time for more comments.
  • I'd suggest giving the option to choose different graph types (more linear).
  • And apply colours of distance from the lowest node (said knot?).
  • Do this cognates in boxes interrupt parsing? Do you process cognates? Can it find incoherences (two different nodes of the same language pointing into the same descendant)?
  • I also recently discovered template:etymtree]] and Template:findetym: can you feed them (there are less than 100 created)?
  • It could be used for Wikisaurus, as it is even more standardised. Sobreira ►〓 (parlez) 13:36, 17 February 2017 (UTC)

caché?Edit

After I did this and this, does the categories Category:Latin defective first conjugation verbs and Category:Latin defective second conjugation verbs update to you with new entries? (this worked with Category:Latin defective fourth conjugation verbs) Sobreira ►〓 (parlez) 12:47, 17 February 2017 (UTC)

  • Works perfectly (46 and 37 pages included respectively): Twas a problem of caché memory. Sobreira ►〓 (parlez) 09:08, 20 February 2017 (UTC)

Template:IPA reports invalid character on umzuzuEdit

It says that ḿ is not a valid character, but note that this is a syllabic nasal; the word has four syllables, the second and fourth are high toned. Can this be fixed? —CodeCat 23:32, 18 February 2017 (UTC)

The module returns an error because composed letters with acute accents are, properly speaking, not correct IPA: a plain letter with a tone mark diacritic should be used instead. You can enter the tone mark diacritics by placing the X-SAMPA shortcuts (in this case, _H) into {{subst:x2i}}. Or maybe we could add a full set of acute-accented letters into the "valid" list in Module:IPA/data/symbols. But using the correct character is best. — Eru·tuon 23:42, 18 February 2017 (UTC)
I see that the "valid" list in Module:IPA/data/symbols already has a lot of pre-composed characters. So you can add m with acute to the list. — Eru·tuon 23:44, 18 February 2017 (UTC)
Characters are input into Lua as precomposed characters, and are likewise converted to precomposed by the software when output. There are two functions, mw.ustring.toNFC and mw.ustring.toNFD which compose and decompose characters respectively. If the module has trouble handling precomposed diacritics, it should decompose them before doing any processing. —CodeCat 00:14, 19 February 2017 (UTC)
That would be true if the tone diacritics were the same as the plain diacritics, but they are not. m plus combining acute tone mark (0x341) is not converted to m with acute ( 0x1E3F). At least this seems to be true when I enter {{subst:x2ipachar|m_H}} (which yields ḿ): no error message is displayed. — Eru·tuon 00:29, 19 February 2017 (UTC)
The high tone mark is a different character from the plain acute (0x0301)? —CodeCat 00:33, 19 February 2017 (UTC)
Yes, and the low tone mark (0x340) is different from the combining grave (0x300). But now that I look, there are no distinct characters for the rest of the tonal diacritics. That's inconsistent. — Eru·tuon 00:41, 19 February 2017 (UTC)
Ow, my head. Unicode, why are you so broken at times? —CodeCat 00:46, 19 February 2017 (UTC)

Template:obsolete form of is brokenEdit

The parameter |nocap=1 doesn't function anymore. |nodot=1 does still work.
{{obsolete form of|term|lang=en|nocap=1|nodot=1}} becomes obsolete form of term with a capital O and not a non-capital o, and without a dot. -Wilhelm-231 (talk) 08:28, 19 February 2017 (UTC)

I fixed it. It was because the text "obsolete form of" had italics (''Obsolete form of''), which prevented the lcfirst: and ucfirst: magic words from working. — Eru·tuon 23:41, 19 February 2017 (UTC)

Warning: Other pages link to or transclude the page you are about to delete.Edit

This message turns up when deleting an entry, but I've come to ignore it, because if it's listed on RFV, then there'll be a link to WT:RFV. Is it possible to prevent this warning from appearing when the only links to the page are on WT:RFV, WT:RFD, or WT:RFDO? —Μετάknowledgediscuss/deeds 01:08, 20 February 2017 (UTC)

Ugly charboxes in mobile viewEdit

I'll leave this issue here in case someone's interested. After I was informed about it in my talk page, I was meaning to try to fix it but didn't do it yet.

The character boxes are very ugly when seen in a cell phone, and need some proper CSS formatting.

I'll leave a link to the asterisk entry in mobile view, as an example: https://en.m.wiktionary.org/wiki/*

--Daniel Carrero (talk) 20:47, 21 February 2017 (UTC)

By "ugly", I'm assuming you mean "of inconsistent widths"? ‑‑ Eiríkr Útlendi │Tala við mig 21:41, 21 February 2017 (UTC)
That's right. Yes, thanks for summing it up. Plus I'd like to add "float: right" in all these boxes, because apparently we currently have to scroll past all the boxes to start seeing the actual entry. Maybe the appendix name (like "Basic Latin") could be smaller, too. --Daniel Carrero (talk) 21:45, 21 February 2017 (UTC)
Mobile devices have very little width to work with, so floating things right won't go well for them. —CodeCat 21:59, 21 February 2017 (UTC)
I'm curious, is there any way from the server side to distinguish between tablets (which have more width) versus phones (which are quite skinny)? ‑‑ Eiríkr Útlendi │Tala við mig 00:18, 22 February 2017 (UTC)
I don't know, but at least I see that we have a whole CSS page specific to mobile view: MediaWiki:Mobile.css. Wikipedia has one too: w:MediaWiki:Mobile.css. If hiding content is needed, the Wikipedia page suggests this: "Do not use display:none. Instead edit the template and markup the element you want to hide with the `nomobile` class." --Daniel Carrero (talk) 08:21, 22 February 2017 (UTC)
CSS is capable by itself of using different rules based on the width of the viewport. —suzukaze (tc) 08:29, 22 February 2017 (UTC)
What about making the tables collapsible, instead of making them float to the right? That would make them take up less vertical space, and require less scrolling. — Eru·tuon 22:39, 21 February 2017 (UTC)

For what it's worth it seems like the Mobile CSS is designed to disable "float" and "width". —suzukaze (tc) 05:15, 22 February 2017 (UTC)

Template uxEdit

The template {{ux}} requires to fill the translation parameter, which is sometimes not possible. May I ask for suggestions how to solve -e#Etymology 2? Thanks. --Jan Kameníček (talk) 21:33, 23 February 2017 (UTC)

@Jan.Kamenicek: For suffixes, you can use {{suffixusex}} instead of {{ux}}. See my recent edits to -e. —Aɴɢʀ (talk) 11:02, 24 February 2017 (UTC)
That is exactly what I was looking for. Thanks! --Jan Kameníček (talk) 11:50, 24 February 2017 (UTC)

Left-to-right mark in Module:headword and Module:usexEdit

I'm puzzled by the inclusion of a left-to-right mark (&lrm;) in the output of Module:headword and Module:usex. This is unnecessary, since text direction for right-to-left languages is specified in MediaWiki:Common.css. I removed the left-to-right mark from Module:headword (though the edit summary is misleading; Module:script utilities no longer adds text direction markers, because they are unnecessary). It is a small thing to be concerned with, but I will remove it from Module:usex if there isn't a good reason for it. — Eru·tuon 10:26, 24 February 2017 (UTC)

Language-sensitive labelingEdit

I've added the necessary code to Module:labels and Module:labels/data/regional to allow categories to be restricted to a set of languages. You simply add a list of language codes to the data table, and {{label}} will only add the category to those languages. I've tested it with the label "Koine" (the only one that currently has a "languages" field) and it works: {{label|grc|Koine}} adds a category, while {{label|en|Koine}} does not.

Unfortunately, this does not yet allow the same label to be used by different languages with different content. I can't think of a case where this would be needed, but it should be possible. — Eru·tuon 07:15, 25 February 2017 (UTC)

Okay, an example in which different content for the same label would be useful: Doric, which should refer to Doric Scots when the language code is sco, and to Doric Greek when the language code is grc.

I am thinking that one way to have this feature would be to have a table of language codes, and under each language code, a list of labels associated with that language. If more than one language uses the label, one language's table would contain the label, while others would refer to it. For instance, the label "honorific" would have to be listed under either "zh" (Chinese), or "ja" (Japanese), or "ko" (Korean), or another language, and have the other languages refer to it. This idea would result in more complexity: there would be a table of non-language-specific labels, and another table of language-specific ones.

And I am not sure how the module could return an error if an editor tries to use a label in a language that does not allow it (for instance, using "honorific" in English). — Eru·tuon 00:46, 26 February 2017 (UTC)

I suppose the answer is yet another table of labels with a list of languages in which they can be used: such a table would include a table indexed by "honorific" containing { ["zh"] = true, ["ja"] = true, ["ko"] = true }. — Eru·tuon 00:50, 26 February 2017 (UTC)

A table for "Doric" would contain ["grc"] = true, ["sco"] = true, even though the contents of the Ancient Greek and the Scots label would be different. — Eru·tuon 00:51, 26 February 2017 (UTC)

This sounds like a pretty bad idea. We really don't want to have to list everything for every language, because that would swiftly become unmanageable. —Μετάknowledgediscuss/deeds 01:05, 26 February 2017 (UTC)
@Μετάknowledge: It would be messy to have it all written out, but it could actually be fairly simple if we have functions that do most of the work. — Eru·tuon 01:19, 26 February 2017 (UTC)
But we don't want to have to list out all the languages that use honorifics. We would doubtlessly forget some, and we shouldn't have problems when someone eventually wants to add honorific terms in a new language and can't figure out why it's failing to work. —Μετάknowledgediscuss/deeds 01:51, 26 February 2017 (UTC)
Okay, then that's a bad example. But the feature would definitely be useful for the label "Doric". — Eru·tuon 02:01, 26 February 2017 (UTC)

Labels in Module:labels/data/subvarieties can now be made available by adding a language = "<code>" field. Without the language code, they will be ignored by Module:labels/data (which gathers up all the labels from the submodules). I'm going to move the Ancient Greek labels there. — Eru·tuon 03:22, 26 February 2017 (UTC)

Could a sysop change the protection level of Module:labels/data/subvarieties to registered users? There's no longer a reason for protection, since it is functional and editors should begin adding or moving labels there. — Eru·tuon 20:13, 26 February 2017 (UTC)

@Erutuon:   Done. Please note that you still have label module errors left. —Μετάknowledgediscuss/deeds 21:42, 26 February 2017 (UTC)
@Μετάknowledge: Wow, the module errors really take a long time to clear up. They disappear once I preview the page. — Eru·tuon 21:45, 26 February 2017 (UTC)
However, I did break the label {{lb|_}}; it's now fixed. — Eru·tuon 22:10, 26 February 2017 (UTC)

Can somebody please fix this new topic category?Edit

Category:ko:Korean letter names. It has become difficult to add new topic cats. --Anatoli T. (обсудить/вклад) 10:12, 25 February 2017 (UTC)

@Anatoli T.: What's wrong with the category as it currently is? — Eru·tuon 01:27, 27 February 2017 (UTC)
@Erutuon: It's fixed, thank you. Not sure by who and what was done. I only changed the title - inserted a missing word. --01:31, 27 February 2017 (UTC)

Documentation for "Template:projectlink/Wikipedia"Edit

Would someone kindly create a documentation page for {{projectlink/Wikipedia}} (to which {{pedia}} redirects)? I cannot figure out from Module:wikipedia, which the template calls, what parameters the template takes. Thanks. — SMUconlaw (talk) 13:54, 25 February 2017 (UTC)

Duplicate label in Module:labels/dataEdit

The label British spelling appears twice in the module, so that when {{lb|en|British spelling}} is used, the result is (British) and not (British spelling). Could a sysop fix that by removing one of the two labels? — Automatik (talk) 14:34, 26 February 2017 (UTC)

Moved the correct form of the label to Module:labels/data/subvarieties (which is now functional). — Eru·tuon 20:12, 26 February 2017 (UTC)

Message at top of module pagesEdit

Hi, where does the message at top of module pages (with exisiting documentation page) come from? (See: Module:labels for example). I'm talking about the text that reads

"The following documentation is located at Module:labels/documentation. [edit]
Useful links: subpage list • transclusions • testcases"

I'm guessing it is a MediaWiki-page but I was only able to find MediaWiki:Scribunto-doc-page-does-not-exist. –dMoberg 20:53, 26 February 2017 (UTC)

@Moberg: I went to Special:PrefixIndex/MediaWiki:Scribunto and then to MediaWiki:Scribunto-doc-page-header and Template:documentation subpage and Template:documentation. Maybe the last is the one that generates this text? It uses Module:documentation. — Eru·tuon 21:26, 26 February 2017 (UTC)
@Erutuon: Unfortunately MediaWiki:Scribunto-doc-page-header does not show up at Module pages, at least not on Swedish Wiktionary. –dMoberg 21:42, 26 February 2017 (UTC)
@Moberg: MediaWiki:Scribunto-doc-page-header seems to be the content that shows up on documentation pages, including module documentation pages. Do you mean that the content in sv:MediaWiki:Scribunto-doc-page-header does not display on documentation pages on Swedish Wiktionary? — Eru·tuon 21:59, 26 February 2017 (UTC)
@Erutuon: I found it, it should be this message: MediaWiki:Scribunto-doc-page-show. Thanks for the help. –dMoberg 22:01, 26 February 2017 (UTC)
@Moberg: Oh yeah, there you go! And oops, I realize because MediaWiki:Scribunto-doc-page-header is prefixed with Scribunto-, it's only for Module pages. Glad I could help, however little I know about the subject. — Eru·tuon 22:15, 26 February 2017 (UTC)

Help adding new reference templateEdit

Hi,

I'm sorry if this is not the best place to request such help. I am unfamiliar with adding new templates, and I would like to start doing so. At the moment I'd like to add a new reference template, specifically a Tahitian reference template. I understand that I could simply troubleshoot, and possibly find the solution after more time and research; however, I have limited time, and I would also like to learn how to do this correctly the first time -- so that I will know the best possible manner to go about this in the future.

Additional questions:

  • Is there a feature/set of features that allows for automating some actions, such as adding a definition for a particular language to an existing page? By this I mean automating the following steps:
  1. Navigating to the translations for the word, e.g. headache, and adding the term for a non-preexisting language.
  2. Then navigating to the term's page itself, hoa.
  3. Adding a new section, language specific category and any additional information.
  • What is the best way to cite sources for terms on articles? I see a Citations tab at the top of each article. Is there an easier/more productive way to add many words from a single source - in this case, a dictionary - without having to add the same source to the Citations tab of each term's article? To clarify, I mean both the article for a term containing the translation table, e.g. headache, and the page for the term itself, e.g. hoa.

I greatly appreciate any and all assistance.

Thanks,

Tezamen (talk) 23:44, 26 February 2017 (UTC)

Answers to some of your questions: the citations tab should be used for uses of the word in print, such as newspaper articles, books, etc. This is distinct from a reference, which is placed on the main entry and is usually a link to another dictionary or other scholarly source. If you state the bibliographic details here someone can make a reference template for you, or you can look at some examples at Category:Reference templates by language. DTLHS (talk) 00:51, 27 February 2017 (UTC)
What type of reference would you like to create a template for? The list of citation templates, which are used to create reference templates, is found at Category:Citation templates. You simply choose the citation template that is most appropriate for your reference (for instance, {{cite-book}}) and place it at the page name Template:R:<reference name> or Template:R:<language code>:<reference name> (for instance, {{R:LSJ}} and {{R:ar:Wehr-4}}, two templates I happen to use often), and then fill out the parameters of the template as explained on the template documentation page. — Eru·tuon 01:05, 27 February 2017 (UTC)
Thank you both for your responses. @Erutuon: Would you use the latter template format (e.g. {{R:ar:Wehr-4}}) where the language code is the language in which the source is written? If not, what differentiates using this format from the format without the language code? The source for which I'm currently trying to create a template is a dictionary. The title is listed on the dictionary in both target languages; what is the best manner to handle this when formatting the reference? Would it suffice to only include the English portion of the title (e.g. English-Tahitian Dictionary)? Also, how do I handle a title that's formatted as: "English - Tahitian (newline) Tahitian - English (newline) Dictionary" in the reference itself? Here's what I have thus far, Template:R:ETD-Wahlroos
Thanks! Tezamen (talk) 02:10, 27 February 2017 (UTC)
@Tezamen: There seems to be no clear criterion determining whether the template name contains the language code. I would have thought that the language code would be used in cases where, without it, the reference name would be ambiguous, but I think there's no ambiguity in the case of {{R:ar:Wehr-4}} (Wehr's Arabic Dictionary).
The language code would be the language that the reference work is about. This case is odd because each half of the dictionary is about a different language. I think it is probably fine to give the title in English, as it is given on the Google Books page. Newlines should be ignored. — Eru·tuon 03:02, 27 February 2017 (UTC)
@Erutuon: Yeah, it would be useful to develop clearer criteria for when the inclusion of the language code is warranted, hmm. Regarding titling the reference, I understand that newlines are to be ignored -- I was simply trying to illustrate the formatting of the title as it is displayed on the book cover, and, moreover, was asking how I should format the title into the reference. Does the reference, as formatted in the template I made here, properly convey the title as it is on the cover here? To be clearer, should it be "English - Tahiti Dictionary" or something such as "English - Tahiti / Tahiti - English Dictionary" ? If the latter, how should I properly format it inside of the reference (i.e. Sven Wahlroos (2002) English-Tahitian Dictionary, First edition, Honolulu: The Mā'ohi Heritage Press, →ISBN ? Thanks! Tezamen (talk) 03:20, 27 February 2017 (UTC)
@Tezamen: I would use a comma and n-dash: English–Tahitian, Tahitian–English Dictionary. — Eru·tuon 04:12, 27 February 2017 (UTC)
@Erutuon: Thank you very much! Tezamen (talk) 23:40, 27 February 2017 (UTC)

Template:de-noun creates incorrect plural without parametersEdit

No parameters are given on Client, not even gender, but it's making a plural anyway and it's the wrong one. Can the template be fixed so that it no longer generates incorrect forms when no parameters are given? —CodeCat 19:31, 27 February 2017 (UTC)

list:Latin script lettersEdit

An IP has been generating and adding language-specific subtemplates for a lot of languages lately. One of the more recent ones was added to the Swedish section at e, which triggered "not enough memory" errors. Previewing the section containing this (and nothing else) shows that this uses 2.74 MB of memory. Obviously, that would make it impossible to use these templates on anywhere close to all 62 of the language sections on that page if it weren't for the fact that some of the memory use is shared between many of the module calls on the page.

Still, Latin-letter entries are inherently huge and resource-intensive, and having a type of template specifically designed to be used large numbers of times on each of these pages is tempting fate. Is there any way that these templates can be tightened up/rethought so they don't use so much memory? Chuck Entz (talk) 04:46, 1 March 2017 (UTC)

That's a ridiculously large amount of memory for one template. I wonder how that is happening: does every instance of {{l-self}} require the language object from Module:languages to be duplicated in memory? — Eru·tuon 04:54, 1 March 2017 (UTC)
In any case, it would be best to create a module that can generate letter and letter name templates in a consistent way. I think I'll work on that. — Eru·tuon 05:00, 1 March 2017 (UTC)
Oh, @Daniel Carrero has already created a module that does that, Module:letters. — Eru·tuon 05:05, 1 March 2017 (UTC)
I guess it's a work in progress. I used that module in appendices like Appendix:Letters/Portuguese. --Daniel Carrero (talk) 05:06, 1 March 2017 (UTC)
I don't understand how the module works exactly, but it seems like the only difference from the previous form of the existing series of templates {{list:Latin script letters/en}} is that it doesn't include the language's word for "letter". That can easily be fixed. — Eru·tuon 05:40, 1 March 2017 (UTC)

I've created a function in Module:letters that is called by {{letters/sandbox}}. It's ready for implementation in any languages that don't have digraphs or trigraphs in their alphabets. I have implemented it in a few Latin-script letter lists: {{list:Latin script letters/en}}, {{list:Latin script letters/fr}}, {{list:Latin script letters/sv}}.

It needs a better name. {{letters}} is a template for Appendices, while {{letters/sandbox}} is for entries. I will look into how they could be merged: the differences are the presence of the word for "letter" at the beginning of the list in {{letters/sandbox}}, and the categories added by {{letters}}. Those could easily be dealt with by the module.

I also need to decide on a way to deal with digraphs and trigraphs (for instance in the Hungarian alphabet: {{list:Latin script letters/hu}}). — Eru·tuon 09:23, 1 March 2017 (UTC)

I'd argue that it's much more efficient to delegate these entries to appendixes than to have them as entries. They aren't "words" in the truest sense, after all. Moreover, if we do so, then any actual words that are spelled with a single letter, like English a or Dutch u, will not be buried under relatively useless "letter" entries. —CodeCat 13:28, 13 April 2017 (UTC)