Wiktionary:Grease pit/2011/December

From Wiktionary, the free dictionary
Jump to navigation Jump to search
This is an archive page that has been kept for historical purposes. The conversations on this page are no longer live.

December 2011

A little problem with the one-line Perl dumper

As some of you may know, I have earlier created a free ePub/mobi (Kindle) English - English dictionary based on Wiktionary and CIDE (i.e. Webster's 1913 Unabridged with some additions). There's also now a Wiktionary only edition. Links to these are on my web page http://personal.inet.fi/koti/korhoj/.

I think there's a little problem in the Perl script that creates the dump file http://toolserver.org/~enwikt/definitions/enwikt-defs-latest-en.tsv.gz. Namely there are some entries that have spanning HTML comments and these aren't recognized. As a result, the dump has some dangling comment end tags. Such as in end of "Chelsea Proper noun # A type of porcelain once manufactured there." The comment continues in the next line like this: "A football club based there. Football clubs don't belong in Wiktionary" (click Edit to see it).

I couldn't think of an easy way to fix this and am not good in Perl anyway. Currently I just remove those entries which I can't convert to well-formed XHTML.

Korhoj 08:32, 2 December 2011 (UTC)[reply]

Tagalog and Indonesian

I am doing a comparative study of the vocabulary of Indonesian and Tagalog, two closely related languages. If I look up the Indonesian word pulih, the Wiktionary entry will say "Compare Tagalog puti" and if I look up the word bawang there will be entries for both Indonesian and Tagalog. Is there any way I can pull out all the Wiktionary entries which gives comparisons for both languages and entries for both languages, please? — This comment was unsigned. 

<DynamicPageList>
category=Tagalog nouns
category=Indonesian nouns
namespace=0
count=100
mode=none
order=ascending
</DynamicPageList>


tawa
ulam
kulit
bata
abaka
aral
pasok
halaman
titik
karpet
lumpia
balak
adik
agas
tahanan
lawa
batok
paksa
antok
hukuman
sapa
ilat
hikmat
babat
limpa
sikat
awak
gusi
arya
dupa
sabo
sambat
asal
timba
tukil
shabu
ulat
tawas
tapal
itik
kendi
tahi
yakis
sambal
tiket
pari
agrikultura
tulisan
dahan
tapak
liwat
galon
uban
babad
tatal
katedral
huma
donat
salin
nipis
plastik
martir
daulat
konyak
pasukan
alamat
kaba
kanal
lalim
ganti
sisi
balon
kriminal
karbon
astaka
modus
tato
kain
papan
bistek
hati
sarap
mula
pandan
gaban
gerilya
tawaran
toge
kulot
siomai
loka
bagal
harapan
datu
parak
kamisa
alam
ayam
dosis
sikap


Protect against users without autopatrolling permission

The current protection options for pages aren't really sufficient in some areas. Sysop protection seems too much in many cases and prevents many users from making useful contributions and fixes, but autoconfirm protection takes away our ability to keep a check on who is trustworthy enough to be allowed to make edits. It would be nice if there were an additional block option which allows editing as soon as the user is an autopatroller. Could this be added? —CodeCat 21:28, 9 December 2011 (UTC)[reply]

If I understand correctly, the software only supports two protection levels, "semi-protected" (editable by users with the autoconfirmed access right) and "protected" (editable by users with the protect access right, which also confers access to protect/unprotect/modify-protection-of a page). So I don't think we can add a new protection level in between. However, I think it is possible to change things so that members of the "Autoconfirmed users" group don't actually have the autoconfirmed access right; we'd have to file a Bugzilla ticket to make the request. —RuakhTALK 21:55, 9 December 2011 (UTC)[reply]
Purely out of curiosity, has there been a spate of vandalism by people who are auto-confirmed? I will also make the requisite statement concerning our desire to have as much of the project editable by as many people as possible yada yada yada. - [The]DaveRoss 21:03, 10 December 2011 (UTC)[reply]

Template:fro-decl-adj

The box doesn't need to be full width. I've looked into making it less, say 50%, but I can't work out how. Is it possible to just have it fit the width of the content of the table? Thank you, Mglovesfun (talk) 17:49, 11 December 2011 (UTC)[reply]

I used the CSS display:inline-block; but it doesn't work in IE7 (surprise). —Internoob 04:58, 12 December 2011 (UTC)[reply]
Thanks, I've rolled this out into a few other templates. Mglovesfun (talk) 14:46, 15 December 2011 (UTC)[reply]

WOTD RSS feed

When there is more than one definition in the WOTD, as there commonly is, the RSS feed shows only the first one, and when it has a term with a link inside it, it doesn't display anything. —Internoob 04:32, 12 December 2011 (UTC)[reply]

Is that true whether the link uses [[ or {{l}}?​—msh210℠ (talk) 18:11, 12 December 2011 (UTC)[reply]
I've not tried {{l}} but {{transitive}} breaks it too. —Internoob 00:50, 13 December 2011 (UTC)[reply]
I'll get back to you on that on December 19. —Internoob 02:00, 14 December 2011 (UTC)[reply]
{{l}} also breaks it. Anything with a link. —Internoob 20:49, 24 December 2011 (UTC)[reply]
So I guess delinking and putting the most interesting definition first work unless/until this can be fixed. Whose RSS feed is that, anyway?​—msh210℠ (talk) 18:48, 15 January 2012 (UTC)[reply]
It's Connel's. Here's the Toolserver page. —Internoob 19:09, 15 January 2012 (UTC)[reply]
But Conrad (I assume Irwin) is listed on that page as author. I've posted a note to his talkpage here.​—msh210℠ (talk) 00:43, 16 January 2012 (UTC)[reply]

The WOTD RSS feed appears to be stuck on February 17: ultracrepidarian. Is anyone else seeing this? Apologies if this is not the correct method/place to comment on this.

Some PREFS not working

In Wiktionary:Per-browser preferences, I have "Replace text in deletion log comment" checked - but it is not working. Is this related to the nasty look of the current site? SemperBlotto 08:37, 12 December 2011 (UTC)[reply]

Sorry about that. It was a bug in TabbedLanguages from the Mediawiki 1.18 upgrade. It's fixed now. --Yair rand 09:10, 12 December 2011 (UTC)[reply]

Having preloadable templates?

I am a very occasional user at Wiktionary, though do contribute widely through WMF. I find it difficult to quickly add simple entries, or to add citations due to not having ready ability to quickly insert data in the right format. In the end, it is easier to add nothing rather than try to struggle through when I come across old words from my efforts at Wikisource. I wonder whether your community had considered the use of Editnotice to preload templates/text. Here I am thinking of an example like how Commons uses their Creator template into their Creator namespace. If something could be preloaded into the right format for Citations, or for new words, so it is all preset I know that I would find it really useful. Even it was all within html comments, and I unblock the needed bits. — billinghurst sDrewth 03:08, 13 December 2011 (UTC)[reply]

User:Yair rand/newentrywiz.js is linked to whenever you search for a term which doesn't exist. Mglovesfun (talk) 14:24, 13 December 2011 (UTC)[reply]
That may be the case, it often isn't how I am arriving when I am building at Wikisource to link through archaic words. I probably go straight for the entry though a trial [[wikt:|]] style link. Would there be a means to get that javascript to be built into the editnotice component? Alternatively, could some of that be gadgetised as an alternative? Also for when trying to link from the word back to the presented word in the work at WS, it would be useful to have an easier citation schema. (… yes, I know that it is my laziness in a time-scarce world) — billinghurst sDrewth 01:21, 14 December 2011 (UTC)[reply]
You could add the following to your Special:MyPage/common.js:
if (wgAction == "edit"){
 var tosSummary = document.getElementsByClassName("mw-tos-summary")[0]
 tosSummary.innerHTML += "<pre> #*{{quote-book<br/>|year=<br/>|author=<br/>|title=<br/>|chapter=<br/>|passage=}} </pre>"
}
To display whatever you want for copy and paste just below the terms of service summary when you edit a page. What you have here is the code for {{quote-book}} but you can just change it. —Internoob 03:08, 14 December 2011 (UTC)[reply]

Lost the alpha-bar

I seem to have lost the "alpha-bar" (can't remember what it's really called — the JavaScript thing that loads after the main entry and shows you the previous and next few entries, like "Abba - abbey - abbeys - abduct - abducted"). I think this happened when the new visual layout appeared (the aforementioned Godawful boxes). Are the two things incompatible? Equinox ◑ 22:11, 13 December 2011 (UTC)[reply]

Well, I dunno what happened in December, but the alpha-bar is back. Hurrah! Equinox ◑ 22:58, 15 January 2012 (UTC)[reply]

gracility

The 'hide quote' function isn't working. Have tried clearing my caché, which suggests it is server side, not my computer. I use Firefox and have disabled the current admin-only trial. Mglovesfun (talk) 17:19, 14 December 2011 (UTC)[reply]

Works on my side. -- Liliana • 17:25, 14 December 2011 (UTC)[reply]
Yeah it's working now, weird! Mglovesfun (talk) 17:33, 14 December 2011 (UTC)[reply]
That's probably because cite-book has been replaced by quote-book. SemperBlotto 17:39, 14 December 2011 (UTC)[reply]
I seem to think with cite-book you have to use prefix=#*. Don't ask me why this is, it seems to be a clever feature to make the template more difficult to use. Mglovesfun (talk) 17:52, 14 December 2011 (UTC)[reply]
The whole prefix= thing was an attempt, on the part of various editors, to make quotation templates work both on entry pages (where citations are nested under a definition) and on citations pages (where they are not). There's a much simpler and better way to do that, which I've implemented at various templates as I've come across them, and I've now fixed {{cite-book}} to use said better way, but plenty of templates still use the prefix= approach. (Better yet, IMO, would be to get rid of these templates altogether — they're more trouble than they're worth — but I suppose that some editors must feel differently, or else they wouldn't keep using them.) —RuakhTALK 19:55, 14 December 2011 (UTC)[reply]
{{quote-book}} is preferable in a number of respects. It recognizes more parameters (including "editor", "location" and "publisher"). Also, if you don't end your {{cite-book}} parameters with a page number, {{cite-book}} will print the citation line so that it ends with a comma instead of a colon. But, I agree with Ruakh -- best of all is the old fashioned way of just typing the citations without using templates. -- · 21:19, 14 December 2011 (UTC)[reply]

a

That page beats even water in inefficiency; it uses 1 MB of the 2 MB limit! Anyone able to figure out what causes it? -- Liliana • 20:06, 14 December 2011 (UTC)[reply]

addendum: I think I found it, the {{list}} template is the culprit. Can't we just get rid of this obvious duplication of topical categories? -- Liliana • 20:17, 14 December 2011 (UTC)[reply]

Update Mediawiki:sp-contributions-footer

Would an admin be so kind to update the file Mediawiki:sp-contributions-footer, one to update ~vvv's script to be quentin's scrip, and two make the toolserver urls protocol relative. I have done that at s:Mediawiki:sp-contributions-footer if you need to peek. — billinghurst sDrewth 22:37, 14 December 2011 (UTC)[reply]

Template:Wikipedia

See Template_talk:wikipedia#Sidebar_display_bug. Does anyone else experience this bug? —Michael Z. 2011-12-15 16:20 z

I do. As I recall, we also used to have the same problem with the "visibility" section; but I don't remember who fixed that, or how. —RuakhTALK 20:23, 16 December 2011 (UTC)[reply]
In MediaWiki:common.js there is the section
    // Add a new global toggle to the side bar
    addGlobalToggle: function(category) {...
I don't know the exact code problem, but it would seem that the icons to use for open, show close, and vice versa. It will need a sysop to get in and edit. — billinghurst sDrewth 06:41, 19 December 2011 (UTC)[reply]
(Actually, the relevant section is function Projectlinks() { ...) --Yair rand 06:55, 19 December 2011 (UTC)[reply]
Fixed. --Yair rand 06:54, 19 December 2011 (UTC)[reply]

Non-English categories and tabbed languages

Is there any way of making the links on pages in the Category namespace go straight to the appropriate language section when using tabbed languages? —Internoob 20:47, 24 December 2011 (UTC)[reply]

That may be worthwhile even without Tabbed Languages . . . yes, it's possible, using JavaScript to modify the links on the category-pages to include hashes. I won't volunteer, though, yet, because there's another programming task on this page that I volunteered for a while back and still haven't done. :-/   —RuakhTALK 17:55, 29 December 2011 (UTC)[reply]
If you're talking about #link to page with quotations visible, which was my request, then, if my 2c have any weight with you, I think the current request is more important.​—msh210℠ (talk) 18:39, 29 December 2011 (UTC)[reply]
Hm, if we're going to be fiddling with category member HTML, we might as well also fix it so that the scripts display right, and the lang parameter is set... --Yair rand 00:09, 30 December 2011 (UTC)[reply]
Here we go: User:Yair rand/catfix (template to be added to category templates, first parameter is the language code), and User:Yair rand/catfix.js. --Yair rand 21:11, 3 January 2012 (UTC)[reply]
Brilliant! Very smoothly done, in every detail, except that I believe the template should have a sc= parameter for categories of words not in their default script (e.g. Serbo-Croatian in Latin script), and perhaps it should just use {{Xyzy}} rather than jumping directly to (e.g.) {{he/script}}. Aside from that, my only concern is that, if I'm not mistaken, it would fail ungracefully if (e.g.) {{he/script}} or {{Hebr}} didn't exist, or if {{Hebr}} started with something other than an HTML element. (I admit, I'm not aware of any script templates with the latter property, but SFAIK nothing currently forbids it. In the past we've discussed the possibility of {{Hebr}} wrapping its contents in bidi characters to prevent internal RTL directionality from "leaking out" in the case of interstitial punctuation and/or subsequent digits, especially the latter.) Similarly, it could behave rather oddly if {{Hebr}} did start with an HTML element, but that element wasn't intended to directly hold the templated text (say, if {{Hebr}} used two layers deep of HTML elements for some reason). It might be safer to use some sort of placeholder text, such as %PLACEHOLDER_TEXT%, and resort to the less-fancy approach of manipulating innerHTML.   Oh, and by the way, p should totally be named li. :-P   —RuakhTALK 22:29, 3 January 2012 (UTC)[reply]
I've added the sc= parameter, changed the variable name, and fixed the bug with script templates not beginning with HTML element, and with those without an HTML element at all (ex. {{Sgnw}}, which should really be fixed, if just to pass the lang parameter). If there is no script template at all, quite a lot of templates would break, so I think it's okay to assume that one exists. --Yair rand 01:13, 4 January 2012 (UTC)[reply]
Thanks!   Re: "If there is no script template at all, quite a lot of templates would break": Are you sure? I thought that most script-using templates used {{Xyzy}}, which copes with a nonexistent {{he/script}} by falling back on {{Eror}} (though it does not, I admit, cope with a nonexistent {{ {{he/script}} }}). —RuakhTALK 02:01, 4 January 2012 (UTC)[reply]
A quick check of a bunch of the most-used templates: {{l}} doesn't use Xyzy, {{t}}, {{slink}}, {{term}}, {{makelink}}, and {{wlink2}} do use Xyzy. So, yeah, most templates can handle it. --Yair rand 02:14, 4 January 2012 (UTC)[reply]

^ above numbers

Is there a character that looks like a ^ that can be placed above numbers in normal text and in page headers? Celloplayer115 18:53, 25 December 2011 (UTC)[reply]

You mean like the scale degrees 1̂, 2̂, 3̂, 4̂, 5̂, 6̂, 7̂? You can use U+0302 COMBINING CIRCUMFLEX ACCENT (&#770;). —Angr 21:27, 25 December 2011 (UTC)[reply]
Yes, that's exactly what I was thinking. Thanks. Celloplayer115 03:15, 26 December 2011 (UTC)[reply]

Getting collapsible tables to fit their contents

I recently got a widescreen monitor, and since we use collapsible tables a lot on Wiktionary, I noticed that a lot of the time, the tables are stretched to the entire width of the screen, leaving a lot of empty space in between. Is it possible somehow to make the table only as wide as its contents, so that it becomes wider or narrower as the words in the table are longer or shorter? —CodeCat 15:16, 26 December 2011 (UTC)[reply]

This is what I asked at #Template:fro-decl-adj. Mglovesfun (talk) 15:19, 26 December 2011 (UTC)[reply]

Wiktionary:Frequency lists

There's been some recent activity here. Can we get one for French, as our current French one sucks? --Simplus2 14:15, 29 December 2011 (UTC)[reply]

The most used word isn't something we should change every month. Please tell us if you see some examples of list we should copy or go toward. JackPotte 22:21, 8 January 2012 (UTC)[reply]

Antiblue

Hi all. Can someone tell me how to quickly unlink to pages with a specific language section. I'm thinking of stripping all entries on User:Simplus2/more French crap which already have a French section. --Simplus2 20:13, 29 December 2011 (UTC)[reply]

This tool is free if you download AWB on a Windows PC. JackPotte 22:24, 8 January 2012 (UTC)[reply]
Retrieved from "https://en.wiktionary.org/w/index.php?title=Wiktionary:Grease_pit/2011/December&oldid=65119666"