Wiktionary:Landsbybrønden
Landsbybrønd i Den Gamle By |
Velkommen nybegyndere og andre forundrede brugere! Hvis du har et spørgsmål om Wiktionary og hvordan det hele virker, så placer det i bunden af listen, og nogen vil forsøge at besvare det for dig.
Før du stiller et spørgsmål, så check lige om det ikke allerede er besvaret under ofte stillede spørgsmål.
NOTE - spørgsmål og svar bliver ikke på denne side for evigt. Efter et stykke tid bliver de flyttet til et mere passende sted, for eksempel under ofte stillede spørgsmål.
(purge)
Sådan skriver man et indlæg på Landsbybrønden
[redigér]- Tryk på rediger
- Gå til redigeringsfeltet og indsæt
- {{Brønd|Overskrift=Overskrift for emne}}
- Gå til bunden af siden og tryk på et af de røde links der svarer til dit nye indlæg
- Skriv dit indlæg, du skal starte med overskriften:
- == Overskrift for emne ==
- Gem siden
Benyt ikke det rediger-link der er nederst på Landsbybrønden. Det vil placere dit indlæg sammen med den hidtil nyeste men uvedkommende diskussion.
Hvis ovenstående giver dig problemer, så gør du det bare så godt du kan, så kommer der sikkert en mere rutineret bruger og retter det til for dig.
Se også den detaljerede vejledning.
Arkiverede debatter
[redigér]Kronologiske arkiver
[redigér]Samtlige debatter på Wiktionary:Landsbybrønden, arkiveret mere eller mindre kronologisk.
- Arkiv 1 - usorteret - 12. maj 2005 - 19. juli 2007
- Arkiv 2 - usorteret - feb. 2008 - nov. 2009
- Arkiv 3 - usorteret - jan. 2010 -
Indlæg fra robotter
[redigér]Her arkiveres globale beskeder, indsat direkte på Wiktionary:Landsbybrønden af en robot.
function showSeeAlso()
[redigér]{{også|...}}
- Se [1]. Ville anvende her? Bedsten (diskussion) 29. apr 2014, 12:05 (UTC)
- Hvad indebærer den funktion?
- Sarrus (d • b) d. 10. maj 2014, 10:15 (UTC) - Hvis er i side Vorlage_Siehe_auch (Skabelon_også) vis Skabelon_også.
- Medmindre ikke er in side Vorlage_Siehe_auch (Skabelon_også) og der er to siden som adskiller sig genom minuskel og majuskel vis ... . Bedsten (diskussion) 12. maj 2014, 05:13 (UTC)
- Hvad indebærer den funktion?
Støtter Tyskeren (diskussion) 10. aug 2016, 12:29 (UTC)
Skabeloner for #Bestemt ental af .. ?
[redigér]Hej, findes der skabeloner for den bestemte entalsform og de ubestemte og bestemte flertalsformer af danske navneord?
Så man slipper for at måtte skrive #Bestemt ental af '''[[ditordher]]'''., etc ?
Hvis ej, har det været diskuteret før? Jeg søgte lidt, men fandt intet om dette. Tak på forhånd, B Lemeukx 7. jan 2017, 00:54 (UTC).
- Jeg har ikke lige fundet nogen med den ordlyd, men jeg har fundet nogle andre, som jeg nu har placeret i Kategori:Bøjningsskabeloner. Jeg opretter aldrig opslag om bøjede ord, så kan have overset dem. Du kan selv søge efter det, ved at gå ind på Speciel:Søgning, klikke på "avanceret", fjerne markeringen ved "(Hoved)", aktivere markeringen ved "Skabelon", skrive et søgeord og derefter klikke på "søg" (eller "enter" på tastaturet).
- Sarrus (d • b) d. 7. jan 2017, 11:21 (UTC)
En enkel model for at bestemme en-ord eller et-ord samt bøgningerne ?
[redigér]Hej, findes der allerede nogle ordlister der er baseret på "logik"?
Jer er ellers startet på at lave nogle beskrivelser selv (Bruger:B Lemeux/Discussion/nom-da-en+et) til at fine ud af om et dansk navneord er intetkøn eller fælleskøn, samt i hvilken bøgningsgruppe det falder (løst baseret på Kategori:Bøjningsskabeloner til dansk). Men hvis der allerede er nogle fastbrændte lister her på stedet, kan jeg måske stoppe med mine lister :-) ?
Tak på forhånd, B Lemeukx (diskussion) 7. jan 2017, 08:51 (UTC)
- Hvis du er i tvivl om, hvilket køn et ord er, kan du slå det op i en ordbog. Det er ikke rigtigt muligt, at lave en regel om det. Omend de fleste ord, der omtaler mennesker (familierelationer, stillingsbetegnelser, aldersrelaterede ord osv.) er fælleskøn, men der er udtagelser, f.eks. er barn intetkøn. Du kan finde en liste over internetbaserede ordbøger på Wiktionary:Ordbøger. Du må gerne opdatere ordbogsoversigten, hvis du kender nogen, der ikke er angivet.
- Sarrus (d • b) d. 7. jan 2017, 11:27 (UTC)- Hej og tak Sarrus,
Hvor meget må vi bruge fra Wiktionary:Ordbøger (der står intet om begrænsninger/tilladelser på denne side) eller andre ordbøger, før vi får copy-dan på halsen? Ifølge Kinamand var en bruger for nogen tid siden i farezonen.- Øh, tænker du på ophavsret? Det eneste, der kan være ophavsret på, er vel definitionen, så den bør man selv formulere. Der er vel ikke ophavsret på oplysninger om, hvordan et ord bøjes og hvilket køn ordene er? Ordenes etymologi og evt. andre oplysninger om ordet kan der vel ikke være ophavsret på?
- Sarrus (d • b) d. 7. jan 2017, 23:02 (UTC)- Gælder det også udtaleformer som /ˈmʌd̥ə/? Jeg har hidtil kun brugt kilder indenfor wiki-verdenen, B Lemeukx (diskussion).
- Kan du ikke prøve at stille ophavsretsspørgsmålene på Nybegynderforummet på Wikipedia. Der er flere aktive brugere og de samme ophavsretsregler må gøre sig gældende på både Wikipedia og Wiktionary.
- Sarrus (d • b) d. 8. jan 2017, 12:42 (UTC)
- Kan du ikke prøve at stille ophavsretsspørgsmålene på Nybegynderforummet på Wikipedia. Der er flere aktive brugere og de samme ophavsretsregler må gøre sig gældende på både Wikipedia og Wiktionary.
- Gælder det også udtaleformer som /ˈmʌd̥ə/? Jeg har hidtil kun brugt kilder indenfor wiki-verdenen, B Lemeukx (diskussion).
- Øh, tænker du på ophavsret? Det eneste, der kan være ophavsret på, er vel definitionen, så den bør man selv formulere. Der er vel ikke ophavsret på oplysninger om, hvordan et ord bøjes og hvilket køn ordene er? Ordenes etymologi og evt. andre oplysninger om ordet kan der vel ikke være ophavsret på?
- Hej og tak Sarrus,
Hvis andre brugere har alligevel mod på det, prøv at se mine lister igennem, om de holder? :-) For eksempel at navneord der slutter på "~graf" altid følger "en|er" eller om der findes undtagelser? Tak på forhånd. B Lemeukx (diskussion) 7. jan 2017, 19:50 (UTC)
- Kom lige i tanke om det: Hvordan kan vi søge på artikler der slutter med en bestemt endelse? At finde ord der starter med "abc" er en barneleg, men det modsætte ???
- Hvad angår endelser, kan du kigge i Kategori:Endelsers underkategorier, men den er sikkert ikke komplet. Desuden ser det ud til, at man kan f.eks. kan skrive "*tion" i Speciel:Søgning og så få ord frem, der ender på "tion".
- Sarrus (d • b) d. 7. jan 2017, 23:02 (UTC)- Genialos, merci, B Lemeukx (diskussion) 8. jan 2017, 12:29 (UTC).
- Hvad angår endelser, kan du kigge i Kategori:Endelsers underkategorier, men den er sikkert ikke komplet. Desuden ser det ud til, at man kan f.eks. kan skrive "*tion" i Speciel:Søgning og så få ord frem, der ender på "tion".
Artikelstrukturen : hund-da vs hund-no og hund-sv ??
[redigér]Hej, mønsterartiklen hund har strukturen "noun etym pronun decl" for den danske del, men "etym pronun noun decl" for den norske og svenske. Er den danske struktur den rigtige? Tak, B Lemeukx (diskussion) 8. jan 2017, 21:59 (UTC)
- Etymologi og udtale bør stå før ordklassen (altså øverst efter sprogkoden), hvis begge dele er fælles for alle ordklasser (for det tilfælde, at et ord tilhører flere ordklasser). Ellers ser det ud til, at det kun gør sig gældende for den ene ordklasse. For at opslagene er nogenlunde ensartede bør det også gælde opslag, der kun dækker én ordklasse (såsom hund).
- Sarrus (d • b) d. 9. jan 2017, 14:52 (UTC)- Tak, jeg har rettet. B Lemeukx (diskussion) 23. jan 2017, 22:42 (UTC)
Skabelon:User ... ???
[redigér]Der er et fåtal gamle skabeloner tilbage med navne der starter med:
Skabelon:User
Fundet via følgende søgning (som giver lidt for meget, men any way).
Da de nuværende, brugte, skabeloner er lokaliserede, kunne de med "User" vist fjernes, eller?
De sider, der bruger dem, forbliver allesammen i deres økosystem, eg Skabelon:User lang-2 bruges kun af Skabelon:User nn-2,Skabelon:User sv-2 og Skabelon:User fr-2.
Eventuelt skal der laves lidt ved én af dem: User_lang_subcat . B Lemeukx (diskussion) 23. jan 2017, 22:48 (UTC)
- Jeg markerer dem med "hurtigslet" nu, B Lemeukx (diskussion) 25. jun 2017, 03:52 (UTC)
Skabelon : da-noun-infl folder sammen, hvorfor ??
[redigér]Hej, artiklen mus og insulin bruger begge bøjningsskabelonen da-noun-infl. Hos mus-artiklen vises alle bøjningsformer hele tiden. Når jeg læser insulin-artiklen ind, vises bøjningsformen i sin helhed kun i omkring 1 sekund, så folder den sammen og man skal trykke på "Show"-lænken. Hvorfor?
Kan man indstille det at de bøjningsformer altid vises udfoldet?
Og hvorfor hedder det "Show" og "Hide", og ej "Vis" og "Skjul"? B Lemeukx (diskussion) 5. feb 2017, 21:32 (UTC)
- Skabelonen da-noun-infl, der er brugt i insulin, henviser inernt til skabelonen da-noun-infl-base. Der er altså tale af forskellige versioner af samme skabelon. Med venlig hilsen --Olelog (diskussion) 6. feb 2017, 09:15 (UTC)
- If you want to change the text "Show" and "Hide" into "Vis" and "Skjul", I believe page MediaWiki:Common.js should be adjusted. Only an admin can change that page (Sarrus?).
- MediaWiki:Common.js, lines 9 & 10, currently:
var NavigationBarHide = '[Hide]';
var NavigationBarShow = '[Show]';
- This could be changed into something like:
var NavigationBarHide = '[Skjul]';
var NavigationBarShow = '[Vis]';
- Kind regards, Curious (diskussion) 20. feb 2017, 19:56 (UTC)
2 modeller -da- og =da=
[redigér]Hej, jeg finder to modeller
{{-da-}}
og
{{=da=}}
Har vi brug for begge, eller kunne den første erstattes af den sidste? Det ser ud til at vi kun har -da- for danske artikler her, alle andre sprog er med dobbelt-streger. Tak, B Lemeukx (diskussion) 3. jun 2017, 12:44 (UTC)
- Nej, en er nok. Dansk er ikke det eneste sprog, der har begge: se f.eks. {{-eo-}}/=eo=, {{-en-}}/=en=, {{-de-}}/=de=. Personligt bruger jeg altid ligmedtegnsversionerne, fordi de skiller sig ud fra de andre overskriftsskabeloner. En ulempe ved at bruge det format er, at man ikke kan bruge {{vis}}-skabelonen, men det virker ikke betydningsfuldt.__Gamren (diskussion) 4. jun 2017, 10:18 (UTC)
Etymologie-skabeloner giver ekstra linjeskift
[redigér]Hej,
jeg ville lave dokumentation på etymologi-skabelonerne {{term}}, {{suffix}} og {{prefix}}, men det har de det tilsyneladende rigtigt dårligt med. For suffix så det sådan ud:
- ven
+ -skab
- bouquin
+ -iste
Hvordan kan man lave en ordentlig dokumentation på disse skabeloner, dvs rækkefølge af elementer og deres betydning? Det er absolut nødvendigt hvis vore brugere skal kunne bruge dem rigtig.
Jeg forstår faktisk overhovedet ej; på den franske wikti har jeg rettet flere end én skabelondokumentation - allesammen uden de problemer jeg støder på her!
I al fald, hvis nogen kan udrette disse skabeloner igen, tak på forskud, B Lemeukx (diskussion) 2. jul 2017, 19:03 (UTC)
Etymologie-skabeloner igen uden fejl idag
[redigér]- Hmm, idag ser alt igen OK ud på Skabelon:term/doc, Skabelon:prefix/doc, Skabelon:suffix/doc og da:Wiktionary:Skabeloner. Men igår så de ud som på vedhæftede skærmaftryk!
Jeg ville dog gerne have at vi laver lidt bedre dokumentation på hvad disse modeller forventer for at give de rigtige resultater. Tak, B Lemeukx (diskussion) 3. jul 2017, 19:49 (UTC).
Enabling Page Previews
[redigér]Enabling Page Previews
Hello,
Based on the positive results of a series of quantitative and qualitative tests, the Reading web team at the Wikimedia Foundation would like to enable the Page Previews feature for this project.
Page Previews provide a preview of any linked article, giving readers a quick understanding of a related article without leaving the current page. However, we realize the needs of the Wiktionary community will not be satisfied by the current implementation of the feature. We are interested in developing separate previews for Wiktionary that will display the wiktionary definition of an item, as well as an image, if available.
We'd like to invite some discussion around interest in this feature, as well as the requirements and elements that would make it useful for the Wiktionary community.
Flottere bøjningsskabelon for "bager-model"
[redigér]Hej,
en tidligere kommentar på Wiktionary:Skabeloner i underafsnittet af {{-decl-}} ====Bøjning==== sagde om Skabelon:da-noun-infl: Det er ikke det kønneste layout, så du må meget gerne forbedre det.
Jeg har tænkt på at lave farverne mere i stil af vores basismodel Skabelon:da-noun. Et eksempel er på følgende side:
Bruger:B Lemeux/superbager
Kunne I sige hvad I mener?
Jeg har også lavet en "bager-model", for at gøre det nemt at angiver bøjningerne for stort set alle danske stillingsbetegnelser der ender i -er. Man kan direkte bruge den uden at måtte angive formerne for pl-def og pl-def-gen (se eg infl-diskussion). Skal vi have denne skabelon generelt? Tak, B Lemeukx (diskussion) 15. jul 2017, 17:07 (UTC)
Skabeloner: Salmonsens og Salmonsen2 er stort set ens ?
[redigér]Hej, vi har to referenceskabeloner til dansk som er stort set ens, Salmonsens Konversationsleksikon. - 2. udg. 26 bind, 1915-1930, og heldigvis er ingen af dem endnu brugt, burde vi slette en af dem?, B Lemeukx (diskussion) 21. aug 2017, 19:57 (UTC)
- Det lader ikke til, at nogen af dem er i brug. Måske kunne vi slette dem begge to? Du kan prøve at tage det op på Wiktionary:Sider der bør slettes.
- Sarrus (d • b) d. 22. aug 2017, 09:56 (UTC)
- Det lader ikke til, at nogen af dem er i brug. Måske kunne vi slette dem begge to? Du kan prøve at tage det op på Wiktionary:Sider der bør slettes.
Anmodning om sletninger
[redigér]I skrivende stund er der 26 sider, der er foreslået slettet i Kategori:Sider der er foreslået slettet hurtigt. Måske kunne Bruger:Kinamand eller Bruger:Palnatoke lokkes til at se på dem :-). Samt evt. konkludere på forslagene på Wiktionary:Sider der bør slettes, når det er passende.
- Sarrus (d • b) d. 26. aug 2017, 09:45 (UTC)
- Det er sket nu (af Palnatoke :-) ). Kinamand (diskussion) 28. aug 2017, 13:18 (UTC)
Columns for references
[redigér]Hello,
At the request of Wikipedia editors, a new feature has been added to MediaWiki. Long lists of references (also called citations or footnotes) will automatically be displayed in columns. This will make it easier for most people to read the references, especially on narrow screens. Short lists of references will not be affected.
I plan to enable this new feature at this wiki on Monday, 11 September 2017. After that date, use the normal <references />
tag on any page with many references to see this feature. If you do not want columns used on that page, then use this wikitext code instead: <references responsive="0" />
For mange løse lænker i Wiktionary:Velkommen nybegynder
[redigér]Hej,
jeg synes der er for mange løse sider i Wiktionary:Velkommen nybegynder. Jeg nævner i flæng:
- opslagsordets diskussionsside
- på Wiktionary politik
- de mest almindelige begynderfejl på Wiktionary.
- se vores svar til kritikere.
- Hvis du har lyst til at være med, så kan du fortsætte på Wiktionary:Kom hurtigt i gang.
Er der nogen der kunne stramme teksten til? Den ser ud til at være så gammel hine steder at der er ej længere relevante emner den beskriver. Eller tager jeg fejl? Tak, B Lemeukx (diskussion) 3. sep 2017, 21:23 (UTC)
Ejendomsmægler søger fuge-s
[redigér]Hej,
hvordan kan jeg bedst udtrykke her på da-wikt i etymologi-delen at et sammensat ord "holdes sammen" af fuge-s? Som jeg har startet på i artiklen ejendomsmægler. Er brugen af compound godt nok, eller bliver det for tungt med al den henvisningstekst: ejendom + s (interfix) + mægler, eller skal vi lave specielle skabeloner (til fuge-s, fuge-e, fuge-n, ...) ? Tak, B Lemeukx (diskussion) 4. sep 2017, 19:57 (UTC)
- Kan man ikke bare gøre som i denne version? Det plejer jeg at gøre. Er der nogen grund til, at der skal stå (interfix) midt i etymologien? Måske skulle man lave skabelonen om, så der henvises til en artikel med navnet -s-, -e- eller -n-, På enwikt findes opslaget en:-s-#Danish eksempelvis.
- Sarrus (d • b) d. 5. sep 2017, 17:31 (UTC)- På en.wikt angiver jeg altid, at et fugebogstav er brugt (f.eks. her, her, her), ud fra princippet om, at man ikke kan tillade sig at betragte nogle af morfemerne og se bort fra resten, selvom jeg sagtens kan forstå hvis nogen anser dem for betydningsløse. At skrive interfix (som forresten staves interfiks på dansk, jf. suffiks, præfiks) virker ikke nødvendigt. Som regel markerer man blot morfemer der kræver et element på hver side med med bindestreger på hver side.__Gamren (diskussion) 7. sep 2017, 15:59 (UTC)
- OK, altså ligesom hos en:helhedsvurdering der henviser til et afsnit med overskrift Interfix også hos os: ejendom + -s- + mægler, og så lave en artikel om fuge-s: -s-, etc. Skal vi gøre dette? , B Lemeukx (diskussion) 17. sep 2017, 19:08 (UTC)
- Og hvad skal overskriften hedde? Interfiks som hos w:Bindebogstav (eller det skal ændres dér?), Fugebogstav, Bindebogstav, Interfiks, eller noget helt andet? Tak, B Lemeukx (diskussion) 17. sep 2017, 19:13 (UTC)
- Hmm, det ser ud til at jeg selv må tage beslutningen og vil gøre sådan:
- På en.wikt angiver jeg altid, at et fugebogstav er brugt (f.eks. her, her, her), ud fra princippet om, at man ikke kan tillade sig at betragte nogle af morfemerne og se bort fra resten, selvom jeg sagtens kan forstå hvis nogen anser dem for betydningsløse. At skrive interfix (som forresten staves interfiks på dansk, jf. suffiks, præfiks) virker ikke nødvendigt. Som regel markerer man blot morfemer der kræver et element på hver side med med bindestreger på hver side.__Gamren (diskussion) 7. sep 2017, 15:59 (UTC)
- Ingen ændring af skabelonen compound. På et tidspunkt findes der måske et ord der er sammensat med s ej som bindebogstav men som et eget ord. Denne fare forekommer mig ej ved -s-.
- -s- følger standarden på andre wikter, en, nl, sv, fr, etc.
- ny artikler -s-, -e-, -n-, -er- + -nt- med beskrivelsen: Interfiks (selvom kun Informationshåndbogen skriver det sådan, andre danske sider sætter Interfix). Jeg vil kopiere den del der står nu i s.
- Lidt flere krydshenvisninger indenfor interfiks (skal skrives dd!), interfix, bindebogstav, fugebogstav, vidensform, dobbeltform, etc.
- Andet arbejde: erstatning af tidligere brugt s i nogle tilfælde af compound eller som direkte henvisning. Hvis nogen har en bot til at gøre dette, ville det være fint. Der er lidt under 250 sider der henviser til s på nuværende tidspunkt. Øvelsen skal også gøres for n og e.
- God weekend, B Lemeukx (diskussion) 29. sep 2017, 19:11 (UTC)
Forvirrende : Sådan skriver man et indlæg på Landsbybrønden
[redigér]Hej, det er rigtigt forvirrende med de to modsatrettede råd man får hhv på selve Landsbybrønden og hvad man ser, når man har trykket på lænken rediger.
Sådan ser det omtrentligt ud hos mig:
<!--
Landsbybrønden er konverteret til et The Danish village pump has been
redigeringsvenligt format. Nye emner changed to a more editable format. New
tilføjes sådan: topics are added like this:
1. Kopier {{Brønd|Overskrift=}} ind 1. Paste {{Brønd|Overskrift=}} into
over denne kommentar. the text above this comment.
2. Indsæt din overskrift på emnet 2. Insert the subject after =
efter = 3. Save this page.
3. Gem siden 4. Follow the red link
''rediger'' (edit) at the bottom of
4. I bunden af siden er der nu et the page, and create your topic there.
rødt link. Følg dette, og Remember to place a heading
(== ... ==)
opret emnet som normalt. at the top of that page.
Husk at starte siden med
en overskrift (== ... ==)
Bevar venligst denne kommentar. Please preserve this comment.
-->
Det læser jeg som at jeg skal indsætte overskrift-delen ovenover denne forklaring: Kopier Brønd|Overskrift= ind over denne kommentar.!
Mens på selve Landsbybrønden står der:
- Tryk på rediger
- Gå til redigeringsfeltet og indsæt
- {{Brønd|Overskrift=Overskrift for emne}}
- Gå til bunden af siden og tryk på et af de røde links der svarer til dit nye indlæg
- Skriv dit indlæg, du skal starte med overskriften:
- == Overskrift for emne ==
- Gem siden
Altså skal man faktisk ej indsætte sin overskriftsdel ind over men faktisk i bunden af siden (under alle de andre indlæg).
Jeg forslår at vi ændrer hjælpeteksten i de to ubehjælpsomme søjler til to blokke, først dansk og så engelsk, og så også gør klarere at man bør indsætte overskrift... i bunden af siden.
Allerhelst så jeg, at man kunne lave denne rediger lænke så den automatisk indsætte lænket i bunden af siden. Kan vi ej finde ud af dette?
Tak, B Lemeukx (diskussion) 21. aug 2017, 20:17 (UTC)
etymologiebank.nl - Bronverwijsning: Sijs, Nicoline van der ...
[redigér]Hej,
når jeg bruger etymologiebank.nl synes de i bunden på hver artikel og på deres hovedside at gøre opmærksom på en fuld kildehenvisning. Jeg har derfor bragt vores tilsvarende skabelon på højde med dette. Men er det nødvendigt? Kan vi "nøjes" med bare at have den fulde kildebeskrivelse i selve skabelonopsætningen? Så at den tekst vi indsætter i vore opslagsordsartikler bliver kort som før:
Og i skabelonen er der tilføjet en noinclude-del som følger:
- Sijs, Nicoline van der (samensteller) (2010), Etymologiebank, op etymologiebank.nl/
Så at man kan se fuld kildeangivelse ved at bruge vores interne lænke til skabelonen og den ej fylder vore artikler op? Ville vi være "god" på denne måde?, B Lemeukx (diskussion) 21. okt 2017, 13:16 (UTC)
- Værker har sommetider en sådan anvisning om, hvordan de gerne vil citeres, men det plejer jeg at læse som et høfligt forslag; hvis jeg f.eks. skriver en artikel, vil jeg som regel gerne bruge en konsistent referencestandard, og det må vel være skribentens valg. Især skal kildeangivelsen naturligvis stå på det sprog, som der skrives i, hvilket her er dansk (så "samensteller" og "op" går ikke). Samtidig kan jeg ikke se fordelen ved at udelade proveniens. Skabelonsiden er til os der redigerer og bruger skabeloner, og bør i princippet være "usynlig" for den ikke-redigerende bruger, dvs. det bør ikke være nødvendigt at se på den, medmindre man er bidrager.__Gamren (diskussion) 21. okt 2017, 14:47 (UTC)
Skabelon:also og også Skabelon:også ?
[redigér]Hej, jeg ser vi har yderligere en dublet på to skabeloner: {{also}} og {{også}}. Den sidste bliver flittigt brugt og er den mest danske, den første kom vist fra opstarten, pardon startup og bruges "kun" mellem 250 og under 500 gange.
Begge er begrænsede til kun 10 eller 9 elementer. Angives flere, som i dé-, optræder de i følgende: Kategori:Limit of template reached; og kun de 10 eller 9 første elementer vises.
Jeg vil forslå at vi laver to ting:
- Finder en venlig bot-tæmmer der erstatter {{also}} med {{også}}.
- Måske er nogen i jule(gave)humør ;-)?
- Laver {{også}} mere generelt, så den kan klare flere elementer.
- Jeg har set lige omkring, og den "nyeste" er nok fra fr-wikt, hvor de bruger en <div class="bandeau-voir"><span class="bandeau-voir-icone">''Voir aussi''</span> : {{#invoke:voir|liste_voir}}</div><noinclude>, dvs der ser ej ud til at være en numerisk begrænsning på 9 eller 10 eller 50 (es-wikt) elementer.
- fr-wikt har ændret fra "kun" 100 elementer til brugen af <nowiki>#invoke:voir|liste_voir<nowiki> i 2013 [2].
- Vi har brug for at kunne kalde på noget lignende end <nowiki>#invoke:voir|liste_voir<nowiki>! Har vi det allerede her?
Tak, B Lemeukx (diskussion) 23. dec 2017, 11:56 (UTC)
- Ser lige at vore nynorske venner har en fin listefunktionalitet nn:Modul:Template:also som de bruger i nn:Mal:sjå òg siden juli iår.
- Jeg tror jeg starter med at udvide {{også}} til flere elementer, så har vi noget at gå videre med, og så kan vi tage det tunge arbejde med listefunktioner i næste år. Glædelig jul, godt nytår, fra : B Lemeukx (diskussion) 23. dec 2017, 12:12 (UTC)
- Kan {{also}} erstattes af {{også}} i alle opslagsord uden problemer? Har de helt samme funktionalitet? Det burde ikke være noget problem at gøre med AutoWikiBrowser, men jeg har bare ikke en konto med botflag her på dawiktionary (har på dawiki og nowiktionary). Ifølge AWB er der 291 opslag, der bruger {{also}} og 607 opslag, der bruger {{også}}.
- Sarrus (d • b) d. 23. dec 2017, 12:42 (UTC)- Tak, Sarrus, vi kan erstatte {{also}} med {{også}} på alle, med undtagelse af dé-, da dens liste er længere end 9 elementer. B Lemeukx (diskussion) 23. dec 2017, 13:34 (UTC)
- Jeg har opgivet at ændre {{også}}, den er for indviklet at udvide med bare ét element nå! :-( Det må blive den rigtige løsning med en liste-funktionalitet senere, B Lemeukx (diskussion) 23. dec 2017, 13:34 (UTC)
- Kan {{also}} erstattes af {{også}} i alle opslagsord uden problemer? Har de helt samme funktionalitet? Det burde ikke være noget problem at gøre med AutoWikiBrowser, men jeg har bare ikke en konto med botflag her på dawiktionary (har på dawiki og nowiktionary). Ifølge AWB er der 291 opslag, der bruger {{also}} og 607 opslag, der bruger {{også}}.
Skabelon:decl og også Skabelon:bøjn ?
[redigér]Hej igen, vi har også en dublet her med {{-bøjn-}} som kun bruges lidt over 100 gange. Normalt bruger vi {{-decl-}}.
- Vi har brug for en bot-tæmmer til der erstatter {{-bøjn-}} med {{-decl-}} ;-) B Lemeukx (diskussion) 23. dec 2017, 13:42 (UTC)
Oversættelseværktøj
[redigér]Hej B Lemeux og andre,
Du har tidligere udtrykt et ønske om et oversættelseværktøj. Jeg har kopieret translation_editor fra sv.wikt. Vil du (og andre interesserede) installere det (under Mine indstillinger > Gadgets) og fortælle mig hvad I synes? Det virker kun sammen med {{trans-top}} ({{(}} bliver vist også brugt til andre ting, så at ændre den ville nok være en dårlig idé). Desuden bliver navnet på sproget givet direkte, og ikke ved skabelon, hvilket jeg selv synes er en fordel. Jeg kan også få sprognavnet til at være med stort begyndelsesbogstav, hvis der er flertal for det (selv foretrækker jeg lille).__Gamren (diskussion) 16. dec 2017, 18:48 (UTC)
- Det ser ud til, at den skriver “u” for fælleskøn. Her på stedet plejer vi at bruge “c”. Hvis man bruger “u”, vises ordets køn ikke.
- Sarrus (d • b) d. 16. dec 2017, 19:06 (UTC)- Tak for det, hermed rettet.__Gamren (diskussion) 16. dec 2017, 22:29 (UTC)
- Der er stadig nogle svenske reminiscenser hist og pist. Det kunne måske også overvejes, om køn og bøjninger kunne fremstå på dansk. Det er eksempelvis ikke sikkert, at alle kan regne ud, at “mask.”=“maskulinum”=“hankøn”. Desuden kan det måske overvejes at erstatte “Læg oversættelse til” med “Tilføj oversættelse”? Derudover: På svwikt. kan man med et tilsvarende system tilføje oversættelser til et opslag, der endnu ikke har nogen oversættelser. Mon man kan tilføje det her også? På nowikt. er der også et tilsvarende system, men der kan man ikke. Når de forslag er nævnt, ser det ud til at virke :-).
- Sarrus (d • b) d. 17. dec 2017, 08:22 (UTC)- Jeg tror jeg har fået det sidste svenske væk nu (bortset fra det sted hvor Mall:sidnamn bliver kaldt). Forkortelserne er skrevet ud som hele ord. Muligheden for at tilføje nye oversættelsesskabeloner bliver sørget for af en anden gadget. Jeg kan prøve at kopiere den over, men den ser ud til at forvente at overskrifter angives med lighedstegn (==Dansk==, ====Oversættelser====) og ikke skabeloner ({=da=}, {-trans-}). En anden grund til at ønske at gøre det på den første måde er, at det gør det muligt at redigere enkelte afsnit ad gangen, og en tredje er at vi manuelt kan bestemme niveauet. Det kræver bare, at vi finder en anden måde at kategorisere efter sprog på. På en.wikt (og tilsyneladende også sv.wikt) bliver det gjort via den skabelon, der angiver navnet på ordet (og evt. andre data såsom køn, nogle få bøjninger, aspekt (for f.eks. russiske verber) eller klasse (for substantiver på zulu)), umiddelbart over definitionerne, altså det vi på en.wikt kalder the headword-line template.__Gamren (diskussion) 17. dec 2017, 09:57 (UTC)
- Nu kan jeg slet ikke få funktionen til at virke. Kan det være fordi du er kommet til at slette et tegn efter “Kan ikke balancere pga. indskudte linjer”? Hvad siger du til at oversætte den tekst, der er ved knapperne? Resultatet står jo på dansk, så hvorfor ikke knappernes tekster?
- Sarrus (d • b) d. 17. dec 2017, 11:32 (UTC)
- Nu kan jeg slet ikke få funktionen til at virke. Kan det være fordi du er kommet til at slette et tegn efter “Kan ikke balancere pga. indskudte linjer”? Hvad siger du til at oversætte den tekst, der er ved knapperne? Resultatet står jo på dansk, så hvorfor ikke knappernes tekster?
- Jeg tror jeg har fået det sidste svenske væk nu (bortset fra det sted hvor Mall:sidnamn bliver kaldt). Forkortelserne er skrevet ud som hele ord. Muligheden for at tilføje nye oversættelsesskabeloner bliver sørget for af en anden gadget. Jeg kan prøve at kopiere den over, men den ser ud til at forvente at overskrifter angives med lighedstegn (==Dansk==, ====Oversættelser====) og ikke skabeloner ({=da=}, {-trans-}). En anden grund til at ønske at gøre det på den første måde er, at det gør det muligt at redigere enkelte afsnit ad gangen, og en tredje er at vi manuelt kan bestemme niveauet. Det kræver bare, at vi finder en anden måde at kategorisere efter sprog på. På en.wikt (og tilsyneladende også sv.wikt) bliver det gjort via den skabelon, der angiver navnet på ordet (og evt. andre data såsom køn, nogle få bøjninger, aspekt (for f.eks. russiske verber) eller klasse (for substantiver på zulu)), umiddelbart over definitionerne, altså det vi på en.wikt kalder the headword-line template.__Gamren (diskussion) 17. dec 2017, 09:57 (UTC)
- Der er stadig nogle svenske reminiscenser hist og pist. Det kunne måske også overvejes, om køn og bøjninger kunne fremstå på dansk. Det er eksempelvis ikke sikkert, at alle kan regne ud, at “mask.”=“maskulinum”=“hankøn”. Desuden kan det måske overvejes at erstatte “Læg oversættelse til” med “Tilføj oversættelse”? Derudover: På svwikt. kan man med et tilsvarende system tilføje oversættelser til et opslag, der endnu ikke har nogen oversættelser. Mon man kan tilføje det her også? På nowikt. er der også et tilsvarende system, men der kan man ikke. Når de forslag er nævnt, ser det ud til at virke :-).
- Tak for det, hermed rettet.__Gamren (diskussion) 16. dec 2017, 22:29 (UTC)
- Tak. Jeg forsøgte lidt på land. Da jeg arbejdede med værktøjet, stod de tre sidste oversættelser sidst. Kan vi samle de to for [en]: country og state? Når jeg nu genkælder siden, står de først. De grønne pile for at flytte fra venstre til højre, eller omvendt, hjalp ej. Tak, B Lemeukx (diskussion) 20. dec 2017, 01:13 (UTC)
- Det er fordi den forventer, at sprogene er skrevet som ord og alfabetiserer derefter, hvorimod de eksisterende oversættelser var skrevet med sprogskabeloner. Hvis I er enige i at skrive sprognavnene på den måde værktøjet nu gør, kan vi bede nogen med en bot rette de gamle oversættelser.__Gamren (diskussion) 20. dec 2017, 20:51 (UTC)
- PS: Jeg er ikke sikker på hvad du mener med at genkælde/genkalde?__Gamren (diskussion) 20. dec 2017, 20:58 (UTC)
- Så spørger jeg for tredje gang (kan ikke se, at nogen har kommenteret på det endnu, hvad enten I er for, imod eller ligeglade): Hvad siger I til, at teksten ved siden af oversættelsesknapperne skal stå på dansk, da ikke alle kan forventes at forstå, hvad eksempelvis “maskulinum” (hankøn), “femininum” (hunkøn), “neutrum” (intetkøn) og “pluralis” (flertal) betyder? Denne Wiktionary er trods alt en dansksproget ordbog. Resultatet står jo på dansk, så hvorfor ikke også “knapteksten”?
- Sarrus (d • b) d. 21. dec 2017, 13:20 (UTC)- Mener du at ændre ordene i gåseøjne til ordene i parenteser? Jeg er fuldstændig ligeglad. Jeg forstår ikke dit argument med dansksprogethed, når alle ordene er danske. Jeg brugte de ord jeg mente var hyppigst brugt, men alle ordene i parenteser har opslag her, så folk kan bare slå dem op, hvis de ikke kender dem.__Gamren (diskussion) 21. dec 2017, 19:45 (UTC)
- Det er i hvert fald fagsprog så. Der er nok flere, der kender ordet "hankøn" end "maskulinum". Hvis man vil have folk til at bruge Wiktionary, må man bruge et sprog, som flest muligt forstår :-). Jeg ved ikke, hvorfor man har valgt at bruge skabeloner til at angive sprogkoder i oversættelsesafsnittet. Måske Bruger:Kinamand og/eller Bruger:Palnatoke kan svare på det. De har været her længere tid end mig. Det ser ikke ud til, at en skabelon som {{el}} gør andet end at skrive sprognavnet. Kan du eller andre gennemskue det?
- Sarrus (d • b) d. 21. dec 2017, 20:17 (UTC)
- Det er i hvert fald fagsprog så. Der er nok flere, der kender ordet "hankøn" end "maskulinum". Hvis man vil have folk til at bruge Wiktionary, må man bruge et sprog, som flest muligt forstår :-). Jeg ved ikke, hvorfor man har valgt at bruge skabeloner til at angive sprogkoder i oversættelsesafsnittet. Måske Bruger:Kinamand og/eller Bruger:Palnatoke kan svare på det. De har været her længere tid end mig. Det ser ikke ud til, at en skabelon som {{el}} gør andet end at skrive sprognavnet. Kan du eller andre gennemskue det?
- Mener du at ændre ordene i gåseøjne til ordene i parenteser? Jeg er fuldstændig ligeglad. Jeg forstår ikke dit argument med dansksprogethed, når alle ordene er danske. Jeg brugte de ord jeg mente var hyppigst brugt, men alle ordene i parenteser har opslag her, så folk kan bare slå dem op, hvis de ikke kender dem.__Gamren (diskussion) 21. dec 2017, 19:45 (UTC)
- Så spørger jeg for tredje gang (kan ikke se, at nogen har kommenteret på det endnu, hvad enten I er for, imod eller ligeglade): Hvad siger I til, at teksten ved siden af oversættelsesknapperne skal stå på dansk, da ikke alle kan forventes at forstå, hvad eksempelvis “maskulinum” (hankøn), “femininum” (hunkøn), “neutrum” (intetkøn) og “pluralis” (flertal) betyder? Denne Wiktionary er trods alt en dansksproget ordbog. Resultatet står jo på dansk, så hvorfor ikke også “knapteksten”?
- Mit gæt er at sprogkodeskabelonerne er der for at gøre det lettere at copy/paste mellem sprogene. Man skal stort set bare rette ordforklaringen. --Palnatoke (diskussion) 22. dec 2017, 07:38 (UTC)
- Mener du at kopiere mellem forskellige sprogversioner? I princippet en god idé, hvis vi alle brugte samme format. de.wikt bruger sprogskabeloner, en.wikt og som sagt sv.wikt bruger selve navnene, fr.wikt bruger {T}.__Gamren (diskussion) 22. dec 2017, 11:14 (UTC)
- Mit gæt er at sprogkodeskabelonerne er der for at gøre det lettere at copy/paste mellem sprogene. Man skal stort set bare rette ordforklaringen. --Palnatoke (diskussion) 22. dec 2017, 07:38 (UTC)
- B Lemeukx (diskussion) 22. dec 2017, 20:51 (UTC) : >>
- * For: genkælde/genkalde, når jeg genindlæser siden via e.g. F5
- * For: land, nu er der blandet engelsk (som tekst), Esperanto (fra {{eo}}), .... Jeg vil foretrække at sprognavnene bliver skrevet med stort, jeg synes det ser kønnest ud.
- * For: at kopiere mellem forskellige sprogversioner?, med det ny værktøj kan de brugere bidrage der ej vil lære den underliggende wikt-programmering. Til gengæld vil vi med de udskrevne sprognavne gøre denne kopiering sværere for brugere der bruger kildeeditoren.
- * For: teksten ved siden af oversættelsesknapperne skal stå på dansk, da ikke alle kan forventes at forstå, hvad eksempelvis “maskulinum” (hankøn), “femininum” (hunkøn), “neutrum” (intetkøn) og “pluralis” (flertal) betyder? :
- * De fleste andre wikter bruger de lokale udtryk, men nogle sprog er mere "forkælede" ved at de som romanske sprog bruger de latinske udtryk - som "alle" kan forstå. Den islandske bruger de islandske udtryk, og jeg regner ej med at alle danskere kan tyde hvad hvorugkyn betyder.
- * Antallet af sådanne fagudtryk er begrænsede; jeg vil mene de fleste internationale brugere nemt kan lære hvornår de skal trykke ved fælleskøn eller intetkøn for de danske ord og hankøn, hunkøn eller intetkøn for de fleste andre sprog.
- * Hvis vi vil være ekstraflinke kan vi tilføje de latinske betegnelser i parenteser, eg: fælleskøn (utrum).
- << B Lemeukx (diskussion) 22. dec 2017, 20:51 (UTC)
- PS: Jeg har ikke sat default til, hvilket vil sige at IP'er ikke kan bruge det endnu.__Gamren (diskussion) 3. jan 2018, 15:36 (UTC)
- Dipsacus fullonum, kunne du stå for udskiftningen? Altså: I oversættelsesskabeloner (mellem {trans-top} og {trans-bottom}) at udskifte {en} med Engelsk, {de} med Tysk osv., og desuden {O|de|erinnern} med Tysk: {t|de|erinnern}? Det er måske også muligt at udskifte {(}, {-} og {)}, som mange steder bruges til oversættelser, med {trans-top}, {trans-mid} og {trans-bottom}? F.eks. vil der sandsynligvis være tale om en oversættelsestabel hvis {en} og/eller {de} forekommer.__Gamren (diskussion) 10. jan 2018, 15:57 (UTC)
- PS: Jeg har ikke sat default til, hvilket vil sige at IP'er ikke kan bruge det endnu.__Gamren (diskussion) 3. jan 2018, 15:36 (UTC)
Nynorsk / bokmål
[redigér]Jeg har ofte lyst til å legge inn oversettelser til norsk når jeg ser det mangler; kanskje også opprette oppslag for ord som ikke har det. Men norsk kommer i flere former (offisielle målformer bokmål og nynorsk, uoffisielle målformer riksmål og høgnorsk), og jeg vet ikke om dere har en politikk på hvordan dere angir dette? Det er et noe komplisert tema, og ikke opplagt hvilken måte man bør gjøre det på (f.eks. behandles det som ett språk på no-wikt, men to på nn-wikt) – men ihvertfall virker det logisk å ha en felles rettningslinje på det, så oppslagene får noenlunde likt oppsett. Det virker litt unødvendig å legge inn oversettelser før noe slikt er på plass, for man må muligens gjøre alt om igjen .. Mewasul (diskussion) 8. feb 2018, 04:26 (UTC)
- Hvis du gør det på en ensartet måde kan man senere skrive en bot der ændre det hele til noget andet. Kinamand (diskussion) 8. feb 2018, 13:36 (UTC)
- På den anden måde er der ingen grund til at udskyde diskussionen. Personligt synes jeg bedst om at behandle norsk som ét sprog ligesom no.wikt gør (idet der selvf. gøres opmærksom på forskelle i bøjninger, køn osv. og at ord kun findes på en variant, som her) , primært fordi vi, hvis vi opretter bokmål og nynorsk, ikke har et sted at gøre af ord og former der falder udenfor de to normer. Det er garanteret blevet diskuteret på de norske wikter, og jeg ved det er blevet diskuteret på en.wikt, bl.a. var der en afstemning om det. Men hvad siger I der har arbejdet med norsk her, som f.eks. Bruger:Teodor605, Bruger:Mede?__Gamren (diskussion) 8. feb 2018, 17:18 (UTC)
- Norsk er greit, men undertiden umuligt altid at angive de rigtige genusformer. Lad os se på første definition af no:brus. Alt i alt har vi brug for mindst tre forme, idet der skelnes mellem:
- brus m (Bokmål/Nynorsk), c (Riksmål).
- Her ser vi sammenfald på bokmål og nynorsk, men det kunne jo være at genus er forskelligt for alle tre sprog!
- Vi kan lave følgende oversættelser på da-wikt, men hvordan skal vi angi Riksmål (eller høgnorsk?) korrekt? Via {{no}}?:
- Faldt lige over et ekstremt tilfælde - no:søppel :
- søppel m, f eller n (Bokmål), m, f eller n (Nynorsk), c eller n (Riksmål)
- Kanske det bedste er at udelade genus på norske oversættelser?
- Det næste er: skal vi understøtte alle tre forme som nu; eller endda udbygge med en fjerde: {{nr}} (for riksmål)? Eller skal vi slå sammen {{nb}} og {{no}}? Og bibeholde {{nn}}? Der findes en nn-wikt men ej en nb-wikt; så, er det den "mest gangbare" vej?
- B Lemeukx (diskussion) 10. feb 2018, 11:12 (UTC)
- Jeg forstår ikke hvorfor du mener at det er "umuligt altid at angive de rigtige genusformer"? Hvis vi samler norsk, bruger vi kun en enkelt kode - no - og specificerer i oversættelsestabeller. Jeg har lagt et parameter til {t} kaldet d der også kan bruges til at specificere dialekter og accenter (det skal selvfølgelig flyttes et andet sted hen for at undgå spagettikode), se her.__Gamren (diskussion) 10. feb 2018, 14:04 (UTC)
- OK, jeg prøver lige med søppel som jo har alle fire genusformer, og som så måtte blive (med en ny parameter g for multiple genusformer; jeg skriver dem bare i rentekst bagved for at vise hvad jeg mener):
- * {{t|no|søppel|d=nb|g=m,f,n}} : søppel (bokmål) (no) hankøn, hunkøn, intetkøn
- * {{t|no|søppel|d=nn|g=m,f,n}} : søppel (nynorsk) (no) hankøn, hunkøn, intetkøn
- * {{t|no|søppel|d=no|g=n,c}} : søppel (no) (no) intetkøn, fælleskøn
- Hvis vi altså afbilder alle genusangivelserne fra no-wikt også her! (Sideidé: Findes der mon en nemmere måde via wikimedia, så at alle navneord indsættes dér - med alle deres genusangivelser, som så kommer automatisk med?), B Lemeukx (diskussion) 10. feb 2018, 15:32 (UTC)
- Jeg forstår ikke hvorfor du mener at det er "umuligt altid at angive de rigtige genusformer"? Hvis vi samler norsk, bruger vi kun en enkelt kode - no - og specificerer i oversættelsestabeller. Jeg har lagt et parameter til {t} kaldet d der også kan bruges til at specificere dialekter og accenter (det skal selvfølgelig flyttes et andet sted hen for at undgå spagettikode), se her.__Gamren (diskussion) 10. feb 2018, 14:04 (UTC)
- Norsk er greit, men undertiden umuligt altid at angive de rigtige genusformer. Lad os se på første definition af no:brus. Alt i alt har vi brug for mindst tre forme, idet der skelnes mellem:
- På den anden måde er der ingen grund til at udskyde diskussionen. Personligt synes jeg bedst om at behandle norsk som ét sprog ligesom no.wikt gør (idet der selvf. gøres opmærksom på forskelle i bøjninger, køn osv. og at ord kun findes på en variant, som her) , primært fordi vi, hvis vi opretter bokmål og nynorsk, ikke har et sted at gøre af ord og former der falder udenfor de to normer. Det er garanteret blevet diskuteret på de norske wikter, og jeg ved det er blevet diskuteret på en.wikt, bl.a. var der en afstemning om det. Men hvad siger I der har arbejdet med norsk her, som f.eks. Bruger:Teodor605, Bruger:Mede?__Gamren (diskussion) 8. feb 2018, 17:18 (UTC)
Gamren: det at en del ord faller utenfor gitte normer er også en del av min motivasjon for å behandle norsk som ett språk, på no-wikt. :) Ellers: alt er mulig, man må bare tenke litt og se hva som vil virke hensiktsmessig.
- Antatt at vi behandler norsk som ett språk, er det ønskelig å oppgi hvilken målform ved oversettelser? (Er egentlig en større ting enn norsk - oppgir dere f.eks. om det er amerikansk eller britisk skrivemåte for engelsk?) På en side gir det jo mer informasjon, på en annen side kan det lett bli litt overveldende, med mange gjentagelser, og (sett at oppslaget finnes) er dette samme informasjon som angis i oppslaget i seg selv.
- Det også er mulig å angi alle kjønn i oversettelsestabellen uten å angi målform, og så gi mer informasjon på hovedoppslaget.
- Mange ord på norsk kan skrives litt ulikt (som kanskje kan være forvirrende til tider - men som også gjør at man har større mulighet til å tilpasse skriftspråket sin egen dialekt). F.eks. kan man skrive sten eller stein, hvit eller kvit, øst eller aust. I nynorsk kan verb slutte på -e eller -a: legge, legga, leggje, leggja; samme gjelder (enda flere varianter) bøteleggja, bøteleggje, bøtelegga, bøtelegge, bøtlegga, bøtlegge, bøtleggja, bøtleggje. Dette sprer seg videre i sammensetninger: stenlegge, steinlegge, steinlegga, steinleggje, steinleggja. (Merk at dette også er et spørsmål vi må jobbe mer med på no-wikt :))
Dette er vel større spørsmål enn norsk, men er ganske relevante i denne diskusjonen. Og hvis dere allerede har en praksis på dette er det kanskje lettest å følge den videre :)
- (Sideidé svar: Jeg har en ønskedrøm om at all grammatisk informasjon, og kanskje andre ting også, kan legges inn et sted sentralt slik at alt man trenger å gjøre lokalt er å tilby et grensesnitt. Tenk deg f.eks. at man ikke trenger å angi bøyning på alle språkversjoner, men bare har en mal som henter dette fra noe ala Wikidata. Men tror ikke det kommer i nær fremtid ihvertfall ..)
Mewasul (diskussion) 14. feb 2018, 02:44 (UTC)
- Der er ikke som sådan noget behov for at angive hverken køn eller sprogvariant i oversættelsestabeller; pointen var nok bare, at man så ikke skulle behøve besøge siden, men mange former vil nok gøre det mere besværligt. Hvad angår selve siderne, så udvælger jeg en ordvariant som får al information samt en liste over alternative former (se f.eks. bismuth, fandeme).
- Mht. centralisering af grammatisk info: Under alle omstændigheder ville det kræve noget viden, da der findes ord der staves ens men bøjes forskelligt, som f.eks. øl.__Gamren (diskussion) 14. feb 2018, 12:50 (UTC)
Jeg prøvde meg litt frem – men er fortsatt litt usikker. Hvis dere, som er kjent med deres struktur, skulle legge inn et ord på norsk – det være godkjent i alle målformer, som kaffe, eller kun i bokmål og riksmål, som være (nynorsk har vere eller vera) – hvor ville dere angitt målform? Mewasul (diskussion) 25. mar 2018, 06:07 (UTC)
Invitation to attend “Ask Me Anything about Movement Charter” Sessions
[redigér]Hello all,
During the 2022 Wikimedia Summit, the Movement Charter Drafting Committee (MCDC) presented the first outline of the Movement Charter, giving a glimpse on the direction of its future work, and the Charter itself. The MCDC then integrated the initial feedback collected during the Summit. Before proceeding with writing the Charter for the whole Movement, the MCDC wants to interact with community members and gather feedback on the drafts of the three sections: Preamble, Values & Principles, and Roles & Responsibilities (intentions statement). The Movement Charter drafts will be available on the Meta page here on November 14, 2022. Community wide consultation period on MC will take place from November 20 to December 18, 2022. Learn more about it here.
With the goal of ensuring that people are well informed to fully participate in the conversations and are empowered to contribute their perspective on the Movement Charter, three “Ask Me Anything about Movement Charter" sessions have been scheduled in different time zones. Everyone in the Wikimedia Movement is invited to attend these conversations. The aim is to learn about Movement Charter - its goal, purpose, why it matters, and how it impacts your community. MCDC members will attend these sessions to answer your questions and hear community feedback.
The “Ask Me Anything” sessions accommodate communities from different time zones. Only the presentation of the session is recorded and shared afterwards, no recording of conversations. Below is the list of planned events:
Asia/Pacific: November 4, 2022 at 09:00 UTC (your local time). Interpretation is available in Chinese and Japanese.- Europe/MENA/Sub Saharan Africa: November 12, 2022 at 15:00 UTC (your local time). Interpretation is available in Arabic, French and Russian.
- North and South America/ Western Europe: November 12, 2022 at 15:00 UTC (your local time). Interpretation is available in Spanish and Portuguese.
On the Meta page you will find more details; Zoom links will be shared 48 hours ahead of the call.
Call for Movement Charter Ambassadors
Individuals or groups from all communities who wish to help include and start conversations in their communities on the Movement Charter are encouraged to become Movement Charter Ambassadors (MC Ambassadors). MC Ambassadors will carry out their own activities and get financial support for enabling conversations in their own languages. Regional facilitators from the Movement Strategy and Governance team are available to support applicants with MC Ambassadors grantmaking. If you are interested please sign up here. Should you have specific questions, please reach out to the MSG team via email: strategy2030@wikimedia.org or on the MS forum.
We thank you for your time and participation.
On behalf of the Movement Charter Drafting Committee,
MNadzikiewicz (WMF) 7. nov. 2022, 15:33 (UTC)
Apply for Funding through the Movement Strategy Community Engagement Package to Support Your Community
[redigér]The Wikimedia Movement Strategy implementation is a collaborative effort for all Wikimedians. Movement Strategy Implementation Grants support projects that take the current state of a Movement Strategy Initiative and push it one step forward. If you are looking for an example or some guide on how to engage your community further on Movement Strategy and the Movement Strategy Implementation Grants specifically, you may find this community engagement package helpful.
The goal of this community engagement package is to support more people to access the funding they might need for the implementation work. By becoming a recipient of this grant, you will be able to support other community members to develop further grant applications that fit with your local contexts to benefit your own communities. With this package, the hope is to break down language barriers and to ensure community members have needed information on Movement Strategy to connect with each other. Movement Strategy is a two-way exchange, we can always learn more from the experiences and knowledge of Wikimedians everywhere. We can train and support our peers by using this package, so more people can make use of this great funding opportunity.
If this information interests you or if you have any further thoughts or questions, please do not hesitate to reach out to us as your regional facilitators to discuss further. We will be more than happy to support you. When you are ready, follow the steps on this page to apply. We look forward to receiving your application.
Best regards,
Movement Strategy and Governance Team
Wikimedia Foundation
MNadzikiewicz (WMF) 14. nov. 2022, 16:26 (UTC)
Opportunities open for the Ombuds commission and the Case Review Committee
[redigér]Hi everyone! The Ombuds commission (OC) and the Case Review Committee (CRC) are looking for members. People are encouraged to nominate themselves or encourage others they feel would contribute to these groups to do so. There is more information below about the opportunity and the skills that are needed.
About the Ombuds commission
The Ombuds commission (OC) works on all Wikimedia projects to investigate complaints about violations of the privacy policy, especially in use of CheckUser and Oversight (also known as Suppression) tools. The Commission mediates between the parties of the investigation and, when violations of the policies are identified, advises the Wikimedia Foundation on best handling. They may also assist the General Counsel, the Chief Executive Officer, or the Board of Trustees of the Foundation in these investigations when legally necessary. For more on the OC's duties and roles, see Ombuds commission on Meta-Wiki.
Volunteers serving in this role should be experienced Wikimedians, active on any project, who have previously used the CheckUser/Oversight tools OR who have the technical ability to understand these tools and the willingness to learn them. They must be able to communicate in English, the common language of the commission. They are expected to be able to engage neutrally in investigating these concerns and to know when to recuse when other roles and relationships may cause conflict. Commissioners will serve two-year terms (note that this is different from past years, when the terms have been for one year).
About the Case Review Committee
The Case Review Committee (CRC) reviews appeals of eligible Trust & Safety office actions. The CRC is a critical layer of oversight to ensure that Wikimedia Foundation office actions are fair and unbiased. They also make sure the Wikimedia Foundation doesn’t overstep established practices or boundaries. For more about the role, see Case Review Committee on Meta-Wiki.
We are looking for current or former functionaries and experienced volunteers with an interest in joining this group. Applicants must be fluent in English (additional languages are a strong plus) and willing to abide by the terms of the Committee charter. If the work resonates and you qualify, please apply. Committee members will serve two-year terms (note that this is different from past years, when the terms have been for one year).
Applying to join either of these groups
Members are required to sign the Confidentiality agreement for nonpublic information and must be willing to comply with the appropriate Wikimedia Foundation board policies (such as the access to non-public information policy and the Foundation privacy policy). These positions requires a high degree of discretion and trust. Members must also be over 18 years of age.
If you are interested in serving in either capacity listed above, please write in English to the Trust and Safety team at cawikimedia.org (to apply to the OC) or to the Legal Team at legalwikimedia.org (to apply to the CRC) with information about:
- Your primary projects
- Languages you speak/write
- Any experience you have serving on committees, whether movement or non-movement
- Your thoughts on what you could bring to the OC or CRC if appointed
- Any experience you have with the Checkuser or Oversight tools (OC only)
- Any other information you think is relevant
The deadline for applications is 31 December 2022 in any timezone.
Please feel free to pass this invitation along to any users who you think may be qualified and interested. Thank you!
On behalf of the Committee Support team,
Hvordan kan Wikimedia Danmark hjælpe communityet?
[redigér]Wikimedia Danmark er det danske Wikimedia-chapter og har til formål at støtte op om Wikimedias projekter – herunder Wiktionary – og fri viden generelt. Som redegjort for på w:Wikipedia:Landsbybrønden/Wikimedia Danmarks strategiplan for de kommende år har foreningen udarbejdet en strategiplan der skal være vejledende for vores arbejde i de kommende år. Søjle I i strategiplanen omhandler understøttelse af Wikimedia-fællesskabet, og et underelement af denne søjle er det jeg kalder umiddelbare tiltag. Altså meget direkte måder vi kan hjælpe dem der bidrager til Wikimedia-projekterne.
Hvis man har noget input til, hvordan Wikimedia Danmark kan være til gavn for communityet – hvad enten her på Wiktionary eller på de andre Wikimedia-projekter, skal man være meget velkommen til at deltage i diskussionen på w:Wikipedia:Landsbybrønden/Hvordan kan Wikimedia Danmark hjælpe communityet? InsaneHacker (diskussion) 6. dec. 2022, 16:28 (UTC)
Community Wishlist Survey 2023 opens in January
[redigér]Hjælp venligst med at oversætte til dit sprog
(There is a translatable version of this message on MetaWiki)
Hej
The Community Wishlist Survey (CWS) 2023, which lets contributors propose and vote for tools and improvements, starts next month on Monday, 23 January 2023, at 18:00 UTC and will continue annually.
We are inviting you to share your ideas for technical improvements to our tools and platforms. Long experience in editing or technical skills is not required. If you have ever used our software and thought of an idea to improve it, this is the place to come share those ideas!
The dates for the phases of the Survey will be as follows:
- Phase 1: Submit, discuss, and revise proposals – Monday, Jan 23, 2023 to Sunday, Feb 6, 2023
- Phase 2: WMF/Community Tech reviews and organizes proposals – Monday, Jan 30, 2023 to Friday, Feb 10, 2023
- Phase 3: Vote on proposals – Friday, Feb 10, 2023 to Friday, Feb 24, 2023
- Phase 4: Results posted – Tuesday, Feb 28, 2023
If you want to start writing out your ideas ahead of the Survey, you can start thinking about your proposals and draft them in the CWS sandbox.
We are grateful to all who participated last year. See you in January 2023!
Tak! Community Tech, STei (WMF) 15. dec. 2022, 16:44 (UTC)
Global ban for PlanespotterA320/RespectCE
[redigér]Per the Global bans policy, I'm informing the project of this request for comment: m:Requests for comment/Global ban for PlanespotterA320 (2) about banning a member from your community. Thank you.--Lemonaka (talk) 21:40, 6 February 2023 (UTC)
Editing news 2023 #1
[redigér]Read this in another language • Subscription list for this multilingual newsletter
This newsletter includes two key updates about the Editing team's work:
- The Editing team will finish adding new features to the Talk pages project and deploy it.
- They are beginning a new project, Edit check.
Talk pages project
The Editing team is nearly finished with this first phase of the Talk pages project. Nearly all new features are available now in the Beta Feature for Discussion tools.
It will show information about how active a discussion is, such as the date of the most recent comment. There will soon be a new "Tilføj emne" button. You will be able to turn them off at Special:Preferences#mw-prefsection-editing-discussion. Please tell them what you think.
An A/B test for Discussion tools on the mobile site has finished. Editors were more successful with Discussion tools. The Editing team is enabling these features for all editors on the mobile site.
New Project: Edit Check
The Editing team is beginning a project to help new editors of Wikipedia. It will help people identify some problems before they click "Offentliggør ændringer". The first tool will encourage people to add references when they add new content. Please watch that page for more information. You can join a conference call on 3 March 2023 to learn more.
–Whatamidoing (WMF) (diskussion) 22. feb. 2023, 23:25 (UTC)
Your wiki will be in read only soon
[redigér]Read this message in another language • Hjælp venligst med at oversætte til dit sprog
The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.
All traffic will switch on 1 March. The test will start at 14:00 UTC.
Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.
You will be able to read, but not edit, all wikis for a short period of time.
- You will not be able to edit for up to an hour on Wednesday 1 March 2023.
- If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
- Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
- We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
- GitLab will be unavailable for about 90 minutes.
Trizek (WMF) (Diskussion) 27. feb. 2023, 21:21 (UTC)
Wikimania 2023 Welcoming Program Submissions
[redigér]
Your wiki will be in read-only soon
[redigér]Read this message in another language • Hjælp venligst med at oversætte til dit sprog
The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.
All traffic will switch on 26 April. The test will start at 14:00 UTC.
Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.
You will be able to read, but not edit, all wikis for a short period of time.
- You will not be able to edit for up to an hour on Wednesday 26 April 2023.
- If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
- Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
- We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
- GitLab will be unavailable for about 90 minutes.
MediaWiki message delivery 21. apr. 2023, 00:41 (UTC)
Seeking volunteers for the next step in the Universal Code of Conduct process
[redigér]Hello,
As follow-up to the message about the Universal Code of Conduct Enforcement Guidelines by Wikimedia Foundation Board of Trustees Vice Chair, Shani Evenstein Sigalov, I am reaching out about the next steps. I want to bring your attention to the next stage of the Universal Code of Conduct process, which is forming a building committee for the Universal Code of Conduct Coordinating Committee (U4C). I invite community members with experience and deep interest in community health and governance to nominate themselves to be part of the U4C building committee, which needs people who are:
- Community members in good standing
- Knowledgeable about movement community processes, such as, but not limited to, policy drafting, participatory decision making, and application of existing rules and policies on Wikimedia projects
- Aware and appreciative of the diversity of the movement, such as, but not limited to, languages spoken, identity, geography, and project type
- Committed to participate for the entire U4C Building Committee period from mid-May - December 2023
- Comfortable with engaging in difficult, but productive conversations
- Confidently able to communicate in English
The Building Committee shall consist of volunteer community members, affiliate board or staff, and Wikimedia Foundation staff.
The Universal Code of Conduct has been a process strengthened by the skills and knowledge of the community and I look forward to what the U4C Building Committee creates. If you are interested in joining the Building Committee, please either sign up on the Meta-Wiki page, or contact ucocprojectwikimedia.org by May 12, 2023. Read more on Meta-Wiki.
Best regards,
Xeno (WMF) 26. apr. 2023, 19:01 (UTC)
Global ban proposal for Leonardo José Raimundo
[redigér]Apologies for writing in English. Hjælp venligst med at oversætte til dit sprog There is an on-going discussion about a proposal that Leonardo José Raimundo be globally banned from editing all Wikimedia projects. You are invited to participate at Requests for comment/Global ban for Leonardo José Raimundo on Meta-Wiki. Tak! Elton (diskussion) 26. maj 2023, 00:59 (UTC)
- As a result of m:Requests for comment/Global ban for Leonardo José Raimundo, Leonardo José Raimundo has been banned from all Wikimedia projects. --AntiCompositeNumber (diskussion) 8. jun. 2023, 02:12 (UTC)
Selection of the U4C Building Committee
[redigér]The next stage in the Universal Code of Conduct process is establishing a Building Committee to create the charter for the Universal Code of Conduct Coordinating Committee (U4C). The Building Committee has been selected. Read about the members and the work ahead on Meta-wiki.
-- UCoC Project Team, 27. maj 2023, 04:21 (UTC)
Announcing the new Elections Committee members
[redigér]Hello there,
We are glad to announce the new members and advisors of the Elections Committee. The Elections Committee assists with the design and implementation of the process to select Community- and Affiliate-Selected trustees for the Wikimedia Foundation Board of Trustees. After an open nomination process, the strongest candidates spoke with the Board and four candidates were asked to join the Elections Committee. Four other candidates were asked to participate as advisors.
Thank you to all the community members who submitted their names for consideration. We look forward to working with the Elections Committee in the near future.
On behalf of the Wikimedia Foundation Board of Trustees,
RamzyM (WMF) 28. jun. 2023, 18:00 (UTC)
Deploying the Phonos in-line audio player to your Wiki
[redigér]Hej!
Apologies if this message is not in your language, ⧼Please help translate⧽ to your language.
This wiki will soon be able to use the inline audio player implemented by the Phonos extension. This is part of fulfilling a wishlist proposal of providing audio links that play on click.
With the inline audio player, you can add text-to-speech audio snippets to wiki pages by simply using a tag:
<phonos file="audio file" label="Listen"/>
The above tag will show the text next to a speaker icon, and clicking on it will play the audio instantly without taking you to another page. A common example where you can use this feature is in adding pronunciation to words as illustrated on the English Wiktionary below.
{{audio|en|En-uk-English.oga|Audio (UK)}}
Could become:
<phonos file="En-uk-English.oga" label="Audio (UK)"/>
The inline audio player will be available in your wiki in 2 weeks time; in the meantime, we would like you to read about the features and give us feedback or ask questions about it in this talk page.
Thank you!UOzurumba (WMF), on behalf of the Foundation's Language team
27. jul. 2023, 02:26 (UTC)
Review the Charter for the Universal Code of Conduct Coordinating Committee
[redigér]Hello all,
I am pleased to share the next step in the Universal Code of Conduct work. The Universal Code of Conduct Coordinating Committee (U4C) draft charter is now ready for your review.
The Enforcement Guidelines require a Building Committee form to draft a charter that outlines procedures and details for a global committee to be called the Universal Code of Conduct Coordinating Committee (U4C). Over the past few months, the U4C Building Committee worked together as a group to discuss and draft the U4C charter. The U4C Building Committee welcomes feedback about the draft charter now through 22 September 2023. After that date, the U4C Building Committee will revise the charter as needed and a community vote will open shortly afterward.
Join the conversation during the conversation hours or on Meta-wiki.
Best,
RamzyM (WMF), on behalf of the U4C Building Committee, 28. aug. 2023, 15:35 (UTC)
Your wiki will be in read-only soon
[redigér]Read this message in another language • Hjælp venligst med at oversætte til dit sprog
The Wikimedia Foundation will switch the traffic between its data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.
All traffic will switch on 20 September. The test will start at 14:00 UTC.
Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.
You will be able to read, but not edit, all wikis for a short period of time.
- You will not be able to edit for up to an hour on Wednesday 20 September 2023.
- If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
- Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
- We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
- GitLab will be unavailable for about 90 minutes.
Trizek_(WMF) (talk) 15. sep. 2023, 09:23 (UTC)
Opportunities open for the Affiliations Committee, Ombuds commission, and the Case Review Committee
[redigér]You can find this message translated into additional languages on Meta-wiki.
Flere sprog • Hjælp venligst med at oversætte til dit sprogHi everyone! The Affiliations Committee (AffCom), Ombuds commission (OC), and the Case Review Committee (CRC) are looking for new members. These volunteer groups provide important structural and oversight support for the community and movement. People are encouraged to nominate themselves or encourage others they feel would contribute to these groups to apply. There is more information about the roles of the groups, the skills needed, and the opportunity to apply on the Meta-wiki page.
On behalf of the Committee Support team,
Review and comment on the 2024 Wikimedia Foundation Board of Trustees selection rules package
[redigér]Dear all,
Please review and comment on the Wikimedia Foundation Board of Trustees selection rules package from now until 29 October 2023. The selection rules package was based on older versions by the Elections Committee and will be used in the 2024 Board of Trustees selection. Providing your comments now will help them provide a smoother, better Board selection process. More on the Meta-wiki page.
Best,
Katie Chan
Chair of the Elections Committee
17. okt. 2023, 01:13 (UTC)
The Vector 2022 skin as the default in three weeks?
[redigér]Read this in your language • Hjælp venligst med at oversætte til dit sprog • Please tell other users about these changes
Hello. I'm writing on behalf of the Wikimedia Foundation Web team. In two weeks, we would like to make the Vector 2022 skin the default on this wiki.
If you prefer keeping the current skin select "Vector legacy (2010)" on the appearance tab of the global preferences and save the change. We encourage you to give the new skin a try, though.
Since I last came to you with this question, many things have changed. The skin is now the default on most Wikipedias, and all logos are done! We have also made some tweaks in the skin itself. Below is the text I've sent to you once, but I'm sending it again, just slightly edited, for those who haven't seen it.
If you know what this is about, jump straight to the section "Our plan":
It would become the default for all logged-out users, and also all logged-in users who currently use Vector legacy as a local (but not global) preference. Logged-in users can at any time switch to any other skin. No changes are expected for these skins.
About the skin
[redigér][Why is a change necessary] When the current default skin was created, it reflected the needs of the readers and editors as these were 14 years ago. Since then, new users have begun using the Internet and Wikimedia projects in different ways. The old Vector does not meet their needs.
[Objective] The objective for the Vector 2022 skin is to make the interface more welcoming and comfortable for readers and useful for advanced users. It introduces a series of changes that aim to improve problems new and existing readers and editors were having with the old skin. It draws inspiration from previous user requests, the Community Wishlist Surveys, and gadgets and scripts. The work helped our code follow the standards and improve all other skins. The PHP code in the other available skins has been reduced by 75%. The project has also focused on making it easier to support gadgets and use APIs.
[Changes in a nutshell] The skin introduces changes that improve readability and usability. The new skin does not remove any functionality currently available on the Vector skin.
- The limited width and pin-able menus allow to adjust the interface to the screen size, and focus on editing or reading. Logged-in and logged-out users may use a toggle button to keep the full width, though.
- The sticky header makes it easier to find tools that editors use often. It decreases scrolling to the top of the page by 16%.
- The new table of contents makes it easier to navigate to different sections. Readers and editors jump to different sections of the page 50% more than with the old table of contents. It also looks a bit different on talk pages.
- The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the tested wikis.
- The skin does not negatively affect pageviews, edit rates, or account creation. There is evidence of increases in pageviews and account creation across partner communities.
[Customize this skin] It's possible to configure and personalize our changes. We support volunteers who create new gadgets and user scripts. Check out the repository for a list of currently available customizations and changes, or add your own.
Our plan
[redigér]If no large concerns are raised, we plan on deploying on 14 November. If you'd like to ask our team anything, if you have questions, concerns, or additional thoughts, please comment in any language. If this is the first comment to my message, make sure to ping me. We will gladly answer! Also, check out our FAQ. Thank you! SGrabarczuk (WMF) (diskussion) 26. okt. 2023, 01:09 (UTC)
(New) Feature on Kartographer: Adding geopoints via QID
[redigér]Since September 2022, it is possible to create geopoints using a QID. Many wiki contributors have asked for this feature, but it is not being used much. Therefore, we would like to remind you about it. More information can be found on the project page. If you have any comments, please let us know on the talk page. – Best regards, the team of Technical Wishes at Wikimedia Deutschland
Thereza Mengs (WMDE) 13. dec. 2023, 12:31 (UTC)
Do you use Wikidata in Wikimedia sibling projects? Tell us about your experiences
[redigér]Note: Apologies for cross-posting and sending in English.
Hello, the Wikidata for Wikimedia Projects team at Wikimedia Deutschland would like to hear about your experiences using Wikidata in the sibling projects. If you are interested in sharing your opinion and insights, please consider signing up for an interview with us in this Registration form.
Currently, we are only able to conduct interviews in English.
The front page of the form has more details about what the conversation will be like, including how we would compensate you for your time.
For more information, visit our project issue page where you can also share your experiences in written form, without an interview.
We look forward to speaking with you, Danny Benjafield (WMDE) (talk) 08:53, 5 January 2024 (UTC)
Reusing references: Can we look over your shoulder?
[redigér]Apologies for writing in English.
The Technical Wishes team at Wikimedia Deutschland is planning to make reusing references easier. For our research, we are looking for wiki contributors willing to show us how they are interacting with references.
- The format will be a 1-hour video call, where you would share your screen. More information here.
- Interviews can be conducted in English, German or Dutch.
- Compensation is available.
- Sessions will be held in January and February.
- Sign up here if you are interested.
- Please note that we probably won’t be able to have sessions with everyone who is interested. Our UX researcher will try to create a good balance of wiki contributors, e.g. in terms of wiki experience, tech experience, editing preferences, gender, disability and more. If you’re a fit, she will reach out to you to schedule an appointment.
We’re looking forward to seeing you, Thereza Mengs (WMDE)
Vote on the Charter for the Universal Code of Conduct Coordinating Committee
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Hello all,
I am reaching out to you today to announce that the voting period for the Universal Code of Conduct Coordinating Committee (U4C) Charter is now open. Community members may cast their vote and provide comments about the charter via SecurePoll now through 2 February 2024. Those of you who voiced your opinions during the development of the UCoC Enforcement Guidelines will find this process familiar.
The current version of the U4C Charter is on Meta-wiki with translations available.
Read the charter, go vote and share this note with others in your community. I can confidently say the U4C Building Committee looks forward to your participation.
On behalf of the UCoC Project team,
RamzyM (WMF) 19. jan. 2024, 18:09 (UTC)
Last days to vote on the Charter for the Universal Code of Conduct Coordinating Committee
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Hello all,
I am reaching out to you today to remind you that the voting period for the Universal Code of Conduct Coordinating Committee (U4C) charter will close on 2 February 2024. Community members may cast their vote and provide comments about the charter via SecurePoll. Those of you who voiced your opinions during the development of the UCoC Enforcement Guidelines will find this process familiar.
The current version of the U4C charter is on Meta-wiki with translations available.
Read the charter, go vote and share this note with others in your community. I can confidently say the U4C Building Committee looks forward to your participation.
On behalf of the UCoC Project team,
RamzyM (WMF) 31. jan. 2024, 17:01 (UTC)
Announcing the results of the UCoC Coordinating Committee Charter ratification vote
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Dear all,
Thank you everyone for following the progress of the Universal Code of Conduct. I am writing to you today to announce the outcome of the ratification vote on the Universal Code of Conduct Coordinating Committee Charter. 1746 contributors voted in this ratification vote with 1249 voters supporting the Charter and 420 voters not. The ratification vote process allowed for voters to provide comments about the Charter.
A report of voting statistics and a summary of voter comments will be published on Meta-wiki in the coming weeks.
Please look forward to hearing about the next steps soon.
On behalf of the UCoC Project team,
RamzyM (WMF) 12. feb. 2024, 18:24 (UTC)
Report of the U4C Charter ratification and U4C Call for Candidates now available
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Hello all,
I am writing to you today with two important pieces of information. First, the report of the comments from the Universal Code of Conduct Coordinating Committee (U4C) Charter ratification is now available. Secondly, the call for candidates for the U4C is open now through April 1, 2024.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members are invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.
Per the charter, there are 16 seats on the U4C: eight community-at-large seats and eight regional seats to ensure the U4C represents the diversity of the movement.
Read more and submit your application on Meta-wiki.
On behalf of the UCoC project team,
RamzyM (WMF) 5. mar. 2024, 16:25 (UTC)
Wikimedia Foundation Board of Trustees 2024 Selection
[redigér]Dear all,
This year, the term of 4 (four) Community- and Affiliate-selected Trustees on the Wikimedia Foundation Board of Trustees will come to an end [1]. The Board invites the whole movement to participate in this year’s selection process and vote to fill those seats.
The Elections Committee will oversee this process with support from Foundation staff [2]. The Board Governance Committee created a Board Selection Working Group from Trustees who cannot be candidates in the 2024 community- and affiliate-selected trustee selection process composed of Dariusz Jemielniak, Nataliia Tymkiv, Esra'a Al Shafei, Kathy Collins, and Shani Evenstein Sigalov [3]. The group is tasked with providing Board oversight for the 2024 trustee selection process, and for keeping the Board informed. More details on the roles of the Elections Committee, Board, and staff are here [4].
Here are the key planned dates:
- May 2024: Call for candidates and call for questions
- June 2024: Affiliates vote to shortlist 12 candidates (no shortlisting if 15 or less candidates apply) [5]
- June-August 2024: Campaign period
- End of August / beginning of September 2024: Two-week community voting period
- October–November 2024: Background check of selected candidates
- Board's Meeting in December 2024: New trustees seated
Learn more about the 2024 selection process - including the detailed timeline, the candidacy process, the campaign rules, and the voter eligibility criteria - on this Meta-wiki page, and make your plan.
Election Volunteers
Another way to be involved with the 2024 selection process is to be an Election Volunteer. Election Volunteers are a bridge between the Elections Committee and their respective community. They help ensure their community is represented and mobilize them to vote. Learn more about the program and how to join on this Meta-wiki page.
Best regards,
Dariusz Jemielniak (Governance Committee Chair, Board Selection Working Group)
[5] Even though the ideal number is 12 candidates for 4 open seats, the shortlisting process will be triggered if there are more than 15 candidates because the 1-3 candidates that are removed might feel ostracized and it would be a lot of work for affiliates to carry out the shortlisting process to only eliminate 1-3 candidates from the candidate list.
MPossoupe_(WMF)12. mar. 2024, 19:57 (UTC)
Your wiki will be in read-only soon
[redigér]Read this message in another language • Hjælp venligst med at oversætte til dit sprog
The Wikimedia Foundation will switch the traffic between its data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster.
All traffic will switch on 20 March. The test will start at 14:00 UTC.
Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.
You will be able to read, but not edit, all wikis for a short period of time.
- You will not be able to edit for up to an hour on Wednesday 20 March 2024.
- If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
- Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
- We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
- GitLab will be unavailable for about 90 minutes.
Trizek (WMF), 15. mar. 2024, 00:00 (UTC)
Søudtryk
[redigér]Jag har i Projekt Runeberg lagt in den danska Opfindelsernes Bog (1877-1883) och där finns i del 2 en 25 sidor lång Ordfortegnelse over de vigtigste Søudtryk som kanske kan vara av intresse för Wiktionary. Det finns också i del 4 en kort lista över Kemiske Betegnelser, der ere forskjellige paa Dansk og Norsk. --LA2 (diskussion) 29. mar. 2024, 22:23 (UTC)
Vote now to select members of the first U4C
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Dear all,
I am writing to you to let you know the voting period for the Universal Code of Conduct Coordinating Committee (U4C) is open now through May 9, 2024. Read the information on the voting page on Meta-wiki to learn more about voting and voter eligibility.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.
Please share this message with members of your community so they can participate as well.
On behalf of the UCoC project team,
RamzyM (WMF) 25. apr. 2024, 20:21 (UTC)
Sign up for the language community meeting on May 31st, 16:00 UTC
[redigér]Hello all,
The next language community meeting is scheduled in a few weeks - May 31st at 16:00 UTC. If you're interested, you can sign up on this wiki page.
This is a participant-driven meeting, where we share language-specific updates related to various projects, collectively discuss technical issues related to language wikis, and work together to find possible solutions. For example, in the last meeting, the topics included the machine translation service (MinT) and the languages and models it currently supports, localization efforts from the Kiwix team, and technical challenges with numerical sorting in files used on Bengali Wikisource.
Do you have any ideas for topics to share technical updates related to your project? Any problems that you would like to bring for discussion during the meeting? Do you need interpretation support from English to another language? Please reach out to me at ssethi(__AT__)wikimedia.org and add agenda items to the document here.
We look forward to your participation!
MediaWiki message delivery 14. maj 2024, 21:23 (UTC)
Feedback invited on Procedure for Sibling Project Lifecycle
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Dear community members,
The Community Affairs Committee (CAC) of the Wikimedia Foundation Board of Trustees invites you to give feedback on a draft Procedure for Sibling Project Lifecycle. This draft Procedure outlines proposed steps and requirements for opening and closing Wikimedia Sibling Projects, and aims to ensure any newly approved projects are set up for success. This is separate from the procedures for opening or closing language versions of projects, which is handled by the Language Committee or closing projects policy.
You can find the details on this page, as well as the ways to give your feedback from today until the end of the day on June 23, 2024, anywhere on Earth.
You can also share information about this with the interested project communities you work with or support, and you can also help us translate the procedure into more languages, so people can join the discussions in their own language.
On behalf of the CAC,
RamzyM (WMF) 22. maj 2024, 02:26 (UTC)
Announcing the first Universal Code of Conduct Coordinating Committee
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Hello,
The scrutineers have finished reviewing the vote results. We are following up with the results of the first Universal Code of Conduct Coordinating Committee (U4C) election.
We are pleased to announce the following individuals as regional members of the U4C, who will fulfill a two-year term:
- North America (USA and Canada)
- –
- Northern and Western Europe
- Latin America and Caribbean
- –
- Central and East Europe (CEE)
- —
- Sub-Saharan Africa
- –
- Middle East and North Africa
- East, South East Asia and Pacific (ESEAP)
- South Asia
- –
The following individuals are elected to be community-at-large members of the U4C, fulfilling a one-year term:
- Barkeep49
- Superpes15
- Civvì
- Luke081515
- –
- –
- –
- –
Thank you again to everyone who participated in this process and much appreciation to the candidates for your leadership and dedication to the Wikimedia movement and community.
Over the next few weeks, the U4C will begin meeting and planning the 2024-25 year in supporting the implementation and review of the UCoC and Enforcement Guidelines. Follow their work on Meta-wiki.
On behalf of the UCoC project team,
RamzyM (WMF) 3. jun. 2024, 08:15 (UTC)
The final text of the Wikimedia Movement Charter is now on Meta
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Hi everyone,
The final text of the Wikimedia Movement Charter is now up on Meta in more than 20 languages for your reading.
What is the Wikimedia Movement Charter?
The Wikimedia Movement Charter is a proposed document to define roles and responsibilities for all the members and entities of the Wikimedia movement, including the creation of a new body – the Global Council – for movement governance.
Join the Wikimedia Movement Charter “Launch Party”
Join the “Launch Party” on June 20, 2024 at 14.00-15.00 UTC (your local time). During this call, we will celebrate the release of the final Charter and present the content of the Charter. Join and learn about the Charter before casting your vote.
Movement Charter ratification vote
Voting will commence on SecurePoll on June 25, 2024 at 00:01 UTC and will conclude on July 9, 2024 at 23:59 UTC. You can read more about the voting process, eligibility criteria, and other details on Meta.
If you have any questions, please leave a comment on the Meta talk page or email the MCDC at mcdc@wikimedia.org.
On behalf of the MCDC,
RamzyM (WMF) 11. jun. 2024, 08:45 (UTC)
Voting to ratify the Wikimedia Movement Charter is now open – cast your vote
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Hello everyone,
The voting to ratify the Wikimedia Movement Charter is now open. The Wikimedia Movement Charter is a document to define roles and responsibilities for all the members and entities of the Wikimedia movement, including the creation of a new body – the Global Council – for movement governance.
The final version of the Wikimedia Movement Charter is available on Meta in different languages and attached here in PDF format for your reading.
Voting commenced on SecurePoll on June 25, 2024 at 00:01 UTC and will conclude on July 9, 2024 at 23:59 UTC. Please read more on the voter information and eligibility details.
After reading the Charter, please vote here and share this note further.
If you have any questions about the ratification vote, please contact the Charter Electoral Commission at cec@wikimedia.org.
On behalf of the CEC,
RamzyM (WMF) 25. jun. 2024, 10:52 (UTC)
Voting to ratify the Wikimedia Movement Charter is ending soon
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Hello everyone,
This is a kind reminder that the voting period to ratify the Wikimedia Movement Charter will be closed on July 9, 2024, at 23:59 UTC.
If you have not voted yet, please vote on SecurePoll.
On behalf of the Charter Electoral Commission,
RamzyM (WMF) 8. jul. 2024, 03:47 (UTC)
U4C Special Election - Call for Candidates
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Hello all,
A special election has been called to fill additional vacancies on the U4C. The call for candidates phase is open from now through July 19, 2024.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members are invited to submit their applications in the special election for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.
In this special election, according to chapter 2 of the U4C charter, there are 9 seats available on the U4C: four community-at-large seats and five regional seats to ensure the U4C represents the diversity of the movement. No more than two members of the U4C can be elected from the same home wiki. Therefore, candidates must not have English Wikipedia, German Wikipedia, or Italian Wikipedia as their home wiki.
Read more and submit your application on Meta-wiki.
In cooperation with the U4C,
-- Keegan (WMF) (talk) 10. jul. 2024, 00:03 (UTC)
Wikimedia Movement Charter ratification voting results
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Hello everyone,
After carefully tallying both individual and affiliate votes, the Charter Electoral Commission is pleased to announce the final results of the Wikimedia Movement Charter voting.
As communicated by the Charter Electoral Commission, we reached the quorum for both Affiliate and individual votes by the time the vote closed on July 9, 23:59 UTC. We thank all 2,451 individuals and 129 Affiliate representatives who voted in the ratification process. Your votes and comments are invaluable for the future steps in Movement Strategy.
The final results of the Wikimedia Movement Charter ratification voting held between 25 June and 9 July 2024 are as follows:
Individual vote:
Out of 2,451 individuals who voted as of July 9 23:59 (UTC), 2,446 have been accepted as valid votes. Among these, 1,710 voted “yes”; 623 voted “no”; and 113 selected “–” (neutral). Because the neutral votes don’t count towards the total number of votes cast, 73.30% voted to approve the Charter (1710/2333), while 26.70% voted to reject the Charter (623/2333).
Affiliates vote:
Out of 129 Affiliates designated voters who voted as of July 9 23:59 (UTC), 129 votes are confirmed as valid votes. Among these, 93 voted “yes”; 18 voted “no”; and 18 selected “–” (neutral). Because the neutral votes don’t count towards the total number of votes cast, 83.78% voted to approve the Charter (93/111), while 16.22% voted to reject the Charter (18/111).
Board of Trustees of the Wikimedia Foundation:
The Wikimedia Foundation Board of Trustees voted not to ratify the proposed Charter during their special Board meeting on July 8, 2024. The Chair of the Wikimedia Foundation Board of Trustees, Nataliia Tymkiv, shared the result of the vote, the resolution, meeting minutes and proposed next steps.
With this, the Wikimedia Movement Charter in its current revision is not ratified.
We thank you for your participation in this important moment in our movement’s governance.
The Charter Electoral Commission,
Abhinav619, Borschts, Iwuala Lucy, Tochiprecious, Der-Wir-Ing
MediaWiki message delivery (diskussion) 18. jul. 2024, 17:53 (UTC)
Vote now to fill vacancies of the first U4C
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Dear all,
I am writing to you to let you know the voting period for the Universal Code of Conduct Coordinating Committee (U4C) is open now through August 10, 2024. Read the information on the voting page on Meta-wiki to learn more about voting and voter eligibility.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.
Please share this message with members of your community so they can participate as well.
In cooperation with the U4C,
RamzyM (WMF) 27. jul. 2024, 02:47 (UTC)
Reminder! Vote closing soon to fill vacancies of the first U4C
[redigér]- You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Dear all,
The voting period for the Universal Code of Conduct Coordinating Committee (U4C) is closing soon. It is open through 10 August 2024. Read the information on the voting page on Meta-wiki to learn more about voting and voter eligibility. If you are eligible to vote and have not voted in this special election, it is important that you vote now.
Why should you vote? The U4C is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community input into the committee membership is critical to the success of the UCoC.
Please share this message with members of your community so they can participate as well.
In cooperation with the U4C,
-- Keegan (WMF) (talk) 6. aug. 2024, 15:30 (UTC)
Det kommer snart: En ny underreferencerfunktion - prøv det!
[redigér]Hej. Fællesskabets medlemmer har i mange år efterspurgt en let måde at genbruge henvisninger med forskellige detaljer. Nu er der en MediaWiki-løsning på vej: Den nye henvisningsmulighed kommer til at kunne bruges i wikitext og Visual Editor, og den vil udvide det eksisterende henvisningssystem. Man kan stadig bruge forskellige måder at henvise på, men man vil sikkert møde underhenvisninger i artikler, der er skrevet af andre brugere. Der er flere informationer på projektets side.
Vi har brug for dit feedback, så vi kan være sikre på, at muligheden virker godt for dig:
- Prøv venligst den nuværende udviklingstilstand på beta wiki og lad os vide, hvad du mener.
- Meld dig til her, så du kan få opdateringer og/eller invitationer til at deltage i brugernes undersøgelser.
Wikimedia Deutschland’s hold for Tekniske Ønsker har planer om at indføre denne mulighed på Wikimedia wiki'erne senere på året. Vi vil henvende os til opbyggerne/vedligeholderne af værktøjer og templates, der på forhånd er knyttet til henvisninger.
Hjælp os venligst med at udbrede denne besked. --Johannes Richter (WMDE) (talk) 10:36, 19 August 2024 (UTC)
Sign up for the language community meeting on August 30th, 15:00 UTC
[redigér]Hi all,
The next language community meeting is scheduled in a few weeks—on August 30th at 15:00 UTC. If you're interested in joining, you can sign up on this wiki page.
This participant-driven meeting will focus on sharing language-specific updates related to various projects, discussing technical issues related to language wikis, and working together to find possible solutions. For example, in the last meeting, topics included the Language Converter, the state of language research, updates on the Incubator conversations, and technical challenges around external links not working with special characters on Bengali sites.
Do you have any ideas for topics to share technical updates or discuss challenges? Please add agenda items to the document here and reach out to ssethi(__AT__)wikimedia.org. We look forward to your participation!
MediaWiki message delivery (diskussion) 22. aug. 2024, 23:20 (UTC)
Announcing the Universal Code of Conduct Coordinating Committee
[redigér]- Original message at wikimedia-l. You can find this message translated into additional languages on Meta-wiki. Hjælp venligst med at oversætte til dit sprog
Hello all,
The scrutineers have finished reviewing the vote and the Elections Committee have certified the results for the Universal Code of Conduct Coordinating Committee (U4C) special election.
I am pleased to announce the following individual as regional members of the U4C, who will fulfill a term until 15 June 2026:
- North America (USA and Canada)
- Ajraddatz
The following seats were not filled during this special election:
- Latin America and Caribbean
- Central and East Europe (CEE)
- Sub-Saharan Africa
- South Asia
- The four remaining Community-At-Large seats
Thank you again to everyone who participated in this process and much appreciation to the candidates for your leadership and dedication to the Wikimedia movement and community.
Over the next few weeks, the U4C will begin meeting and planning the 2024-25 year in supporting the implementation and review of the UCoC and Enforcement Guidelines. You can follow their work on Meta-Wiki.
On behalf of the U4C and the Elections Committee,
RamzyM (WMF) 2. sep. 2024, 14:07 (UTC)
Have your say: Vote for the 2024 Board of Trustees!
[redigér]Hello all,
The voting period for the 2024 Board of Trustees election is now open. There are twelve (12) candidates running for four (4) seats on the Board.
Learn more about the candidates by reading their statements and their answers to community questions.
When you are ready, go to the SecurePoll voting page to vote. The vote is open from September 3rd at 00:00 UTC to September 17th at 23:59 UTC.
To check your voter eligibility, please visit the voter eligibility page.
Best regards,
The Elections Committee and Board Selection Working Group
MediaWiki message delivery (diskussion) 3. sep. 2024, 12:15 (UTC)
Your wiki will be in read-only soon
[redigér]Read this message in another language • Hjælp venligst med at oversætte til dit sprog
The Wikimedia Foundation will switch the traffic between its data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster.
All traffic will switch on 25 September. The switch will start at 15:00 UTC.
Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.
A banner will be displayed on all wikis 30 minutes before this operation happens. This banner will remain visible until the end of the operation.
You will be able to read, but not edit, all wikis for a short period of time.
- You will not be able to edit for up to an hour on Wednesday 25 September 2024.
- If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
- Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
- We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
- GitLab will be unavailable for about 90 minutes.
This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule.
Please share this information with your community.Trizek_(WMF), 20. sep. 2024, 09:36 (UTC)
'Wikidata item' link is moving. Find out where...
[redigér]Hello everyone, a small change will soon be coming to the user-interface of your Wikimedia project. The Wikidata item sitelink currently found under the General section of the Tools sidebar menu will move into the In Other Projects section.
We would like the Wiki communities feedback so please let us know or ask questions on the Discussion page before we enable the change which can take place October 4 2024, circa 15:00 UTC+2.
More information can be found on the project page.
We welcome your feedback and questions.
MediaWiki message delivery (diskussion) 27. sep. 2024, 18:56 (UTC)
Invitation to Participate in Wiki Loves Ramadan Community Engagement Survey
[redigér]Dear all,
Apologies for writing in English. Please help to translate in your language. We are excited to announce the upcoming Wiki Loves Ramadan event, a global initiative aimed at celebrating Ramadan by enriching Wikipedia and its sister projects with content related to this significant time of year. As we plan to organize this event globally, your insights and experiences are crucial in shaping the best possible participation experience for the community.
To ensure that Wiki Loves Ramadan is engaging, inclusive, and impactful, we kindly invite you to participate in our community engagement survey. Your feedback will help us understand the needs of the community, set the event's focus, and guide our strategies for organizing this global event.
Survey link: https://forms.gle/f66MuzjcPpwzVymu5
Please take a few minutes to share your thoughts. Your input will make a difference!
Thank you for being a part of our journey to make Wiki Loves Ramadan a success.
Warm regards,
User:ZI Jony 6. okt. 2024, 03:19 (UTC)
Wiki Loves Ramadan Organizing Team
Preliminary results of the 2024 Wikimedia Foundation Board of Trustees elections
[redigér]Hello all,
Thank you to everyone who participated in the 2024 Wikimedia Foundation Board of Trustees election. Close to 6000 community members from more than 180 wiki projects have voted.
The following four candidates were the most voted:
While these candidates have been ranked through the vote, they still need to be appointed to the Board of Trustees. They need to pass a successful background check and meet the qualifications outlined in the Bylaws. New trustees will be appointed at the next Board meeting in December 2024.
Learn more about the results on Meta-Wiki.
Best regards,
The Elections Committee and Board Selection Working Group
MPossoupe_(WMF) 14. okt. 2024, 08:26 (UTC)
Seeking volunteers to join several of the movement’s committees
[redigér]Each year, typically from October through December, several of the movement’s committees seek new volunteers.
Read more about the committees on their Meta-wiki pages:
Applications for the committees open on 16 October 2024. Applications for the Affiliations Committee close on 18 November 2024, and applications for the Ombuds commission and the Case Review Committee close on 2 December 2024. Learn how to apply by visiting the appointment page on Meta-wiki. Post to the talk page or email cst@wikimedia.org with any questions you may have.
For the Committee Support team,
-- Keegan (WMF) (talk) 16. okt. 2024, 23:09 (UTC)
'Wikidata item' link is moving, finally.
[redigér]Hello everyone, I previously wrote on the 27th September to advise that the Wikidata item sitelink will change places in the sidebar menu, moving from the General section into the In Other Projects section. The scheduled rollout date of 04.10.2024 was delayed due to a necessary request for Mobile/MinervaNeue skin. I am happy to inform that the global rollout can now proceed and will occur later today, 22.10.2024 at 15:00 UTC-2. Please let us know if you notice any problems or bugs after this change. There should be no need for null-edits or purging cache for the changes to occur. Kind regards, -Danny Benjafield (WMDE) 22. okt. 2024, 11:28 (UTC)
Problems with Expressions and -expr- Template
[redigér]Hello all, sorry to write in English, but I do not speak Danish at all.
I'm a Wiktionarian, NLP researcher and I am the author of DBnary, a tool that extracts many language editions of wiktionaries and make it freely available as linked data. I have recently been asked to extract the Danish edition and the extractor is now almost fully operational and Danish is the 26th edition extracted by DBnary.
During the extraction process, I wander around the pages and saw a strange choice in the page encodings that leads to difficulties in extracting, but more importantly to inconsistencies in many entries. The problem comes with the -expr- Template used ambiguously for the definition of "Expressions" (Udtryk) as Lexical entries and the definition of expressions involving the currently described lexical entry.
As far as I can tell, the main usage is to add a language tag as argument in {{-expr-|da}} for the former and no argument as in {{-expr-}} for the later. It is only a usage as the argument is never used nor tested by the template itself and no category is added for the former. There are also some errors, which I corrected to add more consistency in the current status. This usage is also mentioned in some documentation pages like Wiktionary:WikiProjekt Fransk/Værktøj and Wiktionary:Skabeloner.
The main problem comes from the fact that the former use should involve a level 3 heading and the later use a level 4 heading. This leads to pages where the structure is unclear and the entry rendering is puzzling as the Part Of Speech appears too small (as in tueur en série). To avoid this, few pages used directly a Heading as in viel Geschrei und wenig Wolle.
Would it be interesting to create a new template for the first usage (Udtryk as a Part of Speech, that would take a language code as first arg and create the correct heading along the correct category (as -noun- or other PoS templates. The list of entries that would be impacted by the decision is given in may user page User:dodecaplex. What do you think of this proposal, would somebody volunteer to create such a template and correct the mentioned entries ?
Thanks in advance.
Final Reminder: Join us in Making Wiki Loves Ramadan Success
[redigér]Dear all,
We’re thrilled to announce the Wiki Loves Ramadan event, a global initiative to celebrate Ramadan by enhancing Wikipedia and its sister projects with valuable content related to this special time of year. As we organize this event globally, we need your valuable input to make it a memorable experience for the community.
Last Call to Participate in Our Survey: To ensure that Wiki Loves Ramadan is inclusive and impactful, we kindly request you to complete our community engagement survey. Your feedback will shape the event’s focus and guide our organizing strategies to better meet community needs.
- Survey Link: Complete the Survey
- Deadline: November 10, 2024
Please take a few minutes to share your thoughts. Your input will truly make a difference!
Volunteer Opportunity: Join the Wiki Loves Ramadan Team! We’re seeking dedicated volunteers for key team roles essential to the success of this initiative. If you’re interested in volunteer roles, we invite you to apply.
- Application Link: Apply Here
- Application Deadline: October 31, 2024
Explore Open Positions: For a detailed list of roles and their responsibilities, please refer to the position descriptions here: Position Descriptions
Thank you for being part of this journey. We look forward to working together to make Wiki Loves Ramadan a success!
Warm regards,
The Wiki Loves Ramadan Organizing Team 29. okt. 2024, 05:11 (UTC)
Sign up for the language community meeting on November 29th, 16:00 UTC
[redigér]Hello everyone,
The next language community meeting is coming up next week, on November 29th, at 16:00 UTC (Zonestamp! For your timezone <https://zonestamp.toolforge.org/1732896000>). If you're interested in joining, you can sign up on this wiki page: <https://www.mediawiki.org/wiki/Wikimedia_Language_and_Product_Localization/Community_meetings#29_November_2024>.
This participant-driven meeting will be organized by the Wikimedia Foundation’s Language Product Localization team and the Language Diversity Hub. There will be presentations on topics like developing language keyboards, the creation of the Moore Wikipedia, and the language support track at Wiki Indaba. We will also have members from the Wayuunaiki community joining us to share their experiences with the Incubator and as a new community within our movement. This meeting will have a Spanish interpretation.
Looking forward to seeing you at the language community meeting! Cheers, Srishti 21. nov. 2024, 19:55 (UTC)