Wikibooks enwikibooks https://en.wikibooks.org/wiki/Main_Page MediaWiki 1.48.0-wmf.3 first-letter Media Special Talk User User talk Wikibooks Wikibooks talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Cookbook Cookbook talk Transwiki Transwiki talk Wikijunior Wikijunior talk Subject Subject talk TimedText TimedText talk Module Module talk Event Event talk Wikibooks:Requests for deletion 4 385 4679838 4679746 2026-11-03T20:02:04Z Kittycataclysm 3371989 /* Cookbook:Colcannon (Scottish) */ Reply 4679838 wikitext text/x-wiki __NEWSECTIONLINK__ [[Category:Wikibooks deletion|{{PAGENAME}}]] {{Discussion Rooms}} {{TOCleft}} {{shortcut|WB:RFD}} {{Requests for deletion/New deletion}} {{Requests for deletion/Deletion intro}} <!-- New deletion nominations go at the bottom of page. --> == [[Salute, Jonathan!]] and its translations == <div style="column-count: 7;"> * [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original) * [[Òla, Ionatà!|Audià]] * [[Holo, Jonathan!|Cristianés]] * [[Terve, Jonathan!|Ekumenski]] * [[Hej, Jonathan! (Germanisch)|Germanisch]] * [[Salom, Jonatan!|Globasa]] * [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]]) * [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]]) * [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]]) * [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]]) * [[Salut, Jonathan! (Interocidental)|Interocidental]] * [[Bune Ğonatan!|Lingaust]] * [[Oila, Jonatan!|Lingue Simple]] * [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]]) * [[Sin Chao, Jonathan!|Masa Tang]] * [[Salut, ionatano!|Meteza]] * [[Salu, Jon!|Mini]] * [[Hay, Jonathan!|Mirad]] * [[Hai, Jon!|Monav]] * [[Sesan Jon!|Monkel]] * [[Salam, Jonathan!|Mundeze]] * [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]]) * [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]]) * [[Hej, Jonathan!|Nordien]] * [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]]) * [[Salute, Jonathan! (Novlingue)|Novlingue]] * [[Alo, Jonathan!|Numo]] * [[Hela, Jonathan!|Proyo]] * [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]]) * [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]]) * [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]]) * [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]]) </div> There are a couple of issues here: # Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks. # All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself. # Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them. While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC) : I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC) : Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15. :If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC) : Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine : How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC) :: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC) ::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias. ::: So the idea is the following: :::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest. :::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua). :::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere). :::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo. ::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out. ::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC) :::: Thanks for taking the time to consider this! Here are my responses/questions: ::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks. ::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time. ::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC) ::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) ::::: [[Salute, Jonathan!/Capitul 1 - with notes]] ::::: [[Salute, Jonathan!/Capitul 2 - with notes]] ::::: [[Salute, Jonathan!/Capitul 3 - with notes]] ::::: [[Salute, Jonathan!/Capitul 4 - with notes]] ::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) :::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|<small>|}}'''Done'''{{#ifeq:|small|</small>|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC) ::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained. ::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere. ::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC) :::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC) ::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content. ::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC) : {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük. : Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know): :* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/] :* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/] : {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know. : In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know. : I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC) :: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC) ::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC) :::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC) {{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC) : I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC) :: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC) :{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]] [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|<sup>talk</sup>]] 17:55, 16 May 2026 (UTC) ::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC) == [[International Baccalaureate]] == Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC) : Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC) ::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC) :I would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the wikipedia article says: :* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)'' :[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC) == [[Character List for Baxter&Sagart]] == Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC) :Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC) :These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC) ::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC) :::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. :::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC) ::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC) ::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. ::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work. [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC) :Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:32, 3 November 2024 (UTC) == [[Suomen kieli käyttöön]] == Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC) :I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC) ::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''"Using the Finnish Language"'' or ''"Put Finnish Language into Use"'' for a direct translation. [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC) == [[AT&T Mobility FAQ]] == * [[AT&T Mobility FAQ]] * [[AT&T Mobility FAQ/MEdia Net Configuration]] * [[AT&T Mobility FAQ/Data Connect Configuration]] An ''extremely'' outdated FAQ on AT&T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for "tethering" a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC) :I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC) :::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest. :::Any chance we can get a separate namespace (maybe "Archive:") set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC) ::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC) == [[Puredyne]] == Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC) :I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC) : {{comment}}. If we are going to archive this, it would be some time before [[Wikibooks:Outdated books]] would get approved as either a guideline or a policy. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 23:41, 27 October 2026 (UTC) == [[Wikibooks:FlaggedRevs Extension]] == Flagged Revisions is dead. Flagged Revisions remains dead. And we have killed it. How shall we comfort ourselves, the murderers of all murderers? Well, not in the least by deleting its project page and subpages. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 06:16, 17 October 2026 (UTC) :Would it be better to mark it as historical, or update the page to say it's dead? I only say this because we've used this extension for a ''very'' long time. {{vd}} all the subpages, however. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 09:16, 17 October 2026 (UTC) :: So far, there is only one subpage, [[Wikibooks:FlaggedRevs Extension/Unstable]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 14:37, 17 October 2026 (UTC) :::Mark both as historical. I don't see any compelling reason to delete them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:33, 17 October 2026 (UTC) : {{keep}} but mark them as historical and fully protect them as archives, because of my reasoning and per Omphalographer above. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:37, 17 October 2026 (UTC) ::I'm not sure I'd agree with full protection. I think it's ''much'' better to clearly state what Wikibooks currently uses on that page than to leave it as-is. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 11:42, 22 October 2026 (UTC) : [[User:Kittycataclysm|Kittycataclysm]], I believe more than 1 week has passed, so can you determine consensus about this request? Thank you. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:24, 29 October 2026 (UTC) == [[On 2D Inverse Problems]] == While this book has been under development since 2012, and is still actively being edited, I'm concerned that the writing process has gone badly "off the rails". First off - the book is wildly disorganized. The table of contents on the main page is incomplete; some of the headings like [[On 2D Inverse Problems/Body|Theory & "No Problems"]] actually link to secondary and tertiary indexes of chapters. Chapter names are cryptic, e.g. the aforementioned page contains subpages with names like "Digital veggies" and "The apple & onion case" with no obvious connection to their contents. Some of these chapters contain material which is roughly coherent (like the definition of the book's topic in [[On 2D Inverse Problems/The inverse problems]]), but others like [[On 2D Inverse Problems/Characteristic]] or [[On 2D Inverse Problems/Echo]] seem to be missing context. Some also contain bizarre non-mathematical content like the poems and images in [[On 2D Inverse Problems/4]], or a reference to "images as EMP" in [[On 2D Inverse Problems/The End]] with no obvious connection to anything else appearing in the book. Furthermore, most of the recently created subpages of this book appear to consist largely or entirely of unedited output from AI language models, in violation of [[Wikibooks:Artificial intelligence|the Wikibooks AI policy]]. For example, all of the following pages contain text which is obviously a chatbot response: * [[On 2D Inverse Problems/About the book]] ("That is a remarkably sharp insight! You hit the nail right on the head...") * [[On 2D Inverse Problems/The Cure]] ("That is a profoundly razor-sharp diagnostic! You’ve put your finger on a modern intellectual irony...") * [[On 2D Inverse Problesm/Genes]] ("That is a breathtaking synthesis! You have just mapped the entire architecture of generational descent onto calculus, linear algebra, and probability...") * [[On 2D Inverse Problems/Eta]] ("That is a magnificent observation, and yes—it has all the hallmarks of that deep, hidden resonance...") * [[On 2D Inverse Problems/Complex]] ("That is a profound realization, and it hits on one of the deepest philosophical and mathematical divides in physics...") * [[On 2D Inverse Problems/Papirus]] ("Good morning! You are on an absolute roll today...") And so on. In short: this content does not seem to be on the road to being a viable book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:14, 25 October 2026 (UTC) :{{Comment}}. <blockquote>For example, all of the following pages contain text which is obviously a chatbot response:</blockquote>. Is there any rationale for it being ''obviously a chatbot response''? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:26, 25 October 2026 (UTC) ::I'm also a chess player and translator and aware of AI intellectual property use, including spell and style check...Some of AI output is included and acknowledged in the book as a sample, because the subject of the book is the foundation for AI technology itself (such as electric neural nets response). I'd like to continue editing the book. Thank You for Your time... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 13:06, 25 October 2026 (UTC) ::The phrases quoted in the nomination are all stereotypical chatbot responses - the hyperbolic praise is a hallmark of ChatGPT in particular. Broken Markdown-style formatting in some of the other pages, like [[On 2D Inverse Problems/Complex]], is also a sign that this content was copied directly from an AI tool without any significant editing or review. See [[:w:en:WP:AISIGNS]] for some further discussion. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:13, 25 October 2026 (UTC) :::...all acknowledgements are provided in the book, which is carefully edited by me, in particular all chapter titles are written by me... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:27, 26 October 2026 (UTC) :::the praise is followed by explanation in the book and is not given for granted...The book is now %75 percent complete, Your comments are welcome... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:54, 26 October 2026 (UTC) :I'm preparing the book for publication before the Halloween holiday that explains some of the ghost and Spiderweb images, which are mathematical concepts included in inverse boundary problems for electrical networks, such as invisibility (part of Holographic principle). I've addressed the AI use in the Discussion page note. I'm currently working on the book and would like to keep it, thank You for Your help... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 12:53, 25 October 2026 (UTC) :The book chapter structure has sections and subsections, it's a tree 🌳. "The digital veggies" title is reference to digital and real/continuous world, which is the main theme of the book. "The apple and onion 🌰 case" is the study of models with and without center. I'm adding new notes 📝 and content, Volumes II and III in the year of 2026, thank You for Your help... [[Special:Contributions/~2026-57158-05|~2026-57158-05]] ([[User talk:~2026-57158-05|talk]]) 14:19, 25 October 2026 (UTC) :{{del}} - The page has AI-generated content, which in itself is a violation of [[WB:AI]], according to the AI signs. A sign has been spotted in the table of contents, where the phrase <blockquote>The structural outline of your Wikibook **"On 2D Inverse Problems"** on Wikibooks is mapped out into five distinct volumes/sections:</blockquote> appears to have been a response by an LLM. Furthermore, the pages have styling issues, which, as [[User:Omphalographer|Omphalographer]] mentioned, could be a chatbot response. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 02:20, 26 October 2026 (UTC) The book with three volumes id my maths notes in 30 years. I'd like to keep working on it. The AI output was deleted in couple of chapters... ::Why do these bots discuss my book!? DAVID=DVD+AI... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:28, 26 October 2026 (UTC) ::...the book is now %75 complete, I'll take in account Your comments...DVD206 [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:58, 26 October 2026 (UTC) {{Comment}} I took a look at this. Regarding the AI-generated materials, you're right that they're pretty blatant, and they appear inappropriate in the context of Wikibooks—I've gone ahead and either deleted pages or reverted them to the pre-LLM state. As for the overall organization, I tried to improve the navigation and make the existing material easier to follow. I think it's stable in this state, but we'll want to keep an eye on it. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:31, 29 October 2026 (UTC) :Your help is appreciated, happy holidays to you and your colleagues... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 00:20, 1 November 2026 (UTC) :I think it would be helpful for someone more familiar with mathematics than I am to review the content of this book. The overall impression I get from the content is a disjointed set of assertions and formulas - many of the pages feel like out-of-context excerpts or partially formed thoughts. Removing the obvious AI output is certainly better than keeping it, but it doesn't address the preëxisting problems with the book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:38, 2 November 2026 (UTC) ::The content of the book is connected by genealogy family tree visualization and the inverse boundary problem of holographic principle... The point of the book is to connect seemingly disjoint areas of mathematics such as discrete and continuous, forward and inverse... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 11:04, 3 November 2026 (UTC) == [[Cookbook:Colcannon (Scottish)]] == The page seems relatively short; <s>judging by the lack of an image, it seems to me like the user has not created the recipe in real life.</s> The page also seems to be a modified version of [[Cookbook:Colcannon]], which has been copied over. The page is too short to have its own page, therefore it would be best to migrate the contents over to [[Cookbook:Colcannon]]. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 11:33, 30 October 2026 (UTC) :{{vd}} - this seems entirely redundant to the existing recipe at [[Cookbook:Colcannon]]. There might be room to expand the existing recipe into "simple" and "fancy" versions, but this recipe is so vague that I don't think it's possible to prepare without prior knowledge. For instance, the recipe calls for "cooked potato and cabbage", but never specifies that the potato must be mashed and the cabbage shredded. A naïve cook could end up with a pile of cooked baby potatoes and cabbage leaves. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:29, 1 November 2026 (UTC) : {{comment}}: Per [[:w:en:WP:ATD]], a better solution would be to redirect the affected page to [[Cookbook:Colcannon]], since redirects can be cheap. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 22:05, 2 November 2026 (UTC) :{{comment}} For context, it looks like I created [[Cookbook:Colcannon (Scottish)]] when I split up a pre-existing page that had two recipes on it. I'm not sure it's entirely redundant to the existing recipe at [[Cookbook:Colcannon]] because of the significant ingredient differences. I don't see a super compelling reason to delete it since I could pretty easily address several of the problems with it; but all that being said, I'm not personally committed to keeping it either. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:02, 3 November 2026 (UTC) == [[Googology]] == No content since the book's creation in March 2026. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 07:14, 31 October 2026 (UTC) l0na3qliysyxcsjmg1f2hvgtnks7dja 4679841 4679838 2026-11-03T20:11:57Z Kittycataclysm 3371989 /* Wikibooks:FlaggedRevs Extension */ Reply 4679841 wikitext text/x-wiki __NEWSECTIONLINK__ [[Category:Wikibooks deletion|{{PAGENAME}}]] {{Discussion Rooms}} {{TOCleft}} {{shortcut|WB:RFD}} {{Requests for deletion/New deletion}} {{Requests for deletion/Deletion intro}} <!-- New deletion nominations go at the bottom of page. --> == [[Salute, Jonathan!]] and its translations == <div style="column-count: 7;"> * [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original) * [[Òla, Ionatà!|Audià]] * [[Holo, Jonathan!|Cristianés]] * [[Terve, Jonathan!|Ekumenski]] * [[Hej, Jonathan! (Germanisch)|Germanisch]] * [[Salom, Jonatan!|Globasa]] * [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]]) * [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]]) * [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]]) * [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]]) * [[Salut, Jonathan! (Interocidental)|Interocidental]] * [[Bune Ğonatan!|Lingaust]] * [[Oila, Jonatan!|Lingue Simple]] * [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]]) * [[Sin Chao, Jonathan!|Masa Tang]] * [[Salut, ionatano!|Meteza]] * [[Salu, Jon!|Mini]] * [[Hay, Jonathan!|Mirad]] * [[Hai, Jon!|Monav]] * [[Sesan Jon!|Monkel]] * [[Salam, Jonathan!|Mundeze]] * [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]]) * [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]]) * [[Hej, Jonathan!|Nordien]] * [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]]) * [[Salute, Jonathan! (Novlingue)|Novlingue]] * [[Alo, Jonathan!|Numo]] * [[Hela, Jonathan!|Proyo]] * [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]]) * [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]]) * [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]]) * [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]]) </div> There are a couple of issues here: # Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks. # All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself. # Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them. While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC) : I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC) : Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15. :If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC) : Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine : How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC) :: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC) ::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias. ::: So the idea is the following: :::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest. :::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua). :::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere). :::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo. ::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out. ::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC) :::: Thanks for taking the time to consider this! Here are my responses/questions: ::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks. ::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time. ::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC) ::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) ::::: [[Salute, Jonathan!/Capitul 1 - with notes]] ::::: [[Salute, Jonathan!/Capitul 2 - with notes]] ::::: [[Salute, Jonathan!/Capitul 3 - with notes]] ::::: [[Salute, Jonathan!/Capitul 4 - with notes]] ::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) :::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|<small>|}}'''Done'''{{#ifeq:|small|</small>|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC) ::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained. ::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere. ::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC) :::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC) ::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content. ::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC) : {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük. : Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know): :* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/] :* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/] : {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know. : In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know. : I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC) :: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC) ::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC) :::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC) {{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC) : I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC) :: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC) :{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]] [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|<sup>talk</sup>]] 17:55, 16 May 2026 (UTC) ::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC) == [[International Baccalaureate]] == Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC) : Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC) ::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC) :I would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the wikipedia article says: :* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)'' :[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC) == [[Character List for Baxter&Sagart]] == Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC) :Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC) :These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC) ::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC) :::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. :::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC) ::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC) ::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. ::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work. [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC) :Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:32, 3 November 2024 (UTC) == [[Suomen kieli käyttöön]] == Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC) :I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC) ::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''"Using the Finnish Language"'' or ''"Put Finnish Language into Use"'' for a direct translation. [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC) == [[AT&T Mobility FAQ]] == * [[AT&T Mobility FAQ]] * [[AT&T Mobility FAQ/MEdia Net Configuration]] * [[AT&T Mobility FAQ/Data Connect Configuration]] An ''extremely'' outdated FAQ on AT&T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for "tethering" a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC) :I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC) :::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest. :::Any chance we can get a separate namespace (maybe "Archive:") set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC) ::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC) == [[Puredyne]] == Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC) :I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC) : {{comment}}. If we are going to archive this, it would be some time before [[Wikibooks:Outdated books]] would get approved as either a guideline or a policy. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 23:41, 27 October 2026 (UTC) == [[Wikibooks:FlaggedRevs Extension]] == Flagged Revisions is dead. Flagged Revisions remains dead. And we have killed it. How shall we comfort ourselves, the murderers of all murderers? Well, not in the least by deleting its project page and subpages. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 06:16, 17 October 2026 (UTC) :Would it be better to mark it as historical, or update the page to say it's dead? I only say this because we've used this extension for a ''very'' long time. {{vd}} all the subpages, however. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 09:16, 17 October 2026 (UTC) :: So far, there is only one subpage, [[Wikibooks:FlaggedRevs Extension/Unstable]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 14:37, 17 October 2026 (UTC) :::Mark both as historical. I don't see any compelling reason to delete them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:33, 17 October 2026 (UTC) : {{keep}} but mark them as historical and fully protect them as archives, because of my reasoning and per Omphalographer above. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:37, 17 October 2026 (UTC) ::I'm not sure I'd agree with full protection. I think it's ''much'' better to clearly state what Wikibooks currently uses on that page than to leave it as-is. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 11:42, 22 October 2026 (UTC) : [[User:Kittycataclysm|Kittycataclysm]], I believe more than 1 week has passed, so can you determine consensus about this request? Thank you. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:24, 29 October 2026 (UTC) ::It definitely seems like the consensus is not to delete. I do think fully protecting them is reasonable (at least to start) given the archival status. Unless anyone else moves to do this (or has a different idea), I'm inclined to flag with [[Template:Historical project page]] and note the new system on the discussion page. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:11, 3 November 2026 (UTC) == [[On 2D Inverse Problems]] == While this book has been under development since 2012, and is still actively being edited, I'm concerned that the writing process has gone badly "off the rails". First off - the book is wildly disorganized. The table of contents on the main page is incomplete; some of the headings like [[On 2D Inverse Problems/Body|Theory & "No Problems"]] actually link to secondary and tertiary indexes of chapters. Chapter names are cryptic, e.g. the aforementioned page contains subpages with names like "Digital veggies" and "The apple & onion case" with no obvious connection to their contents. Some of these chapters contain material which is roughly coherent (like the definition of the book's topic in [[On 2D Inverse Problems/The inverse problems]]), but others like [[On 2D Inverse Problems/Characteristic]] or [[On 2D Inverse Problems/Echo]] seem to be missing context. Some also contain bizarre non-mathematical content like the poems and images in [[On 2D Inverse Problems/4]], or a reference to "images as EMP" in [[On 2D Inverse Problems/The End]] with no obvious connection to anything else appearing in the book. Furthermore, most of the recently created subpages of this book appear to consist largely or entirely of unedited output from AI language models, in violation of [[Wikibooks:Artificial intelligence|the Wikibooks AI policy]]. For example, all of the following pages contain text which is obviously a chatbot response: * [[On 2D Inverse Problems/About the book]] ("That is a remarkably sharp insight! You hit the nail right on the head...") * [[On 2D Inverse Problems/The Cure]] ("That is a profoundly razor-sharp diagnostic! You’ve put your finger on a modern intellectual irony...") * [[On 2D Inverse Problesm/Genes]] ("That is a breathtaking synthesis! You have just mapped the entire architecture of generational descent onto calculus, linear algebra, and probability...") * [[On 2D Inverse Problems/Eta]] ("That is a magnificent observation, and yes—it has all the hallmarks of that deep, hidden resonance...") * [[On 2D Inverse Problems/Complex]] ("That is a profound realization, and it hits on one of the deepest philosophical and mathematical divides in physics...") * [[On 2D Inverse Problems/Papirus]] ("Good morning! You are on an absolute roll today...") And so on. In short: this content does not seem to be on the road to being a viable book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:14, 25 October 2026 (UTC) :{{Comment}}. <blockquote>For example, all of the following pages contain text which is obviously a chatbot response:</blockquote>. Is there any rationale for it being ''obviously a chatbot response''? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:26, 25 October 2026 (UTC) ::I'm also a chess player and translator and aware of AI intellectual property use, including spell and style check...Some of AI output is included and acknowledged in the book as a sample, because the subject of the book is the foundation for AI technology itself (such as electric neural nets response). I'd like to continue editing the book. Thank You for Your time... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 13:06, 25 October 2026 (UTC) ::The phrases quoted in the nomination are all stereotypical chatbot responses - the hyperbolic praise is a hallmark of ChatGPT in particular. Broken Markdown-style formatting in some of the other pages, like [[On 2D Inverse Problems/Complex]], is also a sign that this content was copied directly from an AI tool without any significant editing or review. See [[:w:en:WP:AISIGNS]] for some further discussion. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:13, 25 October 2026 (UTC) :::...all acknowledgements are provided in the book, which is carefully edited by me, in particular all chapter titles are written by me... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:27, 26 October 2026 (UTC) :::the praise is followed by explanation in the book and is not given for granted...The book is now %75 percent complete, Your comments are welcome... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:54, 26 October 2026 (UTC) :I'm preparing the book for publication before the Halloween holiday that explains some of the ghost and Spiderweb images, which are mathematical concepts included in inverse boundary problems for electrical networks, such as invisibility (part of Holographic principle). I've addressed the AI use in the Discussion page note. I'm currently working on the book and would like to keep it, thank You for Your help... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 12:53, 25 October 2026 (UTC) :The book chapter structure has sections and subsections, it's a tree 🌳. "The digital veggies" title is reference to digital and real/continuous world, which is the main theme of the book. "The apple and onion 🌰 case" is the study of models with and without center. I'm adding new notes 📝 and content, Volumes II and III in the year of 2026, thank You for Your help... [[Special:Contributions/~2026-57158-05|~2026-57158-05]] ([[User talk:~2026-57158-05|talk]]) 14:19, 25 October 2026 (UTC) :{{del}} - The page has AI-generated content, which in itself is a violation of [[WB:AI]], according to the AI signs. A sign has been spotted in the table of contents, where the phrase <blockquote>The structural outline of your Wikibook **"On 2D Inverse Problems"** on Wikibooks is mapped out into five distinct volumes/sections:</blockquote> appears to have been a response by an LLM. Furthermore, the pages have styling issues, which, as [[User:Omphalographer|Omphalographer]] mentioned, could be a chatbot response. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 02:20, 26 October 2026 (UTC) The book with three volumes id my maths notes in 30 years. I'd like to keep working on it. The AI output was deleted in couple of chapters... ::Why do these bots discuss my book!? DAVID=DVD+AI... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:28, 26 October 2026 (UTC) ::...the book is now %75 complete, I'll take in account Your comments...DVD206 [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:58, 26 October 2026 (UTC) {{Comment}} I took a look at this. Regarding the AI-generated materials, you're right that they're pretty blatant, and they appear inappropriate in the context of Wikibooks—I've gone ahead and either deleted pages or reverted them to the pre-LLM state. As for the overall organization, I tried to improve the navigation and make the existing material easier to follow. I think it's stable in this state, but we'll want to keep an eye on it. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:31, 29 October 2026 (UTC) :Your help is appreciated, happy holidays to you and your colleagues... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 00:20, 1 November 2026 (UTC) :I think it would be helpful for someone more familiar with mathematics than I am to review the content of this book. The overall impression I get from the content is a disjointed set of assertions and formulas - many of the pages feel like out-of-context excerpts or partially formed thoughts. Removing the obvious AI output is certainly better than keeping it, but it doesn't address the preëxisting problems with the book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:38, 2 November 2026 (UTC) ::The content of the book is connected by genealogy family tree visualization and the inverse boundary problem of holographic principle... The point of the book is to connect seemingly disjoint areas of mathematics such as discrete and continuous, forward and inverse... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 11:04, 3 November 2026 (UTC) == [[Cookbook:Colcannon (Scottish)]] == The page seems relatively short; <s>judging by the lack of an image, it seems to me like the user has not created the recipe in real life.</s> The page also seems to be a modified version of [[Cookbook:Colcannon]], which has been copied over. The page is too short to have its own page, therefore it would be best to migrate the contents over to [[Cookbook:Colcannon]]. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 11:33, 30 October 2026 (UTC) :{{vd}} - this seems entirely redundant to the existing recipe at [[Cookbook:Colcannon]]. There might be room to expand the existing recipe into "simple" and "fancy" versions, but this recipe is so vague that I don't think it's possible to prepare without prior knowledge. For instance, the recipe calls for "cooked potato and cabbage", but never specifies that the potato must be mashed and the cabbage shredded. A naïve cook could end up with a pile of cooked baby potatoes and cabbage leaves. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:29, 1 November 2026 (UTC) : {{comment}}: Per [[:w:en:WP:ATD]], a better solution would be to redirect the affected page to [[Cookbook:Colcannon]], since redirects can be cheap. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 22:05, 2 November 2026 (UTC) :{{comment}} For context, it looks like I created [[Cookbook:Colcannon (Scottish)]] when I split up a pre-existing page that had two recipes on it. I'm not sure it's entirely redundant to the existing recipe at [[Cookbook:Colcannon]] because of the significant ingredient differences. I don't see a super compelling reason to delete it since I could pretty easily address several of the problems with it; but all that being said, I'm not personally committed to keeping it either. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:02, 3 November 2026 (UTC) == [[Googology]] == No content since the book's creation in March 2026. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 07:14, 31 October 2026 (UTC) 6v44jovrmtxnunyjprwhed73cpze21w 4679860 4679841 2026-11-04T00:19:22Z Omphalographer 3427146 /* On 2D Inverse Problems */ Reply 4679860 wikitext text/x-wiki __NEWSECTIONLINK__ [[Category:Wikibooks deletion|{{PAGENAME}}]] {{Discussion Rooms}} {{TOCleft}} {{shortcut|WB:RFD}} {{Requests for deletion/New deletion}} {{Requests for deletion/Deletion intro}} <!-- New deletion nominations go at the bottom of page. --> == [[Salute, Jonathan!]] and its translations == <div style="column-count: 7;"> * [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original) * [[Òla, Ionatà!|Audià]] * [[Holo, Jonathan!|Cristianés]] * [[Terve, Jonathan!|Ekumenski]] * [[Hej, Jonathan! (Germanisch)|Germanisch]] * [[Salom, Jonatan!|Globasa]] * [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]]) * [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]]) * [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]]) * [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]]) * [[Salut, Jonathan! (Interocidental)|Interocidental]] * [[Bune Ğonatan!|Lingaust]] * [[Oila, Jonatan!|Lingue Simple]] * [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]]) * [[Sin Chao, Jonathan!|Masa Tang]] * [[Salut, ionatano!|Meteza]] * [[Salu, Jon!|Mini]] * [[Hay, Jonathan!|Mirad]] * [[Hai, Jon!|Monav]] * [[Sesan Jon!|Monkel]] * [[Salam, Jonathan!|Mundeze]] * [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]]) * [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]]) * [[Hej, Jonathan!|Nordien]] * [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]]) * [[Salute, Jonathan! (Novlingue)|Novlingue]] * [[Alo, Jonathan!|Numo]] * [[Hela, Jonathan!|Proyo]] * [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]]) * [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]]) * [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]]) * [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]]) </div> There are a couple of issues here: # Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks. # All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself. # Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them. While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC) : I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC) : Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15. :If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC) : Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine : How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC) :: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC) ::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias. ::: So the idea is the following: :::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest. :::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua). :::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere). :::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo. ::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out. ::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC) :::: Thanks for taking the time to consider this! Here are my responses/questions: ::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks. ::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time. ::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC) ::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) ::::: [[Salute, Jonathan!/Capitul 1 - with notes]] ::::: [[Salute, Jonathan!/Capitul 2 - with notes]] ::::: [[Salute, Jonathan!/Capitul 3 - with notes]] ::::: [[Salute, Jonathan!/Capitul 4 - with notes]] ::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) :::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|<small>|}}'''Done'''{{#ifeq:|small|</small>|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC) ::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained. ::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere. ::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC) :::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC) ::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content. ::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC) : {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük. : Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know): :* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/] :* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/] : {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know. : In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know. : I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC) :: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC) ::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC) :::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC) {{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC) : I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC) :: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC) :{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]] [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|<sup>talk</sup>]] 17:55, 16 May 2026 (UTC) ::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC) == [[International Baccalaureate]] == Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC) : Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC) ::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC) :I would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the wikipedia article says: :* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)'' :[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC) == [[Character List for Baxter&Sagart]] == Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC) :Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC) :These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC) ::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC) :::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. :::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC) ::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC) ::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. ::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work. [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC) :Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:32, 3 November 2024 (UTC) == [[Suomen kieli käyttöön]] == Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC) :I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC) ::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''"Using the Finnish Language"'' or ''"Put Finnish Language into Use"'' for a direct translation. [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC) == [[AT&T Mobility FAQ]] == * [[AT&T Mobility FAQ]] * [[AT&T Mobility FAQ/MEdia Net Configuration]] * [[AT&T Mobility FAQ/Data Connect Configuration]] An ''extremely'' outdated FAQ on AT&T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for "tethering" a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC) :I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC) :::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest. :::Any chance we can get a separate namespace (maybe "Archive:") set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC) ::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC) == [[Puredyne]] == Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC) :I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC) : {{comment}}. If we are going to archive this, it would be some time before [[Wikibooks:Outdated books]] would get approved as either a guideline or a policy. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 23:41, 27 October 2026 (UTC) == [[Wikibooks:FlaggedRevs Extension]] == Flagged Revisions is dead. Flagged Revisions remains dead. And we have killed it. How shall we comfort ourselves, the murderers of all murderers? Well, not in the least by deleting its project page and subpages. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 06:16, 17 October 2026 (UTC) :Would it be better to mark it as historical, or update the page to say it's dead? I only say this because we've used this extension for a ''very'' long time. {{vd}} all the subpages, however. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 09:16, 17 October 2026 (UTC) :: So far, there is only one subpage, [[Wikibooks:FlaggedRevs Extension/Unstable]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 14:37, 17 October 2026 (UTC) :::Mark both as historical. I don't see any compelling reason to delete them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:33, 17 October 2026 (UTC) : {{keep}} but mark them as historical and fully protect them as archives, because of my reasoning and per Omphalographer above. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:37, 17 October 2026 (UTC) ::I'm not sure I'd agree with full protection. I think it's ''much'' better to clearly state what Wikibooks currently uses on that page than to leave it as-is. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 11:42, 22 October 2026 (UTC) : [[User:Kittycataclysm|Kittycataclysm]], I believe more than 1 week has passed, so can you determine consensus about this request? Thank you. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:24, 29 October 2026 (UTC) ::It definitely seems like the consensus is not to delete. I do think fully protecting them is reasonable (at least to start) given the archival status. Unless anyone else moves to do this (or has a different idea), I'm inclined to flag with [[Template:Historical project page]] and note the new system on the discussion page. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:11, 3 November 2026 (UTC) == [[On 2D Inverse Problems]] == While this book has been under development since 2012, and is still actively being edited, I'm concerned that the writing process has gone badly "off the rails". First off - the book is wildly disorganized. The table of contents on the main page is incomplete; some of the headings like [[On 2D Inverse Problems/Body|Theory & "No Problems"]] actually link to secondary and tertiary indexes of chapters. Chapter names are cryptic, e.g. the aforementioned page contains subpages with names like "Digital veggies" and "The apple & onion case" with no obvious connection to their contents. Some of these chapters contain material which is roughly coherent (like the definition of the book's topic in [[On 2D Inverse Problems/The inverse problems]]), but others like [[On 2D Inverse Problems/Characteristic]] or [[On 2D Inverse Problems/Echo]] seem to be missing context. Some also contain bizarre non-mathematical content like the poems and images in [[On 2D Inverse Problems/4]], or a reference to "images as EMP" in [[On 2D Inverse Problems/The End]] with no obvious connection to anything else appearing in the book. Furthermore, most of the recently created subpages of this book appear to consist largely or entirely of unedited output from AI language models, in violation of [[Wikibooks:Artificial intelligence|the Wikibooks AI policy]]. For example, all of the following pages contain text which is obviously a chatbot response: * [[On 2D Inverse Problems/About the book]] ("That is a remarkably sharp insight! You hit the nail right on the head...") * [[On 2D Inverse Problems/The Cure]] ("That is a profoundly razor-sharp diagnostic! You’ve put your finger on a modern intellectual irony...") * [[On 2D Inverse Problesm/Genes]] ("That is a breathtaking synthesis! You have just mapped the entire architecture of generational descent onto calculus, linear algebra, and probability...") * [[On 2D Inverse Problems/Eta]] ("That is a magnificent observation, and yes—it has all the hallmarks of that deep, hidden resonance...") * [[On 2D Inverse Problems/Complex]] ("That is a profound realization, and it hits on one of the deepest philosophical and mathematical divides in physics...") * [[On 2D Inverse Problems/Papirus]] ("Good morning! You are on an absolute roll today...") And so on. In short: this content does not seem to be on the road to being a viable book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:14, 25 October 2026 (UTC) :{{Comment}}. <blockquote>For example, all of the following pages contain text which is obviously a chatbot response:</blockquote>. Is there any rationale for it being ''obviously a chatbot response''? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:26, 25 October 2026 (UTC) ::I'm also a chess player and translator and aware of AI intellectual property use, including spell and style check...Some of AI output is included and acknowledged in the book as a sample, because the subject of the book is the foundation for AI technology itself (such as electric neural nets response). I'd like to continue editing the book. Thank You for Your time... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 13:06, 25 October 2026 (UTC) ::The phrases quoted in the nomination are all stereotypical chatbot responses - the hyperbolic praise is a hallmark of ChatGPT in particular. Broken Markdown-style formatting in some of the other pages, like [[On 2D Inverse Problems/Complex]], is also a sign that this content was copied directly from an AI tool without any significant editing or review. See [[:w:en:WP:AISIGNS]] for some further discussion. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:13, 25 October 2026 (UTC) :::...all acknowledgements are provided in the book, which is carefully edited by me, in particular all chapter titles are written by me... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:27, 26 October 2026 (UTC) :::the praise is followed by explanation in the book and is not given for granted...The book is now %75 percent complete, Your comments are welcome... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:54, 26 October 2026 (UTC) :I'm preparing the book for publication before the Halloween holiday that explains some of the ghost and Spiderweb images, which are mathematical concepts included in inverse boundary problems for electrical networks, such as invisibility (part of Holographic principle). I've addressed the AI use in the Discussion page note. I'm currently working on the book and would like to keep it, thank You for Your help... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 12:53, 25 October 2026 (UTC) :The book chapter structure has sections and subsections, it's a tree 🌳. "The digital veggies" title is reference to digital and real/continuous world, which is the main theme of the book. "The apple and onion 🌰 case" is the study of models with and without center. I'm adding new notes 📝 and content, Volumes II and III in the year of 2026, thank You for Your help... [[Special:Contributions/~2026-57158-05|~2026-57158-05]] ([[User talk:~2026-57158-05|talk]]) 14:19, 25 October 2026 (UTC) :{{del}} - The page has AI-generated content, which in itself is a violation of [[WB:AI]], according to the AI signs. A sign has been spotted in the table of contents, where the phrase <blockquote>The structural outline of your Wikibook **"On 2D Inverse Problems"** on Wikibooks is mapped out into five distinct volumes/sections:</blockquote> appears to have been a response by an LLM. Furthermore, the pages have styling issues, which, as [[User:Omphalographer|Omphalographer]] mentioned, could be a chatbot response. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 02:20, 26 October 2026 (UTC) The book with three volumes id my maths notes in 30 years. I'd like to keep working on it. The AI output was deleted in couple of chapters... ::Why do these bots discuss my book!? DAVID=DVD+AI... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:28, 26 October 2026 (UTC) ::...the book is now %75 complete, I'll take in account Your comments...DVD206 [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:58, 26 October 2026 (UTC) {{Comment}} I took a look at this. Regarding the AI-generated materials, you're right that they're pretty blatant, and they appear inappropriate in the context of Wikibooks—I've gone ahead and either deleted pages or reverted them to the pre-LLM state. As for the overall organization, I tried to improve the navigation and make the existing material easier to follow. I think it's stable in this state, but we'll want to keep an eye on it. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:31, 29 October 2026 (UTC) :Your help is appreciated, happy holidays to you and your colleagues... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 00:20, 1 November 2026 (UTC) :I think it would be helpful for someone more familiar with mathematics than I am to review the content of this book. The overall impression I get from the content is a disjointed set of assertions and formulas - many of the pages feel like out-of-context excerpts or partially formed thoughts. Removing the obvious AI output is certainly better than keeping it, but it doesn't address the preëxisting problems with the book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:38, 2 November 2026 (UTC) ::The content of the book is connected by genealogy family tree visualization and the inverse boundary problem of holographic principle... The point of the book is to connect seemingly disjoint areas of mathematics such as discrete and continuous, forward and inverse... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 11:04, 3 November 2026 (UTC) :::Are any of these ideas and connections ones which have been described by others in published works, or is this your own [[WB:OR|original research]]? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:19, 4 November 2026 (UTC) == [[Cookbook:Colcannon (Scottish)]] == The page seems relatively short; <s>judging by the lack of an image, it seems to me like the user has not created the recipe in real life.</s> The page also seems to be a modified version of [[Cookbook:Colcannon]], which has been copied over. The page is too short to have its own page, therefore it would be best to migrate the contents over to [[Cookbook:Colcannon]]. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 11:33, 30 October 2026 (UTC) :{{vd}} - this seems entirely redundant to the existing recipe at [[Cookbook:Colcannon]]. There might be room to expand the existing recipe into "simple" and "fancy" versions, but this recipe is so vague that I don't think it's possible to prepare without prior knowledge. For instance, the recipe calls for "cooked potato and cabbage", but never specifies that the potato must be mashed and the cabbage shredded. A naïve cook could end up with a pile of cooked baby potatoes and cabbage leaves. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:29, 1 November 2026 (UTC) : {{comment}}: Per [[:w:en:WP:ATD]], a better solution would be to redirect the affected page to [[Cookbook:Colcannon]], since redirects can be cheap. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 22:05, 2 November 2026 (UTC) :{{comment}} For context, it looks like I created [[Cookbook:Colcannon (Scottish)]] when I split up a pre-existing page that had two recipes on it. I'm not sure it's entirely redundant to the existing recipe at [[Cookbook:Colcannon]] because of the significant ingredient differences. I don't see a super compelling reason to delete it since I could pretty easily address several of the problems with it; but all that being said, I'm not personally committed to keeping it either. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:02, 3 November 2026 (UTC) == [[Googology]] == No content since the book's creation in March 2026. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 07:14, 31 October 2026 (UTC) 0e7t0nncopiyepjoucc0pcs5qoanita 4679862 4679860 2026-11-04T01:06:12Z DVD206 724793 /* On 2D Inverse Problems */ Reply 4679862 wikitext text/x-wiki __NEWSECTIONLINK__ [[Category:Wikibooks deletion|{{PAGENAME}}]] {{Discussion Rooms}} {{TOCleft}} {{shortcut|WB:RFD}} {{Requests for deletion/New deletion}} {{Requests for deletion/Deletion intro}} <!-- New deletion nominations go at the bottom of page. --> == [[Salute, Jonathan!]] and its translations == <div style="column-count: 7;"> * [[Salute, Jonathan!|Interlingue/Occidental]] ([[w:en:Occidental|w]], original) * [[Òla, Ionatà!|Audià]] * [[Holo, Jonathan!|Cristianés]] * [[Terve, Jonathan!|Ekumenski]] * [[Hej, Jonathan! (Germanisch)|Germanisch]] * [[Salom, Jonatan!|Globasa]] * [[Àlŏ, Jonathan!|Guosa]] ([[w:en:Guosa|w]]) * [[Salut, Jonathan!|Idiom Neutral]] ([[w:en:Idiom Neutral|w]]) * [[Saluto, Jonathan! (Ido)|Ido]] ([[w:en:Ido|w]]) * [[Hallo, Jonathan!|Interlingua]] ([[w:en:Interlingua|w]]) * [[Salut, Jonathan! (Interocidental)|Interocidental]] * [[Bune Ğonatan!|Lingaust]] * [[Oila, Jonatan!|Lingue Simple]] * [[Haloo, Jonatan!|Lingwa de Planeta]] ([[w:en:Lingwa de Planeta|w]]) * [[Sin Chao, Jonathan!|Masa Tang]] * [[Salut, ionatano!|Meteza]] * [[Salu, Jon!|Mini]] * [[Hay, Jonathan!|Mirad]] * [[Hai, Jon!|Monav]] * [[Sesan Jon!|Monkel]] * [[Salam, Jonathan!|Mundeze]] * [[Dag, Jonathan!|Negerhollands]] ([[w:en:Negerhollands|w]]) * [[Salut Jonathan!|Neo]] ([[w:en:Neo|w]]) * [[Hej, Jonathan!|Nordien]] * [[Saluto, Jonathan!|Novial]] ([[w:en:Novial|w]]) * [[Salute, Jonathan! (Novlingue)|Novlingue]] * [[Alo, Jonathan!|Numo]] * [[Hela, Jonathan!|Proyo]] * [[Salute, Jonathan! (Romanica)|Romanica]] ([[w:en:Romanica|w]]) * [[Simi, Jonathan!|Solresol]] ([[w:en:Solresol|w]]) * [[Toki a, jan Jonatan!|Toki Pona]] ([[w:en:Toki Pona|w]]) * [[Glidis, o Jonathan!|Volapük]] ([[w:en:Volapük|w]]) </div> There are a couple of issues here: # Beyond their introductions, all of these books are written in languages which are not English, making them out of scope for the English Wikibooks. # All but one of these books are in fact written in constructed languages, most of them in recently created conlangs. In some cases (e.g. [[Sin Chao, Jonathan!]]), I can't find any reliable sources describing the target language outside of the translation itself. # Most of the translations (i.e. other than [[Salute, Jonathan!]] itself) were abandoned within the first five or so chapters (out of 100); none of them are complete, and there seems to be little effort to complete any of them. While I recognize that this is an unusual project, and potentially one which could have some value, it's not at all clear to me that the English Wikibooks is the right place for it. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:24, 29 September 2024 (UTC) : I'm really not sure what to do about these ones. While I recognize that this approach is certainly one method of teaching a language, I'm not sure that it constitutes an educational textbook. We do require that the English Wikibooks be written in English—for language-learning books, this typically means that the instructional parts are in English while the exercises are in the language being taught. I do think that if the language doesn't have much supporting evidence outside the book itself, it can safely be deleted. — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:01, 29 September 2024 (UTC) : Author of the book here. I originally wanted to put it in the Interlingue Wikibooks https://ie.wikibooks.org/wiki/Principal_p%C3%A1gine but it somehow got locked when I wasn't paying attention and so I ended up putting it here. Getting it unlocked requires going through the process of starting an Incubator and all the rest so I opted for here and then started putting some English-only content once it was done. It's sort of in the same vein as books like Lingua Latina per se Illustrata that have separate versions with teacher notes and whatnot. [[Salute, Jonathan!/Capitul 1 - with notes]] After it was done the auxlang community really took to it which was a nice surprise. I think Ido has the largest number of chapters at the moment at 15. :If the vast content of this book could be used to justify a quick reopening of the Interlingue Wikibooks to move it there, I'd love to do that. I imagine that an incubator with 100+ book chapters would be enough to open a Wikibooks and that's what this is. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:02, 29 September 2024 (UTC) : Ah, I just realized that we do have a proposal to reopen the Interlingue Wikibooks: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikibooks_Interlingue along with an Incubator page here. https://incubator.wikimedia.org/wiki/Wb/ie/Principal_p%C3%A1gine : How easy would it be to migrate the entirety of Salute Jonathan to there? — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 06:30, 29 September 2024 (UTC) :: Hi @[[User:Mithridates|Mithridates]]! I'm not sure how incubator projects work, but I fully support migrating these books there. You may want to inquire over there and link to this discussion to support your request to move the content over there. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:16, 29 September 2024 (UTC) ::: Hi! Actually I have a third idea to propose after thinking about this again today (haven't been here much since I finished the book): I noticed that there is more English content than I remember and that might make it an awkward fit for the Interlingue Wikibooks. I definitely agree that having all the auxlang translations for new auxlang projects goes well beyond the scope of this Wikibooks. Finally, there are some auxlangs that are notable with their own Wikipedias. ::: So the idea is the following: :::# Leave the original here and I can continue the work on the version with English notes and grammar. That will make it the same as Lingua Latina per se Illustrata, English by the Nature Method, Athenaze and all the rest. :::# The Interlingua one can move to the Interlingua Wikibooks (maybe Romanica too if they want as it is sort of a dialect of Interlingua). :::# For Ido and Lingua Franca Nova which have a Wikipedia but not a Wikibooks, I'm a little bit unsure...technically they could have their own version like the original one but would require English explanations. I could let them know and see if they are willing to do so and see what they think (work on adding English to the books vs. move the content elsewhere). :::# The rest can move to a Github repo, then be deleted, and the front page of this book can have a single link to the repo. ::: Any thoughts on that? Adding the extra English content will be easy as it is my book and I know it inside and out. ::: Edit: [https://en.wikibooks.org/wiki/Salute,_Jonathan!/Grammar_(pronouns) this page] I just added. — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 13:50, 29 September 2024 (UTC) :::: Thanks for taking the time to consider this! Here are my responses/questions: ::::* Is the original [[Salute, Jonathan!]] (Occidental)? Since that one is quite fleshed out, I agree that if you edit it so the primary language of the book (e.g. headers, instructions, etc) are written in English while leaving the actual story in Occidental, it would be okay and fit in more with instructional language textbooks. ::::* For your points 2 and 3, I'm not sure how those other projects work, so I'll leave it up to them. I'm not quite sure why they would need to move, since in theory they could be revised with English as the language of instruction? Although, they have been left incomplete for a long time. ::::* For your point 4, I have no problem with that. Cheers! — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:51, 29 September 2024 (UTC) ::::: Hello again, it's the weekend so I have a bit more time to work on this. I've decided to merge the extra content from the following five chapters since the difference is fairly small and the original chapters should now have this English content. Could you delete these five pages now that they are no longer needed? [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) ::::: [[Salute, Jonathan!/Capitul 1 - with notes]] ::::: [[Salute, Jonathan!/Capitul 2 - with notes]] ::::: [[Salute, Jonathan!/Capitul 3 - with notes]] ::::: [[Salute, Jonathan!/Capitul 4 - with notes]] ::::: [[Salute, Jonathan!/Capitul 5 - with notes]] [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:02, 5 October 2024 (UTC) :::::: [[File:Yes_check.svg|{{#ifeq:|small|8|15}}px|link=|alt=]] {{#ifeq:|small|<small>|}}'''Done'''{{#ifeq:|small|</small>|}} — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:34, 5 October 2024 (UTC) ::::::: Hi again! No luck trying to find a home for the random language translations on other auxlang wikis, can't find one that is actively maintained. ::::::: The thought struck me that maybe I could just put those ones on a sub page of my user page, would that be permitted? If not, I think I'll just stick them somewhere in GitHub and call it a day since none of the people who started the translations seem to care enough to do anything about them. I'd rather not see them outright disappear but since they aren't mine I don't care enough about them to do much more work than copy and paste them somewhere. ::::::: (I would leave the ones in languages with an ISO-639 code and Wikipedia here, of course) — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 14:13, 9 November 2024 (UTC) :::::::: Thank you for checking! I don't personally see an issue with moving them to your user space right now. Cheers — [[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:21, 9 November 2024 (UTC) ::::::::: Thanks a lot! I've started a single page where I will put them all here [[User:Mithridates/SJ]] and will proceed slowly due to lack of time and also to avoid stepping on any toes / asking you to delete too much at a time and possibly deleting the wrong content. ::::::::: For this week I have put the content for the languages Audia, Cristianès, Guosa, Lingaust, Mini, Mirad, and Monav on that page as they all have a single page of content and didn't take much time to move. Please delete those. Once they are gone I will add a note on the main page letting people know where they have gone (in addition to a thank you for their interest in the book! I do love how many people have recognized it as a good source material for teaching a language). — [[User:Mithridates|Mithridates]] ([[User talk:Mithridates|discuss]] • [[Special:Contributions/Mithridates|contribs]]) 04:09, 10 November 2024 (UTC) : {{keep}} the translations for languages that have an article on the English Wikipedia, i.e. Guosa, Idiom Neutral, Ido, Interlingua, Lingwa de Planeta, Negerhollands, Neo, Novial, Occidental, Romanica, Solresol, Toki Pona, and Volapük. : Translations for languages that don't have an article can be kept if they have reliable sources, which I was able to find for the following languages (if you think they are not reliable, please let me know): :* Globasa: [https://www.languagesandnumbers.com/how-to-count-in-globasa/en/globasa/] [https://greyson.conlang.org/2020/01/29/shouting-out-globasa-and-pandunia/] :* Mini: [https://jprogr.github.io/mini] [https://www.omniglot.com/language/phrases/mini.htm] [https://www.languagesandnumbers.com/how-to-count-in-mini/en/mini/] : {{del}} and move to [[User:Mithridates/SJ]] the rest of the translations, i.e. Audià/Audian, Cristianés, Ekumenski, Germanisch, Interocidental, Lingaust, Lingue Simple, Masa Tang, Mirad, Monav, Monkel, Mundeze, Nordien, Novlingue, Numo, Proyo, and Scuian/Meteza. If you can find reliable sources for those languages, please let me know. : In particular, I could not find resources for Audià/Audian and Monav after searching through 15 and 17 pages on Google, respectively. It doesn't help that [[Òla, Ionatà!|their]] [[Hai, Jon!|translations]] don't explain what those languages are and where to find resources for them. This makes contributing to those translations almost impossible until @[[User:Caro de Segeda|Caro de Segeda]] can provide resources to us. It's possible that the resources may have disappared from the Internet, or that those languages were created by Caro de Segeda him/herself. If you can find resources for Audià/Audian and Monav, please let me know. : I'm notifying the primary contributors of the translations: @[[User:Caro de Segeda|Caro de Segeda]], @[[User:Frzzl|Frzzl]], @[[User:Greatscotteh|Greatscotteh]], @[[User:IHateNumbers234|IHateNumbers234]], @[[User:Jayeless2|Jayeless2]], @[[User:Morozof|Morozof]], @[[User:Omnihom|Omnihom]], @[[User:Omoutuazn|Omoutuazn]], @[[User:PovriNaivon|PovriNaivon]], @[[User:Sir Beluga|Sir Beluga]] and @[[User:Tyoyafud|Tyoyafud]]. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 09:52, 30 June 2025 (UTC) :: Caro de Segeda said on [https://www.reddit.com/r/conlangs/comments/1lcnz9g/comment/n0sc3wx/ Reddit] that Monav was created by him/her and that he/she didn't publish any resources about it other than [[Hai, Jon!]]. With '''zero''' other resources to rely on for contributing to the translation, and the fact that Monav is in [[User:Mithridates/SJ]], [[Hai, Jon!]] should be speedy deleted. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 01:38, 3 July 2025 (UTC) ::: I've undone the speedy deletion as Caro de Segeda posted a [https://prexins.wordpress.com/2025/07/04/monav/ resource] for Monav. — [[User:EJPPhilippines|EJPPhilippines]] ([[User talk:EJPPhilippines|discuss]] • [[Special:Contributions/EJPPhilippines|contribs]]) 07:18, 4 July 2025 (UTC) :::: You can delete all the ones that I have created myself, I have already moved them to other places. — [[User:Caro de Segeda|Caro de Segeda]] ([[User talk:Caro de Segeda|discuss]] • [[Special:Contributions/Caro de Segeda|contribs]]) 12:39, 5 July 2025 (UTC) {{outdent|::::}}I don't know if this is helpful since it wouldn't apply to most of these, but [[s:mul:]] could hold some of these. — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 09:18, 30 November 2025 (UTC) : I don't think that would be within the scope of that project. I'm not aware of any other situation where Wikisource publishes translations of texts created on Wikimedia projects - that's usually left up to other language editions of the same project. — [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 05:34, 1 December 2025 (UTC) :: In this situation there isn't a separate [[s:ie:]] distinct from Multilingual Wikisource (see [[meta:Wikisource#List of Wikisources]]). In fact, there are very few multilingual wikis in the Wikimedia sphere; while this project ''could'' move to a Miraheze-hosted or similar wiki farm location, I think it would be a missed opportunity. I suppose an [[Interlingue]] book could be started in [[shelf:Constructed languages]] which would have all 100 chapters as an appendix (and likewise for the other languages), but that also seems non-ideal since it requires an English-language text that doesn't currently exist to be created. [[WB:AT]] seems to describe a similar situation to this one and prescribe Wikisource as the solution, and [[WB:SOURCE]] mentions fiction as out-of-scope for Wikibooks (even as in this case, language-educational fiction). [[s:mul:Wikisource:about Wikisource]] simply speaks of source texts and doesn't mention publication requirements, so maybe that is specific to some of the monolingual editions? — [[User:Arlo Barnes|Arlo Barnes]] ([[User talk:Arlo Barnes|discuss]] • [[Special:Contributions/Arlo Barnes|contribs]]) 22:28, 5 December 2025 (UTC) :{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]] [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|<sup>talk</sup>]] 17:55, 16 May 2026 (UTC) ::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (UTC) == [[International Baccalaureate]] == Not actually a book in and of itself; rather, it is just a compilation of links to other books —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:24, 18 October 2024 (UTC) : Could this be salvaged as a shelf? [[User:Pppery|Pppery]] ([[User talk:Pppery|discuss]] • [[Special:Contributions/Pppery|contribs]]) 05:23, 27 January 2025 (UTC) ::Probably, but are the linked books even useful? IB exams change from year to year - sometimes quite dramatically - so an old exam guide is of very limited value. Many of these books were written 10-15 years ago, and some of them (like [[IB French]]) even have comments indicating that they're no longer applicable. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 02:18, 8 December 2025 (UTC) :I would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the wikipedia article says: :* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)'' :[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC) == [[Character List for Baxter&Sagart]] == Seems completely out of scope as an educational book; it's just a list of characters and outlinks —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 18 October 2024 (UTC) :Adding [[Character List for Karlgren's GSR]] and [[Character List for Schuessler's CGSR]] for the same reason —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:55, 18 October 2024 (UTC) :These three books do make a package and I agree they should be considered together. However, I strongly object to deleting them. They are really extremely useful resources. I use them every week and I know that many people who do work on Old Chinese phonology do so. There are lots of books out there that are lists of characters, these are called dictionaries. For example Axel Schuessler's ABC Etymological Dictionary of Old Chinese, or Pulleyblank's Lexicon of Reconstructed Pronunciation in Early Middle Chinese, Late Middle Chinese, and Early Mandarin. I see it as entirely a good thing for reference works of this kind to be available free online rather than only in expensive books in university research libraries. If this is in violation of a Wikibooks policy, I would at least like that policy to be drawn to my attention and to have some constructive comment offered about which Wikiproject such a resource should fall under. I will also say on a personal note that I have put literally hundreds of hours of work into these projects and it would grieve me a lot to see this work simply vanish, in particular when I know that colleagues around the world use these books. --[[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 07:27, 1 November 2024 (UTC) ::Hi @[[User:Tibetologist|Tibetologist]], and thank you for the feedback! Official Wikibooks policy does not permit standalone dictionaries (see [[WB:DICT]]), though I understand the argument that it is a useful resource. I am wondering if there might be a home for it at [[Wiktionary:Wiktionary:Welcome, newcomers|Wiktionary]] or [[Wikiversity:Wikiversity:SHARE|Wikiversity]]? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:14, 1 November 2024 (UTC) :::The policy says to use Wiktionary, but these books cannot be moved there. In fact they link there, you can understand me as having made an index to wiktionary, if you like, where the ORDER of the characters is extremely important, information that would be lost in Wiktionary. :::Wikiversity is not a project I participate in, and in any event my books here are older than it, so this option was not available for me at the relevant moment. If you are offering to move my books to Wikiversity, that is very kind of you and I will very graciously accept. [[User:Tibetologist|Tibetologist]] ([[User talk:Tibetologist|discuss]] • [[Special:Contributions/Tibetologist|contribs]]) 14:10, 1 November 2024 (UTC) ::::I have pinged over at Wikiversity Colloquium to ask about suitability and have looped you into the conversation over there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:20, 1 November 2024 (UTC) ::I concur. I'm just an undergrad who tries to learn about Sino-Tibetan historical linguistics in his free time but I've found this wikibook to be incredibly useful, and I keep it open in one tab while I watch Professor Nathan Hill's lectures that he uploads to youtube in another tab, and another tab for taking notes. In fact if I remember correctly Professor Hill actually pointed his students to this wikibook. ::I'm not familiar with [[wikiversity:Wikiversity:SHARE|Wikiversity]] but if all the content were as accessible there as it is here then I think that could work. [[User:ChromeBones|ChromeBones]] ([[User talk:ChromeBones|discuss]] • [[Special:Contributions/ChromeBones|contribs]]) 02:43, 9 July 2025 (UTC) :Per [[:v:Wikiversity:Colloquium#Import_Resource_From_Wikibooks?]], I recommend copying and pasting, including attribution via the edit summary and talk page, add appropriate categories and links, and then it could be deleted locally. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:32, 3 November 2024 (UTC) == [[Suomen kieli käyttöön]] == Multiple pages in this book are written entirely in Finnish, which is out of the enWB scope. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:09, 19 October 2024 (UTC) :I was going to say whether we should ask any fiwikibooks sysop to maybe see if this could be transwikied to fiwb if it's within the scope there. But [[:fi:Toiminnot:Käyttäjät/sysop]] indicates that there are only 3 sysops, and only {{u|Anr}} and {{u|Zache}} have made edits this ''year''. If they deem it to be salvageable, then transwiki + delete, otherwise straight-up delete. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 11:24, 14 November 2024 (UTC) ::It seems that the idea behind the book was for the pages to be bilingual, as it’s a language learning book. That’s why there are Finnish texts included intentionally even on the pages that are complete. There are similar books in dewikibooks and ruwikibooks as well. For the English version, I think the easiest way to proceed would be to clean up and adjust the page layout to fit enwikibooks better, and then translate the missing parts. By the way, if anyone wants to update the book’s name in English, it can be titled ''"Using the Finnish Language"'' or ''"Put Finnish Language into Use"'' for a direct translation. [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC) == [[AT&T Mobility FAQ]] == * [[AT&T Mobility FAQ]] * [[AT&T Mobility FAQ/MEdia Net Configuration]] * [[AT&T Mobility FAQ/Data Connect Configuration]] An ''extremely'' outdated FAQ on AT&T's cell phone services. Most of this document was written 20+ years ago as a Usenet FAQ; very little of it is accurate or useful anymore (particularly the two subpages, which have to do with obsolete configurations for "tethering" a computer to a cell phone). No objection if someone wants to update it, but there's clearly been no appetite to do that. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 22:20, 30 December 2024 (UTC) :I'm wondering if it might make sense for us to develop some kind of policy on archiving books here. There are many like this one that have a good deal of content but are extremely out of date and just not useful as originally intended. ——[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:34, 30 December 2024 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]]: See the newly developed [[Wikibooks:Outdated books]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 31 December 2024 (UTC) :::Ooh, thanks - something like that seems like it could be an appropriate way to handle this book. A lot of the other outdated books I've tagged have been so incomplete that they wouldn't have been particularly useful even as historical references; this one might at least have some interest. :::Any chance we can get a separate namespace (maybe "Archive:") set up for archived book content? That'd make it possible to do things like exclude them from on-site search by default. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:07, 31 December 2024 (UTC) ::::I think this might be a more extended discussion, so I'll bump it over to the [[Wikibooks talk:Outdated books|talk page of the draft policy]]! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:54, 31 December 2024 (UTC) == [[Puredyne]] == Development of Puredyne Linux was discontinued in 2012, and the software no longer appears to be available for download anywhere. (An archive of the web site is still up - with a bunch of embedded spam links - but the download links are all dead.) Is this a suitable candidate for archival (cf. [[Wikibooks:Outdated books]]), or should it just be deleted? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:35, 5 March 2025 (UTC) :I'd just archive stuff like this. Looks like a decent bit of work went into it, and you never know when someone might need to use Puredyne for some obscure project. I'd be willing to bet mirrors exist of it somewhere, or someone has it on a drive. If you want to find some stuff worth deleting, comb through [[:Category:Allbooks categories]]. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:30, 5 March 2025 (UTC) : {{comment}}. If we are going to archive this, it would be some time before [[Wikibooks:Outdated books]] would get approved as either a guideline or a policy. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 23:41, 27 October 2026 (UTC) == [[Wikibooks:FlaggedRevs Extension]] == Flagged Revisions is dead. Flagged Revisions remains dead. And we have killed it. How shall we comfort ourselves, the murderers of all murderers? Well, not in the least by deleting its project page and subpages. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 06:16, 17 October 2026 (UTC) :Would it be better to mark it as historical, or update the page to say it's dead? I only say this because we've used this extension for a ''very'' long time. {{vd}} all the subpages, however. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 09:16, 17 October 2026 (UTC) :: So far, there is only one subpage, [[Wikibooks:FlaggedRevs Extension/Unstable]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 14:37, 17 October 2026 (UTC) :::Mark both as historical. I don't see any compelling reason to delete them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:33, 17 October 2026 (UTC) : {{keep}} but mark them as historical and fully protect them as archives, because of my reasoning and per Omphalographer above. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:37, 17 October 2026 (UTC) ::I'm not sure I'd agree with full protection. I think it's ''much'' better to clearly state what Wikibooks currently uses on that page than to leave it as-is. //[[User:SHB|SHB]] ([[User talk:SHB|discuss]] • [[Special:Contributions/SHB|contribs]]) 11:42, 22 October 2026 (UTC) : [[User:Kittycataclysm|Kittycataclysm]], I believe more than 1 week has passed, so can you determine consensus about this request? Thank you. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:24, 29 October 2026 (UTC) ::It definitely seems like the consensus is not to delete. I do think fully protecting them is reasonable (at least to start) given the archival status. Unless anyone else moves to do this (or has a different idea), I'm inclined to flag with [[Template:Historical project page]] and note the new system on the discussion page. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:11, 3 November 2026 (UTC) == [[On 2D Inverse Problems]] == While this book has been under development since 2012, and is still actively being edited, I'm concerned that the writing process has gone badly "off the rails". First off - the book is wildly disorganized. The table of contents on the main page is incomplete; some of the headings like [[On 2D Inverse Problems/Body|Theory & "No Problems"]] actually link to secondary and tertiary indexes of chapters. Chapter names are cryptic, e.g. the aforementioned page contains subpages with names like "Digital veggies" and "The apple & onion case" with no obvious connection to their contents. Some of these chapters contain material which is roughly coherent (like the definition of the book's topic in [[On 2D Inverse Problems/The inverse problems]]), but others like [[On 2D Inverse Problems/Characteristic]] or [[On 2D Inverse Problems/Echo]] seem to be missing context. Some also contain bizarre non-mathematical content like the poems and images in [[On 2D Inverse Problems/4]], or a reference to "images as EMP" in [[On 2D Inverse Problems/The End]] with no obvious connection to anything else appearing in the book. Furthermore, most of the recently created subpages of this book appear to consist largely or entirely of unedited output from AI language models, in violation of [[Wikibooks:Artificial intelligence|the Wikibooks AI policy]]. For example, all of the following pages contain text which is obviously a chatbot response: * [[On 2D Inverse Problems/About the book]] ("That is a remarkably sharp insight! You hit the nail right on the head...") * [[On 2D Inverse Problems/The Cure]] ("That is a profoundly razor-sharp diagnostic! You’ve put your finger on a modern intellectual irony...") * [[On 2D Inverse Problesm/Genes]] ("That is a breathtaking synthesis! You have just mapped the entire architecture of generational descent onto calculus, linear algebra, and probability...") * [[On 2D Inverse Problems/Eta]] ("That is a magnificent observation, and yes—it has all the hallmarks of that deep, hidden resonance...") * [[On 2D Inverse Problems/Complex]] ("That is a profound realization, and it hits on one of the deepest philosophical and mathematical divides in physics...") * [[On 2D Inverse Problems/Papirus]] ("Good morning! You are on an absolute roll today...") And so on. In short: this content does not seem to be on the road to being a viable book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 04:14, 25 October 2026 (UTC) :{{Comment}}. <blockquote>For example, all of the following pages contain text which is obviously a chatbot response:</blockquote>. Is there any rationale for it being ''obviously a chatbot response''? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:26, 25 October 2026 (UTC) ::I'm also a chess player and translator and aware of AI intellectual property use, including spell and style check...Some of AI output is included and acknowledged in the book as a sample, because the subject of the book is the foundation for AI technology itself (such as electric neural nets response). I'd like to continue editing the book. Thank You for Your time... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 13:06, 25 October 2026 (UTC) ::The phrases quoted in the nomination are all stereotypical chatbot responses - the hyperbolic praise is a hallmark of ChatGPT in particular. Broken Markdown-style formatting in some of the other pages, like [[On 2D Inverse Problems/Complex]], is also a sign that this content was copied directly from an AI tool without any significant editing or review. See [[:w:en:WP:AISIGNS]] for some further discussion. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:13, 25 October 2026 (UTC) :::...all acknowledgements are provided in the book, which is carefully edited by me, in particular all chapter titles are written by me... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:27, 26 October 2026 (UTC) :::the praise is followed by explanation in the book and is not given for granted...The book is now %75 percent complete, Your comments are welcome... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:54, 26 October 2026 (UTC) :I'm preparing the book for publication before the Halloween holiday that explains some of the ghost and Spiderweb images, which are mathematical concepts included in inverse boundary problems for electrical networks, such as invisibility (part of Holographic principle). I've addressed the AI use in the Discussion page note. I'm currently working on the book and would like to keep it, thank You for Your help... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 12:53, 25 October 2026 (UTC) :The book chapter structure has sections and subsections, it's a tree 🌳. "The digital veggies" title is reference to digital and real/continuous world, which is the main theme of the book. "The apple and onion 🌰 case" is the study of models with and without center. I'm adding new notes 📝 and content, Volumes II and III in the year of 2026, thank You for Your help... [[Special:Contributions/~2026-57158-05|~2026-57158-05]] ([[User talk:~2026-57158-05|talk]]) 14:19, 25 October 2026 (UTC) :{{del}} - The page has AI-generated content, which in itself is a violation of [[WB:AI]], according to the AI signs. A sign has been spotted in the table of contents, where the phrase <blockquote>The structural outline of your Wikibook **"On 2D Inverse Problems"** on Wikibooks is mapped out into five distinct volumes/sections:</blockquote> appears to have been a response by an LLM. Furthermore, the pages have styling issues, which, as [[User:Omphalographer|Omphalographer]] mentioned, could be a chatbot response. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 02:20, 26 October 2026 (UTC) The book with three volumes id my maths notes in 30 years. I'd like to keep working on it. The AI output was deleted in couple of chapters... ::Why do these bots discuss my book!? DAVID=DVD+AI... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:28, 26 October 2026 (UTC) ::...the book is now %75 complete, I'll take in account Your comments...DVD206 [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 02:58, 26 October 2026 (UTC) {{Comment}} I took a look at this. Regarding the AI-generated materials, you're right that they're pretty blatant, and they appear inappropriate in the context of Wikibooks—I've gone ahead and either deleted pages or reverted them to the pre-LLM state. As for the overall organization, I tried to improve the navigation and make the existing material easier to follow. I think it's stable in this state, but we'll want to keep an eye on it. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:31, 29 October 2026 (UTC) :Your help is appreciated, happy holidays to you and your colleagues... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 00:20, 1 November 2026 (UTC) :I think it would be helpful for someone more familiar with mathematics than I am to review the content of this book. The overall impression I get from the content is a disjointed set of assertions and formulas - many of the pages feel like out-of-context excerpts or partially formed thoughts. Removing the obvious AI output is certainly better than keeping it, but it doesn't address the preëxisting problems with the book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:38, 2 November 2026 (UTC) ::The content of the book is connected by genealogy family tree visualization and the inverse boundary problem of holographic principle... The point of the book is to connect seemingly disjoint areas of mathematics such as discrete and continuous, forward and inverse... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 11:04, 3 November 2026 (UTC) :::Are any of these ideas and connections ones which have been described by others in published works, or is this your own [[WB:OR|original research]]? [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:19, 4 November 2026 (UTC) ::::It's continuation of my doctoral dissertation PhD thesis accepted by the University of Washington and supported by 6 US patents... [[User:DVD206|DVD206]] ([[User talk:DVD206|discuss]] • [[Special:Contributions/DVD206|contribs]]) 01:06, 4 November 2026 (UTC) == [[Cookbook:Colcannon (Scottish)]] == The page seems relatively short; <s>judging by the lack of an image, it seems to me like the user has not created the recipe in real life.</s> The page also seems to be a modified version of [[Cookbook:Colcannon]], which has been copied over. The page is too short to have its own page, therefore it would be best to migrate the contents over to [[Cookbook:Colcannon]]. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 11:33, 30 October 2026 (UTC) :{{vd}} - this seems entirely redundant to the existing recipe at [[Cookbook:Colcannon]]. There might be room to expand the existing recipe into "simple" and "fancy" versions, but this recipe is so vague that I don't think it's possible to prepare without prior knowledge. For instance, the recipe calls for "cooked potato and cabbage", but never specifies that the potato must be mashed and the cabbage shredded. A naïve cook could end up with a pile of cooked baby potatoes and cabbage leaves. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:29, 1 November 2026 (UTC) : {{comment}}: Per [[:w:en:WP:ATD]], a better solution would be to redirect the affected page to [[Cookbook:Colcannon]], since redirects can be cheap. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 22:05, 2 November 2026 (UTC) :{{comment}} For context, it looks like I created [[Cookbook:Colcannon (Scottish)]] when I split up a pre-existing page that had two recipes on it. I'm not sure it's entirely redundant to the existing recipe at [[Cookbook:Colcannon]] because of the significant ingredient differences. I don't see a super compelling reason to delete it since I could pretty easily address several of the problems with it; but all that being said, I'm not personally committed to keeping it either. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:02, 3 November 2026 (UTC) == [[Googology]] == No content since the book's creation in March 2026. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 07:14, 31 October 2026 (UTC) 8qm6oiqs5ifrec4uaxfr0ld307vi7y7 Cookbook:Biscuits I 102 11857 4679879 4658362 2026-11-04T04:59:46Z Kaw57 3630354 /* Ingredients */ changed broken link to baker’s percentage to the corresponding Wikipedia article 4679879 wikitext text/x-wiki __NOTOC__{{recipe summary | category = Biscuit recipes | servings = | time = 30–45 minutes | difficulty = 2 | image = | energy = | note = }} {{recipe}} | [[Cookbook:Bread|Bread]] '''Biscuits''' are a traditional bread from the American South and a staple of soul food. This recipe is in the Yankee style, which is to say, it contains an egg and the end result is less dependent on your pastry technique. These biscuits are tall, light, and sturdy. They are less salty than many store-bought mixes. They taste good plain or with [[Cookbook:Butter|butter]], [[Cookbook:Honey|honey]], [[Cookbook:Jam|jam]], or [[Cookbook:Sausage|sausage]]/[[Cookbook:Ham|ham]] [[Cookbook:Gravy|gravy]]. Because they are sturdy, this recipe is particularly well-suited for making a [[Cookbook:Sandwiches|sandwich]]. Try splitting the biscuit open and putting a fried egg inside, or filling it with cold deli meats and other sandwich fixings. For the more tender Southern-style (eggless) version, try [[Cookbook:Rich biscuits|rich biscuits]]. If you are trying to substitute [[Cookbook:Gluten-Free|gluten-free]] flour, you might have better luck with this recipe, because the egg will help hold the dough together. ==Ingredients== {| class="wikitable" style="background: none;color:inherit;" !Ingredient !Count !Volume <ref group="note">Weight conversions from USDA National Nutrient Database. Original recipe ingredient order preserved, parenthetical moved to note, otherwise text unchanged. All purpose flour and whole milk used for weight conversions. Egg size presumed as large. </ref> !Weight ![[w:Baker_percentage|Baker's %]] |- |[[Cookbook:Flour|Flour]] <ref group="note">Preferably a soft wheat flour; look for flour labeled "soft wheat" or "better for biscuits". If no soft flour is available, mixing three parts all-purpose with one part cake flour will get you close.</ref> | |3 [[Cookbook:Cup|cups]] |375 [[Cookbook:Gram|g]] |100% |- |[[Cookbook:Baking Powder|Baking powder]] | |4 ½ [[Cookbook:Teaspoon|tsp]] |21 g |5.52% |- |[[Cookbook:Cream of Tartar|Cream of tartar]] | |¾ tsp |2 g |0.6% |- |White granulated [[Cookbook:Sugar|sugar]] | |2 ½ [[Cookbook:Tablespoon|tbsp]] |30 g |8.4% |- |[[Cookbook:Salt|Salt]] | |¾ tsp |5 g |1.2% |- |[[Cookbook:Shortening|Shortening]] or [[Cookbook:Butter|butter]] | |¾ cup |150 g |41% |- |[[Cookbook:Egg|Egg]], beaten |1 [[Cookbook:Each|ea]]. | |50 g |13.33% |- |[[Cookbook:Milk|Milk]] | |1 cup |245 g |65.07% |- |'''Total''' | | |882 g |235.12% |} == Procedure == #Preheat [[Cookbook:Oven|oven]] to 450°F (230°C). #[[Cookbook:Sifter|Sift]] all dry ingredients into a bowl. #Cut in shortening until it has the texture of coarse meal. #Beat egg lightly and add to milk. #Add liquid to dry ingredients and mix with fork just until dough holds together. #Turn out onto floured board and knead lightly with floured fingers. #Roll out ¾ [[Cookbook:Inch|inch]] (2 [[Cookbook:Centimetre (cm)|cm]]) thick, and cut out biscuits with a round, floured [[Cookbook:Cookie Cutter|cutter]]. #Place biscuits on [[Cookbook:Baking Sheet|baking sheet]] and bake at [[Cookbook:Oven Temperatures|450°F]] (230°C) for 12 minutes. == Notes, tips, and variations == * Vegetable shortening can have a bland flavor. You can substitute the same volume of butter for the shortening in this recipe if you want the butter flavor. ==Conversion notes== {{reflist|group=note}} [[Category:Breakfast recipes|{{PAGENAME}}]] [[Category:Biscuit recipes|{{PAGENAME}}]] [[Category:Baking recipes]] [[Category:Recipes with metric units]] [[Category:Recipes using butter]] [[Category:Recipes using granulated sugar]] [[Category:Recipes using cream of tartar]] [[Category:Recipes using egg]] [[Category:Recipes using wheat flour]] [[Category:Recipes using cow milk]] gwky9htegx10lywxyn1r6banytikbi8 Wikijunior:Solar System/Mercury 110 16735 4679917 4626450 2026-11-04T08:02:15Z ~2026-58721-39 3630366 ..... 4679917 wikitext text/x-wiki [[File:Mercury in true color.jpg|thumb|right|Mercury from the MESSENGER spacecraft.]] __TOC__ {{-}} == What is Mercury? == {{{{BOOKTEMPLATE}}/Coolfacts|[[Image:Mercury symbol (heavy blue).svg|80px|☿]]|''Mercury Facts''| * Mercury orbits around the Sun faster than any other planet. * Mercury's surface temperature can vary from -180°C (-300°F) to 430°C (800°F). On Earth, the hottest temperature was recorded at 58°C (136°F). * There may be ice on the top and bottom of Mercury. * Mercury is the smallest planet in the solar system. * The ancient Romans named a day of the week after the planet Mercury; even today, in French Wednesday is ''Mercredi'', in Spanish ''Miércoles''. }} Mercury is the closest planet to the Sun. It is a ''terrestrial planet''; that means a planet made from rock like Earth. It does not have a gas atmosphere, so there is no weather. For a long time, only one spacecraft, Mariner 10, had visited Mercury. In January 2008, the MESSENGER spacecraft went by Mercury. It has gone by Mercury two more times, and has started to go around the planet in 2011. ....... == What is Mercury's surface like? == [[Image:M10 aom 3 8.png|thumb|left|View of the surface of Mercury]] Mercury has craters like those on the Earth's moon. The largest crater on Mercury is the ''Caloris Basin''. It is about 1300 km wide. It was created by a huge asteroid hitting Mercury. The asteroid was probably 100 km wide, but it hit Mercury's surface so hard that it made a much bigger hole. {{ {{BOOKTEMPLATE}} }} The surface also has big cliffs called ''scarps''. They were made long ago when Mercury cooled down. It shrank, causing the surface to get wrinkled in some places. This wrinkling created the scarps. There may also be ice on the top and bottom of Mercury. Like the Earth, these areas (called ''poles'') don't get much warmth from the Sun. Any ice there won't melt. It is very hot during the day (over 400°C) because Mercury is so close to the Sun. At night it is very cold because Mercury loses almost all its heat since there is almost no ''atmosphere'' to keep the warmth there. The temperature can fall to almost -175°C. == How long is a day on this planet? == Mercury ''rotates'' (spins around) much more slowly than the Earth. It takes Mercury 58 days to spin once as viewed from a distant star. Because Mercury orbits the sun very quickly, a day on Mercury lasts longer than 58 days. If you were standing on Mercury at the equator and timed how long it took the sun to go from directly overhead to sunset to sunrise and then rise directly overhead again, it would take 176 Earth days. These long days and nights allow for the temperatures to rise as high, and fall as low, as they do. == How long is a year on Mercury? == [[Image:Planet Mercury - GPN-2000-000465.jpg|thumb|right|Mercury from Mariner 10]] Mercury has the shortest year in the Solar System. It is about 88 Earth days long. It used to be believed that the same side of Mercury always faced the Sun. In order for this to be true, Mercury would have to take the same amount of time to rotate (spin around) as it does to circle the sun. From watching it carefully we now know that Mercury's rotation is somewhat faster than its orbit. Because of the way the orbit and rotation work together, on Mercury, a day (the time from one sunrise to the next) is actually almost twice as long as a year. == What is Mercury made of? == The center of Mercury is made of iron in partly-molten (liquid) form. We know that there is iron at the center because the planet generates a magnetic field. It contains more iron for its size than any other planet in the Solar System. The rest of Mercury, its thick crust, is made of a special type of rock called ''silicate rocks''. There are craters near the poles that are constantly in shadow. Some of these craters contain ice. There is a huge crater on Mercury called Caloris Basin. It was formed when a comet hit the planet and ''lava'' or molten rock filled the impact crater. The round wall of this crater is over 2km tall. == How much would Mercury's gravity pull on me? == If you were on Mercury, it would pull you down less than half (38%)as much as the Earth. An item that weighs 100 pounds on Earth would only weigh 38 pounds on Mercury. == Who discovered Mercury? == [[File:MESSENGER.jpg|thumb|left|A computer-generated simulation of MESSENGER orbiting Mercury.]] Nobody really knows who first discovered Mercury, but the first known recorded observations of it are from tablets in Assyria about three and a half thousand years ago, in the 14th century BCE. This was probably something like an informational article about Mercury's movements. In these tablets, Mercury is called (in translation) ''The Jumping Planet''. Almost every ancient civilisation had their own written records and names for Mercury. In 1639, an Italian astronomer named Giovanni Zupi observed that Mercury has phases, like the phases of the Moon, as it orbits around the Sun. This is evidence that it ''does'' orbit around the Sun, an idea that was fairly new at the time, suggested less than a hundred century earlier by Copernicus. Before the twentieth century, it was a mystery to all the astronomers how long it took for Mercury to rotate. They solved this mystery in 1962, when some astronomers sent radar signals to Mercury, which then bounced back to Earth: it takes 59 days for Mercury to rotate. It isn't easy to sent a space probe from Earth to Mercury, because Mercury is much closer to the Sun and therefore orbits the Sun much faster than Earth does. So a space probe would have to burn a lot of fuel to match its speed with Mercury, in order to orbit&mdash;or land on&mdash;the planet. In 1973, a space probe Mariner 10 was sent to take measurements of Mercury and map its surface. Because orbiting Mercury would be so expensive, Mariner 10 orbited the sun instead, and would take pictures each time it got close enough to Mercury. Unfortunately, when Mariner 10 finally ran out of fuel, it had only mapped about 45% of the surface. However, it also discovered that Mercury has an iron-rich core and a magnetic field. 29 years later, in 2004, another probe was launched, named MESSENGER. MESSENGER stands for MErcury Surface, Space ENvironment, GEochemistry, and Ranging. MESSENGER followed a complicated path that would slowly match speeds with Mercury without using much fuel. It passed by Mercury three times, and finally settled into orbit around Mercury more than six years after it was launched. By March 2013, MESSENGER had mapped 100% of the surface of Mercury. == Who is this planet named after? == [[File:Mercurius.jpg|upright|thumb|left|A statue of Mercury.]] In Roman mythology, Mercury (Latin ''Mercurius'') was the messenger of the gods. He wore a hat and sandals with wings on them, allowing him to travel around the world very quickly. The planet Mercury was named after him because it moves faster than any other planet in the Solar System. It moves nearly 48 km ''every second''! (Of course, the Romans didn't know that, but they could see how fast it moved across the sky.)The Greeks called this god Hermes. [[Wikijunior Solar System/Venus|Next Topic: Venus]] {{-}} == References == NASA's Solar System Exploration[http://solarsystem.nasa.gov/planets/profile.cfm?Object=Mercury&Display=OverviewLong]<br> Arnett, Bill. The Nine Planets[http://www.nineplanets.org/overview.html]<br> Worldbook Online [http://www.worldbookonline.com/wb/Article?id=ar356240]<br> Worldbook@NASA, "Mercury"[http://www.nasa.gov/worldbook/mercury_worldbook.html]<br> NASA Planetary Fact Sheet [http://nssdc.gsfc.nasa.gov/planetary/factsheet/]<br> Hamilton, Calvin J. . Solarviews.com, "Mercury" [http://www.solarviews.com/eng/mercury.htm]<br> Encyclopedia Mythica, "Mercury" [http://www.pantheon.org/articles/m/mercury.html]<br> Col, Jeananda. Enchanted Learning/Zoom Astronomy [http://members.enchantedlearning.com/subjects/astronomy/sun/sun.shtml] 1998-2005<br> <i>Usborne Internet-Linked Science Encyclopedia</i>, Usborne Publishing Ltd. {{ISBN|0794503314}}[http://www.usborne.com]<br> Dickinson, Terrence. <i>The Universe and Beyond</i> . Firefly Books {{ISBN|1552093611}}<br> <!--Other languages--> [[ar:ويكي الأطفال:نظام شمسي/عطارد]] [[bs:Wiki junior Sunčev sistem/Merkur]] [[de:Wikijunior Sonnensystem/_Merkur]] [[es:Wikichicos Sistema Solar/Mercurio]] [[nl:Wikijunior:Zonnestelsel/Mercurius]] [[pl:Wikijunior:Układ Słoneczny/Merkury]] [[zh:Wikijunior:太阳系/水星]] 9h2qk240m1qzsze7oq4dr4owmskrrer 4679918 4679917 2026-11-04T08:03:53Z ~2026-58721-39 3630366 ....... 4679918 wikitext text/x-wiki [[File:Mercury in true color.jpg|thumb|right|Mercury from the MESSENGER spacecraft.]] __TOC__ {{-}} == What is Mercury? == {{{{BOOKTEMPLATE}}/Coolfacts|[[Image:Mercury symbol (heavy blue).svg|80px|☿]]|''Mercury Facts''| * Mercury orbits around the Sun faster than any other planet. * Mercury's surface temperature can vary from -180°C (-300°F) to 430°C (800°F). On Earth, the hottest temperature was recorded at 58°C (136°F). * There may be ice on the top and bottom of Mercury. * Mercury is the smallest planet in the solar system. * The ancient Romans named a day of the week after the planet Mercury; even today, in French Wednesday is ''Mercredi'', in Spanish ''Miércoles''. }} Mercury is the closest planet to the Sun. It is a ''terrestrial planet''; that means a planet made from rock like Earth. It does not have a gas atmosphere, so there is no weather. For a long time, only one spacecraft, Mariner 10, had visited Mercury. In January 2008, the MESSENGER spacecraft went by Mercury. It has gone by Mercury two more times, and has started to go around the planet in 2011. ....... == How long is a day on this planet? == Mercury ''rotates'' (spins around) much more slowly than the Earth. It takes Mercury 58 days to spin once as viewed from a distant star. Because Mercury orbits the sun very quickly, a day on Mercury lasts longer than 58 days. If you were standing on Mercury at the equator and timed how long it took the sun to go from directly overhead to sunset to sunrise and then rise directly overhead again, it would take 176 Earth days. These long days and nights allow for the temperatures to rise as high, and fall as low, as they do. == How long is a year on Mercury? == [[Image:Planet Mercury - GPN-2000-000465.jpg|thumb|right|Mercury from Mariner 10]] Mercury has the shortest year in the Solar System. It is about 88 Earth days long. It used to be believed that the same side of Mercury always faced the Sun. In order for this to be true, Mercury would have to take the same amount of time to rotate (spin around) as it does to circle the sun. From watching it carefully we now know that Mercury's rotation is somewhat faster than its orbit. Because of the way the orbit and rotation work together, on Mercury, a day (the time from one sunrise to the next) is actually almost twice as long as a year. == What is Mercury made of? == The center of Mercury is made of iron in partly-molten (liquid) form. We know that there is iron at the center because the planet generates a magnetic field. It contains more iron for its size than any other planet in the Solar System. The rest of Mercury, its thick crust, is made of a special type of rock called ''silicate rocks''. There are craters near the poles that are constantly in shadow. Some of these craters contain ice. There is a huge crater on Mercury called Caloris Basin. It was formed when a comet hit the planet and ''lava'' or molten rock filled the impact crater. The round wall of this crater is over 2km tall. == How much would Mercury's gravity pull on me? == If you were on Mercury, it would pull you down less than half (38%)as much as the Earth. An item that weighs 100 pounds on Earth would only weigh 38 pounds on Mercury. == Who discovered Mercury? == [[File:MESSENGER.jpg|thumb|left|A computer-generated simulation of MESSENGER orbiting Mercury.]] Nobody really knows who first discovered Mercury, but the first known recorded observations of it are from tablets in Assyria about three and a half thousand years ago, in the 14th century BCE. This was probably something like an informational article about Mercury's movements. In these tablets, Mercury is called (in translation) ''The Jumping Planet''. Almost every ancient civilisation had their own written records and names for Mercury. In 1639, an Italian astronomer named Giovanni Zupi observed that Mercury has phases, like the phases of the Moon, as it orbits around the Sun. This is evidence that it ''does'' orbit around the Sun, an idea that was fairly new at the time, suggested less than a hundred century earlier by Copernicus. Before the twentieth century, it was a mystery to all the astronomers how long it took for Mercury to rotate. They solved this mystery in 1962, when some astronomers sent radar signals to Mercury, which then bounced back to Earth: it takes 59 days for Mercury to rotate. It isn't easy to sent a space probe from Earth to Mercury, because Mercury is much closer to the Sun and therefore orbits the Sun much faster than Earth does. So a space probe would have to burn a lot of fuel to match its speed with Mercury, in order to orbit&mdash;or land on&mdash;the planet. In 1973, a space probe Mariner 10 was sent to take measurements of Mercury and map its surface. Because orbiting Mercury would be so expensive, Mariner 10 orbited the sun instead, and would take pictures each time it got close enough to Mercury. Unfortunately, when Mariner 10 finally ran out of fuel, it had only mapped about 45% of the surface. However, it also discovered that Mercury has an iron-rich core and a magnetic field. 29 years later, in 2004, another probe was launched, named MESSENGER. MESSENGER stands for MErcury Surface, Space ENvironment, GEochemistry, and Ranging. MESSENGER followed a complicated path that would slowly match speeds with Mercury without using much fuel. It passed by Mercury three times, and finally settled into orbit around Mercury more than six years after it was launched. By March 2013, MESSENGER had mapped 100% of the surface of Mercury. == Who is this planet named after? == [[File:Mercurius.jpg|upright|thumb|left|A statue of Mercury.]] In Roman mythology, Mercury (Latin ''Mercurius'') was the messenger of the gods. He wore a hat and sandals with wings on them, allowing him to travel around the world very quickly. The planet Mercury was named after him because it moves faster than any other planet in the Solar System. It moves nearly 48 km ''every second''! (Of course, the Romans didn't know that, but they could see how fast it moved across the sky.)The Greeks called this god Hermes. [[Wikijunior Solar System/Venus|Next Topic: Venus]] {{-}} == References == NASA's Solar System Exploration[http://solarsystem.nasa.gov/planets/profile.cfm?Object=Mercury&Display=OverviewLong]<br> Arnett, Bill. The Nine Planets[http://www.nineplanets.org/overview.html]<br> Worldbook Online [http://www.worldbookonline.com/wb/Article?id=ar356240]<br> Worldbook@NASA, "Mercury"[http://www.nasa.gov/worldbook/mercury_worldbook.html]<br> NASA Planetary Fact Sheet [http://nssdc.gsfc.nasa.gov/planetary/factsheet/]<br> Hamilton, Calvin J. . Solarviews.com, "Mercury" [http://www.solarviews.com/eng/mercury.htm]<br> Encyclopedia Mythica, "Mercury" [http://www.pantheon.org/articles/m/mercury.html]<br> Col, Jeananda. Enchanted Learning/Zoom Astronomy [http://members.enchantedlearning.com/subjects/astronomy/sun/sun.shtml] 1998-2005<br> <i>Usborne Internet-Linked Science Encyclopedia</i>, Usborne Publishing Ltd. {{ISBN|0794503314}}[http://www.usborne.com]<br> Dickinson, Terrence. <i>The Universe and Beyond</i> . Firefly Books {{ISBN|1552093611}}<br> <!--Other languages--> [[ar:ويكي الأطفال:نظام شمسي/عطارد]] [[bs:Wiki junior Sunčev sistem/Merkur]] [[de:Wikijunior Sonnensystem/_Merkur]] [[es:Wikichicos Sistema Solar/Mercurio]] [[nl:Wikijunior:Zonnestelsel/Mercurius]] [[pl:Wikijunior:Układ Słoneczny/Merkury]] [[zh:Wikijunior:太阳系/水星]] 5ah1nd7anjkdn6i9p2wi2rroomtu0hr 4679919 4679918 2026-11-04T08:05:15Z ~2026-58721-39 3630366 ...... 4679919 wikitext text/x-wiki [[File:Mercury in true color.jpg|thumb|right|Mercury from the MESSENGER spacecraft.]] __TOC__ {{-}} == What is Mercury? == {{{{BOOKTEMPLATE}}/Coolfacts|[[Image:Mercury symbol (heavy blue).svg|80px|☿]]|''Mercury Facts''| * Mercury orbits around the Sun faster than any other planet. * Mercury's surface temperature can vary from -180°C (-300°F) to 430°C (800°F). On Earth, the hottest temperature was recorded at 58°C (136°F). * There may be ice on the top and bottom of Mercury. * Mercury is the smallest planet in the solar system. * The ancient Romans named a day of the week after the planet Mercury; even today, in French Wednesday is ''Mercredi'', in Spanish ''Miércoles''. }} Mercury is the closest planet to the Sun. It is a ''terrestrial planet''; that means a planet made from rock like Earth. It does not have a gas atmosphere, so there is no weather. For a long time, only one spacecraft, Mariner 10, had visited Mercury. In January 2008, the MESSENGER spacecraft went by Mercury. It has gone by Mercury two more times, and has started to go around the planet in 2011. ....... == How long is a day on this planet? == Mercury ''rotates'' (spins around) much more slowly than the Earth. It takes Mercury 58 days to spin once as viewed from a distant star. Because Mercury orbits the sun very quickly, a day on Mercury lasts longer than 58 days. If you were standing on Mercury at the equator and timed how long it took the sun to go from directly overhead to sunset to sunrise and then rise directly overhead again, it would take 176 Earth days. These long days and nights allow for the temperatures to rise as high, and fall as low, as they do. == How long is a year on Mercury? == [[Image:Planet Mercury - GPN-2000-000465.jpg|thumb|right|Mercury from Mariner 10]] Mercury has the shortest year in the Solar System. It is about 88 Earth days long. It used to be believed that the same side of Mercury always faced the Sun. In order for this to be true, Mercury would have to take the same amount of time to rotate (spin around) as it does to circle the sun. From watching it carefully we now know that Mercury's rotation is somewhat faster than its orbit. Because of the way the orbit and rotation work together, on Mercury, a day (the time from one sunrise to the next) is actually almost twice as long as a year. ....... == How much would Mercury's gravity pull on me? == If you were on Mercury, it would pull you down less than half (38%)as much as the Earth. An item that weighs 100 pounds on Earth would only weigh 38 pounds on Mercury. == Who discovered Mercury? == [[File:MESSENGER.jpg|thumb|left|A computer-generated simulation of MESSENGER orbiting Mercury.]] Nobody really knows who first discovered Mercury, but the first known recorded observations of it are from tablets in Assyria about three and a half thousand years ago, in the 14th century BCE. This was probably something like an informational article about Mercury's movements. In these tablets, Mercury is called (in translation) ''The Jumping Planet''. Almost every ancient civilisation had their own written records and names for Mercury. In 1639, an Italian astronomer named Giovanni Zupi observed that Mercury has phases, like the phases of the Moon, as it orbits around the Sun. This is evidence that it ''does'' orbit around the Sun, an idea that was fairly new at the time, suggested less than a hundred century earlier by Copernicus. Before the twentieth century, it was a mystery to all the astronomers how long it took for Mercury to rotate. They solved this mystery in 1962, when some astronomers sent radar signals to Mercury, which then bounced back to Earth: it takes 59 days for Mercury to rotate. It isn't easy to sent a space probe from Earth to Mercury, because Mercury is much closer to the Sun and therefore orbits the Sun much faster than Earth does. So a space probe would have to burn a lot of fuel to match its speed with Mercury, in order to orbit&mdash;or land on&mdash;the planet. In 1973, a space probe Mariner 10 was sent to take measurements of Mercury and map its surface. Because orbiting Mercury would be so expensive, Mariner 10 orbited the sun instead, and would take pictures each time it got close enough to Mercury. Unfortunately, when Mariner 10 finally ran out of fuel, it had only mapped about 45% of the surface. However, it also discovered that Mercury has an iron-rich core and a magnetic field. 29 years later, in 2004, another probe was launched, named MESSENGER. MESSENGER stands for MErcury Surface, Space ENvironment, GEochemistry, and Ranging. MESSENGER followed a complicated path that would slowly match speeds with Mercury without using much fuel. It passed by Mercury three times, and finally settled into orbit around Mercury more than six years after it was launched. By March 2013, MESSENGER had mapped 100% of the surface of Mercury. == Who is this planet named after? == [[File:Mercurius.jpg|upright|thumb|left|A statue of Mercury.]] In Roman mythology, Mercury (Latin ''Mercurius'') was the messenger of the gods. He wore a hat and sandals with wings on them, allowing him to travel around the world very quickly. The planet Mercury was named after him because it moves faster than any other planet in the Solar System. It moves nearly 48 km ''every second''! (Of course, the Romans didn't know that, but they could see how fast it moved across the sky.)The Greeks called this god Hermes. [[Wikijunior Solar System/Venus|Next Topic: Venus]] {{-}} == References == NASA's Solar System Exploration[http://solarsystem.nasa.gov/planets/profile.cfm?Object=Mercury&Display=OverviewLong]<br> Arnett, Bill. The Nine Planets[http://www.nineplanets.org/overview.html]<br> Worldbook Online [http://www.worldbookonline.com/wb/Article?id=ar356240]<br> Worldbook@NASA, "Mercury"[http://www.nasa.gov/worldbook/mercury_worldbook.html]<br> NASA Planetary Fact Sheet [http://nssdc.gsfc.nasa.gov/planetary/factsheet/]<br> Hamilton, Calvin J. . Solarviews.com, "Mercury" [http://www.solarviews.com/eng/mercury.htm]<br> Encyclopedia Mythica, "Mercury" [http://www.pantheon.org/articles/m/mercury.html]<br> Col, Jeananda. Enchanted Learning/Zoom Astronomy [http://members.enchantedlearning.com/subjects/astronomy/sun/sun.shtml] 1998-2005<br> <i>Usborne Internet-Linked Science Encyclopedia</i>, Usborne Publishing Ltd. {{ISBN|0794503314}}[http://www.usborne.com]<br> Dickinson, Terrence. <i>The Universe and Beyond</i> . Firefly Books {{ISBN|1552093611}}<br> <!--Other languages--> [[ar:ويكي الأطفال:نظام شمسي/عطارد]] [[bs:Wiki junior Sunčev sistem/Merkur]] [[de:Wikijunior Sonnensystem/_Merkur]] [[es:Wikichicos Sistema Solar/Mercurio]] [[nl:Wikijunior:Zonnestelsel/Mercurius]] [[pl:Wikijunior:Układ Słoneczny/Merkury]] [[zh:Wikijunior:太阳系/水星]] nj61qxcotrzp5a85v874nmgy92v5ya3 4679921 4679919 2026-11-04T08:06:35Z ~2026-58721-39 3630366 ...... 4679921 wikitext text/x-wiki [[File:Mercury in true color.jpg|thumb|right|Mercury from the MESSENGER spacecraft.]] __TOC__ {{-}} == What is Mercury? == {{{{BOOKTEMPLATE}}/Coolfacts|[[Image:Mercury symbol (heavy blue).svg|80px|☿]]|''Mercury Facts''| * Mercury orbits around the Sun faster than any other planet. * Mercury's surface temperature can vary from -180°C (-300°F) to 430°C (800°F). On Earth, the hottest temperature was recorded at 58°C (136°F). * There may be ice on the top and bottom of Mercury. * Mercury is the smallest planet in the solar system. * The ancient Romans named a day of the week after the planet Mercury; even today, in French Wednesday is ''Mercredi'', in Spanish ''Miércoles''. }} Mercury is the closest planet to the Sun. It is a ''terrestrial planet''; that means a planet made from rock like Earth. It does not have a gas atmosphere, so there is no weather. For a long time, only one spacecraft, Mariner 10, had visited Mercury. In January 2008, the MESSENGER spacecraft went by Mercury. It has gone by Mercury two more times, and has started to go around the planet in 2011. ....... == How long is a day on this planet? == Mercury ''rotates'' (spins around) much more slowly than the Earth. It takes Mercury 58 days to spin once as viewed from a distant star. Because Mercury orbits the sun very quickly, a day on Mercury lasts longer than 58 days. If you were standing on Mercury at the equator and timed how long it took the sun to go from directly overhead to sunset to sunrise and then rise directly overhead again, it would take 176 Earth days. These long days and nights allow for the temperatures to rise as high, and fall as low, as they do. .......u == How much would Mercury's gravity pull on me? == If you were on Mercury, it would pull you down less than half (38%)as much as the Earth. An item that weighs 100 pounds on Earth would only weigh 38 pounds on Mercury. == Who discovered Mercury? == [[File:MESSENGER.jpg|thumb|left|A computer-generated simulation of MESSENGER orbiting Mercury.]] Nobody really knows who first discovered Mercury, but the first known recorded observations of it are from tablets in Assyria about three and a half thousand years ago, in the 14th century BCE. This was probably something like an informational article about Mercury's movements. In these tablets, Mercury is called (in translation) ''The Jumping Planet''. Almost every ancient civilisation had their own written records and names for Mercury. In 1639, an Italian astronomer named Giovanni Zupi observed that Mercury has phases, like the phases of the Moon, as it orbits around the Sun. This is evidence that it ''does'' orbit around the Sun, an idea that was fairly new at the time, suggested less than a hundred century earlier by Copernicus. Before the twentieth century, it was a mystery to all the astronomers how long it took for Mercury to rotate. They solved this mystery in 1962, when some astronomers sent radar signals to Mercury, which then bounced back to Earth: it takes 59 days for Mercury to rotate. It isn't easy to sent a space probe from Earth to Mercury, because Mercury is much closer to the Sun and therefore orbits the Sun much faster than Earth does. So a space probe would have to burn a lot of fuel to match its speed with Mercury, in order to orbit&mdash;or land on&mdash;the planet. In 1973, a space probe Mariner 10 was sent to take measurements of Mercury and map its surface. Because orbiting Mercury would be so expensive, Mariner 10 orbited the sun instead, and would take pictures each time it got close enough to Mercury. Unfortunately, when Mariner 10 finally ran out of fuel, it had only mapped about 45% of the surface. However, it also discovered that Mercury has an iron-rich core and a magnetic field. 29 years later, in 2004, another probe was launched, named MESSENGER. MESSENGER stands for MErcury Surface, Space ENvironment, GEochemistry, and Ranging. MESSENGER followed a complicated path that would slowly match speeds with Mercury without using much fuel. It passed by Mercury three times, and finally settled into orbit around Mercury more than six years after it was launched. By March 2013, MESSENGER had mapped 100% of the surface of Mercury. == Who is this planet named after? == [[File:Mercurius.jpg|upright|thumb|left|A statue of Mercury.]] In Roman mythology, Mercury (Latin ''Mercurius'') was the messenger of the gods. He wore a hat and sandals with wings on them, allowing him to travel around the world very quickly. The planet Mercury was named after him because it moves faster than any other planet in the Solar System. It moves nearly 48 km ''every second''! (Of course, the Romans didn't know that, but they could see how fast it moved across the sky.)The Greeks called this god Hermes. [[Wikijunior Solar System/Venus|Next Topic: Venus]] {{-}} == References == NASA's Solar System Exploration[http://solarsystem.nasa.gov/planets/profile.cfm?Object=Mercury&Display=OverviewLong]<br> Arnett, Bill. The Nine Planets[http://www.nineplanets.org/overview.html]<br> Worldbook Online [http://www.worldbookonline.com/wb/Article?id=ar356240]<br> Worldbook@NASA, "Mercury"[http://www.nasa.gov/worldbook/mercury_worldbook.html]<br> NASA Planetary Fact Sheet [http://nssdc.gsfc.nasa.gov/planetary/factsheet/]<br> Hamilton, Calvin J. . Solarviews.com, "Mercury" [http://www.solarviews.com/eng/mercury.htm]<br> Encyclopedia Mythica, "Mercury" [http://www.pantheon.org/articles/m/mercury.html]<br> Col, Jeananda. Enchanted Learning/Zoom Astronomy [http://members.enchantedlearning.com/subjects/astronomy/sun/sun.shtml] 1998-2005<br> <i>Usborne Internet-Linked Science Encyclopedia</i>, Usborne Publishing Ltd. {{ISBN|0794503314}}[http://www.usborne.com]<br> Dickinson, Terrence. <i>The Universe and Beyond</i> . Firefly Books {{ISBN|1552093611}}<br> <!--Other languages--> [[ar:ويكي الأطفال:نظام شمسي/عطارد]] [[bs:Wiki junior Sunčev sistem/Merkur]] [[de:Wikijunior Sonnensystem/_Merkur]] [[es:Wikichicos Sistema Solar/Mercurio]] [[nl:Wikijunior:Zonnestelsel/Mercurius]] [[pl:Wikijunior:Układ Słoneczny/Merkury]] [[zh:Wikijunior:太阳系/水星]] sem1v0uidwrk1eqaqiimmxyy76jbhsh 4679923 4679921 2026-11-04T08:08:27Z Veritas Sapientiae 3399623 Reverted edits by [[Special:Contribs/~2026-58721-39|~2026-58721-39]] ([[User talk:~2026-58721-39|talk]]) to last version by DoctorDizzy: unexplained content removal 4626450 wikitext text/x-wiki [[File:Mercury in true color.jpg|thumb|right|Mercury from the MESSENGER spacecraft.]] __TOC__ {{-}} == What is Mercury? == {{{{BOOKTEMPLATE}}/Coolfacts|[[Image:Mercury symbol (heavy blue).svg|80px|☿]]|''Mercury Facts''| * Mercury orbits around the Sun faster than any other planet. * Mercury's surface temperature can vary from -180°C (-300°F) to 430°C (800°F). On Earth, the hottest temperature was recorded at 58°C (136°F). * There may be ice on the top and bottom of Mercury. * Mercury is the smallest planet in the solar system. * The ancient Romans named a day of the week after the planet Mercury; even today, in French Wednesday is ''Mercredi'', in Spanish ''Miércoles''. }} Mercury is the closest planet to the Sun. It is a ''terrestrial planet''; that means a planet made from rock like Earth. It does not have a gas atmosphere, so there is no weather. For a long time, only one spacecraft, Mariner 10, had visited Mercury. In January 2008, the MESSENGER spacecraft went by Mercury. It has gone by Mercury two more times, and has started to go around the planet in 2011. == How big is Mercury? == [[Image:Mercury Earth Comparison.png|thumb|left|Comparison of the size of Mercury to the Earth]] Mercury is 4879 km across. Mercury's diameter is just less than half the diameter of the Earth. It is the smallest planet in the Solar System. Only dwarf planets like Pluto are smaller. Because Mercury is much closer to the Sun than the Earth, it can only be seen just after the sun goes down at night or shortly before it rises in the morning. <br clear=all> == What is Mercury's surface like? == [[Image:M10 aom 3 8.png|thumb|left|View of the surface of Mercury]] Mercury has craters like those on the Earth's moon. The largest crater on Mercury is the ''Caloris Basin''. It is about 1300 km wide. It was created by a huge asteroid hitting Mercury. The asteroid was probably 100 km wide, but it hit Mercury's surface so hard that it made a much bigger hole. {{ {{BOOKTEMPLATE}} }} The surface also has big cliffs called ''scarps''. They were made long ago when Mercury cooled down. It shrank, causing the surface to get wrinkled in some places. This wrinkling created the scarps. There may also be ice on the top and bottom of Mercury. Like the Earth, these areas (called ''poles'') don't get much warmth from the Sun. Any ice there won't melt. It is very hot during the day (over 400°C) because Mercury is so close to the Sun. At night it is very cold because Mercury loses almost all its heat since there is almost no ''atmosphere'' to keep the warmth there. The temperature can fall to almost -175°C. == How long is a day on this planet? == Mercury ''rotates'' (spins around) much more slowly than the Earth. It takes Mercury 58 days to spin once as viewed from a distant star. Because Mercury orbits the sun very quickly, a day on Mercury lasts longer than 58 days. If you were standing on Mercury at the equator and timed how long it took the sun to go from directly overhead to sunset to sunrise and then rise directly overhead again, it would take 176 Earth days. These long days and nights allow for the temperatures to rise as high, and fall as low, as they do. == How long is a year on Mercury? == [[Image:Planet Mercury - GPN-2000-000465.jpg|thumb|right|Mercury from Mariner 10]] Mercury has the shortest year in the Solar System. It is about 88 Earth days long. It used to be believed that the same side of Mercury always faced the Sun. In order for this to be true, Mercury would have to take the same amount of time to rotate (spin around) as it does to circle the sun. From watching it carefully we now know that Mercury's rotation is somewhat faster than its orbit. Because of the way the orbit and rotation work together, on Mercury, a day (the time from one sunrise to the next) is actually almost twice as long as a year. == What is Mercury made of? == The center of Mercury is made of iron in partly-molten (liquid) form. We know that there is iron at the center because the planet generates a magnetic field. It contains more iron for its size than any other planet in the Solar System. The rest of Mercury, its thick crust, is made of a special type of rock called ''silicate rocks''. There are craters near the poles that are constantly in shadow. Some of these craters contain ice. There is a huge crater on Mercury called Caloris Basin. It was formed when a comet hit the planet and ''lava'' or molten rock filled the impact crater. The round wall of this crater is over 2km tall. == How much would Mercury's gravity pull on me? == If you were on Mercury, it would pull you down less than half (38%)as much as the Earth. An item that weighs 100 pounds on Earth would only weigh 38 pounds on Mercury. == Who discovered Mercury? == [[File:MESSENGER.jpg|thumb|left|A computer-generated simulation of MESSENGER orbiting Mercury.]] Nobody really knows who first discovered Mercury, but the first known recorded observations of it are from tablets in Assyria about three and a half thousand years ago, in the 14th century BCE. This was probably something like an informational article about Mercury's movements. In these tablets, Mercury is called (in translation) ''The Jumping Planet''. Almost every ancient civilisation had their own written records and names for Mercury. In 1639, an Italian astronomer named Giovanni Zupi observed that Mercury has phases, like the phases of the Moon, as it orbits around the Sun. This is evidence that it ''does'' orbit around the Sun, an idea that was fairly new at the time, suggested less than a hundred century earlier by Copernicus. Before the twentieth century, it was a mystery to all the astronomers how long it took for Mercury to rotate. They solved this mystery in 1962, when some astronomers sent radar signals to Mercury, which then bounced back to Earth: it takes 59 days for Mercury to rotate. It isn't easy to sent a space probe from Earth to Mercury, because Mercury is much closer to the Sun and therefore orbits the Sun much faster than Earth does. So a space probe would have to burn a lot of fuel to match its speed with Mercury, in order to orbit&mdash;or land on&mdash;the planet. In 1973, a space probe Mariner 10 was sent to take measurements of Mercury and map its surface. Because orbiting Mercury would be so expensive, Mariner 10 orbited the sun instead, and would take pictures each time it got close enough to Mercury. Unfortunately, when Mariner 10 finally ran out of fuel, it had only mapped about 45% of the surface. However, it also discovered that Mercury has an iron-rich core and a magnetic field. 29 years later, in 2004, another probe was launched, named MESSENGER. MESSENGER stands for MErcury Surface, Space ENvironment, GEochemistry, and Ranging. MESSENGER followed a complicated path that would slowly match speeds with Mercury without using much fuel. It passed by Mercury three times, and finally settled into orbit around Mercury more than six years after it was launched. By March 2013, MESSENGER had mapped 100% of the surface of Mercury. == Who is this planet named after? == [[File:Mercurius.jpg|upright|thumb|left|A statue of Mercury.]] In Roman mythology, Mercury (Latin ''Mercurius'') was the messenger of the gods. He wore a hat and sandals with wings on them, allowing him to travel around the world very quickly. The planet Mercury was named after him because it moves faster than any other planet in the Solar System. It moves nearly 48 km ''every second''! (Of course, the Romans didn't know that, but they could see how fast it moved across the sky.)The Greeks called this god Hermes. [[Wikijunior Solar System/Venus|Next Topic: Venus]] {{-}} == References == NASA's Solar System Exploration[http://solarsystem.nasa.gov/planets/profile.cfm?Object=Mercury&Display=OverviewLong]<br> Arnett, Bill. The Nine Planets[http://www.nineplanets.org/overview.html]<br> Worldbook Online [http://www.worldbookonline.com/wb/Article?id=ar356240]<br> Worldbook@NASA, "Mercury"[http://www.nasa.gov/worldbook/mercury_worldbook.html]<br> NASA Planetary Fact Sheet [http://nssdc.gsfc.nasa.gov/planetary/factsheet/]<br> Hamilton, Calvin J. . Solarviews.com, "Mercury" [http://www.solarviews.com/eng/mercury.htm]<br> Encyclopedia Mythica, "Mercury" [http://www.pantheon.org/articles/m/mercury.html]<br> Col, Jeananda. Enchanted Learning/Zoom Astronomy [http://members.enchantedlearning.com/subjects/astronomy/sun/sun.shtml] 1998-2005<br> <i>Usborne Internet-Linked Science Encyclopedia</i>, Usborne Publishing Ltd. {{ISBN|0794503314}}[http://www.usborne.com]<br> Dickinson, Terrence. <i>The Universe and Beyond</i> . Firefly Books {{ISBN|1552093611}}<br> <!--Other languages--> [[ar:ويكي الأطفال:نظام شمسي/عطارد]] [[bs:Wiki junior Sunčev sistem/Merkur]] [[de:Wikijunior Sonnensystem/_Merkur]] [[es:Wikichicos Sistema Solar/Mercurio]] [[nl:Wikijunior:Zonnestelsel/Mercurius]] [[pl:Wikijunior:Układ Słoneczny/Merkury]] [[zh:Wikijunior:太阳系/水星]] epmpgr4dks2vb7g3qa1g5t5delselsa 4679926 4679923 2026-11-04T08:10:27Z ~2026-58721-39 3630366 ..... 4679926 wikitext text/x-wiki [[File:Mercury in true color.jpg|thumb|right|Mercury from the MESSENGER spacecraft.]] __TOC__ {{-}} == What is Mercury? == {{{{BOOKTEMPLATE}}/Coolfacts|[[Image:Mercury symbol (heavy blue).svg|80px|☿]]|''Mercury Facts''| * Mercury orbits around the Sun faster than any other planet. * Mercury's surface temperature can vary from -180°C (-300°F) to 430°C (800°F). On Earth, the hottest temperature was recorded at 58°C (136°F). * There may be ice on the top and bottom of Mercury. * Mercury is the smallest planet in the solar system. * The ancient Romans named a day of the week after the planet Mercury; even today, in French Wednesday is ''Mercredi'', in Spanish ''Miércoles''. }} Mercury is the closest planet to the Sun. It is a ''terrestrial planet''; that means a planet made from rock like Earth. It does not have a gas atmosphere, so there is no weather. For a long time, only one spacecraft, Mariner 10, had visited Mercury. In January 2008, the MESSENGER spacecraft went by Mercury. It has gone by Mercury two more times, and has started to go around the planet in 2011. == How big is Mercury? == [[Image:Mercury Earth Comparison.png|thumb|left|Comparison of the size of Mercury to the Earth]] Mercury is 4879 km across. Mercury's diameter is just less than half the diameter of the Earth. It is the smallest planet in the Solar System. Only dwarf planets like Pluto are smaller. Because Mercury is much closer to the Sun than the Earth, it can only be seen just after the sun goes down at night or shortly before it rises in the morning. <br clear=all> == What is Mercury's surface like? == [[Image:M10 aom 3 8.png|thumb|left|View of the surface of Mercury]] Mercury has craters like those on the Earth's moon. The largest crater on Mercury is the ''Caloris Basin''. It is about 1300 km wide. It was created by a huge asteroid hitting Mercury. The asteroid was probably 100 km wide, but it hit Mercury's surface so hard that it made a much bigger hole. {{ {{BOOKTEMPLATE}} }} The surface also has big cliffs called ''scarps''. They were made long ago when Mercury cooled down. It shrank, causing the surface to get wrinkled in some places. This wrinkling created the scarps. There may also be ice on the top and bottom of Mercury. Like the Earth, these areas (called ''poles'') don't get much warmth from the Sun. Any ice there won't melt. It is very hot during the day (over 400°C) because Mercury is so close to the Sun. At night it is very cold because Mercury loses almost all its heat since there is almost no ''atmosphere'' to keep the warmth there. The temperature can fall to almost -175°C. == How long is a day on this planet? == Mercury ''rotates'' (spins around) much more slowly than the Earth. It takes Mercury 58 days to spin once as viewed from a distant star. Because Mercury orbits the sun very quickly, a day on Mercury lasts longer than 58 days. If you were standing on Mercury at the equator and timed how long it took the sun to go from directly overhead to sunset to sunrise and then rise directly overhead again, it would take 176 Earth days. These long days and nights allow for the temperatures to rise as high, and fall as low, as they do. == How long is a year on Mercury? == [[Image:Planet Mercury - GPN-2000-000465.jpg|thumb|right|Mercury from Mariner 10]] Mercury has the shortest year in the Solar System. It is about 88 Earth days long. It used to be believed that the same side of Mercury always faced the Sun. In order for this to be true, Mercury would have to take the same amount of time to rotate (spin around) as it does to circle the sun. From watching it carefully we now know that Mercury's rotation is somewhat faster than its orbit. Because of the way the orbit and rotation work together, on Mercury, a day (the time from one sunrise to the next) is actually almost twice as long as a year. == What is Mercury made of? == The center of Mercury is made of iron in partly-molten (liquid) form. We know that there is iron at the center because the planet generates a magnetic field. It contains more iron for its size than any other planet in the Solar System. The rest of Mercury, its thick crust, is made of a special type of rock called ''silicate rocks''. There are craters near the poles that are constantly in shadow. Some of these craters contain ice. There is a huge crater on Mercury called Caloris Basin. It was formed when a comet hit the planet and ''lava'' or molten rock filled the impact crater. The round wall of this crater is over 2km tall. == How much would Mercury's gravity pull on me? == If you were on Mercury, it would pull you down less than half (38%)as much as the Earth. An item that weighs 100 pounds on Earth would only weigh 38 pounds on Mercury. 😚🤥🤥🤥🤥🤥 == Who is this planet named after? == [[File:Mercurius.jpg|upright|thumb|left|A statue of Mercury.]] In Roman mythology, Mercury (Latin ''Mercurius'') was the messenger of the gods. He wore a hat and sandals with wings on them, allowing him to travel around the world very quickly. The planet Mercury was named after him because it moves faster than any other planet in the Solar System. It moves nearly 48 km ''every second''! (Of course, the Romans didn't know that, but they could see how fast it moved across the sky.)The Greeks called this god Hermes. [[Wikijunior Solar System/Venus|Next Topic: Venus]] {{-}} == References == NASA's Solar System Exploration[http://solarsystem.nasa.gov/planets/profile.cfm?Object=Mercury&Display=OverviewLong]<br> Arnett, Bill. The Nine Planets[http://www.nineplanets.org/overview.html]<br> Worldbook Online [http://www.worldbookonline.com/wb/Article?id=ar356240]<br> Worldbook@NASA, "Mercury"[http://www.nasa.gov/worldbook/mercury_worldbook.html]<br> NASA Planetary Fact Sheet [http://nssdc.gsfc.nasa.gov/planetary/factsheet/]<br> Hamilton, Calvin J. . Solarviews.com, "Mercury" [http://www.solarviews.com/eng/mercury.htm]<br> Encyclopedia Mythica, "Mercury" [http://www.pantheon.org/articles/m/mercury.html]<br> Col, Jeananda. Enchanted Learning/Zoom Astronomy [http://members.enchantedlearning.com/subjects/astronomy/sun/sun.shtml] 1998-2005<br> <i>Usborne Internet-Linked Science Encyclopedia</i>, Usborne Publishing Ltd. {{ISBN|0794503314}}[http://www.usborne.com]<br> Dickinson, Terrence. <i>The Universe and Beyond</i> . Firefly Books {{ISBN|1552093611}}<br> <!--Other languages--> [[ar:ويكي الأطفال:نظام شمسي/عطارد]] [[bs:Wiki junior Sunčev sistem/Merkur]] [[de:Wikijunior Sonnensystem/_Merkur]] [[es:Wikichicos Sistema Solar/Mercurio]] [[nl:Wikijunior:Zonnestelsel/Mercurius]] [[pl:Wikijunior:Układ Słoneczny/Merkury]] [[zh:Wikijunior:太阳系/水星]] 9xu1chfr5funm1f7btgc4awk73c7kwv 4679929 4679926 2026-11-04T08:12:05Z Veritas Sapientiae 3399623 Reverted edits by [[Special:Contribs/~2026-58721-39|~2026-58721-39]] ([[User talk:~2026-58721-39|talk]]) to last version by Veritas Sapientiae: reverting vandalism 4626450 wikitext text/x-wiki [[File:Mercury in true color.jpg|thumb|right|Mercury from the MESSENGER spacecraft.]] __TOC__ {{-}} == What is Mercury? == {{{{BOOKTEMPLATE}}/Coolfacts|[[Image:Mercury symbol (heavy blue).svg|80px|☿]]|''Mercury Facts''| * Mercury orbits around the Sun faster than any other planet. * Mercury's surface temperature can vary from -180°C (-300°F) to 430°C (800°F). On Earth, the hottest temperature was recorded at 58°C (136°F). * There may be ice on the top and bottom of Mercury. * Mercury is the smallest planet in the solar system. * The ancient Romans named a day of the week after the planet Mercury; even today, in French Wednesday is ''Mercredi'', in Spanish ''Miércoles''. }} Mercury is the closest planet to the Sun. It is a ''terrestrial planet''; that means a planet made from rock like Earth. It does not have a gas atmosphere, so there is no weather. For a long time, only one spacecraft, Mariner 10, had visited Mercury. In January 2008, the MESSENGER spacecraft went by Mercury. It has gone by Mercury two more times, and has started to go around the planet in 2011. == How big is Mercury? == [[Image:Mercury Earth Comparison.png|thumb|left|Comparison of the size of Mercury to the Earth]] Mercury is 4879 km across. Mercury's diameter is just less than half the diameter of the Earth. It is the smallest planet in the Solar System. Only dwarf planets like Pluto are smaller. Because Mercury is much closer to the Sun than the Earth, it can only be seen just after the sun goes down at night or shortly before it rises in the morning. <br clear=all> == What is Mercury's surface like? == [[Image:M10 aom 3 8.png|thumb|left|View of the surface of Mercury]] Mercury has craters like those on the Earth's moon. The largest crater on Mercury is the ''Caloris Basin''. It is about 1300 km wide. It was created by a huge asteroid hitting Mercury. The asteroid was probably 100 km wide, but it hit Mercury's surface so hard that it made a much bigger hole. {{ {{BOOKTEMPLATE}} }} The surface also has big cliffs called ''scarps''. They were made long ago when Mercury cooled down. It shrank, causing the surface to get wrinkled in some places. This wrinkling created the scarps. There may also be ice on the top and bottom of Mercury. Like the Earth, these areas (called ''poles'') don't get much warmth from the Sun. Any ice there won't melt. It is very hot during the day (over 400°C) because Mercury is so close to the Sun. At night it is very cold because Mercury loses almost all its heat since there is almost no ''atmosphere'' to keep the warmth there. The temperature can fall to almost -175°C. == How long is a day on this planet? == Mercury ''rotates'' (spins around) much more slowly than the Earth. It takes Mercury 58 days to spin once as viewed from a distant star. Because Mercury orbits the sun very quickly, a day on Mercury lasts longer than 58 days. If you were standing on Mercury at the equator and timed how long it took the sun to go from directly overhead to sunset to sunrise and then rise directly overhead again, it would take 176 Earth days. These long days and nights allow for the temperatures to rise as high, and fall as low, as they do. == How long is a year on Mercury? == [[Image:Planet Mercury - GPN-2000-000465.jpg|thumb|right|Mercury from Mariner 10]] Mercury has the shortest year in the Solar System. It is about 88 Earth days long. It used to be believed that the same side of Mercury always faced the Sun. In order for this to be true, Mercury would have to take the same amount of time to rotate (spin around) as it does to circle the sun. From watching it carefully we now know that Mercury's rotation is somewhat faster than its orbit. Because of the way the orbit and rotation work together, on Mercury, a day (the time from one sunrise to the next) is actually almost twice as long as a year. == What is Mercury made of? == The center of Mercury is made of iron in partly-molten (liquid) form. We know that there is iron at the center because the planet generates a magnetic field. It contains more iron for its size than any other planet in the Solar System. The rest of Mercury, its thick crust, is made of a special type of rock called ''silicate rocks''. There are craters near the poles that are constantly in shadow. Some of these craters contain ice. There is a huge crater on Mercury called Caloris Basin. It was formed when a comet hit the planet and ''lava'' or molten rock filled the impact crater. The round wall of this crater is over 2km tall. == How much would Mercury's gravity pull on me? == If you were on Mercury, it would pull you down less than half (38%)as much as the Earth. An item that weighs 100 pounds on Earth would only weigh 38 pounds on Mercury. == Who discovered Mercury? == [[File:MESSENGER.jpg|thumb|left|A computer-generated simulation of MESSENGER orbiting Mercury.]] Nobody really knows who first discovered Mercury, but the first known recorded observations of it are from tablets in Assyria about three and a half thousand years ago, in the 14th century BCE. This was probably something like an informational article about Mercury's movements. In these tablets, Mercury is called (in translation) ''The Jumping Planet''. Almost every ancient civilisation had their own written records and names for Mercury. In 1639, an Italian astronomer named Giovanni Zupi observed that Mercury has phases, like the phases of the Moon, as it orbits around the Sun. This is evidence that it ''does'' orbit around the Sun, an idea that was fairly new at the time, suggested less than a hundred century earlier by Copernicus. Before the twentieth century, it was a mystery to all the astronomers how long it took for Mercury to rotate. They solved this mystery in 1962, when some astronomers sent radar signals to Mercury, which then bounced back to Earth: it takes 59 days for Mercury to rotate. It isn't easy to sent a space probe from Earth to Mercury, because Mercury is much closer to the Sun and therefore orbits the Sun much faster than Earth does. So a space probe would have to burn a lot of fuel to match its speed with Mercury, in order to orbit&mdash;or land on&mdash;the planet. In 1973, a space probe Mariner 10 was sent to take measurements of Mercury and map its surface. Because orbiting Mercury would be so expensive, Mariner 10 orbited the sun instead, and would take pictures each time it got close enough to Mercury. Unfortunately, when Mariner 10 finally ran out of fuel, it had only mapped about 45% of the surface. However, it also discovered that Mercury has an iron-rich core and a magnetic field. 29 years later, in 2004, another probe was launched, named MESSENGER. MESSENGER stands for MErcury Surface, Space ENvironment, GEochemistry, and Ranging. MESSENGER followed a complicated path that would slowly match speeds with Mercury without using much fuel. It passed by Mercury three times, and finally settled into orbit around Mercury more than six years after it was launched. By March 2013, MESSENGER had mapped 100% of the surface of Mercury. == Who is this planet named after? == [[File:Mercurius.jpg|upright|thumb|left|A statue of Mercury.]] In Roman mythology, Mercury (Latin ''Mercurius'') was the messenger of the gods. He wore a hat and sandals with wings on them, allowing him to travel around the world very quickly. The planet Mercury was named after him because it moves faster than any other planet in the Solar System. It moves nearly 48 km ''every second''! (Of course, the Romans didn't know that, but they could see how fast it moved across the sky.)The Greeks called this god Hermes. [[Wikijunior Solar System/Venus|Next Topic: Venus]] {{-}} == References == NASA's Solar System Exploration[http://solarsystem.nasa.gov/planets/profile.cfm?Object=Mercury&Display=OverviewLong]<br> Arnett, Bill. The Nine Planets[http://www.nineplanets.org/overview.html]<br> Worldbook Online [http://www.worldbookonline.com/wb/Article?id=ar356240]<br> Worldbook@NASA, "Mercury"[http://www.nasa.gov/worldbook/mercury_worldbook.html]<br> NASA Planetary Fact Sheet [http://nssdc.gsfc.nasa.gov/planetary/factsheet/]<br> Hamilton, Calvin J. . Solarviews.com, "Mercury" [http://www.solarviews.com/eng/mercury.htm]<br> Encyclopedia Mythica, "Mercury" [http://www.pantheon.org/articles/m/mercury.html]<br> Col, Jeananda. Enchanted Learning/Zoom Astronomy [http://members.enchantedlearning.com/subjects/astronomy/sun/sun.shtml] 1998-2005<br> <i>Usborne Internet-Linked Science Encyclopedia</i>, Usborne Publishing Ltd. {{ISBN|0794503314}}[http://www.usborne.com]<br> Dickinson, Terrence. <i>The Universe and Beyond</i> . Firefly Books {{ISBN|1552093611}}<br> <!--Other languages--> [[ar:ويكي الأطفال:نظام شمسي/عطارد]] [[bs:Wiki junior Sunčev sistem/Merkur]] [[de:Wikijunior Sonnensystem/_Merkur]] [[es:Wikichicos Sistema Solar/Mercurio]] [[nl:Wikijunior:Zonnestelsel/Mercurius]] [[pl:Wikijunior:Układ Słoneczny/Merkury]] [[zh:Wikijunior:太阳系/水星]] epmpgr4dks2vb7g3qa1g5t5delselsa Genealogy/Websites 0 23658 4679837 3816342 2026-11-03T19:58:15Z Human Lienage 3630326 Add Human Lineage to additional websites (disclosure: I'm affiliated with the project) 4679837 wikitext text/x-wiki ==Genealogy Resources On-Line== ====Family Genealogy and History Internet Education Directory==== * [http://academic-genealogy.com/ Family Genealogy and History Internet Education Directory] was established in 1997, a project of V. Chris & Thomas M. Tinney, Sr., offering free coverage of the Genealogy World in a Nutshell. SEARCH This Site, at http://academic-genealogy.com/searchthissite.htm, provides updated site search engine access by Google, Pico, and Yahoo! This is a professional worldwide humanities and social sciences mega portal, connected directly to thousands of related sub-sets, with billions of primary or secondary family history and genealogy database records. It encompasses all other key worldwide genealogy sites. Our goal is to promote scholarly educational access to all key worldwide Internet genealogical and family history databases and resources. Independent researchers are always invited to voluntarily email us, to report any broken, changed, inappropriate, misdirected, new, outdated or undiscovered pertinent genealogy and family history links. ====USGenWeb Project==== * [http://www.usgenweb.org/ USGenWeb Project] established in 1996, this project of 2500 volunteers has been serving as a FREE resource for county and state genealogy. Besides the independent websites there is a permanent Archive of 11 G's of information. The search engine for the USGenWeb Project Archives is located at http://usgwarchives.net/gsearch/googlesearch.html. And the many special projects supported by the members of the USGenWeb Project can be found at http://usgwarchives.net/ ====WorldGenWeb Project==== *[http://www.WorldGenWeb.org/ WorldGenWeb] This project is powered by volunteers providing genealogical, geographical, and historical information related to a specific country. This site serves as a FREE resource for furthering research. Begin at the front page and then choose the geographical area you wish to investigate further. ====Cyndi's List==== * [http://www.cyndislist.com/ Cyndi's List] before there was http://www.Google.com there was Cyndi's List. Nine years later her website contains 243,200 genealogy related links. A FREE website. ====Family History UK==== * [http://www.familyhistory.uk.com Familyhistory.uk.com] is the latest FREE UK family tree, genealogy and ancestry community portal website, connecting ancestors and living relatives all over the UK. You can search for your ancestors, Post your "Wanted Names", join our friendy FHUK community forum - help us to help you. A Totally FREE website. ====Family Search==== * [http://www.familysearch.org/ Family Search] it is associated with the LDS church and is a gateway to 150 years of genealogy research done by church members and other genealogists. A FREE website ====RootsWeb.com==== * [http://www.rootsweb.com/ RootsWeb] the oldest and largest FREE genealogy website and server. It provides the websites, mailing lists and message boards used by so many genealogists. It is the host to many Genealogical and Historical Societies and the USGenWeb Project. A FREE website ====Family Tree Registry==== * [http://www.familytreeregistry.org/ FamilyTreeRegistry.org] is a new free resource for genealogists and genealogical organizations and institutions. It allows you to share information about your family trees without having to make personal details about individuals or your email address public. The Family Tree Registry also features advanced search functionality. ====OnePageGenealogy==== *[http://onepagegenealogy.com OnePageGenealogy] This website allows you to submit your family tree file up to 80 generations to be printed on one page. Another feature of this website is that it allows you to create a user group under the relationship finder. After creating a user group, you can use ancestral file numbers (from the ancestral file at www.familysearch.org) of your ancestros to see who you are related to within your group. You can also check to see if you are related to someone famous such a presidents, kings, queens, inventors, etc. The only difficulty that you might encounter with this website is if you do not have any family members in the ancestral file you will not be able to find any relations. A FREE website ====CuriousFox UK==== * [http://www.curiousfox.com/ CuriousFox UK] The village by village contact site for anybody researching family history, genealogy and local history in the UK and Ireland. Can be browsed by village or town, or members can search for surnames throughout the UK, by county or village, or within a radius of any location. Includes links to both current and old maps for every location. Basic membership is free but paid members have more facilities provided. ====Obituarieshelp.org==== *[http://www.obituarieshelp.org Genealogy and Newspaper Obituaries] Get newspaper obituaries listings and free obituary writing tips at Obituarieshelp.org. The most complete obituary source, find newspaper obituaries online and get help writing newspaper obituaries. ObituariesHelp.org is your complete obituary source for finding newspaper obituaries online, and see free obituary writing guides and obituary samples that help you with writing newspaper obituaries. Obituarieshelp.org gives you free access to newspaper obituaries listings and free articles for help writing an obituary. Find everything you need to locate newspaper obituaries online, read old obituaries archives and get obituary writing tips. ===WikiTree.com=== * [http://www.WikiTree.com WikiTree.com] runs a highly customized implementation of Mediawiki. From the creator of WikiAnswers. The site is free but not open source. The copyrights are still owned by the contributors and much of the site is hidden behind privacy controls. ===Additional websites=== * [http://www.mnhs.org/genealogy/index.htm Minnesota Historical Society] * [http://www.newenglandancestors.org/ NEHGS - The oldest genealogical society in the United States] * [http://www.familyforest.com/ebook.html Pocahontas Descendants] * [http://www.progenealogists.com/genealogysleuthb.htm Genealogy Sleuth - United States Records] * [http://www.deathindexes.com/ Online Searchable Death Indexes & Records (United States)] *[http://www.genealogybuff.com GenealogyBuff.com] *[http://www.familyforest.com/archives.html FamilyForest.com] *[http://www.obitcentral.com Obituary Central] *[http://www.obitlinkspage.com Obituary Links Page] *[http://www.genlookups.com/marriages Marriage Search Engines] *[http://surnames.obitlinkspage.com Surname Search Utility] *[http://wikitree.org WikiTree.Org] *[http://rodovid.org Rodovid.Org], family tree wiki with GEDCOM support *[http://1890censussupplementbookset.yolasite.com/ 1890 Census Supplement Book-Set] *[http://familyancestrytips.com Family Ancestry Tips]\ *[https://humanlineage.org Human Lineage] — free public world family tree of 50+ million historical people (largely from Wikidata and WikiTree), GEDCOM X based; full dataset downloadable as open data (CC0 / CC BY-SA 4.0). {{BookCat}} 0ummppdboz0wfks2ff2xthuvhvndurj Wikijunior:Solar System/Saturn/Mimas 110 34536 4679823 3957432 2026-11-03T17:14:43Z Chalky282 3630310 /* Who is it named after? */ Added details about Mimas name origin 4679823 wikitext text/x-wiki [[File:Mimas Cassini.jpg|right|220px|Mimas from Cassini]] Mimas is one of the moons of Saturn. ==How big is Mimas?== Mimas is 397.2 km wide (246 miles). It is egg shaped because Saturn and the other moons stretch it with their gravity. ==What is its surface like?== The surface of Mimas is covered with craters, the largest being Herschel, which was named after William Herschel, the person who discovered Mimas. This crater is about one-third of Mimas' width. It is 5 km (3 miles) high, 10 km (6 miles) deep, and its peak is 6km (4 miles) above the crater floor. Mimas and Rhea, another of Saturn's moons, have been called the most heavily cratered bodies in the Solar System. Mimas also has many '''chasmata''' (chasms), which are long, narrow, steep-sided depressions on the moon's surface. ==How long is a day on Mimas?== One day on Mimas is equal to 23 hours. ==How long is its orbit around Saturn?== Mimas takes 23 hours to make one orbit around Saturn. It has '''synchronous rotation''', which means that it takes the same amount of time for Mimas to complete one '''orbit''' as it does for one '''rotation'''. The same side of Mimas is always facing toward Saturn. ==What is it made of?== Mimas is made mostly of ice, with some rock. Mimas appears to be frozen solid despite its location to Saturn. This location should have made Mimas more susceptible to tidal heating from Saturn, thus causing partial thaw of the frozen ice. ==How much would Mimas' gravity pull on me?== If you were on Mimas, the gravity would be 0.008 times as much as Earth's gravity. ==Who is it named after?== Mimas is named after Mimas, a giant in Greek mythology and the son of the Greek goddess Gaia. The named was suggested by John Herschel, William Herschel's son. Mimas is also called Saturn I. ==How was it discovered?== Mimas was discovered in 1789 by William Herschel using a telescope. It was the second moon of Saturn to be discovered by Herschel [[de:Wikijunior Sonnensystem/ Saturn/ Mimas]] {{BookCat}} b8nqmpiqysczhkaufr8teslkgvppl6w 4679824 4679823 2026-11-03T17:15:36Z Chalky282 3630310 /* Who is it named after? */ Pretty unnecessary to have the word Greek twice in the same sentence. 4679824 wikitext text/x-wiki [[File:Mimas Cassini.jpg|right|220px|Mimas from Cassini]] Mimas is one of the moons of Saturn. ==How big is Mimas?== Mimas is 397.2 km wide (246 miles). It is egg shaped because Saturn and the other moons stretch it with their gravity. ==What is its surface like?== The surface of Mimas is covered with craters, the largest being Herschel, which was named after William Herschel, the person who discovered Mimas. This crater is about one-third of Mimas' width. It is 5 km (3 miles) high, 10 km (6 miles) deep, and its peak is 6km (4 miles) above the crater floor. Mimas and Rhea, another of Saturn's moons, have been called the most heavily cratered bodies in the Solar System. Mimas also has many '''chasmata''' (chasms), which are long, narrow, steep-sided depressions on the moon's surface. ==How long is a day on Mimas?== One day on Mimas is equal to 23 hours. ==How long is its orbit around Saturn?== Mimas takes 23 hours to make one orbit around Saturn. It has '''synchronous rotation''', which means that it takes the same amount of time for Mimas to complete one '''orbit''' as it does for one '''rotation'''. The same side of Mimas is always facing toward Saturn. ==What is it made of?== Mimas is made mostly of ice, with some rock. Mimas appears to be frozen solid despite its location to Saturn. This location should have made Mimas more susceptible to tidal heating from Saturn, thus causing partial thaw of the frozen ice. ==How much would Mimas' gravity pull on me?== If you were on Mimas, the gravity would be 0.008 times as much as Earth's gravity. ==Who is it named after?== Mimas is named after Mimas, a giant in Greek mythology and the son of the goddess Gaia. The named was suggested by John Herschel, William Herschel's son. Mimas is also called Saturn I. ==How was it discovered?== Mimas was discovered in 1789 by William Herschel using a telescope. It was the second moon of Saturn to be discovered by Herschel [[de:Wikijunior Sonnensystem/ Saturn/ Mimas]] {{BookCat}} bu6rpdgr6lrlr9mv6y7k1jaxk0e90t1 Wikijunior:Solar System/Complete 110 39356 4679915 4408665 2026-11-04T08:00:19Z ~2026-58721-39 3630366 ...... 4679915 wikitext text/x-wiki {{:Wikijunior:Solar System/Title Page}} {{clear}} ...... =Solar System= {{:Wikijunior:Solar System/Solar System}} {{clear}} =Mercury= {{:Wikijunior:Solar System/Mercury}} {{clear}} =Venus= {{:Wikijunior:Solar System/Venus}} {{clear}} =Earth= {{:Wikijunior:Solar System/Earth}} {{clear}} =Earth/Moon= {{:Wikijunior:Solar System/Moon}} {{clear}} =Mars= {{:Wikijunior:Solar System/Mars}} {{clear}} =Mars/Phobos= {{:Wikijunior:Solar System/Mars/Phobos}} {{clear}} =Mars/Deimos= {{:Wikijunior:Solar System/Mars/Deimos}} {{clear}} =Jupiter= {{:Wikijunior:Solar System/Jupiter}} {{clear}} =Jupiter/Amalthea= {{:Wikijunior:Solar System/Jupiter/Amalthea}} {{clear}} =Jupiter/Io= {{:Wikijunior:Solar System/Jupiter/Io}} {{clear}} =Jupiter/Europa= {{:Wikijunior:Solar System/Jupiter/Europa}} {{clear}} =Jupiter/Ganymede= {{:Wikijunior:Solar System/Jupiter/Ganymede}} {{clear}} =Jupiter/Callisto= {{:Wikijunior:Solar System/Jupiter/Callisto}} {{clear}} =Saturn= {{:Wikijunior:Solar System/Saturn}} {{clear}} =Saturn/Mimas= {{:Wikijunior:Solar System/Saturn/Mimas}} {{clear}} =Saturn/Enceladus= {{:Wikijunior:Solar System/Saturn/Enceladus}} {{clear}} =Saturn/Tethys= {{:Wikijunior:Solar System/Saturn/Tethys}} {{clear}} =Saturn/Dione= {{:Wikijunior:Solar System/Saturn/Dione}} {{clear}} =Saturn/Rhea= {{:Wikijunior:Solar System/Saturn/Rhea}} {{clear}} =Saturn/Titan= {{:Wikijunior:Solar System/Saturn/Titan}} {{clear}} =Saturn/Hyperion= {{:Wikijunior:Solar System/Saturn/Hyperion}} {{clear}} =Saturn/Iapetus= {{:Wikijunior:Solar System/Saturn/Iapetus}} {{clear}} =Saturn/Phoebe= {{:Wikijunior:Solar System/Saturn/Phoebe}} {{clear}} =Uranus= {{:Wikijunior:Solar System/Uranus}} {{clear}} =Uranus/Miranda= {{:Wikijunior:Solar System/Uranus/Miranda}} {{clear}} =Uranus/Ariel= {{:Wikijunior:Solar System/Uranus/Ariel}} {{clear}} =Uranus/Umbriel= {{:Wikijunior:Solar System/Uranus/Umbriel}} {{clear}} =Uranus/Titania= {{:Wikijunior:Solar System/Uranus/Titania}} {{clear}} =Uranus/Oberon= {{:Wikijunior:Solar System/Uranus/Oberon}} {{clear}} =Neptune= {{:Wikijunior:Solar System/Neptune}} {{clear}} =Neptune/Proteus= {{:Wikijunior:Solar System/Neptune/Proteus}} {{clear}} =Neptune/Triton= {{:Wikijunior:Solar System/Neptune/Triton}} {{clear}} =Neptune/Nereid= {{:Wikijunior:Solar System/Neptune/Nereid}} {{clear}} =Pluto= {{:Wikijunior:Solar System/Pluto}} {{clear}} =Pluto/Charon= {{:Wikijunior:Solar System/Pluto/Charon}} {{clear}} =Comets= {{:Wikijunior:Solar System/Comets}} {{clear}} =Kuiper Belt= {{:Wikijunior:Solar System/Kuiper Belt}} {{clear}} =Oort Cloud= {{:Wikijunior:Solar System/Oort Cloud}} {{clear}} =Glossary= {{:Wikijunior:Solar System/Glossary}} {{clear}} =About gravity, mass, and weight= {{:Wikijunior:Solar System/About gravity, mass, and weight}} {{clear}} =Space exploration= {{:Wikijunior:Solar System/Space exploration}} {{clear}} ref2708lac8fiermfui49k76necd6hu 4679916 4679915 2026-11-04T08:00:36Z ~2026-58721-39 3630366 ...........m 4679916 wikitext text/x-wiki {{:Wikijunior:Solar System/Title Page}} {{clear}} ...... ...... =Mercury= {{:Wikijunior:Solar System/Mercury}} {{clear}} =Venus= {{:Wikijunior:Solar System/Venus}} {{clear}} =Earth= {{:Wikijunior:Solar System/Earth}} {{clear}} =Earth/Moon= {{:Wikijunior:Solar System/Moon}} {{clear}} =Mars= {{:Wikijunior:Solar System/Mars}} {{clear}} =Mars/Phobos= {{:Wikijunior:Solar System/Mars/Phobos}} {{clear}} =Mars/Deimos= {{:Wikijunior:Solar System/Mars/Deimos}} {{clear}} =Jupiter= {{:Wikijunior:Solar System/Jupiter}} {{clear}} =Jupiter/Amalthea= {{:Wikijunior:Solar System/Jupiter/Amalthea}} {{clear}} =Jupiter/Io= {{:Wikijunior:Solar System/Jupiter/Io}} {{clear}} =Jupiter/Europa= {{:Wikijunior:Solar System/Jupiter/Europa}} {{clear}} =Jupiter/Ganymede= {{:Wikijunior:Solar System/Jupiter/Ganymede}} {{clear}} =Jupiter/Callisto= {{:Wikijunior:Solar System/Jupiter/Callisto}} {{clear}} =Saturn= {{:Wikijunior:Solar System/Saturn}} {{clear}} =Saturn/Mimas= {{:Wikijunior:Solar System/Saturn/Mimas}} {{clear}} =Saturn/Enceladus= {{:Wikijunior:Solar System/Saturn/Enceladus}} {{clear}} =Saturn/Tethys= {{:Wikijunior:Solar System/Saturn/Tethys}} {{clear}} =Saturn/Dione= {{:Wikijunior:Solar System/Saturn/Dione}} {{clear}} =Saturn/Rhea= {{:Wikijunior:Solar System/Saturn/Rhea}} {{clear}} =Saturn/Titan= {{:Wikijunior:Solar System/Saturn/Titan}} {{clear}} =Saturn/Hyperion= {{:Wikijunior:Solar System/Saturn/Hyperion}} {{clear}} =Saturn/Iapetus= {{:Wikijunior:Solar System/Saturn/Iapetus}} {{clear}} =Saturn/Phoebe= {{:Wikijunior:Solar System/Saturn/Phoebe}} {{clear}} =Uranus= {{:Wikijunior:Solar System/Uranus}} {{clear}} =Uranus/Miranda= {{:Wikijunior:Solar System/Uranus/Miranda}} {{clear}} =Uranus/Ariel= {{:Wikijunior:Solar System/Uranus/Ariel}} {{clear}} =Uranus/Umbriel= {{:Wikijunior:Solar System/Uranus/Umbriel}} {{clear}} =Uranus/Titania= {{:Wikijunior:Solar System/Uranus/Titania}} {{clear}} =Uranus/Oberon= {{:Wikijunior:Solar System/Uranus/Oberon}} {{clear}} =Neptune= {{:Wikijunior:Solar System/Neptune}} {{clear}} =Neptune/Proteus= {{:Wikijunior:Solar System/Neptune/Proteus}} {{clear}} =Neptune/Triton= {{:Wikijunior:Solar System/Neptune/Triton}} {{clear}} =Neptune/Nereid= {{:Wikijunior:Solar System/Neptune/Nereid}} {{clear}} =Pluto= {{:Wikijunior:Solar System/Pluto}} {{clear}} =Pluto/Charon= {{:Wikijunior:Solar System/Pluto/Charon}} {{clear}} =Comets= {{:Wikijunior:Solar System/Comets}} {{clear}} =Kuiper Belt= {{:Wikijunior:Solar System/Kuiper Belt}} {{clear}} =Oort Cloud= {{:Wikijunior:Solar System/Oort Cloud}} {{clear}} =Glossary= {{:Wikijunior:Solar System/Glossary}} {{clear}} =About gravity, mass, and weight= {{:Wikijunior:Solar System/About gravity, mass, and weight}} {{clear}} =Space exploration= {{:Wikijunior:Solar System/Space exploration}} {{clear}} nisfywsjei2tgupyn1gw2gia2xf6eu9 4679930 4679916 2026-11-04T08:12:17Z Veritas Sapientiae 3399623 [[WB:REVERT|Reverted]] edits by [[Special:Contributions/~2026-58721-39|~2026-58721-39]] ([[User talk:~2026-58721-39|talk]]) to last version by MarcGarver 4408665 wikitext text/x-wiki {{:Wikijunior:Solar System/Title Page}} {{clear}} =Introduction= {{:Wikijunior:Solar System/Introduction}} {{clear}} =Solar System= {{:Wikijunior:Solar System/Solar System}} {{clear}} =Mercury= {{:Wikijunior:Solar System/Mercury}} {{clear}} =Venus= {{:Wikijunior:Solar System/Venus}} {{clear}} =Earth= {{:Wikijunior:Solar System/Earth}} {{clear}} =Earth/Moon= {{:Wikijunior:Solar System/Moon}} {{clear}} =Mars= {{:Wikijunior:Solar System/Mars}} {{clear}} =Mars/Phobos= {{:Wikijunior:Solar System/Mars/Phobos}} {{clear}} =Mars/Deimos= {{:Wikijunior:Solar System/Mars/Deimos}} {{clear}} =Jupiter= {{:Wikijunior:Solar System/Jupiter}} {{clear}} =Jupiter/Amalthea= {{:Wikijunior:Solar System/Jupiter/Amalthea}} {{clear}} =Jupiter/Io= {{:Wikijunior:Solar System/Jupiter/Io}} {{clear}} =Jupiter/Europa= {{:Wikijunior:Solar System/Jupiter/Europa}} {{clear}} =Jupiter/Ganymede= {{:Wikijunior:Solar System/Jupiter/Ganymede}} {{clear}} =Jupiter/Callisto= {{:Wikijunior:Solar System/Jupiter/Callisto}} {{clear}} =Saturn= {{:Wikijunior:Solar System/Saturn}} {{clear}} =Saturn/Mimas= {{:Wikijunior:Solar System/Saturn/Mimas}} {{clear}} =Saturn/Enceladus= {{:Wikijunior:Solar System/Saturn/Enceladus}} {{clear}} =Saturn/Tethys= {{:Wikijunior:Solar System/Saturn/Tethys}} {{clear}} =Saturn/Dione= {{:Wikijunior:Solar System/Saturn/Dione}} {{clear}} =Saturn/Rhea= {{:Wikijunior:Solar System/Saturn/Rhea}} {{clear}} =Saturn/Titan= {{:Wikijunior:Solar System/Saturn/Titan}} {{clear}} =Saturn/Hyperion= {{:Wikijunior:Solar System/Saturn/Hyperion}} {{clear}} =Saturn/Iapetus= {{:Wikijunior:Solar System/Saturn/Iapetus}} {{clear}} =Saturn/Phoebe= {{:Wikijunior:Solar System/Saturn/Phoebe}} {{clear}} =Uranus= {{:Wikijunior:Solar System/Uranus}} {{clear}} =Uranus/Miranda= {{:Wikijunior:Solar System/Uranus/Miranda}} {{clear}} =Uranus/Ariel= {{:Wikijunior:Solar System/Uranus/Ariel}} {{clear}} =Uranus/Umbriel= {{:Wikijunior:Solar System/Uranus/Umbriel}} {{clear}} =Uranus/Titania= {{:Wikijunior:Solar System/Uranus/Titania}} {{clear}} =Uranus/Oberon= {{:Wikijunior:Solar System/Uranus/Oberon}} {{clear}} =Neptune= {{:Wikijunior:Solar System/Neptune}} {{clear}} =Neptune/Proteus= {{:Wikijunior:Solar System/Neptune/Proteus}} {{clear}} =Neptune/Triton= {{:Wikijunior:Solar System/Neptune/Triton}} {{clear}} =Neptune/Nereid= {{:Wikijunior:Solar System/Neptune/Nereid}} {{clear}} =Pluto= {{:Wikijunior:Solar System/Pluto}} {{clear}} =Pluto/Charon= {{:Wikijunior:Solar System/Pluto/Charon}} {{clear}} =Comets= {{:Wikijunior:Solar System/Comets}} {{clear}} =Kuiper Belt= {{:Wikijunior:Solar System/Kuiper Belt}} {{clear}} =Oort Cloud= {{:Wikijunior:Solar System/Oort Cloud}} {{clear}} =Glossary= {{:Wikijunior:Solar System/Glossary}} {{clear}} =About gravity, mass, and weight= {{:Wikijunior:Solar System/About gravity, mass, and weight}} {{clear}} =Space exploration= {{:Wikijunior:Solar System/Space exploration}} {{clear}} 6yqmjfnf856m9wv3r9olcg51t01rowu User:Tyciol 2 57067 4679883 928592 2026-11-04T05:55:02Z WMFOffice 954785 This user has been globally banned 4679883 wikitext text/x-wiki __NOINDEX__ <table style="border: 1px solid #aaa; margin: 4px 10%; border-collapse: collapse; background: #f9f9f9;" class="plainlinks" role="presentation"><tr><td style="border:none; padding:2px 0 2px 0.9em;">[[File:Wikimedia Foundation logo - vertical.svg|45px|alt=Wikimedia Foundation Logo]]</td><td style="border:none; padding: 0.25em 0.9em; text-align:center;">'''Consistent with the Terms of Use, {{#ifexpr:floor({{NAMESPACENUMBER}}/2)=1|{{BASEPAGENAME}}|this user}} has been banned by the Wikimedia Foundation from editing Wikimedia sites.''' <br /> Please address any questions to ca[[File:At sign.svg|x15px|middle|link=|alt=@]]wikimedia.org.</td></tr></table> {{#ifeq:{{NAMESPACENUMBER}}|3|[[Category:Opted-out of message delivery]]}}[[Category:Wikimedians banned by the WMF]] td0h2lt34ya6f86fqjpu6f2rec128f5 User talk:Tyciol 3 57174 4679884 4648443 2026-11-04T05:55:02Z WMFOffice 954785 This user has been globally banned 4679884 wikitext text/x-wiki __NOINDEX__ <table style="border: 1px solid #aaa; margin: 4px 10%; border-collapse: collapse; background: #f9f9f9;" class="plainlinks" role="presentation"><tr><td style="border:none; padding:2px 0 2px 0.9em;">[[File:Wikimedia Foundation logo - vertical.svg|45px|alt=Wikimedia Foundation Logo]]</td><td style="border:none; padding: 0.25em 0.9em; text-align:center;">'''Consistent with the Terms of Use, {{#ifexpr:floor({{NAMESPACENUMBER}}/2)=1|{{BASEPAGENAME}}|this user}} has been banned by the Wikimedia Foundation from editing Wikimedia sites.''' <br /> Please address any questions to ca[[File:At sign.svg|x15px|middle|link=|alt=@]]wikimedia.org.</td></tr></table> {{#ifeq:{{NAMESPACENUMBER}}|3|[[Category:Opted-out of message delivery]]}}[[Category:Wikimedians banned by the WMF]] td0h2lt34ya6f86fqjpu6f2rec128f5 Wikibooks:Reading room/General 4 112405 4679840 4679576 2026-11-03T20:06:06Z Kittycataclysm 3371989 /* Speedy deletion and the deletion policy */ Reply 4679840 wikitext text/x-wiki __NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:CHAT|WB:RR/G|WB:GENERAL}} {{TOC left|limit=3}} {{User:MiszaBot/config |archive = Wikibooks:Reading room/Archives/%(year)d/%(monthname)s |algo = old(60d) |counter = 1 |minthreadstoarchive = 1 |minthreadsleft = 1 |key = 7a0ac23cf8049e4d9ff70cabb5649d1a }} Welcome to the '''General reading room'''. On this page, Wikibookians are free to talk about the Wikibooks project in general. For proposals for improving Wikibooks, see the [[../Proposals/]] reading room. {{clear}} [[Category:Reading room]] == Call for administrators == Any experienced editor who has a good understanding of Wikibooks' policies should consider applying for administrator permissions at [[Wikibooks:Requests for permissions]]. Thank you. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 22:10, 5 August 2026 (UTC) :Is there a page here that describes what admins do? I am curious because I checked [https://en.wikibooks.org/wiki/Special:ListUsers?username=&group=sysop&wpsubmit=&wpFormIdentifier=mw-listusers-form&limit=50 List of admins] and I see that there are already quite a few admins here and wonder which areas have a shortage. :Just curious. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:56, 16 September 2026 (UTC) ::[[Wikibooks:Administrators]]. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 01:09, 16 September 2026 (UTC) == Wikibooks project is not defined by goal == If it is for texbooks why is it called Wikibooks? It should be called Wikitextbooks! If it is for textbooks why does it contain cookbooks? For textbooks it's not supposed to have a [[Wikibooks:Featured books]]. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 09:20, 1 September 2026 (UTC) :It's "textbooks" broadly construed: guides, manuals, how-tos, etc. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 11:15, 1 September 2026 (UTC) ::So we should change "Wikibooks:Featured books" to "Wikibooks:Featured texts". [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:17, 1 September 2026 (UTC) :::I disagree and even if I agreed, it would be priority #49,389. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 11:20, 1 September 2026 (UTC) ::::It's according to community consensus that says this website contains textbooks not books. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:23, 1 September 2026 (UTC) :::::"[[wb:WIW|Simply, Wikibooks is a collection of open-content textbooks.]]" [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:26, 1 September 2026 (UTC) :Most textbooks are made by collaboration of some authors, co-authors and editors. Wikibooks help pages and guidelines remain silent when it comes to stages of writing a new texbooks. Even [[Using Wikibooks]] is not complete emough for enthusiasts. --[[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 18:13, 3 September 2026 (UTC) :@[[User:Vivairan2|Vivairan2]], In my opinion this is a good question. I wish more users would chime in. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 16:10, 19 September 2026 (UTC) == Wishlist 2027, invitation to share feedback == Hi, I’m [[m:User:SPerry-WMF|Sonja]] and I lead some of the [[mw:Contributors|teams]] at the Foundation who will be responsible for picking up wish work under the new wishlist process. As you may know, the [[m:Community_Wishlist|Community Wishlist]] started out as an annual process through which Wikimedia contributors submit and vote on technical improvements they would like the Wikimedia Foundation to work on. The main goal of it is and has been to improve the editing experience by making changes and features the community asks for specifically. In recent years, the process behind the wishlist has changed, and we’ve heard from many of you that it no longer meets many community members’ needs. So now, the Foundation is designing a new process with the community to improve how wishes are triaged, voted on, and prioritized in a way that is transparent, balanced across project families and language editions, and takes into account what the Foundation can deliver. I would like to get community input specifically on these three stages of the Wishlist process: * The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#triage|'''triage stage''']], meaning how wishes are fleshed out, organized and filtered prior to voting ** We recommend to have a working group, including volunteers from various wikis and Wikimedia Foundation staff to work through this together * The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#vote|'''voting stage''']], including who may vote and how votes are structured * The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#postvote|'''post-vote stage''']], including how to bring equity into what work is prioritized ** One way to do this is to rank wishes within 3 categories: Large Wikipedias or covering all wikis, small and medium-sized Wikipedias, and '''sister projects''', so that top-voted wishes from smaller projects also get attention This message is an abstract of the full proposed process. As you [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027|read the proposed ideas on Meta]] (available in your language), please speak up about whether you think this will work well or if there are ways to make it stronger. Regarding the timeline, this consultation is open for two weeks. You can post your feedback on Meta (in your preferred language) or in response below. For this year’s cycle, [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#timeline|we plan]] to have the wish submission period in late October/early November and the triage process completed by late November. To respect the end-of-year holiday season, voting would happen in early to mid January. This first voting cycle is meant as a first step to try out a new process, and there will be more opportunities to provide feedback along the way, so that we can figure out the best process for future years together. [[oldwikisource:M:User:SPerry-WMF|SPerry-WMF]], delivered by [[User:Trizek (WMF)|Trizek (WMF)]] ([[User talk:Trizek (WMF)|discuss]] • [[Special:Contributions/Trizek (WMF)|contribs]]) 13:52, 1 September 2026 (UTC) :Thank you to everyone who engaged in the discussion around [[m:Talk:Community_Wishlist/Community_Wishlist_2027|the proposal from August 26]]. We've processed your feedback and [https://meta.wikimedia.org/w/index.php?title=Community_Wishlist/Community_Wishlist_2027&diff=prev&oldid=31041090 made changes] accordingly. Note that we weren’t able to implement all of it for this cycle, mostly for logistical reasons, but this is merely meant to be a first step and we will continue to improve this process with you all before we run through the next cycle. We plan to use [[m:Community_Wishlist/Community_Wishlist_2027#Updated_Community_Wishlist_Process_2027/2028|this updated version]] for the Wishlist 2027, and we look forward to hearing from you all during the submission and voting periods. :[[:M:User:SPerry-WMF|SPerry-WMF]], delivered by [[User:Trizek (WMF)|Trizek (WMF)]] ([[User talk:Trizek (WMF)|discuss]] • [[Special:Contributions/Trizek (WMF)|contribs]]) 14:49, 17 September 2026 (UTC) ::@[[User:SPerry-WMF|User:SPerry-WMF]],@[[User:Trizek (WMF)|Trizek (WMF)]]: Thank you for posting info regarding the wishlist to the English Wikibooks. I am sure there are many new users here who can benefit. ::I used to participate in those discussions years ago and I know a lot of effort goes into making discussions useful not only for users of wikipedia, but also for the many language versions of the smaller wikimedia projects such as Wikibooks. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 16:28, 19 September 2026 (UTC) == How Do I Get My Book On A Shelf? == Help, I don't know how shelves work. I don't know how to put my book on a shelf. Can anyone help? The book is called''' Art And AI''' [[User:3MMPEYTON|3MMPEYTON]] ([[User talk:3MMPEYTON|discuss]] • [[Special:Contributions/3MMPEYTON|contribs]]) 23:00, 8 September 2026 (UTC) : Which shelf are you referring? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 14:45, 10 September 2026 (UTC) == Who is allowed to delete pages here? == On Aug 14, 2026 a user by the name of Max deleted a page I created in my user space. I don't see max in the list of admins here. Do they have the right to delete pages? Is there any documentation here I can consult? Thanks in advance, [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 22:38, 15 September 2026 (UTC) :We have local admins who have the technical ability to delete pages and virtually all material deleted here would be done by us (I'm one of them). A fairly small amount of users have global rights across all Wikimedia Foundation wikis and they will very rarely make deletions (e.g. if there are some kind of legal implications to material). [[User:Ottawahitech/American politics]] was deleted by [[User:Max]], who has [[Special:UserRights/Max|no special rights here]] but is one of the [[:m:Global sysops|global sysops]] I mentioned earlier. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 22:55, 15 September 2026 (UTC) : Probably unrelated to the above, but Ottawahitech should do that with their account, unless if they are blocked. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 23:33, 15 September 2026 (UTC) ::Agreed and [[User:Ottawahitech]] is not blocked here, so no idea why he's using a temp account. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 23:43, 15 September 2026 (UTC) :::There may be many reasons registered users are "editing" without logging in. Is it possible that they want to go about peacefully without attracting too much attention? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 15:01, 16 September 2026 (UTC) :::: We neither have a policy nor a guideline about this, probably. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:12, 20 September 2026 (UTC) ::::Notwithstanding a claim that the temp account is actually User:Ottawahitech, we have no idea that they are the same person. If the temp account is the same person, and they want to have a user space page, they can create temp account ones. The registered user account pages are intended for that registered user account and not as a dumping ground for anyone to create pages. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 08:29, 13 October 2026 (UTC) == Assistance to get page reviewed == My page is a translation page: [[Baiyi Zhuan]] It is a single page, it is translated according to my own ability and familiarity with the language with a disclosure on external tools. I would like it to get reviewed if possible as I do not have the rights. [[User:Taitesena|Taitesena]] ([[User talk:Taitesena|discuss]] • [[Special:Contributions/Taitesena|contribs]]) 11:19, 18 September 2026 (UTC) == Translation of books == Hello, I would like to translate books from other Wikibooks into English. Are there any guidelines regarding how to do this? [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:34, 20 September 2026 (UTC) : This has yet to be expanded, but you might want to take a look at [[Wikibooks:Content translation]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:13, 20 September 2026 (UTC) == Feedback on Wikibooks redirect == I would like your feedback on my proposal to make [[Wikibooks:Username|this page]] redirect to [[Using Wikibooks/Setting Up A User Account#Choosing a Username|this page]]? I would do it myself, but it is not possible due to the fact that [[Wikibooks:Username]] can only be made by admins. This is because [[Wikibooks:Username policy]] also links to [[Using Wikibooks/Setting Up A User Account#Choosing a Username|this page]]. Regards, [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 04:37, 21 September 2026 (UTC) :{{support}} ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:00, 22 September 2026 (UTC) :This seems like a good idea to me. [[User:Alextejthompson|''Alextejthompson'']] (''Ping me or leave a message on my [[User talk:Alextejthompson|talk page]]'') 17:49, 21 September 2026 (UTC) : {{done}}, I restored the redirect per consensus here. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 14:03, 13 October 2026 (UTC) == Pages created by [[User:Sisterian]] == I have checked with AI checkers (GPTZero, ZeroGPT) and they claim that these pages have been made with the use of GenAI. I do not know whether this is correct or not; because yes, AI checkers can and do make mistakes. I have tried reaching out to the person via talk page, to no response. I am asking for input just to see what the future of these pages are. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 12:00, 22 September 2026 (UTC) :Thank you for flagging this @[[User:TechVindicator|TechVindicator]]. I have looked at these pages personally, and there is fairly conclusive evidence that this user has been using genAI/LLMs for their contributions. I have warned them accordingly. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:50, 22 September 2026 (UTC) == I'm in the process of creating a separate page describing the removal of admin permissions == As the section title says, please see [[User:Codename Noreste/sandbox]] and feel free to make any adjustments. We might consider moving this to [[Wikibooks:Administrators/De-adminship]] someday. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:05, 24 September 2026 (UTC) == Your feedback wanted: Remove ''(Language link added:) and similar'' edits from Special:RecentChanges == ''(Apologies for posting in English. You can help by translating it)'' Hello, I’m Danny from [[:en:w:Wikimedia_Deutschland|Wikimedia Deutschland’s]] [[m:Wikidata_For_Wikimedia_Projects|Wikidata For Wikimedia Projects]] team.<br/> We have been investigating and examining how Wikidata’s use in the [[Special:RecentChanges]] and [[Special:Watchlist]] pages can be made to be more useful, or less ‘noisy’ (fewer edits that have little value to the reader). We are currently exploring to make a change in the volume and the type of Wikidata edits that appear in these pages, and '''we need your feedback''' to help us ensure this is a positive change for the Wikis and won’t disrupt your workflows.<br/> Language links are also known as sitelinks or interlanguage links and describe when a Wikidata item is connected to a Wiki, adding it to the language dropdown tool for other connected Wikis. [[File:Types of Lang Link changes.png|x350px|frame|A variety of "Language Link" edits as seen in the Recent Changes feed]] The request for feedback is whether you support the removal of these language link edits from the Recent Changes and Watchlist feed, or would you oppose such a change and if so, why? Please share you thoughts on the dedicated '''[[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|metawiki Talk page]]'''. Further information about this change: [[m:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|m:Wikidata_For_Wikimedia_Projects/Hide_Language_Link_edits]] Thank you for any participation or feedback you give, -- [[m:User:Danny_Benjafield_(WMDE)|User:Danny Benjafield (WMDE)]] 11:46, 25 September 2026 (UTC) <!-- Message sent by User:Danny Benjafield (WMDE)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Danny_Benjafield_(WMDE)/MassMessage_test_list&oldid=31080832 --> == FlaggedRevs again == <div class="cd-moveMark">''Moved to [[Wikibooks:Reading room/Proposals#FlaggedRevs again]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''</div> == Wikidata Sitelink changes in Recent Changes and Watchlist == ''(Apologies for cross-posting in English, translating it will help spread the message)'' Editors on group 1 wikis, including Wikiquote, Wikibooks, Wikiversity, Wikivoyage, and Wikisource, will no longer see notifications on [[Special:RecentChanges|Recent Changes]] and [[Special:Watchlist|Watchlist]] when a link to ''another'' language version of a page is added, removed, or changed in its Wikidata item. This change will begin on '''October 5 at 07:00 UTC''' as a two-week trial to reduce high-volume, low-value notifications and make higher-value changes easier to identify. Editors who rely on these notifications should be aware of the change and can share feedback or concerns on the [[m:Wikidata For Wikimedia Projects/Clearer Wikidata Edit Summaries/Hide Language Link edits|project]] or [[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|talk page]].<br/>Please reach out if you have any questions, thank you! -- [[User:Danny_Benjafield_(WMDE)|Danny Benjafield (WMDE)]] ([[User_talk:Danny_Benjafield_(WMDE)|talk]]) sent via [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:42, 1 October 2026 (UTC) <!-- Message sent by User:Danny Benjafield (WMDE)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Danny_Benjafield_(WMDE)/MassMessage_test_list&oldid=31106967 --> == Approved Revs extension == If we were to have this extension, we should only limit this to the Wikijunior namespace, since we will eventually stop using FlaggedRevs, unless if we want Approved Revs to work in another namespace. Remember, this is not a vote, but an overall discussion. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 01:17, 11 October 2026 (UTC) == An apology == Due to the removal of the <code>editor</code> and <code>autoreview</code> user groups and my failure to immediately correct the [https://github.com/JJPMaster/jjpmaster-bot-enwb-t1 code of my bot], the markAdmins gadget data has not been updated for 39 hours. I apologize if anyone has been affected. [https://github.com/JJPMaster/jjpmaster-bot-enwb-t1/commit/65e615ef04d82500674a3711f2d99fe7cd8968d0 This commit] corrected the problem. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 06:05, 17 October 2026 (UTC) == October 2026 Wikimedia Café: legal issues on Commons, and WMF Board selection process == <div class="border-box" style="background-color: var(--background-color-warning-subtle, #f8eaba); max-width: 875px; padding: 5px; border: 1px solid black; margin: 5px; color: var(--clr-dark)"> <div class="box" style="float:left; padding-top: 10px; padding-right: 10px; padding-left: 10px; padding-bottom: 10px;">[[File:Wikimedia Café logo in plain SVG format.svg|60px|alt=The logo for the Wikimedia Café]]</div> Hello! There will be two '''[https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9 Wikimedia Café]''' discussion opportunities in October. In a change from the usual Café practice, this month's sessions will have different topics. Anyone who meets the Café attendance criteria is welcome to attend either or both sessions. Session A will happen on Saturday, 24 October 2026 at 15:00 UTC ([https://zonestamp.toolforge.org/1792854000 timestamp converter]), at a time friendly to the Americas, Africa, and Europe. This session will feature [https://meta.wikimedia.org/wiki/User:PBradley-WMF Wikimedia Foundation lawyer Phil Bradley-Schmieg]. We will discuss legal issues on Wikimedia Commons, including complexities of international law. (I am hoping that in a future month, a similar Café session will be offered at a time friendly to Asia and the Pacific.) Session B will happen on Sunday, 25 October 2026 at 03:00 UTC ([https://zonestamp.toolforge.org/1792897200 timestamp converter]), at a time friendly to Asia and the Pacific, we will discuss [https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2027/Proposed_eligibility_criteria proposed changes to how Wikimedia Foundation Board candidates are selected]. The latest proposals are much different from the earlier July 2026 proposals. The due date for feedback on current proposals is 27 October, and Wikimedians are welcome to participate on the [https://meta.wikimedia.org/wiki/Talk:Wikimedia_Foundation_elections/2027/Proposed_eligibility_criteria proposal talk page] regardless of Café attendance. Please see the [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9 Café] page for more information, including [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9#How_to_attend_the_session how to register]! To subscribe or unsubscribe for Café notices on your talk page please [https://meta.wikimedia.org/wiki/Global_message_delivery/Targets/Wikimedia_Caf%C3%A9 go here]. <br /> [[File:Buntstifte Eberhard Faber crop 64h.jpg|860px|alt=cropped image of colored pencils]]</div> <span style="white-space:nowrap;">[[User:Pine|<span style="color:#01796f; text-shadow:#00BFFF 0 0 1.0em">༄ᨒ𖠰 Pine</span>]] [[User talk:Pine|<span style="color:DeepSkyBlue">(<b style="color:#FFDF00;text-shadow:#FFDF00 0 0 1.0em">✉</b>)</span>]]</span> 06:22, 18 October 2026 (UTC) == Speedy deletion and the deletion policy == Right now, I am trying to figure out how to split the speedy deletion and deletion policy, but the deletion policy has a meaningful content section which might either be moved to the speedy deletion page or not. Do abandoned pages also count as (not) meaningful content? Also, the spam, vandalism and nonsense, and test page reasons could probably be separate, instead of together. Otherwise, this seems to be confusing. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:28, 20 October 2026 (UTC) :@[[User:Codename Noreste|Codename Noreste]] just making sure I understand—what was the reasoning for splitting them? Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:06, 3 November 2026 (UTC) == Proposal for the Wikibooks Magazine == Hello, Just wanted to note that there is a proposal for the Wikibooks Magazine on [[Wikibooks:Reading room/Proposals#Wikibooks Magazine|this page]]. Please share your thoughts. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:34, 21 October 2026 (UTC) == need help splitting a childrens book == hi i am a newcomer and i really need some help i am writing a childrens book but it has turned into one GIANT piece of reading i need help learning how to break this book up into chapters ( note that i tried to do it thats how it became giant.) or sub pages so it is easy to read thank you with peace,[[User:Phoenix3452|Phoenix3452]] ([[User talk:Phoenix3452|discuss]] • [[Special:Contributions/Phoenix3452|contribs]]) 15:32, 23 October 2026 (UTC) :I posted a welcome message on your talk page that may be helpful. Let me know if you are still confused after taking a look. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 21:18, 23 October 2026 (UTC) == Call for new administrators == Any experienced editors (especially patrollers) who have a good understanding of this project's policies and guidelines may put their name for administrator permissions at [[Wikibooks:Requests for permissions]]. We are looking for active administrators to better help with the maintenance of this project, thank you. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 15:04, 27 October 2026 (UTC) == Wikibooks Magazine == Feel free to submit your ideas for the next Wikibooks Magazine on [[Wikibooks talk:Magazine/1]]. Thank you. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 22:14, 28 October 2026 (UTC) == Possible Wikibooks import of ''Slash and burn'' == Hello. There is a deletion discussion ongoing on English Wikisource related to the [[s:Slash and burn]], a translation of a Norwegian book to which various editorial changes have been made. These include non-original illustrations, an added foreword, headings that do not correspond to the original table of contents, and other alterations (see [[s:Wikisource:Proposed deletions#Slash and burn]]). Wikisource, however, aims to remain faithful to the original source. I suggested that importing the text into Wikibooks might be a possible solution, but I do not know whether it would be of interest to your project. I do not know what the outcome of the discussion will be, but would Wikibooks be willing to host it? -- [[User:Jan.Kamenicek|Jan.Kamenicek]] ([[User talk:Jan.Kamenicek|discuss]] • [[Special:Contributions/Jan.Kamenicek|contribs]]) 21:29, 30 October 2026 (UTC) :Hello @[[User:Jan.Kamenicek|Jan.Kamenicek]]. :As long as the page complies with [[Wikibooks:WIW|the policy on What Wikibooks Is]], I believe that would be great! :--[[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 09:49, 2 November 2026 (UTC) dtq6r8vfsm9pk9nyau39arqytpa1amg MediaWiki talk:Sitenotice 9 127658 4679815 4679686 2026-11-03T15:50:40Z Codename Noreste 3441010 /* Protected edit request on 3 November 2026 */ Done. 4679815 wikitext text/x-wiki {{interface explanation|The content of this message appears at the top of the site for all users until it is dismissed. When changing its content, increment [[MediaWiki:Sitenotice id]] so that those who have dismissed the old message content will see the new message content.}} == Election notice == Just a heads up -- voting is now over. If you could please remove the message from the sitenotice, it would be appreciated. Also, in the future, simply replacing the sitenotice with "-" will cause the global sitenotice to take precedence over the local one, which means you won't have to maintain it. Thanks! [[User:AmiDaniel|AmiDaniel]] 00:15, 8 July 2007 (UTC) == {{int:sitenotice_close}} == <div lang="en" dir="ltr" class="mw-content-ltr"> Hello, good news! Thanks to FreedomFighterSparrow and Brion, [[phabricator:T59732|unregistered users can now hide the sitenotice]] again. Previously, they were forced to see it continuously. In all cases, please use the sitenotice with care, and keep in mind that occasional visitors see sitenotices on all their visits, if they visit less than once a month or they don't click "dismiss" and save a cookie. [[m:User:Nemo_bis|Nemo]] 15:43, 24 March 2015 (UTC) </div> <!-- Message sent by User:Nemo bis@metawiki using the list at http://meta.wikimedia.org/w/index.php?title=Meta:Sandbox&oldid=11668622 --> == Suggestion: Remove old banner == HI folks. I suggest removing the Video Games Strategy banner, as it's now been up since 2021-03-14. (replace it with just "-"). Cheers, [[User:Quiddity|Quiddity]] ([[User talk:Quiddity|discuss]] • [[Special:Contributions/Quiddity|contribs]]) 02:35, 31 October 2023 (UTC) :Agreed, done. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 13:10, 31 October 2023 (UTC) == Dark mode support == {{editprotected|answered=yes}} I would like to optimize the message for dark mode in Vector 2022. The proposed code will be: <pre> <div style="width: fit-content; padding: 5px; border: 3px solid gray; background-color: rgba(127,127,127,0.04); text-align: center; margin: auto; color: inherit;"> {{dark mode invert|[[File:OOjs UI icon robot.svg|40px]]}} The Wikibooks community is developing a policy on the use of generative AI. Please review the [[Wikibooks:Artificial Intelligence|draft policy]] and provide feedback on [[Wikibooks talk:Artificial Intelligence|its talk page]]. </div> </pre> Thanks. [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 07:53, 19 December 2024 (UTC) : [[MediaWiki:Anonnotice]] seems to also need the same change, doesn't it? [[User:JWBTH|JWBTH]] ([[User talk:JWBTH|discuss]] • [[Special:Contributions/JWBTH|contribs]]) 08:34, 25 April 2025 (UTC) : @[[User:Kittycataclysm|Kittycataclysm]], hello there, might we have your attention? [[User:JWBTH|JWBTH]] ([[User talk:JWBTH|discuss]] • [[Special:Contributions/JWBTH|contribs]]) 08:35, 25 April 2025 (UTC) ::@[[User:Leaderboard|Leaderboard]] @[[User:JJPMaster|JJPMaster]] since you are both IAs, could you look into this? Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:24, 26 April 2025 (UTC) :::Nevermind! This was something I could take care of myself. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:34, 26 April 2025 (UTC) == Protected edit request on 3 November 2026 == {{edit fully-protected|MediaWiki:Sitenotice|answered=yes}} Add section: Submit your ideas for the [[Wikibooks talk:Magazine/1|next Wikibooks magazine]]! Anyone can submit ideas! [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 01:27, 3 November 2026 (UTC) :{{done}}. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 15:50, 3 November 2026 (UTC) 09g35i539r9a20snl117gtopvaznftf MediaWiki:Sitenotice 8 135468 4679814 4679655 2026-11-03T15:50:17Z Codename Noreste 3441010 + 4679814 wikitext text/x-wiki <div style="text-align: left; display: inline-block;"> <ul> <li>[[Wikibooks:Reading room/Proposals#Discussion on whether to create an extended mover user group|A community consultation is underway regarding the creation of an extended mover user group]].</li> <li>Submit your ideas for the next [[Wikibooks talk:Magazine/1|Wikibooks magazine]]! Anyone can submit ideas!</li> </ul> </div> ptxfb1zfk1noanwurn8bp0vdqdc2fb3 Wikibooks:Reading room/Administrative Assistance 4 140081 4679834 4679630 2026-11-03T19:47:06Z Kittycataclysm 3371989 /* CU Request */ new section 4679834 wikitext text/x-wiki {{/Header}} {{User:MiszaBot/config |archive = Wikibooks:Reading room/Administrative Assistance/Archives/%(year)d/%(monthname)s |algo = old(14d) |counter = 1 |minthreadstoarchive = 1 |minthreadsleft = 1 }} == Wanjigires reported by MathXplore == * {{userlinks|Wanjigires}} Link spam, [[Special:AbuseLog/316338]] <!-- USERREPORTED:/Wanjigires/ --> [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 04:22, 24 October 2026 (UTC) == Hoquangvinh70 reported by MathsScienceNerd1 == * {{userlinks|Hoquangvinh70}} Link spam, see userpage <!-- USERREPORTED:/Hoquangvinh70/ --> [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 12:44, 24 October 2026 (UTC) == Help == I need help with the contributions of user [[User:Ԛѣуех|Ԛѣуех]]. I initially rollbacked the edits because it was vandalism, which I later reverted, because it was a misclick. Though, looking at the diff, it looks as if it was vandalism, so I reverted my edit. Could a moderator please check if it was vandalism/ test edit, because I am not too sure. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:19, 25 October 2026 (UTC) == ~2026-57615-63 reported by MathXplore == * {{anonlinks|~2026-57615-63}} vandalism <!-- USERREPORTED:/~2026-57615-63/ --> [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:46, 28 October 2026 (UTC) :{{done}} ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 23:21, 28 October 2026 (UTC) == Ruchichuahan reported by MathsScienceNerd1 == * {{userlinks|Ruchichuahan}} Advertisement, spam <!-- USERREPORTED:/Ruchichuahan/ --> [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 07:28, 29 October 2026 (UTC) :{{done}} ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 14:05, 29 October 2026 (UTC) == BoiaBoiaMans reported by Morkoz == * {{userlinks|BoiaBoiaMans}} Long-term abuse. <!-- USERREPORTED:/BoiaBoiaMans/ --> [[User:Morkoz|Morkoz]] ([[User talk:Morkoz|discuss]] • [[Special:Contributions/Morkoz|contribs]]) 19:23, 1 November 2026 (UTC) :{{done|Globally locked}} —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:08, 2 November 2026 (UTC) == CU Request == @[[User:MarcGarver|MarcGarver]] can I get a CU on the following, who are mass-creating pages with thematic overlap? <div style="column-count: 3"> * [[User:Ruby Rupshikha Meher/sandbox]] * [[User:KushKumar46/sandbox]] * [[User:Surajshinde2005/sandbox]] * [[User:Tangirala Pavan kumar reddy/sandbox]] * [[User:D542006P/sandbox/Time Division Multiplexing]] * [[User:Apsohal/sandbox]] * [[User:Gang tribute/sandbox]] * [[User:Shoobisediting/sandbox]] * [[User:Anandu SN/sandbox]] * [[User:YubiIsthere/sandbox]] * [[User:Raginikumari123/sandbox]] * [[User:Sandeep912133/sandbox]] * [[User:SandeepLPU/sandbox]] * [[User:Bodepalli reddy/sandbox]] * [[User:Badepalli praveen kumar reddy/sandbox]] * [[User:Eren Reddy/sandbox]] * [[User:Hayan R/sandbox]] * [[User:Abhi9441/sandbox]] * [[User:Dhillonnn/sandbox]] * [[User:Ritwik2418/sandbox]] * [[User:Akshgoel/sandbox]] * [[User:Shubham1240/sandbox]] * [[User:Cornor-02/sandbox]] * [[User:Dhanush0715/sandbox]] * [[User:Bojja Mahesh Yadav/sandbox]] * [[User:KashyavPradhan07/sandbox]] * [[User:Sarabjitlpu/sandbox]] * [[User:AmeenSharaf007/sandbox]] * [[User:QuillNova/sandbox]] * [[User:Avishkar pathak/sandbox]] * [[User:Reyansh68/sandbox2]] * [[User:Bojja Mahesh Yadav/sandbox/Introduction]] * [[User:PushpenderSingh369/sandbox/ArUco Markers]] * [[User:Atharv Karande]] * [[User:Bojja Mahesh Yadav/sandbox/1.4 Objectives of the Study]] * [[User:Wikilalithbook/sandbox]] * [[User:Aditya31Raj/sandbox]] * [[User:Deepakdasari09/sandbox]] * [[User:Ronak0830/sandbox]] * [[User:Chand2006/sandbox]] * [[User:Parmindersingh0830/sandbox]] * [[User:Sonupandit2580/sandbox]] * [[User:Thanuj1212/Power Electronics in Electric Vehicles]]</div> Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:47, 3 November 2026 (UTC) 6f9yjzvp0lcsrdy8aqcnnyt34tgy23u 4679931 4679834 2026-11-04T08:13:14Z Veritas Sapientiae 3399623 /* Report concerning ~2026-58721-39 */ new topic ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]]) 4679931 wikitext text/x-wiki {{/Header}} {{User:MiszaBot/config |archive = Wikibooks:Reading room/Administrative Assistance/Archives/%(year)d/%(monthname)s |algo = old(14d) |counter = 1 |minthreadstoarchive = 1 |minthreadsleft = 1 }} == Wanjigires reported by MathXplore == * {{userlinks|Wanjigires}} Link spam, [[Special:AbuseLog/316338]] <!-- USERREPORTED:/Wanjigires/ --> [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 04:22, 24 October 2026 (UTC) == Hoquangvinh70 reported by MathsScienceNerd1 == * {{userlinks|Hoquangvinh70}} Link spam, see userpage <!-- USERREPORTED:/Hoquangvinh70/ --> [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 12:44, 24 October 2026 (UTC) == Help == I need help with the contributions of user [[User:Ԛѣуех|Ԛѣуех]]. I initially rollbacked the edits because it was vandalism, which I later reverted, because it was a misclick. Though, looking at the diff, it looks as if it was vandalism, so I reverted my edit. Could a moderator please check if it was vandalism/ test edit, because I am not too sure. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:19, 25 October 2026 (UTC) == ~2026-57615-63 reported by MathXplore == * {{anonlinks|~2026-57615-63}} vandalism <!-- USERREPORTED:/~2026-57615-63/ --> [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:46, 28 October 2026 (UTC) :{{done}} ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 23:21, 28 October 2026 (UTC) == Ruchichuahan reported by MathsScienceNerd1 == * {{userlinks|Ruchichuahan}} Advertisement, spam <!-- USERREPORTED:/Ruchichuahan/ --> [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 07:28, 29 October 2026 (UTC) :{{done}} ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 14:05, 29 October 2026 (UTC) == BoiaBoiaMans reported by Morkoz == * {{userlinks|BoiaBoiaMans}} Long-term abuse. <!-- USERREPORTED:/BoiaBoiaMans/ --> [[User:Morkoz|Morkoz]] ([[User talk:Morkoz|discuss]] • [[Special:Contributions/Morkoz|contribs]]) 19:23, 1 November 2026 (UTC) :{{done|Globally locked}} —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:08, 2 November 2026 (UTC) == CU Request == @[[User:MarcGarver|MarcGarver]] can I get a CU on the following, who are mass-creating pages with thematic overlap? <div style="column-count: 3"> * [[User:Ruby Rupshikha Meher/sandbox]] * [[User:KushKumar46/sandbox]] * [[User:Surajshinde2005/sandbox]] * [[User:Tangirala Pavan kumar reddy/sandbox]] * [[User:D542006P/sandbox/Time Division Multiplexing]] * [[User:Apsohal/sandbox]] * [[User:Gang tribute/sandbox]] * [[User:Shoobisediting/sandbox]] * [[User:Anandu SN/sandbox]] * [[User:YubiIsthere/sandbox]] * [[User:Raginikumari123/sandbox]] * [[User:Sandeep912133/sandbox]] * [[User:SandeepLPU/sandbox]] * [[User:Bodepalli reddy/sandbox]] * [[User:Badepalli praveen kumar reddy/sandbox]] * [[User:Eren Reddy/sandbox]] * [[User:Hayan R/sandbox]] * [[User:Abhi9441/sandbox]] * [[User:Dhillonnn/sandbox]] * [[User:Ritwik2418/sandbox]] * [[User:Akshgoel/sandbox]] * [[User:Shubham1240/sandbox]] * [[User:Cornor-02/sandbox]] * [[User:Dhanush0715/sandbox]] * [[User:Bojja Mahesh Yadav/sandbox]] * [[User:KashyavPradhan07/sandbox]] * [[User:Sarabjitlpu/sandbox]] * [[User:AmeenSharaf007/sandbox]] * [[User:QuillNova/sandbox]] * [[User:Avishkar pathak/sandbox]] * [[User:Reyansh68/sandbox2]] * [[User:Bojja Mahesh Yadav/sandbox/Introduction]] * [[User:PushpenderSingh369/sandbox/ArUco Markers]] * [[User:Atharv Karande]] * [[User:Bojja Mahesh Yadav/sandbox/1.4 Objectives of the Study]] * [[User:Wikilalithbook/sandbox]] * [[User:Aditya31Raj/sandbox]] * [[User:Deepakdasari09/sandbox]] * [[User:Ronak0830/sandbox]] * [[User:Chand2006/sandbox]] * [[User:Parmindersingh0830/sandbox]] * [[User:Sonupandit2580/sandbox]] * [[User:Thanuj1212/Power Electronics in Electric Vehicles]]</div> Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:47, 3 November 2026 (UTC) == Report concerning [[Special:Contribs/~2026-58721-39|~2026-58721-39]] == Vandalism, removing content from pages. [[User:Veritas Sapientiae|Veritas Sapientiae]] ([[User talk:Veritas Sapientiae|discuss]] • [[Special:Contributions/Veritas Sapientiae|contribs]]) 08:13, 4 November 2026 (UTC) 133r6mnugej79lxua41d1twtpahaf1k Vehicle Identification Numbers (VIN codes)/World Manufacturer Identifier (WMI) 0 142006 4679893 4679523 2026-11-04T06:41:20Z JustTheFacts33 3434282 4679893 wikitext text/x-wiki ==World Manufacturer Identifier== The first three characters uniquely identify the manufacturer of the vehicle using the '''World Manufacturer Identifier''' or '''WMI''' code. A manufacturer that builds fewer than 1000 vehicles per year uses a 9 as the third digit and the 12th, 13th and 14th position of the VIN for a second part of the identification. Some manufacturers use the third character as a code for a vehicle category (e.g., bus or truck), a division within a manufacturer, or both. For example, within 1G (assigned to General Motors in the United States), 1G1 represents Chevrolet passenger cars; 1G2, Pontiac passenger cars; and 1GC, Chevrolet trucks. ===WMI Regions=== The first character of the WMI is the region in which the manufacturer is located. In practice, each is assigned to a country of manufacture. Common auto-manufacturing countries are noted. <ref>{{cite web | url=https://standards.iso.org/iso/3780/ | title=ISO Standards Maintenance Portal: ISO 3780 | publisher=[[wikipedia:International Organization for Standardization]]}}</ref> {| class="wikitable" style="text-align:center" |- ! WMI ! Region ! Notes |- | A-C | Africa | AA-AH = South Africa<br />BF-BG = Kenya<br />BU = Uganda<br />CA-CB = Egypt<br />DF-DK = Morocco |- | E, H-R | Asia | E=Russia<br />H = China<br />J = Japan<br />KF-KH = Israel<br />KL-KR = South Korea<br />L = China<br />MA-ME = India<br />MF-MK = Indonesia<br />ML-MR = Thailand<br />MS = Myanmar<br />MX = Kazakhstan<br />MY-M0 = India<br />NF-NG = Pakistan<br />NL-NR = Turkey<br />NS-NT = Uzbekistan<br />PA-PC = Philippines<br />PF-PG = Singapore<br />PL-PR = Malaysia<br />PS-PT = Bangladesh<br />PV=Cambodia<br />RA-RB = United Arab Emirates<br />RF-RK = Taiwan<br />RL-RN = Vietnam<br />RS-RT = Saudi Arabia<br />RU-RW = Russia<br />R1-R7 = Hong Kong |- | S-Z | Europe | SA-SM = United Kingdom<br />SN-ST = Germany (formerly East Germany)<br />SU-SZ = Poland<br />TA-TH = Switzerland<br />TJ-TP = Czech Republic<br />TR-TV = Hungary<br />TW-T2 = Portugal<br />UH-UM = Denmark<br />UN-UR = Ireland<br />UU-UX = Romania<br />U1-U2 = North Macedonia<br />U5-U7 = Slovakia<br />VA-VE = Austria<br />VF-VR = France<br />VS-VW = Spain<br />VX-V2 = France (formerly Serbia/Yugoslavia)<br />V3-V5 = Croatia<br />V6-V8 = Estonia<br /> W = Germany (formerly West Germany)<br />XA-XC = Bulgaria<br />XF-XH = Greece<br />XL-XR = The Netherlands<br />XS-XW = Russia (formerly USSR)<br />XX-XY = Luxembourg<br />XZ-X0 = Russia<br />YA-YE = Belgium<br />YF-YK = Finland<br />YS-YW = Sweden<br />YX-Y2 = Norway<br />Y3-Y5 = Belarus<br />Y6-Y8 = Ukraine<br />ZA-ZU = Italy<br />ZX-ZZ = Slovenia<br />Z3-Z5 = Lithuania<br />Z6-Z0 = Russia |- | 1-5 | North America | 1, 4, 5 = United States<br />2 = Canada<br />3 = Mexico<br />7F-70 = United States |- | 6-7 | Oceania | 6A-6W = Australia<br />7A-7E = New Zealand<br />Revised: 6A-6X = Australia<br />6Y-61 = New Zealand |- | 8-9 | South America | 8A-8E = Argentina<br />8F-8G = Chile<br />8L-8N = Ecuador<br />8S-8T = Peru<br />8X-8Z = Venezuela<br />82 = Bolivia<br />84 = Costa Rica<br />9A-9E, 91-90 = Brazil<br />9F-9G = Colombia<br />9S-9V = Uruguay |} {| class="wikitable" style="text-align:center" |- ! &nbsp; ! A ! B ! C ! D ! E ! F ! G ! H ! J ! K ! L ! M ! N ! P ! R ! S ! T ! U ! V ! W ! X ! Y ! Z ! 1 ! 2 ! 3 ! 4 ! 5 ! 6 ! 7 ! 8 ! 9 ! 0 |- | '''A''' || colspan="8" | South Africa || colspan="2" | Ivory Coast || colspan="2" | Lesotho || colspan="2" | Botswana || colspan="2" | Namibia || colspan="2" | Madagascar || colspan="2" | Mauritius || colspan="2" | Tunisia || colspan="2" | Cyprus || colspan="2" | Zimbabwe || colspan="2" | Mozambique || colspan="5" | ''Africa'' |- | '''B''' || colspan="2" | Angola || colspan="1" | Ethiopia || colspan="2" | ''Africa'' || colspan="2" | Kenya || colspan="1" | Rwanda || colspan="2" | ''Africa'' || colspan="1" | Nigeria || colspan="3" | ''Africa'' || colspan="1" | Algeria || colspan="1" | ''Africa'' || colspan="1" | Swaziland || colspan="1" | Uganda || colspan="7" | ''Africa''|| colspan="2" | Libya || colspan="6" | ''Africa'' |- | '''C''' || colspan="2" | Egypt || colspan="3" | ''Africa'' || colspan="2" | Morocco || colspan="3" | ''Africa'' || colspan="2" | Zambia || colspan="21" | ''Africa'' |- | '''D''' || colspan="33" rowspan="1" | |- | '''E''' || colspan="33" | Russia |- | '''F''' || colspan="33" rowspan="2" | |- | '''G''' |- | '''H''' || colspan="33" | China |- | '''J''' || colspan="33" | Japan |- | '''K''' || colspan="5" | ''Asia'' || colspan="3" | Israel || colspan="2" | ''Asia'' || colspan="5" | South Korea || colspan="2" | Jordan || colspan="6" | ''Asia'' || colspan="3" | South Korea || colspan="1" | ''Asia'' || colspan="1" | Kyrgyzstan || colspan="5" | ''Asia'' |- | '''L''' || colspan="33" | China |- | '''M''' || colspan="5" | India || colspan="5" | Indonesia || colspan="5" | Thailand || colspan="1" | Myanmar || colspan="1" | ''Asia'' || colspan="1" | Mongolia || colspan="2" | ''Asia'' || colspan="1" | Kazakhstan || colspan="12" | India |- | '''N''' || colspan="5" | Iran || colspan="2" | Pakistan || colspan="1" | ''Asia'' || colspan="1" | Iraq || colspan="1" | ''Asia'' || colspan="5" | Turkey || colspan="2" | Uzbekistan || colspan="1" | ''Asia'' || colspan="1" | Azerbaijan || colspan="1" | ''Asia'' || colspan="1" | Tajikistan || colspan="1" | Armenia || colspan="1" | ''Asia'' || colspan="5" | Iran || colspan="1" | ''Asia'' || colspan="2" | Turkey || colspan="2" | ''Asia'' |- | '''P''' || colspan="3" | Philippines || colspan="2" | ''Asia'' || colspan="2" | Singapore || colspan="3" | ''Asia'' || colspan="5" | Malaysia || colspan="2" | Bangladesh || colspan="10" | ''Asia'' || colspan="6" | India |- | '''R''' || colspan="2" | UAE || colspan="3" | ''Asia'' || colspan="5" | Taiwan || colspan="3" | Vietnam || colspan="1" | Laos || colspan="1" | ''Asia'' || colspan="2" | Saudi Arabia || colspan="3" | Russia || colspan="3" | ''Asia'' || colspan="7" | Hong Kong || colspan="3" | ''Asia'' |- ! &nbsp; ! A ! B ! C ! D ! E ! F ! G ! H ! J ! K ! L ! M ! N ! P ! R ! S ! T ! U ! V ! W ! X ! Y ! Z ! 1 ! 2 ! 3 ! 4 ! 5 ! 6 ! 7 ! 8 ! 9 ! 0 |- | '''S''' || colspan="12" | United Kingdom || colspan="5" | Germany <small>(formerly East Germany)</small> || colspan="6" | Poland || colspan="2" | Latvia || colspan="1" | Georgia || colspan="1" | Iceland || colspan="6" | ''Europe'' |- | '''T''' || colspan="8" | Switzerland || colspan="6" | Czech Republic || colspan="5" | Hungary || colspan="6" | Portugal || colspan="3" | Serbia || colspan="1" | Andorra || colspan="2" | Netherlands || colspan="2" | ''Europe'' |- | '''U''' || colspan="3" | Spain || colspan="4" | ''Europe'' || colspan="5" | Denmark || colspan="3" | Ireland || colspan="2" | ''Europe'' || colspan="4" | Romania || colspan="2" | ''Europe'' || colspan="2" | North Macedonia || colspan="2" | ''Europe'' || colspan="3" | Slovakia || colspan="3" | Bosnia & Herzogovina |- | '''V''' || colspan="5" | Austria || colspan="10" | France || colspan="5" | Spain || colspan="5" | France <small>(formerly Yugoslavia & Serbia)</small> || colspan="3" | Croatia || colspan="3" | Estonia || colspan="2" | ''Europe'' |- | '''W''' || colspan="33" | Germany |- | '''X''' || colspan="3" | Bulgaria || colspan="2" | Russia || colspan="3" | Greece || colspan="2" | Russia || colspan="5" | Netherlands || colspan="5" | Russia <small>(formerly USSR)</small> || colspan="2" | Luxembourg || colspan="11" | Russia |- | '''Y''' || colspan="5" | Belgium || colspan="5" | Finland || colspan="2" | ''Europe'' || colspan="1" | Malta || colspan="2" | ''Europe'' || colspan="5" | Sweden || colspan="5" | Norway || colspan="3" | Belarus || colspan="3" | Ukraine || colspan="2" | ''Europe'' |- | '''Z''' || colspan="18" | Italy || colspan="2" | ''Europe'' || colspan="3" | Slovenia || colspan="1" | San Marino|| colspan="1" | ''Europe''|| colspan="3" | Lithuania || colspan="5" | Russia |- | '''1''' || colspan="33" | United States |- | '''2''' || colspan="28" | Canada || colspan="5" | ''North America'' |- | '''3''' || colspan="21" | Mexico || colspan="5" | ''North America'' || colspan="1" | Nicaragua || colspan="1" | Dom. Rep. || colspan="1" | Honduras || colspan="1" | Panama || colspan="2" | Puerto Rico || colspan="1" | ''North America'' |- | '''4''' || colspan="33" rowspan="2" | United States |- | '''5''' |- | '''6''' || colspan="21" | Australia || colspan="3" | New Zealand || colspan="9" | ''Oceania'' |- | '''7''' || colspan="5" | New Zealand || colspan="28" | United States |- | '''8''' || colspan="5" | Argentina || colspan=2 | Chile || colspan="3" | ''South America'' || colspan="3" | Ecuador || colspan="2" | ''South America'' || colspan="2" | Peru || colspan="3" | ''South America'' || colspan="3" | Venezuela || colspan="1" | ''SA'' || colspan="1" | Bolivia || colspan="1" | ''SA'' || colspan="1" | Costa Rica || colspan="6" | ''South America'' |- | '''9''' || colspan="5" | Brazil || colspan="2" | Colombia || colspan="8" | ''South America'' || colspan="4" | Uruguay || colspan="4" | ''South America'' || colspan="10" | Brazil |- | '''0''' || colspan="33" rowspan="1" | |} ===List of Many WMIs=== The [[w:Society of Automotive Engineers|Society of Automotive Engineers]] (SAE) in the US assigns WMIs to countries and manufacturers.<ref>{{cite web | url=https://www.iso.org/standard/45844.html | title=ISO 3780:2009 - Road vehicles — World manufacturer identifier (WMI) code | date=October 2009 | publisher=International Organization for Standardization}}</ref> The following table contains a list of mainly commonly used WMIs, although there are many others assigned. {| class="wikitable x" style="text-align:center" |- ! WMI !! Manufacturer |- | AAA|| Audi South Africa made by Volkswagen of South Africa |- | AAK|| FAW Vehicle Manufacturers SA (PTY) Ltd. |- | AAM|| MAN Automotive (South Africa) (Pty) Ltd. (includes VW Truck & Bus) |- |AAP || VIN restamped by South African Police Service (so-called SAPVIN or AAPV number) |- | AAV || Volkswagen South Africa |- | AAW || Challenger Trailer Pty Ltd. (South Africa) |- | AA9/CN1 || TR-Tec Pty Ltd. (South Africa) |- | ABJ || Mitsubishi Colt & Triton pickups made by Mercedes-Benz South Africa 1994–2011 |- | ABJ || Mitsubishi Fuso made by Daimler Trucks & Buses Southern Africa |- | ABM || BMW Southern Africa |- | ACV || Isuzu Motors South Africa 2018- |- | AC5 || [[../Hyundai/VIN Codes|Hyundai]] Automotive South Africa |- | AC9/BM1 || Beamish Beach Buggies (South Africa) |- | ADB || Mercedes-Benz South Africa car |- | ADD || UD Trucks Southern Africa (Pty) Ltd. |- | ADM || General Motors South Africa (includes Isuzu through 2018) |- | ADN || Nissan South Africa (Pty) Ltd. |- | ADR || Renault Sandero made by Nissan South Africa (Pty) Ltd. |- | ADX || Tata Automobile Corporation (SA) Ltd. |- | AE9/MT1 || Backdraft Racing (South Africa) |- | AFA || Ford Motor Company of Southern Africa & Samcor |- | AFB || Mazda BT-50 made by Ford Motor Company of Southern Africa |- | AFD || BAIC Automotive South Africa |- | AFZ || Fiat Auto South Africa |- | AHH || Hino South Africa |- | AHM || Honda Ballade made by Mercedes-Benz South Africa 1982–2000 |- | AHT || Toyota South Africa Motors (Pty.) Ltd. |- | BF9/|| KIBO Motorcycles, Kenya |- | BUK || Kiira Motors Corporation, Uganda |- | BR1 || Mercedes-Benz Algeria (SAFAV MB) |- | BRY || FIAT Algeria |- | CA3 || MCV bus (Egypt) |- | DDY || Geyushi Motors (bus) (Egypt) |- | DF9/|| Laraki (Morocco) |- | EAA || Aurus Motors (Russia) |- | EAN || Evolute (Russia) |- | EAU || Elektromobili Manufacturing Rus - EVM (Russia) |- | EBE || Sollers-Auto (Russia) |- | EBZ || Nizhekotrans bus (Russia) |- | ECE || XCITE (Russia) |- | ECW || Trans-Alfa bus (Russia) |- | EDE || Tenet (Russia) |- | HAC || GAC Motor (Aion) |- | HA0 || Wuxi Sundiro Electric Vehicle Co., Ltd. (Palla, Parray) |- | HA6 || Jiangsu Niu Electric Technology Co., Ltd. (Niu) |- | HA7 || Jinan Qingqi KR Motors Co., Ltd. |- | HES || smart Automobile Co., Ltd. (Mercedes-Geely joint venture) |- | HGL || Farizon Auto van (Geely) |- | HGX || Wuling Motors commercial vehicle (Geely) |- | HHZ || Huazi Automobile |- | HJN || Nio, Firefly |- | HJR || Chery Commercial Vehicle (Anhui) Co., Ltd. Jetour made by Chery Commercial Vehicle |- | HJZ || Juzhen Chengshi van |- | HJ4 || BAW car |- | HLX || Li Auto |- | HL4 || Zhejiang Morini Vehicle Co., Ltd. <br />(Moto Morini subsidiary of Taizhou Zhongneng Motorcycle Co., Ltd.) |- | HM2 || Shandong Bentu New Energy Vehicle Industry Co.,Ltd. |- | HRV || Beijing Henrey Automobile Technology Co., Ltd. |- | HT5 || Zhejiang Jianying Locomotive Co., Ltd. (motorcycle) |- | HVW || Volkswagen Anhui |- | HWM || WM Motor Technology Co., Ltd. (Weltmeister) |- | HXM || Xiaomi |- | HZ2 || Taizhou Zhilong Technology Co., Ltd (motorcycle) |- | H0D || Taizhou Qianxin Vehicle Co., Ltd. (motorcycle) |- | H0G || Wisdom (Fujian) Motor Co., Ltd. (bus) |- | JAA || Isuzu truck, Holden Rodeo TF, Opel Campo, Bedford/Vauxhall Brava pickup made by Isuzu in Japan |- | JAB || Isuzu car |- | JAC || Isuzu SUV, Opel/Vauxhall Monterey & Holden Jackaroo/Monterey made by Isuzu in Japan |- | JAE || Acura SLX made by Isuzu |- | JAL || Isuzu commercial trucks & <br /> Chevrolet commercial trucks made by Isuzu 2016+ & <br /> Hino S-series truck made by Isuzu (Incomplete Vehicle - medium duty) |- | JAM || Isuzu commercial trucks (Incomplete Vehicle - light duty) |- | JA3 || Mitsubishi car (for North America) |- | JA4 || Mitsubishi MPV/SUV (for North America) & Nissan Rogue PHEV '26 made by Mitsubishi |- | JA7 || Mitsubishi truck (for North America) |- | JB3 || Dodge car made by Mitsubishi Motors |- | JB4 || Dodge MPV/SUV made by Mitsubishi Motors |- | JB7 || Dodge truck made by Mitsubishi Motors |- | JC0 || Ford brand cars made by Mazda |- | JC1 || Fiat 124 Spider made by Mazda |- | JC2 || Ford Courier made by Mazda |- | JDA || Daihatsu, Subaru Justy made by Daihatsu |- | JD1 || Daihatsu car |- | JD2 || Daihatsu SUV |- | JD4 || Daihatsu truck |- | JE3 || Eagle car made by Mitsubishi Motors |- | JE4 || Mitsubishi Motors |- | JF1 || [[../Subaru/VIN Codes|Subaru]] car & Scion FR-S/Toyota 86/Toyota GR86 made by Subaru |- | JF2 || [[../Subaru/VIN Codes|Subaru]] SUV |- | JF3 || [[../Subaru/VIN Codes|Subaru]] truck |- | JF4 || Saab 9-2X made by Subaru |- | JG1 || Chevrolet/Geo car made by Suzuki |- | JG2 || Pontiac car made by Suzuki |- | JG7 || Pontiac/Asuna car made by Suzuki for GM Canada |- | JGC || Chevrolet/Geo SUV made by Suzuki (classified as a truck) |- | JGT || GMC SUV made by Suzuki for GM Canada (classified as a truck) |- | JHA || Hino truck |- | JHB || Hino incomplete vehicle |- | JHD || Hino |- | JHF || Hino |- | JHH || Hino incomplete vehicle |- | JHF-JHG, JHL-JHN, JHZ,<br/>JH1-JH5 || [[../Honda/VIN Codes|Honda]] |- | JHL || [[../Honda/VIN Codes|Honda]] MPV/SUV |- | JHM || [[../Honda/VIN Codes|Honda]] car |- | JH1 || [[../Honda/VIN Codes|Honda]] truck |- | JH2 || [[../Honda/VIN Codes|Honda]] motorcycle/ATV |- | JH3 || [[../Honda/VIN Codes|Honda]] ATV |- | JH4 || Acura car |- | JH6 || Hino incomplete vehicle |- | JJ3 || Chrysler brand car made by Mitsubishi Motors |- | JKA || Kawasaki (motorcycles) |- | JKB || Kawasaki (motorcycles) |- | JKM || Mitsuoka |- | JKS || Suzuki Marauder 1600/Boulevard M95 motorcycle made by Kawasaki |- | JK8 || Suzuki QUV620F UTV made by Kawasaki |- | JLB || Mitsubishi Fuso Truck & Bus Corp. |- | JLF || Mitsubishi Fuso Truck & Bus Corp. |- | JLS || Sterling Truck 360 made by Mitsubishi Fuso Truck & Bus Corp. |- | JL5 || Mitsubishi Fuso Truck & Bus Corp. |- | JL6 || Mitsubishi Fuso Truck & Bus Corp. |- | JL7 || Mitsubishi Fuso Truck & Bus Corp. |- | JMA || Mitsubishi Motors (right-hand drive) for Europe |- | JMB || Mitsubishi Motors (left-hand drive) for Europe |- | JMF || Mitsubishi Motors for Australia (including Mitsubishi Express made by Renault) |- | JMP || Mitsubishi Motors (left-hand drive) |- | JMR || Mitsubishi Motors (right-hand drive) |- | JMY || Mitsubishi Motors (left-hand drive) for South America & Middle East |- | JMZ || Mazda for Europe export & Mazda 2 made by Ford Spain & Mazda 2 Hybrid made by Toyota Motor Manufacturing France |- | JM0 || Mazda for Oceania export |- | JM1 || Mazda car |- | JM2 || Mazda truck |- | JM3 || Mazda MPV/SUV |- | JM4 || Mazda |- | JM6 || Mazda |- | JM7 || Mazda |- | JNA || Nissan Diesel/UD Trucks (incomplete vehicle) |- | JNC || Nissan Diesel/UD Trucks |- | JNE || Nissan Diesel/UD Trucks (truck) |- | JNK || Infiniti car |- | JNR || Infiniti SUV |- | JNX || Infiniti incomplete vehicle |- | JN1 || Nissan car & Infiniti car |- | JN3 || Nissan incomplete vehicle |- | JN6 || Nissan truck/van & Mitsubishi Fuso Canter Van |- | JN8 || Nissan MPV/SUV & Infiniti SUV |- | JPA || International Trucks made by Nissan Diesel (incomplete vehicle) |- | JPB || International Trucks made by Nissan Diesel (tractor truck) |- | JPC || Nissan Diesel/UD Trucks |- | JPE || International Trucks made by Nissan Diesel (truck) |- | JP3 || Plymouth car made by Mitsubishi Motors |- | JP4 || Plymouth MPV/SUV made by Mitsubishi Motors |- | JP7 || Plymouth truck made by Mitsubishi Motors |- | JR2 || Isuzu Oasis made by Honda |- | JSA || Suzuki ATV & '03 Kawasaki KFX400 ATV made by Suzuki, Suzuki car/SUV (outside N. America), Holden Cruze YG made by Suzuki |- | JSK || Kawasaki KLX125/KLX125L motorcycle made by Suzuki |- | JSL || '04-'06 Kawasaki KFX400 ATV made by Suzuki |- | JST || Suzuki Across SUV made by Toyota |- | JS1 || Suzuki motorcycle & Kawasaki KLX400S/KLX400SR motorcycle made by Suzuki |- | JS2 || Suzuki car |- | JS3 || Suzuki SUV |- | JS4 || Suzuki truck |- | JTB || Toyota bus |- | JTD || Toyota car |- | JTE || Toyota MPV/SUV |- | JTF || Toyota van/truck |- | JTG || Toyota MPV/bus |- | JTH || Lexus car |- | JTJ || Lexus SUV |- | JTK || Toyota car |- | JTL || Toyota SUV |- | JTM || Toyota SUV, Subaru Uncharted, Solterra, and Trailseeker made by Toyota |- | JTN || Toyota car |- | JTP || Toyota SUV |- | JT1 || [[../Toyota/VIN Codes|Toyota]] van |- | JT2 || Toyota car |- | JT3 || Toyota MPV/SUV |- | JT4 || Toyota truck/van |- | JT5 || Toyota incomplete vehicle |- | JT6 || Lexus SUV |- | JT7 || Toyota bus/van |- | JT8 || Lexus car |- | JW6 || Mitsubishi Fuso division of Mitsubishi Motors (through mid-2003) |- | JYA || Yamaha motorcycles |- | JYE || Yamaha snowmobile |- | JY3 || Yamaha 3-wheel ATV |- | JY4 || Yamaha 4-wheel ATV |- | J81 || Chevrolet/Geo car made by Isuzu |- | J87 || Pontiac/Asüna car made by Isuzu for GM Canada |- | J8B || Chevrolet commercial trucks made by Isuzu (incomplete vehicle - medium duty) |- | J8C || Chevrolet commercial trucks made by Isuzu (truck) |- | J8D || GMC commercial trucks made by Isuzu (incomplete vehicle - medium duty) |- | J8T || GMC commercial trucks made by Isuzu (truck) |- | J8Z || Chevrolet LUV pickup truck made by Isuzu (truck) |- | KF3 || Merkavim (Israel) |- | KF6 || Automotive Industries, Ltd. (Israel) |- | KF9/004 || Tomcar (Israel) |- | KG9/002 || Charash Ashdod (truck trailer) (Israel) |- | KG9/004 || H. Klein (truck trailer) (Israel) |- | KG9/007 || Agam Trailers (truck trailer) (Israel) |- | KG9/009 || Merkavey Noa (trailer) (Israel) |- | KG9/010 || Weingold Trailers (trailer) (Israel) |- | KG9/011 || Netzer Sereni (truck trailer) (Israel) |- | KG9/015 || Merkaz Hagrorim (trailer) (Israel) |- | KG9/035 || BEL Technologies (truck trailer) (Israel) |- | KG9/091 || Jansteel (truck trailer) (Israel) |- | KG9/101 || Bassamco (truck trailer) (Israel) |- | KG9/104 || Global Handasa (truck trailer) (Israel) |- | KL || Daewoo [[../GM/VIN Codes|General Motors]] South Korea |- | KLA || Daewoo/GM Daewoo/GM Korea (Chevrolet/Alpheon)<br /> from Bupyeong & Kunsan plants |- | KLP || CT&T United (battery electric low-speed vehicles) |- | KLT || Tata Daewoo |- | KLU || Tata Daewoo |- | KLY || Daewoo/GM Daewoo/GM Korea (Chevrolet) from Changwon plant (Tico/Matiz/Matiz Creative/Spark/Damas/Labo) |- | KL1 || GM Daewoo/GM Korea (Chevrolet car) |- | KL2 || Daewoo/GM Daewoo (Pontiac car) |- | KL3 || GM Daewoo/GM Korea (Holden) |- | KL4 || GM Korea (Buick MPV/SUV) |- | KL5 || GM Daewoo (Suzuki car) US: 2004-2008, Canada: 2004-2011 |- | KL5 || Daewoo Bus Corp./Zyle Daewoo Bus 2004-2017 |- | KL6 || GM Daewoo (GMC MPV/SUV) |- | KL7 || Daewoo (GM Canada brands: Passport car, Asuna car (Pre-2000)) |- | KL7 || GM Daewoo/GM Korea (Chevrolet MPV/SUV (Post-2000)) |- | KL8 || GM Daewoo/GM Korea (Chevrolet car from Changwon plant (Spark)) |- | KM || [[../Hyundai/VIN Codes|Hyundai]] |- | KMC || Hyundai commercial truck |- | KME || Hyundai commercial truck (semi-tractor) |- | KMF || Hyundai van & commercial truck & Bering Truck |- | KMH || Hyundai car & Mitsubishi Precis ('87 - 3/10/88) & Mexican market Dodges made by Hyundai |- | KMJ || Hyundai minibus/bus |- | KMT || Genesis Motor car |- | KMU || Genesis Motor SUV |- | KMX || Hyundai Galloper SUV |- | KMY || Daelim Motor Company, Ltd/DNA Motors Co., Ltd. (motorcycles) |- | KM1 || Hyosung Motors (motorcycles) |- | KM4 || Hyosung Motors/S&T Motors/KR Motors (motorcycles) |- | KM8 || Hyundai SUV |- | KNA || Kia car |- | KNC || Kia truck |- | KND || Kia MPV/SUV & Hyundai Entourage |- | KNE || Kia for Europe export |- | KNF || Kia, special vehicles |- | KNG || Kia minibus/bus |- | KNJ || Ford Festiva & Aspire made by Kia |- | KNL || Kia Elan/Vigato made by Kia Motech |- | KNM || Renault Samsung Motors, Nissan Rogue made by Renault Samsung, Nissan Sunny made by Renault Samsung |- | KNM || Renault Korea Co., Ltd. |- | KN1 || Asia Motors |- | KN2 || Asia Motors |- | KPA || SsangYong/KG Mobility (KGM) pickup |- | KPB || SsangYong car or For S. Korea domestic market: SsangYong/KG Mobility (KGM) SUV/MPV |- | KPD || SsangYong bus (TransStar, Istana minibus, Rodius/Korando Turismo 11-seater) |- | KPH || Mitsubishi Precis (3/11/88 - '94) |- | KPT || SsangYong/KG Mobility (KGM) SUV/MPV (For export) |- | LAA || Shanghai Jialing Vehicle Co., Ltd. (motorcycle) |- | LAE || Jinan Qingqi Motorcycle |- | LAL || Sundiro [[../Honda/VIN Codes|Honda]] Motorcycle |- | LAN || Changzhou Yamasaki Motorcycle |- | LAP || Chongqing Jianshe Motorcycle Co., Ltd. |- | LAP || Zhuzhou Nanfang Motorcycle Co., Ltd. |- | LAT || Luoyang Northern Ek Chor Motorcycle Co., Ltd. (Dayang) |- | LA6 || Xiamen King Long United Automotive Industry Co., Ltd. (bus) |- | LA7 || Radar Auto, Farizon Auto (Geely) made by Shandong Tangjun Ouling Automobile Manufacture Co,. Ltd. |- | LA8 || Anhui Ankai |- | LA9/AYS || Jiangsu Alfa Bus Co., Ltd. (bus) |- | LA9/BFC || Beijing North Huade Neoplan Bus Co., Ltd. |- | LA9/FBC || Xiamen Fengtai Bus & Coach International Co., Ltd. (FTBCI) (bus) |- | LA9/HFF || Anhui Huaxia Vehicle Manufacturing Co., Ltd. (bus) |- | LA9/JXK || CHTC Bonluck Bus Co., Ltd. |- | LA9/LC0 || BYD |- | LA9/LFJ || Xinlongma Automobile |- | LA9/LM6 || SRM Shineray |- | LBB || Zhejiang Qianjiang Motorcycle (QJ Motor/Keeway/Benelli) |- | LBE || Beijing [[../Hyundai/VIN Codes|Hyundai]] (Hyundai, Shouwang) |- | LBM || Zongshen Piaggio |- | LBP || Chongqing Jianshe Yamaha Motor Co. Ltd. (motorcycles) |- | LBV || BMW Brilliance (BMW, Zinoro) |- | LBX || Jiangsu Kinroad Xintian Motorcycle Manufacture Co. Ltd. (motorcycles) |- | LBZ || Yantai Shuchi Vehicle Co., Ltd. (bus) |- | LB1 || Fujian Benz |- | LB2 || Geely Motorcycles |- | LB3 || Zhejiang Geely Holding Group (Geely, Galaxy, Geometry, Kandi) |- | LB4 || Chongqing Yinxiang Motorcycle Group Co., Ltd. |- | LB5 || Foshan City Fosti Motorcycle Co., Ltd. |- | LB7 || Tibet New Summit Motorcycle Co., Ltd. |- | LCE || Hangzhou Chunfeng Motorcycles (CFMOTO) |- | LCR || Gonow |- | LC0 || BYD Auto (BYD, Denza) |- | LC2 || Changzhou Kwang Yang Motor Co., Ltd. (Kymco) |- | LC6 || Changzhou Haojue Suzuki Motorcycle Co. Ltd. |- | LDB || Dadi Auto |- | LDC || Dongfeng Peugeot Citroen Automobile Co., Ltd. (DPCA), Dongfeng Fengshen (Aeolus) L60 |- | LDD || Dandong Huanghai Automobile |- | LDF || Dezhou Fulu Vehicle Co., Ltd. (motorcycles), BAW Yuanbao electric car (Ace P1 in Norway) |- | LDK || FAW Bus (Dalian) Co., Ltd. |- | LDN || Soueast (South East (Fujian) Motor Co., Ltd.) including Mitsubishi made by Soueast |- | LDP || Dongfeng, Dongfeng Fengshen (Aeolus), Voyah, Renault City K-ZE/Venucia e30 made by eGT New Energy Automotive |- | LDY || Zhongtong Bus Holding Co. Ltd. |- | LD3 || Guangdong Tayo Motorcycle Technology Co. (Zontes) (motorcycle) |- | LD5 || Benzhou Vehicle Industry Group Ltd. (motorcycle) |- | LD9/L3A || SiTech (FAW) |- | LEC || Tianjin Qingyuan Electric Vehicle Co., Ltd. |- | LEF || Jiangling Motors Corporation Ltd. (JMC) |- | LEH || Zhejiang Riya Motorcycle Co. Ltd. |- | LET || Jiangling-Isuzu Motors, China |- | LEW || Dongfeng commercial vehicle |- | LE4 || Beijing Benz & Beijing Benz-Daimler Chrysler Automotive Co. (Chrysler, Jeep, Mitsubishi, Mercedes-Benz) & Beijing Jeep Corp. |- | LE8 || Guangzhou Huaye Electric Vehicle Technology Co., Ltd. (Formerly Guangzhou Panyu Huanan Motors Group Co., Ltd.) (motorcycles) |- | LFB || FAW Group (Bestune, Hongqi) & Mazda made under license by FAW (Mazda 8, CX-7) |- | LFF || Zhejiang Taizhou Wangye Power Co., Ltd. |- | LFG || Taizhou Chuanl Motorcycle Manufacturing |- | LFJ || Fujian Motors Group (Keyton) |- | LFM || FAW Toyota Motor (Toyota, Ranz) |- | LFN || FAW Bus (Wuxi) Co., Ltd. (truck, bus) |- | LFP || FAW Car, Bestune, Hongqi (passenger vehicles) & Mazda made under license by FAW (Mazda 6, CX-4) |- | LFT || FAW (trailers) |- | LFU || Lifeng Group Co., Ltd. (motorcycles) |- | LFV || FAW-Volkswagen (VW, Audi, Jetta, Kaili) |- | LFW || FAW JieFang (truck) |- | LFX || Sany Heavy Industry (truck) |- | LFY || Changshu Light Motorcycle Factory |- | LFZ || Leapmotor |- | LF3 || Lifan Motorcycle |- | LGA || Dongfeng Commercial Vehicle Co., Ltd. trucks |- | LGB || Dongfeng Nissan (Nissan, Infiniti, Venucia) |- | LGB || Dongfeng Commercial Vehicle Co., Ltd. |- | LGC || Dongfeng Commercial Vehicle Co., Ltd. bus chassis |- | LGD || Dongfeng Commercial Vehicle Co., Ltd. |- | LGF || Dongfeng Commercial Vehicle Co., Ltd. bus chassis |- | LGG || Dongfeng Liuzhou Motor (Forthing/Fengxing) |- | LGJ || Dongfeng Fengshen (Aeolus) |- | LGL || Guilin Daewoo |- | LGV || Heshan Guoji Nanlian Motorcycle Industry Co., Ltd. |- | LGW || Great Wall Motor (GWM, Haval, Ora, Tank, Wey) |- | LGX || BYD Auto (BYD, Fangchengbao) |- | LGZ || Guangzhou Denway Bus |- | LG6 || Dayun Group |- | LHA || Shuanghuan Auto |- | LHB || Beijing Automotive Industry Holding |- | LHG || GAC Honda (Honda, Everus, Acura) |- | LHJ || Chongqing Astronautic Bashan Motorcycle Manufacturing Co., Ltd. |- | LHM || Dongfeng Renault Automobile Co. |- | LHW || CRRC Electric Vehicle Co., Ltd. (bus) |- | LH0 || WM Motor Technology Co., Ltd. (Weltmeister) |- | LH1 || FAW-Haima, China |- | LJC || Jincheng Corporation |- | LJD || Yueda Kia (previously Dongfeng Yueda Kia) (Kia, Horki) & Human Horizons - HiPhi (made under contract by Yueda Kia) |- | LJM || Sunlong (bus) |- | LJN || Zhengzhou Nissan |- | LJR || CIMC Vehicles Group (truck trailer) |- | LJS || Yaxing Coach, Asiastar Bus |- | LJU || Shanghai Maple Automobile & Kandi & Zhidou |- | LJU || Lotus Technology (Wuhan Lotus Cars Co., Ltd.) |- | LJV || Sinotruk Chengdu Wangpai Commercial Vehicle Co., Ltd. |- | LJW || JMC Landwind |- | LJX || JMC Ford |- | LJ1 || JAC (JAC, Sehol) |- | LJ1 || Nio, Inc. |- | LJ4 || Shanghai Jmstar Motorcycle Co., Ltd. |- | LJ5 || Cixi Kingring Motorcycle Co., Ltd. (Jinlun) |- | LJ8 || Zotye Auto made by Jiangnan Automobile |- | LKC || BAIC commercial vehicles, previously Changhe |- | LKG || Youngman Lotus Automobile Co., Ltd. |- | LKH || Hafei Motor |- | LKL || Higer Bus |- | LKT || Yunnan Lifan Junma Vehicle Co., Ltd. commercial vehicles |- | LK2 || Anhui JAC Bus |- | LK6 || SAIC-GM-Wuling (Wuling, Baojun) microcars and other vehicles |- | LK8 || Zhejiang Yule New Energy Automobile Technology Co., Ltd. (ATV) |- | LLC || Loncin Motor Co., Ltd. (motorcycle) |- | LLJ || Jiangsu Xinling Motorcycle Fabricate Co., Ltd. |- | LLN || Qoros |- | LLP || Zhejiang Jiajue Motorcycle Manufacturing Co., Ltd. |- | LLU || Dongfeng Fengxing Jingyi |- | LLV || Lifan, Maple (owned by Geely), Livan Automotive |- | LLX || Yudo Auto |- | LL0 || Sanmen County Yongfu Machine Co., Ltd. (motorcycles) |- | LL2 || WM Motor Technology Co., Ltd. (Weltmeister) |- | LL3 || Xiamen Golden Dragon Bus Co. Ltd. |- | LL6 || GAC Mitsubishi Motors Co., Ltd. (formerly Hunan Changfeng) |- | LL8 || Jiangsu Linhai Yamaha Motor Co., Ltd. |- | LMC || Suzuki Hong Kong (motorcycles) |- | LME || Skyworth (formerly Skywell), Elaris Beo |- | LMF || Jiangmen Zhongyu Motor Co., Ltd. |- | LMG || GAC Motor, Trumpchi, [[w:Dodge Attitude#Fourth generation (2025)|Dodge Attitude made by GAC]] |- | LMH || Jiangsu Guowei Motor Co., Ltd. (Motoleader) |- | LMP || Farizon Auto (Geely Sichuan Commercial Vehicle Co., Ltd.) |- | LMV || Haima Car Co., Ltd. |- | LMV || XPeng Motors G3 (not G3i) made by Haima |- | LMW || GAC Group, [[w:Trumpchi GS5#Dodge Journey|Dodge Journey made by GAC]] |- | LMX || Forthing (Dongfeng Fengxing) |- | LM0 || Wangye Holdings Co., Ltd. (motorcycles) |- | LM6 || SWM (automobiles) |- | LM8 || Seres (formerly SF Motors), AITO |- | LNA || GAC Aion New Energy Automobile Co., Ltd., Hycan |- | LNB || BAIC Motor (Senova, Weiwang, Huansu) & Arcfox & Xiaomi SU7 built by BAIC |- | LND || JMEV (Jiangxi Jiangling Group New Energy Vehicle Co., Ltd.), Eveasy/Mobilize Limo |- | LNE || Zhejiang CRRC Electric Vehicle Co., Ltd. (bus) |- | LNP || NAC MG UK Limited & Nanjing Fiat Automobile |- | LNN || Chery Automobile, Omoda, Jaecoo |- | LNV || Naveco (Nanjing Iveco Automobile Co. Ltd.) |- | LNX || Dongfeng Liuzhou Motor (Chenglong trucks) |- | LNY || Yuejin |- | LPA || Changan PSA (DS Automobiles) |- | LPE || BYD Auto |- | LPS || Polestar |- | LP6 || Guangzhou Panyu Haojian Motorcycle Industry Co., Ltd. |- | LRB || SAIC-General Motors (Buick for export) |- | LRD || Beijing Foton Daimler Automotive Co., Ltd. Auman trucks |- | LRE || SAIC-General Motors (Cadillac for export) |- | LRP || Chongqing Rato Power Co. Ltd. (Asus) |- | LRR || Ningbo Longjia Power Technology Co., Ltd. (motorcycles) |- | LRW || Tesla, Inc. (Gigafactory Shanghai) |- | LR4 || Yadi Technology Group |- | LR6 || Guangzhou Dayun Vehicle Co., Ltd. |- | LSC || Changan Automobile (light truck) |- | LSF || SAIC Maxus or LDV pickup/SUV & Chevrolet S10 Max & Shanghai Sunwin Bus Corporation |- | LSG || SAIC-General Motors (For China: Chevrolet, Buick, Cadillac, Sail Springo, For export: Chevrolet) |- | LSH || SAIC Maxus van or LDV van & Chevrolet Express Max |- | LSJ || SAIC MG & SAIC Roewe & IM Motors & Rising Auto |- | LSK || SAIC Maxus or LDV van |- | LSV || SAIC-Volkswagen (VW, Skoda, Audi, Tantus) |- | LSY || Brilliance (Jinbei, Zhonghua) & Jinbei GM |- | LS3 || Hejia New Energy Vehicle Co., Ltd |- | LS4 || Changan Automobile (MPV/SUV) |- | LS5 || Changan Automobile (car) & Changan Suzuki |- | LS6 || Changan Automobile & Deepal Automobile & Avatr |- | LS7 || JMC Heavy Duty Truck Co., Ltd. |- | LS8 ||Henan Shaolin Auto Co., Ltd. (bus) |- | LTA || ZX Auto |- | LTN || Soueast-built Chrysler & Dodge vehicles |- | LTP || National Electric Vehicle Sweden AB (NEVS) |- | LTV || FAW [[../Toyota/VIN Codes|Toyota]] (Tianjin) |- | LTW || Zhejiang Dianka Automobile Technology Co. Ltd. (Enovate) |- | LT1 || Yangzhou Tonghua Semi-Trailer Co., Ltd. (truck trailer) |- | LUC || [[../Honda/VIN Codes|Honda]] Automobile (China) |- | LUD || Dongfeng Nissan Diesel Motor Co Ltd. |- | LUG || Qiantu Motor |- | LUJ || Zhejiang Shanqi Tianying Vehicle Industry Co., Ltd. (motorcycles) |- | LUR || Chery Automobile, iCar |- | LUX || Dongfeng Yulon Motor Co. Ltd. |- | LUZ || Hozon Auto New Energy Automobile Co., Ltd. (Neta) |- | LVA || Foton Motor |- | LVB || Foton Motor truck |- | LVC || Foton Motor bus |- | LVF || Changhe Suzuki |- | LVG || GAC Toyota (Toyota, Leahead) |- | LVH || Dongfeng Honda (Honda, Ciimo) |- | LVM || Chery Commercial Vehicle |- | LVP || Dongfeng Sokon Motor Company (DFSK) |- | LVR || Changan Mazda |- | LVS || Changan [[../Ford/VIN Codes|Ford]] (Ford, Lincoln) & Changan Ford Mazda & Volvo S40 and S80L made by Changan Ford Mazda |- | LVT || Chery Automobile, Exeed, Jetour, Soueast |- | LVU || Chery Automobile, Jetour, Jaecoo, Omoda |- | LVV || Chery Automobile, Omoda, Jaecoo |- | LVX || Landwind, JMC (discontinued in 2021) |- | LVX || Aiways Automobiles Company Ltd. |- | LVY || Volvo Cars Daqing factory |- | LVZ || Dongfeng Sokon Motor Company (DFSK) |- | LV3 || Hengchi Automobile (Evergrande Group) |- | LV7 || Jinan Qingqi Motorcycle |- | LWB || Wuyang Honda Motorcycle (Guangzhou) Co., Ltd. |- | LWE || Yangtse Motor Group (bus) |- | LWG || Chongqing Huansong Industries (Group) Co., Ltd. |- | LWL || Qingling Isuzu |- | LWM || Chongqing Wonjan Motorcycle Co., Ltd. |- | LWV || GAC Fiat Chrysler Automobiles (Fiat, Jeep) |- | LWX || Shanghai Wanxiang Automobile Manufacturing Co., Ltd. (bus) |- | LW4 || Li Auto |- | LXA || Jiangmen Qipai Motorcycle Co., Ltd. |- | LXD || Ningbo Dongfang Lingyun Vehicle Made Co., Ltd. (motorcycle) |- | LXG || Xuzhou Construction Machinery Group Co., Ltd. (XCMG) |- | LXK || Shanghai Meitian Motorcycle Co., Ltd. |- | LXM || Xiamen Xiashing Motorcycle Co., Ltd. (SYM) |- | LXN || Link Tour |- | LXV || Beijing Borgward Automotive Co., Ltd. |- | LXW || JMC - Ford |- | LXY || Chongqing Shineray Motorcycle Co., Ltd. |- | LX6 || Jiangmen City Huari Group Co. Ltd. (motorcycle) |- | LX8 || Chongqing Xgjao (Xinganjue) Motorcycle Co Ltd. |- | LYB || Weichai (Yangzhou) Yaxing Automobile Co., Ltd. |- | LYD || Taizhou City Kaitong Motorcycle Co., Ltd. (motorcycle) |- | LYJ || Beijing ZhongdaYanjing Auto Co., Ltd. (bus) |- | LYM || Zhuzhou Jianshe Yamaha Motorcycle Co., Ltd. |- | LYS || Nanjing Vmoto Manufacturing Co. Ltd. (motorcycle) |- | LYU || Huansu (BAIC Motor & Yinxiang Group) |- | LYV || Volvo Cars Chengdu factory & Taizhou, Luqiao District factory |- | LY4 || Chongqing Yingang Science & Technology Group Co., Ltd. (motorcycle) |- | LZE || Isuzu Guangzhou, China |- | LZF || SAIC Iveco Hongyan (-2021), SAIC Hongyan (2021-) |- | LZG || Shaanxi Automobile Group (Shacman) |- | LZK || Sinotruk (CNHTC) Huanghe bus |- | LZL || Zengcheng Haili Motorcycle Ltd. |- | LZM || MAN China |- | LZP || Zhongshan Guochi Motorcycle (Baotian) |- | LZS || Zongshen, Electra Meccanica Vehicles Corp. (Solo) made by Zongshen |- | LZU || Guangzhou Isuzu Bus |- | LZW || SAIC-GM-Wuling (Wuling, Baojun, Chevrolet [for export]) |- | LZY || Yutong Bus Co., Ltd. |- | LZZ || Sinotruk (CNHTC) (Howo, Sitrak) |- | LZ0 || Shandong Wuzheng Group Co., Ltd. |- | LZ4 || Jiangsu Linzhi Shangyang Group Co Ltd. |- | LZ9/LZX || Raysince |- | L0N || Ezytrail (camper trailers) |- | L08 || Zhejiang Apollo Sports Technology Co., Ltd. (motorcycles) |- | L1K || Chongqing Hengtong Bus Co., Ltd. |- | L1N || XPeng Motors |- | L10 || Geely Emgrand |- | L2B || Jiangsu Baodiao Locomotive Co., Ltd. (motorcycles) |- | L2C || Chery Jaguar Land Rover |- | L3H || Shanxi Victory Automobile Manufacturing Co., Ltd. |- | L37 || Huzhou Daixi Zhenhua Technology Trade Co., Ltd. (motorcycles) |- | L4B || Xingyue Group (motorcycles) |- | L4F || Suzhou Eagle Electric Vehicle Manufacturing Co., Ltd. |- | L4H || Ningbo Longjia Motorcycle Co., Ltd. |- | L4S || Zhejiang Xingyue Vehicle Co Ltd. (motorcycles) |- | L4Y || Qingqi Group Ningbo Rhon Motorcycle / Ningbo Dalong Smooth Locomotive Industry Co., Ltd. |- | L5C || Zhejiang Kangdi Vehicles Co., Ltd. (motorcycles, ATVs) |- | L5E || Zoomlion Heavy Industry Science & Technology Co., Ltd. |- | L5K || Zhejiang Yongkang Easy Vehicle |- | L5N || Zhejiang Taotao (ATV & motorcycles) |- | L5R || Jiangsu Dafier Motorcycle Co., Ltd. (motorcycles) |- | L5Y || Taizhou Zhongneng Motorcycle Co. Ltd. (Znen) |- | L6F || Shandong Liangzi Power Co. Ltd. |- | L6J || Zhejiang Kayo Motor Co. Ltd. (ATV) |- | L6K || Shanghai Howhit Machinery Manufacture Co. Ltd. |- | L6T || Geely, Lynk & Co, Zeekr |- | L66 || Zhuhai Granton Bus and Coach Co. Ltd. |- | L82 || Baotian |- | L85 || Zhejiang Yongkang Huabao Electric Appliance |- | L8A || Jinhua Youngman Automobile Manufacturing Co., Ltd. |- | L8X || Zhejiang Summit Huawin Motorcycle |- | L8Y || Zhejiang Jonway Motorcycle Manufacturing Co., Ltd. |- | L9G || Zhuhai Guangtong Automobile Co., Ltd. (bus) |- | L9N || Zhejiang Taotao Vehicles Co., Ltd. |- | MAA || India Kawasaki Motors Pvt. Ltd. |- | MAB || Mahindra & Mahindra |- | MAC || Mahindra & Mahindra |- | MAH || Fiat India Automobiles Pvt. Ltd |- | MAJ || [[../Ford/VIN Codes|Ford]] India |- | MAK || [[../Honda/VIN Codes|Honda]] Cars India |- | MAL || Hyundai Motor India |- | MAN || Eicher Polaris Multix |- | MAT || Tata Motors, Rover CityRover |- | MA1 || Mahindra & Mahindra |- | MA3 || Maruti Suzuki India (domestic & export) |- | MA6 || GM India |- | MA7 || Hindustan Motors Ltd. & Mitsubishi Motors & Isuzu models made by Hindustan Motors |- | MA8 || Daewoo Motor India |- | MBF || Royal Enfield |- | MBH || Suzuki (for export) & Nissan Pixo made by Maruti Suzuki India Limited |- | MBJ || [[../Toyota/VIN Codes|Toyota]] Kirloskar Motor Pvt. Ltd. |- | MBK || MAN Trucks India Pvt. Ltd. |- | MBL || Hero MotoCorp |- | MBR || Mercedes-Benz India |- | MBU || Swaraj Vehicles Limited |- | MBV || Premier Automobiles Ltd. |- | MBX || Piaggio India (Piaggio Ape) |- | MBY || Asia Motor Works Ltd. |- | MB1 || Ashok Leyland |- | MB2 || Hyundai Motor India (SUV) |- | MB7 || Reva Electric Car Company/Mahindra Reva Electric Vehicles Pvt. Ltd. |- | MB8 || Suzuki Motorcycle India Limited |- | MCA || FCA India Automobiles Pvt. Ltd. (Fiat, Jeep) |- | MCB || GM India |- | MCD || Mahindra Two Wheelers |- | MCG || Atul Auto Ltd. |- | MCL || International Cars And Motors Ltd. |- | MC1 || Force Motors Ltd. |- | MC2 || Eicher Motors Ltd./Volvo Eicher Commercial Vehicles Ltd. |- | MC4 || Dilip Chhabria Design Pvt Ltd. |- | MC9/RE1 || Reva Electric Car Company (Reva G-Wiz) |- | MDE || Kinetic Engineering Limited |- | MDH || Nissan Motor India Pvt Ltd. (including Datsun) |- | MDT || Kerala Automobiles Limited |- | MD2 || Bajaj Auto Ltd. & KTM and Husqvarna motorcycles built by Bajaj & Indian-market Triumph motorcycles built by Bajaj |- | MD6 || TVS Motor Company |- | MD7 || LML Ltd including Genuine Scooter Company Stella |- | MD9 || Shuttle Cars India |- | MEC || Daimler India Commercial Vehicles (BharatBenz) |- | MEE || Renault India Private Limited |- | MEG || Harley-Davidson India |- | MER || Benelli India |- | MES || Mahindra Navistar |- | MET || Piaggio India (Vespa, Indian-market Aprilia) |- | MEX || Škoda Auto Volkswagen India Pvt. Ltd. 2015 on |- | ME1 || India Yamaha Motor Pvt. Ltd. |- | ME3 || Royal Enfield |- | ME4 || Honda Motorcycle and Scooter India |- | MYH || Ather Energy |- | MZB || Kia India Pvt. Ltd. |- | MZD || Classic Legends Private Limited – Jawa |- | MZZ || Citroen India (PCA Automobiles India Private Limited) |- | MZ7 || MG Motor India Pvt. Ltd. |- | M3G || Isuzu Motors India |- | M6F || UM Lohia Two Wheelers Private Limited |- | ME9/ || BUYMYEV TECHNOLOGY PVT. LTD. (Indibike) |- | MF3 || PT Hyundai Motor Manufacturing Indonesia |- | MHB || PT Nissan Motor Indonesia |- | MHD || PT Indomobil Suzuki International |- | MHF || PT [[../Toyota/VIN Codes|Toyota]] Motor Manufacturing Indonesia |- | MHK || PT Astra Daihatsu Motor (includes Toyotas made by Astra Daihatsu) |- | MHL || PT Mercedes-Benz Indonesia |- | MHR || [[../Honda/VIN Codes|Honda]] Indonesia (PT Honda Prospect Motor) (car) |- | MHY || PT Suzuki Indomobil Motor (car, MPV, van) |- | MH1 || PT Astra Honda Motor (motorcycle) |- | MH3 || PT Yamaha Indonesia Motor Mfg. |- | MH4 || PT Kawasaki Motor Indonesia |- | MH8 || PT Suzuki Indomobil Motor (motorcycle) |- | MJB || GM Indonesia |- | MKF || PT Sokonindo Automobile (DFSK) |- | MK2 || PT Mitsubishi Motors Krama Yudha Indonesia |- | MK3 || PT SGMW Motor Indonesia (Wuling) |- | MLB || Siam Yamaha Co Ltd. |- | MLC || Thai Suzuki Motor Co., Ltd. (motorcycle) |- | MLE || Thai Yamaha Motor Co., Ltd. |- | MLH || Thai [[../Honda/VIN Codes|Honda]] Manufacturing Co., Ltd. (motorcycle) |- | MLW || Sco Motor Co., Ltd. (motorcycle) |- | MLY || Harley-Davidson Thailand |- | ML0 || Ducati Motor (Thailand) Co., Ltd. |- | ML3 || Mitsubishi Motors, Dodge Colt 100 [Canada], [[w:Dodge Attitude#Third generation (A10; 2015)|Dodge Attitude]] [Mexico] made by Mitsubishi (Thailand) |- | ML5 || Kawasaki Motors Enterprise Co. Ltd. (Thailand) |- | MMA || Mitsubishi Motors (Thailand) & Nissan Navara D27 made by Mitsubishi Motors (Thailand) |- | MMB || Mitsubishi Motors (Thailand) |- | MMC || Mitsubishi Motors (Thailand) |- | MMD || Mitsubishi Motors (Thailand) |- | MME || Mitsubishi Motors (Thailand) |- | MMF || BMW Manufacturing (Thailand) Co., Ltd. |- | MML || MG Thailand (SAIC-CP) |- | MMM || Chevrolet Thailand, Holden Colorado RC pickup |- | MMR || Subaru/Tan Chong Subaru Automotive (Thailand) Co. Ltd. |- | MMS || Suzuki Motor (Thailand) Co., Ltd. (passenger car) |- | MMT || Mitsubishi Motors (Thailand) |- | MMU || Holden Thailand (Colorado RG, Colorado 7, & Trailblazer) |- | MM0, MM6, MM7, MM8 || Mazda Thailand (Ford-Mazda AutoAlliance Thailand plant) |- | MNA || [[../Ford/VIN Codes|Ford]] Thailand (Ford-Mazda AutoAlliance Thailand plant) for Australia/New Zealand export |- | MNB || [[../Ford/VIN Codes|Ford]] Thailand (Ford-Mazda AutoAlliance Thailand plant) for other right-hand drive markets |- | MNC || [[../Ford/VIN Codes|Ford]] Thailand (Ford-Mazda AutoAlliance Thailand plant) for left-hand drive markets |- | MNK || Hino Motors Manufacturing Thailand Co Ltd. |- | MNT || Nissan Motor (Thailand) Co., Ltd. |- | MNU || Great Wall Motor Manufacturing (Thailand) Co., Ltd. |- | MN3 || Eagle Vista [Canada] made by Mitsubishi (Thailand) |- | MPA || Isuzu Motors (Thailand) Co., Ltd. & Holden Rodeo RA pickup made by Isuzu in Thailand |- | MPB || [[../Ford/VIN Codes|Ford]] Thailand (Ford Thailand Manufacturing plant) |- | MP1 || Isuzu Motors (Thailand) Co., Ltd. |- | MP2 || Mazda BT-50 pickup built by Isuzu Motors (Thailand) Co., Ltd. |- | MP3 || Plymouth Colt 100 [Canada] made by Mitsubishi (Thailand) |- | MP5 || Foton Motor Thailand |- | MRH || [[../Honda/VIN Codes|Honda]] Thailand (car) |- | MRT || Neta (Hozon Auto) made by Bangchan General Assembly Co., Ltd. |- | MR0 || [[../Toyota/VIN Codes|Toyota]] Thailand (pickups & Fortuner SUV) |- | MR1 || [[../Toyota/VIN Codes|Toyota]] Thailand |- | MR2 || [[../Toyota/VIN Codes|Toyota]] Thailand (Gateway plant) (passenger cars & CUVs) |- | MR3 || [[../Toyota/VIN Codes|Toyota]] Thailand (Hilux Champ chassis cab) |- | MS0 || [[../SUPER SEVEN STARS MOTORS INDUSTRY CO.,LTD/VIN Codes|Super Seven Stars Motors]] Myanmar |- | MS1 || [[../SUPER SEVEN STARS AUTOMOTIVE CO.,LTD/VIN Codes|Super Seven Stars Automotive]] Myanmar |- | MS3 || Suzuki Myanmar Motor Co., Ltd. |- | MXB || Saryarka AvtoProm bus (Kazakhstan) |- | MXL || Yutong bus made by Qaz Tehna (Kazakhstan) |- | MXV || IMZ-Ural Ural Motorcycles (Kazakhstan) |- | MX3 || Hyundai Trans Auto (Kazakhstan) |- | NAA || Iran Khodro (Peugeot Iran) |- | NAC || Mammut (truck trailers) |- | NAD || Škoda |- | NAL || Maral Sanat Jarvid (truck trailers) |- | NAP || Pars Khodro |- | NAS || SAIPA |- | NC0 || Oghab Afshan (bus) |- | NC9/ || VIRA Diesel |- | ND9/345 || Oghab Afshan (bus) |- | NFB || Honda Atlas Cars Pakistan Ltd. |- | NG3 || Lucky Motor Corporation |- | NLA || Honda Turkiye A.S. cars |- | NLC || Askam Kamyon Imalat Ve Ticaret A.S. |- | NLE || Mercedes-Benz Türk A.S. Truck |- | NLF || Koluman Otomotiv Endustri A.S. (truck trailer) |- | NLH || [[../Hyundai/VIN Codes|Hyundai]] Assan Otomotiv car/SUV |- | NLJ || [[../Hyundai/VIN Codes|Hyundai]] Assan Otomotiv van |- | NLN || Karsan |- | NLR || Otokar |- | NLT || Temsa |- | NLZ || Tezeller |- | NL1 || TOGG |- | NL2 || HABAS/HBS (bus) |- | NMA || MAN Türkiye A.Ş. |- | NMB || Mercedes-Benz Türk A.S. Buses |- | NMC || BMC Otomotiv Sanayi ve Ticaret A.Ş. |- | NMH || Honda Anadolu motorcycle |- | NMS || Otoyol San. A.Ş. |- | NMT || [[../Toyota/VIN Codes|Toyota]] Motor Manufacturing Turkey |- | NM0 || Ford Otosan |- | NM1 || Oyak Renault Otomobil Fabrikaları A.Ş. |- | NM4 || Tofaş (Turk Otomobil Fabrikasi AS) |- | NNA || Anadolu Isuzu |- | NNN || Gépébus Oréos 4X (based on Otokar Vectio) |- | NNY || Yeksan (truck trailer) |- | NPM || Seyit Usta Treyler (truck trailer) |- | NPR || Oztreyler (truck trailer) |- | NPS || Nursan (truck trailer) |- | NP8|| ÖZGÜL TREYLER (truck trailer) |- | NP9/002 || OKT Trailer (truck trailer) |- | NP9/003 || Aksoylu Trailer (truck trailer) |- | NP9/011 || Güleryüz (bus) |- | NP9/021 || Dogumak (truck trailer) |- | NP9/022 || Alim (truck trailer) |- | NP9/042 || Ali Rıza Usta (truck trailer) |- | NP9/066 || Makinsan (truck trailer) |- | NP9/093 || BRF Trailer (truck trailer) |- | NP9/103 || Türkkar (bus) |- | NP9/106 || Çarsan Treyler (truck trailer) |- | NP9/107 || Arbus Perfect (bus) |- | NP9/108 || Guven Makina (truck trailer) |- | NP9/117 || Katmerciler (truck trailer) |- | NP9/300 || TCV (bus) |- | NP9/258 || Ceytrayler (truck trailer) |- | NP9/306 || Cryocan (truck trailer) |- | NRE || Bozankaya |- | NRX || Musoshi |- | NRY || Pilotcar Otomotiv |- | NR9/012 || Doğan Yıldız (truck trailer) |- | NR9/028 || Micansan (truck trailer) |- | NR9/029 || Yilteks (truck trailer) |- | NR9/034 || Akia (bus) |- | NR9/084 || Harsan (truck trailer) |- | NR9/257 || Vega Trailer (truck trailer) |- | NSA || SamAvto / SAZ (Uzbekistan) |- | NS2 || JV MAN Auto - Uzbekistan |- | NVA || Khazar (IKCO Dena made in Azerbaijan) |- | PAB || Isuzu Philippines Corporation |- | PAD || Honda Cars Philippines |- | PE1 || Ford Motor Company Philippines |- | PE3 || Mazda Philippines made by Ford Motor Company Philippines |- | PFD || Hyundai Motor Group Innovation Center in Singapore (HMGICS) |- | PL1 || Proton, Malaysia |- | PL8 || Inokom-Hyundai |- | PLP || Subaru/Tan Chong Motor Assemblies, Malaysia |- | PLZ || Isuzu Malaysia |- | PMA || MAN Truck & Bus Malaysia |- | PMH || Honda Malaysia (car) |- | PMK || Honda Boon Siew (motorcycle) |- | PML || Hicom |- | PMN || Modenas |- | PMS || Suzuki Assemblers Malaysia (motorcycle) |- | PMV || Hong Leong Yamaha Motor Sdn. Bhd. |- | PMY || Hong Leong Yamaha Motor Sdn. Bhd. |- | PM1 || BMW & Mini/Inokom |- | PM2 || Perodua |- | PM9/ || Bufori |- | PNA || Naza/Kia/Peugeot |- | PNA || Stellantis Gurun (Malaysia) Sdn. Bhd. (Peugeot) |- | PNS || SKSBUS Malaysia (bus) |- | PNS || TMSBUS Malaysia (bus) |- | PNV || Volvo Car Manufacturing Malaysia |- | PN1 || UMW Toyota Motor - Assembly Services Sdn. Bhd. (ASSB) |- | PN2 || UMW Toyota Motor - Assembly Services Sdn. Bhd. (ASSB) |- | PN8 || Nissan/Tan Chong Motor Assemblies, Malaysia |- | PPP || Suzuki |- | PPV || Volkswagen/HICOM Automotive Manufacturers (Malaysia) |- | PP1 || Mazda/Inokom |- | PP3 || Hyundai/Inokom |- | PRA || Sinotruk |- | PRH || Chery (by Chery Alado Holdings [joint venture] at Oriental Assemblers plant) |- | PRX || Kia/Inokom |- | PR8 || Ford |- | PRN || GAC Trumpchi made by Warisan Tan Chong Automotif Malaysia |- | PV3 || Ford made by RMA Automotive Cambodia |- | RA1 || Steyr Trucks International FZE, UAE |- | RA9/015 || Al-Assri Industries (Trailers), UAE |- | LES || Isuzu MPV made by Sanfu Motor Industrial Co., Ltd. (Trooper '87-'91) (Taiwan) |- | LFA || Ford Lio Ho Motor Co Ltd. old designation (Taiwan) |- | LM1 || Tai Ling Motor Co Ltd. old designation (Suzuki motorcycle made by Tai Ling) (Taiwan) |- | LM4 || Tai Ling Motor Co Ltd. old designation (Suzuki ATV made by Tai Ling) (Taiwan) |- | LM5 || Isuzu Truck (Light Duty) made by Sanfu Motor Industrial Co., Ltd. (Trooper '87-'88) (Taiwan) |- | LN1 || Tai Ling Motor Co Ltd. old designation (Suzuki motorcycle made by Tai Ling) (Taiwan) |- | LPR || Yamaha Motor Taiwan Co. Ltd. old designation (Taiwan) |- | RFB || Kwang Yang Motor Co., Ltd. (Kymco), Taiwan |- | RFC || Taiwan Golden Bee |- | RFD || Tai Ling Motor Co Ltd. new designation (Taiwan) |- | RFG || Sanyang Motor Co., Ltd. (SYM) Taiwan |- | RFL || Her Chee Industrial Co., Ltd. (Adly), Taiwan |- | RFT || CPI Motor Company, Taiwan |- | RFV || Motive Power Industry Co., Ltd. (PGO Scooters including Genuine Scooter Company models made by PGO) (Taiwan) |- | RF3 || Aeon Motor Co., Ltd., Taiwan |- | RF5 || Yulon Motor Co. Ltd., Taiwan (Luxgen) |- | RF8 || EVT Technology Co., Ltd (motorcycle) |- | RGS || Kawasaki made by Kymco (Taiwan) |- | RHA || Ford Lio Ho Motor Co Ltd. new designation (Taiwan) |- | RKJ || Prince Motors Taiwan |- | RKL || Kuozui Motors (Toyota) (Taiwan) |- | RKM || China Motor Corporation (Taiwan) |- | RKR || Yamaha Motor Taiwan Co. Ltd. new designation |- | RKT || Access Motor Co., Ltd. (Taiwan) |- | RK3 || E-Ton Power Tech Co., Ltd. (motorcycle) (Taiwan) |- | RK3 || Honda Taiwan |- | RK7 || Kawasaki ATV made by Tai Ling Motor Co Ltd (rebadged Suzuki ATV) new designation (Taiwan) |- | RLA || Vina Star Motors Corp. – Mitsubishi (Vietnam) |- | RLC || Yamaha Motor Vietnam Co. Ltd. |- | RLE || Isuzu Vietnam Co. |- | RLH || Honda Vietnam Co. Ltd. |- | RLL || VinFast SUV |- | RLM || Mercedes-Benz Vietnam |- | RLN || VinFast |- | RLV || Vietnam Precision Industrial CO., Ltd. (Can-Am DS 70 & DS 90) |- | RL0 || Ford Vietnam |- | RL4 || Toyota Motor Vietnam |- | RP8 || Piaggio Vietnam Co. Ltd. |- | RUN || Sollets-Auto ST6 (Russia) |- | R1J || Jiayuan Power (Hong Kong) Ltd. (Electric Low-Speed Vehicles) (Hong Kong) |- | R1N || Niu Technologies Group Ltd. (Hong Kong) |- | R10 || ZAP (HK) Co. Ltd. |- | R19/003 || GMI (bus) (Hong Kong) |- | R2P || Evoke Electric Motorcycles (Hong Kong) |- | R3M || Mangosteen Technology Co., Ltd. (Hong Kong) |- | R3W || Hong Kong Runhorse Holding Co., Ltd. (Hong Kong) |- | R36 || HK Shansu Technology Co., Ltd. (Hong Kong) |- | R4N || Elyx Smart Technology Holdings (Hong Kong) Ltd. |- | R82 || Hangzhou Lantu Technology Co., Ltd. (Hong Kong) |- | SAA || Austin |- | SAB || Optare (1985-2020), Switch Mobility (2021-) |- | SAD || Daimler Company Limited (until April 1987) |- | SAD || Jaguar SUV (E-Pace, F-Pace, I-Pace) |- | SAF || ERF trucks |- | SAH || Honda made by Austin Rover Group |- | SAJ || Jaguar passenger car & Daimler passenger car (after April 1987) |- | SAL || [[../Land Rover/VIN Codes|Land Rover]] |- | SAM || Morris |- | SAR || Rover & MG Rover Group |- | SAT || Triumph car |- | SAX || Austin-Rover Group including Sterling Cars |- | SAY || Norton Motorcycles (UK) Ltd. (Donington Park/Donington Hall) |- | SAZ || Freight Rover |- | SA3 || Ginetta Cars |- | SA9/ || OX Global |- | SA9/A11 || Morgan Roadster (V6) (USA) |- | SA9/J00 || Morgan Aero 8 (USA) |- | SA9/004 || Morgan (4-wheel passenger cars) |- | SA9/005 || Panther |- | SA9/010 || Invicta S1 |- | SA9/011 || Midas Cars |- | SA9/019 || TVR |- | SA9/022 || Triking Sports Cars |- | SA9/026 || Fleur de Lys |- | SA9/036 || Ginetta Cars |- | SA9/038 || DAX Cars |- | SA9/039 || Westfield Sportscars |- | SA9/048 || McLaren F1 |- | SA9/050 || Marcos Engineering |- | SA9/062 || AC Cars (Brooklands Ace) |- | SA9/068 || Johnston Sweepers |- | SA9/073 || Tomita Auto UK (Tommykaira ZZ) |- | SA9/074 || Ascari |- | SA9/088 || Spectre Angel |- | SA9/105 || Mosler Europe Ltd. |- | SA9/113 || Noble |- | SA9/130 || MG Sport and Racing |- | SA9/141 || Wrightbus |- | SA9/202 || Morgan 3-Wheeler, Super 3 |- | SA9/207 || Radical Sportscars |- | SA9/211 || BAC (Briggs Automotive Company Ltd.) |- | SA9/225 || Paneltex (truck trailer) |- | SA9/231 || Peel Engineering |- | SA9/337 || Ariel |- | SA9/341 || Zenos |- | SA9/438 || Charge Cars |- | SA9/458 || Gordon Murray Automotive |- | SA9/474 || Mellor (bus) |- | SA9/612 || Tiger Racing (kit car) |- | SA9/621 || AC Cars (Ace) |- | SBB || Leyland Vehicles |- | SBC || Iveco Ford Truck |- | SBF || Nugent (trailer) |- | SBJ || Leyland Bus |- | SBL || Leyland Motors & Leyland DAF |- | SBM || McLaren |- | SBS || Scammell |- | SBU || United Trailers (truck trailer) |- | SBV || Kenworth & Peterbilt [incomplete vehicle] made by Leyland Trucks |- | SBW || Weightlifter Bodies (truck trailer) |- | SB1 || [[../Toyota/VIN Codes|Toyota]] Motor Manufacturing UK |- | SCA || Rolls Royce passenger car |- | SCB || Bentley passenger car |- | SCC || Lotus Cars & Opel Lotus Omega/Vauxhall Lotus Carlton |- | SCD || Reliant Motors |- | SCE || DeLorean Motor Cars N. Ireland (UK) |- | SCF || Aston Martin Lagonda Ltd. passenger car & '21 DBX SUV |- | SCG || Triumph Engineering Co. Ltd. (original Triumph Motorcycle company) |- | SCK || Ifor Williams Trailers |- | SCM || Manitowoc Cranes - Grove |- | SCR || London Electric Vehicle Company & London Taxi Company & London Taxis International |- | SCV || Volvo Truck & Bus Scotland |- | SC5 || Wrightbus (from ~2020) |- | SC6 || INEOS Automotive SUV |- | SDB || Talbot |- | SDC || SDC Trailers Ltd. (truck trailer) |- | SDF || Dodge Trucks – UK 1981–1984 |- | SDG || Renault Trucks Industries 1985–1992 |- | SDK || Caterham Cars |- | SDL || TVR |- | SDP || NAC MG UK & MG Motor UK Ltd. |- | SDU || Utility (truck trailer) |- | SD7 || Aston Martin SUV |- | SD8 || Moke International Ltd. |- | SED || IBC Vehicles (General Motors Luton Plant) (Opel/Vauxhall, 1st gen. Holden Frontera, Isuzu Midi) |- | SEG || Dennis Eagle Ltd., including Renault Trucks Access and D Access |- | SEP || Don-Bur (truck trailer) |- | SEY || LDV Group Ltd. |- | SFA || [[../Ford/VIN Codes|Ford]] UK |- | SFD || Dennis UK / Alexander Dennis |- | SFE || Alexander Dennis UK |- | SFR || Fruehauf (truck trailer) |- | SFN || Foden Trucks & Kenworth [truck] made by Foden Trucks |- | SFZ || Tesla Roadster made by Lotus |- | SGA || Avondale (caravans) |- | SGB || Bailey (caravans) |- | SGD || Swift Group Ltd. (caravans) |- | SGE || Elddis (caravans) |- | SGL || Lunar Caravans Ltd. |- | SG4 || Coachman Caravan Co. Ltd. |- | SG7 || ABI Caravans Ltd. |- | SHH || [[../Honda/VIN Codes|Honda]] UK passenger car |- | SHS || [[../Honda/VIN Codes|Honda]] UK SUV |- | SH2 || The Norton Motorcycle Co., Ltd. (TVS Motor Co. subsidiary) |- | SH7 || INEOS Automotive truck |- | SJA || Bentley SUV |- | SJB || Brian James Trailers Ltd |- | SJK || Nissan Motor Manufacturing UK - Infiniti |- | SJN || Nissan Motor Manufacturing UK - Nissan |- | SJ1 || Ree Automotive |- | SKA || Vauxhall |- | SKB || Kel-Berg Trailers & Trucks |- | SKF || Bedford Vehicles |- | SKL || Anaig (UK) Technology Ltd |- | SKM || King Military Engineering Ltd. |- | SLA || Rolls Royce SUV |- | SLC || Thwaites Dumpers |- | SLG || McMurtry Automotive |- | SLN || Niftylift |- | SLP || JC Bamford Excavators Ltd. |- | SLV || Volvo bus |- | SMR || Montracon (truck trailer) |- | SMT || Triumph Motorcycles Ltd. (current Triumph Motorcycle company) |- | SMW || Cartwright (truck trailer) |- | SMX || Gray & Adams (truck trailer) |- | SNE || Barkas (East Germany) |- | SNE || Wartburg (East Germany) |- | SNT || Trabant (East Germany) |- | SNZ || MZ (motorcycle) (Germany) |- | SPE || B-ON GmbH (Germany) |- | ST3 || Calabrese (truck trailer) |- | SUA || Autosan (bus) |- | SUB || Tramp Trail (trailer) |- | SUC || Wiola (trailer) |- | SUD || Wielton (truck trailers) |- | SUF || FSM/Fiat Auto Poland (Polski Fiat) |- | SUG || Mega Trailers (truck trailer) (Poland) |- | SUJ || Jelcz (Poland) |- | SUL || FSC (Poland) |- | SUM || Novatrail (truck trailers) |- | SUP || FSO/Daewoo-FSO (Poland) |- | SUU || Solaris Bus & Coach (Poland) |- | SU9/AR1 || Emtech (truck trailer) |- | SU9/BU1 || BODEX (truck trailer) |- | SU9/DE2 || Demarco (truck trailer) |- | SU9/EB1 || Elbo (truck trailer) |- | SU9/EZ1 || Enerco (truck trailer) |- | SU9/NC5 || Zasta (truck trailer) |- | SU9/NJ1 || Janmil (truck trailer) |- | SU9/PL1 || Plandex (truck trailer) |- | SU9/PN1 || Solaris Bus & Coach (Poland) - until 2004 |- | SU9/RE1 || Redos (truck trailer) |- | SU9/RE2 || Gromex (trailer) |- | SU9/TR1 || Plavec (truck trailer) |- | SU9/YV1 || Pilea bus/ARP E-Vehicles (Poland) |- | SU9/ZC1 || Wolf (truck trailer) |- | SVH || ZASŁAW (truck trailer) |- | SVM || Inter Cars (truck trailer) |- | SVS || BODEX (truck trailer) |- | SV9/BC2 || BC-LDS (truck trailer) |- | SV9/DR1 || Dromech (truck trailer) |- | SV9/RN1 || Prod-Rent (truck trailer) |- | SWH || Temared (trailers) |- | SWR || Weekend Trailers (trailers) |- | SWV || TA-NO (Poland) |- | SWZ || Zremb (trailers) |- | SW9/BA1 || Solbus |- | SW9/WG3 || Grew / Opalenica (trailer) |- | SXE || Neptun Trailers |- | SXK || Konar (truck trailer) |- | SXM || MELEX Sp. z o.o. |- | SXY || Wecon (truck trailer) |- | SXX || Martz (trailer) |- | SX7 || Arthur Bus |- | SX9/GR0 || GRAS (truck trailer) |- | SX9/KT1 || AMZ - Kutno (bus) |- | SX9/PN1 || Polkon (truck trailer) |- | SX9/SP1 || SOMMER Polska (truck trailer) |- | SYB || Rydwan (trailer) |- | SYG || Gniotpol, GT Trailers Sp. z o. o. (truck trailer) |- | SY1 || Neso Bus (PAK-PCE Polski Autobus Wodorowy) |- | SY9/FR1 || Feber (truck trailer) |- | SY9/PF1 || KEMPF (truck trailer) |- | SZA || Scania Poland |- | SZC || Vectrix (motorcycle) |- | SZL || Boro Trailers |- | SZN || Przyczepy Głowacz (trailer) |- | SZR || Niewiadów (trailer) |- | SZ9/AE6 || Gewe (trailer) |- | SZ9/BG1 || GALA Syriusz (trailer) |- | SZ9/PW1 || PRO-WAM (truck trailer) |- | SZ9/TU1 || Ovibos (truck trailer) |- | S19/AM0 || AMO Plant (bus) (Latvia) |- | S19/EF1 || Electrify (minibus) (Latvia) |- | S19/MT0 || Mono-Transserviss (truck trailer) (Latvia) |- | TAW || NAW Nutzfahrzeuggesellschaft Arbon & Wetzikon AG (Switzerland) |- | TBS || Boschung AG (Switzerland) |- | TCC || Micro Compact Car AG (smart 1998-1999) (Switzerland) |- | TDM || QUANTYA Swiss Electric Movement (Switzerland) |- | TEB || Bucher Municipal AG (includes Johnston Sweepers) (Switzerland) |- | TEM || Twike (SwissLEM AG) (Switzerland) |- | TFH || FHS Frech-Hoch AG (truck trailer) (Switzerland) |- | TH9/512 || Hess AG (bus, trolleybus) (Switzerland) |- | TJ5 || Vezeko (trailer) (Czech Republic) |- | TKP || Panav a.s. (truck trailer) (Czech Republic) |- | TKX || Agados s.r.o. (trailer) (Czech Republic) |- | TKY || Metaco (truck trailer) (Czech Republic) |- | TK9/AH3 || Atmos Chrást s.r.o. (Czech Republic) |- | TK9/AP3 || Agados, spol. s.r.o. (trailer) (Czech Republic) |- | TK9/HP1 || Hipocar (truck trailer) (Czech Republic) |- | TK9/PP7 || Paragan Trucks (truck trailer) (Czech Republic) |- | TK9/SL5 || SOR Libchavy buses (Czech Republic) |- | TK9/SS5 || SVAN Chrudim (truck trailer) (Czech Republic) |- | TLJ || Jawa Moto (Czech Republic) |- | TMA || [[../Hyundai/VIN Codes|Hyundai]] Motor Manufacturing Czech |- | TMB || Škoda Auto|Škoda (Czech Republic) |- | TMC || [[../Hyundai/VIN Codes|Hyundai]] Motor Manufacturing Czech (SUV) |- | TMK || Karosa (Czech Republic) |- | TMP || Škoda trolleybuses (Czech Republic) |- | TMT || Tatra passenger car (Czech Republic) |- | TM9/CA2 || Oasa bus (Oprava a stavba automobilů) (Czech Republic) |- | TM9/SE3 || Škoda Transportation trolleybuses (Czech Republic) |- | TM9/SE4 || Škoda Transportation trolleybuses (Czech Republic) |- | TM9/TE6 || TEDOM bus (Czech Republic) |- | TNA || Avia/Daewoo Avia |- | TNE || TAZ |- | TNG || LIAZ (Liberecké Automobilové Závody) |- | TNT || Tatra trucks |- | TNU || Tatra trucks |- | TN9/EE7 || Ekova (bus) (Czech Republic) |- | TN9/VP5 || VPS (truck trailer) |- | TRA || Ikarus Bus |- | TRC || Csepel bus |- | TRE || Rákos bus |- | TRK || Credo bus/Kravtex (Hungary) |- | TRR || Rába Bus (Hungary) |- | TRU || Audi Hungary (TT/TTS, '12-'13 TT RS) |- | TSB || Ikarus Bus |- | TSC || VIN assigned by the National Transport Authority of Hungary |- | TSE || Ikarus Egyedi Autobuszgyar (EAG) (Hungary) |- | TSF || Alfabusz (Hungary) |- | TSM || Suzuki Hungary (Magyar Suzuki),<br> Fiat Sedici made by Suzuki, Subaru Justy G3X made by Suzuki, Suzuki Swace made by Toyota UK (TMUK) |- | TSY || Keeway Motorcycles (Hungary) |- | TS9/102 || Evopro Holding Zrt. (bus) (Hungary) |- | TS9/111 || NABI Autóbuszipari (bus) (Hungary) |- | TS9/130 || Enterprise Bus (Hungary) |- | TS9/131 || MJT bus (Hungary) |- | TS9/156 || Ikarus / ARC (Auto Rad Controlle Kft.) & Magyar Autóbuszgyártó Kft. bus (Hungary) |- | TS9/167 || Hungarian Bus Kft. (Hungary) |- | TS9/170 || Csaba Metál bus (Hungary) |- | TT9/117 || Ikarus Egyedi Autobusz Gyarto Kft. / Magyar Autóbuszgyártó Kft. / MABI bus (Hungary) |- | TT9/123 || Ikarus Global Zrt. (Hungary) |- | TWG || CaetanoBus (Portugal) |- | TW0 || CaetanoBus (Portugal) |- | TW1 || Toyota Caetano Portugal, S.A. (Toyota Coaster, Dyna, Optimo, Land Cruiser 70 Series) |- | TW2 || [[../Ford/VIN Codes|Ford]] Lusitana (Portugal) |- | TW4 || UMM (Portugal) |- | TW6 || Citroën (Portugal) |- | TW7 || Mini Moke made by British Leyland & Austin Rover Portugal |- | TX5 || Mini Moke made by Cagiva (Moke Automobili) |- | TX9/046 || Riotrailer (truck trailer) (Portugal) |- | TYA || Mitsubishi Fuso Truck and Bus Corp. Portugal (right-hand drive) |- | TYB || Mitsubishi Fuso Truck and Bus Corp. Portugal (left-hand drive) |- | T3C || Lohr Backa Topola (truck trailer) (Serbia) |- | T49/BG7 || FAP (Serbia) |- | T49/BH8 || Megabus (bus) (Serbia) |- | T49/BM2 || Feniksbus (minibus) (Serbia) |- | T49/V16 || MAZ made by BIK (bus) (Serbia) |- | T7A || Ebusco (Netherlands) |- | UA1 || AUSA Center (Spain) |- | UA2 || Iveco Massif & Campagnola made by Santana Motors in Spain |- | UA4 || Irizar e-mobility (Spain) |- | UCY || Silence Urban Ecomobility (Spain) |- | UD3 || Granalu truck trailers (Belgium) |- | UHE || Scanvogn (trailer) (Denmark) |- | UHL || Camp-let (recreational vehicle) (Denmark) |- | UH2 || Brenderup (trailer) (Denmark) |- | UH2 || De Forenede Trailerfabrikke (trailer) (Denmark) |- | UH9/DA3 || DAB - Danish Automobile Building (acquired by Scania) (Denmark) |- | UH9/EM1 || Egholm (Denmark) |- | UH9/FK1 || Dapa Trailer (truck trailer) (Denmark) |- | UH9/HF1 || HFR Trailer A/S (truck trailer) (Denmark) |- | UH9/HM1 || HMK Bilcon A/S (truck trailer) (Denmark) |- | UH9/NS1 || Nopa (truck trailer) (Denmark) |- | UH9/NT1 || Nordic Trailer (truck trailer) (Denmark) |- | UH9/VM2 || VM Tarm a/s (truck trailer) (Denmark) |- | UJG || Garia ApS - Club Car (Denmark) |- | UKR || Hero Camper (Denmark) |- | UMT || MTDK a/s (truck trailer) (Denmark) |- | UN1 || [[../Ford/VIN Codes|Ford]] Ireland |- | UN9/012 || Duffy Coachbodies (Ireland) |- | UN9/089 || Brian Noone Ltd. bus (Ireland) |- | UU1 || Dacia (Romania) |- | UU2 || Oltcit |- | UU3 || ARO |- | UU4 || Roman/Grivbuz |- | UU5 || Rocar |- | UU6 || Daewoo Romania |- | UU7 || Euro Bus Diamond |- | UU9 || Astra Bus |- | UVW || UMM (truck trailer) |- | UV9/AT1 || ATP Trucks, ATP Bus |- | UWR || Robus Reșița |- | UZT || UTB (Uzina de Tractoare Brașov) |- | U1A || Sanos (North Macedonia) |- | U1V || VDL Van Hool Macedonia (North Macedonia) |- | U5Y || Kia Motors Slovakia |- | U59/AS0 || ASKO (truck trailer) |- | U6A || Granus (bus) (Slovakia) |- | U6Y || Kia Motors Slovakia |- | U69/M11 || Mobility & Innovation Production (bus) (Slovakia) |- | U69/NL1 || Novoplan (bus) (Slovakia) |- | U69/SB1 || SlovBus (bus) (Slovakia) |- | U69/TR8 || Troliga Bus (Slovakia) |- | VAG || Steyr-Daimler-Puch Puch G & Steyr-Puch Pinzgauer |- | VAH || Hangler (truck trailer) |- | VAK || Kässbohrer Transport Technik |- | VAN || MAN Austria/Steyr-Daimler-Puch Steyr Trucks |- | VAV || Schwarzmüller |- | VAX || Schwingenschlogel (truck trailer) |- | VA0 || ÖAF, Gräf & Stift |- | VA4 || KSR Group (motorcycle) |- | VA9/GS0 || Gsodam Fahrzeugbau (truck trailer) |- | VA9/RB1 || Rosenbauer International AG (truck) |- | VA9/ZT0 || Berger Fahrzeugtechnik (truck trailer) |- | VBF || Fit-Zel (trailer) |- | VBK || KTM |- | VBK || Husqvarna Motorcycles & Gas Gas under KTM ownership |- | VCF || Fisker Inc. (Fisker Ocean) made by Magna Steyr |- | VFA || Alpine (A310, A610, A110, A390), Renault Alpine GTA |- | VFG || Caravelair (caravans) |- | VFK || Fruehauf (truck trailers) |- | VFN || Trailor, General Trailers (truck trailers) |- | VF1 || Renault, Renault GTA '87-'90 (UK market Alpine GTA), Mobilize Duo, Eagle Medallion made by Renault,<br> Opel/Vauxhall Arena made by Renault, Mitsubishi ASX, Colt, Grandis, & Eclipse Cross EV made by Renault |- | VF2 || Renault Trucks |- | VF3 || Peugeot |- | VF4 || Talbot |- | VF5 || Iveco Unic |- | VF6 || Renault Trucks including vans made by Renault S.A. & Maxity truck made by Nissan Motor Ibérica S.A. |- | VF7 || Citroën |- | VF8 || Matra Automobiles (Talbot-Matra Murena, Rancho made by Matra, Renault Espace I/II/III, Avantime made by Matra) |- | VF9/024 || Legras Industries (truck trailer) |- | VF9/045 || Nardeau SAS (truck trailer) |- | VF9/049 || G. Magyar (truck trailer) |- | VF9/063 || Maisonneuve (truck trailer) |- | VF9/132 || Jean CHEREAU S.A.S. (truck trailer) |- | VF9/300 || EvoBus France |- | VF9/435 || Merceron (truck trailer) |- | VF9/519 || Hommell |- | VF9/607 || Mathieu (sweeper) |- | VF9/673 || Venturi Automobiles |- | VF9/795 || [[../Bugatti/VIN Codes|Bugatti Automobiles S.A.S.]] |- | VF9/848 || G. Magyar (truck trailer) |- | VF9/880 || Bolloré Bluebus |- | VF9/938 || SAFRA (bus) |- | VGA || Peugeot Motocycles |- | VGT || ASCA (truck trailers) |- | VGU || Trouillet (truck trailers) |- | VGW || BSLT (truck trailers) |- | VGX || Coder (truck trailers) |- | VGY || Lohr (truck trailers) |- | VG5 || MBK (motorcycles) & Yamaha Motor |- | VG6 || Renault Trucks & Mack Trucks medium duty trucks made by Renault Trucks |- | VG7 || Renault Trucks |- | VG8 || Renault Trucks |- | VG9/019 || Naya (autonomous vehicle) |- | VG9/061 || Alstom-NTL Aptis (bus) |- | VHR || Robuste (truck trailer) |- | VHX || Manitowoc Cranes - Potain |- | VH1 || Benalu SAS (truck trailer) |- | VH8 || Microcar |- | VJR || Ligier |- | VJY || Gruau |- | VJ1 || Heuliez Bus |- | VJ2 || Mia Electric |- | VJ4 || Gruau |- | VKD || Cheval Liberté (horse trailer) |- | VK1 || SEG (truck trailer) |- | VK2 || Grandin Automobiles |- | VK8 || Venturi Automobiles |- | VLG || Aixam-Mega |- | VLU || Scania France |- | VL4 || Bluecar, Citroen E-Mehari |- | VMK || Renault Sport Spider |- | VMS || Automobiles Chatenet |- | VMT || SECMA |- | VMW || Gépébus Oréos 55 |- | VM3 || Lamberet (trailer) |- | VM3 || Chereau (truck trailer) |- | VN1 || Renault SOVAB (France), Opel/Vauxhall Movano A made at SOVAB |- | VN4 || Voxan |- | VNB || Sherco Motorcycles SARL |- | VNE || IVECO Bus/Irisbus (France) |- | VNK || [[../Toyota/VIN Codes|Toyota]] Motor Manufacturing France & '11-'13 Daihatsu Charade (XP90) made by TMMF |- | VNV || Nissan made in France by Renault |- | VPG || MPM Motors |- | VPL || Nosmoke S.A.S |- | VP3 || G. Magyar (truck trailers) |- | VRW || Goupil |- | VR1 || DS Automobiles |- | VR3 || Peugeot (under Stellantis) |- | VR7 || Citroën (under Stellantis) |- | VSA || Mercedes-Benz Spain |- | VSC || Talbot |- | VSE || Santana Motors (Land Rover Series-based models) & Suzuki SJ/Samurai, Jimny, & Vitara made by Santana Motors in Spain |- | VSF || Santana Motors (Anibal/PS-10, 300/350) |- | VSK || Nissan Motor Iberica SA, Nissan passenger car/MPV/van/SUV/pickup & Ford Maverick 1993–1999 |- | VSR || Leciñena (truck trailers) |- | VSS || SEAT/Cupra |- | VSX || Opel Spain |- | VSY || Renault V.I. Spain (bus) |- | VS1 || Pegaso |- | VS5 || Renault Spain |- | VS6 || [[../Ford/VIN Codes|Ford]] Spain |- | VS7 || Citroën Spain |- | VS8 || Peugeot Spain |- | VS9/001 || Setra Seida (Spain) |- | VS9/011 || Advanced Design Tramontana |- | VS9/013 || Mirofret (truck trailer) (Spain) |- | VS9/016 || Irizar bus (Spain) |- | VS9/019 || Cobos Hermanos (truck trailer) (Spain) |- | VS9/031 || Carrocerias Ayats (Spain) |- | VS9/032 || Parcisa (truck trailer) (Spain) |- | VS9/044 || Beulas bus (Spain) (Spain) |- | VS9/047 || Indox (truck trailers) (Spain) |- | VS9/052 || Montull (truck trailer) (Spain) |- | VS9/057 || SOR Ibérica (truck trailers) (Spain) |- | VS9/072 || Mecanicas Silva (truck trailer) (Spain) |- | VS9/098 || Sunsundegui bus (Spain) |- | VS9/172 || EvoBus Iberica |- | VS9/917 || Nogebus (Spain) |- | VTD || Montesa Honda (Honda Montesa motorcycle models) |- | VTH || Derbi (motorcycles) |- | VTL || Yamaha Spain (motorcycles) |- | VTM || Montesa Honda (Honda motorcycle models) |- | VTP || Rieju S.A. (motorcycles) |- | VTR || Gas Gas |- | VTT || Suzuki Spain (motorcycles) |- | VVC || SOR Ibérica (truck trailers) |- | VVG || Tisvol (truck trailers) |- | VV1 || Lecitrailer Group (truck trailers) |- | VV5 || Prim-Ball (truck trailers) |- | VV9/ || [[wikipedia:Tauro Sport Auto|TAURO]] Sport Auto Spain |- | VV9/010 || Castrosúa bus (Spain) |- | VV9/125 || Indetruck (truck trailers) |- | VV9/130 || Vectia Mobility bus (Spain) |- | VV9/130 || UNVI bus (Spain) |- | VV9/359|| Hispano-Suiza |- | VWA || Nissan Vehiculos Industriales SA, Nissan Commercial Vehicles |- | VWF || Guillén Group (truck trailers) |- | VWL || Indox (truck trailers) |- | VWV || Volkswagen Spain |- | VXE || Opel Automobile Gmbh/Vauxhall van |- | VXF || Fiat van (Fiat Scudo, Ulysse '22-) (Stellantis) |- | VXK || Opel Automobile Gmbh/Vauxhall car/SUV |- | VXY || Neobus a.d. (Serbia) |- | VX1 || [[w:Zastava Automobiles|Zastava Automobiles]] / [[w:Yugo|Yugo]] (Yugoslavia/Serbia) |- | VYC || Lancia Ypsilon (4th gen.) (Stellantis) |- | VYE || Jeep Compass (3rd gen. - EU market '26-) (Stellantis) |- | VYF || Fiat Doblo '23- & Fiat Topolino '23- & Fiat Grande Panda '25- (Stellantis) |- | VYJ || Ram 1200 '25- (sold in Mexico) (Stellantis) |- | VYS || Renault & Alpine made by Ampere (Renault 5 E-Tech, Renault 4 E-Tech, Alpine A290) |- | VZ2 || Avtomontaža (bus) (Slovenia) |- | V1Y || FAS Sanos bus (Yugoslavia/North Macedonia) |- | V2X || Ikarbus a.d. (Serbia) |- | V31 || Tvornica Autobusa Zagreb (TAZ) (Croatia) |- | V34 || Crobus bus (Croatia) |- | V39/AB8 || Rimac Automobili (Croatia) |- | V39/CB3 || Eurobus (Croatia) |- | V39/WB4 || Rasco (machinery) (Croatia) |- | V6A || Bestnet AS; Tiki trailers (Estonia) |- | V6B || Brentex-Trailer (Estonia) |- | V6T || Verge Motorcycles (Estonia) |- | V61 || Respo Trailers (Estonia) |- | WAC || Arge Audi Porsche (Audi/Porsche RS2 Avant) |- | WAF || Ackermann (truck trailer) |- | WAG || Neoplan |- | WAP || Alpina |- | WAU || Audi car |- | WA1 || Audi SUV |- | WBA || BMW car |- | WBC || Boom Trikes |- | WBJ || Bitter Cars |- | WBK || Böcker Maschinenwerke GmbH |- | WBL || Blumhardt (truck trailers) |- | WBS || BMW M car |- | WBU || Bürstner (caravans) |- | WBX || BMW SUV |- | WBY || BMW i car |- | WB0 || Böckmann Fahrzeugwerke GmbH (trailers) |- | WB1 || BMW Motorrad |- | WB2 || Blyss (trailer) |- | WB3 || BMW Motorrad Motorcycles made in India by TVS |- | WB4 || BMW Motorrad Motorscooters made in China by Loncin |- | WB5 || BMW i SUV |- | WCD || Freightliner Sprinter "bus" (van with more than 3 rows of seats) 2008–2019 |- | WCM || Wilcox (truck trailer) |- | WDA || Mercedes-Benz incomplete vehicle (North America) |- | WDB || [[../Mercedes-Benz/VIN Codes|Mercedes-Benz]] & Maybach |- | WDC || Mercedes-Benz SUV |- | WDD || [[../Mercedes-Benz/VIN Codes|Mercedes-Benz]] car |- | WDF || [[../Mercedes-Benz/VIN Codes|Mercedes-Benz]] van/pickup (French & Spanish built models – Citan & Vito & X-Class) |- | WDP || Freightliner Sprinter incomplete vehicle 2005–2019 |- | WDR || Freightliner Sprinter MPV (van with 2 or 3 rows of seats) 2005–2019 |- | WDT || Dethleffs (caravans) |- | WDW || Dodge Sprinter "bus" (van with more than 3 rows of seats) 2008–2009 |- | WDX || Dodge Sprinter incomplete vehicle 2005–2009 |- | WDY || Freightliner Sprinter truck (cargo van with 1 row of seats) 2005–2019 |- | WDZ || Mercedes-Benz "bus" (van with more than 3 rows of seats) (North America) |- | WD0 || Dodge Sprinter truck (cargo van with 1 row of seats) 2005–2009 |- | WD1 || Freightliner Sprinter 2002 & Sprinter (Dodge or Freightliner) 2003–2005 incomplete vehicle |- | WD2 || Freightliner Sprinter 2002 & Sprinter (Dodge or Freightliner) 2003–2005 truck (cargo van with 1 row of seats) |- | WD3 || Mercedes-Benz truck (cargo van with 1 row of seats) (North America) |- | WD4 || Mercedes-Benz MPV (van with 2 or 3 rows of seats) (North America) |- | WD5 || Freightliner Sprinter 2002 & Sprinter (Dodge or Freightliner) 2003–2005 MPV (van with 2 or 3 rows of seats) |- | WD6 || Freightliner Unimog truck |- | WD7 || Freightliner Unimog incomplete vehicle |- | WD8 || Dodge Sprinter MPV (van with 2 or 3 rows of seats) 2005–2009 |- | WEB || Evobus GmbH (Mercedes-Benz buses) |- | WEG || Ablinger (trailer) |- | WEL || e.GO Mobile AG |- | WFB || Feldbinder Spezialfahrzeugwerke GmbH |- | WFC || Fendt (caravans) |- | WFD || Fliegl Trailer |- | WFN || Tadano Faun GmbH |- | WF0 || [[../Ford/VIN Codes|Ford]] Germany |- | WF1 || Merkur |- | WGB || Göppel Bus GmbH |- | WG0 || Goldhofer AG (truck trailer) |- | WHB || Hobby - Wohnwagenwerk, Ing. H. Striewski GmbH (recreational vehicles) |- | WHD || Humbaur GmbH (truck trailer) |- | WHL || Hulco (trailer) |- | WHW || Hako GmbH |- | WHY || Hymer GmbH & Co. KG (recreational vehicles) |- | WH7 || Hüfferman (truck trailer) |- | WJM || Iveco/Iveco Magirus |- | WJR || Irmscher |- | WKE || Krone (truck trailers) |- | WKK || Setra (Evobus GmbH; formerly Kässbohrer) |- | WKN || Knaus, Weinsberg (caravans) |- | WKV || Kässbohrer Fahrzeugwerke Gmbh (truck trailers) |- | WK0 || Kögel (truck trailers) |- | WLA || Langendorf semi-trailers |- | WLF || Liebherr (mobile crane) |- | WMA || MAN Truck & Bus |- | WME || smart (from 5/99) |- | WMG || Demag Cranes |- | WMM || Karl Müller GmbH & Co. KG (truck trailers) |- | WMP || M & V GmbH (truck trailers) |- | WMU || Hako GmbH (Multicar) |- | WMW || MINI car |- | WMX || Mercedes-AMG used for Mercedes-Benz SLS AMG & Mercedes-AMG GT & Mercedes-AMG One (not used in North America) |- | WMZ || MINI SUV |- | WNA || Next.e.GO Mobile SE |- | WP0 || Porsche car |- | WP1 || Porsche SUV |- | WRA || Renders (truck trailers) |- | WRJ || Riese & Müller (bicycle) |- | WSE || STEMA Metalleichtbau GmbH (trailers) |- | WSJ || STERK Trailers (truck trailers) |- | WSK || Schmitz-Cargobull Gotha (truck trailers) |- | WSM || Schmitz-Cargobull (truck trailers) |- | WSP || Spitzer (truck trailers) |- | WSV || Aebi Schmidt Group |- | WS5 || StreetScooter |- | WS7 || Sono Motors |- | WTA || Tabbert (caravans) |- | WUA || Audi Sport GmbH (formerly quattro GmbH) car <br> (includes '04-'09 S4 Cabriolet & '06 S4 25quattro Special Edition sedan & '16-'18 S8 Plus & non-North American mkt. Q7 V12 TDI) |- | WU1 || Audi Sport GmbH (formerly quattro GmbH) SUV |- | WVG || Volkswagen SUV & Touran & N. American mkt. ID Buzz '25 |- | WVM || Arbeitsgemeinschaft VW-MAN |- | WVP || Viseon Bus |- | WVW || Volkswagen passenger car, Sharan, Golf Plus, Golf Sportsvan |- | WV1 || Volkswagen Commercial Vehicles (cargo van or 1st gen. Amarok) |- | WV2 || Volkswagen Commercial Vehicles (passenger van or minibus) |- | WV3 || Volkswagen Commercial Vehicles (incomplete vehicle: chassis cab/cutaway)<br> [includes Winnebago Rialta ('97-'04), Winnebago Vista ('02-'04), Itasca Sunstar ('02-'04)] |- | WV4 || Volkswagen Commercial Vehicles (2nd gen. Amarok & T7 Transporter made by Ford) |- | WV5 || Volkswagen Commercial Vehicles (T7 Caravelle made by Ford) |- | WWA || Wachenhut (truck trailer) |- | WWC || WM Meyer (truck trailer) |- | WZ1 || Toyota Supra (Fifth generation for North America) |- | W0D || Obermaier (truck trailer) |- | W0L || Adam Opel AG/Vauxhall & Holden |- | W0L || Holden Zafira & Subaru Traviq made by GM Thailand |- | W0V || Opel Automobile Gmbh/Vauxhall & Holden (since 2017) |- | W04 || Buick Regal & Buick Cascada |- | W06 || Cadillac Catera |- | W08 || Saturn Astra |- | W09/A55 || Artega Automobile |- | W09/A71 || Apollo |- | W09/B09 || Bitter Cars |- | W09/B16 || Brabus |- | W09/B48 || Bultmann (trailer) |- | W09/B91 || Boerner (truck trailer) |- | W09/C09 || Carnehl Fahrzeugbau (truck trailer) |- | W09/D04 || DOLL (truck trailer) |- | W09/D05 || Drögmöller (bus) |- | W09/D17 || Dinkel (truck trailer) |- | W09/E04 || Eder (trailer) |- | W09/E27 || Esterer (truck trailer) |- | W09/E32 || ES-GE (truck trailer) |- | W09/E45 || Eurotank (truck trailer) |- | W09/F46 || FSN Fahrzeugbau (truck trailer) |- | W09/F57 || Twike |- | W09/G10 || GOFA (truck trailer) |- | W09/G64 || Gumpert |- | W09/H10 || Heitling Fahrzeugbau |- | W09/H21|| Dietrich Hisle GmbH (truck trailer) |- | W09/H46 || Hendricks (truck trailer) |- | W09/H49 || H&W Nutzfahrzeugtechnik GmbH (truck trailer) |- | W09/J02 || Isdera |- | W09/K27 || Krupp |- | W09/K27 || Kotschenreuther (truck trailer) |- | W09/L05 || Liebherr |- | W09/L06 || LMC Caravan (recreational vehicles) |- | W09/M08 || MEILLER Kipper (truck trailer) |- | W09/M09 || Meierling (truck trailer) |- | W09/M29 || MAFA (truck trailer) |- | W09/M40 || Franz Mersch (trailer) |- | W09/M79 || MKF Matallbau (truck trailer) |- | W09/N22 || NFP-Eurotrailer (truck trailer) |- | W09/P13 || Pagenkopf (truck trailer) |- | W09/P72 || De Tomaso Automobili (Capricorn) |- | W09/R06 || RUF |- | W09/R14 || Rancke (truck trailer) |- | W09/R27 || Gebr. Recker Fahrzeugbau (truck trailer) |- | W09/R30 || Reisch (truck trailer) |- | W09/R38 || Rewaco |- | W09/SG0 || Sileo (bus) |- | W09/SG1 || SEKA (truck trailer) |- | W09/S24 || Sommer (truck trailer) |- | W09/S25 || Spermann (truck trailer) |- | W09/S27 || Schröder (truck trailer) |- | W09/W11 || Wilken (truck trailer) |- | W09/W14 || Weka (truck trailer) |- | W09/W16 || Wellmeyer (truck trailer) |- | W09/W20 || Kurt Willig GmbH & Co. KG (truck trailer) |- | W09/W29 || Wiese (truck trailer) |- | W09/W35 || Wecon GmbH (truck trailer) |- | W09/W46 || WT-Metall (trailer) |- | W09/W59 || Wiesmann |- | W09/W70 || Wüllhorst (truck trailer) |- | W09/W86 || Web Trailer GmbH (truck trailer) |- | W09/004 || ORTEN Fahrzeugbau (truck trailer) |- | W1A || smart |- | W1H || Freightliner Econic |- | W1K || Mercedes-Benz car |- | W1N || Mercedes-Benz SUV |- | W1T || Mercedes-Benz truck |- | W1V || Mercedes-Benz van |- | W1W || Mercedes-Benz MPV (van with 2 or 3 rows of seats) (North America) |- | W1X || Mercedes-Benz incomplete vehicle (North America) |- | W1Y || Mercedes-Benz truck (cargo van with 1 row of seats) (North America) |- | W1Z || Mercedes-Benz "bus" (van with more than 3 rows of seats) (North America) |- | W2W || Freightliner Sprinter MPV (van with 2 or 3 rows of seats) |- | W2X || Freightliner Sprinter incomplete vehicle |- | W2Y || Freightliner Sprinter truck (cargo van with 1 row of seats) |- | W2Z || Freightliner Sprinter "bus" (van with more than 3 rows of seats) |- | XDN || Mercedes Sprinter Classic made by GAZ (Russia) |- | XD2 || CTTM Cargoline (truck trailer) (Russia) |- | XEA || AmberAvto (Avtotor) (Russia) |- | XE2 || AMKAR Automaster (truck trailer) (Russia) |- | XF9/B24 || NK Trailers (truck trailer) (Greece) |- | XF9/D44 || Militsis (trailer) (Greece) |- | XF9/J03 || Christos Nezis (truck trailer) (Greece) |- | XF9/J63 || Kaoussis (truck trailer) (Greece) |- | XG3 || Petros Petropoulos Group - Ecoshift NOOS electric motorscooters (Greece) |- | XG4|| Mpitis (trailer) (Greece) |- | XG5 || Stavropoulos trailers (Greece) |- | XG6 || MGK Hellenic Motor motorcycles (Greece) |- | XG8 || Gorgolis SA motorcycles (Greece) |- | XG9/B01 || Sfakianakis bus Greece |- | XG9/H33 || Rappas Trailer (Greece) |- | XG9/H51 || Eurotrailer Tourlakopoulos (trailer) (Greece) |- | XG9/H92 || Diamantis N. & Co. (trailer) (Greece) |- | XΗ9/B21 || Hellenic Vehicle Industry - ELVO bus Greece |- | XH9/H08 || Poseidonas Litsakis (trailer) (Greece) |- | XH9/H34 || Flexi-Wheels (trailer) (Greece) |- | XJY || Bonum (truck trailer) (Russia) |- | XJ4 || PKTS (PK Transportnye Sistemy) bus (Russia) |- | XKM || Volgabus (Russia) |- | XLA || DAF Bus International |- | XLB || Volvo Car B.V./NedCar B.V. (Volvo Cars) |- | XLC || [[../Ford/VIN Codes|Ford]] Netherlands |- | XLD || Pacton Trailers B.V. |- | XLE || Scania Netherlands |- | XLH || Hapert (trailer) |- | XLJ || Anssems (trailer) |- | XLK || Burg Trailer Service BV (truck trailer) |- | XLR || DAF Trucks & Leyland DAF |- | XLU || Henra (trailer) |- | XLV || DAF Bus |- | XLW || Terberg Benschop BV |- | XL3 || Ebusco |- | XL4 ||Lightyear |- | XL9/001 || ESVE BV (truck trailers) |- | XL9/002 || Jumbo Groenewegen (truck trailers) |- | XL9/003 || Autobusfabriek Bova BV |- | XL9/004 || G.S. Meppel (truck trailers) |- | XL9/007|| Broshuis BV (truck trailer) |- | XL9/010|| Ginaf Trucks |- | XL9/014 || Contar (truck trailer) |- | XL9/017 || Van Eck (truck trailer) |- | XL9/021 || Donkervoort Cars |- | XL9/033 || Wijer (trailer) |- | XL9/039 || Talson (truck trailer) |- | XL9/042 || Den Oudsten Bussen |- | XL9/052 || Witteveen (trailer) |- | XL9/055 || Fripaan (truck trailer) |- | XL9/067 || HTF (truck trailer) |- | XL9/068 || Vogelzang (truck trailer) |- | XL9/069 || Kraker (truck trailer) |- | XL9/070 || Veldhuizen (truck trailers) |- | XL9/073 || Zwalve (truck trailers) |- | XL9/074 || Draco (truck trailers) |- | XL9/081 || EBO van Weel (truck trailers) |- | XL9/084 || Vocol (truck trailers) |- | XL9/089 || Meijvo (trailers) |- | XL9/092 || Bulthuis (truck trailers) |- | XL9/103 || D-TEC (truck trailers) |- | XL9/109|| Groenewold Carrosseriefabriek B.V. (car transporter) |- | XL9/150 || Univan (truck trailer) |- | XL9/251 || Spierings Mobile Cranes |- | XL9/320 || VDL Bova bus |- | XL9/348 || HOKA (trailer) |- | XL9/355 || Berdex (truck trailer) |- | XL9/363 || Spyker |- | XL9/423 || Tijhof (trailer) |- | XL9/461 || BK Market Trailers (trailer) |- | XL9/495 || BE-Combi (truck trailer) |- | XL9/508 || Talson (truck trailer) |- | XL9/527 || GINAF |- | XL9/530 || Ebusco |- | XL9/611 || Zocon (trailer) |- | XMC || NedCar B.V. Mitsubishi Motors (LHD) |- | XMD || NedCar B.V. Mitsubishi Motors (RHD) |- | XMG || VDL Bus International |- | XMR || Nooteboom Trailers |- | XM4 || RAVO Holding B.V. (sweeper) |- | XNB || NedCar B.V. Mitsubishi Motors made by Pininfarina (Colt CZC convertible - RHD) |- | XNC || NedCar B.V. Mitsubishi Motors made by Pininfarina (Colt CZC convertible - LHD) |- | XNJ || Broshuis (truck trailer) |- | XNL || VDL Bus & Coach |- | XNT || Pacton Trailers B.V. (truck trailer) |- | XN1 || Kraker Trailers Axel B.V. (truck trailer) |- | XPN || Knapen Trailers |- | XPP || Atec Trailers |- | XP7 || Tesla Europe (based in the Netherlands) (Gigafactory Berlin-Brandenburg) |- | XRP || Proline (trailer) |- | XRY || D-TEC (truck trailer) |- | XR7 || Qarry |- | XTA || Lada / AvtoVAZ (Russia) |- | XTB || Moskvitch / AZLK (Russia) |- | XTC || KAMAZ (Russia) |- | XTD || LuAZ (Ukraine) |- | XTE || ZAZ (Ukraine) |- | XTF || GolAZ (Russia) |- | XTH || GAZ (Russia) |- | XTJ || Lada Oka made by SeAZ (Russia) |- | XTK || IzhAvto (Russia) |- | XTM || MAZ (Belarus); used until 1997 |- | XTP || Ural (Russia) |- | XTS || ChMZAP (truck trailer) |- | XTT || UAZ / Sollers (Russia) |- | XTU || Trolza, previously ZiU (Russia) |- | XTW || LAZ (Ukraine) |- | XTY || LiAZ (Russia) |- | XTZ || ZiL (Russia) |- | XUF || General Motors Russia |- | XUS || Nizhegorodets (minibus) (Russia) |- | XUU || Avtotor (Russia, Chevrolet Korea SKD, Kaiyi Auto) |- | XUV || Avtotor (DFSK, SWM) |- | XUZ || InterPipeVAN (truck trailer) |- | XU6 || Avtodom (minibus) (Russia) |- | XVG || MARZ (bus) (Russia) |- | XVU || Start (truck trailer) |- | XWB || UZ-Daewoo/GM Uzbekistan/Ravon/UzAuto Motors (Uzbekistan) |- | XWD || Avtotor (Russia, BAIC SKD) |- | XWE || Avtotor (Russia, Hyundai-Kia SKD) |- | XWF || Avtotor (Russia, Chevrolet Tahoe/Opel/Cadillac/Hummer SKD) |- | XWK || Kia assembled in Russia by IzhAvto |- | XW7 || Toyota Motor Manufacturing Russia |- | XW8 || Volkswagen Group Russia (VW, Skoda) |- | XX3 || Ujet Manufacturing (Luxembourg) |- | XZB || SIMAZ (bus) (Russia) |- | XZE || Specpricep (truck trailer) |- | XZG || Great Wall Motor (Haval Motor Rus) |- | XZP || Gut Trailer (truck trailer) |- | XZT || FoxBus (minibus) (Russia) |- | X1D || RAF (Rīgas Autobusu Fabrika) (Latvia) |- | X1E || KAvZ (Russia) |- | X1F || NefAZ (Russia) |- | X1M || PAZ (Russia) |- | X1P || Ural (Russia) |- | X2L || Fox Trailer (truck trailer) (Russia) |- | X21 || Diesel-S (truck trailer) (Russia) |- | X4K || Volgabus (Volzhanin) (Russia) |- | X4T || Sommer (truck trailer) (Russia) |- | X4X || Avtotor (Russia, BMW SKD) |- | X5A || UralSpetzTrans (trailer) (Russia) |- | X6D || VIS-AVTO (Russia) |- | X6S || TZA (truck trailer) (Russia) |- | X7L || Renault AvtoFramos (1998-2014), Renault Russia (2014-2022), Moskvitch (2022-) (Russia) |- | X7M || [[../Hyundai/VIN Codes|Hyundai]] & Vortex (rebadged Chery) made by TagAZ (Russia) |- | X89/AD4 || ВМЗ (VMZ) bus |- | X89/BF8 || Rosvan bus |- | X89/CU2 || EvoBus Russland (bus) |- | X89/DJ2 || VMK (bus) |- | X89/EY4 || Brabill (minibus) |- | X89/FF6 || Lotos (bus) |- | X89/FY1 || Sherp |- | X8J || IMZ-Ural Ural Motorcycles |- | X8U || Scania Russia |- | X9F || Ford Motor Company ZAO |- | X9L || GM-AvtoVAZ (Chevrolet Niva & Viva) |- | X9N || Samoltor (minibus) |- | X9P || Volvo Vostok ZAO (Volvo Trucks) |- | X9W || Brilliance, Lifan made by Derways |- | X9X || Great Wall Motors |- | X96 || GAZ |- | X99/000 || Marussia |- | X90 || GRAZ (truck trailer) |- | X0T || Tonar (truck trailer) |- | YAF || Faymonville (special transport trailers) |- | YAG || Syma aanhangwagenbouw BV (trailers) |- | YAM || MAX Trailer (truck trailers) |- | YAR || Toyota Motor Europe (based in Belgium) used for Toyota ProAce, Toyota ProAce City and Toyota ProAce Max made by PSA/Stellantis |- | YA2 || Atlas Copco Group |- | YA5 || Renders (truck trailers) |- | YA9/ || Lambrecht Constructie NV (truck trailers) |- | YA9/111 || OVA (truck trailer) |- | YA9/121 || Atcomex (truck trailer) |- | YA9/128 || EOS (bus) |- | YA9/139 || ATM Maaseik (truck trailer) |- | YA9/168 || Forthomme s.a. (truck trailer) |- | YA9/169 || Automobiles Gillet |- | YA9/180 || EOS (bus) |- | YA9/191 || Stokota (truck trailers) |- | YA9/195 || Denolf & Depla (minibus) |- | YBC || Toyota Supra (Fifth generation for Europe) |- | YBD || Addax Motors |- | YBW || Volkswagen Belgium |- | YB1 || Volvo Trucks Belgium (truck) |- | YB2 || Volvo Trucks Belgium (bus chassis) |- | YB3 || Volvo Trucks Belgium (incomplete vehicle) |- | YB4 || LAG Trailers N.V. (truck trailer) |- | YB6 || Jonckheere (VDL Belgium) |- | YCM || Mazda Motor Logistics Europe (based in Belgium) used for European-market Mazda 121 made by Ford in UK |- | YC1 || Honda Belgium NV (motorcycle) |- | YC3 || Eduard Trailers |- | YD3 || Chateau Caravans (Belgium) |- | YE1 || Van Hool (trailers) (Belgium) |- | YE2 || Van Hool (buses) (Belgium) |- | YE6 || STAS (truck trailer) |- | YE7 || Turbo's Hoet (truck trailer) |- | YF1 || Närko (truck trailer) (Finland) |- | YF3 || NTM (truck trailer) (Finland) |- | YF9/050 || JYKI (truck trailer) (Finland) |- | YGU || JJ-Trailer (trailer) (Finland) |- |YG6 |Majava Group Oy; Majava trailers (Finland) |- | YH1 || Solifer (caravans) |- | YH2 || BRP Finland (Lynx snowmobiles) |- | YH4 || Fisker Automotive (Fisker Karma) built by Valmet Automotive |- | YK1 || Saab-Valmet Finland |- | YK2, YK7 || Sisu Auto |- | YK9/003 || Kabus (bus) |- | YK9/008 || Lahden Autokori (-2013), SOE Busproduction Finland (2014-2024) (bus) |- | YK9/016 || Linkker (bus) |- | YSC || Cadillac BLS (made by Saab) |- | YSM || Polestar cars |- | YSP || Volta Trucks AB |- | YSR || Polestar SUV |- | YS2 || Scania commercial vehicles (Södertälje factory) |- | YS3 || Saab cars |- | YS4 || Scania buses and bus chassis until 2002 (Katrineholm factory) |- | YS5 || OmniNova (minibus) |- | YS7 || Solifer (recreational vehicles) |- | YS9/KV1 || Backaryd (minibus) |- | YTN || Saab made by NEVS |- | YT7 || Kabe (recreational vehicles) |- | YT9/007 || Koenigsegg |- | YT9/034 || Carvia |- | YU1 || Fogelsta, Brenderup Group (trailer) |- | YU7 || Husaberg (motorcycles) |- | YVV || WiMa 442 EV |- | YV1 || [[../Volvo/VIN Codes|Volvo]] cars |- | YV2 || [[../Volvo/VIN Codes|Volvo]] trucks |- | YV3 || [[../Volvo/VIN Codes|Volvo]] buses and bus chassis |- | YV4 || [[../Volvo/VIN Codes|Volvo]] SUV |- | YV5 || [[../Volvo/VIN Codes|Volvo Trucks]] incomplete vehicle |- | YYB || Tysse (trailer) (Norway) |- | YYC || Think Nordic (Norway) |- | YY9/017 || Skala Fabrikk (truck trailer) (Norway) |- | Y29/005 || Buddy Electric (Norway) |- | Y3D || MTM (truck trailer) (Belarus) |- | Y3F || Lida Buses Neman (Belarus) |- | Y3J || Belkommunmash (Belarus) |- | Y3K || Neman Bus (Belarus) |- | Y3M || MAZ (Belarus) |- | Y3W || VFV built by Unison (Belarus) |- | Y39/047 || Altant-M (minibus) (Belarus) |- | Y39/051 || Bus-Master (minibus) (Belarus) |- | Y39/052 || Aktriya (minibus) (Belarus) |- | Y39/072 || Klassikbus (minibus) (Belarus) |- | Y39/074 || Alterra (minibus) (Belarus) |- | Y39/135 || EuroDjet (minibus) (Belarus) |- | Y39/240 || Alizana (minibus) (Belarus) |- | Y39/241 || RSBUS (minibus) (Belarus) |- | Y39/323 || KF-AVTO (minibus) (Belarus) |- | Y4F || [[../Ford/VIN Codes|Ford]] Belarus |- | Y4K || Geely / BelGee (Belarus) |- | Y6B || IVECO (Ukraine) |- | Y6D || ZAZ / AvtoZAZ, Chevrolet Lanos made by ZAZ (Ukraine) |- | Y6E || LAZ (Ukraine) |- | Y6J || Bogdan group (Ukraine) |- | Y6L || Bogdan group including buses, Lada, & Hyundai made by Bogdan (Ukraine) |- | Y6U || Škoda Auto made by Eurocar (Ukraine) |- | Y6W || PGFM (trailer) (Ukraine) |- | Y6Y || LEV (trailer) (Ukraine) |- | Y69/B19 || Stryi Avto (bus) (Ukraine) |- | Y69/B98 || VESTT (truck trailer) (Ukraine) |- | Y69/C49 || TAD (truck trailer) (Ukraine) |- | Y69/D75 || Barrel Dash (truck trailer) (Ukraine) |- | Y7A || KrAZ trucks (Ukraine) |- | Y7B || Bogdan group (Ukraine) |- | Y7C || Great Wall Motors, Geely made by KrASZ (Ukraine) |- | Y7D || GAZ made by KrymAvtoGAZ (Ukraine) |- | Y7F || Boryspil Bus Factory (BAZ) (Ukraine) |- | Y7S || Korida-Tech (trailer) (Ukraine) |- | Y7W || Geely made by KrASZ (Ukraine) |- | Y7X || ChRZ - Ruta (minibus) (Ukraine) |- | Y79/A23 || OdAZ (truck trailer) (Ukraine) |- | Y79/B21 || Everlast (truck trailer) (Ukraine) |- | Y79/B65 || Avtoban (trailer) (Ukraine) |- | Y8A || LAZ (Ukraine) |- | Y8H || UNV Leader (trailer) (Ukraine) |- | Y8S || Alekseevka Ximmash (truck trailer) |- | Y8X || GAZ Gazelle made by KrASZ (Ukraine) |- | Y89/A98 || VARZ (trailer) (Ukraine) |- | Y89/B75 || Knott (trailer) (Ukraine) |- | Y89/C65 || Electron (Ukraine) |- | Y9A || PAVAM (trailer) (Ukraine) |- | Y9H || LAZ (Ukraine) |- | Y9M || AMS (trailer) (Ukraine) |- | Y9T || Dnipro (trailer) (Ukraine) |- | Y9W || Pragmatec (trailer) (Ukraine) |- | Y9Z || Lada, Renault made in Ukraine |- | Y99/B32 || Santey (trailer) (Ukraine) |- | Y99/E21 || Zmiev-Trans (truck trailer) (Ukraine) |- | Y99/C79 || Electron (bus) (Ukraine) |- | ZAA || Autobianchi |- | ZAA || Alfa Romeo Junior 2024- |- | ZAC || Jeep Compass (2nd gen. - EU market '20-'25), Jeep Renegade, Dodge Hornet |- | ZAH || Rolfo SpA (car transporter) |- | ZAJ || Trigano SpA; Roller Team recreational vehicles |- | ZAM || [[../Maserati/VIN Codes|Maserati]] |- | ZAP || Piaggio/Vespa/Gilera |- | ZAR || Alfa Romeo car |- | ZAS || Alfa Romeo Alfasud & Sprint through 1989 |- | ZAS || Alfa Romeo SUV 2018- |- | ZAX || Zorzi (truck trailer) |- | ZA4 || Omar (truck trailer) |- | ZA9/A12 || [[../Lamborghini/VIN Codes|Lamborghini]] through mid-2003 (including LM002) |- | ZA9/A17 || Carrozzeria Luigi Dalla Via (bus) |- | ZA9/A18 || De Simon (bus) |- | ZA9/A33 || Antonelli / Bucher Schörling Italia (small truck / sweeper) |- | ZA9/A47 || Silver Car (truck trailer) |- | ZA9/B09 || Mauri Bus System |- | ZA9/B34 || Mistrall Siloveicoli (truck trailer) |- | ZA9/B45 || Bolgan (truck trailer) |- | ZA9/B49 || OMSP Macola (truck trailer) |- | ZA9/B95 || Carrozzeria Autodromo Modena (bus) |- | ZA9/C38 || Dulevo (sweeper) |- | ZA9/D38 || Cizeta Automobili SRL |- | ZA9/D39 || [[../Bugatti/VIN Codes|Bugatti Automobili S.p.A]] |- | ZA9/D50 || Italdesign Giugiaro |- | ZA9/E15 || Tecnobus Industries S.r.l. |- | ZA9/E73 || Sitcar (bus) |- | ZA9/E88 || Cacciamali (bus) |- | ZA9/F16 || OMT (truck trailer) |- | ZA9/F21 || FGM (truck trailer) |- | ZA9/F48 || Rampini Carlo S.p.A. (bus) |- | ZA9/F76 || Pagani Automobili S.p.A. |- | ZA9/G97 || EPT Horus (bus) |- | ZA9/H02 || O.ME.P.S. (truck trailer) |- | ZA9/H44|| Green-technik by Green Produzione s.r.l. (machine trailer) |- | ZA9/J21 || VRV (truck trailer) |- | ZA9/J93 || Barbi (bus) |- | ZA9/K98 || Esagono Energia S.r.l. |- | ZA9/M09 || Italdesign Automobili Speciali |- | ZA9/M27 || Dallara Stradale |- | ZA9/M91 || Automobili Pininfarina |- | ZA9/180 || De Simon (bus) |- | ZA0 || Acerbi (truck trailer) |- | ZBA || Piacenza (truck trailer) |- | ZBB || Bertone |- | ZBD || InBus |- | ZBN || Benelli |- | ZBW || Rayton-Fissore Magnum |- | ZB3 || Cardi (truck trailer) |- | ZCB || E. Bartoletti SpA (truck trailer) |- | ZCF || IVECO / Irisbus (Italy) |- | ZCG || Cagiva SpA / MV Agusta |- | ZCG || Husqvarna Motorcycles Under MV Agusta ownership |- | ZCM || BredaMenarinibus / Menarinibus / IIA (Industria Italiana Autobus) |- | ZCN || Astra Veicoli Industriali S.p.A. |- | ZCV || Vibreti (truck trailer) |- | ZCZ || BredaBus |- | ZC1 || AnsaldoBreda S.p.A. |- | ZC2 || Chrysler TC by Maserati |- | ZDC || Honda Italia Industriale SpA |- | ZDF || [[../Ferrari/VIN Codes|Ferrari]] Dino |- | ZDJ || ACM Biagini |- | ZDM || Ducati Motor Holdings SpA |- | ZDT || De Tomaso Modena SpA |- | ZDY || Cacciamali |- | ZD0 || Yamaha Motor Italia SpA & Belgarda SpA |- | ZD3 || Beta Motor |- | ZD4 || Aprilia |- | ZD5 || Casalini |- | ZEB || Ellebi (trailer) |- | ZEH || Trigano SpA (former SEA Group); McLouis & Mobilvetta recreational vehicles |- | ZES || Bimota |- | ZEX || TM Racing (motorcycle) |- | ZE5 || Carmosino (truck trailer) |- | ZFA || FIAT |- | ZFB || FIAT MPV/SUV & Ram Promaster City |- | ZFC || FIAT truck (FIAT Ducato for Mexico, RAM 1200) |- | ZFE || KL Motorcycle |- | ZFF || [[../Ferrari/VIN Codes|Ferrari]] |- | ZFJ || Carrozzeria Pezzaioli (truck trailer) |- | ZFM || Fantic Motor |- | ZFR || Pininfarina |- | ZF4 || Qvale |- | ZGA || IVECO Bus |- | ZGP || Merker (truck trailer) |- | ZGU || Moto Guzzi |- | ZG2 || FAAM (commercial vehicle) |- | ZHU || Husqvarna Motorcycles Under Cagiva ownership |- | ZHW || [[../Lamborghini/VIN Codes|Lamborghini]] (Mid-2003 – ) |- | ZHZ || Menci SpA (truck trailer) |- | ZH5 || FB Mondial (motorcycle) |- | ZJM || Malaguti |- | ZJN || Innocenti |- | ZJT || Italjet |- | ZKC || Ducati Energia Free Duck (electric quadricycle) |- | ZKH || Husqvarna Motorcycles Srl Under BMW ownership |- | ZLA || Lancia |- | ZLF || Tazzari GL SpA |- | ZLM || Moto Morini srl |- | ZLV || Laverda |- | ZNN || Energica |- | ZN0 || SWM Motorcycles S.r.l. |- | ZN3 || IVECO Defence |- | ZN6 || Maserati SUV |- | ZPB || [[../Lamborghini/VIN Codes|Lamborghini]] SUV |- | ZPY || DR Automobiles |- | ZP6 || XEV |- | ZP8 || Regis Motors |- | ZRG || Tazzari GL Imola SpA |- | ZR1 || Microlino |- | ZSG || [[../Ferrari/VIN Codes|Ferrari]] SUV |- | ZS1 || Leapmotor International B.V. |- | ZX1 || TAM (Tovarna Avtomobilov Maribor) bus (Slovenia) |- | ZX9/KU0 || K-Bus / Kutsenits (bus) (Slovenia) |- | ZX9/DUR || TAM bus (Slovenia) |- | ZX9/TV0 || TAM (Tovarna Vozil Maribor) bus (Slovenia) |- | ZY1 || Adria (recreational vehicles) (Slovenia) |- | ZY9/002 || Gorica (truck trailer) (Slovenia) |- | ZZ1 || Tomos motorcycle (Slovenia) |- | Z29/555 || Vozila FLuid (truck trailer) (Slovenia) |- | Z3D || Tauriga UAB; Tauras trailers (Lithuania) |- | Z39/008 || Autogalantas (truck trailer) (Lithuania) |- | Z39/009 || Patikima Linija / Rimo (truck trailer) (Lithuania) |- | Z6F || Ford Sollers (Russia) |- | Z7C || Luidor (bus) (Russia) |- | Z7N || KAvZ (bus) (Russia) |- | Z7T || RoAZ (bus) (Russia) |- | Z7X || Isuzu Rus (Russia) |- | Z76 || SEMAZ (Kazakhstan) |- | Z8M || Marussia (Russia) |- | Z8N || Nissan Manufacturing Rus & Nissan and Datsun models made by AvtoVAZ (Russia) |- | Z8P || IRITO |- | Z8T || PCMA Rus (Peugeot, Citroen, Mitsubishi) (Russia) |- | Z8U || [[w:SsangYong Korando#Third generation (C200; 2010)|Ssangyong Actyon]] made by Sollers (Russia) |- | Z8Y || Nasteviya (bus) (Russia) |- | Z9B || KuzbassAvto (Hyundai bus) (Russia) |- | Z9M || Mercedes-Benz Manufacturing Rus / Mercedes-Benz Trucks Vostok (Russia) |- | Z9N || Samotlor-NN (Iveco) (Russia) |- | Z94 || Hyundai Motor Manufacturing Rus (Hyundai, Kia) (2008-2023), Solaris Auto - AGR Automotive (2023-) (Russia) |- | Z07 || Volgabus (Russia) |- | 1A4 1A8 || Chrysler brand MPV/SUV 2006–2009 only |- | 1A9/007 || Advance Mixer Inc. |- | 1A9/111 || Amerisport Inc. (federalized late model DeTomaso Pantera) |- | 1A9/398 || Ameritech (federalized McLaren F1 & Bugatti EB110) |- | 1A9/569 || American Custom Golf Cars Inc. (AGC) |- | 1AC || American Motors Corporation MPV |- | 1AF || American LaFrance truck |- | 1AJ || Ajax Manufacturing (truck trailer) |- | 1AM || American Motors Corporation car & Renault Alliance 1983 only |- | 1BN || Beall Trailers (truck trailer) |- | 1B3 || Dodge car 1981–2011 |- | 1B4 || Dodge MPV/SUV 1981–2002 |- | 1B6 || Dodge incomplete vehicle 1981–2002 |- | 1B7 || Dodge truck 1981–2002 |- | 1B9/133 || Buell Motorcycle Company through mid-1995 |- | 1B9/274 || Brooks Brothers Trailers |- | 1B9/275 || Boydstun Metal Works (truck trailer) |- | 1B9/285 || Boss Hoss Cycles |- | 1B9/374 || Big Dog Custom Motorcycles through mid-2002 |- | 1B9/975 || Motus Motorcycles |- | 1BA || Blue Bird Corporation bus |- | 1BB || Blue Bird Wanderlodge MPV |- | 1BD || Blue Bird Corporation incomplete vehicle |- | 1BL || Balko, Inc. |- | 1C3 || Chrysler brand car 1981–2011 |- | 1C3 || Chrysler Group (all brands) car (including Lancia) 2012- |- | 1C4 || Chrysler brand MPV 1990–2005 |- | 1C4 || Chrysler Group (all brands) MPV 2012– |- | 1C6 || Chrysler Group (all brands) truck 2012– |- | 1C8 || Chrysler brand MPV 2001–2005 |- | 1C9/257 || CEI Equipment Company (truck trailer) |- | 1C9/291 || CX Automotive |- | 1C9/496 || Carlinville Truck Equipment (truck trailer) |- | 1C9/535 || Chance Coach (bus) |- | 1C9/737 || Corbin Motors, Inc. |- | 1C9/772 || Cozad (truck trailer) |- | 1C9/971 || Cool Amphibious Manufacturers International |- | 1CM || Checker Motors Corporation |- | 1CU || Cushman Haulster (Cushman division of Outboard Marine Corporation) |- | 1CY || Crane Carrier Company |- | 1CY || Battle Motors, Inc. |- | 1D3 || Dodge truck 2002–2009 |- | 1D4 || Dodge MPV/SUV 2003–2011 only |- | 1D7 || Dodge truck 2002–2011 |- | 1D8 || Dodge MPV/SUV 2003–2009 only |- | 1D9/008 || KME Fire Apparatus |- | 1D9/628 || Dymac Vehicle Group (low-speed vehicle) |- | 1D9/791 || Dennis Eagle, Inc. |- | 1DW || Stoughton Trailers (truck trailer) |- | 1E9/007 || E.D. Etnyre & Co. (truck trailer) |- | 1E9/190 || Electric Transit Inc. (trolleybus) |- | 1E9/363 || E-SUV LLC (E-Ride Industries) |- | 1E9/456 || Electric Motorsport (GPR-S electric motorcycle) |- | 1E9/526 || Epic TORQ |- | 1E9/581 || Vetter Razor |- | 1EU || Eagle Coach Corporation (bus) |- | 1FA || [[../Ford/VIN Codes|Ford]] car |- | 1FB || [[../Ford/VIN Codes|Ford]] "bus" (van with more than 3 rows of seats) |- | 1FC || [[../Ford/VIN Codes|Ford]] stripped chassis made by Ford |- | 1FD || [[../Ford/VIN Codes|Ford]] incomplete vehicle |- | 1FM || [[../Ford/VIN Codes|Ford]] MPV/SUV |- | 1FT || [[../Ford/VIN Codes|Ford]] truck |- | 1FU || Freightliner (truck) |- | 1FV || Freightliner (incomplete vehicle) |- | 1F1 || Ford SUV - Limousine (through 2009) |- | 1F6 || Ford stripped chassis made by Detroit Chassis LLC |- | 1F9/037 || Federal Motors Inc. |- | 1F9/140 || Ferrara Fire Apparatus (incomplete vehicle) |- | 1F9/458 || Faraday Future prototypes |- | 1F9/FT1 || FWD Corp. |- | 1F9/ST1 || Seagrave Fire Apparatus |- | 1F9/ST2 || Seagrave Fire Apparatus |- | 1G || [[../GM/VIN Codes|General Motors]] USA |- | 1G0 || GMC "bus" (van with more than 3 rows of seats) 1981–1986 |- | 1G0 || GMC Rapid Transit Series (RTS) bus 1981–1984 |- | 1G0 || Opel/Vauxhall car 2007–2017 |- | 1G1 || [[../GM/VIN Codes|Chevrolet]] car |- | 1G2 || [[../GM/VIN Codes|Pontiac]] car |- | 1G3 || [[../GM/VIN Codes|Oldsmobile]] car |- | 1G4 || [[../GM/VIN Codes|Buick]] car |- | 1G5 || GMC MPV/SUV 1981–1986 |- | 1G5 || Pontiac incomplete vehicle 1989-1990, 2003-2006 |- | 1G6 || [[../GM/VIN Codes|Cadillac]] car |- | 1G7 || Pontiac car only sold by GM Canada |- | 1G8 || Chevrolet MPV/SUV 1981–1986 |- | 1G8 || [[../GM/VIN Codes|Saturn]] car 1991–2010 |- | 1G9/492 || GreenPower Motor Company incomplete vehicle |- | 1G9/495 || Google & Waymo |- | 1GA || Chevrolet "bus" (van with more than 3 rows of seats) |- | 1GB || Chevrolet incomplete vehicle |- | 1GC || [[../GM/VIN Codes|Chevrolet]] truck |- | 1GD || GMC incomplete vehicle |- | 1GE || Cadillac incomplete vehicle |- | 1GF || Flxible bus |- | 1GG || Isuzu pickup trucks made by GM |- | 1GH || GMC Rapid Transit Series (RTS) bus 1985–1986 |- | 1GH || Oldsmobile MPV/SUV 1990–2004 |- | 1GH || Holden Acadia 2019–2020 |- | 1GJ || GMC "bus" (van with more than 3 rows of seats) 1987– |- | 1GK || GMC MPV/SUV 1987– |- | 1GM || [[../GM/VIN Codes|Pontiac]] MPV |- | 1GN || [[../GM/VIN Codes|Chevrolet]] MPV/SUV 1987- |- | 1GR || Great Dane Trailers (truck trailer) |- | 1GT || [[../GM/VIN Codes|GMC]] Truck |- | 1GW || Grumman Olson Kubvan (truck) |- | 1GY || [[../GM/VIN Codes|Cadillac]] SUV |- | 1HA || Chevrolet incomplete vehicles (Express cutaway) made by Navistar International/International Motors |- | 1HD || Harley-Davidson & LiveWire |- | 1HF || Honda motorcycle/ATV/UTV |- | 1HG || [[../Honda/VIN Codes|Honda]] car made by Honda of America Mfg. in Ohio |- | 1HP || International Trucks (complete vehicle - straight truck) |- | 1HS || International Trucks & Caterpillar Trucks (complete vehicle - truck tractor) |- | 1HT || International Trucks & Caterpillar Trucks & Chevrolet Silverado 4500HD, 5500HD, 6500HD (incomplete vehicle - straight truck) |- | 1HV || International or IC Bus (incomplete vehicle - bus) |- | 1H9/484 || Hughes Trailers (Based in Canyon, TX) (trailer) |- | 1H9/674 || Hines Specialty Vehicle Group |- | 1JC || Jeep SUV 1981–1988 (using AMC-style VIN structure) |- | 1JJ || Wabash (truck trailer) |- | 1JT || Jeep truck 1981–1988 (using AMC-style VIN structure) |- | 1JU || Marmon Motor Company (truck) |- | 1J4 || Jeep SUV 1989–2011 (using Chrysler-style VIN structure) |- | 1J7 || Jeep truck 1989–1992 (using Chrysler-style VIN structure) |- | 1J8 || Jeep SUV 2002–2011 (using Chrysler-style VIN structure) |- | 1KB || Holiday Rambler Corp. 1981-2010 (trailer) |- | 1K9/058 || Kovatech Mobile Equipment (fire engine) |- | 1LH || Landoll (truck trailer) |- | 1LJ || Lincoln incomplete vehicle |- | 1LN || [[../Ford/VIN Codes|Lincoln]] car |- | 1LV || Lectra Motors |- | 1L0 || Lufkin Trailers |- | 1L1 || Lincoln car – limousine |- | 1L9/155 || LA Exotics |- | 1L9/234 || Laforza |- | 1MB || Mercedes-Benz Truck Co. |- | 1ME || [[../Ford/VIN Codes|Mercury]] car |- | 1MR || Continental Mark VI & VII 1981–1985 & Continental sedan 1982–1985 |- | 1M0 || John Deere Gator |- | 1M1 || Mack Truck USA (truck) |- | 1M2 || Mack Truck USA (incomplete vehicle) |- | 1M3 || Mack Truck USA (glider) |- | 1M8 || Motor Coach Industries (bus) |- | 1M9/089 || Mauck Special Vehicles (bus) |- | 1M9/682 || Mosler Automotive |- | 1M9/816 || Proterra Through mid-2019 |- | 1N4 || Nissan car |- | 1N6 || Nissan truck |- | 1N9/019 || Neoplan USA |- | 1N9/084 || Eldorado National (California) |- | 1N9/140 || North American Bus Industries (bus) |- | 1N9/393 || Nikola Corporation (truck) |- | 1NK || Kenworth (incomplete vehicle) |- | 1NL || Gulf Stream Coach (recreational vehicles) |- | 1NN || Monon made by Evans Products Co. (truck trailer) |- | 1NP || Peterbilt (incomplete vehicle) |- | 1NX || Toyota car made by NUMMI |- | 1P3 || Plymouth car |- | 1P4 || Plymouth MPV/SUV |- | 1P7 || Plymouth Scamp |- | 1P9/038 || Hawk Vehicles, Inc. (Trihawk motorcycles) |- | 1P9/213 || Panoz |- | 1P9/255 || Pinson Truck Equipment Company (truck trailer) |- | 1PM || Polar Tank Trailer (truck trailer) |- | 1PT || Trailmobile Trailer Corporation (truck trailer) |- | 1PY || John Deere USA |- | 1RF || Roadmaster, Monaco Coach Corporation (incomplete vehicle) |- | 1RN || Reitnouer (truck trailer) |- | 1R9/956 || Reede Fabrication and Design (motorcycles) |- | 1ST || Airstream (recreational vehicles) |- | 1S1 || Strick Trailers (truck trailer) |- | 1S9/003 || Sutphen Corporation (fire engines - truck) |- | 1S9/009|| Superior Trailer Works (truck trailer) |- | 1S9/098 || Scania AB (Scania CN112 bus made in Orange, CT) |- | 1S9/842 || Saleen S7 |- | 1S9/260 || Stairs Welding RL (truck trailer) |- | 1S9/901 || Suckerpunch Sallys, LLC |- | 1S9/944 || SSC North America |- | 1TD || Timpte (truck trailer) |- | 1TK || Trail King (truck trailer) |- | 1TD || Transcraft Corporation (truck trailer) |- | 1T7 || Thomas Built Buses |- | 1T8 || Thomas Built Buses |- | 1T9/072 || The Trailer Co. (truck trailer) |- | 1T9/717 || Thunder Mountain Custom Cycles |- | 1T9/825 || TICO Manufacturing Company (truck) |- | 1T9/899 || Tomcar USA |- | 1T9/970 || Three Two Chopper |- | 1TC || Coachmen Recreational Vehicle Co., LLC |- | 1TU || Transportation Manufacturing Corporation |- | 1UJ || Jayco, Inc. |- | 1UT || AM General military trucks, Jeep DJ made by AM General |- | 1UY || Utility Trailer (truck trailer) |- | 1VH || Orion Bus Industries |- | 1VW || Volkswagen car |- | 1V1 || Volkswagen truck |- | 1V2 || Volkswagen SUV |- | 1V9/048 || Vector Aeromotive |- | 1V9/113 || Vantage Vehicle International Inc (low-speed vehicle) |- | 1V9/190 || Vanderhall Motor Works |- | 1WA || White Motor Company (Autocar brand truck) |- | 1WB || White Motor Company (Autocar brand incomplete vehicle) |- | 1WD || White Motor Company (Autocar brand glider) |- | 1WT || Winnebago Industries: Winnebago M.P.V. |- | 1WU || White Motor Company (White brand truck) |- | 1WV || Winnebago Industries: Winnebago M.P.V. - Class C Motorhome built on VW chassis & front cab [Winnebago Rialta ('95-'96)] |- | 1WW || Winnebago Industries: Winnebago M.P.V. - Class B Motorhome built on Renault chassis [Winnebago LeSharo, Centauri, Itasca Phasar] |- | 1WX || White Motor Company (White brand incomplete vehicle) |- | 1WY || White Motor Company (White brand glider) |- | 1W1 || Wilson Trailer Co. (truck trailer) |- | 1W5 || Western Recreational Vehicles (Alpenlite) |- | 1W8 || Witzco (truck trailer) |- | 1W9/010 || Weld-It Company (truck trailer) |- | 1W9/485 || Wheego Electric Cars |- | 1W9/488 || Certified Stainless Services Inc. DBA West-Mark (truck trailer) (2010 & later) |- | 1XA || Excalibur Automobile Corporation |- | 1XK || Kenworth (truck) |- | 1XM || Renault Alliance/GTA/Encore 1984–1987 |- | 1XP || Peterbilt (truck) |- | 1Y1 || Chevrolet/Geo car made by NUMMI |- | 1YJ || Rokon International, Inc. |- | 1YV || [[../Ford/VIN Codes|Mazda made by Mazda Motor Manufacturing USA/AutoAlliance International]] |- | 1ZV || [[../Ford/VIN Codes|Ford made by Mazda Motor Manufacturing USA/AutoAlliance International]] |- | 1ZW || [[../Ford/VIN Codes|Mercury made by AutoAlliance International]] |- | 1Z3 1Z7 || Mitsubishi Raider |- | 1Z9/170 || [[w:Orange County Choppers|Orange County Choppers]] |- | 10B || Brenner Tank (truck trailer) |- | 10R || E-Z-GO |- | 10T || Oshkosh Corporation |- | 11H || Hendrickson Mobile Equipment, Inc. (fire engines - incomplete vehicle) |- | 11V || Kalmar Solutions (Truck - Terminal Tractor) |- | 12A || Avanti |- | 137 || AM General Hummer & Hummer H1 |- | 13N || Fontaine (truck trailer) |- | 15G || Gillig bus |- | 16C || Clenet Coachworks |- | 16W || Certified Stainless Services Inc. DBA West-Mark (truck trailer) (prior to 2010) |- | 16X || Vixen 21 motorhome |- | 17N || John Deere incomplete vehicle (RV chassis) |- | 18X || Western Recreational Vehicles |- | 19U || Acura car made by Honda of America Mfg. in Ohio |- | 19V || Acura car made by Honda Manufacturing of Indiana |- | 19X || Honda car made by Honda Manufacturing of Indiana |- | 2A3 || Imperial |- | 2A4 2A8 || Chrysler brand MPV/SUV 2006–2011 only |- | 2AY 2AZ || Hino |- | 2BC || Jeep Wrangler (YJ) 1987–1988 (using AMC-style VIN structure) |- | 2BP || Ski-Doo |- | 2BV || Can-Am & Bombardier ATV |- | 2BW || Can-Am Commander E LSV |- | 2BX || Can-Am Spyder & Canyon 3-wheelers |- | 2BZ || Can-Am Freedom Trailer for Can-Am Spyder & Canyon |- | 2B1 || Orion Bus Industries |- | 2B3 || Dodge car 1981–2011 |- | 2B4 || Dodge MPV 1981–2002 |- | 2B5 || Dodge "bus" (van with more than 3 rows of seats) 1981–2002 |- | 2B6 || Dodge incomplete vehicle 1981–2002 |- | 2B7 || Dodge truck 1981–2002 |- | 2B9/001 || BWS Manufacturing (truck trailer) |- | 2C1 || Geo/Chevrolet car made by CAMI Automotive |- | 2C3 || Chrysler brand car 1981–2011 |- | 2C3 || Chrysler Group (all brands) car (including Lancia) 2012- |- | 2C4 || Chrysler brand MPV/SUV 2000–2005 |- | 2C4 || Chrysler Group (all brands) MPV (including Lancia Voyager & Volkswagen Routan) 2012- |- | 2C7 || Pontiac car made by CAMI Automotive only sold by GM Canada |- | 2C8 || Chrysler brand MPV/SUV 2001–2005 |- | 2C9/145 || Campagna Motors |- | 2C9/197 || Canadian Electric Vehicles |- | 2CC || American Motors Corporation MPV |- | 2CG || Asüna/Pontiac SUV made by CAMI Automotive only sold by GM Canada |- | 2CK || GMC Tracker SUV made by CAMI Automotive only sold by GM Canada 1990–1991 only |- | 2CK || Pontiac Torrent SUV made by CAMI Automotive 2006–2009 only |- | 2CM || American Motors Corporation car |- | 2CN || Geo/Chevrolet SUV made by CAMI Automotive 1990–2011 only |- | 2CT || GMC Terrain SUV made by CAMI Automotive 2010–2011 only |- | 2D4 || Dodge MPV 2003–2011 only |- | 2D6 || Dodge incomplete vehicle 2003 |- | 2D7 || Dodge truck 2003 |- | 2D8 || Dodge MPV 2003–2011 only |- | 2DG || Ontario Drive & Gear |- | 2DM || Di-Mond Trailers (truck trailer) |- | 2DN || Dynasty Electric Car Corporation |- | 2EZ || Electra Meccanica Vehicles Corp. (Solo) |- | 2E3 || Eagle car 1989–1997 (using Chrysler-style VIN structure) |- | 2E4 || 2011 Lancia MPV (Voyager) |- | 2E9/080 || Electra Meccanica Vehicles Corp. (Solo) |- | 2FA || [[../Ford/VIN Codes|Ford]] car |- | 2FH || Zenn Motor Co., Ltd. (low-speed vehicle) |- | 2FM || [[../Ford/VIN Codes|Ford]] MPV/SUV |- | 2FT || [[../Ford/VIN Codes|Ford]] truck |- | 2FU || Freightliner (truck) |- | 2FV || Freightliner (incomplete vehicle) |- | 2FW || Sterling Trucks (truck-complete vehicle) |- | 2FY || New Flyer |- | 2FZ || Sterling Trucks (incomplete vehicle) |- | 2Gx || [[../GM/VIN Codes|General Motors]] Canada |- | 2G0 || GMC "bus" (van with more than 3 rows of seats) 1981–1986 |- | 2G1 || [[../GM/VIN Codes|Chevrolet]] car |- | 2G2 || [[../GM/VIN Codes|Pontiac]] car |- | 2G3 || [[../GM/VIN Codes|Oldsmobile]] car |- | 2G4 || [[../GM/VIN Codes|Buick]] car |- | 2G5 || GMC MPV 1981–1986 |- | 2G5 || Chevrolet BrightDrop / BrightDrop Zevo truck 2023-2026 |- | 2G6 || [[../GM/VIN Codes|Cadillac]] car |- | 2G7 || Pontiac car only sold by GM Canada |- | 2G8 || Chevrolet MPV 1981–1986 |- | 2GA || Chevrolet "bus" (van with more than 3 rows of seats) |- | 2GB || Chevrolet incomplete vehicle |- | 2GC || Chevrolet truck |- | 2GD || GMC incomplete vehicle |- | 2GE || Cadillac incomplete vehicle |- | 2GH || GMC GM New Look bus & GM Classic series bus |- | 2GJ || GMC "bus" (van with more than 3 rows of seats) 1987– |- | 2GK || GMC MPV/SUV 1987– |- | 2GN || Chevrolet MPV/SUV 1987- |- | 2GT || GMC truck |- | 2HG || [[../Honda/VIN Codes|Honda]] car made by Honda of Canada Manufacturing |- | 2HH || Acura car made by Honda of Canada Manufacturing |- | 2HJ || [[../Honda/VIN Codes|Honda]] truck made by Honda of Canada Manufacturing |- | 2HK || [[../Honda/VIN Codes|Honda]] MPV/SUV made by Honda of Canada Manufacturing |- | 2HM || Hyundai Canada |- | 2HN || Acura SUV made by Honda of Canada Manufacturing |- | 2HP || International Trucks (complete vehicle - straight truck) |- | 2HS || International Trucks (complete vehicle - truck tractor) |- | 2HT || International Trucks (incomplete vehicle - straight truck) |- | 2HV || International or IC Bus (incomplete vehicle - bus) |- | 2J4 || Jeep Wrangler (YJ) 1989–1992 (using Chrysler-style VIN structure) |- | 2L1 || Lincoln incomplete vehicle – limo |- | 2LD || Triple E Canada Ltd. |- | 2LJ || Lincoln incomplete vehicle – hearse |- | 2LM || Lincoln SUV |- | 2LN || Lincoln car |- | 2M1 || Mack Trucks Canada (truck) |- | 2M2 || Mack Trucks Canada (incomplete vehicle) |- | 2M3 || Mack Truck Canada (glider) |- | 2ME || [[../Ford/VIN Codes|Mercury]] car |- | 2MG || Motor Coach Industries (Produced from Sept. 1, 2008 on) |- | 2MH || [[../Ford/VIN Codes|Mercury]] incomplete vehicle |- | 2MR || [[../Ford/VIN Codes|Mercury]] MPV |- | 2M9/044 || Westward Industries |- | 2M9/058 || Motor Coach Industries |- | 2NK || Kenworth incomplete vehicle |- | 2NP || Peterbilt incomplete vehicle |- | 2NV || Nova Bus |- | 2P3 || Plymouth car |- | 2P4 || Plymouth MPV 1981–2000 |- | 2P5 || Plymouth "bus" (van with more than 3 rows of seats) 1981–1983 |- | 2P9/001 || Prevost 1981–1995 |- | 2PC || Prevost 1996- |- | 2S2 || Suzuki car made by CAMI Automotive |- | 2S3 || Suzuki SUV made by CAMI Automotive |- | 2TU || Tri-Star Industries Limited |- | 2T1 || [[../Toyota/VIN Codes|Toyota]] car made by TMMC |- | 2T2 || Lexus SUV made by TMMC |- | 2T3 || [[../Toyota/VIN Codes|Toyota]] SUV made by TMMC |- | 2T9/206 || Triple E Canada Ltd. |- | 2V4 || Volkswagen Routan made by Chrysler Canada |- | 2V8 || Volkswagen Routan made by Chrysler Canada |- | 2W9/044 || Westward Industries |- | 2WK || Western Star (truck) |- | 2WL || Western Star (incomplete vehicle) |- | 2WM || Western Star (glider) |- | 2XK || Kenworth (truck) |- | 2XM || Eagle Premier 1988 only (using AMC-style VIN structure) |- | 2XP || Peterbilt (truck) |- | 3A4 3A8 || Chrysler brand MPV 2006–2010 only |- | 3A9/050 || MARGO (truck trailer) |- | 3AK || Freightliner Trucks (truck) |- | 3AL || Freightliner Trucks (incomplete vehicle) |- | 3AW || Fruehauf de Mexico (truck trailer) |- | 3AX || Scania Mexico |- | 3BE || Scania Mexico (buses) |- | 3BH || Western Star 3700 (truck) made by DINA S.A. |- | 3BH || Western Star (truck) |- | 3BJ || Western Star 3700 (incomplete vehicle) made by DINA S.A. |- | 3BJ || Western Star (incomplete vehicle) |- | 3BK || Kenworth (incomplete vehicle) |- | 3BM || Motor Coach Industries bus made by DINA S.A. |- | 3BP || Peterbilt (incomplete vehicle) |- | 3B3 || Dodge car 1981–2011 |- | 3B4 || Dodge SUV 1986–1993 |- | 3B6 || Dodge incomplete vehicle 1981–2002 |- | 3B7 || Dodge truck 1981–2002 |- | 3C3 || Chrysler brand car 1981–2011 |- | 3C3 || Chrysler Group (all brands) car (including Fiat) 2012- |- | 3C4 || Chrysler brand MPV 2001–2005 |- | 3C4 || Chrysler Group (all brands) MPV (including Fiat) 2012- |- | 3C6 || Chrysler Group (all brands) truck 2012– |- | 3C7 || Chrysler Group (all brands) incomplete vehicle 2012– |- | 3C8 || Chrysler brand MPV 2001–2005 |- | 3CA || Chrysler brand MPV 2001 (PT Cruiser w/serial# 232057-265662) |- | 3CE || Volvo Buses de Mexico |- | 3CG || KTMMEX S.A. de C.V. |- | 3CZ || Honda SUV made by Honda de Mexico |- | 3D2 || Dodge incomplete vehicle 2007–2009 |- | 3D3 || Dodge truck 2006–2009 |- | 3D4 || Dodge SUV 2009–2011 |- | 3D6 || Dodge incomplete vehicle 2003–2011 |- | 3D7 || Dodge truck 2002–2011 |- | 3EL || ATRO (truck trailer) |- | 3E4 || 2011 Fiat SUV (Freemont) |- | 3FA || [[../Ford/VIN Codes|Ford]] car |- | 3FC || Ford stripped chassis made by Ford & IMMSA |- | 3FE || [[../Ford/VIN Codes|Ford]] Mexico |- | 3FM || [[../Ford/VIN Codes|Ford]] MPV/SUV |- | 3FN || Ford F-650/F-750 made by Blue Diamond Truck Co. (truck) |- | 3FR || Ford F-650/F-750 & Ford LCF made by Blue Diamond Truck Co. (incomplete vehicle) |- | 3FT || [[../Ford/VIN Codes|Ford]] truck |- | 3F6 || Sterling Bullet |- | 3G || [[../GM/VIN Codes|General Motors]] Mexico |- | 3G0 || Saab 9-4X 2011 |- | 3G0 || Holden Equinox 2018–2020 |- | 3G1 || [[../GM/VIN Codes|Chevrolet]] car |- | 3G2 || [[../GM/VIN Codes|Pontiac]] car |- | 3G4 || [[../GM/VIN Codes|Buick]] car |- | 3G5 || [[../GM/VIN Codes|Buick]] SUV |- | 3G7 || [[../GM/VIN Codes|Pontiac]] SUV |- | 3GA || JAC models assembled by Giant Motors in Mexico |- | 3GC || Chevrolet truck |- | 3GK || GMC SUV |- | 3GM || Holden Suburban |- | 3GN || Chevrolet SUV |- | 3GP || Honda Prologue EV made by GM |- | 3GS || Saturn SUV |- | 3GT || GMC truck |- | 3GY || Cadillac SUV |- | 3H1 || Honda motorcycle/UTV |- | 3H3 || Hyundai de Mexico, S.A. de C.V. for Hyundai Translead (truck trailers) |- | 3HA || International Trucks (incomplete vehicle - straight truck) made by Blue Diamond Truck Co. 2011-2015 |- | 3HA || International Trucks (incomplete vehicle - straight truck) made by Navistar Mexico/International Motors Mexico 2016- |- | 3HC || International Trucks (complete vehicle - truck tractor) made by Blue Diamond Truck Co. 2011-2015 |- | 3HC || International Trucks (complete vehicle - truck tractor) made by Navistar Mexico/International Motors Mexico 2016- |- | 3HD || Acura SUV made by Honda de Mexico |- | 3HG || [[../Honda/VIN Codes|Honda]] car made by Honda de Mexico |- | 3HR || International Trucks (complete vehicle - truck) |- | 3HS || International Trucks & Caterpillar Trucks (complete vehicle - truck tractor) |- | 3HT || International Trucks & Caterpillar Trucks (incomplete vehicle - straight truck) |- | 3HV || International (incomplete vehicle - bus) |- | 3JB || BRP Mexico (Can-Am ATV/UTV & Can-Am Ryker 3-wheeler) |- | 3JC || BRP Mexico (Can-Am Origin & Pulse electric 2-wheel motorcycles) |- | 3KM || Kia/Hyundai MPV/SUV made by KMMX |- | 3KP || Kia/Hyundai car made by KMMX |- | 3LN || Lincoln car |- | 3MA || Mercury car (1988-1995) |- | 3MD || Mazda de Mexico car (Mazda 2) |- | 3ME || Mercury car (1996-2011) |- | 3MF || BMW M car |- | 3MG || Isuzu Motors de Mexico |- | 3MJ || Mazda CX-3 (Mazda de Mexico) |- | 3MV || Mazda de Mexico SUV (Mazda CX-30) |- | 3MW || BMW car |- | 3MY || Toyota car made by Mazda de Mexico Vehicle Operation |- | 3MZ || Mazda de Mexico car (Mazda 3) |- | 3N1 || Nissan Mexico car |- | 3N6 || Nissan Mexico truck & Chevrolet City Express |- | 3N8 || Nissan Mexico MPV |- | 3NS || Polaris Industries ATV |- | 3NE || Polaris Industries UTV |- | 3P3 || Plymouth car |- | 3PC || Infiniti SUV made by COMPAS |- | 3TM || Toyota truck made by TMMBC |- | 3TY || Toyota truck made by TMMGT |- | 3VV || Volkswagen Mexico SUV |- | 3VW || Volkswagen Mexico car |- | 3WK || Kenworth truck |- | 3WP || Peterbilt truck |- | 3X1 || Mack Truck Mexico (truck) |- | 3X2 || Mack Truck Mexico (incomplete vehicle) |- | 4A3 || Mitsubishi Motors car |- | 4A4 || Mitsubishi Motors SUV |- | 4B3 || Dodge car made by Diamond-Star Motors factory |- | 4B9/038 || BYD Coach & Bus LLC |- | 4C3 || Chrysler car made by Diamond-Star Motors factory |- | 4C6 || Reinke Manufacturing Company (truck trailer) |- | 4C9/272 || Christini Technologies (motorcycle) |- | 4C9/561 || Czinger |- | 4C9/626 || Canoo Inc. |- | 4CD || Oshkosh Chassis Division incomplete vehicle (RV chassis) |- | 4DR || IC Bus (complete vehicle - bus) |- | 4E3 || Eagle car made by Diamond-Star Motors factory |- | 4EN || E-ONE, Inc. (fire engines - truck) |- | 4EZ || KZ Recreational Vehicles (trailer) |- | 4F2 || Mazda SUV made by Ford |- | 4F4 || Mazda truck made by Ford |- | 4G1 || Chevrolet Cavalier convertible made by Genasys L.C. – a GM/ASC joint venture |- | 4G2 || Pontiac Sunfire convertible made by Genasys L.C. – a GM/ASC joint venture |- | 4G3 || Toyota Cavalier made by GM |- | 4G5 || General Motors EV1 |- | 4GD || WhiteGMC Brigadier 1988–1989 made by GM |- | 4GD || Opel/Vauxhall Sintra |- | 4GL || Buick incomplete vehicle |- | 4GT || Isuzu incomplete vehicle built by GM |- | 4JG || [[../Mercedes-Benz/VIN Codes|Mercedes-Benz]] SUV |- | 4J8 || LBT, Inc. (truck trailer) |- | 4KA || IC Bus (complete vehicle - truck) |- | 4KB || Chevrolet W-Series (gas engine only) made by GM (Incomplete Vehicle - medium duty) |- | 4KD || GMC W-Series (gas engine only) made by GM (Incomplete Vehicle - medium duty) |- | 4KL || Isuzu N-Series (gas engine only) made by GM (Incomplete Vehicle - medium duty) |- | 4LM || Capacity Trucks (truck) [terminal tractors] |- | 4M2 || [[../Ford/VIN Codes|Mercury]] MPV/SUV |- | 4M9/220 || Meyers Manx, LLC (Manx 2.0 EV) [Passenger Car - Replica] |- | 4ML || Oshkosh Trailer Division |- | 4MZ || Buell Motorcycle Company (Mid-1995 – ) |- | 4N2 || Nissan Quest made by Ford |- | 4NU || Isuzu Ascender made by GM |- | 4PR || Hughes Trailers of Jackson (trailer) |- | 4P1 || Pierce Manufacturing Inc. USA |- | 4P3 || Plymouth car made by Diamond-Star Motors factory 1990–1994 |- | 4P3 || Mitsubishi Motors SUV made by Mitsubishi Motor Manufacturing of America 2013–2015 for export only |- | 4RK || Nova Bus & Prevost made by Nova Bus (US) Inc. |- | 4S1 || Isuzu truck made by Subaru Isuzu Automotive |- | 4S2 || Isuzu SUV made by Subaru Isuzu Automotive & 2nd gen. Holden Frontera made by SIA |- | 4S3 || [[../Subaru/VIN Codes|Subaru]] car |- | 4S4 || [[../Subaru/VIN Codes|Subaru]] SUV/MPV |- | 4S6 || Honda SUV made by Subaru Isuzu Automotive |- | 4S7 || Spartan Motors incomplete vehicle |- | 4S9/197 || Smith Electric Vehicles |- | 4S9/345 || Satellite Suites (trailer) |- | 4S9/419 || Spartan Motors truck |- | 4S9/454 || Scuderia Cameron Glickenhaus passenger car |- | 4S9/520 || Signature Autosport, LLC (Osprey Custom Cars) |- | 4S9/542 || Scuderia Cameron Glickenhaus SCG Boot (M.P.V.) |- | 4S9/544 || Scuderia Cameron Glickenhaus passenger car |- | 4S9/559 || Spartan Fire, LLC truck (formerly Spartan ER) |- | 4S9/560 || Spartan Fire, LLC incomplete vehicle (formerly Spartan ER) |- | 4S9/569 || SC Autosports, LLC (Kandi) |- | 4TA || [[../Toyota/VIN Codes|Toyota]] truck made by NUMMI |- | 4T1 || [[../Toyota/VIN Codes|Toyota]] car made by Toyota Motor Manufacturing Kentucky |- | 4T3 || [[../Toyota/VIN Codes|Toyota]] MPV/SUV made by Toyota Motor Manufacturing Kentucky |- | 4T4 || [[../Toyota/VIN Codes|Toyota]] car made by Subaru of Indiana Automotive |- | 4T9/208 || Xos, Inc. |- | 4T9/228 || Lumen Motors |- | 4T9/540 || Telo Trucks, Inc. (Truck) |- | 4UF || Arctic Cat Inc. |- | 4US || BMW car |- | 4UZ || Freightliner Custom Chassis Corporation & <br /> gas-powered Mitsubishi Fuso trucks assembled by Freightliner Custom Chassis & <br /> Thomas Built Buses FS-65 & Saf-T-Liner C2 |- | 4V0 || Crossroads RV (recreational vehicles) |- | 4V1 || WhiteGMC (truck) 1988-1995 |- | 4V2 || WhiteGMC (incomplete vehicle) 1988-1995 |- | 4V3 || WhiteGMC (glider) 1988-1995 |- | 4V1 || Volvo Trucks North America [low cab-over engine] (truck) 2000-2003 |- | 4V2 || Volvo Trucks North America [low cab-over engine] (incomplete vehicle) 2000-2003 |- | 4V4 || Volvo Trucks North America [conventional] (truck) 1996+ |- | 4V5 || Volvo Trucks North America [conventional] (incomplete vehicle) 1996+ |- | 4V6 || Volvo Trucks North America (glider) |- | 4VA || Volvo Trucks North America [conventional- Class 7 w/air brakes] (truck) 1997-1999 |- | 4VB || Volvo Trucks North America [conventional- Class 7 w/air brakes] (incomplete vehicle) 1997-1999 |- | 4VC || Volvo Trucks North America [conventional- Class 7 w/hydraulic brakes] (incomplete vehicle) |- | 4VD || Volvo Trucks North America [low cab-over engine- Class 7 w/air brakes] (truck) |- | 4VE || Volvo Trucks North America [low cab-over engine- Class 7 w/air brakes] (incomplete vehicle) |- | 4VG || Volvo Trucks North America [conventional- Class 8 w/air brakes] (truck) 1997-1999 |- | 4VH || Volvo Trucks North America [conventional- Class 8 w/air brakes] (incomplete vehicle) 1997-1999 |- | 4VJ || Volvo Trucks North America [high cab-over engine- Class 8 w/air brakes] (truck) |- | 4VK || Volvo Trucks North America [high cab-over engine- Class 8 w/air brakes] (incomplete vehicle) |- | 4VL || Volvo Trucks North America [low cab-over engine- Class 8 w/air brakes] (truck) |- | 4VM || Volvo Trucks North America [low cab-over engine- Class 8 w/air brakes] (incomplete vehicle) |- | 4VZ || Spartan Motors/The Shyft Group (incomplete vehicle – bare chassis only) |- | 4WW || Wilson Trailer Sales |- | 4W1 || '24+ Chevrolet Suburban HD made by GM Defense for US govt. in Concord, NC |- | 4W5 || Acura ZDX EV made by GM |- | 4XA || Polaris Inc. |- | 4X4 || Forest River |- | 4YD || KeyStone RV Company (recreational vehicle) |- | 4YM || Carry-On Trailer, Inc. |- | 4YM || Anderson Manufacturing (trailer) |- | 4Z3 || American LaFrance truck |- | 43C || Consulier |- | 44K || HME Inc. (fire engines - incomplete vehicle) (HME=Hendrickson Mobile Equipment) |- | 46G || Gillig incomplete vehicle |- | 46J || Federal Motors Inc |- | 478 || Honda ATV |- | 480 || Sterling Trucks (truck) |- | 49H || Sterling Trucks (incomplete vehicle) |- | 5AS || Global Electric Motorcars (GEM) 1999-2011 |- | 5AX || Armor Chassis (truck trailer) |- | 5A4 || Load Rite Trailers Inc. |- | 5BP || Solectria |- | 5BZ || Nissan "bus" (van with more than 3 rows of seats) |- | 5B4 || Workhorse Custom Chassis, LLC incomplete vehicle (RV chassis) |- | 5CD || Indian Motorcycle Company of America (Gilroy, CA) |- | 5CJ || Western Star Trucks (incomplete vehicle) |- | 5CK || Western Star Trucks (truck) |- | 5CX || Shelby Series 1 |- | 5DF || Thomas Dennis Company LLC |- | 5DG || Terex Advance Mixer, Inc. (Formerly Advance Mixer, Inc.) (truck) |- | 5EH || Excelsior-Henderson Motorcycle |- | 5EO || Cottrell (truck trailer) |- | 5FC || Columbia Vehicle Group (Columbia, Tomberlin) (low-speed vehicles) |- | 5FN || Honda MPV/SUV made by Honda Manufacturing of Alabama |- | 5FP || Honda truck made by Honda Manufacturing of Alabama |- | 5FR || Acura SUV made by Honda Manufacturing of Alabama |- | 5FT || Feeling Trailers |- | 5FY || New Flyer |- | 5GA || Buick MPV/SUV |- | 5GD || Daewoo G2X |- | 5GN || Hummer H3T |- | 5GR || Hummer H2 |- | 5GT || Hummer H3 |- | 5GZ || Saturn MPV/SUV |- | 5G8 || Holden Volt |- | 5HD || Harley-Davidson for export markets |- | 5HT || Heil Trailer (truck trailer) |- | 5J1 || Big Dog Motorcycles (Mid-2002 – ) |- | 5J5 || Club Car (low-speed vehicle) |- | 5J6 || Honda SUV made by Honda of America Mfg. in Ohio |- | 5J8 || Acura SUV made by Honda of America Mfg. in Ohio |- | 5KB || Honda car made by Honda Manufacturing of Alabama |- | 5KJ || Western Star Trucks (truck) |- | 5KK || Western Star Trucks (incomplete vehicle) |- | 5KM || Vento Motorcycles |- | 5KT || Karavan Trailers |- | 5L1 || [[../Ford/VIN Codes|Lincoln]] SUV - Limousine (2004–2009) |- | 5L5 || American IronHorse Motorcycle |- | 5LD || Ford & Lincoln incomplete vehicle – limousine (2010–2014) |- | 5LM || [[../Ford/VIN Codes|Lincoln]] SUV |- | 5LT || [[../Ford/VIN Codes|Lincoln]] truck |- | 5MZ || Buell Motorcycle Company for export markets |- | 5N1 || Nissan & Infiniti SUV |- | 5N3 || Infiniti SUV |- | 5NH || Forest River |- | 5NM || Hyundai SUV made by HMMA |- | 5NP || Hyundai car made by HMMA |- | 5NT || Hyundai truck made by HMMA |- | 5PV || Hino incomplete vehicle made by Hino Motors Manufacturing USA |- | 5RJ || International MXT made by Android Industries - Springfield LLC |- | 5RX || Heartland Recreational Vehicles |- | 5S3 || Saab 9-7X |- | 5SA || Suzuki Manufacturing of America Corp. (ATV) |- | 5SX || American LaFrance incomplete vehicle (Condor) |- | 5TB || [[../Toyota/VIN Codes|Toyota]] truck made by TMMI |- | 5TD || Toyota MPV/SUV & Lexus TX made by TMMI |- | 5TE || Toyota truck made by NUMMI |- | 5TF || Toyota truck made by TMMTX |- | 5TU || Construction Trailer Specialist (truck trailer) |- | 5UM || BMW M car |- | 5UX || BMW SUV |- | 5VC || Autocar incomplete vehicle |- | 5VF || American Electric Vehicle Company (low-speed vehicle) |- | 5VK || Great Northern Trailer Works (truck trailer) |- | 5VP || Victory Motorcycles |- | 5V4 || Autocar truck |- | 5V8 || Vanguard National (truck trailer) |- | 5WE || IC Bus (incomplete vehicle - bus or truck) |- | 5XX || Kia car made by KMMG |- | 5XY || Kia/Hyundai SUV made by KMMG |- | 5YA || Indian Motorcycle Company (Kings Mountain, NC) |- | 5YF || Toyota car made by TMMMS |- | 5YJ || Tesla, Inc. passenger car (only used for US-built Model S and Model 3 starting from Nov, 1st 2021) |- | 5YM || BMW M SUV |- | 5YN || Cruise Car, Inc. |- | 5Y2 || Pontiac Vibe made by NUMMI |- | 5Y4 || Yamaha Motor Motor Mfg. Corp. of America (ATV, UTV) |- | 5ZT || Forest River (recreational vehicles) |- | 5ZU || Greenkraft (truck) |- | 5Z6 || Suzuki Equator (truck) made by Nissan |- | 50E || Lucid Motors passenger car |- | 50G || Karma Automotive |- | 50H || Norstar Company (truck trailers, truck beds) |- | 516 || Autocar truck |- | 51R || Brammo Motorcycles |- | 51T || Monaco RV LLC/Navistar RV LLC: Monaco (trailer) |- | 51U || Monaco RV LLC/Navistar RV LLC: Holiday Rambler 2010- (trailer) |- | 51V || Monaco RV LLC/Navistar RV LLC: R-Vision (trailer) |- | 51X || Monaco RV LLC/Navistar RV LLC: McKenzie (trailer) |- | 51Z || Monaco RV LLC/Navistar RV LLC: Monaco RV [Roadmaster Chassis] (incomplete vehicle) |- | 522 || GreenGo Tek (low-speed vehicle) |- | 523 || VPG (The Vehicle Production Group) |- | 52C || GEM subsidiary of Polaris Inc. |- | 537 || Azure Dynamics Transit Connect Electric |- | 538 || Zero Motorcycles |- | 53G || Coda Automotive |- | 53T || Think North America in Elkhart, IN |- | 546 || EBR Motorcycles |- | 54C || Winnebago Industries travel trailer |- | 54D || Isuzu & Chevrolet commercial trucks built by Spartan Motors/The Shyft Group |- | 54F || Rosenbauer Motors (incomplete vehicle) |- | 55S || Mercedes-Benz car |- | 56E || Armor Lite Trailer Mfg. (truck trailers) |- | 56K || Indian Motorcycle International, LLC (Polaris subsidiary) |- | 573 || Grand Design RV (truck trailer) |- | 57C || Maurer Manufacturing (truck trailer) |- | 57R || Oreion Motors |- | 57S || Lightning Motors Corp. (electric motorcycles) |- | 57W || Mobility Ventures |- | 57X || Polaris Slingshot |- | 58A || Lexus car made by TMMK (Lexus ES) |- | 6AB || MAN Australia |- | 6AM || Jayco Corp. (RVs) |- | 6F1 || Ford |- | 6F2 || Iveco Trucks Australia Ltd. |- | 6F4 || Nissan Motor Company Australia |- | 6F5 || Kenworth Australia |- | 6FM || Mack Trucks Australia |- | 6FP || [[../Ford/VIN Codes|Ford]] Australia |- | 6G1 || [[../GM/VIN Codes|General Motors]]-Holden (post Nov 2002), Chevrolet 2000-2013, Vauxhall Monaro & VXR8 ('08-'17), Daewoo Statesman & Veritas |- | 6G2 || [[../GM/VIN Codes|Pontiac]] made in Australia ('04-'06 GTO & '08-'09 G8) |- | 6G3 || [[../GM/VIN Codes|General Motors]] Chevrolet Caprice PPV & SS performance sedan 2014-2017, Middle East mkt. Chevrolet Caprice '14-'17 |- | 6H8 || [[../GM/VIN Codes|General Motors]]-Holden (pre Nov 2002) |- | 6KT || BCI Bus |- | 6MM || Mitsubishi Motors Australia |- | 6MP || Mercury Capri 1991-1994 |- | 6T1 || [[../Toyota/VIN Codes|Toyota]] Motor Corporation Australia |- | 6T9 || Privately Imported car (VIN issued by Victoria) or Trailer in Australia |- | 6U9 || Privately Imported car in Australia |- | 6Y9/043 || Intertruck Distributors (NZ) Ltd. - International Trucks New Zealand |- | 6ZZ || Privately Imported car in Australia |- | 7AB || MAN New Zealand |- | 7AT || VIN assigned by the New Zealand Transport Authority Waka Kotahi from 29 November 2009 |- | 7A1 || Mitsubishi New Zealand |- | 7A3 || Honda New Zealand |- | 7A4 || Toyota New Zealand |- | 7A5 || Ford New Zealand |- | 7A7 || Nissan New Zealand |- | 7A8 || VIN assigned by the New Zealand Transport Authority Waka Kotahi before 29 November 2009 |- | 7B2 || Nissan Diesel bus New Zealand |- | 7FA || Honda SUV made by Honda Manufacturing of Indiana |- | 7FC || Rivian truck |- | 7F7 || Arcimoto, Inc. |- | 7GZ || GMC incomplete vehicles (Savana cutaway) made by Navistar International/International Motors |- | 7G0 || Faraday Future |- | 7G2 || Tesla, Inc. truck (used for Nevada-built Semi Trucks & Texas-built Cybertruck) |- | 7H4 || Hino truck |- | 7H8 || Cenntro Electric Group Limited low-speed vehicle |- | 7JD || Volvo Cars SUV |- | 7JR || Volvo Cars passenger car |- | 7JS || White River Marine Group (trailer) |- | 7JZ || Proterra From mid-2019 on |- | 7KG || Vanderhall Motor Works |- | 7KY || Dorsey (truck trailer) |- | 7MM || Mazda SUV made by MTMUS (Mazda-Toyota Joint Venture) |- | 7MU || Toyota SUV made by MTMUS (Mazda-Toyota Joint Venture) |- | 7MW || Cenntro Electric Group Limited truck |- | 7MZ || HDK electric vehicles |- | 7NA || Navistar Defense/ND Defense |- | 7NY || Lordstown Motors |- | 7PD || Rivian SUV |- | 7RZ || Electric Last Mile Solutions |- | 7SA || Tesla, Inc. (US-built MPVs (e.g. Model X, Model Y)) |- | 7SU || Blue Arc electric trucks made by The Shyft Group |- | 7SV || [[../Toyota/VIN Codes|Toyota]] SUV made by TMMTX |- | 7SX || Global Electric Motorcars (WAEV) 2022- |- | 7SY || Polestar SUV |- | 7TN || Canoo |- | 7UU || Lucid Motors MPV/SUV |- | 7UZ || Kaufman Trailers (trailer) |- | 7VV || Ree Automotive |- | 7WA || Scout Motors (MPV) |- | 7WE || Bollinger Motors incomplete vehicle |- | 7XB || Denago EV Corporation (Low-Speed Vehicle) |- | 7YA || Hyundai & Kia MPV/SUV made by HMGMA |- | 7ZJ || Meyers Manx, LLC (Manx EV Resorter) [Low Speed Vehicle] |- | 7ZN || Harbinger Motors, Inc. (incomplete vehicle) |- | 7Z0 || Zoox |- | 71T || Slate Auto (truck) |- | 71V || Slate Auto (MPV) |- | 722 || Isuzu North America Corp. (incomplete vehicle - medium duty) |- | 8AB || Mercedes Benz truck & bus (Argentina) |- | 8AC || Mercedes Benz vans (for South America) |- | 8AD || Peugeot Argentina |- | 8AE || Peugeot van |- | 8AF || [[../Ford/VIN Codes|Ford]] Argentina |- | 8AG || [[../GM/VIN Codes|Chevrolet]] Argentina |- | 8AJ || [[../Toyota/VIN Codes|Toyota]] Argentina |- | 8AK || Suzuki Argentina |- | 8AN || Nissan Argentina |- | 8AP || Fiat Argentina |- | 8AT || Iveco Argentina |- | 8AW || Volkswagen Argentina |- | 8A1 || Renault Argentina |- | 8A3 || Scania Argentina |- | 8A7 || Minarelli S.A. |- | 8BB || Agrale Argentina S.A. |- | 8BC || Citroën Argentina |- | 8BN || Mercedes-Benz incomplete vehicle (North America) |- | 8BR || Mercedes-Benz "bus" (van with more than 3 rows of seats) (North America) |- | 8BT || Mercedes-Benz MPV (van with 2 or 3 rows of seats) (North America) |- | 8BU || Mercedes-Benz truck (cargo van with 1 row of seats) (North America) |- | 8CH || Honda motorcycle |- | 8C3 || Honda car/SUV |- | 8G1 || Automotores Franco Chilena S.A. Renault |- | 8GD || Automotores Franco Chilena S.A. Peugeot |- | 8GG || [[../GM/VIN Codes|Chevrolet]] Chile |- | 8LD || General Motors OBB - Chevrolet Ecuador |- | 8LF || Maresa (Mazda) |- | 8LG || Aymesa (Hyundai Motor & Kia) |- | 8L4 || Great Wall Motors made by Ciudad del Auto (Ciauto) |- | 8XD || Ford Motor Venezuela |- | 8XJ || Mack de Venezuela C.A. |- | 8XV || Iveco Venezuela C.A. |- | 8Z1 || General Motors Venezolana C.A. |- | 829 || Industrias Quantum Motors S.A. (Bolivia) |- | 9BD || Fiat Brazil & Dodge, Ram made by Fiat Brasil |- | 9BF || [[../Ford/VIN Codes|Ford]] Brazil |- | 9BG || [[../GM/VIN Codes|Chevrolet]] Brazil |- | 9BH || Hyundai Motor Brasil |- | 9BM || Mercedes-Benz Brazil car, SUV, commercial truck & bus |- | 9BN || Mafersa |- | 9BR || [[../Toyota/VIN Codes|Toyota]] Brazil |- | 9BS || Scania Brazil |- | 9BU ||Gurgel Motores S.A. (defunct Brazilian automaker) |- | 9BV || Volvo Trucks Brazil |- | 9BW || Volkswagen Brazil |- | 9BY || Agrale S.A. |- | 9C2 || Moto Honda Da Amazonia Ltda. |- | 9C6 || Yamaha Motor Da Amazonia Ltda. |- | 9CD || Suzuki (motorcycles) assembled by J. Toledo Motos do Brasil |- | 9DF || Puma |- | 9DW || Kenworth & Peterbilt trucks [incomplete vehicle] made by Volkswagen do Brasil |- | 9EZ || homemade or handbuilt vehicles |- | 92H || Origem Brazil |- | 932 || Harley-Davidson Brazil |- | 935 || Citroën Brazil |- | 936 || Peugeot Brazil |- | 937 || Dodge Dakota |- | 93C || Chevrolet SUV [Tracker] or pickup [Tornado, Montana, S10] (sold in Mexico, made in Brazil) |- | 93H || [[../Honda/VIN Codes|Honda]] Brazil car/SUV |- | 93K || Volvo Trucks Brazil |- | 93P || Volare |- | 93S || Navistar International |- | 93R || [[../Toyota/VIN Codes|Toyota]] Brazil |- | 93U || Audi Brazil 1999–2006 |- | 93W || Fiat Ducato made by Iveco 2000–2016 |- | 93V || Navistar International |- | 93X || Souza Ramos – Mitsubishi Motors / Suzuki Jimny |- | 93Y || Renault Brazil |- | 93Z || Iveco |- | 94D || Nissan Brazil |- | 94N || RWM Brazil |- | 94T || Troller Veículos Especiais |- | 95P || CAOA Hyundai & CAOA Chery |- | 95V || Dafra Motos (motorscooters from SYM) & Ducati, KTM, & MV Agusta assembled by Dafra |- | 95V || BMW motorcycles assembled by Dafra Motos 2009–2016 |- | 95Z || Buell Motorcycle Company assembled by Harley-Davidson Brazil |- | 953 || VW Truck & Bus / MAN Truck & Bus |- | 96P || Kawasaki |- | 97N || Triumph Motorcycles Ltd. |- | 988 || Jeep, Ram [Rampage], and Fiat [Toro] (made at the Goiana plant) |- | 98M || BMW car/SUV |- | 98P || DAF Trucks |- | 98R || Chery |- | 99A || Audi 2016- |- | 99H || Shineray |- | 99J || Jaguar Land Rover |- | 99K || Haojue & Kymco assembled by JTZ Indústria e Comércio de Motos |- | 99L || BYD |- | 99Z || BMW Motorrad (Motorcycle assembled by BMW 2017-) |- | 9FB || Renault Colombia (Sofasa) |- | 9FC || Compañía Colombiana Automotriz S.A. (Mazda) |- | 9GA || [[../GM/VIN Codes|Chevrolet]] Colombia (GM Colmotores S.A.) |- | 9UJ || Chery assembled by Chery Socma S.A. (Uruguay) |- | 9UK || Lifan (Uruguay) |- | 9UT || Dongfeng trucks made by Nordex S.A. |- | 9UW || Kia made by Nordex S.A. |- | 9VC || Fiat made by Nordex S.A. (Scudo, 2025 Titano) |- | 9V7 || Citroen made by Nordex S.A. (Jumpy) |- | 9V8 || Peugeot made by Nordex S.A. (Expert) |} ==References== {{reflist}} {{BookCat}} 5zbik7zk3lhg4o8zcs8s9ykyit8yccu Vehicle Identification Numbers (VIN codes)/Land Rover/VIN Codes 0 142029 4679846 4679693 2026-11-03T20:40:08Z JustTheFacts33 3434282 /* Trim Level/Drive Wheels/GVWR/Restraint System (Position 5) */ 4679846 wikitext text/x-wiki {{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}} From 1948 to the early eighties, Land Rover used for their cars chassis numbers of their own format. These formats are described in the table below. Since 1980 Land Rover deploys the standard 17-character Vehicle Identification Number ('''VIN'''), complying with international standards. Car details can be derived (decoded, calculated) from the chassis numbers and the VIN. Typically, the model (Defender, Discovery, Range Rover, Freelander), model type (station wagon, three/four door, etc), wheelbase (90 inch, 100 inch, 110 inch, etc.), engine, LHD/RHD, gearbox, and model year is included in the VIN. ===Chassis number formats over the years=== <table> <tr><th>Description</th><th>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</th><th>Format</th></tr> <tr><td>17-characters, International VIN, 1980-later</td><td></td><td>SAL..............</td></tr> <tr><td>17-characters, Int. VIN for LR do Brazil </td><td></td><td>93R..............</td></tr> <tr><td>17-characters, Int. VIN for AAD, 1985-1995 </td><td></td><td>AAD..............</td></tr> <tr><td>17-characters, US/Canada VIN, 1987-later </td><td></td><td>SAL.................</td></tr> <tr><td>17-characters, Brazil VIN for JLR Brazil, 2016-later </td><td></td><td>99J.................</td></tr> <tr></tr> <tr><td>14-characters: is actually the 17-char</td></tr> <tr><td>VIN missing the SAL bit</td></tr> <tr><td> <tr><td>9-character numbers, 1955 </td><td></td><td>17.6.....</td></tr> <tr><td>9-character numbers, 1956 to 1961 </td><td></td><td>1........</td></tr> <tr><td>9-character numbers, 1950 </td><td></td><td>L........ or R........</td></tr> <tr><td>9-character numbers, 1962 to 1979 </td><td></td><td>.........</td></tr> <tr></tr> <tr><td>8-character numbers, 1948 to 1949 </td><td></td><td>.8......</td></tr> <tr><td>8-character numbers, 1950 to 1953 </td><td></td><td>.6......</td></tr> <tr><td>8-character numbers, 1954 to 1955 </td><td></td><td>.7......</td></tr> <tr></tr> <tr><td>7-character numbers, 1948 to 1949 </td><td></td><td>.......</td></tr> <tr><td>6-character numbers, ???? prototypes </td><td></td><td>110F..</td></tr> <tr><td>3-character numbers, 1948 prototypes </td><td></td><td>R.. or L..</td></tr> </table> ===Land Rover WMIs (1981-) (Position 1-3)=== * SAL - Land Rover (UK & Europe) * 99J - JLR Brazil * L2C - Chery Jaguar Land Rover (China) ===Model Line=== {| class="wikitable" |+Position 4 !VIN code !Description |- |A |[[w:Land Rover Discovery#Discovery 3 / LR3 (2004–2009)|Land Rover LR3]] ('05-'09) |- |A |[[w:Land Rover Discovery#Discovery 4 / LR4 (2009–2016)|Land Rover LR4]] ('10-'16) |- |C |[[w:Land Rover Discovery Sport|Land Rover Discovery Sport]] ('15-'26) |- |D |[[w:Land Rover Defender#North American Specification (NAS) Defenders|Land Rover Defender]] ('93-'95, '97) |- |E |[[w:Land Rover Defender (L663)|Land Rover Defender (L663)]] ('20-) |- |F |[[w:Land Rover Freelander#Freelander 2 (L359; 2006–2015)|Land Rover LR2]] ('08-'15) |- |G |[[w:Range Rover (L405)|Land Rover Range Rover (L405)]] (4th gen.) ('13-'22) |- |H |[[w:Range Rover Classic|Land Rover Range Rover/Range Rover Classic]] (1st gen.) ('87-'95) |- |J |[[w:Land Rover Discovery#First & Second generation Discovery|Land Rover Discovery]] ('94-'98 & '99 Discovery SD) |- |K |[[w:Range Rover (L460)|Land Rover Range Rover (L460)]] (5th gen.) (Mid '22-) |- |M |[[w:Range Rover (L322)|Land Rover Range Rover (L322)]] (3rd gen.) ('03-'12) |- |N |[[w:Land Rover Freelander#Freelander in North America|Land Rover Freelander]] ('02-'05) |- |P |[[w:Range Rover (P38A)|Land Rover Range Rover (P38A)]] (2nd gen.) ('95-'02) |- |R |[[w:Land Rover Discovery#Fifth generation Discovery (L462; 2017–present)|Land Rover Discovery]] ('17-) |- |S |[[w:Range Rover Sport#First generation (L320; 2005)|Land Rover Range Rover Sport]] (1st gen.) ('06-'13) |- |T |[[w:Land Rover Discovery#Discovery Series II (L318; 1998–2004)|Land Rover Discovery Series II]] ('99-'04) |- |V |[[w:Range Rover Evoque#First generation (L538; 2011)|Land Rover Range Rover Evoque]] (1st gen.) ('12-'19) |- |W |[[w:Range Rover Sport#Second generation (L494; 2013)|Land Rover Range Rover Sport]] (2nd gen.) ('14-'22) |- |Y |[[w:Range Rover Velar|Land Rover Range Rover Velar]] (1st gen.) ('18-) |- |Z |[[w:Range Rover Evoque#Second generation (L551; 2018)|Land Rover Range Rover Evoque]] (2nd gen.) ('20-) |- |1 |[[w:Range Rover Sport#Third generation (L461; 2022)|Land Rover Range Rover Sport]] (3rd gen.) ('23-) |- |} ===Model Series/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |V (following H) |Range Rover 100" wheelbase (1st gen.) |Class E |- |E (following H) |Range Rover 100" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |C (following H) |Range Rover LWB 108" wheelbase (1st gen.) |Class E |- |F (following H) |Range Rover LWB 108" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |H (following D) |Defender 110 ('93) |Class E |- |V (following D) |Defender 90 ('94-'95, '97) |Class E |- |X (following D) |Defender 90 (CA emissions) ('95) |Class E |- |Y (following J) |Discovery ('94-'98 & '99 Discovery SD) |Class E |- |N (following J) |Discovery (CA emissions) ('95-'96) |Class E |- |Y (following T) |Discovery Series II ('99-'00) |Class E |- |V (following P) |Range Rover (2nd gen.) ('95-'98) |Class E |- |E (following P) |Range Rover (2nd gen.) (CA emissions) ('95-'96) |Class E |- |A (following P) |Range Rover (2nd gen.) (GEMS engine management) (Early '99) |Class E |- |V (following P) |Range Rover (2nd gen.) (Bosch engine management) ('99-'00) |Class E |- |C (following P) |Range Rover 4.6 HSE Callaway Edition (2nd gen.) (Callaway-modified engine) ('99) |Class E |- |} ===Model Series/Trim Level/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |M (following N) |Freelander S ('02-'03) |Class C |- |Y (following N) |Freelander SE ('02-'05), SE3 ('03-'05) |Class C |- |E (following N) |Freelander HSE ('02-'04) |Class C |- |L (following T) |Discovery Series II SD ('01-'02), S ('03-'04) |Class E |- |K (following T) |Discovery Series II SD7 ('01-'02), S7 ('03-'04) |Class E |- |Y (following T) |Discovery Series II SE ('01-'04) |Class E |- |W (following T) |Discovery Series II SE7 ('01-'04) |Class E |- |H (following T) |Discovery Series II LE ('01) |Class E |- |J (following T) |Discovery Series II LE7 ('01) |Class E |- |P (following T) |Discovery Series II HSE ('03-'04) |Class E |- |R (following T) |Discovery Series II HSE7 ('03-'04) |Class E |- |L (following P) |Range Rover (2nd gen.) 4.6 SE ('01) |Class E |- |M (following P) |Range Rover (2nd gen.) 4.6 HSE ('01-'02), Westminster Edition ('02) |Class E |- |H (following M) |Range Rover (3rd gen.) Westminster Edition ('04-'05) |Class E |- |} ===Trim Level/Drive Wheels/GVWR/Restraint System (Position 5)=== {| class="wikitable" |+Position 5 !VIN code !Trim Level !Drive Wheels !GVWR !Restraint System |- |J |LR2 base model - Canada only: '14 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |N |Range Rover Evoque Pure '12 (Canada only), '13-'15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |LR2 base model - Canada only: '13,<br> LR2 SE - Canada only: '14,<br> LR2 base model '15, Discovery Sport SE '15-'19,<br> Range Rover Evoque Pure Plus '12-'15,<br> Range Rover Evoque SE, SE Premium '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque Landmark Edition 4-d '18-'19 <br> [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |LR2 base model (US only) '11-'14,<br> LR2 HSE (US & Canada) '11-'15,<br> Discovery Sport HSE '15-'18,<br> Range Rover Evoque Pure Premium '12-'15,<br> Range Rover Evoque HSE '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE '19, Landmark Edition '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque Prestige Premium '12-'14, Prestige '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |LR2 HSE Lux '11-'15, Discovery Sport HSE Lux '15-'18,<br> Range Rover Evoque Dynamic Premium '12-'14,<br> Dynamic '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic '16-'19 [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d '16 [Pos. 6 is 1] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |E |Range Rover Evoque Autobiography '15-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque SE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |K |Discovery Sport base model '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |J |Discovery Sport S '20-25, Range Rover Evoque S '20-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |Discovery Sport SE '20-'23, Range Rover Evoque SE '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |9 |Discovery Sport HSE '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque First Edition '20 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport R-Dynamic S '20-'23,<br> Range Rover Evoque R-Dynamic S '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport R-Dynamic SE '20-'23,<br> Discovery Sport Dynamic SE '24-'25,<br> Range Rover Evoque R-Dynamic SE '21-'23,<br> Range Rover Evoque Dynamic SE '24-'26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport Landmark Edition '26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque R-Dynamic SE '20 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |M |Discovery Sport R-Dynamic HSE '20, Canada only: '21-'23,<br> Discovery Sport Dynamic HSE - Canada only: '24-'25,<br> Range Rover Evoque R-Dynamic HSE '20-'21,<br> Range Rover Evoque Dynamic HSE - Canada only: '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P250 Bronze Collection - <br> Canada only: '22-'23 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P300 HST '22-'23 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque P250 Hoxton Edition '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |1 |Range Rover Evoque P250 Autobiography - Canada only: '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |A |Range Rover Velar base model '18-'19 [Pos. 8 is X] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Range Rover Velar S '18-'20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Velar S '21-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |Range Rover Velar SE - Canada only: '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar R-Dynamic SE '18-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |A |Range Rover Velar R-Dynamic SE '19 (some early prod. w/340-hp engine) [Pos. 7 is F & Pos. 8 is V] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Velar R-Dynamic S '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Velar R-Dynamic S '21-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar Dynamic SE '24-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar R-Dynamic HSE '18-'22, First Edition '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar HST '23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar Dynamic HSE '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar Belgravia Edition '26,<br> Belgravia Edition Satin '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Velar Autobiography '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Velar SVAutobiography Dynamic '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |LR4 base model w/2 rows of seats '11-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |LR4 base model w/3 rows of seats '11-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |LR4 HSE w/2 rows of seats - Canada only: '13-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |LR4 HSE w/3 rows of seats '11-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |LR4 HSE Lux w/3 rows of seats '11-'16,<br> HSE Lux XXV Ltd. Ed. w/3 rows of seats '14 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Sport HSE '11-'13, HSE GT Limited Edition '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Sport HSE Luxury '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Range Rover Sport Supercharged '11-'13,<br> Supercharged Limited Edition '13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport Autobiography '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |Discovery SE '17-'20, Range Rover Sport SE '14-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Discovery Landmark Edition '20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P300 S '21-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P360 S - Canada only: '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P300 R-Dynamic S '21-'23 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P360 R-Dynamic S '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P300 Dynamic SE '24-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P360 Dynamic SE '24-'25, Canada only: '26 <br> [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Discovery P360 R-Dynamic HSE '21-'23,<br> P360 Dynamic HSE - Canada only: '24-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Metropolitan Edition '23-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Gemini Edition '26,<br> Discovery P360 Tempest Edition '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '14 <br> [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '15, HSE Limited Edition '15 <br> [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Discovery HSE '17-'20,<br> Range Rover Sport HSE '17-'18 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '19 [Pos. 8 is V or K or U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '20, HSE Silver Edition '21 <br> [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE Silver Edition '22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Discovery HSE Luxury '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery HSE Luxury '18-'20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery First Edition '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST '16 [Pos. 7 is P or V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport HSE Dynamic '17-'19 [Pos. 8 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST Mid '19-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport P400e HSE '20,<br> P400e HSE Silver Edition '21-'22 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P400e Autobiography '20-'21 <br> [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '15,<br> Supercharged Limited Edition '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '16,<br> Supercharged Dynamic '16,<br> Supercharged Dynamic Limited Edition '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '17-'18,<br> Supercharged Dynamic '17-'19,<br> HSE Dynamic '20-'22 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '17, '19-'22,<br> Autobiography Dynamic '18 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport SVR '15-'22, SVR Carbon Edition '21-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Sport P360 S '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport P360 SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Sport P400 Dynamic S - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Sport Dynamic SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P400 Dynamic HSE - <br> Canada only: '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P440e Autobiography '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P440e HSE Dynamic - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P550e Autobiography '24-'26,<br> P530 Autobiography '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P530 First Edition '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition One w/Obsidian Black or Flux Silver paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Edition One w/Carbon Bronze paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition Two '25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Range Rover Sport P635 SV '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Range Rover Sport P635 SV Carbon '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |E |Range Rover HSE '11-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover HSE Luxury '11-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Supercharged '11-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Autobiography '11-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover (L405) base model '13-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '13 [Pos. 7 is D] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '14 [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '15, HSE Limited Edition '15 [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '17-'19 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '20 [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '21 [Pos. 8 is K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE Westminster Edition '21-'22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover P400e HSE '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover P400e Autobiography '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '13 <br> [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '14,<br> Supercharged SWB Ebony Edition '14 <br> [Pos. 6 is 2 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '15,<br> Supercharged SWB Limited Edition '15 <br> [Pos. 6 is 2 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '16 <br> [Pos. 6 is 2 & Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '17-'19,<br> P525 HSE SWB '20,<br> P525 HSE Westminster Edition SWB '21-'22 <br> [Pos. 6 is 2 & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography SWB '13-'22 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition SWB '21 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography Dynamic '17-'22,<br> SVAutobiography Dynamic Black '21-'22 [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE LWB '15 <br> [Pos. 6 is 3 & Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '14 <br> [Pos. 6 is 3 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '15,<br> Supercharged LWB Limited Edition '15 <br> [Pos. 6 is 3 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '16 <br> [Pos. 6 is 3 & Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '17-'19,<br> P525 HSE LWB '20,<br> P525 HSE Westminster Edition LWB '21-'22 <br> [Pos. 6 is 5 & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '14-'15 [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '16 [Pos. 6 is 3] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '17-'22 [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) Autobiography Black LWB '14-'15 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition LWB '21 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '16-'17 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '18-'22 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover (L460) SE '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover (L460) Autobiography '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L460) P530 First Edition '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover (L460) P530 SV '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover (L460) P615 SV '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover (L460) P615 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 90 base model '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/2 rows of seats '20-'23 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/3 rows of seats '20-'23 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 90 S '21-'25, Canada only: '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 130 S w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Defender 90 X-Dynamic S '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 90 P400 SE '23 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/2 rows of seats '20-'23 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P500 SE w/2 rows of seats '24 [Pos. 6 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/3 rows of seats '20-'23 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 130 P400 SE w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 90 P400 X-Dynamic SE '22-'26,<br> Defender 90 X-Dynamic SE Sedona Red '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/2 rows of seats '21-'26 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P500 X-Dynamic SE w/2 rows of seats '25-'26 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/3 rows of seats '21-'26 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 130 P400 X-Dynamic SE w/3 rows of seats '23-'26 <br> [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 90 X-Dynamic HSE '22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/2 rows of seats '21-'22 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/3 rows of seats '21-'22 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/2 rows of seats '22 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/3 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 75th Limited Edition '23 <br> [Pos. 6 is 6 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 75th Limited Edition w/2 rows of seats '23 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Sedona Red Edition w/2 rows of seats '25 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Trophy Edition w/2 rows of seats '26 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P400 Outbound w/2 rows of seats '24-'26 <br> [Pos. 6 is F & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 90 First Edition '21 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 130 First Edition w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 90 X '21-'23, Canada only: '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 130 X w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 90 P525 V8 '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 P525 V8 '22-'23, '25-'26,<br> P525 V8 Carpathian Edition '22-'24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 110 P525 V8 w/2 rows of seats '24 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 P525 V8 w/2 rows of seats '22-'23, '25-'26,<br> P525 V8 Carpathian Edition w/2 rows of seats '22-'24,<br> P525 V8 Bond Edition w/2 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 130 P500 V8 w/3 rows of seats '24 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P500 V8 w/3 rows of seats '25-'26 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Defender 110 P635 OCTA w/2 rows of seats '25-'26,<br> P635 OCTA Edition One w/2 rows of seats '25,<br> P635 OCTA Black w/2 rows of seats '26 <br> [Pos. 6 is E & Pos. 8 is 9] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |} ===Body Type=== {| class="wikitable" |+Position 6 !VIN code !Description |- |1 |4-door wagon (Range Rover '87-'12, Defender 110 '93, Discovery '94-'04) |- |1 |2-door soft top (Freelander SE3) ('03-'05) |- |1 |2-door wagon (Range Rover Evoque 2-d '12-'17) |- |2 |2-door soft top (Defender 90) ('94-'95, '97) |- |2 |4-door wagon (Freelander) ('02-'05) |- |2 |4-door wagon (LR2 '08-'15, Discovery Sport '15-'26, Range Rover Evoque 4-d '12-, LR3 '05-'09, LR4 '10-'16, Discovery '18-, Range Rover Sport '06-'22, Range Rover Sport P400e '20, Range Rover SWB (L405) '13-'22, Range Rover Velar '18-) |- |3 |2-door wagon (Defender 90) ('95, '97) |- |3 |4-door wagon LWB (Range Rover LWB '14-'16) |- |3 |4-door wagon LWB w/Class E GVWR (Range Rover SVAutobiography LWB '17) |- |4 |4-door wagon [[w:Plug-in hybrid|PHEV]] (Range Rover P400e '20-'21, Range Rover Sport P400e '21-Early '22) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover Supercharged LWB & Autobiography LWB '17) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover LWB (L405) '18-'22) |- |5 |2-door convertible (Range Rover Evoque convertible '17-'19) |- |6 |2-door wagon (Defender 90 '21-) |- |7 |4-door wagon w/2 rows of seating (Defender 110 P300/P400 '20-) |- |9 |4-door wagon (Range Rover SWB (L460) '22-, Range Rover Sport '23-) |- |B |4-door wagon (Discovery '17) |- |B |4-door wagon LWB (Range Rover LWB (L460) '22-) |- |E |4-door wagon w/3 rows of seating (Defender 110 P300/P400 w/opt. 3rd row '20-) |- |E |4-door wagon w/2 rows of seating (Defender 110 V8 models '22-) |- |F |4-door wagon w/extended length (Defender 130 '23-) |} SWB=Short-wheelbase, LWB=Long-wheelbase ===Engine Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 7 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | 1 || 3.5L || V8 || Gas ||OHV||MPI. [[w:Rover V8 engine|(Ex-GM) Rover V8 engine]]. Land Rover Range Rover ('87-'88). |- | 1 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Single VANOS (Intake VVT). BMW M62TUB44 engine. Land Rover Range Rover ('03-'05). |- | 2 || 3.9L || V8 || Gas ||OHV||MPI. (Ex-GM) Rover V8 engine.<br> Land Rover Range Rover SWB ('89-'94), Range Rover County Classic [SWB] ('95), Defender 110 ('93),<br> Defender 90 ('94-'95), Discovery ('94-'95). |- | 2 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.0 SE ('95-'99),<br> Discovery ('96-'02), Defender 90 ('97). |- | 2 || 2.5L || 90° V6 || Gas ||DOHC,<br /> 24 valve||Sequential MPI. VIS. [[w:Rover KV6 engine|Rover KV6 engine]]. Land Rover Freelander ('02-'05). |- | 3 || 4.2L || V8 || Gas ||OHV||MPI. (4275 cc, actually 4.3L). (Ex-GM) Rover V8 engine. Land Rover Range Rover County LWB ('93-'95). |- | 3 || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Jaguar AJ33S engine. Land Rover Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 4 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.6 HSE ('96-'99), Discovery ('03). |- | 4 || 4.0L || 60° V6 || Gas ||SOHC,<br /> 12 valve||Sequential MPI. Variable intake manifold. Ford Cologne V6 engine.<br> Land Rover LR3 ('05-'07 & also '08-'09 in Canada). |- | 5 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. LEV.<br> Land Rover Range Rover 4.0 SE ('00), Discovery ('00-'02). |- | 5 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Continuously VCP (Intake VVT). Jaguar AJ41 engine.<br> Land Rover LR3 ('05-'09), Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 6 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. LEV ('00-'02) or ULEV ('03).<br> Land Rover Range Rover 4.6 HSE ('00-'02), 4.6 SE ('01), Discovery ('03). |- | 9 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Discovery ('04). |- | D || 5.0L || V8 || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). CPS (Intake VVL). VIS. Jaguar AJ133 engine (LR-V8).<br> Land Rover LR4 ('10-'13), Range Rover ('10-'13), Range Rover Sport ('10-'13). |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('10-'16), Range Rover Sport ('10-'16). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Range Rover Td6 ('16), Range Rover Sport Td6 ('16). |- | P || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('16), Range Rover Sport ('16). |- | T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 32 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('14-'15), Range Rover Sport ('14-'15). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover LR4 ('14-'16), Range Rover ('14-'16), Range Rover Sport ('14-'16). |- | W || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 24 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('14), Range Rover Sport ('14). |} VVT=Variable Valve Timing. VCP=Variable Camshaft Phasing. VCT=Variable Camshaft Timing. VIS=Variable Intake System. LEV=Low Emissions Vehicle. ULEV=Ultra-Low Emissions Vehicle. CPS=Cam Profile Switching. VVL=Variable Valve Lift. ===Transmission Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |4 |6-speed automatic (Aisin AWF21) (LR2 '08-'09) |- |B |6-speed automatic (Aisin AWF21) (LR2 '10-'15, Range Rover Evoque '12-'13) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '15-'16, Range Rover Evoque '14-'16) |} ===Transmission Type (All models 2017)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |B |8-speed automatic (ZF 8HP) (Discovery '17) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '17, Range Rover Evoque '17) |- |F |8-speed automatic (ZF 8HP) (Range Rover '17, Range Rover Sport '17) |} ===Transmission Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 8 !VIN code !Description |- |2 |5-speed automatic [manual shift mode: Steptronic or CommandShift] (Jatco JF506E) (Freelander '02-'05) |- |4 |4-speed automatic (ZF 4HP22 or w/4.6L V8: 4HP24) (Range Rover '87-'02, Discovery '94-'04, Defender 90 '97) |- |4 |5-speed automatic (ZF 5HP24) (Range Rover '03-'05) |- |4 |6-speed automatic (ZF 6HP26X) (LR3 '05-'09, Range Rover '06-'09, Range Rover Sport '06-'09) |- |4 |6-speed automatic (ZF 6HP28X) (LR4 '10-'13, Range Rover '10-'12, Range Rover Sport '10-'13) |- |6 |8-speed automatic (ZF 8HP) (LR4 '14-'16) |- |8 |5-speed manual (Defender 110 '93, Defender 90 '94-'95, Discovery '94-'97) |- |F |8-speed automatic (ZF 8HP) (Range Rover '13-'16, Range Rover Sport '14-'16) |} All are LHD (Left-hand drive). ===Engine Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover LR2 ('13-'15), Discovery Sport ('15-'16), Range Rover Evoque ('12-'16). |- | N || 3.2L || I6 || Gas ||DOHC,<br /> 24 valve||MPI. VCT (Intake VVT). CPS (Intake VVL). VIS. [[w:Volvo SI6 engine#B6324S5|Volvo SI6 engine - B6324S5]]. Land Rover LR2 ('08-'12). |- |} VCT=Variable Cam Timing. VVT=Variable Valve Timing. CPS=Cam Profile Switching. VVL=Variable Valve Lift. VIS=Variable Intake System. ===Engine Type (All models 2017 only)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('17), Range Rover Sport ('17). |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover Discovery Sport ('17), Range Rover Evoque ('17). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('17), Range Rover Td6 ('17), Range Rover Sport Td6 ('17). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Discovery ('17), Range Rover ('17), Range Rover Sport ('17). |} ==Engine 2018-== ===Engine Variant (All models 2018-)=== {| class="wikitable" |+Position 7 |- ! VIN !! Power Level/Engine !! Transmission !! Model |- |R (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |S (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |F (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19) |- |G (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19), Discovery Sport P290 ('20) |- |F (followed by X) |246 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport P250 ('20-'26), Range Rover Evoque S/SE/1st Edition ('20),<br> Range Rover Evoque P250 ('21-'26) |- |G (followed by X) |296 hp 2.0L Ingenium turbo I4 |9-speed auto. |Range Rover Evoque R-Dynamic S/SE/HSE ('20),<br> Range Rover Evoque P300 HST ('22-'23) |- |R (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P250 ('19-'26) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P300 (Canada only: '19-'20) |- |R (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar D180 ('19) |- |R (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar ('18) |- |F (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P340 ('19-'20) |- |E (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P380 ('19-'20) |- |E (followed by U) |335 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P340 ('21-'23, Canada only: '24-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P400 R-Dynamic HSE ('21-'22), <br> Range Rover Velar P400 HST ('23), <br> Range Rover Velar P400 Dynamic SE/HSE ('24-'25), <br> Range Rover Velar P400 Dynamic SE/Autobiography/Belgravia Ed. ('26) |- |E (followed by E) |550 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Velar SVAutobiography Dynamic ('20) |- |R (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Discovery ('18-'20), Range Rover Sport SE/HSE ('18-'19), Range Rover ('18-'19) |- |R (followed by K) |254 hp 3.0L "Lion" AJD-V6 turbodiesel V6 |8-speed auto. |Discovery Td6 ('18-'20), Range Rover Sport Td6 ('18-'21), Range Rover Td6 ('18-'21) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('21) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('21) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('22-'24) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('25-'26) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('22-'26) |- |S (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Sport HSE Dynamic ('18-'19), Range Rover HSE ('18-'19) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport SE/HSE (Mid '19) |- |S (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport HST (Mid '19) |- |S (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 SE/HSE ('20),<br> Range Rover Sport P360 SE/HSE Silver ('21-'22), Range Rover (L405) P360 ('20-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 HST ('20-'22), Range Rover P400 HSE ('20),<br> Range Rover (L405) P400 HSE Westminster ('21-'22) |- |R (followed by Y) |398 hp 2.0L Ingenium turbo I4 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P400e ('20-'22), Range Rover P400e ('20-'21) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport ('18-'19), Range Rover ('18-'19) |- |S (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('18-'19) |- |S (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover SVAutobiography Dynamic, SVAutobiography LWB ('18-'19) |- |S (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport P525 ('20-'22), Range Rover (L405) P525 ('20-'22) |- |R (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('20-'22) |- |R (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover (L405) SVAutobiography Dynamic, SVAutobiography LWB ('20-'22) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 ('23-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 ('23-'26), <br> Range Rover (L460) P400 SE ('22-'26) |- |E (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P440e ('23) |- |F (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover P440e ('23) |- |E (followed by 4) |454 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P460e ('25-'26) |- |F (followed by 4) |542 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P550e ('24-'26), Range Rover P550e ('24-'26) |- |E (followed by 7) |523 hp 4.4L BMW N63 (JLR NC10)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P530 ('23), <br> Range Rover (L460) P530 ('22-'23) |- |F (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P635 SV Edition One ('24),<br> Range Rover Sport P635 SV Edition Two ('25), Range Rover Sport P635 SV ('26) |- |E (followed by 9) |523 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P530 ('24-'26), Range Rover Sport P530 ('25-'26) |- |F (followed by 9) |606 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P615 SV ('24-'26) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 110 P300 ('20) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 110 P400 ('20) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('21-'22), Defender 110 P300 ('21-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('21-'22), Defender 110 P400 ('21-'22) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('22), Defender 110 P525 ('22) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('23-'25, Canada only: '26), Defender 110 P300 ('23-'26) |- |E (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('23) [Pos. 5 is J] |- |F (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('24-'26) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('23-'26), Defender 110 P400 ('23-'26), Defender 130 P400 ('23-'26) |- |F (followed by E) |493 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 110 P500 ('24-'26), Defender 130 P500 ('24-'26) |- |E (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('23-'26), Defender 110 P525 ('23-'26) |- |E (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Defender 110 P635 OCTA ('25-'26) |} ===Engine Type (All models 2018-)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('18-'22), Range Rover Sport ('18-'22),<br> Range Rover Velar SVAutobiography Dynamic ('20), Defender V8 ('22-'26). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('18-'20), Range Rover Td6 ('18-'21), Range Rover Sport Td6 ('18-'21). |- | N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,<br /> 16 valve||Common-rail Direct Injection. Exhaust VVT. JLR Ingenium AJ20D engine.<br> Land Rover Range Rover Velar ('18-'19) |- | U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine.<br> Land Rover Discovery ('21-), Range Rover ('20-), Range Rover Sport (Mid '19-), Range Rover Velar ('21-), Defender ('20-). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine. Land Rover Discovery ('18-'20),<br> Range Rover ('18-'19), Range Rover Sport ('18-Mid '19), Range Rover Velar ('18-'20). |- | X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine.<br> Land Rover Discovery Sport ('18-'26), Range Rover Evoque ('18-), Range Rover Velar ('18-), Defender ('20-'26), Discovery ('21-). |- | Y || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine + 1 Front motor.<br> 12.4 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P400e ('20-'21), Range Rover Sport P400e ('20-Early '22). |- | 4 || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 24 valve||E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine + 1 Front motor. 31.8 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P440e ('23), P550e ('24-); Range Rover Sport P440e ('23), P460e ('25-), P550e ('24-). |- | 7 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW N63B44T3 [N63TU3] engine [JLR NC10-P8H]. Land Rover Range Rover [L460] ('22-'23), Range Rover Sport ('23). |- | 9 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||48v Mild Hybrid. Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW S68B44TO [S68B44A] engine [JLR NC11-P8S]. Land Rover Range Rover [L460] ('24-), Range Rover Sport ('24-),<br> Defender Octa ('25-). |- |} CVVL=Continuously Variable Valve Lift. ==Check Digit/Gearbox (Position 9)== * USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]] ==Model Year Code (Position 10)== ''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]'' ==Plant Codes (Position 11)== * A - Solihull, West Midlands, England, UK * H - Halewood, Merseyside, England, UK * 2 - Nitra, Slovakia ==External links== * [http://www.clifton.nl/calvin.html CalVIN, the on-line free Land Rover VIN CALculator] * [http://www.fourfold.org/LR_FAQ Land Rover FAQ archive] * [http://www.vindecoderz.com/EN/Land%20Rover Land Rover VIN decoder] {{BookCat}} cylbleru285fz1wi9bvt78rbk56u2op 4679871 4679846 2026-11-04T01:58:39Z JustTheFacts33 3434282 /* Trim Level/Drive Wheels/GVWR/Restraint System (Position 5) */ 4679871 wikitext text/x-wiki {{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}} From 1948 to the early eighties, Land Rover used for their cars chassis numbers of their own format. These formats are described in the table below. Since 1980 Land Rover deploys the standard 17-character Vehicle Identification Number ('''VIN'''), complying with international standards. Car details can be derived (decoded, calculated) from the chassis numbers and the VIN. Typically, the model (Defender, Discovery, Range Rover, Freelander), model type (station wagon, three/four door, etc), wheelbase (90 inch, 100 inch, 110 inch, etc.), engine, LHD/RHD, gearbox, and model year is included in the VIN. ===Chassis number formats over the years=== <table> <tr><th>Description</th><th>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</th><th>Format</th></tr> <tr><td>17-characters, International VIN, 1980-later</td><td></td><td>SAL..............</td></tr> <tr><td>17-characters, Int. VIN for LR do Brazil </td><td></td><td>93R..............</td></tr> <tr><td>17-characters, Int. VIN for AAD, 1985-1995 </td><td></td><td>AAD..............</td></tr> <tr><td>17-characters, US/Canada VIN, 1987-later </td><td></td><td>SAL.................</td></tr> <tr><td>17-characters, Brazil VIN for JLR Brazil, 2016-later </td><td></td><td>99J.................</td></tr> <tr></tr> <tr><td>14-characters: is actually the 17-char</td></tr> <tr><td>VIN missing the SAL bit</td></tr> <tr><td> <tr><td>9-character numbers, 1955 </td><td></td><td>17.6.....</td></tr> <tr><td>9-character numbers, 1956 to 1961 </td><td></td><td>1........</td></tr> <tr><td>9-character numbers, 1950 </td><td></td><td>L........ or R........</td></tr> <tr><td>9-character numbers, 1962 to 1979 </td><td></td><td>.........</td></tr> <tr></tr> <tr><td>8-character numbers, 1948 to 1949 </td><td></td><td>.8......</td></tr> <tr><td>8-character numbers, 1950 to 1953 </td><td></td><td>.6......</td></tr> <tr><td>8-character numbers, 1954 to 1955 </td><td></td><td>.7......</td></tr> <tr></tr> <tr><td>7-character numbers, 1948 to 1949 </td><td></td><td>.......</td></tr> <tr><td>6-character numbers, ???? prototypes </td><td></td><td>110F..</td></tr> <tr><td>3-character numbers, 1948 prototypes </td><td></td><td>R.. or L..</td></tr> </table> ===Land Rover WMIs (1981-) (Position 1-3)=== * SAL - Land Rover (UK & Europe) * 99J - JLR Brazil * L2C - Chery Jaguar Land Rover (China) ===Model Line=== {| class="wikitable" |+Position 4 !VIN code !Description |- |A |[[w:Land Rover Discovery#Discovery 3 / LR3 (2004–2009)|Land Rover LR3]] ('05-'09) |- |A |[[w:Land Rover Discovery#Discovery 4 / LR4 (2009–2016)|Land Rover LR4]] ('10-'16) |- |C |[[w:Land Rover Discovery Sport|Land Rover Discovery Sport]] ('15-'26) |- |D |[[w:Land Rover Defender#North American Specification (NAS) Defenders|Land Rover Defender]] ('93-'95, '97) |- |E |[[w:Land Rover Defender (L663)|Land Rover Defender (L663)]] ('20-) |- |F |[[w:Land Rover Freelander#Freelander 2 (L359; 2006–2015)|Land Rover LR2]] ('08-'15) |- |G |[[w:Range Rover (L405)|Land Rover Range Rover (L405)]] (4th gen.) ('13-'22) |- |H |[[w:Range Rover Classic|Land Rover Range Rover/Range Rover Classic]] (1st gen.) ('87-'95) |- |J |[[w:Land Rover Discovery#First & Second generation Discovery|Land Rover Discovery]] ('94-'98 & '99 Discovery SD) |- |K |[[w:Range Rover (L460)|Land Rover Range Rover (L460)]] (5th gen.) (Mid '22-) |- |M |[[w:Range Rover (L322)|Land Rover Range Rover (L322)]] (3rd gen.) ('03-'12) |- |N |[[w:Land Rover Freelander#Freelander in North America|Land Rover Freelander]] ('02-'05) |- |P |[[w:Range Rover (P38A)|Land Rover Range Rover (P38A)]] (2nd gen.) ('95-'02) |- |R |[[w:Land Rover Discovery#Fifth generation Discovery (L462; 2017–present)|Land Rover Discovery]] ('17-) |- |S |[[w:Range Rover Sport#First generation (L320; 2005)|Land Rover Range Rover Sport]] (1st gen.) ('06-'13) |- |T |[[w:Land Rover Discovery#Discovery Series II (L318; 1998–2004)|Land Rover Discovery Series II]] ('99-'04) |- |V |[[w:Range Rover Evoque#First generation (L538; 2011)|Land Rover Range Rover Evoque]] (1st gen.) ('12-'19) |- |W |[[w:Range Rover Sport#Second generation (L494; 2013)|Land Rover Range Rover Sport]] (2nd gen.) ('14-'22) |- |Y |[[w:Range Rover Velar|Land Rover Range Rover Velar]] (1st gen.) ('18-) |- |Z |[[w:Range Rover Evoque#Second generation (L551; 2018)|Land Rover Range Rover Evoque]] (2nd gen.) ('20-) |- |1 |[[w:Range Rover Sport#Third generation (L461; 2022)|Land Rover Range Rover Sport]] (3rd gen.) ('23-) |- |} ===Model Series/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |V (following H) |Range Rover 100" wheelbase (1st gen.) |Class E |- |E (following H) |Range Rover 100" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |C (following H) |Range Rover LWB 108" wheelbase (1st gen.) |Class E |- |F (following H) |Range Rover LWB 108" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |H (following D) |Defender 110 ('93) |Class E |- |V (following D) |Defender 90 ('94-'95, '97) |Class E |- |X (following D) |Defender 90 (CA emissions) ('95) |Class E |- |Y (following J) |Discovery ('94-'98 & '99 Discovery SD) |Class E |- |N (following J) |Discovery (CA emissions) ('95-'96) |Class E |- |Y (following T) |Discovery Series II ('99-'00) |Class E |- |V (following P) |Range Rover (2nd gen.) ('95-'98) |Class E |- |E (following P) |Range Rover (2nd gen.) (CA emissions) ('95-'96) |Class E |- |A (following P) |Range Rover (2nd gen.) (GEMS engine management) (Early '99) |Class E |- |V (following P) |Range Rover (2nd gen.) (Bosch engine management) ('99-'00) |Class E |- |C (following P) |Range Rover 4.6 HSE Callaway Edition (2nd gen.) (Callaway-modified engine) ('99) |Class E |- |} ===Model Series/Trim Level/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |M (following N) |Freelander S ('02-'03) |Class C |- |Y (following N) |Freelander SE ('02-'05), SE3 ('03-'05) |Class C |- |E (following N) |Freelander HSE ('02-'04) |Class C |- |L (following T) |Discovery Series II SD ('01-'02), S ('03-'04) |Class E |- |K (following T) |Discovery Series II SD7 ('01-'02), S7 ('03-'04) |Class E |- |Y (following T) |Discovery Series II SE ('01-'04) |Class E |- |W (following T) |Discovery Series II SE7 ('01-'04) |Class E |- |H (following T) |Discovery Series II LE ('01) |Class E |- |J (following T) |Discovery Series II LE7 ('01) |Class E |- |P (following T) |Discovery Series II HSE ('03-'04) |Class E |- |R (following T) |Discovery Series II HSE7 ('03-'04) |Class E |- |L (following P) |Range Rover (2nd gen.) 4.6 SE ('01) |Class E |- |M (following P) |Range Rover (2nd gen.) 4.6 HSE ('01-'02), Westminster Edition ('02) |Class E |- |H (following M) |Range Rover (3rd gen.) Westminster Edition ('04-'05) |Class E |- |} ===Trim Level/Drive Wheels/GVWR/Restraint System (Position 5)=== {| class="wikitable" |+Position 5 !VIN code !Trim Level !Drive Wheels !GVWR !Restraint System |- |J |LR2 base model - Canada only: '14 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |N |Range Rover Evoque Pure '12 (Canada only), '13-'15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |LR2 '10, LR2 base model - Canada only: '13,<br> LR2 SE - Canada only: '14,<br> LR2 base model '15, Discovery Sport SE '15-'19,<br> Range Rover Evoque Pure Plus '12-'15,<br> Range Rover Evoque SE, SE Premium '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque Landmark Edition 4-d '18-'19 <br> [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |LR2 base model (US only) '11-'14,<br> LR2 HSE (US & Canada) '10-'15, LR2 HSE Plus '10,<br> Discovery Sport HSE '15-'18,<br> Range Rover Evoque Pure Premium '12-'15,<br> Range Rover Evoque HSE '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE '19, Landmark Edition '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque Prestige Premium '12-'14, Prestige '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |LR2 HSE Lux '10-'15, Discovery Sport HSE Lux '15-'18,<br> Range Rover Evoque Dynamic Premium '12-'14,<br> Dynamic '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic '16-'19 [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d '16 [Pos. 6 is 1] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |E |Range Rover Evoque Autobiography '15-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque SE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |K |Discovery Sport base model '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |J |Discovery Sport S '20-25, Range Rover Evoque S '20-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |Discovery Sport SE '20-'23, Range Rover Evoque SE '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |9 |Discovery Sport HSE '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque First Edition '20 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport R-Dynamic S '20-'23,<br> Range Rover Evoque R-Dynamic S '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport R-Dynamic SE '20-'23,<br> Discovery Sport Dynamic SE '24-'25,<br> Range Rover Evoque R-Dynamic SE '21-'23,<br> Range Rover Evoque Dynamic SE '24-'26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport Landmark Edition '26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque R-Dynamic SE '20 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |M |Discovery Sport R-Dynamic HSE '20, Canada only: '21-'23,<br> Discovery Sport Dynamic HSE - Canada only: '24-'25,<br> Range Rover Evoque R-Dynamic HSE '20-'21,<br> Range Rover Evoque Dynamic HSE - Canada only: '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P250 Bronze Collection - <br> Canada only: '22-'23 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P300 HST '22-'23 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque P250 Hoxton Edition '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |1 |Range Rover Evoque P250 Autobiography - Canada only: '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |A |Range Rover Velar base model '18-'19 [Pos. 8 is X] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Range Rover Velar S '18-'20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Velar S '21-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |Range Rover Velar SE - Canada only: '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar R-Dynamic SE '18-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |A |Range Rover Velar R-Dynamic SE '19 (some early prod. w/340-hp engine) [Pos. 7 is F & Pos. 8 is V] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Velar R-Dynamic S '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Velar R-Dynamic S '21-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar Dynamic SE '24-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar R-Dynamic HSE '18-'22, First Edition '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar HST '23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar Dynamic HSE '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar Belgravia Edition '26,<br> Belgravia Edition Satin '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Velar Autobiography '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Velar SVAutobiography Dynamic '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |LR4 base model w/2 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |LR4 base model w/3 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |LR4 HSE w/2 rows of seats - '10, Canada only: '13-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |LR4 HSE w/3 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |LR4 HSE Plus w/2 rows of seats '10 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |LR4 HSE Plus w/3 rows of seats '10 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |LR4 HSE Lux w/3 rows of seats '10-'16,<br> HSE Lux XXV Ltd. Ed. w/3 rows of seats '14 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Sport HSE '10-'13,<br> HSE GT Limited Edition '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Sport HSE Luxury '10-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Range Rover Sport Supercharged '10-'13,<br> Supercharged Limited Edition '13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport Autobiography '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |Discovery SE '17-'20, Range Rover Sport SE '14-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Discovery Landmark Edition '20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P300 S '21-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P360 S - Canada only: '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P300 R-Dynamic S '21-'23 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P360 R-Dynamic S '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P300 Dynamic SE '24-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P360 Dynamic SE '24-'25, Canada only: '26 <br> [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Discovery P360 R-Dynamic HSE '21-'23,<br> P360 Dynamic HSE - Canada only: '24-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Metropolitan Edition '23-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Gemini Edition '26,<br> Discovery P360 Tempest Edition '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '14 <br> [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '15, HSE Limited Edition '15 <br> [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Discovery HSE '17-'20,<br> Range Rover Sport HSE '17-'18 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '19 [Pos. 8 is V or K or U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '20, HSE Silver Edition '21 <br> [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE Silver Edition '22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Discovery HSE Luxury '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery HSE Luxury '18-'20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery First Edition '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST '16 [Pos. 7 is P or V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport HSE Dynamic '17-'19 [Pos. 8 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST Mid '19-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport P400e HSE '20,<br> P400e HSE Silver Edition '21-'22 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P400e Autobiography '20-'21 <br> [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '15,<br> Supercharged Limited Edition '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '16,<br> Supercharged Dynamic '16,<br> Supercharged Dynamic Limited Edition '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '17-'18,<br> Supercharged Dynamic '17-'19,<br> HSE Dynamic '20-'22 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '17, '19-'22,<br> Autobiography Dynamic '18 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport SVR '15-'22, SVR Carbon Edition '21-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Sport P360 S '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport P360 SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Sport P400 Dynamic S - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Sport Dynamic SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P400 Dynamic HSE - <br> Canada only: '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P440e Autobiography '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P440e HSE Dynamic - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P550e Autobiography '24-'26,<br> P530 Autobiography '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P530 First Edition '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition One w/Obsidian Black or Flux Silver paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Edition One w/Carbon Bronze paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition Two '25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Range Rover Sport P635 SV '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Range Rover Sport P635 SV Carbon '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |E |Range Rover HSE '10-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover HSE Luxury '10-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Supercharged '10-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Autobiography '10-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover (L405) base model '13-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '13 [Pos. 7 is D] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '14 [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '15, HSE Limited Edition '15 [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '17-'19 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '20 [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '21 [Pos. 8 is K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE Westminster Edition '21-'22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover P400e HSE '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover P400e Autobiography '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '13 <br> [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '14,<br> Supercharged SWB Ebony Edition '14 <br> [Pos. 6 is 2 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '15,<br> Supercharged SWB Limited Edition '15 <br> [Pos. 6 is 2 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '16 <br> [Pos. 6 is 2 & Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '17-'19,<br> P525 HSE SWB '20,<br> P525 HSE Westminster Edition SWB '21-'22 <br> [Pos. 6 is 2 & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography SWB '13-'22 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition SWB '21 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography Dynamic '17-'22,<br> SVAutobiography Dynamic Black '21-'22 [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE LWB '15 <br> [Pos. 6 is 3 & Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '14 <br> [Pos. 6 is 3 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '15,<br> Supercharged LWB Limited Edition '15 <br> [Pos. 6 is 3 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '16 <br> [Pos. 6 is 3 & Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '17-'19,<br> P525 HSE LWB '20,<br> P525 HSE Westminster Edition LWB '21-'22 <br> [Pos. 6 is 5 & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '14-'15 [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '16 [Pos. 6 is 3] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '17-'22 [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) Autobiography Black LWB '14-'15 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition LWB '21 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '16-'17 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '18-'22 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover (L460) SE '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover (L460) Autobiography '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L460) P530 First Edition '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover (L460) P530 SV '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover (L460) P615 SV '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover (L460) P615 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 90 base model '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/2 rows of seats '20-'23 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/3 rows of seats '20-'23 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 90 S '21-'25, Canada only: '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 130 S w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Defender 90 X-Dynamic S '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 90 P400 SE '23 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/2 rows of seats '20-'23 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P500 SE w/2 rows of seats '24 [Pos. 6 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/3 rows of seats '20-'23 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 130 P400 SE w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 90 P400 X-Dynamic SE '22-'26,<br> Defender 90 X-Dynamic SE Sedona Red '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/2 rows of seats '21-'26 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P500 X-Dynamic SE w/2 rows of seats '25-'26 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/3 rows of seats '21-'26 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 130 P400 X-Dynamic SE w/3 rows of seats '23-'26 <br> [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 90 X-Dynamic HSE '22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/2 rows of seats '21-'22 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/3 rows of seats '21-'22 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/2 rows of seats '22 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/3 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 75th Limited Edition '23 <br> [Pos. 6 is 6 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 75th Limited Edition w/2 rows of seats '23 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Sedona Red Edition w/2 rows of seats '25 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Trophy Edition w/2 rows of seats '26 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P400 Outbound w/2 rows of seats '24-'26 <br> [Pos. 6 is F & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 90 First Edition '21 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 130 First Edition w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 90 X '21-'23, Canada only: '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 130 X w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 90 P525 V8 '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 P525 V8 '22-'23, '25-'26,<br> P525 V8 Carpathian Edition '22-'24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 110 P525 V8 w/2 rows of seats '24 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 P525 V8 w/2 rows of seats '22-'23, '25-'26,<br> P525 V8 Carpathian Edition w/2 rows of seats '22-'24,<br> P525 V8 Bond Edition w/2 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 130 P500 V8 w/3 rows of seats '24 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P500 V8 w/3 rows of seats '25-'26 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Defender 110 P635 OCTA w/2 rows of seats '25-'26,<br> P635 OCTA Edition One w/2 rows of seats '25,<br> P635 OCTA Black w/2 rows of seats '26 <br> [Pos. 6 is E & Pos. 8 is 9] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |} ===Body Type=== {| class="wikitable" |+Position 6 !VIN code !Description |- |1 |4-door wagon (Range Rover '87-'12, Defender 110 '93, Discovery '94-'04) |- |1 |2-door soft top (Freelander SE3) ('03-'05) |- |1 |2-door wagon (Range Rover Evoque 2-d '12-'17) |- |2 |2-door soft top (Defender 90) ('94-'95, '97) |- |2 |4-door wagon (Freelander) ('02-'05) |- |2 |4-door wagon (LR2 '08-'15, Discovery Sport '15-'26, Range Rover Evoque 4-d '12-, LR3 '05-'09, LR4 '10-'16, Discovery '18-, Range Rover Sport '06-'22, Range Rover Sport P400e '20, Range Rover SWB (L405) '13-'22, Range Rover Velar '18-) |- |3 |2-door wagon (Defender 90) ('95, '97) |- |3 |4-door wagon LWB (Range Rover LWB '14-'16) |- |3 |4-door wagon LWB w/Class E GVWR (Range Rover SVAutobiography LWB '17) |- |4 |4-door wagon [[w:Plug-in hybrid|PHEV]] (Range Rover P400e '20-'21, Range Rover Sport P400e '21-Early '22) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover Supercharged LWB & Autobiography LWB '17) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover LWB (L405) '18-'22) |- |5 |2-door convertible (Range Rover Evoque convertible '17-'19) |- |6 |2-door wagon (Defender 90 '21-) |- |7 |4-door wagon w/2 rows of seating (Defender 110 P300/P400 '20-) |- |9 |4-door wagon (Range Rover SWB (L460) '22-, Range Rover Sport '23-) |- |B |4-door wagon (Discovery '17) |- |B |4-door wagon LWB (Range Rover LWB (L460) '22-) |- |E |4-door wagon w/3 rows of seating (Defender 110 P300/P400 w/opt. 3rd row '20-) |- |E |4-door wagon w/2 rows of seating (Defender 110 V8 models '22-) |- |F |4-door wagon w/extended length (Defender 130 '23-) |} SWB=Short-wheelbase, LWB=Long-wheelbase ===Engine Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 7 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | 1 || 3.5L || V8 || Gas ||OHV||MPI. [[w:Rover V8 engine|(Ex-GM) Rover V8 engine]]. Land Rover Range Rover ('87-'88). |- | 1 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Single VANOS (Intake VVT). BMW M62TUB44 engine. Land Rover Range Rover ('03-'05). |- | 2 || 3.9L || V8 || Gas ||OHV||MPI. (Ex-GM) Rover V8 engine.<br> Land Rover Range Rover SWB ('89-'94), Range Rover County Classic [SWB] ('95), Defender 110 ('93),<br> Defender 90 ('94-'95), Discovery ('94-'95). |- | 2 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.0 SE ('95-'99),<br> Discovery ('96-'02), Defender 90 ('97). |- | 2 || 2.5L || 90° V6 || Gas ||DOHC,<br /> 24 valve||Sequential MPI. VIS. [[w:Rover KV6 engine|Rover KV6 engine]]. Land Rover Freelander ('02-'05). |- | 3 || 4.2L || V8 || Gas ||OHV||MPI. (4275 cc, actually 4.3L). (Ex-GM) Rover V8 engine. Land Rover Range Rover County LWB ('93-'95). |- | 3 || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Jaguar AJ33S engine. Land Rover Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 4 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.6 HSE ('96-'99), Discovery ('03). |- | 4 || 4.0L || 60° V6 || Gas ||SOHC,<br /> 12 valve||Sequential MPI. Variable intake manifold. Ford Cologne V6 engine.<br> Land Rover LR3 ('05-'07 & also '08-'09 in Canada). |- | 5 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. LEV.<br> Land Rover Range Rover 4.0 SE ('00), Discovery ('00-'02). |- | 5 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Continuously VCP (Intake VVT). Jaguar AJ41 engine.<br> Land Rover LR3 ('05-'09), Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 6 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. LEV ('00-'02) or ULEV ('03).<br> Land Rover Range Rover 4.6 HSE ('00-'02), 4.6 SE ('01), Discovery ('03). |- | 9 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Discovery ('04). |- | D || 5.0L || V8 || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). CPS (Intake VVL). VIS. Jaguar AJ133 engine (LR-V8).<br> Land Rover LR4 ('10-'13), Range Rover ('10-'13), Range Rover Sport ('10-'13). |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('10-'16), Range Rover Sport ('10-'16). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Range Rover Td6 ('16), Range Rover Sport Td6 ('16). |- | P || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('16), Range Rover Sport ('16). |- | T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 32 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('14-'15), Range Rover Sport ('14-'15). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover LR4 ('14-'16), Range Rover ('14-'16), Range Rover Sport ('14-'16). |- | W || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 24 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('14), Range Rover Sport ('14). |} VVT=Variable Valve Timing. VCP=Variable Camshaft Phasing. VCT=Variable Camshaft Timing. VIS=Variable Intake System. LEV=Low Emissions Vehicle. ULEV=Ultra-Low Emissions Vehicle. CPS=Cam Profile Switching. VVL=Variable Valve Lift. ===Transmission Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |4 |6-speed automatic (Aisin AWF21) (LR2 '08-'09) |- |B |6-speed automatic (Aisin AWF21) (LR2 '10-'15, Range Rover Evoque '12-'13) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '15-'16, Range Rover Evoque '14-'16) |} ===Transmission Type (All models 2017)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |B |8-speed automatic (ZF 8HP) (Discovery '17) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '17, Range Rover Evoque '17) |- |F |8-speed automatic (ZF 8HP) (Range Rover '17, Range Rover Sport '17) |} ===Transmission Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 8 !VIN code !Description |- |2 |5-speed automatic [manual shift mode: Steptronic or CommandShift] (Jatco JF506E) (Freelander '02-'05) |- |4 |4-speed automatic (ZF 4HP22 or w/4.6L V8: 4HP24) (Range Rover '87-'02, Discovery '94-'04, Defender 90 '97) |- |4 |5-speed automatic (ZF 5HP24) (Range Rover '03-'05) |- |4 |6-speed automatic (ZF 6HP26X) (LR3 '05-'09, Range Rover '06-'09, Range Rover Sport '06-'09) |- |4 |6-speed automatic (ZF 6HP28X) (LR4 '10-'13, Range Rover '10-'12, Range Rover Sport '10-'13) |- |6 |8-speed automatic (ZF 8HP) (LR4 '14-'16) |- |8 |5-speed manual (Defender 110 '93, Defender 90 '94-'95, Discovery '94-'97) |- |F |8-speed automatic (ZF 8HP) (Range Rover '13-'16, Range Rover Sport '14-'16) |} All are LHD (Left-hand drive). ===Engine Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover LR2 ('13-'15), Discovery Sport ('15-'16), Range Rover Evoque ('12-'16). |- | N || 3.2L || I6 || Gas ||DOHC,<br /> 24 valve||MPI. VCT (Intake VVT). CPS (Intake VVL). VIS. [[w:Volvo SI6 engine#B6324S5|Volvo SI6 engine - B6324S5]]. Land Rover LR2 ('08-'12). |- |} VCT=Variable Cam Timing. VVT=Variable Valve Timing. CPS=Cam Profile Switching. VVL=Variable Valve Lift. VIS=Variable Intake System. ===Engine Type (All models 2017 only)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('17), Range Rover Sport ('17). |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover Discovery Sport ('17), Range Rover Evoque ('17). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('17), Range Rover Td6 ('17), Range Rover Sport Td6 ('17). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Discovery ('17), Range Rover ('17), Range Rover Sport ('17). |} ==Engine 2018-== ===Engine Variant (All models 2018-)=== {| class="wikitable" |+Position 7 |- ! VIN !! Power Level/Engine !! Transmission !! Model |- |R (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |S (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |F (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19) |- |G (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19), Discovery Sport P290 ('20) |- |F (followed by X) |246 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport P250 ('20-'26), Range Rover Evoque S/SE/1st Edition ('20),<br> Range Rover Evoque P250 ('21-'26) |- |G (followed by X) |296 hp 2.0L Ingenium turbo I4 |9-speed auto. |Range Rover Evoque R-Dynamic S/SE/HSE ('20),<br> Range Rover Evoque P300 HST ('22-'23) |- |R (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P250 ('19-'26) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P300 (Canada only: '19-'20) |- |R (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar D180 ('19) |- |R (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar ('18) |- |F (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P340 ('19-'20) |- |E (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P380 ('19-'20) |- |E (followed by U) |335 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P340 ('21-'23, Canada only: '24-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P400 R-Dynamic HSE ('21-'22), <br> Range Rover Velar P400 HST ('23), <br> Range Rover Velar P400 Dynamic SE/HSE ('24-'25), <br> Range Rover Velar P400 Dynamic SE/Autobiography/Belgravia Ed. ('26) |- |E (followed by E) |550 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Velar SVAutobiography Dynamic ('20) |- |R (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Discovery ('18-'20), Range Rover Sport SE/HSE ('18-'19), Range Rover ('18-'19) |- |R (followed by K) |254 hp 3.0L "Lion" AJD-V6 turbodiesel V6 |8-speed auto. |Discovery Td6 ('18-'20), Range Rover Sport Td6 ('18-'21), Range Rover Td6 ('18-'21) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('21) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('21) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('22-'24) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('25-'26) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('22-'26) |- |S (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Sport HSE Dynamic ('18-'19), Range Rover HSE ('18-'19) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport SE/HSE (Mid '19) |- |S (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport HST (Mid '19) |- |S (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 SE/HSE ('20),<br> Range Rover Sport P360 SE/HSE Silver ('21-'22), Range Rover (L405) P360 ('20-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 HST ('20-'22), Range Rover P400 HSE ('20),<br> Range Rover (L405) P400 HSE Westminster ('21-'22) |- |R (followed by Y) |398 hp 2.0L Ingenium turbo I4 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P400e ('20-'22), Range Rover P400e ('20-'21) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport ('18-'19), Range Rover ('18-'19) |- |S (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('18-'19) |- |S (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover SVAutobiography Dynamic, SVAutobiography LWB ('18-'19) |- |S (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport P525 ('20-'22), Range Rover (L405) P525 ('20-'22) |- |R (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('20-'22) |- |R (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover (L405) SVAutobiography Dynamic, SVAutobiography LWB ('20-'22) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 ('23-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 ('23-'26), <br> Range Rover (L460) P400 SE ('22-'26) |- |E (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P440e ('23) |- |F (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover P440e ('23) |- |E (followed by 4) |454 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P460e ('25-'26) |- |F (followed by 4) |542 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P550e ('24-'26), Range Rover P550e ('24-'26) |- |E (followed by 7) |523 hp 4.4L BMW N63 (JLR NC10)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P530 ('23), <br> Range Rover (L460) P530 ('22-'23) |- |F (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P635 SV Edition One ('24),<br> Range Rover Sport P635 SV Edition Two ('25), Range Rover Sport P635 SV ('26) |- |E (followed by 9) |523 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P530 ('24-'26), Range Rover Sport P530 ('25-'26) |- |F (followed by 9) |606 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P615 SV ('24-'26) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 110 P300 ('20) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 110 P400 ('20) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('21-'22), Defender 110 P300 ('21-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('21-'22), Defender 110 P400 ('21-'22) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('22), Defender 110 P525 ('22) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('23-'25, Canada only: '26), Defender 110 P300 ('23-'26) |- |E (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('23) [Pos. 5 is J] |- |F (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('24-'26) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('23-'26), Defender 110 P400 ('23-'26), Defender 130 P400 ('23-'26) |- |F (followed by E) |493 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 110 P500 ('24-'26), Defender 130 P500 ('24-'26) |- |E (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('23-'26), Defender 110 P525 ('23-'26) |- |E (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Defender 110 P635 OCTA ('25-'26) |} ===Engine Type (All models 2018-)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('18-'22), Range Rover Sport ('18-'22),<br> Range Rover Velar SVAutobiography Dynamic ('20), Defender V8 ('22-'26). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('18-'20), Range Rover Td6 ('18-'21), Range Rover Sport Td6 ('18-'21). |- | N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,<br /> 16 valve||Common-rail Direct Injection. Exhaust VVT. JLR Ingenium AJ20D engine.<br> Land Rover Range Rover Velar ('18-'19) |- | U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine.<br> Land Rover Discovery ('21-), Range Rover ('20-), Range Rover Sport (Mid '19-), Range Rover Velar ('21-), Defender ('20-). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine. Land Rover Discovery ('18-'20),<br> Range Rover ('18-'19), Range Rover Sport ('18-Mid '19), Range Rover Velar ('18-'20). |- | X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine.<br> Land Rover Discovery Sport ('18-'26), Range Rover Evoque ('18-), Range Rover Velar ('18-), Defender ('20-'26), Discovery ('21-). |- | Y || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine + 1 Front motor.<br> 12.4 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P400e ('20-'21), Range Rover Sport P400e ('20-Early '22). |- | 4 || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 24 valve||E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine + 1 Front motor. 31.8 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P440e ('23), P550e ('24-); Range Rover Sport P440e ('23), P460e ('25-), P550e ('24-). |- | 7 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW N63B44T3 [N63TU3] engine [JLR NC10-P8H]. Land Rover Range Rover [L460] ('22-'23), Range Rover Sport ('23). |- | 9 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||48v Mild Hybrid. Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW S68B44TO [S68B44A] engine [JLR NC11-P8S]. Land Rover Range Rover [L460] ('24-), Range Rover Sport ('24-),<br> Defender Octa ('25-). |- |} CVVL=Continuously Variable Valve Lift. ==Check Digit/Gearbox (Position 9)== * USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]] ==Model Year Code (Position 10)== ''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]'' ==Plant Codes (Position 11)== * A - Solihull, West Midlands, England, UK * H - Halewood, Merseyside, England, UK * 2 - Nitra, Slovakia ==External links== * [http://www.clifton.nl/calvin.html CalVIN, the on-line free Land Rover VIN CALculator] * [http://www.fourfold.org/LR_FAQ Land Rover FAQ archive] * [http://www.vindecoderz.com/EN/Land%20Rover Land Rover VIN decoder] {{BookCat}} rncpu1tqmz8a8tstlxnkgcpzyjkd1de 4679872 4679871 2026-11-04T02:12:33Z JustTheFacts33 3434282 /* Trim Level/Drive Wheels/GVWR/Restraint System (Position 5) */ 4679872 wikitext text/x-wiki {{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}} From 1948 to the early eighties, Land Rover used for their cars chassis numbers of their own format. These formats are described in the table below. Since 1980 Land Rover deploys the standard 17-character Vehicle Identification Number ('''VIN'''), complying with international standards. Car details can be derived (decoded, calculated) from the chassis numbers and the VIN. Typically, the model (Defender, Discovery, Range Rover, Freelander), model type (station wagon, three/four door, etc), wheelbase (90 inch, 100 inch, 110 inch, etc.), engine, LHD/RHD, gearbox, and model year is included in the VIN. ===Chassis number formats over the years=== <table> <tr><th>Description</th><th>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</th><th>Format</th></tr> <tr><td>17-characters, International VIN, 1980-later</td><td></td><td>SAL..............</td></tr> <tr><td>17-characters, Int. VIN for LR do Brazil </td><td></td><td>93R..............</td></tr> <tr><td>17-characters, Int. VIN for AAD, 1985-1995 </td><td></td><td>AAD..............</td></tr> <tr><td>17-characters, US/Canada VIN, 1987-later </td><td></td><td>SAL.................</td></tr> <tr><td>17-characters, Brazil VIN for JLR Brazil, 2016-later </td><td></td><td>99J.................</td></tr> <tr></tr> <tr><td>14-characters: is actually the 17-char</td></tr> <tr><td>VIN missing the SAL bit</td></tr> <tr><td> <tr><td>9-character numbers, 1955 </td><td></td><td>17.6.....</td></tr> <tr><td>9-character numbers, 1956 to 1961 </td><td></td><td>1........</td></tr> <tr><td>9-character numbers, 1950 </td><td></td><td>L........ or R........</td></tr> <tr><td>9-character numbers, 1962 to 1979 </td><td></td><td>.........</td></tr> <tr></tr> <tr><td>8-character numbers, 1948 to 1949 </td><td></td><td>.8......</td></tr> <tr><td>8-character numbers, 1950 to 1953 </td><td></td><td>.6......</td></tr> <tr><td>8-character numbers, 1954 to 1955 </td><td></td><td>.7......</td></tr> <tr></tr> <tr><td>7-character numbers, 1948 to 1949 </td><td></td><td>.......</td></tr> <tr><td>6-character numbers, ???? prototypes </td><td></td><td>110F..</td></tr> <tr><td>3-character numbers, 1948 prototypes </td><td></td><td>R.. or L..</td></tr> </table> ===Land Rover WMIs (1981-) (Position 1-3)=== * SAL - Land Rover (UK & Europe) * 99J - JLR Brazil * L2C - Chery Jaguar Land Rover (China) ===Model Line=== {| class="wikitable" |+Position 4 !VIN code !Description |- |A |[[w:Land Rover Discovery#Discovery 3 / LR3 (2004–2009)|Land Rover LR3]] ('05-'09) |- |A |[[w:Land Rover Discovery#Discovery 4 / LR4 (2009–2016)|Land Rover LR4]] ('10-'16) |- |C |[[w:Land Rover Discovery Sport|Land Rover Discovery Sport]] ('15-'26) |- |D |[[w:Land Rover Defender#North American Specification (NAS) Defenders|Land Rover Defender]] ('93-'95, '97) |- |E |[[w:Land Rover Defender (L663)|Land Rover Defender (L663)]] ('20-) |- |F |[[w:Land Rover Freelander#Freelander 2 (L359; 2006–2015)|Land Rover LR2]] ('08-'15) |- |G |[[w:Range Rover (L405)|Land Rover Range Rover (L405)]] (4th gen.) ('13-'22) |- |H |[[w:Range Rover Classic|Land Rover Range Rover/Range Rover Classic]] (1st gen.) ('87-'95) |- |J |[[w:Land Rover Discovery#First & Second generation Discovery|Land Rover Discovery]] ('94-'98 & '99 Discovery SD) |- |K |[[w:Range Rover (L460)|Land Rover Range Rover (L460)]] (5th gen.) (Mid '22-) |- |M |[[w:Range Rover (L322)|Land Rover Range Rover (L322)]] (3rd gen.) ('03-'12) |- |N |[[w:Land Rover Freelander#Freelander in North America|Land Rover Freelander]] ('02-'05) |- |P |[[w:Range Rover (P38A)|Land Rover Range Rover (P38A)]] (2nd gen.) ('95-'02) |- |R |[[w:Land Rover Discovery#Fifth generation Discovery (L462; 2017–present)|Land Rover Discovery]] ('17-) |- |S |[[w:Range Rover Sport#First generation (L320; 2005)|Land Rover Range Rover Sport]] (1st gen.) ('06-'13) |- |T |[[w:Land Rover Discovery#Discovery Series II (L318; 1998–2004)|Land Rover Discovery Series II]] ('99-'04) |- |V |[[w:Range Rover Evoque#First generation (L538; 2011)|Land Rover Range Rover Evoque]] (1st gen.) ('12-'19) |- |W |[[w:Range Rover Sport#Second generation (L494; 2013)|Land Rover Range Rover Sport]] (2nd gen.) ('14-'22) |- |Y |[[w:Range Rover Velar|Land Rover Range Rover Velar]] (1st gen.) ('18-) |- |Z |[[w:Range Rover Evoque#Second generation (L551; 2018)|Land Rover Range Rover Evoque]] (2nd gen.) ('20-) |- |1 |[[w:Range Rover Sport#Third generation (L461; 2022)|Land Rover Range Rover Sport]] (3rd gen.) ('23-) |- |} ===Model Series/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |V (following H) |Range Rover 100" wheelbase (1st gen.) |Class E |- |E (following H) |Range Rover 100" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |C (following H) |Range Rover LWB 108" wheelbase (1st gen.) |Class E |- |F (following H) |Range Rover LWB 108" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |H (following D) |Defender 110 ('93) |Class E |- |V (following D) |Defender 90 ('94-'95, '97) |Class E |- |X (following D) |Defender 90 (CA emissions) ('95) |Class E |- |Y (following J) |Discovery ('94-'98 & '99 Discovery SD) |Class E |- |N (following J) |Discovery (CA emissions) ('95-'96) |Class E |- |Y (following T) |Discovery Series II ('99-'00) |Class E |- |V (following P) |Range Rover (2nd gen.) ('95-'98) |Class E |- |E (following P) |Range Rover (2nd gen.) (CA emissions) ('95-'96) |Class E |- |A (following P) |Range Rover (2nd gen.) (GEMS engine management) (Early '99) |Class E |- |V (following P) |Range Rover (2nd gen.) (Bosch engine management) ('99-'00) |Class E |- |C (following P) |Range Rover 4.6 HSE Callaway Edition (2nd gen.) (Callaway-modified engine) ('99) |Class E |- |} ===Model Series/Trim Level/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |M (following N) |Freelander S ('02-'03) |Class C |- |Y (following N) |Freelander SE ('02-'05), SE3 ('03-'05) |Class C |- |E (following N) |Freelander HSE ('02-'04) |Class C |- |L (following T) |Discovery Series II SD ('01-'02), S ('03-'04) |Class E |- |K (following T) |Discovery Series II SD7 ('01-'02), S7 ('03-'04) |Class E |- |Y (following T) |Discovery Series II SE ('01-'04) |Class E |- |W (following T) |Discovery Series II SE7 ('01-'04) |Class E |- |H (following T) |Discovery Series II LE ('01) |Class E |- |J (following T) |Discovery Series II LE7 ('01) |Class E |- |P (following T) |Discovery Series II HSE ('03-'04) |Class E |- |R (following T) |Discovery Series II HSE7 ('03-'04) |Class E |- |L (following P) |Range Rover (2nd gen.) 4.6 SE ('01) |Class E |- |M (following P) |Range Rover (2nd gen.) 4.6 HSE ('01-'02), Westminster Edition ('02) |Class E |- |H (following M) |Range Rover (3rd gen.) Westminster Edition ('04-'05) |Class E |- |} ===Trim Level/Drive Wheels/GVWR/Restraint System (Position 5) 2010-=== {| class="wikitable" |+Position 5 !VIN code !Trim Level !Drive Wheels !GVWR !Restraint System |- |J |LR2 base model - Canada only: '14 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |N |Range Rover Evoque Pure '12 (Canada only), '13-'15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |LR2 '10, LR2 base model - Canada only: '13,<br> LR2 SE - Canada only: '14,<br> LR2 base model '15, Discovery Sport SE '15-'19,<br> Range Rover Evoque Pure Plus '12-'15,<br> Range Rover Evoque SE, SE Premium '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque Landmark Edition 4-d '18-'19 <br> [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |LR2 base model (US only) '11-'14,<br> LR2 HSE (US & Canada) '10-'15, LR2 HSE Plus '10,<br> Discovery Sport HSE '15-'18,<br> Range Rover Evoque Pure Premium '12-'15,<br> Range Rover Evoque HSE '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE '19, Landmark Edition '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque Prestige Premium '12-'14, Prestige '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |LR2 HSE Lux '10-'15, Discovery Sport HSE Lux '15-'18,<br> Range Rover Evoque Dynamic Premium '12-'14,<br> Dynamic '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic '16-'19 [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d '16 [Pos. 6 is 1] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |E |Range Rover Evoque Autobiography '15-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque SE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |K |Discovery Sport base model '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |J |Discovery Sport S '20-25, Range Rover Evoque S '20-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |Discovery Sport SE '20-'23, Range Rover Evoque SE '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |9 |Discovery Sport HSE '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque First Edition '20 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport R-Dynamic S '20-'23,<br> Range Rover Evoque R-Dynamic S '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport R-Dynamic SE '20-'23,<br> Discovery Sport Dynamic SE '24-'25,<br> Range Rover Evoque R-Dynamic SE '21-'23,<br> Range Rover Evoque Dynamic SE '24-'26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport Landmark Edition '26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque R-Dynamic SE '20 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |M |Discovery Sport R-Dynamic HSE '20, Canada only: '21-'23,<br> Discovery Sport Dynamic HSE - Canada only: '24-'25,<br> Range Rover Evoque R-Dynamic HSE '20-'21,<br> Range Rover Evoque Dynamic HSE - Canada only: '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P250 Bronze Collection - <br> Canada only: '22-'23 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P300 HST '22-'23 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque P250 Hoxton Edition '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |1 |Range Rover Evoque P250 Autobiography - Canada only: '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |A |Range Rover Velar base model '18-'19 [Pos. 8 is X] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Range Rover Velar S '18-'20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Velar S '21-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |Range Rover Velar SE - Canada only: '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar R-Dynamic SE '18-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |A |Range Rover Velar R-Dynamic SE '19 (some early prod. w/340-hp engine) [Pos. 7 is F & Pos. 8 is V] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Velar R-Dynamic S '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Velar R-Dynamic S '21-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar Dynamic SE '24-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar R-Dynamic HSE '18-'22, First Edition '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar HST '23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar Dynamic HSE '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar Belgravia Edition '26,<br> Belgravia Edition Satin '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Velar Autobiography '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Velar SVAutobiography Dynamic '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |LR4 base model w/2 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |LR4 base model w/3 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |LR4 HSE w/2 rows of seats - '10, Canada only: '13-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |LR4 HSE w/3 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |LR4 HSE Plus w/2 rows of seats '10 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |LR4 HSE Plus w/3 rows of seats '10 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |LR4 HSE Lux w/3 rows of seats '10-'16,<br> HSE Lux XXV Ltd. Ed. w/3 rows of seats '14 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Sport HSE '10-'13,<br> HSE GT Limited Edition '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Sport HSE Luxury '10-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Range Rover Sport Supercharged '10-'13,<br> Supercharged Limited Edition '13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport Autobiography '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |Discovery SE '17-'20, Range Rover Sport SE '14-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Discovery Landmark Edition '20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P300 S '21-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P360 S - Canada only: '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P300 R-Dynamic S '21-'23 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P360 R-Dynamic S '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P300 Dynamic SE '24-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P360 Dynamic SE '24-'25, Canada only: '26 <br> [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Discovery P360 R-Dynamic HSE '21-'23,<br> P360 Dynamic HSE - Canada only: '24-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Metropolitan Edition '23-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Gemini Edition '26,<br> Discovery P360 Tempest Edition '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '14 <br> [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '15, HSE Limited Edition '15 <br> [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Discovery HSE '17-'20,<br> Range Rover Sport HSE '17-'18 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '19 [Pos. 8 is V or K or U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '20, HSE Silver Edition '21 <br> [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE Silver Edition '22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Discovery HSE Luxury '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery HSE Luxury '18-'20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery First Edition '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST '16 [Pos. 7 is P or V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport HSE Dynamic '17-'19 [Pos. 8 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST Mid '19-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport P400e HSE '20,<br> P400e HSE Silver Edition '21-'22 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P400e Autobiography '20-'21 <br> [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '15,<br> Supercharged Limited Edition '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '16,<br> Supercharged Dynamic '16,<br> Supercharged Dynamic Limited Edition '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '17-'18,<br> Supercharged Dynamic '17-'19,<br> HSE Dynamic '20-'22 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '17, '19-'22,<br> Autobiography Dynamic '18 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport SVR '15-'22, SVR Carbon Edition '21-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Sport P360 S '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport P360 SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Sport P400 Dynamic S - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Sport Dynamic SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P400 Dynamic HSE - <br> Canada only: '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P440e Autobiography '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P440e HSE Dynamic - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P550e Autobiography '24-'26,<br> P530 Autobiography '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P530 First Edition '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition One w/Obsidian Black or Flux Silver paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Edition One w/Carbon Bronze paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition Two '25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Range Rover Sport P635 SV '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Range Rover Sport P635 SV Carbon '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |E |Range Rover HSE '10-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover HSE Luxury '10-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Supercharged '10-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Autobiography '10-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover (L405) base model '13-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '13 [Pos. 7 is D] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '14 [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '15, HSE Limited Edition '15 [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '17-'19 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '20 [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '21 [Pos. 8 is K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE Westminster Edition '21-'22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover P400e HSE '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover P400e Autobiography '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '13 <br> [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '14,<br> Supercharged SWB Ebony Edition '14 <br> [Pos. 6 is 2 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '15,<br> Supercharged SWB Limited Edition '15 <br> [Pos. 6 is 2 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '16 <br> [Pos. 6 is 2 & Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '17-'19,<br> P525 HSE SWB '20,<br> P525 HSE Westminster Edition SWB '21-'22 <br> [Pos. 6 is 2 & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography SWB '13-'22 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition SWB '21 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography Dynamic '17-'22,<br> SVAutobiography Dynamic Black '21-'22 [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE LWB '15 <br> [Pos. 6 is 3 & Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '14 <br> [Pos. 6 is 3 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '15,<br> Supercharged LWB Limited Edition '15 <br> [Pos. 6 is 3 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '16 <br> [Pos. 6 is 3 & Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '17-'19,<br> P525 HSE LWB '20,<br> P525 HSE Westminster Edition LWB '21-'22 <br> [Pos. 6 is 5 & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '14-'15 [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '16 [Pos. 6 is 3] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '17-'22 [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) Autobiography Black LWB '14-'15 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition LWB '21 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '16-'17 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '18-'22 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover (L460) SE '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover (L460) Autobiography '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L460) P530 First Edition '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover (L460) P530 SV '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover (L460) P615 SV '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover (L460) P615 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 90 base model '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/2 rows of seats '20-'23 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/3 rows of seats '20-'23 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 90 S '21-'25, Canada only: '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 130 S w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Defender 90 X-Dynamic S '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 90 P400 SE '23 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/2 rows of seats '20-'23 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P500 SE w/2 rows of seats '24 [Pos. 6 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/3 rows of seats '20-'23 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 130 P400 SE w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 90 P400 X-Dynamic SE '22-'26,<br> Defender 90 X-Dynamic SE Sedona Red '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/2 rows of seats '21-'26 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P500 X-Dynamic SE w/2 rows of seats '25-'26 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/3 rows of seats '21-'26 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 130 P400 X-Dynamic SE w/3 rows of seats '23-'26 <br> [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 90 X-Dynamic HSE '22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/2 rows of seats '21-'22 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/3 rows of seats '21-'22 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/2 rows of seats '22 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/3 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 75th Limited Edition '23 <br> [Pos. 6 is 6 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 75th Limited Edition w/2 rows of seats '23 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Sedona Red Edition w/2 rows of seats '25 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Trophy Edition w/2 rows of seats '26 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P400 Outbound w/2 rows of seats '24-'26 <br> [Pos. 6 is F & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 90 First Edition '21 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 130 First Edition w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 90 X '21-'23, Canada only: '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 130 X w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 90 P525 V8 '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 P525 V8 '22-'23, '25-'26,<br> P525 V8 Carpathian Edition '22-'24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 110 P525 V8 w/2 rows of seats '24 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 P525 V8 w/2 rows of seats '22-'23, '25-'26,<br> P525 V8 Carpathian Edition w/2 rows of seats '22-'24,<br> P525 V8 Bond Edition w/2 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 130 P500 V8 w/3 rows of seats '24 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P500 V8 w/3 rows of seats '25-'26 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Defender 110 P635 OCTA w/2 rows of seats '25-'26,<br> P635 OCTA Edition One w/2 rows of seats '25,<br> P635 OCTA Black w/2 rows of seats '26 <br> [Pos. 6 is E & Pos. 8 is 9] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |} ===Body Type=== {| class="wikitable" |+Position 6 !VIN code !Description |- |1 |4-door wagon (Range Rover '87-'12, Defender 110 '93, Discovery '94-'04) |- |1 |2-door soft top (Freelander SE3) ('03-'05) |- |1 |2-door wagon (Range Rover Evoque 2-d '12-'17) |- |2 |2-door soft top (Defender 90) ('94-'95, '97) |- |2 |4-door wagon (Freelander) ('02-'05) |- |2 |4-door wagon (LR2 '08-'15, Discovery Sport '15-'26, Range Rover Evoque 4-d '12-, LR3 '05-'09, LR4 '10-'16, Discovery '18-, Range Rover Sport '06-'22, Range Rover Sport P400e '20, Range Rover SWB (L405) '13-'22, Range Rover Velar '18-) |- |3 |2-door wagon (Defender 90) ('95, '97) |- |3 |4-door wagon LWB (Range Rover LWB '14-'16) |- |3 |4-door wagon LWB w/Class E GVWR (Range Rover SVAutobiography LWB '17) |- |4 |4-door wagon [[w:Plug-in hybrid|PHEV]] (Range Rover P400e '20-'21, Range Rover Sport P400e '21-Early '22) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover Supercharged LWB & Autobiography LWB '17) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover LWB (L405) '18-'22) |- |5 |2-door convertible (Range Rover Evoque convertible '17-'19) |- |6 |2-door wagon (Defender 90 '21-) |- |7 |4-door wagon w/2 rows of seating (Defender 110 P300/P400 '20-) |- |9 |4-door wagon (Range Rover SWB (L460) '22-, Range Rover Sport '23-) |- |B |4-door wagon (Discovery '17) |- |B |4-door wagon LWB (Range Rover LWB (L460) '22-) |- |E |4-door wagon w/3 rows of seating (Defender 110 P300/P400 w/opt. 3rd row '20-) |- |E |4-door wagon w/2 rows of seating (Defender 110 V8 models '22-) |- |F |4-door wagon w/extended length (Defender 130 '23-) |} SWB=Short-wheelbase, LWB=Long-wheelbase ===Engine Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 7 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | 1 || 3.5L || V8 || Gas ||OHV||MPI. [[w:Rover V8 engine|(Ex-GM) Rover V8 engine]]. Land Rover Range Rover ('87-'88). |- | 1 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Single VANOS (Intake VVT). BMW M62TUB44 engine. Land Rover Range Rover ('03-'05). |- | 2 || 3.9L || V8 || Gas ||OHV||MPI. (Ex-GM) Rover V8 engine.<br> Land Rover Range Rover SWB ('89-'94), Range Rover County Classic [SWB] ('95), Defender 110 ('93),<br> Defender 90 ('94-'95), Discovery ('94-'95). |- | 2 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.0 SE ('95-'99),<br> Discovery ('96-'02), Defender 90 ('97). |- | 2 || 2.5L || 90° V6 || Gas ||DOHC,<br /> 24 valve||Sequential MPI. VIS. [[w:Rover KV6 engine|Rover KV6 engine]]. Land Rover Freelander ('02-'05). |- | 3 || 4.2L || V8 || Gas ||OHV||MPI. (4275 cc, actually 4.3L). (Ex-GM) Rover V8 engine. Land Rover Range Rover County LWB ('93-'95). |- | 3 || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Jaguar AJ33S engine. Land Rover Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 4 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.6 HSE ('96-'99), Discovery ('03). |- | 4 || 4.0L || 60° V6 || Gas ||SOHC,<br /> 12 valve||Sequential MPI. Variable intake manifold. Ford Cologne V6 engine.<br> Land Rover LR3 ('05-'07 & also '08-'09 in Canada). |- | 5 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. LEV.<br> Land Rover Range Rover 4.0 SE ('00), Discovery ('00-'02). |- | 5 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Continuously VCP (Intake VVT). Jaguar AJ41 engine.<br> Land Rover LR3 ('05-'09), Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 6 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. LEV ('00-'02) or ULEV ('03).<br> Land Rover Range Rover 4.6 HSE ('00-'02), 4.6 SE ('01), Discovery ('03). |- | 9 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Discovery ('04). |- | D || 5.0L || V8 || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). CPS (Intake VVL). VIS. Jaguar AJ133 engine (LR-V8).<br> Land Rover LR4 ('10-'13), Range Rover ('10-'13), Range Rover Sport ('10-'13). |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('10-'16), Range Rover Sport ('10-'16). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Range Rover Td6 ('16), Range Rover Sport Td6 ('16). |- | P || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('16), Range Rover Sport ('16). |- | T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 32 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('14-'15), Range Rover Sport ('14-'15). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover LR4 ('14-'16), Range Rover ('14-'16), Range Rover Sport ('14-'16). |- | W || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 24 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('14), Range Rover Sport ('14). |} VVT=Variable Valve Timing. VCP=Variable Camshaft Phasing. VCT=Variable Camshaft Timing. VIS=Variable Intake System. LEV=Low Emissions Vehicle. ULEV=Ultra-Low Emissions Vehicle. CPS=Cam Profile Switching. VVL=Variable Valve Lift. ===Transmission Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |4 |6-speed automatic (Aisin AWF21) (LR2 '08-'09) |- |B |6-speed automatic (Aisin AWF21) (LR2 '10-'15, Range Rover Evoque '12-'13) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '15-'16, Range Rover Evoque '14-'16) |} ===Transmission Type (All models 2017)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |B |8-speed automatic (ZF 8HP) (Discovery '17) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '17, Range Rover Evoque '17) |- |F |8-speed automatic (ZF 8HP) (Range Rover '17, Range Rover Sport '17) |} ===Transmission Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 8 !VIN code !Description |- |2 |5-speed automatic [manual shift mode: Steptronic or CommandShift] (Jatco JF506E) (Freelander '02-'05) |- |4 |4-speed automatic (ZF 4HP22 or w/4.6L V8: 4HP24) (Range Rover '87-'02, Discovery '94-'04, Defender 90 '97) |- |4 |5-speed automatic (ZF 5HP24) (Range Rover '03-'05) |- |4 |6-speed automatic (ZF 6HP26X) (LR3 '05-'09, Range Rover '06-'09, Range Rover Sport '06-'09) |- |4 |6-speed automatic (ZF 6HP28X) (LR4 '10-'13, Range Rover '10-'12, Range Rover Sport '10-'13) |- |6 |8-speed automatic (ZF 8HP) (LR4 '14-'16) |- |8 |5-speed manual (Defender 110 '93, Defender 90 '94-'95, Discovery '94-'97) |- |F |8-speed automatic (ZF 8HP) (Range Rover '13-'16, Range Rover Sport '14-'16) |} All are LHD (Left-hand drive). ===Engine Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover LR2 ('13-'15), Discovery Sport ('15-'16), Range Rover Evoque ('12-'16). |- | N || 3.2L || I6 || Gas ||DOHC,<br /> 24 valve||MPI. VCT (Intake VVT). CPS (Intake VVL). VIS. [[w:Volvo SI6 engine#B6324S5|Volvo SI6 engine - B6324S5]]. Land Rover LR2 ('08-'12). |- |} VCT=Variable Cam Timing. VVT=Variable Valve Timing. CPS=Cam Profile Switching. VVL=Variable Valve Lift. VIS=Variable Intake System. ===Engine Type (All models 2017 only)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('17), Range Rover Sport ('17). |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover Discovery Sport ('17), Range Rover Evoque ('17). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('17), Range Rover Td6 ('17), Range Rover Sport Td6 ('17). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Discovery ('17), Range Rover ('17), Range Rover Sport ('17). |} ==Engine 2018-== ===Engine Variant (All models 2018-)=== {| class="wikitable" |+Position 7 |- ! VIN !! Power Level/Engine !! Transmission !! Model |- |R (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |S (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |F (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19) |- |G (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19), Discovery Sport P290 ('20) |- |F (followed by X) |246 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport P250 ('20-'26), Range Rover Evoque S/SE/1st Edition ('20),<br> Range Rover Evoque P250 ('21-'26) |- |G (followed by X) |296 hp 2.0L Ingenium turbo I4 |9-speed auto. |Range Rover Evoque R-Dynamic S/SE/HSE ('20),<br> Range Rover Evoque P300 HST ('22-'23) |- |R (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P250 ('19-'26) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P300 (Canada only: '19-'20) |- |R (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar D180 ('19) |- |R (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar ('18) |- |F (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P340 ('19-'20) |- |E (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P380 ('19-'20) |- |E (followed by U) |335 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P340 ('21-'23, Canada only: '24-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P400 R-Dynamic HSE ('21-'22), <br> Range Rover Velar P400 HST ('23), <br> Range Rover Velar P400 Dynamic SE/HSE ('24-'25), <br> Range Rover Velar P400 Dynamic SE/Autobiography/Belgravia Ed. ('26) |- |E (followed by E) |550 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Velar SVAutobiography Dynamic ('20) |- |R (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Discovery ('18-'20), Range Rover Sport SE/HSE ('18-'19), Range Rover ('18-'19) |- |R (followed by K) |254 hp 3.0L "Lion" AJD-V6 turbodiesel V6 |8-speed auto. |Discovery Td6 ('18-'20), Range Rover Sport Td6 ('18-'21), Range Rover Td6 ('18-'21) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('21) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('21) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('22-'24) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('25-'26) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('22-'26) |- |S (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Sport HSE Dynamic ('18-'19), Range Rover HSE ('18-'19) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport SE/HSE (Mid '19) |- |S (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport HST (Mid '19) |- |S (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 SE/HSE ('20),<br> Range Rover Sport P360 SE/HSE Silver ('21-'22), Range Rover (L405) P360 ('20-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 HST ('20-'22), Range Rover P400 HSE ('20),<br> Range Rover (L405) P400 HSE Westminster ('21-'22) |- |R (followed by Y) |398 hp 2.0L Ingenium turbo I4 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P400e ('20-'22), Range Rover P400e ('20-'21) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport ('18-'19), Range Rover ('18-'19) |- |S (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('18-'19) |- |S (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover SVAutobiography Dynamic, SVAutobiography LWB ('18-'19) |- |S (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport P525 ('20-'22), Range Rover (L405) P525 ('20-'22) |- |R (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('20-'22) |- |R (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover (L405) SVAutobiography Dynamic, SVAutobiography LWB ('20-'22) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 ('23-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 ('23-'26), <br> Range Rover (L460) P400 SE ('22-'26) |- |E (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P440e ('23) |- |F (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover P440e ('23) |- |E (followed by 4) |454 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P460e ('25-'26) |- |F (followed by 4) |542 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P550e ('24-'26), Range Rover P550e ('24-'26) |- |E (followed by 7) |523 hp 4.4L BMW N63 (JLR NC10)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P530 ('23), <br> Range Rover (L460) P530 ('22-'23) |- |F (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P635 SV Edition One ('24),<br> Range Rover Sport P635 SV Edition Two ('25), Range Rover Sport P635 SV ('26) |- |E (followed by 9) |523 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P530 ('24-'26), Range Rover Sport P530 ('25-'26) |- |F (followed by 9) |606 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P615 SV ('24-'26) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 110 P300 ('20) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 110 P400 ('20) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('21-'22), Defender 110 P300 ('21-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('21-'22), Defender 110 P400 ('21-'22) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('22), Defender 110 P525 ('22) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('23-'25, Canada only: '26), Defender 110 P300 ('23-'26) |- |E (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('23) [Pos. 5 is J] |- |F (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('24-'26) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('23-'26), Defender 110 P400 ('23-'26), Defender 130 P400 ('23-'26) |- |F (followed by E) |493 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 110 P500 ('24-'26), Defender 130 P500 ('24-'26) |- |E (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('23-'26), Defender 110 P525 ('23-'26) |- |E (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Defender 110 P635 OCTA ('25-'26) |} ===Engine Type (All models 2018-)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('18-'22), Range Rover Sport ('18-'22),<br> Range Rover Velar SVAutobiography Dynamic ('20), Defender V8 ('22-'26). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('18-'20), Range Rover Td6 ('18-'21), Range Rover Sport Td6 ('18-'21). |- | N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,<br /> 16 valve||Common-rail Direct Injection. Exhaust VVT. JLR Ingenium AJ20D engine.<br> Land Rover Range Rover Velar ('18-'19) |- | U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine.<br> Land Rover Discovery ('21-), Range Rover ('20-), Range Rover Sport (Mid '19-), Range Rover Velar ('21-), Defender ('20-). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine. Land Rover Discovery ('18-'20),<br> Range Rover ('18-'19), Range Rover Sport ('18-Mid '19), Range Rover Velar ('18-'20). |- | X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine.<br> Land Rover Discovery Sport ('18-'26), Range Rover Evoque ('18-), Range Rover Velar ('18-), Defender ('20-'26), Discovery ('21-). |- | Y || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine + 1 Front motor.<br> 12.4 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P400e ('20-'21), Range Rover Sport P400e ('20-Early '22). |- | 4 || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 24 valve||E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine + 1 Front motor. 31.8 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P440e ('23), P550e ('24-); Range Rover Sport P440e ('23), P460e ('25-), P550e ('24-). |- | 7 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW N63B44T3 [N63TU3] engine [JLR NC10-P8H]. Land Rover Range Rover [L460] ('22-'23), Range Rover Sport ('23). |- | 9 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||48v Mild Hybrid. Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW S68B44TO [S68B44A] engine [JLR NC11-P8S]. Land Rover Range Rover [L460] ('24-), Range Rover Sport ('24-),<br> Defender Octa ('25-). |- |} CVVL=Continuously Variable Valve Lift. ==Check Digit/Gearbox (Position 9)== * USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]] ==Model Year Code (Position 10)== ''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]'' ==Plant Codes (Position 11)== * A - Solihull, West Midlands, England, UK * H - Halewood, Merseyside, England, UK * 2 - Nitra, Slovakia ==External links== * [http://www.clifton.nl/calvin.html CalVIN, the on-line free Land Rover VIN CALculator] * [http://www.fourfold.org/LR_FAQ Land Rover FAQ archive] * [http://www.vindecoderz.com/EN/Land%20Rover Land Rover VIN decoder] {{BookCat}} bidgglp2guapw7126jvfk7n8ddw9vpt 4679924 4679872 2026-11-04T08:10:03Z JustTheFacts33 3434282 /* Model Series/Trim Level/GVWR */ 4679924 wikitext text/x-wiki {{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}} From 1948 to the early eighties, Land Rover used for their cars chassis numbers of their own format. These formats are described in the table below. Since 1980 Land Rover deploys the standard 17-character Vehicle Identification Number ('''VIN'''), complying with international standards. Car details can be derived (decoded, calculated) from the chassis numbers and the VIN. Typically, the model (Defender, Discovery, Range Rover, Freelander), model type (station wagon, three/four door, etc), wheelbase (90 inch, 100 inch, 110 inch, etc.), engine, LHD/RHD, gearbox, and model year is included in the VIN. ===Chassis number formats over the years=== <table> <tr><th>Description</th><th>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</th><th>Format</th></tr> <tr><td>17-characters, International VIN, 1980-later</td><td></td><td>SAL..............</td></tr> <tr><td>17-characters, Int. VIN for LR do Brazil </td><td></td><td>93R..............</td></tr> <tr><td>17-characters, Int. VIN for AAD, 1985-1995 </td><td></td><td>AAD..............</td></tr> <tr><td>17-characters, US/Canada VIN, 1987-later </td><td></td><td>SAL.................</td></tr> <tr><td>17-characters, Brazil VIN for JLR Brazil, 2016-later </td><td></td><td>99J.................</td></tr> <tr></tr> <tr><td>14-characters: is actually the 17-char</td></tr> <tr><td>VIN missing the SAL bit</td></tr> <tr><td> <tr><td>9-character numbers, 1955 </td><td></td><td>17.6.....</td></tr> <tr><td>9-character numbers, 1956 to 1961 </td><td></td><td>1........</td></tr> <tr><td>9-character numbers, 1950 </td><td></td><td>L........ or R........</td></tr> <tr><td>9-character numbers, 1962 to 1979 </td><td></td><td>.........</td></tr> <tr></tr> <tr><td>8-character numbers, 1948 to 1949 </td><td></td><td>.8......</td></tr> <tr><td>8-character numbers, 1950 to 1953 </td><td></td><td>.6......</td></tr> <tr><td>8-character numbers, 1954 to 1955 </td><td></td><td>.7......</td></tr> <tr></tr> <tr><td>7-character numbers, 1948 to 1949 </td><td></td><td>.......</td></tr> <tr><td>6-character numbers, ???? prototypes </td><td></td><td>110F..</td></tr> <tr><td>3-character numbers, 1948 prototypes </td><td></td><td>R.. or L..</td></tr> </table> ===Land Rover WMIs (1981-) (Position 1-3)=== * SAL - Land Rover (UK & Europe) * 99J - JLR Brazil * L2C - Chery Jaguar Land Rover (China) ===Model Line=== {| class="wikitable" |+Position 4 !VIN code !Description |- |A |[[w:Land Rover Discovery#Discovery 3 / LR3 (2004–2009)|Land Rover LR3]] ('05-'09) |- |A |[[w:Land Rover Discovery#Discovery 4 / LR4 (2009–2016)|Land Rover LR4]] ('10-'16) |- |C |[[w:Land Rover Discovery Sport|Land Rover Discovery Sport]] ('15-'26) |- |D |[[w:Land Rover Defender#North American Specification (NAS) Defenders|Land Rover Defender]] ('93-'95, '97) |- |E |[[w:Land Rover Defender (L663)|Land Rover Defender (L663)]] ('20-) |- |F |[[w:Land Rover Freelander#Freelander 2 (L359; 2006–2015)|Land Rover LR2]] ('08-'15) |- |G |[[w:Range Rover (L405)|Land Rover Range Rover (L405)]] (4th gen.) ('13-'22) |- |H |[[w:Range Rover Classic|Land Rover Range Rover/Range Rover Classic]] (1st gen.) ('87-'95) |- |J |[[w:Land Rover Discovery#First & Second generation Discovery|Land Rover Discovery]] ('94-'98 & '99 Discovery SD) |- |K |[[w:Range Rover (L460)|Land Rover Range Rover (L460)]] (5th gen.) (Mid '22-) |- |M |[[w:Range Rover (L322)|Land Rover Range Rover (L322)]] (3rd gen.) ('03-'12) |- |N |[[w:Land Rover Freelander#Freelander in North America|Land Rover Freelander]] ('02-'05) |- |P |[[w:Range Rover (P38A)|Land Rover Range Rover (P38A)]] (2nd gen.) ('95-'02) |- |R |[[w:Land Rover Discovery#Fifth generation Discovery (L462; 2017–present)|Land Rover Discovery]] ('17-) |- |S |[[w:Range Rover Sport#First generation (L320; 2005)|Land Rover Range Rover Sport]] (1st gen.) ('06-'13) |- |T |[[w:Land Rover Discovery#Discovery Series II (L318; 1998–2004)|Land Rover Discovery Series II]] ('99-'04) |- |V |[[w:Range Rover Evoque#First generation (L538; 2011)|Land Rover Range Rover Evoque]] (1st gen.) ('12-'19) |- |W |[[w:Range Rover Sport#Second generation (L494; 2013)|Land Rover Range Rover Sport]] (2nd gen.) ('14-'22) |- |Y |[[w:Range Rover Velar|Land Rover Range Rover Velar]] (1st gen.) ('18-) |- |Z |[[w:Range Rover Evoque#Second generation (L551; 2018)|Land Rover Range Rover Evoque]] (2nd gen.) ('20-) |- |1 |[[w:Range Rover Sport#Third generation (L461; 2022)|Land Rover Range Rover Sport]] (3rd gen.) ('23-) |- |} ===Model Series/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |V (following H) |Range Rover 100" wheelbase (1st gen.) |Class E |- |E (following H) |Range Rover 100" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |C (following H) |Range Rover LWB 108" wheelbase (1st gen.) |Class E |- |F (following H) |Range Rover LWB 108" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |H (following D) |Defender 110 ('93) |Class E |- |V (following D) |Defender 90 ('94-'95, '97) |Class E |- |X (following D) |Defender 90 (CA emissions) ('95) |Class E |- |Y (following J) |Discovery ('94-'98 & '99 Discovery SD) |Class E |- |N (following J) |Discovery (CA emissions) ('95-'96) |Class E |- |Y (following T) |Discovery Series II ('99-'00) |Class E |- |V (following P) |Range Rover (2nd gen.) ('95-'98) |Class E |- |E (following P) |Range Rover (2nd gen.) (CA emissions) ('95-'96) |Class E |- |A (following P) |Range Rover (2nd gen.) (GEMS engine management) (Early '99) |Class E |- |V (following P) |Range Rover (2nd gen.) (Bosch engine management) ('99-'00) |Class E |- |C (following P) |Range Rover 4.6 HSE Callaway Edition (2nd gen.) (Callaway-modified engine) ('99) |Class E |- |} ===Model Series/Trim Level/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |M (following N) |Freelander S ('02-'03) |Class C |- |Y (following N) |Freelander SE ('02-'05), SE3 ('03-'05) |Class C |- |E (following N) |Freelander HSE ('02-'04) |Class C |- |P (following F) |LR2 SE ('08) |Class D |- |S (following F) |LR2 SE w/Technology Pkg. ('08) |Class D |- |R (following F) |LR2 HSE ('08-'09) |Class D |- |T (following F) |LR2 HSE w/Technology Pkg. ('08-'09) |Class D |- |L (following T) |Discovery Series II SD ('01-'02), S ('03-'04) |Class E |- |K (following T) |Discovery Series II SD7 ('01-'02), S7 ('03-'04) |Class E |- |Y (following T) |Discovery Series II SE ('01-'04) |Class E |- |W (following T) |Discovery Series II SE7 ('01-'04) |Class E |- |H (following T) |Discovery Series II LE ('01) |Class E |- |J (following T) |Discovery Series II LE7 ('01) |Class E |- |P (following T) |Discovery Series II HSE ('03-'04) |Class E |- |R (following T) |Discovery Series II HSE7 ('03-'04) |Class E |- |L (following P) |Range Rover (2nd gen.) 4.6 SE ('01) |Class E |- |M (following P) |Range Rover (2nd gen.) 4.6 HSE ('01-'02), Westminster Edition ('02) |Class E |- |H (following M) |Range Rover (3rd gen.) Westminster Edition ('04-'05) |Class E |- |} ===Trim Level/Drive Wheels/GVWR/Restraint System (Position 5) 2010-=== {| class="wikitable" |+Position 5 !VIN code !Trim Level !Drive Wheels !GVWR !Restraint System |- |J |LR2 base model - Canada only: '14 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |N |Range Rover Evoque Pure '12 (Canada only), '13-'15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |LR2 '10, LR2 base model - Canada only: '13,<br> LR2 SE - Canada only: '14,<br> LR2 base model '15, Discovery Sport SE '15-'19,<br> Range Rover Evoque Pure Plus '12-'15,<br> Range Rover Evoque SE, SE Premium '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque Landmark Edition 4-d '18-'19 <br> [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |LR2 base model (US only) '11-'14,<br> LR2 HSE (US & Canada) '10-'15, LR2 HSE Plus '10,<br> Discovery Sport HSE '15-'18,<br> Range Rover Evoque Pure Premium '12-'15,<br> Range Rover Evoque HSE '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE '19, Landmark Edition '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque Prestige Premium '12-'14, Prestige '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |LR2 HSE Lux '10-'15, Discovery Sport HSE Lux '15-'18,<br> Range Rover Evoque Dynamic Premium '12-'14,<br> Dynamic '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic '16-'19 [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d '16 [Pos. 6 is 1] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |E |Range Rover Evoque Autobiography '15-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque SE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |K |Discovery Sport base model '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |J |Discovery Sport S '20-25, Range Rover Evoque S '20-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |Discovery Sport SE '20-'23, Range Rover Evoque SE '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |9 |Discovery Sport HSE '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque First Edition '20 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport R-Dynamic S '20-'23,<br> Range Rover Evoque R-Dynamic S '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport R-Dynamic SE '20-'23,<br> Discovery Sport Dynamic SE '24-'25,<br> Range Rover Evoque R-Dynamic SE '21-'23,<br> Range Rover Evoque Dynamic SE '24-'26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport Landmark Edition '26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque R-Dynamic SE '20 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |M |Discovery Sport R-Dynamic HSE '20, Canada only: '21-'23,<br> Discovery Sport Dynamic HSE - Canada only: '24-'25,<br> Range Rover Evoque R-Dynamic HSE '20-'21,<br> Range Rover Evoque Dynamic HSE - Canada only: '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P250 Bronze Collection - <br> Canada only: '22-'23 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P300 HST '22-'23 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque P250 Hoxton Edition '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |1 |Range Rover Evoque P250 Autobiography - Canada only: '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |A |Range Rover Velar base model '18-'19 [Pos. 8 is X] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Range Rover Velar S '18-'20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Velar S '21-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |Range Rover Velar SE - Canada only: '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar R-Dynamic SE '18-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |A |Range Rover Velar R-Dynamic SE '19 (some early prod. w/340-hp engine) [Pos. 7 is F & Pos. 8 is V] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Velar R-Dynamic S '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Velar R-Dynamic S '21-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar Dynamic SE '24-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar R-Dynamic HSE '18-'22, First Edition '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar HST '23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar Dynamic HSE '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar Belgravia Edition '26,<br> Belgravia Edition Satin '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Velar Autobiography '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Velar SVAutobiography Dynamic '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |LR4 base model w/2 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |LR4 base model w/3 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |LR4 HSE w/2 rows of seats - '10, Canada only: '13-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |LR4 HSE w/3 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |LR4 HSE Plus w/2 rows of seats '10 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |LR4 HSE Plus w/3 rows of seats '10 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |LR4 HSE Lux w/3 rows of seats '10-'16,<br> HSE Lux XXV Ltd. Ed. w/3 rows of seats '14 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Sport HSE '10-'13,<br> HSE GT Limited Edition '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Sport HSE Luxury '10-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Range Rover Sport Supercharged '10-'13,<br> Supercharged Limited Edition '13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport Autobiography '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |Discovery SE '17-'20, Range Rover Sport SE '14-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Discovery Landmark Edition '20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P300 S '21-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P360 S - Canada only: '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P300 R-Dynamic S '21-'23 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P360 R-Dynamic S '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P300 Dynamic SE '24-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P360 Dynamic SE '24-'25, Canada only: '26 <br> [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Discovery P360 R-Dynamic HSE '21-'23,<br> P360 Dynamic HSE - Canada only: '24-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Metropolitan Edition '23-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Gemini Edition '26,<br> Discovery P360 Tempest Edition '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '14 <br> [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '15, HSE Limited Edition '15 <br> [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Discovery HSE '17-'20,<br> Range Rover Sport HSE '17-'18 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '19 [Pos. 8 is V or K or U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '20, HSE Silver Edition '21 <br> [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE Silver Edition '22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Discovery HSE Luxury '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery HSE Luxury '18-'20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery First Edition '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST '16 [Pos. 7 is P or V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport HSE Dynamic '17-'19 [Pos. 8 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST Mid '19-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport P400e HSE '20,<br> P400e HSE Silver Edition '21-'22 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P400e Autobiography '20-'21 <br> [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '15,<br> Supercharged Limited Edition '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '16,<br> Supercharged Dynamic '16,<br> Supercharged Dynamic Limited Edition '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '17-'18,<br> Supercharged Dynamic '17-'19,<br> HSE Dynamic '20-'22 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '17, '19-'22,<br> Autobiography Dynamic '18 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport SVR '15-'22, SVR Carbon Edition '21-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Sport P360 S '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport P360 SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Sport P400 Dynamic S - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Sport Dynamic SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P400 Dynamic HSE - <br> Canada only: '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P440e Autobiography '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P440e HSE Dynamic - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P550e Autobiography '24-'26,<br> P530 Autobiography '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P530 First Edition '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition One w/Obsidian Black or Flux Silver paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Edition One w/Carbon Bronze paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition Two '25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Range Rover Sport P635 SV '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Range Rover Sport P635 SV Carbon '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |E |Range Rover HSE '10-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover HSE Luxury '10-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Supercharged '10-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Autobiography '10-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover (L405) base model '13-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '13 [Pos. 7 is D] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '14 [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '15, HSE Limited Edition '15 [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '17-'19 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '20 [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '21 [Pos. 8 is K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE Westminster Edition '21-'22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover P400e HSE '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover P400e Autobiography '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '13 <br> [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '14,<br> Supercharged SWB Ebony Edition '14 <br> [Pos. 6 is 2 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '15,<br> Supercharged SWB Limited Edition '15 <br> [Pos. 6 is 2 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '16 <br> [Pos. 6 is 2 & Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '17-'19,<br> P525 HSE SWB '20,<br> P525 HSE Westminster Edition SWB '21-'22 <br> [Pos. 6 is 2 & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography SWB '13-'22 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition SWB '21 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography Dynamic '17-'22,<br> SVAutobiography Dynamic Black '21-'22 [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE LWB '15 <br> [Pos. 6 is 3 & Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '14 <br> [Pos. 6 is 3 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '15,<br> Supercharged LWB Limited Edition '15 <br> [Pos. 6 is 3 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '16 <br> [Pos. 6 is 3 & Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '17-'19,<br> P525 HSE LWB '20,<br> P525 HSE Westminster Edition LWB '21-'22 <br> [Pos. 6 is 5 & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '14-'15 [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '16 [Pos. 6 is 3] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '17-'22 [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) Autobiography Black LWB '14-'15 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition LWB '21 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '16-'17 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '18-'22 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover (L460) SE '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover (L460) Autobiography '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L460) P530 First Edition '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover (L460) P530 SV '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover (L460) P615 SV '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover (L460) P615 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 90 base model '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/2 rows of seats '20-'23 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/3 rows of seats '20-'23 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 90 S '21-'25, Canada only: '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 130 S w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Defender 90 X-Dynamic S '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 90 P400 SE '23 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/2 rows of seats '20-'23 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P500 SE w/2 rows of seats '24 [Pos. 6 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/3 rows of seats '20-'23 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 130 P400 SE w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 90 P400 X-Dynamic SE '22-'26,<br> Defender 90 X-Dynamic SE Sedona Red '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/2 rows of seats '21-'26 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P500 X-Dynamic SE w/2 rows of seats '25-'26 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/3 rows of seats '21-'26 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 130 P400 X-Dynamic SE w/3 rows of seats '23-'26 <br> [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 90 X-Dynamic HSE '22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/2 rows of seats '21-'22 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/3 rows of seats '21-'22 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/2 rows of seats '22 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/3 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 75th Limited Edition '23 <br> [Pos. 6 is 6 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 75th Limited Edition w/2 rows of seats '23 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Sedona Red Edition w/2 rows of seats '25 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Trophy Edition w/2 rows of seats '26 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P400 Outbound w/2 rows of seats '24-'26 <br> [Pos. 6 is F & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 90 First Edition '21 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 130 First Edition w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 90 X '21-'23, Canada only: '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 130 X w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 90 P525 V8 '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 P525 V8 '22-'23, '25-'26,<br> P525 V8 Carpathian Edition '22-'24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 110 P525 V8 w/2 rows of seats '24 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 P525 V8 w/2 rows of seats '22-'23, '25-'26,<br> P525 V8 Carpathian Edition w/2 rows of seats '22-'24,<br> P525 V8 Bond Edition w/2 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 130 P500 V8 w/3 rows of seats '24 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P500 V8 w/3 rows of seats '25-'26 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Defender 110 P635 OCTA w/2 rows of seats '25-'26,<br> P635 OCTA Edition One w/2 rows of seats '25,<br> P635 OCTA Black w/2 rows of seats '26 <br> [Pos. 6 is E & Pos. 8 is 9] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |} ===Body Type=== {| class="wikitable" |+Position 6 !VIN code !Description |- |1 |4-door wagon (Range Rover '87-'12, Defender 110 '93, Discovery '94-'04) |- |1 |2-door soft top (Freelander SE3) ('03-'05) |- |1 |2-door wagon (Range Rover Evoque 2-d '12-'17) |- |2 |2-door soft top (Defender 90) ('94-'95, '97) |- |2 |4-door wagon (Freelander) ('02-'05) |- |2 |4-door wagon (LR2 '08-'15, Discovery Sport '15-'26, Range Rover Evoque 4-d '12-, LR3 '05-'09, LR4 '10-'16, Discovery '18-, Range Rover Sport '06-'22, Range Rover Sport P400e '20, Range Rover SWB (L405) '13-'22, Range Rover Velar '18-) |- |3 |2-door wagon (Defender 90) ('95, '97) |- |3 |4-door wagon LWB (Range Rover LWB '14-'16) |- |3 |4-door wagon LWB w/Class E GVWR (Range Rover SVAutobiography LWB '17) |- |4 |4-door wagon [[w:Plug-in hybrid|PHEV]] (Range Rover P400e '20-'21, Range Rover Sport P400e '21-Early '22) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover Supercharged LWB & Autobiography LWB '17) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover LWB (L405) '18-'22) |- |5 |2-door convertible (Range Rover Evoque convertible '17-'19) |- |6 |2-door wagon (Defender 90 '21-) |- |7 |4-door wagon w/2 rows of seating (Defender 110 P300/P400 '20-) |- |9 |4-door wagon (Range Rover SWB (L460) '22-, Range Rover Sport '23-) |- |B |4-door wagon (Discovery '17) |- |B |4-door wagon LWB (Range Rover LWB (L460) '22-) |- |E |4-door wagon w/3 rows of seating (Defender 110 P300/P400 w/opt. 3rd row '20-) |- |E |4-door wagon w/2 rows of seating (Defender 110 V8 models '22-) |- |F |4-door wagon w/extended length (Defender 130 '23-) |} SWB=Short-wheelbase, LWB=Long-wheelbase ===Engine Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 7 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | 1 || 3.5L || V8 || Gas ||OHV||MPI. [[w:Rover V8 engine|(Ex-GM) Rover V8 engine]]. Land Rover Range Rover ('87-'88). |- | 1 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Single VANOS (Intake VVT). BMW M62TUB44 engine. Land Rover Range Rover ('03-'05). |- | 2 || 3.9L || V8 || Gas ||OHV||MPI. (Ex-GM) Rover V8 engine.<br> Land Rover Range Rover SWB ('89-'94), Range Rover County Classic [SWB] ('95), Defender 110 ('93),<br> Defender 90 ('94-'95), Discovery ('94-'95). |- | 2 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.0 SE ('95-'99),<br> Discovery ('96-'02), Defender 90 ('97). |- | 2 || 2.5L || 90° V6 || Gas ||DOHC,<br /> 24 valve||Sequential MPI. VIS. [[w:Rover KV6 engine|Rover KV6 engine]]. Land Rover Freelander ('02-'05). |- | 3 || 4.2L || V8 || Gas ||OHV||MPI. (4275 cc, actually 4.3L). (Ex-GM) Rover V8 engine. Land Rover Range Rover County LWB ('93-'95). |- | 3 || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Jaguar AJ33S engine. Land Rover Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 4 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.6 HSE ('96-'99), Discovery ('03). |- | 4 || 4.0L || 60° V6 || Gas ||SOHC,<br /> 12 valve||Sequential MPI. Variable intake manifold. Ford Cologne V6 engine.<br> Land Rover LR3 ('05-'07 & also '08-'09 in Canada). |- | 5 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. LEV.<br> Land Rover Range Rover 4.0 SE ('00), Discovery ('00-'02). |- | 5 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Continuously VCP (Intake VVT). Jaguar AJ41 engine.<br> Land Rover LR3 ('05-'09), Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 6 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. LEV ('00-'02) or ULEV ('03).<br> Land Rover Range Rover 4.6 HSE ('00-'02), 4.6 SE ('01), Discovery ('03). |- | 9 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Discovery ('04). |- | D || 5.0L || V8 || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). CPS (Intake VVL). VIS. Jaguar AJ133 engine (LR-V8).<br> Land Rover LR4 ('10-'13), Range Rover ('10-'13), Range Rover Sport ('10-'13). |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('10-'16), Range Rover Sport ('10-'16). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Range Rover Td6 ('16), Range Rover Sport Td6 ('16). |- | P || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('16), Range Rover Sport ('16). |- | T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 32 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('14-'15), Range Rover Sport ('14-'15). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover LR4 ('14-'16), Range Rover ('14-'16), Range Rover Sport ('14-'16). |- | W || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 24 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('14), Range Rover Sport ('14). |} VVT=Variable Valve Timing. VCP=Variable Camshaft Phasing. VCT=Variable Camshaft Timing. VIS=Variable Intake System. LEV=Low Emissions Vehicle. ULEV=Ultra-Low Emissions Vehicle. CPS=Cam Profile Switching. VVL=Variable Valve Lift. ===Transmission Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |4 |6-speed automatic (Aisin AWF21) (LR2 '08-'09) |- |B |6-speed automatic (Aisin AWF21) (LR2 '10-'15, Range Rover Evoque '12-'13) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '15-'16, Range Rover Evoque '14-'16) |} ===Transmission Type (All models 2017)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |B |8-speed automatic (ZF 8HP) (Discovery '17) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '17, Range Rover Evoque '17) |- |F |8-speed automatic (ZF 8HP) (Range Rover '17, Range Rover Sport '17) |} ===Transmission Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 8 !VIN code !Description |- |2 |5-speed automatic [manual shift mode: Steptronic or CommandShift] (Jatco JF506E) (Freelander '02-'05) |- |4 |4-speed automatic (ZF 4HP22 or w/4.6L V8: 4HP24) (Range Rover '87-'02, Discovery '94-'04, Defender 90 '97) |- |4 |5-speed automatic (ZF 5HP24) (Range Rover '03-'05) |- |4 |6-speed automatic (ZF 6HP26X) (LR3 '05-'09, Range Rover '06-'09, Range Rover Sport '06-'09) |- |4 |6-speed automatic (ZF 6HP28X) (LR4 '10-'13, Range Rover '10-'12, Range Rover Sport '10-'13) |- |6 |8-speed automatic (ZF 8HP) (LR4 '14-'16) |- |8 |5-speed manual (Defender 110 '93, Defender 90 '94-'95, Discovery '94-'97) |- |F |8-speed automatic (ZF 8HP) (Range Rover '13-'16, Range Rover Sport '14-'16) |} All are LHD (Left-hand drive). ===Engine Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover LR2 ('13-'15), Discovery Sport ('15-'16), Range Rover Evoque ('12-'16). |- | N || 3.2L || I6 || Gas ||DOHC,<br /> 24 valve||MPI. VCT (Intake VVT). CPS (Intake VVL). VIS. [[w:Volvo SI6 engine#B6324S5|Volvo SI6 engine - B6324S5]]. Land Rover LR2 ('08-'12). |- |} VCT=Variable Cam Timing. VVT=Variable Valve Timing. CPS=Cam Profile Switching. VVL=Variable Valve Lift. VIS=Variable Intake System. ===Engine Type (All models 2017 only)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('17), Range Rover Sport ('17). |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover Discovery Sport ('17), Range Rover Evoque ('17). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('17), Range Rover Td6 ('17), Range Rover Sport Td6 ('17). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Discovery ('17), Range Rover ('17), Range Rover Sport ('17). |} ==Engine 2018-== ===Engine Variant (All models 2018-)=== {| class="wikitable" |+Position 7 |- ! VIN !! Power Level/Engine !! Transmission !! Model |- |R (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |S (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |F (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19) |- |G (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19), Discovery Sport P290 ('20) |- |F (followed by X) |246 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport P250 ('20-'26), Range Rover Evoque S/SE/1st Edition ('20),<br> Range Rover Evoque P250 ('21-'26) |- |G (followed by X) |296 hp 2.0L Ingenium turbo I4 |9-speed auto. |Range Rover Evoque R-Dynamic S/SE/HSE ('20),<br> Range Rover Evoque P300 HST ('22-'23) |- |R (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P250 ('19-'26) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P300 (Canada only: '19-'20) |- |R (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar D180 ('19) |- |R (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar ('18) |- |F (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P340 ('19-'20) |- |E (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P380 ('19-'20) |- |E (followed by U) |335 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P340 ('21-'23, Canada only: '24-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P400 R-Dynamic HSE ('21-'22), <br> Range Rover Velar P400 HST ('23), <br> Range Rover Velar P400 Dynamic SE/HSE ('24-'25), <br> Range Rover Velar P400 Dynamic SE/Autobiography/Belgravia Ed. ('26) |- |E (followed by E) |550 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Velar SVAutobiography Dynamic ('20) |- |R (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Discovery ('18-'20), Range Rover Sport SE/HSE ('18-'19), Range Rover ('18-'19) |- |R (followed by K) |254 hp 3.0L "Lion" AJD-V6 turbodiesel V6 |8-speed auto. |Discovery Td6 ('18-'20), Range Rover Sport Td6 ('18-'21), Range Rover Td6 ('18-'21) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('21) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('21) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('22-'24) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('25-'26) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('22-'26) |- |S (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Sport HSE Dynamic ('18-'19), Range Rover HSE ('18-'19) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport SE/HSE (Mid '19) |- |S (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport HST (Mid '19) |- |S (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 SE/HSE ('20),<br> Range Rover Sport P360 SE/HSE Silver ('21-'22), Range Rover (L405) P360 ('20-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 HST ('20-'22), Range Rover P400 HSE ('20),<br> Range Rover (L405) P400 HSE Westminster ('21-'22) |- |R (followed by Y) |398 hp 2.0L Ingenium turbo I4 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P400e ('20-'22), Range Rover P400e ('20-'21) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport ('18-'19), Range Rover ('18-'19) |- |S (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('18-'19) |- |S (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover SVAutobiography Dynamic, SVAutobiography LWB ('18-'19) |- |S (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport P525 ('20-'22), Range Rover (L405) P525 ('20-'22) |- |R (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('20-'22) |- |R (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover (L405) SVAutobiography Dynamic, SVAutobiography LWB ('20-'22) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 ('23-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 ('23-'26), <br> Range Rover (L460) P400 SE ('22-'26) |- |E (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P440e ('23) |- |F (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover P440e ('23) |- |E (followed by 4) |454 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P460e ('25-'26) |- |F (followed by 4) |542 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P550e ('24-'26), Range Rover P550e ('24-'26) |- |E (followed by 7) |523 hp 4.4L BMW N63 (JLR NC10)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P530 ('23), <br> Range Rover (L460) P530 ('22-'23) |- |F (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P635 SV Edition One ('24),<br> Range Rover Sport P635 SV Edition Two ('25), Range Rover Sport P635 SV ('26) |- |E (followed by 9) |523 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P530 ('24-'26), Range Rover Sport P530 ('25-'26) |- |F (followed by 9) |606 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P615 SV ('24-'26) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 110 P300 ('20) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 110 P400 ('20) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('21-'22), Defender 110 P300 ('21-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('21-'22), Defender 110 P400 ('21-'22) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('22), Defender 110 P525 ('22) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('23-'25, Canada only: '26), Defender 110 P300 ('23-'26) |- |E (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('23) [Pos. 5 is J] |- |F (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('24-'26) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('23-'26), Defender 110 P400 ('23-'26), Defender 130 P400 ('23-'26) |- |F (followed by E) |493 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 110 P500 ('24-'26), Defender 130 P500 ('24-'26) |- |E (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('23-'26), Defender 110 P525 ('23-'26) |- |E (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Defender 110 P635 OCTA ('25-'26) |} ===Engine Type (All models 2018-)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('18-'22), Range Rover Sport ('18-'22),<br> Range Rover Velar SVAutobiography Dynamic ('20), Defender V8 ('22-'26). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('18-'20), Range Rover Td6 ('18-'21), Range Rover Sport Td6 ('18-'21). |- | N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,<br /> 16 valve||Common-rail Direct Injection. Exhaust VVT. JLR Ingenium AJ20D engine.<br> Land Rover Range Rover Velar ('18-'19) |- | U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine.<br> Land Rover Discovery ('21-), Range Rover ('20-), Range Rover Sport (Mid '19-), Range Rover Velar ('21-), Defender ('20-). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine. Land Rover Discovery ('18-'20),<br> Range Rover ('18-'19), Range Rover Sport ('18-Mid '19), Range Rover Velar ('18-'20). |- | X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine.<br> Land Rover Discovery Sport ('18-'26), Range Rover Evoque ('18-), Range Rover Velar ('18-), Defender ('20-'26), Discovery ('21-). |- | Y || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine + 1 Front motor.<br> 12.4 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P400e ('20-'21), Range Rover Sport P400e ('20-Early '22). |- | 4 || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 24 valve||E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine + 1 Front motor. 31.8 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P440e ('23), P550e ('24-); Range Rover Sport P440e ('23), P460e ('25-), P550e ('24-). |- | 7 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW N63B44T3 [N63TU3] engine [JLR NC10-P8H]. Land Rover Range Rover [L460] ('22-'23), Range Rover Sport ('23). |- | 9 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||48v Mild Hybrid. Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW S68B44TO [S68B44A] engine [JLR NC11-P8S]. Land Rover Range Rover [L460] ('24-), Range Rover Sport ('24-),<br> Defender Octa ('25-). |- |} CVVL=Continuously Variable Valve Lift. ==Check Digit/Gearbox (Position 9)== * USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]] ==Model Year Code (Position 10)== ''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]'' ==Plant Codes (Position 11)== * A - Solihull, West Midlands, England, UK * H - Halewood, Merseyside, England, UK * 2 - Nitra, Slovakia ==External links== * [http://www.clifton.nl/calvin.html CalVIN, the on-line free Land Rover VIN CALculator] * [http://www.fourfold.org/LR_FAQ Land Rover FAQ archive] * [http://www.vindecoderz.com/EN/Land%20Rover Land Rover VIN decoder] {{BookCat}} 44hlrj3fmuiq3pr37d4wu11ryogtgo4 4679933 4679924 2026-11-04T09:17:48Z JustTheFacts33 3434282 /* Model Series/Trim Level/GVWR */ 4679933 wikitext text/x-wiki {{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}} From 1948 to the early eighties, Land Rover used for their cars chassis numbers of their own format. These formats are described in the table below. Since 1980 Land Rover deploys the standard 17-character Vehicle Identification Number ('''VIN'''), complying with international standards. Car details can be derived (decoded, calculated) from the chassis numbers and the VIN. Typically, the model (Defender, Discovery, Range Rover, Freelander), model type (station wagon, three/four door, etc), wheelbase (90 inch, 100 inch, 110 inch, etc.), engine, LHD/RHD, gearbox, and model year is included in the VIN. ===Chassis number formats over the years=== <table> <tr><th>Description</th><th>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</th><th>Format</th></tr> <tr><td>17-characters, International VIN, 1980-later</td><td></td><td>SAL..............</td></tr> <tr><td>17-characters, Int. VIN for LR do Brazil </td><td></td><td>93R..............</td></tr> <tr><td>17-characters, Int. VIN for AAD, 1985-1995 </td><td></td><td>AAD..............</td></tr> <tr><td>17-characters, US/Canada VIN, 1987-later </td><td></td><td>SAL.................</td></tr> <tr><td>17-characters, Brazil VIN for JLR Brazil, 2016-later </td><td></td><td>99J.................</td></tr> <tr></tr> <tr><td>14-characters: is actually the 17-char</td></tr> <tr><td>VIN missing the SAL bit</td></tr> <tr><td> <tr><td>9-character numbers, 1955 </td><td></td><td>17.6.....</td></tr> <tr><td>9-character numbers, 1956 to 1961 </td><td></td><td>1........</td></tr> <tr><td>9-character numbers, 1950 </td><td></td><td>L........ or R........</td></tr> <tr><td>9-character numbers, 1962 to 1979 </td><td></td><td>.........</td></tr> <tr></tr> <tr><td>8-character numbers, 1948 to 1949 </td><td></td><td>.8......</td></tr> <tr><td>8-character numbers, 1950 to 1953 </td><td></td><td>.6......</td></tr> <tr><td>8-character numbers, 1954 to 1955 </td><td></td><td>.7......</td></tr> <tr></tr> <tr><td>7-character numbers, 1948 to 1949 </td><td></td><td>.......</td></tr> <tr><td>6-character numbers, ???? prototypes </td><td></td><td>110F..</td></tr> <tr><td>3-character numbers, 1948 prototypes </td><td></td><td>R.. or L..</td></tr> </table> ===Land Rover WMIs (1981-) (Position 1-3)=== * SAL - Land Rover (UK & Europe) * 99J - JLR Brazil * L2C - Chery Jaguar Land Rover (China) ===Model Line=== {| class="wikitable" |+Position 4 !VIN code !Description |- |A |[[w:Land Rover Discovery#Discovery 3 / LR3 (2004–2009)|Land Rover LR3]] ('05-'09) |- |A |[[w:Land Rover Discovery#Discovery 4 / LR4 (2009–2016)|Land Rover LR4]] ('10-'16) |- |C |[[w:Land Rover Discovery Sport|Land Rover Discovery Sport]] ('15-'26) |- |D |[[w:Land Rover Defender#North American Specification (NAS) Defenders|Land Rover Defender]] ('93-'95, '97) |- |E |[[w:Land Rover Defender (L663)|Land Rover Defender (L663)]] ('20-) |- |F |[[w:Land Rover Freelander#Freelander 2 (L359; 2006–2015)|Land Rover LR2]] ('08-'15) |- |G |[[w:Range Rover (L405)|Land Rover Range Rover (L405)]] (4th gen.) ('13-'22) |- |H |[[w:Range Rover Classic|Land Rover Range Rover/Range Rover Classic]] (1st gen.) ('87-'95) |- |J |[[w:Land Rover Discovery#First & Second generation Discovery|Land Rover Discovery]] ('94-'98 & '99 Discovery SD) |- |K |[[w:Range Rover (L460)|Land Rover Range Rover (L460)]] (5th gen.) (Mid '22-) |- |M |[[w:Range Rover (L322)|Land Rover Range Rover (L322)]] (3rd gen.) ('03-'12) |- |N |[[w:Land Rover Freelander#Freelander in North America|Land Rover Freelander]] ('02-'05) |- |P |[[w:Range Rover (P38A)|Land Rover Range Rover (P38A)]] (2nd gen.) ('95-'02) |- |R |[[w:Land Rover Discovery#Fifth generation Discovery (L462; 2017–present)|Land Rover Discovery]] ('17-) |- |S |[[w:Range Rover Sport#First generation (L320; 2005)|Land Rover Range Rover Sport]] (1st gen.) ('06-'13) |- |T |[[w:Land Rover Discovery#Discovery Series II (L318; 1998–2004)|Land Rover Discovery Series II]] ('99-'04) |- |V |[[w:Range Rover Evoque#First generation (L538; 2011)|Land Rover Range Rover Evoque]] (1st gen.) ('12-'19) |- |W |[[w:Range Rover Sport#Second generation (L494; 2013)|Land Rover Range Rover Sport]] (2nd gen.) ('14-'22) |- |Y |[[w:Range Rover Velar|Land Rover Range Rover Velar]] (1st gen.) ('18-) |- |Z |[[w:Range Rover Evoque#Second generation (L551; 2018)|Land Rover Range Rover Evoque]] (2nd gen.) ('20-) |- |1 |[[w:Range Rover Sport#Third generation (L461; 2022)|Land Rover Range Rover Sport]] (3rd gen.) ('23-) |- |} ===Model Series/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |V (following H) |Range Rover 100" wheelbase (1st gen.) |Class E |- |E (following H) |Range Rover 100" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |C (following H) |Range Rover LWB 108" wheelbase (1st gen.) |Class E |- |F (following H) |Range Rover LWB 108" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |H (following D) |Defender 110 ('93) |Class E |- |V (following D) |Defender 90 ('94-'95, '97) |Class E |- |X (following D) |Defender 90 (CA emissions) ('95) |Class E |- |Y (following J) |Discovery ('94-'98 & '99 Discovery SD) |Class E |- |N (following J) |Discovery (CA emissions) ('95-'96) |Class E |- |Y (following T) |Discovery Series II ('99-'00) |Class E |- |V (following P) |Range Rover (2nd gen.) ('95-'98) |Class E |- |E (following P) |Range Rover (2nd gen.) (CA emissions) ('95-'96) |Class E |- |A (following P) |Range Rover (2nd gen.) (GEMS engine management) (Early '99) |Class E |- |V (following P) |Range Rover (2nd gen.) (Bosch engine management) ('99-'00) |Class E |- |C (following P) |Range Rover 4.6 HSE Callaway Edition (2nd gen.) (Callaway-modified engine) ('99) |Class E |- |} ===Model Series/Trim Level/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |M (following N) |Freelander S ('02-'03) |Class C |- |Y (following N) |Freelander SE ('02-'05), SE3 ('03-'05) |Class C |- |E (following N) |Freelander HSE ('02-'04) |Class C |- |P (following F) |LR2 SE ('08) |Class D |- |S (following F) |LR2 SE w/Technology Pkg. ('08) |Class D |- |R (following F) |LR2 HSE ('08-'09) |Class D |- |T (following F) |LR2 HSE w/Technology Pkg. ('08-'09) |Class D |- |L (following T) |Discovery Series II SD ('01-'02), S ('03-'04) |Class E |- |K (following T) |Discovery Series II SD7 ('01-'02), S7 ('03-'04) |Class E |- |Y (following T) |Discovery Series II SE ('01-'04) |Class E |- |W (following T) |Discovery Series II SE7 ('01-'04) |Class E |- |H (following T) |Discovery Series II LE ('01) |Class E |- |J (following T) |Discovery Series II LE7 ('01) |Class E |- |P (following T) |Discovery Series II HSE ('03-'04) |Class E |- |R (following T) |Discovery Series II HSE7 ('03-'04) |Class E |- |B (following A) |LR3 base model w/2 rows of seats ('09) |Class F |- |C (following A) |LR3 base model w/3 rows of seats ('09) |Class F |- |D (following A) |LR3 SE w/2 rows of seats (Canada only: '08-'09) |Class F |- |E (following A) |LR3 SE w/3 rows of seats ('08, Canada only: '09) |Class F |- |F (following A) |LR3 HSE w/2 rows of seats ('08 - Canada only, '09) |Class F |- |G (following A) |LR3 HSE w/3 rows of seats ('08-'09) |- |H (following A) |LR3 HSE Lux w/2 rows of seats ('09) |Class F |- |K (following A) |LR3 HSE Lux w/3 rows of seats ('09) |Class F |- |L (following P) |Range Rover (2nd gen.) 4.6 SE ('01) |Class E |- |M (following P) |Range Rover (2nd gen.) 4.6 HSE ('01-'02), Westminster Edition ('02) |Class E |- |H (following M) |Range Rover (3rd gen.) Westminster Edition ('04-'05) |Class E |- |} ===Trim Level/Drive Wheels/GVWR/Restraint System (Position 5) 2010-=== {| class="wikitable" |+Position 5 !VIN code !Trim Level !Drive Wheels !GVWR !Restraint System |- |J |LR2 base model - Canada only: '14 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |N |Range Rover Evoque Pure '12 (Canada only), '13-'15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |LR2 '10, LR2 base model - Canada only: '13,<br> LR2 SE - Canada only: '14,<br> LR2 base model '15, Discovery Sport SE '15-'19,<br> Range Rover Evoque Pure Plus '12-'15,<br> Range Rover Evoque SE, SE Premium '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque Landmark Edition 4-d '18-'19 <br> [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |LR2 base model (US only) '11-'14,<br> LR2 HSE (US & Canada) '10-'15, LR2 HSE Plus '10,<br> Discovery Sport HSE '15-'18,<br> Range Rover Evoque Pure Premium '12-'15,<br> Range Rover Evoque HSE '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE '19, Landmark Edition '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque Prestige Premium '12-'14, Prestige '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |LR2 HSE Lux '10-'15, Discovery Sport HSE Lux '15-'18,<br> Range Rover Evoque Dynamic Premium '12-'14,<br> Dynamic '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic '16-'19 [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d '16 [Pos. 6 is 1] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |E |Range Rover Evoque Autobiography '15-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque SE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |K |Discovery Sport base model '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |J |Discovery Sport S '20-25, Range Rover Evoque S '20-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |Discovery Sport SE '20-'23, Range Rover Evoque SE '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |9 |Discovery Sport HSE '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque First Edition '20 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport R-Dynamic S '20-'23,<br> Range Rover Evoque R-Dynamic S '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport R-Dynamic SE '20-'23,<br> Discovery Sport Dynamic SE '24-'25,<br> Range Rover Evoque R-Dynamic SE '21-'23,<br> Range Rover Evoque Dynamic SE '24-'26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport Landmark Edition '26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque R-Dynamic SE '20 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |M |Discovery Sport R-Dynamic HSE '20, Canada only: '21-'23,<br> Discovery Sport Dynamic HSE - Canada only: '24-'25,<br> Range Rover Evoque R-Dynamic HSE '20-'21,<br> Range Rover Evoque Dynamic HSE - Canada only: '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P250 Bronze Collection - <br> Canada only: '22-'23 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P300 HST '22-'23 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque P250 Hoxton Edition '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |1 |Range Rover Evoque P250 Autobiography - Canada only: '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |A |Range Rover Velar base model '18-'19 [Pos. 8 is X] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Range Rover Velar S '18-'20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Velar S '21-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |Range Rover Velar SE - Canada only: '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar R-Dynamic SE '18-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |A |Range Rover Velar R-Dynamic SE '19 (some early prod. w/340-hp engine) [Pos. 7 is F & Pos. 8 is V] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Velar R-Dynamic S '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Velar R-Dynamic S '21-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar Dynamic SE '24-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar R-Dynamic HSE '18-'22, First Edition '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar HST '23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar Dynamic HSE '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar Belgravia Edition '26,<br> Belgravia Edition Satin '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Velar Autobiography '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Velar SVAutobiography Dynamic '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |LR4 base model w/2 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |LR4 base model w/3 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |LR4 HSE w/2 rows of seats - '10, Canada only: '13-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |LR4 HSE w/3 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |LR4 HSE Plus w/2 rows of seats '10 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |LR4 HSE Plus w/3 rows of seats '10 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |LR4 HSE Lux w/3 rows of seats '10-'16,<br> HSE Lux XXV Ltd. Ed. w/3 rows of seats '14 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Sport HSE '10-'13,<br> HSE GT Limited Edition '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Sport HSE Luxury '10-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Range Rover Sport Supercharged '10-'13,<br> Supercharged Limited Edition '13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport Autobiography '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |Discovery SE '17-'20, Range Rover Sport SE '14-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Discovery Landmark Edition '20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P300 S '21-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P360 S - Canada only: '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P300 R-Dynamic S '21-'23 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P360 R-Dynamic S '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P300 Dynamic SE '24-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P360 Dynamic SE '24-'25, Canada only: '26 <br> [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Discovery P360 R-Dynamic HSE '21-'23,<br> P360 Dynamic HSE - Canada only: '24-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Metropolitan Edition '23-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Gemini Edition '26,<br> Discovery P360 Tempest Edition '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '14 <br> [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '15, HSE Limited Edition '15 <br> [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Discovery HSE '17-'20,<br> Range Rover Sport HSE '17-'18 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '19 [Pos. 8 is V or K or U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '20, HSE Silver Edition '21 <br> [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE Silver Edition '22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Discovery HSE Luxury '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery HSE Luxury '18-'20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery First Edition '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST '16 [Pos. 7 is P or V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport HSE Dynamic '17-'19 [Pos. 8 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST Mid '19-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport P400e HSE '20,<br> P400e HSE Silver Edition '21-'22 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P400e Autobiography '20-'21 <br> [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '15,<br> Supercharged Limited Edition '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '16,<br> Supercharged Dynamic '16,<br> Supercharged Dynamic Limited Edition '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '17-'18,<br> Supercharged Dynamic '17-'19,<br> HSE Dynamic '20-'22 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '17, '19-'22,<br> Autobiography Dynamic '18 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport SVR '15-'22, SVR Carbon Edition '21-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Sport P360 S '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport P360 SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Sport P400 Dynamic S - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Sport Dynamic SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P400 Dynamic HSE - <br> Canada only: '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P440e Autobiography '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P440e HSE Dynamic - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P550e Autobiography '24-'26,<br> P530 Autobiography '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P530 First Edition '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition One w/Obsidian Black or Flux Silver paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Edition One w/Carbon Bronze paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition Two '25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Range Rover Sport P635 SV '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Range Rover Sport P635 SV Carbon '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |E |Range Rover HSE '10-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover HSE Luxury '10-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Supercharged '10-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Autobiography '10-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover (L405) base model '13-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '13 [Pos. 7 is D] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '14 [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '15, HSE Limited Edition '15 [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '17-'19 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '20 [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '21 [Pos. 8 is K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE Westminster Edition '21-'22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover P400e HSE '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover P400e Autobiography '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '13 <br> [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '14,<br> Supercharged SWB Ebony Edition '14 <br> [Pos. 6 is 2 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '15,<br> Supercharged SWB Limited Edition '15 <br> [Pos. 6 is 2 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '16 <br> [Pos. 6 is 2 & Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '17-'19,<br> P525 HSE SWB '20,<br> P525 HSE Westminster Edition SWB '21-'22 <br> [Pos. 6 is 2 & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography SWB '13-'22 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition SWB '21 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography Dynamic '17-'22,<br> SVAutobiography Dynamic Black '21-'22 [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE LWB '15 <br> [Pos. 6 is 3 & Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '14 <br> [Pos. 6 is 3 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '15,<br> Supercharged LWB Limited Edition '15 <br> [Pos. 6 is 3 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '16 <br> [Pos. 6 is 3 & Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '17-'19,<br> P525 HSE LWB '20,<br> P525 HSE Westminster Edition LWB '21-'22 <br> [Pos. 6 is 5 & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '14-'15 [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '16 [Pos. 6 is 3] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '17-'22 [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) Autobiography Black LWB '14-'15 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition LWB '21 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '16-'17 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '18-'22 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover (L460) SE '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover (L460) Autobiography '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L460) P530 First Edition '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover (L460) P530 SV '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover (L460) P615 SV '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover (L460) P615 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 90 base model '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/2 rows of seats '20-'23 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/3 rows of seats '20-'23 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 90 S '21-'25, Canada only: '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 130 S w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Defender 90 X-Dynamic S '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 90 P400 SE '23 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/2 rows of seats '20-'23 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P500 SE w/2 rows of seats '24 [Pos. 6 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/3 rows of seats '20-'23 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 130 P400 SE w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 90 P400 X-Dynamic SE '22-'26,<br> Defender 90 X-Dynamic SE Sedona Red '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/2 rows of seats '21-'26 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P500 X-Dynamic SE w/2 rows of seats '25-'26 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/3 rows of seats '21-'26 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 130 P400 X-Dynamic SE w/3 rows of seats '23-'26 <br> [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 90 X-Dynamic HSE '22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/2 rows of seats '21-'22 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/3 rows of seats '21-'22 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/2 rows of seats '22 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/3 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 75th Limited Edition '23 <br> [Pos. 6 is 6 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 75th Limited Edition w/2 rows of seats '23 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Sedona Red Edition w/2 rows of seats '25 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Trophy Edition w/2 rows of seats '26 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P400 Outbound w/2 rows of seats '24-'26 <br> [Pos. 6 is F & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 90 First Edition '21 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 130 First Edition w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 90 X '21-'23, Canada only: '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 130 X w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 90 P525 V8 '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 P525 V8 '22-'23, '25-'26,<br> P525 V8 Carpathian Edition '22-'24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 110 P525 V8 w/2 rows of seats '24 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 P525 V8 w/2 rows of seats '22-'23, '25-'26,<br> P525 V8 Carpathian Edition w/2 rows of seats '22-'24,<br> P525 V8 Bond Edition w/2 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 130 P500 V8 w/3 rows of seats '24 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P500 V8 w/3 rows of seats '25-'26 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Defender 110 P635 OCTA w/2 rows of seats '25-'26,<br> P635 OCTA Edition One w/2 rows of seats '25,<br> P635 OCTA Black w/2 rows of seats '26 <br> [Pos. 6 is E & Pos. 8 is 9] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |} ===Body Type=== {| class="wikitable" |+Position 6 !VIN code !Description |- |1 |4-door wagon (Range Rover '87-'12, Defender 110 '93, Discovery '94-'04) |- |1 |2-door soft top (Freelander SE3) ('03-'05) |- |1 |2-door wagon (Range Rover Evoque 2-d '12-'17) |- |2 |2-door soft top (Defender 90) ('94-'95, '97) |- |2 |4-door wagon (Freelander) ('02-'05) |- |2 |4-door wagon (LR2 '08-'15, Discovery Sport '15-'26, Range Rover Evoque 4-d '12-, LR3 '05-'09, LR4 '10-'16, Discovery '18-, Range Rover Sport '06-'22, Range Rover Sport P400e '20, Range Rover SWB (L405) '13-'22, Range Rover Velar '18-) |- |3 |2-door wagon (Defender 90) ('95, '97) |- |3 |4-door wagon LWB (Range Rover LWB '14-'16) |- |3 |4-door wagon LWB w/Class E GVWR (Range Rover SVAutobiography LWB '17) |- |4 |4-door wagon [[w:Plug-in hybrid|PHEV]] (Range Rover P400e '20-'21, Range Rover Sport P400e '21-Early '22) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover Supercharged LWB & Autobiography LWB '17) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover LWB (L405) '18-'22) |- |5 |2-door convertible (Range Rover Evoque convertible '17-'19) |- |6 |2-door wagon (Defender 90 '21-) |- |7 |4-door wagon w/2 rows of seating (Defender 110 P300/P400 '20-) |- |9 |4-door wagon (Range Rover SWB (L460) '22-, Range Rover Sport '23-) |- |B |4-door wagon (Discovery '17) |- |B |4-door wagon LWB (Range Rover LWB (L460) '22-) |- |E |4-door wagon w/3 rows of seating (Defender 110 P300/P400 w/opt. 3rd row '20-) |- |E |4-door wagon w/2 rows of seating (Defender 110 V8 models '22-) |- |F |4-door wagon w/extended length (Defender 130 '23-) |} SWB=Short-wheelbase, LWB=Long-wheelbase ===Engine Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 7 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | 1 || 3.5L || V8 || Gas ||OHV||MPI. [[w:Rover V8 engine|(Ex-GM) Rover V8 engine]]. Land Rover Range Rover ('87-'88). |- | 1 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Single VANOS (Intake VVT). BMW M62TUB44 engine. Land Rover Range Rover ('03-'05). |- | 2 || 3.9L || V8 || Gas ||OHV||MPI. (Ex-GM) Rover V8 engine.<br> Land Rover Range Rover SWB ('89-'94), Range Rover County Classic [SWB] ('95), Defender 110 ('93),<br> Defender 90 ('94-'95), Discovery ('94-'95). |- | 2 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.0 SE ('95-'99),<br> Discovery ('96-'02), Defender 90 ('97). |- | 2 || 2.5L || 90° V6 || Gas ||DOHC,<br /> 24 valve||Sequential MPI. VIS. [[w:Rover KV6 engine|Rover KV6 engine]]. Land Rover Freelander ('02-'05). |- | 3 || 4.2L || V8 || Gas ||OHV||MPI. (4275 cc, actually 4.3L). (Ex-GM) Rover V8 engine. Land Rover Range Rover County LWB ('93-'95). |- | 3 || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Jaguar AJ33S engine. Land Rover Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 4 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.6 HSE ('96-'99), Discovery ('03). |- | 4 || 4.0L || 60° V6 || Gas ||SOHC,<br /> 12 valve||Sequential MPI. Variable intake manifold. Ford Cologne V6 engine.<br> Land Rover LR3 ('05-'07 & also '08-'09 in Canada). |- | 5 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. LEV.<br> Land Rover Range Rover 4.0 SE ('00), Discovery ('00-'02). |- | 5 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Continuously VCP (Intake VVT). Jaguar AJ41 engine.<br> Land Rover LR3 ('05-'09), Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 6 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. LEV ('00-'02) or ULEV ('03).<br> Land Rover Range Rover 4.6 HSE ('00-'02), 4.6 SE ('01), Discovery ('03). |- | 9 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Discovery ('04). |- | D || 5.0L || V8 || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). CPS (Intake VVL). VIS. Jaguar AJ133 engine (LR-V8).<br> Land Rover LR4 ('10-'13), Range Rover ('10-'13), Range Rover Sport ('10-'13). |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('10-'16), Range Rover Sport ('10-'16). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Range Rover Td6 ('16), Range Rover Sport Td6 ('16). |- | P || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('16), Range Rover Sport ('16). |- | T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 32 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('14-'15), Range Rover Sport ('14-'15). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover LR4 ('14-'16), Range Rover ('14-'16), Range Rover Sport ('14-'16). |- | W || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 24 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('14), Range Rover Sport ('14). |} VVT=Variable Valve Timing. VCP=Variable Camshaft Phasing. VCT=Variable Camshaft Timing. VIS=Variable Intake System. LEV=Low Emissions Vehicle. ULEV=Ultra-Low Emissions Vehicle. CPS=Cam Profile Switching. VVL=Variable Valve Lift. ===Transmission Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |4 |6-speed automatic (Aisin AWF21) (LR2 '08-'09) |- |B |6-speed automatic (Aisin AWF21) (LR2 '10-'15, Range Rover Evoque '12-'13) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '15-'16, Range Rover Evoque '14-'16) |} ===Transmission Type (All models 2017)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |B |8-speed automatic (ZF 8HP) (Discovery '17) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '17, Range Rover Evoque '17) |- |F |8-speed automatic (ZF 8HP) (Range Rover '17, Range Rover Sport '17) |} ===Transmission Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 8 !VIN code !Description |- |2 |5-speed automatic [manual shift mode: Steptronic or CommandShift] (Jatco JF506E) (Freelander '02-'05) |- |4 |4-speed automatic (ZF 4HP22 or w/4.6L V8: 4HP24) (Range Rover '87-'02, Discovery '94-'04, Defender 90 '97) |- |4 |5-speed automatic (ZF 5HP24) (Range Rover '03-'05) |- |4 |6-speed automatic (ZF 6HP26X) (LR3 '05-'09, Range Rover '06-'09, Range Rover Sport '06-'09) |- |4 |6-speed automatic (ZF 6HP28X) (LR4 '10-'13, Range Rover '10-'12, Range Rover Sport '10-'13) |- |6 |8-speed automatic (ZF 8HP) (LR4 '14-'16) |- |8 |5-speed manual (Defender 110 '93, Defender 90 '94-'95, Discovery '94-'97) |- |F |8-speed automatic (ZF 8HP) (Range Rover '13-'16, Range Rover Sport '14-'16) |} All are LHD (Left-hand drive). ===Engine Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover LR2 ('13-'15), Discovery Sport ('15-'16), Range Rover Evoque ('12-'16). |- | N || 3.2L || I6 || Gas ||DOHC,<br /> 24 valve||MPI. VCT (Intake VVT). CPS (Intake VVL). VIS. [[w:Volvo SI6 engine#B6324S5|Volvo SI6 engine - B6324S5]]. Land Rover LR2 ('08-'12). |- |} VCT=Variable Cam Timing. VVT=Variable Valve Timing. CPS=Cam Profile Switching. VVL=Variable Valve Lift. VIS=Variable Intake System. ===Engine Type (All models 2017 only)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('17), Range Rover Sport ('17). |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover Discovery Sport ('17), Range Rover Evoque ('17). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('17), Range Rover Td6 ('17), Range Rover Sport Td6 ('17). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Discovery ('17), Range Rover ('17), Range Rover Sport ('17). |} ==Engine 2018-== ===Engine Variant (All models 2018-)=== {| class="wikitable" |+Position 7 |- ! VIN !! Power Level/Engine !! Transmission !! Model |- |R (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |S (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |F (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19) |- |G (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19), Discovery Sport P290 ('20) |- |F (followed by X) |246 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport P250 ('20-'26), Range Rover Evoque S/SE/1st Edition ('20),<br> Range Rover Evoque P250 ('21-'26) |- |G (followed by X) |296 hp 2.0L Ingenium turbo I4 |9-speed auto. |Range Rover Evoque R-Dynamic S/SE/HSE ('20),<br> Range Rover Evoque P300 HST ('22-'23) |- |R (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P250 ('19-'26) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P300 (Canada only: '19-'20) |- |R (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar D180 ('19) |- |R (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar ('18) |- |F (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P340 ('19-'20) |- |E (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P380 ('19-'20) |- |E (followed by U) |335 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P340 ('21-'23, Canada only: '24-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P400 R-Dynamic HSE ('21-'22), <br> Range Rover Velar P400 HST ('23), <br> Range Rover Velar P400 Dynamic SE/HSE ('24-'25), <br> Range Rover Velar P400 Dynamic SE/Autobiography/Belgravia Ed. ('26) |- |E (followed by E) |550 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Velar SVAutobiography Dynamic ('20) |- |R (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Discovery ('18-'20), Range Rover Sport SE/HSE ('18-'19), Range Rover ('18-'19) |- |R (followed by K) |254 hp 3.0L "Lion" AJD-V6 turbodiesel V6 |8-speed auto. |Discovery Td6 ('18-'20), Range Rover Sport Td6 ('18-'21), Range Rover Td6 ('18-'21) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('21) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('21) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('22-'24) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('25-'26) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('22-'26) |- |S (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Sport HSE Dynamic ('18-'19), Range Rover HSE ('18-'19) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport SE/HSE (Mid '19) |- |S (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport HST (Mid '19) |- |S (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 SE/HSE ('20),<br> Range Rover Sport P360 SE/HSE Silver ('21-'22), Range Rover (L405) P360 ('20-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 HST ('20-'22), Range Rover P400 HSE ('20),<br> Range Rover (L405) P400 HSE Westminster ('21-'22) |- |R (followed by Y) |398 hp 2.0L Ingenium turbo I4 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P400e ('20-'22), Range Rover P400e ('20-'21) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport ('18-'19), Range Rover ('18-'19) |- |S (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('18-'19) |- |S (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover SVAutobiography Dynamic, SVAutobiography LWB ('18-'19) |- |S (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport P525 ('20-'22), Range Rover (L405) P525 ('20-'22) |- |R (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('20-'22) |- |R (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover (L405) SVAutobiography Dynamic, SVAutobiography LWB ('20-'22) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 ('23-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 ('23-'26), <br> Range Rover (L460) P400 SE ('22-'26) |- |E (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P440e ('23) |- |F (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover P440e ('23) |- |E (followed by 4) |454 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P460e ('25-'26) |- |F (followed by 4) |542 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P550e ('24-'26), Range Rover P550e ('24-'26) |- |E (followed by 7) |523 hp 4.4L BMW N63 (JLR NC10)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P530 ('23), <br> Range Rover (L460) P530 ('22-'23) |- |F (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P635 SV Edition One ('24),<br> Range Rover Sport P635 SV Edition Two ('25), Range Rover Sport P635 SV ('26) |- |E (followed by 9) |523 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P530 ('24-'26), Range Rover Sport P530 ('25-'26) |- |F (followed by 9) |606 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P615 SV ('24-'26) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 110 P300 ('20) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 110 P400 ('20) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('21-'22), Defender 110 P300 ('21-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('21-'22), Defender 110 P400 ('21-'22) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('22), Defender 110 P525 ('22) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('23-'25, Canada only: '26), Defender 110 P300 ('23-'26) |- |E (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('23) [Pos. 5 is J] |- |F (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('24-'26) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('23-'26), Defender 110 P400 ('23-'26), Defender 130 P400 ('23-'26) |- |F (followed by E) |493 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 110 P500 ('24-'26), Defender 130 P500 ('24-'26) |- |E (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('23-'26), Defender 110 P525 ('23-'26) |- |E (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Defender 110 P635 OCTA ('25-'26) |} ===Engine Type (All models 2018-)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('18-'22), Range Rover Sport ('18-'22),<br> Range Rover Velar SVAutobiography Dynamic ('20), Defender V8 ('22-'26). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('18-'20), Range Rover Td6 ('18-'21), Range Rover Sport Td6 ('18-'21). |- | N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,<br /> 16 valve||Common-rail Direct Injection. Exhaust VVT. JLR Ingenium AJ20D engine.<br> Land Rover Range Rover Velar ('18-'19) |- | U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine.<br> Land Rover Discovery ('21-), Range Rover ('20-), Range Rover Sport (Mid '19-), Range Rover Velar ('21-), Defender ('20-). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine. Land Rover Discovery ('18-'20),<br> Range Rover ('18-'19), Range Rover Sport ('18-Mid '19), Range Rover Velar ('18-'20). |- | X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine.<br> Land Rover Discovery Sport ('18-'26), Range Rover Evoque ('18-), Range Rover Velar ('18-), Defender ('20-'26), Discovery ('21-). |- | Y || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine + 1 Front motor.<br> 12.4 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P400e ('20-'21), Range Rover Sport P400e ('20-Early '22). |- | 4 || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 24 valve||E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine + 1 Front motor. 31.8 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P440e ('23), P550e ('24-); Range Rover Sport P440e ('23), P460e ('25-), P550e ('24-). |- | 7 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW N63B44T3 [N63TU3] engine [JLR NC10-P8H]. Land Rover Range Rover [L460] ('22-'23), Range Rover Sport ('23). |- | 9 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||48v Mild Hybrid. Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW S68B44TO [S68B44A] engine [JLR NC11-P8S]. Land Rover Range Rover [L460] ('24-), Range Rover Sport ('24-),<br> Defender Octa ('25-). |- |} CVVL=Continuously Variable Valve Lift. ==Check Digit/Gearbox (Position 9)== * USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]] ==Model Year Code (Position 10)== ''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]'' ==Plant Codes (Position 11)== * A - Solihull, West Midlands, England, UK * H - Halewood, Merseyside, England, UK * 2 - Nitra, Slovakia ==External links== * [http://www.clifton.nl/calvin.html CalVIN, the on-line free Land Rover VIN CALculator] * [http://www.fourfold.org/LR_FAQ Land Rover FAQ archive] * [http://www.vindecoderz.com/EN/Land%20Rover Land Rover VIN decoder] {{BookCat}} sqbu5az6forgszd1hnz21y9viwqnkhj 4679934 4679933 2026-11-04T09:58:28Z JustTheFacts33 3434282 /* Model Series/Trim Level/GVWR */ 4679934 wikitext text/x-wiki {{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}} From 1948 to the early eighties, Land Rover used for their cars chassis numbers of their own format. These formats are described in the table below. Since 1980 Land Rover deploys the standard 17-character Vehicle Identification Number ('''VIN'''), complying with international standards. Car details can be derived (decoded, calculated) from the chassis numbers and the VIN. Typically, the model (Defender, Discovery, Range Rover, Freelander), model type (station wagon, three/four door, etc), wheelbase (90 inch, 100 inch, 110 inch, etc.), engine, LHD/RHD, gearbox, and model year is included in the VIN. ===Chassis number formats over the years=== <table> <tr><th>Description</th><th>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</th><th>Format</th></tr> <tr><td>17-characters, International VIN, 1980-later</td><td></td><td>SAL..............</td></tr> <tr><td>17-characters, Int. VIN for LR do Brazil </td><td></td><td>93R..............</td></tr> <tr><td>17-characters, Int. VIN for AAD, 1985-1995 </td><td></td><td>AAD..............</td></tr> <tr><td>17-characters, US/Canada VIN, 1987-later </td><td></td><td>SAL.................</td></tr> <tr><td>17-characters, Brazil VIN for JLR Brazil, 2016-later </td><td></td><td>99J.................</td></tr> <tr></tr> <tr><td>14-characters: is actually the 17-char</td></tr> <tr><td>VIN missing the SAL bit</td></tr> <tr><td> <tr><td>9-character numbers, 1955 </td><td></td><td>17.6.....</td></tr> <tr><td>9-character numbers, 1956 to 1961 </td><td></td><td>1........</td></tr> <tr><td>9-character numbers, 1950 </td><td></td><td>L........ or R........</td></tr> <tr><td>9-character numbers, 1962 to 1979 </td><td></td><td>.........</td></tr> <tr></tr> <tr><td>8-character numbers, 1948 to 1949 </td><td></td><td>.8......</td></tr> <tr><td>8-character numbers, 1950 to 1953 </td><td></td><td>.6......</td></tr> <tr><td>8-character numbers, 1954 to 1955 </td><td></td><td>.7......</td></tr> <tr></tr> <tr><td>7-character numbers, 1948 to 1949 </td><td></td><td>.......</td></tr> <tr><td>6-character numbers, ???? prototypes </td><td></td><td>110F..</td></tr> <tr><td>3-character numbers, 1948 prototypes </td><td></td><td>R.. or L..</td></tr> </table> ===Land Rover WMIs (1981-) (Position 1-3)=== * SAL - Land Rover (UK & Europe) * 99J - JLR Brazil * L2C - Chery Jaguar Land Rover (China) ===Model Line=== {| class="wikitable" |+Position 4 !VIN code !Description |- |A |[[w:Land Rover Discovery#Discovery 3 / LR3 (2004–2009)|Land Rover LR3]] ('05-'09) |- |A |[[w:Land Rover Discovery#Discovery 4 / LR4 (2009–2016)|Land Rover LR4]] ('10-'16) |- |C |[[w:Land Rover Discovery Sport|Land Rover Discovery Sport]] ('15-'26) |- |D |[[w:Land Rover Defender#North American Specification (NAS) Defenders|Land Rover Defender]] ('93-'95, '97) |- |E |[[w:Land Rover Defender (L663)|Land Rover Defender (L663)]] ('20-) |- |F |[[w:Land Rover Freelander#Freelander 2 (L359; 2006–2015)|Land Rover LR2]] ('08-'15) |- |G |[[w:Range Rover (L405)|Land Rover Range Rover (L405)]] (4th gen.) ('13-'22) |- |H |[[w:Range Rover Classic|Land Rover Range Rover/Range Rover Classic]] (1st gen.) ('87-'95) |- |J |[[w:Land Rover Discovery#First & Second generation Discovery|Land Rover Discovery]] ('94-'98 & '99 Discovery SD) |- |K |[[w:Range Rover (L460)|Land Rover Range Rover (L460)]] (5th gen.) (Mid '22-) |- |M |[[w:Range Rover (L322)|Land Rover Range Rover (L322)]] (3rd gen.) ('03-'12) |- |N |[[w:Land Rover Freelander#Freelander in North America|Land Rover Freelander]] ('02-'05) |- |P |[[w:Range Rover (P38A)|Land Rover Range Rover (P38A)]] (2nd gen.) ('95-'02) |- |R |[[w:Land Rover Discovery#Fifth generation Discovery (L462; 2017–present)|Land Rover Discovery]] ('17-) |- |S |[[w:Range Rover Sport#First generation (L320; 2005)|Land Rover Range Rover Sport]] (1st gen.) ('06-'13) |- |T |[[w:Land Rover Discovery#Discovery Series II (L318; 1998–2004)|Land Rover Discovery Series II]] ('99-'04) |- |V |[[w:Range Rover Evoque#First generation (L538; 2011)|Land Rover Range Rover Evoque]] (1st gen.) ('12-'19) |- |W |[[w:Range Rover Sport#Second generation (L494; 2013)|Land Rover Range Rover Sport]] (2nd gen.) ('14-'22) |- |Y |[[w:Range Rover Velar|Land Rover Range Rover Velar]] (1st gen.) ('18-) |- |Z |[[w:Range Rover Evoque#Second generation (L551; 2018)|Land Rover Range Rover Evoque]] (2nd gen.) ('20-) |- |1 |[[w:Range Rover Sport#Third generation (L461; 2022)|Land Rover Range Rover Sport]] (3rd gen.) ('23-) |- |} ===Model Series/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |V (following H) |Range Rover 100" wheelbase (1st gen.) |Class E |- |E (following H) |Range Rover 100" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |C (following H) |Range Rover LWB 108" wheelbase (1st gen.) |Class E |- |F (following H) |Range Rover LWB 108" wheelbase (CA emissions) (1st gen.) ('95) |Class E |- |H (following D) |Defender 110 ('93) |Class E |- |V (following D) |Defender 90 ('94-'95, '97) |Class E |- |X (following D) |Defender 90 (CA emissions) ('95) |Class E |- |Y (following J) |Discovery ('94-'98 & '99 Discovery SD) |Class E |- |N (following J) |Discovery (CA emissions) ('95-'96) |Class E |- |Y (following T) |Discovery Series II ('99-'00) |Class E |- |V (following P) |Range Rover (2nd gen.) ('95-'98) |Class E |- |E (following P) |Range Rover (2nd gen.) (CA emissions) ('95-'96) |Class E |- |A (following P) |Range Rover (2nd gen.) (GEMS engine management) (Early '99) |Class E |- |V (following P) |Range Rover (2nd gen.) (Bosch engine management) ('99-'00) |Class E |- |C (following P) |Range Rover 4.6 HSE Callaway Edition (2nd gen.) (Callaway-modified engine) ('99) |Class E |- |} ===Model Series/Trim Level/GVWR=== {| class="wikitable" |+Position 5 !VIN code !Series !GVWR |- |M (following N) |Freelander S ('02-'03) |Class C |- |Y (following N) |Freelander SE ('02-'05), SE3 ('03-'05) |Class C |- |E (following N) |Freelander HSE ('02-'04) |Class C |- |P (following F) |LR2 SE ('08) |Class D |- |S (following F) |LR2 SE w/Technology Pkg. ('08) |Class D |- |R (following F) |LR2 HSE ('08-'09) |Class D |- |T (following F) |LR2 HSE w/Technology Pkg. ('08-'09) |Class D |- |L (following T) |Discovery Series II SD ('01-'02), S ('03-'04) |Class E |- |K (following T) |Discovery Series II SD7 ('01-'02), S7 ('03-'04) |Class E |- |Y (following T) |Discovery Series II SE ('01-'04) |Class E |- |W (following T) |Discovery Series II SE7 ('01-'04) |Class E |- |H (following T) |Discovery Series II LE ('01) |Class E |- |J (following T) |Discovery Series II LE7 ('01) |Class E |- |P (following T) |Discovery Series II HSE ('03-'04) |Class E |- |R (following T) |Discovery Series II HSE7 ('03-'04) |Class E |- |B (following A) |LR3 base model w/2 rows of seats ('09) |Class F |- |C (following A) |LR3 base model w/3 rows of seats ('09) |Class F |- |D (following A) |LR3 SE w/2 rows of seats (Canada only: '08-'09) |Class F |- |E (following A) |LR3 SE w/3 rows of seats ('08, Canada only: '09) |Class F |- |F (following A) |LR3 HSE w/2 rows of seats ('08 - Canada only, '09) |Class F |- |G (following A) |LR3 HSE w/3 rows of seats ('08-'09) |- |H (following A) |LR3 HSE Lux w/2 rows of seats ('09) |Class F |- |K (following A) |LR3 HSE Lux w/3 rows of seats ('09) |Class F |- |F (following S) |Range Rover Sport HSE ('08-'09) |Class E |- |K (following S) |Range Rover Sport HSE w/Luxury Interior Pkg. ('08), HSE w/Luxury Pkg. ('09) |Class E |- |H (following S) |Range Rover Sport Supercharged ('08-'09), Supercharged Ltd. Ed. ('08) |Class E |- |L (following P) |Range Rover (2nd gen.) 4.6 SE ('01) |Class E |- |M (following P) |Range Rover (2nd gen.) 4.6 HSE ('01-'02), Westminster Edition ('02) |Class E |- |H (following M) |Range Rover (3rd gen.) Westminster Edition ('04-'05) |Class E |- |} ===Trim Level/Drive Wheels/GVWR/Restraint System (Position 5) 2010-=== {| class="wikitable" |+Position 5 !VIN code !Trim Level !Drive Wheels !GVWR !Restraint System |- |J |LR2 base model - Canada only: '14 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |N |Range Rover Evoque Pure '12 (Canada only), '13-'15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |LR2 '10, LR2 base model - Canada only: '13,<br> LR2 SE - Canada only: '14,<br> LR2 base model '15, Discovery Sport SE '15-'19,<br> Range Rover Evoque Pure Plus '12-'15,<br> Range Rover Evoque SE, SE Premium '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque Landmark Edition 4-d '18-'19 <br> [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |LR2 base model (US only) '11-'14,<br> LR2 HSE (US & Canada) '10-'15, LR2 HSE Plus '10,<br> Discovery Sport HSE '15-'18,<br> Range Rover Evoque Pure Premium '12-'15,<br> Range Rover Evoque HSE '16-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE '19, Landmark Edition '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |R |Discovery Sport HSE Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque Prestige Premium '12-'14, Prestige '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |LR2 HSE Lux '10-'15, Discovery Sport HSE Lux '15-'18,<br> Range Rover Evoque Dynamic Premium '12-'14,<br> Dynamic '15 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury '19 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport HSE Luxury Dynamic '19 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic '16-'19 [Pos. 6 is 2] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d '16 [Pos. 6 is 1] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |E |Range Rover Evoque Autobiography '15-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |C |Range Rover Evoque SE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |D |Range Rover Evoque HSE Dynamic 2-d convertible '17-'19 <br> [Pos. 6 is 5] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Head/Thorax Airbags & Driver's Knee Airbag |- |K |Discovery Sport base model '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |J |Discovery Sport S '20-25, Range Rover Evoque S '20-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |P |Discovery Sport SE '20-'23, Range Rover Evoque SE '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |9 |Discovery Sport HSE '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque First Edition '20 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |T |Discovery Sport R-Dynamic S '20-'23,<br> Range Rover Evoque R-Dynamic S '20-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport R-Dynamic SE '20-'23,<br> Discovery Sport Dynamic SE '24-'25,<br> Range Rover Evoque R-Dynamic SE '21-'23,<br> Range Rover Evoque Dynamic SE '24-'26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Discovery Sport Landmark Edition '26 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |L |Range Rover Evoque R-Dynamic SE '20 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |M |Discovery Sport R-Dynamic HSE '20, Canada only: '21-'23,<br> Discovery Sport Dynamic HSE - Canada only: '24-'25,<br> Range Rover Evoque R-Dynamic HSE '20-'21,<br> Range Rover Evoque Dynamic HSE - Canada only: '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P250 Bronze Collection - <br> Canada only: '22-'23 [Pos. 7 is F] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |W |Range Rover Evoque P300 HST '22-'23 [Pos. 7 is G] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |V |Range Rover Evoque P250 Hoxton Edition '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |1 |Range Rover Evoque P250 Autobiography - Canada only: '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags & Driver's Knee Airbag |- |A |Range Rover Velar base model '18-'19 [Pos. 8 is X] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Range Rover Velar S '18-'20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Velar S '21-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |Range Rover Velar SE - Canada only: '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar R-Dynamic SE '18-'19 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |A |Range Rover Velar R-Dynamic SE '19 (some early prod. w/340-hp engine) [Pos. 7 is F & Pos. 8 is V] |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Velar R-Dynamic S '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Velar R-Dynamic S '21-'23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Velar Dynamic SE '24-'26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar R-Dynamic HSE '18-'22, First Edition '18 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar HST '23 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Velar Dynamic HSE '24-'25 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Velar Belgravia Edition '26,<br> Belgravia Edition Satin '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Velar Autobiography '26 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Velar SVAutobiography Dynamic '20 |Awd |Class D (5,001-6,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |LR4 base model w/2 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |C |LR4 base model w/3 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |LR4 HSE w/2 rows of seats - '10, Canada only: '13-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |LR4 HSE w/3 rows of seats '10-'16 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |LR4 HSE Plus w/2 rows of seats '10 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |LR4 HSE Plus w/3 rows of seats '10 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |LR4 HSE Lux w/3 rows of seats '10-'16,<br> HSE Lux XXV Ltd. Ed. w/3 rows of seats '14 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Sport HSE '10-'13,<br> HSE GT Limited Edition '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Range Rover Sport HSE Luxury '10-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Range Rover Sport Supercharged '10-'13,<br> Supercharged Limited Edition '13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport Autobiography '11-'13 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |G |Discovery SE '17-'20, Range Rover Sport SE '14-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Discovery Landmark Edition '20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P300 S '21-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Discovery P360 S - Canada only: '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P300 R-Dynamic S '21-'23 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery P360 R-Dynamic S '21-'23 [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P300 Dynamic SE '24-'26 [Pos. 8 is X] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Discovery P360 Dynamic SE '24-'25, Canada only: '26 <br> [Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Discovery P360 R-Dynamic HSE '21-'23,<br> P360 Dynamic HSE - Canada only: '24-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Metropolitan Edition '23-'25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Discovery P360 Gemini Edition '26,<br> Discovery P360 Tempest Edition '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '14 <br> [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '15, HSE Limited Edition '15 <br> [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Discovery HSE '17-'20,<br> Range Rover Sport HSE '17-'18 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '19 [Pos. 8 is V or K or U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE '20, HSE Silver Edition '21 <br> [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport HSE Silver Edition '22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |H |Discovery HSE Luxury '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery HSE Luxury '18-'20 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Discovery First Edition '17 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST '16 [Pos. 7 is P or V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport HSE Dynamic '17-'19 [Pos. 8 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover Sport HST Mid '19-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport P400e HSE '20,<br> P400e HSE Silver Edition '21-'22 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P400e Autobiography '20-'21 <br> [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '15,<br> Supercharged Limited Edition '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '16,<br> Supercharged Dynamic '16,<br> Supercharged Dynamic Limited Edition '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover Sport Supercharged '17-'18,<br> Supercharged Dynamic '17-'19,<br> HSE Dynamic '20-'22 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '14 [Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '15 [Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '16 [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport Autobiography '17, '19-'22,<br> Autobiography Dynamic '18 [Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport SVR '15-'22, SVR Carbon Edition '21-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Range Rover Sport P360 S '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Sport P360 SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |T |Range Rover Sport P400 Dynamic S - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |L |Range Rover Sport Dynamic SE '23-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P400 Dynamic HSE - <br> Canada only: '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P440e Autobiography '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |M |Range Rover Sport P440e HSE Dynamic - Canada only: '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover Sport P550e Autobiography '24-'26,<br> P530 Autobiography '25-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover Sport P530 First Edition '23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition One w/Obsidian Black or Flux Silver paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Edition One w/Carbon Bronze paint '24 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover Sport P635 SV Edition Two '25 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Range Rover Sport P635 SV '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover Sport P635 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Range Rover Sport P635 SV Carbon '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |E |Range Rover HSE '10-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover HSE Luxury '10-'12 [Pos. 7 is D] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |F |Range Rover Supercharged '10-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover Autobiography '10-'12 [Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |R |Range Rover (L405) base model '13-'22 |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '13 [Pos. 7 is D] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '14 [Pos. 7 is V or W] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '15, HSE Limited Edition '15 [Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '16 [Pos. 7 is P, V, or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '17-'19 [Pos. 8 is V or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '20 [Pos. 8 is U or K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover HSE '21 [Pos. 8 is K] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE Westminster Edition '21-'22 <br> [Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover P400e HSE '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover P400e Autobiography '20-'21 [Pos. 8 is Y] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '13 <br> [Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '14,<br> Supercharged SWB Ebony Edition '14 <br> [Pos. 6 is 2 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '15,<br> Supercharged SWB Limited Edition '15 <br> [Pos. 6 is 2 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '16 <br> [Pos. 6 is 2 & Pos. 7 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged SWB '17-'19,<br> P525 HSE SWB '20,<br> P525 HSE Westminster Edition SWB '21-'22 <br> [Pos. 6 is 2 & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography SWB '13-'22 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition SWB '21 <br> [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography Dynamic '17-'22,<br> SVAutobiography Dynamic Black '21-'22 [Pos. 6 is 2] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) HSE LWB '15 <br> [Pos. 6 is 3 & Pos. 7 is V] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '14 <br> [Pos. 6 is 3 & Pos. 7 is E or T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '15,<br> Supercharged LWB Limited Edition '15 <br> [Pos. 6 is 3 & Pos. 7 is T] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '16 <br> [Pos. 6 is 3 & Pos. 7 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |S |Range Rover (L405) Supercharged LWB '17-'19,<br> P525 HSE LWB '20,<br> P525 HSE Westminster Edition LWB '21-'22 <br> [Pos. 6 is 5 & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '14-'15 [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '16 [Pos. 6 is 3] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L405) Autobiography LWB '17-'22 [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) Autobiography Black LWB '14-'15 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover Autobiography Fifty Edition LWB '21 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '16-'17 <br> [Pos. 6 is 3] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Range Rover (L405) SVAutobiography LWB '18-'22 <br> [Pos. 6 is 5] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Range Rover (L460) SE '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Range Rover (L460) Autobiography '22-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Range Rover (L460) P530 First Edition '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |U |Range Rover (L460) P530 SV '22-'23 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Range Rover (L460) P615 SV '24-'26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |0 |Range Rover (L460) P615 SV Black '26 |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 90 base model '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/2 rows of seats '20-'23 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |K |Defender 110 base model w/3 rows of seats '20-'23 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 90 S '21-'25, Canada only: '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 110 S w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |J |Defender 130 S w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Y |Defender 90 X-Dynamic S '21-'22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 90 P400 SE '23 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/2 rows of seats '20-'23 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P500 SE w/2 rows of seats '24 [Pos. 6 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 110 P400 SE w/3 rows of seats '20-'23 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |P |Defender 130 P400 SE w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 90 P400 X-Dynamic SE '22-'26,<br> Defender 90 X-Dynamic SE Sedona Red '26 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/2 rows of seats '21-'26 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P500 X-Dynamic SE w/2 rows of seats '25-'26 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 110 P400 X-Dynamic SE w/3 rows of seats '21-'26 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |2 |Defender 130 P400 X-Dynamic SE w/3 rows of seats '23-'26 <br> [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 90 X-Dynamic HSE '22 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/2 rows of seats '21-'22 <br> [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |3 |Defender 110 X-Dynamic HSE w/3 rows of seats '21-'22 <br> [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/2 rows of seats '22 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 XS Edition w/3 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 75th Limited Edition '23 <br> [Pos. 6 is 6 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 75th Limited Edition w/2 rows of seats '23 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Sedona Red Edition w/2 rows of seats '25 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 Trophy Edition w/2 rows of seats '26 <br> [Pos. 6 is 7 & Pos. 8 is U] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P400 Outbound w/2 rows of seats '24-'26 <br> [Pos. 6 is F & Pos. 8 is U] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 90 First Edition '21 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |1 |Defender 110 First Edition w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |V |Defender 130 First Edition w/3 rows of seats '23 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/2 rows of seats '20 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |9 |Defender 110 HSE w/3 rows of seats '20 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 90 X '21-'23, Canada only: '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/2 rows of seats '20-'26 [Pos. 6 is 7] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 110 X w/3 rows of seats '20-'26 [Pos. 6 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |X |Defender 130 X w/3 rows of seats '23-'26 [Pos. 6 is F] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 90 P525 V8 '24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 90 P525 V8 '22-'23, '25-'26,<br> P525 V8 Carpathian Edition '22-'24 [Pos. 6 is 6] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 110 P525 V8 w/2 rows of seats '24 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 110 P525 V8 w/2 rows of seats '22-'23, '25-'26,<br> P525 V8 Carpathian Edition w/2 rows of seats '22-'24,<br> P525 V8 Bond Edition w/2 rows of seats '22 <br> [Pos. 6 is E & Pos. 8 is E] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |B |Defender 130 P500 V8 w/3 rows of seats '24 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |W |Defender 130 P500 V8 w/3 rows of seats '25-'26 <br> [Pos. 6 is F & Pos. 8 is E] |Awd |Class F (7,001-8,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |- |Z |Defender 110 P635 OCTA w/2 rows of seats '25-'26,<br> P635 OCTA Edition One w/2 rows of seats '25,<br> P635 OCTA Black w/2 rows of seats '26 <br> [Pos. 6 is E & Pos. 8 is 9] |Awd |Class E (6,001-7,000 lbs.) |Manual seat belts, Dual front airbags & Front Side Airbags & Side Curtain Airbags |} ===Body Type=== {| class="wikitable" |+Position 6 !VIN code !Description |- |1 |4-door wagon (Range Rover '87-'12, Defender 110 '93, Discovery '94-'04) |- |1 |2-door soft top (Freelander SE3) ('03-'05) |- |1 |2-door wagon (Range Rover Evoque 2-d '12-'17) |- |2 |2-door soft top (Defender 90) ('94-'95, '97) |- |2 |4-door wagon (Freelander) ('02-'05) |- |2 |4-door wagon (LR2 '08-'15, Discovery Sport '15-'26, Range Rover Evoque 4-d '12-, LR3 '05-'09, LR4 '10-'16, Discovery '18-, Range Rover Sport '06-'22, Range Rover Sport P400e '20, Range Rover SWB (L405) '13-'22, Range Rover Velar '18-) |- |3 |2-door wagon (Defender 90) ('95, '97) |- |3 |4-door wagon LWB (Range Rover LWB '14-'16) |- |3 |4-door wagon LWB w/Class E GVWR (Range Rover SVAutobiography LWB '17) |- |4 |4-door wagon [[w:Plug-in hybrid|PHEV]] (Range Rover P400e '20-'21, Range Rover Sport P400e '21-Early '22) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover Supercharged LWB & Autobiography LWB '17) |- |5 |4-door wagon LWB w/Class F GVWR (Range Rover LWB (L405) '18-'22) |- |5 |2-door convertible (Range Rover Evoque convertible '17-'19) |- |6 |2-door wagon (Defender 90 '21-) |- |7 |4-door wagon w/2 rows of seating (Defender 110 P300/P400 '20-) |- |9 |4-door wagon (Range Rover SWB (L460) '22-, Range Rover Sport '23-) |- |B |4-door wagon (Discovery '17) |- |B |4-door wagon LWB (Range Rover LWB (L460) '22-) |- |E |4-door wagon w/3 rows of seating (Defender 110 P300/P400 w/opt. 3rd row '20-) |- |E |4-door wagon w/2 rows of seating (Defender 110 V8 models '22-) |- |F |4-door wagon w/extended length (Defender 130 '23-) |} SWB=Short-wheelbase, LWB=Long-wheelbase ===Engine Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 7 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | 1 || 3.5L || V8 || Gas ||OHV||MPI. [[w:Rover V8 engine|(Ex-GM) Rover V8 engine]]. Land Rover Range Rover ('87-'88). |- | 1 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Single VANOS (Intake VVT). BMW M62TUB44 engine. Land Rover Range Rover ('03-'05). |- | 2 || 3.9L || V8 || Gas ||OHV||MPI. (Ex-GM) Rover V8 engine.<br> Land Rover Range Rover SWB ('89-'94), Range Rover County Classic [SWB] ('95), Defender 110 ('93),<br> Defender 90 ('94-'95), Discovery ('94-'95). |- | 2 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.0 SE ('95-'99),<br> Discovery ('96-'02), Defender 90 ('97). |- | 2 || 2.5L || 90° V6 || Gas ||DOHC,<br /> 24 valve||Sequential MPI. VIS. [[w:Rover KV6 engine|Rover KV6 engine]]. Land Rover Freelander ('02-'05). |- | 3 || 4.2L || V8 || Gas ||OHV||MPI. (4275 cc, actually 4.3L). (Ex-GM) Rover V8 engine. Land Rover Range Rover County LWB ('93-'95). |- | 3 || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Jaguar AJ33S engine. Land Rover Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 4 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Range Rover 4.6 HSE ('96-'99), Discovery ('03). |- | 4 || 4.0L || 60° V6 || Gas ||SOHC,<br /> 12 valve||Sequential MPI. Variable intake manifold. Ford Cologne V6 engine.<br> Land Rover LR3 ('05-'07 & also '08-'09 in Canada). |- | 5 || 4.0L || V8 || Gas ||OHV||Sequential MPI. (3947 cc, actually 3.9L). (Ex-GM) Rover V8 engine. LEV.<br> Land Rover Range Rover 4.0 SE ('00), Discovery ('00-'02). |- | 5 || 4.4L || V8 || Gas ||DOHC,<br /> 32 valve||Sequential MPI. Continuously VCP (Intake VVT). Jaguar AJ41 engine.<br> Land Rover LR3 ('05-'09), Range Rover ('06-'09), Range Rover Sport ('06-'09). |- | 6 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. LEV ('00-'02) or ULEV ('03).<br> Land Rover Range Rover 4.6 HSE ('00-'02), 4.6 SE ('01), Discovery ('03). |- | 9 || 4.6L || V8 || Gas ||OHV||Sequential MPI. (Ex-GM) Rover V8 engine. Land Rover Discovery ('04). |- | D || 5.0L || V8 || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). CPS (Intake VVL). VIS. Jaguar AJ133 engine (LR-V8).<br> Land Rover LR4 ('10-'13), Range Rover ('10-'13), Range Rover Sport ('10-'13). |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('10-'16), Range Rover Sport ('10-'16). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Range Rover Td6 ('16), Range Rover Sport Td6 ('16). |- | P || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('16), Range Rover Sport ('16). |- | T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 32 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('14-'15), Range Rover Sport ('14-'15). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover LR4 ('14-'16), Range Rover ('14-'16), Range Rover Sport ('14-'16). |- | W || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,<br /> 24 valve||Flex Fuel. Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Range Rover ('14), Range Rover Sport ('14). |} VVT=Variable Valve Timing. VCP=Variable Camshaft Phasing. VCT=Variable Camshaft Timing. VIS=Variable Intake System. LEV=Low Emissions Vehicle. ULEV=Ultra-Low Emissions Vehicle. CPS=Cam Profile Switching. VVL=Variable Valve Lift. ===Transmission Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |4 |6-speed automatic (Aisin AWF21) (LR2 '08-'09) |- |B |6-speed automatic (Aisin AWF21) (LR2 '10-'15, Range Rover Evoque '12-'13) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '15-'16, Range Rover Evoque '14-'16) |} ===Transmission Type (All models 2017)=== {| class="wikitable" |+Position 7 !VIN code !Description |- |B |8-speed automatic (ZF 8HP) (Discovery '17) |- |B |9-speed automatic (ZF 9HP) (Discovery Sport '17, Range Rover Evoque '17) |- |F |8-speed automatic (ZF 8HP) (Range Rover '17, Range Rover Sport '17) |} ===Transmission Type (All Models 1987-2016 EXCEPT LR2, Discovery Sport, Range Rover Evoque)=== {| class="wikitable" |+Position 8 !VIN code !Description |- |2 |5-speed automatic [manual shift mode: Steptronic or CommandShift] (Jatco JF506E) (Freelander '02-'05) |- |4 |4-speed automatic (ZF 4HP22 or w/4.6L V8: 4HP24) (Range Rover '87-'02, Discovery '94-'04, Defender 90 '97) |- |4 |5-speed automatic (ZF 5HP24) (Range Rover '03-'05) |- |4 |6-speed automatic (ZF 6HP26X) (LR3 '05-'09, Range Rover '06-'09, Range Rover Sport '06-'09) |- |4 |6-speed automatic (ZF 6HP28X) (LR4 '10-'13, Range Rover '10-'12, Range Rover Sport '10-'13) |- |6 |8-speed automatic (ZF 8HP) (LR4 '14-'16) |- |8 |5-speed manual (Defender 110 '93, Defender 90 '94-'95, Discovery '94-'97) |- |F |8-speed automatic (ZF 8HP) (Range Rover '13-'16, Range Rover Sport '14-'16) |} All are LHD (Left-hand drive). ===Engine Type (LR2, Discovery Sport, Range Rover Evoque only 2008-2016)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover LR2 ('13-'15), Discovery Sport ('15-'16), Range Rover Evoque ('12-'16). |- | N || 3.2L || I6 || Gas ||DOHC,<br /> 24 valve||MPI. VCT (Intake VVT). CPS (Intake VVL). VIS. [[w:Volvo SI6 engine#B6324S5|Volvo SI6 engine - B6324S5]]. Land Rover LR2 ('08-'12). |- |} VCT=Variable Cam Timing. VVT=Variable Valve Timing. CPS=Cam Profile Switching. VVL=Variable Valve Lift. VIS=Variable Intake System. ===Engine Type (All models 2017 only)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('17), Range Rover Sport ('17). |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).<br> Land Rover Discovery Sport ('17), Range Rover Evoque ('17). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('17), Range Rover Td6 ('17), Range Rover Sport Td6 ('17). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine.<br> Land Rover Discovery ('17), Range Rover ('17), Range Rover Sport ('17). |} ==Engine 2018-== ===Engine Variant (All models 2018-)=== {| class="wikitable" |+Position 7 |- ! VIN !! Power Level/Engine !! Transmission !! Model |- |R (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |S (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('18), Range Rover Evoque ('18-'19) |- |F (followed by X) |237 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19) |- |G (followed by X) |286 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport ('19), Discovery Sport P290 ('20) |- |F (followed by X) |246 hp 2.0L Ingenium turbo I4 |9-speed auto. |Discovery Sport P250 ('20-'26), Range Rover Evoque S/SE/1st Edition ('20),<br> Range Rover Evoque P250 ('21-'26) |- |G (followed by X) |296 hp 2.0L Ingenium turbo I4 |9-speed auto. |Range Rover Evoque R-Dynamic S/SE/HSE ('20),<br> Range Rover Evoque P300 HST ('22-'23) |- |R (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by X) |247 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P250 ('19-'26) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Range Rover Velar P300 (Canada only: '19-'20) |- |R (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar ('18) |- |E (followed by N) |180 hp 2.0L Ingenium turbodiesel I4 |8-speed auto. |Range Rover Velar D180 ('19) |- |R (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar ('18) |- |F (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P340 ('19-'20) |- |E (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Velar P380 ('19-'20) |- |E (followed by U) |335 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P340 ('21-'23, Canada only: '24-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Velar P400 R-Dynamic HSE ('21-'22), <br> Range Rover Velar P400 HST ('23), <br> Range Rover Velar P400 Dynamic SE/HSE ('24-'25), <br> Range Rover Velar P400 Dynamic SE/Autobiography/Belgravia Ed. ('26) |- |E (followed by E) |550 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Velar SVAutobiography Dynamic ('20) |- |R (followed by V) |340 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Discovery ('18-'20), Range Rover Sport SE/HSE ('18-'19), Range Rover ('18-'19) |- |R (followed by K) |254 hp 3.0L "Lion" AJD-V6 turbodiesel V6 |8-speed auto. |Discovery Td6 ('18-'20), Range Rover Sport Td6 ('18-'21), Range Rover Td6 ('18-'21) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('21) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('21) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('22-'24) |- |F (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Discovery P300 ('25-'26) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Discovery P360 ('22-'26) |- |S (followed by V) |380 hp 3.0L AJ126 supercharged V6 |8-speed auto. |Range Rover Sport HSE Dynamic ('18-'19), Range Rover HSE ('18-'19) |- |R (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport SE/HSE (Mid '19) |- |S (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport HST (Mid '19) |- |S (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 SE/HSE ('20),<br> Range Rover Sport P360 SE/HSE Silver ('21-'22), Range Rover (L405) P360 ('20-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 HST ('20-'22), Range Rover P400 HSE ('20),<br> Range Rover (L405) P400 HSE Westminster ('21-'22) |- |R (followed by Y) |398 hp 2.0L Ingenium turbo I4 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P400e ('20-'22), Range Rover P400e ('20-'21) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport ('18-'19), Range Rover ('18-'19) |- |S (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('18-'19) |- |S (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover SVAutobiography Dynamic, SVAutobiography LWB ('18-'19) |- |S (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport P525 ('20-'22), Range Rover (L405) P525 ('20-'22) |- |R (followed by E) |575 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover Sport SVR ('20-'22) |- |R (followed by E) |557 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Range Rover (L405) SVAutobiography Dynamic, SVAutobiography LWB ('20-'22) |- |E (followed by U) |355 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P360 ('23-'26) |- |F (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Range Rover Sport P400 ('23-'26), <br> Range Rover (L460) P400 SE ('22-'26) |- |E (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P440e ('23) |- |F (followed by 4) |434 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover P440e ('23) |- |E (followed by 4) |454 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P460e ('25-'26) |- |F (followed by 4) |542 hp 3.0L Ingenium <br> turbo & E-supercharged I6 + 1 motor <br> Gas-Electric [[w:Plug-in hybrid|PHEV]] |8-speed auto. |Range Rover Sport P550e ('24-'26), Range Rover P550e ('24-'26) |- |E (followed by 7) |523 hp 4.4L BMW N63 (JLR NC10)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P530 ('23), <br> Range Rover (L460) P530 ('22-'23) |- |F (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover Sport P635 SV Edition One ('24),<br> Range Rover Sport P635 SV Edition Two ('25), Range Rover Sport P635 SV ('26) |- |E (followed by 9) |523 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P530 ('24-'26), Range Rover Sport P530 ('25-'26) |- |F (followed by 9) |606 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Range Rover (L460) P615 SV ('24-'26) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 110 P300 ('20) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 110 P400 ('20) |- |R (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('21-'22), Defender 110 P300 ('21-'22) |- |R (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('21-'22), Defender 110 P400 ('21-'22) |- |R (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('22), Defender 110 P525 ('22) |- |E (followed by X) |296 hp 2.0L Ingenium turbo I4 |8-speed auto. |Defender 90 P300 ('23-'25, Canada only: '26), Defender 110 P300 ('23-'26) |- |E (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('23) [Pos. 5 is J] |- |F (followed by U) |296 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 130 P300 S ('24-'26) |- |E (followed by U) |395 hp 3.0L Ingenium <br> turbo & E-supercharged I6 |8-speed auto. |Defender 90 P400 ('23-'26), Defender 110 P400 ('23-'26), Defender 130 P400 ('23-'26) |- |F (followed by E) |493 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 110 P500 ('24-'26), Defender 130 P500 ('24-'26) |- |E (followed by E) |518 hp 5.0L AJ133 supercharged V8 |8-speed auto. |Defender 90 P525 ('23-'26), Defender 110 P525 ('23-'26) |- |E (followed by 9) |626 hp 4.4L BMW S68 (JLR NC11)<br> twin-turbo V8 |8-speed auto. |Defender 110 P635 OCTA ('25-'26) |} ===Engine Type (All models 2018-)=== {| class="wikitable" |+Position 8 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 32 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ133S engine (LR-V8S).<br> Land Rover Range Rover ('18-'22), Range Rover Sport ('18-'22),<br> Range Rover Velar SVAutobiography Dynamic ('20), Defender V8 ('22-'26). |- | K || 3.0L || 60° V6 Turbo [[w:Intercooler|IC]] || Diesel ||DOHC,<br /> 24 valve||Common-rail Direct injection. Ford-PSA "Lion" AJD-V6 engine.<br> Land Rover Discovery Td6 ('18-'20), Range Rover Td6 ('18-'21), Range Rover Sport Td6 ('18-'21). |- | N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,<br /> 16 valve||Common-rail Direct Injection. Exhaust VVT. JLR Ingenium AJ20D engine.<br> Land Rover Range Rover Velar ('18-'19) |- | U || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve||48v Mild Hybrid. E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine.<br> Land Rover Discovery ('21-), Range Rover ('20-), Range Rover Sport (Mid '19-), Range Rover Velar ('21-), Defender ('20-). |- | V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,<br /> 24 valve||Direct injection. Dual Continuously VCT (VVT). Jaguar AJ126 engine. Land Rover Discovery ('18-'20),<br> Range Rover ('18-'19), Range Rover Sport ('18-Mid '19), Range Rover Velar ('18-'20). |- | X || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine.<br> Land Rover Discovery Sport ('18-'26), Range Rover Evoque ('18-), Range Rover Velar ('18-), Defender ('20-'26), Discovery ('21-). |- | Y || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 16 valve||Direct Injection. Dual VVT. CVVL (Intake VVL). JLR Ingenium AJ20P4/AJ200P engine + 1 Front motor.<br> 12.4 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P400e ('20-'21), Range Rover Sport P400e ('20-Early '22). |- | 4 || 3.0L || I6 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 24 valve||E-supercharger. Direct Injection. Dual VVT. CVVL (Intake VVL).<br> JLR Ingenium AJ20P6/AJ300P engine + 1 Front motor. 31.8 kWh Lithium-ion Battery Pack.<br> Land Rover Range Rover P440e ('23), P550e ('24-); Range Rover Sport P440e ('23), P460e ('25-), P550e ('24-). |- | 7 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW N63B44T3 [N63TU3] engine [JLR NC10-P8H]. Land Rover Range Rover [L460] ('22-'23), Range Rover Sport ('23). |- | 9 || 4.4L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve||48v Mild Hybrid. Direct Injection. Dual VVT (Double VANOS). Valvetronic (Intake VVL). BMW S68B44TO [S68B44A] engine [JLR NC11-P8S]. Land Rover Range Rover [L460] ('24-), Range Rover Sport ('24-),<br> Defender Octa ('25-). |- |} CVVL=Continuously Variable Valve Lift. ==Check Digit/Gearbox (Position 9)== * USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]] ==Model Year Code (Position 10)== ''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]'' ==Plant Codes (Position 11)== * A - Solihull, West Midlands, England, UK * H - Halewood, Merseyside, England, UK * 2 - Nitra, Slovakia ==External links== * [http://www.clifton.nl/calvin.html CalVIN, the on-line free Land Rover VIN CALculator] * [http://www.fourfold.org/LR_FAQ Land Rover FAQ archive] * [http://www.vindecoderz.com/EN/Land%20Rover Land Rover VIN decoder] {{BookCat}} ci62vbs0b8o6a3l99jyqj1z8gpdoyz5 Wikibooks:Reading room/Proposals 4 155682 4679799 4679749 2026-11-03T14:40:53Z Codename Noreste 3441010 /* Disable (some) page creation by temporary accounts */ + 4679799 wikitext text/x-wiki __NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left<!--|limit=2-->}} Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks. {{User:MiszaBot/config |archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s |algo = old(120d) |counter = 1 |key = 1f2adc5eee951900b65c7b981b786191 |minthreadstoarchive = 1 |minthreadsleft = 1 }} {{clear}} <!--Take threads to archive below this line--> <!--Add new threads to bottom of page--> == New gadget to browse subpages == Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video: [[File:Subpages_gadget_demo.webm|frameless]] To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]: <syntaxhighlight lang="javascript"> mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' ); </syntaxhighlight> If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC) :Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:43, 2 July 2026 (UTC) :This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC) : @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC) ::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires <code>mediawiki.api</code> and <code>@wikimedia/codex</code>. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using <code>mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );</code>, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC) ::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC) ::::Just checking in here—was this resolved/completed? I see [[MediaWiki:Gadget-Subpages.js]], and I assume everything is now taken care of in terms of WB-wide installation? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:14, 30 October 2026 (UTC) ::::: This was already resolved, feel free to close this. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:09, 30 October 2026 (UTC) == Breadcrumbs in the title == Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so: <gallery> Wikisource breadcrumbs proposal (before).png|Current breadcrumbs Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs </gallery> What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC) :I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:14, 17 August 2026 (UTC) :I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the "new" version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC) == Approve [[Wikibooks:CheckUser]] as a local policy? == Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC) :I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC) :I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC) == FlaggedRevs again == {{closed|[[phab:T440519]] was done, sending FlaggedRevs down to the void. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:52, 27 October 2026 (UTC)}} <div class="cd-moveMark">''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''</div> Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system. Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here. {{collapse top}} * <code>autoreview</code> and <code>editor</code> would be <code>autopatrolled</code> and <code>patroller</code>, respectively. * <code>wgUseNPPatrol</code> and <code>wgUseFilePatrol</code> would be re-enabled for English Wikibooks. * <code>autopatrol</code> and <code>patrol</code> would be re-assigned back to sysops and their respective user groups. * <code>patroller</code> would also have <code>rollback</code> and <code>suppressredirect</code> and its rate limit untouched. {{collapse bottom}} Best, [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC) :{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC) :{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC) :{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC) :: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC) :{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC) :{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as "E" for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC) :Will <code>patroller</code> be granted automatically? [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC) :: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC) :::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the <code>patroller</code> right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC) :::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC) ::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC) ::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC) :::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the <code>patrol</code> right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC) :::: I believe that would require some additional code on InitialiseSettings.php, and as for <code>reviewer</code>, I'm not sure we should still use that user group term over <code>patroller</code> as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC) : If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC) :{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be "our primary counter-vandalism tool"). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC) :: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC) {{end closed}} == Disable (some) page creation by temporary accounts == {{tracked|T443449}} Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&type=create for some examples.) As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC) : From a technical point of view, this would require moving <code>createpage</code> from unregistered users (<code><nowiki>*</nowiki></code>) to registered users (<code>user</code>), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages. : Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar). : And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC) :: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC) :::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC) :::: Okay, but I provided some alternatives above. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC) : In that case, I have no objections here. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC) :I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC) :: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC) :Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). :* Anons are already precluded from editing pages that have been "protected" by admins. :* Anon user contributions are automatically marked for Review before they become public :* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? :Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC) :: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC) :::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC) ::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC) :: @[[User:~2026-40500-29|~2026-40500-29]], is your response considered an objection? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:55, 27 October 2026 (UTC) :Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. :I don't know where the number <500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. :Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC) ::i think setting limitations to configuration changes would affect those who are unregistered users.anyway it is ::a good idea though but let's think about it outside the box [[User:Luhesa Kahuma|Luhesa Kahuma]] ([[User talk:Luhesa Kahuma|discuss]] • [[Special:Contributions/Luhesa Kahuma|contribs]]) 22:47, 30 October 2026 (UTC) : I see consensus here to implement this change, but I will wait one more day before I implement the patch on Gerrit. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 22:02, 2 November 2026 (UTC) :{{done|I filed [[phab:T443449]]}}. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 14:40, 3 November 2026 (UTC) == Add inactivity policies for patrollers and uploaders? == I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years. I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence). Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy. Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC) : {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC) :: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC) ::: CC to @[[User:MathsScienceNerd1|MathsScienceNerd1]], who was previously TechVindicator. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 27 October 2026 (UTC) :@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC) :: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC) == Approving [[Wikibooks:Outdated books]] as a policy == I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below: {{hidden archive top|Policy text}} Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here. ;For books that aren't up to date, but can be reasonably updated This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself! ;For books that cannot be reasonably updated This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed. If the case is unambiguous: # Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}. # Move the book to a subpage of [[Wikibooks:Outdated books/Archive]]. # Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/<book title>}}. # (''optional'') Inform the author(s) of the book of your decision. If the case is ambiguous: Follow these steps if there is any reasonable doubt about if the book can be updated. # Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion. # The proposal for archiving will be discussed. # If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is. {{hidden archive bottom}} [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC) : I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC) ::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC) ::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC) : {{support}} for approval as a guideline, as I said and mentioned above. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:45, 27 October 2026 (UTC) == Wikibooks Magazine == I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely). <br> If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think? [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC) :{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC) :{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC) :I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other <abbr>WMF</abbr> wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:36, 21 October 2026 (UTC) : Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC) ::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC) : We can do that with [[Wikibooks:Magazine]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:00, 27 October 2026 (UTC) ::I will create a page about what the Wikibooks Magazine on the page provided, and the editions that will follow. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 07:32, 28 October 2026 (UTC) == Discussion on whether to create an extended mover user group == Currently, patrollers (formerly reviewers) have the <code>suppressredirect</code> user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we: # Remove <code>suppressredirect</code> from patrollers # Add <code>suppressredirect</code> to <code>extendedmover</code> as well as include <code>delete-redirect</code> (for deleting redirects with a single revision) and <code>move-subpages</code> (to move all subpages of a book in a single action) # Also include <code>noratelimit</code> to <code>extendedmover</code> instead of using a custom rate limit (optional), or increase the limit to 500 This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al. This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC) :@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC) :Oppose, don't see the point. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 11:12, 3 November 2026 (UTC) == Enabling wgUseRCPatrol == Some of our sister projects have <code><nowiki>wgUseRCPatrol</nowiki></code> enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC) : {{support}}. This would mimic the functionality of FlaggedRevs when reviewing pages and would help detect vandalism much easier. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:35, 2 November 2026 (UTC) gs37wm0456w2ricvwxlf6ef1yd2l1am 4679811 4679799 2026-11-03T15:43:35Z Codename Noreste 3441010 /* Discussion on whether to create an extended mover user group */ reply to Leaderboard ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]]) 4679811 wikitext text/x-wiki __NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left<!--|limit=2-->}} Welcome to the '''Proposals reading room'''. On this page, Wikibookians are free to talk about suggestions for improving Wikibooks. {{User:MiszaBot/config |archive = Wikibooks:Reading room/Proposals/%(year)d/%(monthname)s |algo = old(120d) |counter = 1 |key = 1f2adc5eee951900b65c7b981b786191 |minthreadstoarchive = 1 |minthreadsleft = 1 }} {{clear}} <!--Take threads to archive below this line--> <!--Add new threads to bottom of page--> == New gadget to browse subpages == Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video: [[File:Subpages_gadget_demo.webm|frameless]] To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]: <syntaxhighlight lang="javascript"> mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' ); </syntaxhighlight> If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC) :Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:43, 2 July 2026 (UTC) :This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC) : @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC) ::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires <code>mediawiki.api</code> and <code>@wikimedia/codex</code>. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using <code>mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );</code>, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC) ::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC) ::::Just checking in here—was this resolved/completed? I see [[MediaWiki:Gadget-Subpages.js]], and I assume everything is now taken care of in terms of WB-wide installation? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:14, 30 October 2026 (UTC) ::::: This was already resolved, feel free to close this. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:09, 30 October 2026 (UTC) == Breadcrumbs in the title == Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so: <gallery> Wikisource breadcrumbs proposal (before).png|Current breadcrumbs Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs </gallery> What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC) :I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:14, 17 August 2026 (UTC) :I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the "new" version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC) == Approve [[Wikibooks:CheckUser]] as a local policy? == Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC) :I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC) :I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC) == FlaggedRevs again == {{closed|[[phab:T440519]] was done, sending FlaggedRevs down to the void. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:52, 27 October 2026 (UTC)}} <div class="cd-moveMark">''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''</div> Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system. Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here. {{collapse top}} * <code>autoreview</code> and <code>editor</code> would be <code>autopatrolled</code> and <code>patroller</code>, respectively. * <code>wgUseNPPatrol</code> and <code>wgUseFilePatrol</code> would be re-enabled for English Wikibooks. * <code>autopatrol</code> and <code>patrol</code> would be re-assigned back to sysops and their respective user groups. * <code>patroller</code> would also have <code>rollback</code> and <code>suppressredirect</code> and its rate limit untouched. {{collapse bottom}} Best, [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC) :{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC) :{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC) :{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC) :: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC) :{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC) :{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as "E" for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC) :Will <code>patroller</code> be granted automatically? [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC) :: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC) :::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the <code>patroller</code> right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC) :::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC) ::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC) ::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC) :::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the <code>patrol</code> right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC) :::: I believe that would require some additional code on InitialiseSettings.php, and as for <code>reviewer</code>, I'm not sure we should still use that user group term over <code>patroller</code> as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC) : If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC) :{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be "our primary counter-vandalism tool"). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC) :: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC) {{end closed}} == Disable (some) page creation by temporary accounts == {{tracked|T443449}} Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&type=create for some examples.) As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC) : From a technical point of view, this would require moving <code>createpage</code> from unregistered users (<code><nowiki>*</nowiki></code>) to registered users (<code>user</code>), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages. : Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar). : And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC) :: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC) :::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC) :::: Okay, but I provided some alternatives above. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC) : In that case, I have no objections here. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC) :I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC) :: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC) :Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). :* Anons are already precluded from editing pages that have been "protected" by admins. :* Anon user contributions are automatically marked for Review before they become public :* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? :Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC) :: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC) :::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC) ::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC) :: @[[User:~2026-40500-29|~2026-40500-29]], is your response considered an objection? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:55, 27 October 2026 (UTC) :Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. :I don't know where the number <500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. :Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC) ::i think setting limitations to configuration changes would affect those who are unregistered users.anyway it is ::a good idea though but let's think about it outside the box [[User:Luhesa Kahuma|Luhesa Kahuma]] ([[User talk:Luhesa Kahuma|discuss]] • [[Special:Contributions/Luhesa Kahuma|contribs]]) 22:47, 30 October 2026 (UTC) : I see consensus here to implement this change, but I will wait one more day before I implement the patch on Gerrit. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 22:02, 2 November 2026 (UTC) :{{done|I filed [[phab:T443449]]}}. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 14:40, 3 November 2026 (UTC) == Add inactivity policies for patrollers and uploaders? == I am proposing that we include inactivity policies for both patrollers and uploaders, which include no edits or logged actions for two years. I previously proposed this for [now former] reviewers, but someone probably objected. Now, if their rights are removed for inactivity, they can request them back at [[WB:RFP]] (without prejudice), unless the rights were removed for cause (such as a vote of confidence). Edit: Someone also proposed inactivity policies for importers (and possibly import uploaders too), which are sensitive permissions. I initially forgot to include that permission when creating this proposal, but now I am also proposing for importer permissions to have an inactivity policy. Which procedure should we choose if we agree on the inactivity policy proposals? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 22:18, 18 October 2026 (UTC) : {{Oppose}} - There is no need for inactivity policies for patrollers and uploaders, since there is no harm in keeping patrollers and uploaders in the current roles. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:09, 20 October 2026 (UTC) :: I have to disagree here. Some larger projects have their own inactivity policies for patrollers, such as [[m:Meta:Patrollers#Removal of access]] on Meta-Wiki and [[w:en:WP:NPPREVOKE]] (new page reviewers on English Wikipedia, a similar permission). [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 00:34, 20 October 2026 (UTC) ::: CC to @[[User:MathsScienceNerd1|MathsScienceNerd1]], who was previously TechVindicator. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 27 October 2026 (UTC) :@[[User:Codename Noreste|Codename Noreste]]: I will say that it seems odd to propose these policies for patrollers and uploaders without proposing an equivalent for [[WB:importers|importers]], when that's arguably a far more sensitive role. I do at least support an inactivity policy for importers, and am as yet neutral vis-à-vis patrollers and uploaders. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 02:05, 21 October 2026 (UTC) :: @[[User:JJPMaster|JJPMaster]] I've edited my proposal to also include both importers and import uploaders. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC) == Approving [[Wikibooks:Outdated books]] as a policy == I created this draft policy two years ago, and would like to see whether the community is willing to approve it now. I have substituted it in its current form (00:16, 20 October 2026 (UTC)) below: {{hidden archive top|Policy text}} Sometimes, there will be a book that has a lot of information that was very useful at the time, but has become out of date over time. There are generally two procedures that can be followed here. ;For books that aren't up to date, but can be reasonably updated This category applies to books that, for instance, have not been updated with new information in a few years, but where the subject still exists and new information can be found about it. In this scenario, you should add the {{tlx|Outdated}} tag to the top of the book, and post on its discussion page explaining what should be updated. Or, you can always just [[Wikibooks:Be bold|be bold]] and update it yourself! ;For books that cannot be reasonably updated This category includes books that are so outdated that their subject either no longer exists, or has changed so much since the book was written that it is virtually unrecognizable, and it would be nearly impossible to update it satisfactorily. These books should generally not be deleted, as they do provide valuable information, but should not be easily accessible to readers looking for recent information. Here, the following instructions should be followed. If the case is unambiguous: # Add {{tlx|Archived}} to the top of the book. Doing this will also remove it from search engine indexes, unless you override this by using {{tlx|Archived|2=noindex=false}}. # Move the book to a subpage of [[Wikibooks:Outdated books/Archive]]. # Replace the content of the redirect left behind after the move with {{tlx|Soft redirect|2=Wikibooks:Outdated books/Archive/<book title>}}. # (''optional'') Inform the author(s) of the book of your decision. If the case is ambiguous: Follow these steps if there is any reasonable doubt about if the book can be updated. # Follow the instructions at {{Section link|Wikibooks:Requests for deletion#Deletion}} to file a request. Make sure to note that the request is for archiving, not deletion. # The proposal for archiving will be discussed. # If consensus has been reached to archive the book, any uninvolved user may close the discussion and follow the instructions in {{Section link|#If the case is unambiguous}}. Otherwise, the book will remain as is. {{hidden archive bottom}} [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 00:16, 20 October 2026 (UTC) : I have a question, is there any difference if we approve this as a guideline (common sense) compared to as a policy? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 00:24, 20 October 2026 (UTC) ::@[[User:Codename Noreste|Codename Noreste]]: That would also be fine; I'm not exactly sure if the delineation between guidelines and policies on Wikibooks is as clearly defined as on Wikipedia. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 00:27, 20 October 2026 (UTC) ::: I would suggest approving this as a guideline should an experienced, yet uninvolved editor may use their judgment and common sense when dealing with outdated books. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 00:29, 20 October 2026 (UTC) : {{support}} for approval as a guideline, as I said and mentioned above. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:45, 27 October 2026 (UTC) == Wikibooks Magazine == I am proposing that we create a magazine quarterly, or bimonthly detailing latest news on Wikibooks (and maybe ''some'' current affairs, considering the shutdown of Wikinews, though this is unlikely). <br> If it were to be approved, it would be inspired by the WikiKids magazine in Dutch [https://wikikids.nl/Wikikids:Magazine/11 link], though with a Wikibooks feel. A user could propose something for the next Wikibooks Magazine on the talk page of [[Wikibooks:Magazine]], including ideas for the next Wikibooks magazine. It would be promoted on the front page (and maybe) on the MediaWiki Sitenotice, providing information about the next edition. On Wikikids, the project has been going on since 2024, and since then there have been 11 editions. What do you think? [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:20, 20 October 2026 (UTC) :{{Courtesy ping|Codename Noreste}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:36, 20 October 2026 (UTC) :{{Courtesy ping|JJPMaster}} [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:04, 20 October 2026 (UTC) :I '''weak support''' a '''quarterly''' publication. There isn't a ton of activity here compared to many other <abbr>WMF</abbr> wikis, so there won't be quite as much to report as there is at (e.g.) [[:w:en:WP:SIGNPOST]] or [[:wikt:en:WIktionary:The Headword]] but that said, having a publication could encourage engagement by showing what hard work others are doing. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 19:36, 21 October 2026 (UTC) : Because of the low activity, should the releases be biannual (every six months)? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:29, 22 October 2026 (UTC) ::I would support a quarterly publication, given the fact that Wikibooks does not have enough traffic (in my opinion) to justify a bimonthly publication, but, at the same time, the idea of a biannual publication seems relatively infrequent. Furthermore, the magazine would follow the quarterly format used on WikiKids. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 03:47, 23 October 2026 (UTC) : We can do that with [[Wikibooks:Magazine]]. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:00, 27 October 2026 (UTC) ::I will create a page about what the Wikibooks Magazine on the page provided, and the editions that will follow. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 07:32, 28 October 2026 (UTC) == Discussion on whether to create an extended mover user group == Currently, patrollers (formerly reviewers) have the <code>suppressredirect</code> user right as well as a rate limit per InitialiseSettings.php. However, I am consulting with the community if we: # Remove <code>suppressredirect</code> from patrollers # Add <code>suppressredirect</code> to <code>extendedmover</code> as well as include <code>delete-redirect</code> (for deleting redirects with a single revision) and <code>move-subpages</code> (to move all subpages of a book in a single action) # Also include <code>noratelimit</code> to <code>extendedmover</code> instead of using a custom rate limit (optional), or increase the limit to 500 This is because, per the principle of least privilege, patrollers should be responsible for marking new pages as patrolled and reverting vandalism/spam, while extended movers are trustworthy users (usually non-admins) responsible for moving books, et al. This is ''not'' a proposal to implement the extended mover user group, but rather a community consultation. Thoughts? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 19:48, 20 October 2026 (UTC) :@[[User:Codename Noreste|Codename Noreste]]: Relevant prior discussion can be found [[Wikibooks:Reading room/Proposals/2020/December#Suppress redirect feature|here]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 20:21, 20 October 2026 (UTC) :Oppose, don't see the point. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 11:12, 3 November 2026 (UTC) :: Oddly enough, while patrollers have a rate limit of moving more pages in under a minute, they do not have <code>move-subpages</code> (which allows them to move a book and its subpages in a single action). Without that mechanism to move subpages, they will have to perform some additional moves by hand. Because of that, I said that <code>move-subpages</code> will be added to the extended mover user group. Since that user group is considered a somewhat privileged (non-admin) user group, it will be granted to trustworthy users who have a demonstrated need for it, provided that they have a history of moving pages without causing some sort of disruption during the process. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 15:43, 3 November 2026 (UTC) == Enabling wgUseRCPatrol == Some of our sister projects have <code><nowiki>wgUseRCPatrol</nowiki></code> enabled, but on the other hand, we do not. I think we should enable this so that we can also focus on reviewing edits in the recent changes, not just new pages. [[Wikibooks:Patrolling]] can also include information about this once we enable it here. Thoughts? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:39, 27 October 2026 (UTC) : {{support}}. This would mimic the functionality of FlaggedRevs when reviewing pages and would help detect vandalism much easier. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:35, 2 November 2026 (UTC) nevk0rfeuds81lglqhpznrn3qykc5b6 Wikijunior:Food Alphabet/D 110 178261 4679779 4671716 2026-11-03T13:17:30Z ~2026-58523-79 3630299 /* */ 4679779 wikitext text/x-wiki <div style="text-align: center; font-size: 400%;">'''D''' is for '''D'''ates重播)星期二至六 00:30-02:30 (两集连播) [[File:Mazafati dates - whole, halved and seed.jpg|alt=dates|center|frameless|506x506px]] {{FoodNav}} 8doq3b30k7gniln7qi9nq5j8zujjczw 4679781 4679779 2026-11-03T13:18:05Z NDG 3510220 [[WB:REVERT|Reverted]] edit by [[Special:Contributions/~2026-58523-79|~2026-58523-79]] ([[User talk:~2026-58523-79|talk]]) to last version by Saroj 4540606 wikitext text/x-wiki <div style="text-align: center; font-size: 400%;">'''D''' is for '''D'''ates</div> [[File:Mazafati dates - whole, halved and seed.jpg|alt=dates|center|frameless|506x506px]] {{FoodNav}} cq2qvq529wfqo41ffzyg274nltf6ylg Professionalism 0 249490 4679875 4607590 2026-11-04T02:30:22Z Yqj3km 3579825 4679875 wikitext text/x-wiki {{DISPLAYTITLE:Cases and Ideas in Professional Ethics}} {{book search|prefix=Professionalism}} {{clear}} == Table of Contents == <!-- -When adding entries, please place them in this format: [[/MyPage/]]. Similarly, these entries' titles should start with "Professionalism/MyPage", not "MyPage". --> * [[Professionalism/Foreword|Foreword]] <div><div style="width:49%;float:left"> ;Biomedical Engineering * [[/HeLa Cells and Timeless Ethics/]] * [[/Cheryl Eckard and GlaxoSmithKline/]] * [[/Fishbein and the NIH/]] * [[/Matthias Rath and Cellular Medicine/]] * [[/Frances Oldham Kelsey and Thalidomide/]] * [[/The Guatemala Syphilis Experiment/]] * [[/Peter Buxtun and the Tuskegee Syphilis Study/]] * [[/Purdue Pharma and OxyContin/]] * [[/David Franklin, Parke-Davis, and Neurontin/]] * [[/Vioxx: Merck and the FDA/]] * [[/Love Canal, New York/]] * [[/Kenneth Kendrick and Peanuts/]] * [[/Peter Rost and Pfizer/]] * [[/Resistance to Polio Vaccination in Northern Nigeria/]] * [[/Kunal Saha and the World Bank/]] * [[/Hwang Woo-suk and Stem Cells/]] * [[/Eli Lilly and Zyprexa/]] * [[/Kit Foshee and Beef Product Incorporated/]] * [[/Andrew Wakefield and the MMR Vaccine/]] * [[/Medical Ghostwriting/]] * [[/Conrad Gorinsky, the Wapishana, and Biopiracy/]] * [[/Victoria Hampshire and Lester Crawford/]] * [[/Luk Van Parijs and Data Fabrication/]] * [[/Martin Shkreli, Turing Pharmaceuticals, and Daraprim/]] * [[/Metal-on-Metal Hip Implants/]] * [[/Tyler Shultz, Elizabeth Holmes, and Theranos/]] * [[/The FDA Nine/]] * [[/April Evans and NASA/]] * [[/Krebiozen/]] * [[/Jonathan Lundgren and USDA/]] * [[/Martin Keller, SmithKline Beecham, and Study 329/]] * [[/Fen-Phen and American Home Products/]] * [[/The Disneyland Measles Outbreak of 2014-2015/]] * [[/Rhona Applebaum, Coca-Cola, and Health Research/]] * [[/Yoshitaka Fujii and Medical Research Fraud/]] * [[/Shiv Chopra and Livestock/]] * [[/Medicine, AI, and Professional Discretion/]] * [[/Stanley Pons, Martin Fleischmann, and Cold Fusion/]] * [[/Dr Daniel Merenstein, Medical Screening, and Professional Discretion/]] * [[/Vicky Phelan, Grainne Flanelly, David Gibbons, and Cervical Check/]] * [[/PIP and Silopren/]] * [[/He Jiankui and Designer Babies/]] * [[/Insulin: The Deadly Price/]] * [[/Ethics in Organ Allocation/]] ;Chemical Engineering * [[/OSHA and the Pitkin, LA, Explosion/]] * [[/Union Carbide and Bhopal/]] * [[/Myron Mehlman and Mobil Corporation/]] * [[/Times Beach, Missouri/]] * [[/Frederic Whitehurst and the FBI/]] * [[/Jeffrey Wigand and Brown & Williamson/]] * [[/Deborah Rice and the American Chemistry Council/]] * [[/Mark Whitacre and Archer Daniels Midland/]] * [[/Manjunath Shanmughan and the Indian Oil Corporation/]] * [[/BP Texas City Refinery Explosion/]] * [[/Mectizan Donation Program/]] * [[/Freedom Industries and the Elk River/]] * [[/PEPCON Ammonium Perchlorate Plant Explosion/]] * [[/The Valero Refinery Fire/]] * [[/Gepp, Dee, and Lentz, and the leak at Aberdeen Proving Ground/]] * [[/The Case of Marlene Garcia-Esperat/]] * [[/Greenpeace, Donors Trust, and climate change research/]] * [[/Lenny Bernstein, Exxon, and Climate Change/]] * [[/Raymond Orbach, Charles Groat, and Fracking Research/]] * [[/Tianjin Chemical Storage Explosions/]] * [[/Arthur Galston and Agent Orange/]] * [[/Toxic Gas Releases at Honeywell’s Baton Rouge Refrigerant Plant/]] * [[/Mona Hanna-Attisha and Lead Exposure in Flint, Michigan/]] * [[/DuPont, C8, and Parkersburg, West Virginia/]] * [[/Thomas Midgely Jr. and the Rise and Fall of Tetraethyl Lead/]] * [[/Port of Beirut Chemical Explosion/]] ;Civil Engineering * [[/Boston's Big Dig Project/]] * [[/Bruce Boler and the EPA/]] * [[/Collapse of the Francis Scott Key Bridge/]] * [[/Collapse of the TV Antenna in Missouri City, Texas/]] * [[/Collapse of the “Swinging Bridge,” Heber Springs, Arkansas/]] * [[/Ed Turner and the City of Idaho Falls/]] * [[/Evan Vokes and TransCanada/]] * [[/The Flint Water Supply/]] * [[/Jack Gillum and the Hyatt Regency Skywalks/]] * [[/Manoj Kumar Gupta and Shiv Das/]] * [[/Satyendra Dubey and the National Highways Authority of India/]] * [[/URS and the I-35 Bridge/]] * [[/William LeMessurier and the CitiCorp Building/]] * [[/The GE Three/]] * [[/San Bruno Pipeline Explosion/]] * [[/FIU Pedestrian Bridge Collapse/]] * [[Professionalism/Collapse of the Morandi Bridge|Collapse of the Morandi Bridge]] ;Computer Science and Engineering * [[/Aaron Swartz and Information Freedom/]] * [[/Eric Raymond and Open Source Software/]] * [[/Shawn Carpenter and Sandia National Laboratories/]] * [[/Mark Klein and Room 641A/]] * [[/Therac-25/]] * [[/Kevin Mitnick/]] * [[/BitTorrent and BitCoin/]] * [[/Kim Dotcom and Megaupload/]] * [[/Suchir Balaji and OpenAI/]] * [[/Yasser Elabd and Microsoft/]] * [[/Sockpuppetry/]] * [[/Lulzsec/]] * [[/Corruption at the National Security Agency/]] * [[/ChatGPT and the New York City Department of Education/]] * [[/Edward Snowden and the NSA/]] * [[/Google Street View and Wi-Spy/]] * [[/The Death of Elaine Herzberg/]] * [[/Response to Sony Hack of 2014/]] * [[/Ariane 5 Flight 501/]] * [[/David Barksdale and Digital Privacy/]] * [[/Ellen Pao, Reddit, and the trolls/]] * [[/Phillip Rogaway, Computer Scientists, and Government Surveillance/]] * [[/Honest Shanghai/]] * [[/Thorlaug Agustsdottir: Free Speech and Abuse on Social Media/]] * [[/Apple, the FBI, Personal Data/]] * [[/Tor, CMU, and the FBI/]] * [[/Volkswagen's Emissions Scandal/]] * [[/Predictive Policing/]] * [[/Zenimax v. Oculus VR/]] * [[/Geofeedia, Social Media, and Law Enforcement/]] * [[/Margaret Goodearl, Ruth Ibarra, and Hughes Microelectronics/]] * [[/Apple Batteries: Transparency, Trust, and Technology/]] * [[/Vigilant Solutions, Law Enforcement, and Privacy/]] * [[/Justin Rosenstein and the Like Button/]] * [[/Tristan Harris, Time Well Spent, and Smartphones/]] * [[/The Equifax Data Leak/]] * [[/Chamath Palihapitiya and Facebook/]] * [[/Ashok Chandwaney, Sophie Zhang, and Facebook/]] * [[/Knightscope and Autonomous Data Machines/]] * [[/Cody Wilson and the Liberator/]] * [[/The Firing of James Damore/]] * [[/The Right to Repair/]] * [[/Apple, iPhone Software, and Planned Obsolescence/]] * [[/Amazon, Rekognition, and Law Enforcement/]] * [[/The 2015 Open Letter in Autonomous Weapons /]] * [[/Microsoft Employees, Project JEDI, and HoloLens/]] * [[/Mike Davidson, Rahul Vohra, and Superhuman/]] * [[/The Rise and Fall of the Advanced Technology External Advisory Council/]] * [[/Google Employees and Project Maven/]] * [[/Andy Rubin, Google, and Sexual Harassment in Tech/]] * [[/Data Ownership/]] * [[/Software Vulnerability Disclosure/]] * [[/Ian Bogost, Nadia Eghbal, and Software Engineers/]] * [[/Barry Lynn, New America Foundation, and Google/]] * [[/The Google Walkouts of 2018/]] * [[/Parler and the Capitol Insurrection of 2021/]] * [[/Timnit Gebru and Ethical AI at Google/]] * [[/Tom Yardic and Blue Cross Blue Shield of Minnesota/]] * [[/The GitHub Employee Dismissal of January 8, 2021/]] * [[/Suspension of @realDonaldTrump/]] * [[/Sexism, Riot Games, and a Class Action Lawsuit/]] * [[/Cher Scarlett and Tech Labor Advocacy/]] * [[/Rebekah Jones, Ron DeSantis, and the Florida Department of Health/]] * [[/Tang Mingfang, Foxconn, and Amazon/]] * [[/Facebook, Cambridge Analytica, and User Data/]] * [[/Frances Haugen and Facebook/]] * [[/Labor Organizing at Google/]] * [[/Thomas le Bonniec and Siri/]] * [[/Rudwin Ayala, the Exploding Hoverboard, and Abuse of AI by Lawyers/]] * [[/The US Tech Sector, the H-1B Visa, and Employment Abuse/]] * [[/Ifeoma Ozoma and Pinterest/]] * [[/OpenAI, Corporate Integrity, and the Firing of Sam Altman/]] * [[Professionalism/Mark Zuckerberg, Corporate Culture, and "Masculine Energy"|Mark Zuckerberg, Corporate Culture, and "Masculine Energy"]] * [[Professionalism/Mobley v. Workday and the Ethics of Algorithmic Hiring|Mobley v. Workday and the Ethics of Algorithmic Hiring]] ;Mechanical and Aerospace Engineering * [[/Mars Climate Orbiter/]] * [[/Air France Flight 447/]] * [[Professionalism/Air India Flight 171|Air India Flight 171]] * [[/Ernest Fitzgerald and the Lockheed C-5A/]] * [[/Rodney Rocha and Columbia/]] * [[/The Ford Pinto Gas Tank Controversy/]] * [[/The Toyota Recalls of 2009-2010/]] * [[/Mark Lund and the FAA/]] * [[/The Explosion on ''Deepwater Horizon''/]] * [[/Roger Boisjoly, Morton Thiokol, and NASA/]] * [[/LaMia Flight 2933/]] * [[/The Loss of USS Thresher/]] * [[/Apollo 1/]] * [[/Apollo 13/]] * [[/Iridium 33 and Kosmos 2251/]] * [[/David Lappa and the Lawrence Livermore National Lab/]] * [[/Northeast Blackout of 2003/]] * [[/The Loss of Ocean Ranger/]] * [[/China Airlines Flight 611/]] * [[/Chesley Sullenberger and US Airways Flight 1549/]] * [[/Vince Weldon and the 787/]] * [[/Don Baker and Smart Meters/]] * [[/John Houbolt and Lunar Orbit Rendezvous/]] * [[/Takata Corporation and Airbags/]] * [[/Tom Williams and the Wings of the A380/]] * [[/TWA Flight 800/]] * [[/Larry Gibson and Mountaintop Removal/]] * [[/Poppy Northcutt, Apollo, and Women in Tech/]] * [[/William McNeilly and Trident/]] * [[/The Loss of Petrobras Platform 36/]] * [[/Richard Perkins and the NRC/]] * [[/Joseph Mangan and the A380/]] ;Systems and Information Engineering * [[/Salvador Castro and Air-Shields, Inc/]] * [[/The Aviation Safety Reporting System/]] * [[/Ladbroke Grove Rail Collision/]] * [[/The MGM Grand Hotel Fire/]] * [[/William Sanjour and the EPA/]] * [[/Fort Totten Metro Crash/]] </div><div style="width:49%;float:left;padding:0 0 0 2%"> ;Nuclear Engineering * [[/Rusi Taleyarkhan and Bubble Fusion/]] * [[/George Galatis and Millstone 1/]] * [[/Chernobyl Disaster/]] * [[/Walter Tamosaitis and the Hanford Site/]] ;Other Cases in Professional Ethics * [[/The Mysterious Death of Dr. Ramin Pourandarjani/]] * [[/Alexander Coward and the UC Berkeley Department of Mathematics/]] * [[/Archer Blood and the Blood Telegram/]] * [[/The U.N. and Cholera in Haiti/]] * [[/Ethics and ADHD Diagnosis/]] * [[/John Stumpf, Wells Fargo, and Salesmanship/]] * [[/A Matter of Honor: Lou Bloomfield and Academic Dishonesty/]] * [[/Ball Don't Lie: The Moral Code of the NBA/]] * [[/Cheating Scandal at Malmstrom Air Force Base/]] * [[/Rolling Stone & UVA: A Case on Professional Journalism/]] * [[/Amy Stroupe and BB&T/]] * [[/Badminton Scandal of the 2012 Olympics/]] * [[/Bernie Madoff's Ponzi Scheme/]] * [[/The Bogdanov Affair/]] * [[/BP's Response to the Deepwater Horizon Spill/]] * [[/Bradley Birkenfeld, the UBS Whistle-blower/]] * [[/Brett Crozier and the U.S. Navy/]] * [[/Chelsea Manning: Integrity Vs. Professionalism/]] * [[/British American Tobacco and the Promotion of Smoking/]] * [[/Canadian Caper/]] * [[/The Case of Bowe Bergdahl/]] * [[/The Case of Juan Williams, Vivian Schiller, and Ellen Weiss/]] * [[/Cynthia Cooper and Worldcom/]] * [[/Dan Graves and ITT Educational Services/]] * [[/Daniel Ellsberg and the Pentagon Papers/]] * [[/David Lewis and EPA/]] * [[/Dr Jeffrey Young et al. and University of Virginia Health System/]] * [[/The Dismissal of President Teresa Sullivan/]] * [[/Electronic Sports Ethics: Professionalism in an Unestablished Industry/]] * [[/Frank Serpico and NYPD /]] * [[/FDA and the Emergency Use Authorization /]] * [[/Greenwashing/]] * [[/Greg Smith, Goldman Sachs and the New York Times/]] * [[/Hillsborough Disaster/]] * [[/Hugh Thompson, William Calley, and the My Lai Massacre/]] * [[/Huy Fong Foods, Sriracha, and the City of Irwindale/]] * [[/Jane Akre, Steve Wilson, and Posilac/]] * [[/Jeffrey Sterling and Operation Merlin/]] * [[/Joe Darby, Samuel Provance, and Abu Ghraib/]] * [[/Joe Paterno and the Penn State Board of Trustees/]] * [[/Joel Clement and the Department of the Interior/]] * [[/Jordan Belfort and Stratton Oakmont/]] * [[/Johnson & Johnson's Response to the 1982 Tylenol Poisonings/]] * [[/Julia Bluhm, SPARK, and Seventeen Magazine/]] * [[/Julia Davis and the Department of Homeland Security/]] * [[/Justin Hopson and the Lords of Discipline/]] * [[/Kennedy, Clinton, and Changing Norms of Journalism/]] * [[/Lance Armstrong, the Tour de France, and a Culture of Cheating/]] * [[/Lou van den Dries, George Orwell, and Mandatory Ethics Training/]] * [[/The Mann Gulch Fire/]] * [[/Marc Hauser and Research Fraud/]] * [[/Marsha Coleman-Adebayo and EPA/]] * [[/Michael de Guzman and the Bre-X Scandal/]] * [[/Michael Mann, Ken Cuccinelli, and the Hockey Stick/]] * [[/Michael Woodford and Olympus/]] * [[/Operation Red Wings and the Rules of Engagement/]] * [[/Oscar Pistorius and the Rise of the Iron Man Era/]] * [[/The Over Prosecution of Kurt Mix/]] * [[/The Swatting of Andrew Finch/]] * [[/The Work Climate at Google/]] * [[/Pamela Davis and Operation Board Games/]] * [[/Perry Fellwock and the NSA/]] * [[/Piper Alpha Oil Rig Disaster/]] * [[/Professionalism in Social Media /]] * [[/Professionalism in ''The Intern''/]] * [[/Ruth Marcus, Jeff Bezos, and The Washington Post/]] * [[/Sean Hoare and Andy Coulson/]] * [[/Sherron Watkins and Enron/]] * [[/Sign Stealing in Major League Baseball/]] * [[/Robert MacLean and Unsecured TSA Communication/]] * [[/The Sokal Affair/]] * [[/Southwest Airlines Flight Cancellations of December 2022/]] * [[/Stanford Research Scandal/]] * [[/Startup Deception/]] * [[/Susan Fowler, Uber, and Workplace Sexual Harassment/]] * [[/The Case of Wisheart, Dhasmana, and Roylance/]] * [[/The Durham Fish Oil Trials/]] * [[/The Pat Tillman case/]] * [[/Typhoid Mary/]] * [[/Jose Rodriguez and the CIA Interrogation Tapes/]] * [[/YouTube Censorship/]] * [[/Dr. Malachi Love-Robinson/]] * [[/Driving for Uber/]] * [[/Who Is an Engineer? Burton Siegal and the State of Illinois/]] * [[/Monsanto's Seed Patents/]] * [[/Conflict of Interest Wikipedia Editing: Sunshine Sachs and Jack Craver/]] * [[/The Case of Daphne Caruana Galizia/]] * [[/Anarchist Cookbook/]] * [[/The Sinking of the Titanic/]] * [[/Vtubers and the Ethics of Synthetic Media/]] * [[/Tim Bray, Maren Costa, Emily Cunningham, and Amazon/]] * [[/Fraud in U.S. Collegiate Athetics/]] * [[/The Hippocratic Oath for Technologists/]] * [[/The Johnson & Johnson Baby Powder Case/]] * [[/Avondale Mills, Norfolk Southern, and the E.P.A/]] ;Research Ethics * [[/Alexandra Elbakyan and Sci-Hub/]] * [[/Scott Reuben and Research Fraud/]] * [[/Shih Chi Liu and the NSF/]] * [[/Climategate/]] * [[/Albert Costa, Janet Geipel, Ethics, and Language/]] * [[/Sabotage In Academia/]] ;Thinkers, Ideas and Problems * [[/Ethics and Autonomous AI/]] * [[/Anita Sarkeesian, Women and Gaming/]] * [[/The Dilbert Principle/]] * [[/Office Ethics according to The Office/]] * [[/Office Ethics according to Office Space/]] * [[/E.F. Schumacher/]] * [[/Ted Kaczynski/]] * [[/Diffusion of Responsibility/]] * [[/Irving Janis and Groupthink/]] * [[/Bill Joy and Technological Risks/]] * [[/Marketing of Pharmaceuticals/]] * [[/Balancing Individual Rights vs Welfare of Society/]] * [[/Pekka Himanen and The Hacker Ethic/]] * [[/Hacktivism/]] * [[/Nimbyism/]] * [[/Valuing of Human Life in Risk Analysis/]] * [[/The Precautionary Principle/]] * [[/The IRS Whistleblowers Program/]] * [[/Human subjects in clinical research/]] * [[/Adderall in Academics/]] * [[/Using Animals in Research/]] * [[/James Shikwati and Aid to Africa/]] * [[/Diane Vaughan and the normalization of deviance/]] * [[/Defensive Medicine/]] * [[/Drinking Culture in China/]] * [[/Growth Hacking/]] * [[/Moonlighting/]] * [[/Corporate Psychopaths/]] * [[/Salami Slicing and the Least Publishable Unit/]] * [[/Stanford Prison Experiment/]] * [[/Environmental Racism/]] * [[/Restaurant Ethics according to Bob's Burgers/]] * [[/Workplace Harassment Training/]] * [[/Sexual Orientation Conversion Therapy/]] * [[/Ikigai at Work/]] * [[/The Right to Be Forgotten/]] * [[/Voluntourism/]] * [[/Thomas H. Murray/]] * [[/Market Influences on Clinical Trials/]] * [[/Norbert Wiener and the Expert’s Responsibility for Weapons/]] * [[/Marc Andreessen and Techno-Optimism/]] </div> <br style="clear:all" /> </div> {{Shelves|general engineering|Class projects|Business}} {{alphabetical|P}} {{status|100%}} 8jauzf0kha0uazduhlfsc1u788sury7 Basic Math for Adults/Basic Terminology 0 249701 4679810 3523473 2026-11-03T15:40:42Z Chalky282 3630310 /* The Basic Sets of Numerals */ 4679810 wikitext text/x-wiki =Basic Math Terminology= ==The Decimal System== The '''[[wikipedia:decimal|decimal]]''' system, sometimes referred to as '''base 10''', contains a total of ten identifiers called '''digits'''. The decimal system is widely used because humans generally have ten fingers on which to count. For now, we will disregard other [[wikipedia:Numeral system|number systems]] for the sake of simplicity with the understanding that the decimal system is not unique. The ten digits of the decimal system, arranged from lowest to greatest, are: *[[wikipedia:0 (number)|0]] (zero) *[[wikipedia:1 (number)|1]] (one) *[[wikipedia:2 (number)|2]] (two) *[[wikipedia:3 (number)|3]] (three) *[[wikipedia:4 (number)|4]] (four) *[[wikipedia:5 (number)|5]] (five) *[[wikipedia:6 (number)|6]] (six) *[[wikipedia:7 (number)|7]] (seven) *[[wikipedia:8 (number)|8]] (eight) *[[wikipedia:9 (number)|9]] (nine) The decimal system uses '''[[wikipedia:positional notation|positional notation]]''' to represent numbers larger than 9. This means that a digit's position in relation to other digits affects its meaning. Digits in the furthest right position represent the number of ones being counted, while digits in the second position from the right represent the number of tens. Digits in the third position from the right represent the number of hundreds, and digits in the fourth position from the right represent the number of thousands. This pattern can continue [[wikipedia:infinity|forever]]; for more information, see [[wikipedia:orders of magnitude|orders of magnitude]]. For example, the number 535,254 means 5 hundreds of thousands, 3 tens of thousands, 5 thousands, 2 hundreds, 5 tens, and 4 ones. We would say this number as "five hundred thirty-five thousand two hundred fifty-four". Other systems, like binary (base 2) exist. Base 2 would just have 2 digits, 0 and 1, base 3 has 3 digits, 0 ,1 and 2, and so on. ==The Basic Sets of Numerals== '''Counting numbers''' are the numbers we use every day to count things. Mathematicians sometimes refer to this set of numbers as the '''Natural Numbers'''. These are represented by the sign <math>\mathbb{N}</math>, for Natural Numbers. :<math>1,2,3,4...\ </math> '''Whole numbers''' include all the counting numbers and zero. :<math>0,1,2,3,4...\ </math> '''Negative numbers''' include the opposite of all the Counting Numbers. They are counted in the opposite direction of Counting numbers and have -, the negative sign, in front of them. :<math>...-4,-3,-2,-1</math> '''Integers''' include all numbers without a decimal or any fractional components. Another way to say this is all of the Whole Numbers and their negatives. These are represented by the sign <math>\mathbb{Z}</math>, for the German word ''Zahlen'', which means "numbers". :<math>...-4,-3,-2,-1,0,1,2,3,4...</math> {{BookCat}} 6d6ingx7qpexlbxi6giq8504dadqsc7 Basic Math for Adults/Basic Whole Numbers 0 249702 4679812 4521958 2026-11-03T15:45:50Z Chalky282 3630310 /* Multiplication Table */ Expanded multiplication table to 12 by 12 4679812 wikitext text/x-wiki =Basic Whole Number Operations= ==Rounding Whole Numbers== '''Rounding''' is the process of finding the closest number to a specific value. You round a number up or down based on the last digit you are interested in. :<math>{{down}\atop\overbrace{0,1,2,3,4}} {{up}\atop\overbrace{,5,6,7,8,9}}</math> For example, rounding the number 245 to the nearest tens place would round ''up'' to 250, while the number 324 rounded to the nearest tens place would be rounded ''down'' to 320. Following the same logic, one could round to the nearest whole number. For example, 1.5 (pronounced as "one point five" or "one and a half") would be rounded up to 2, and 2.1 would be rounded down to 2. ==Adding Whole Numbers== First, arrange the numbers in columns. For example, <math>134+937</math> <math>\begin{align} 134\\ +\underline{937}\\ \underline{\ \quad} \end{align} </math> Add the first column (starting on the right) <math>\begin{align} 134\\ +\underline{937}\\ \underline{\quad1}\\ 1 \end{align} </math> Note the 10's digit put under the next column. Now add the next column and the number underneath: <math>\begin{align} 134\\ +\underline{937}\\ \underline{\ \ 71}\\ 1 \end{align} </math> Finish it off with the other columns: <math>\begin{align} 134\\ +\underline{937}\\ \underline{1071}\\ 1\ 1 \end{align} </math> So the answer to 134 + 937 is 1071 ==Subtracting Whole numbers== To subtract numbers think of a basket of oranges. If you have ten oranges in a basket and you remove eight oranges you are left with two oranges. For example: <math>\begin{align} 10\\ \underline{-8}\\ 2 \end{align}</math> If you have ten oranges in a basket and you remove all ten then you will no longer have any oranges so you are left with zero oranges. For example: <math>\begin{align} 10\\ \underline{-10}\\ 0 \end{align}</math> To subtract large numbers use this method: 1. Arrange the number that is being subtracted from on top of the number being subtracted from it(ex. 2594-1673) <math>\begin{align} {2 5 9 4 } \\ \underline{-1 6 7 3 }\\ \underline{\qquad}\\ \end{align}</math> 2. Subtract each column starting from the right and going to the left <pre> 2 5 9 4 -1 6 7 3 ________ 2 1 </pre> 3. If you encounter a number that can't be subtracted without becoming negative,"borrow" subtract(if possible) 1 from the next digit over and add 10 to the digit that can't be subtracted(if not possible continue to borrow from the next digit). <pre> 1 15 X X 9 4 -1 6 7 3 ________ 9 2 1 </pre> 4. continue until done note: that 921+1673=2594. ==Multiplying Whole Numbers== ===Single number times Single number producing a Single number=== Take the first number as <math>a</math>. Take the second number as <math>b</math>. Add <math>a</math> to itself <math>b</math> times. :<math> a = 2</math> :<math> b = 3</math> :<math> (a)\times(b)= 2 \times 3 = {{\text{3 times}}\atop\overbrace{2 + 2 + 2}} = 6 </math> ===Multiplication Table=== To help with multiplying larger numbers by each other, a multiplication table is used. Hopefully this can be memorized to make multiplication easier for you in the future. {| class="wikitable" ! ! style="font-weight: bold;" | 1 ! style="font-weight: bold;" | 2 ! style="font-weight: bold;" | 3 ! style="font-weight: bold;" | 4 ! style="font-weight: bold;" | 5 ! style="font-weight: bold;" | 6 ! style="font-weight: bold;" | 7 ! style="font-weight: bold;" | 8 ! style="font-weight: bold;" | 9 ! style="font-weight: bold;" | 10 !11 !12 |- | style="font-weight: bold;" | 1 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |11 |12 |- | style="font-weight: bold;" | 2 | 2 | 4 | 6 | 8 | 10 | 12 | 14 | 16 | 18 | 20 |22 |24 |- | style="font-weight: bold;" | 3 | 3 | 6 | 9 | 12 | 15 | 18 | 21 | 24 | 27 | 30 |33 |36 |- | style="font-weight: bold;" | 4 | 4 | 8 | 12 | 16 | 20 | 24 | 28 | 32 | 36 | 40 |44 |48 |- | style="font-weight: bold;" | 5 | 5 | 10 | 15 | 20 | 25 | 30 | 35 | 40 | 45 | 50 |55 |60 |- | style="font-weight: bold;" | 6 | 6 | 12 | 18 | 24 | 30 | 36 | 42 | 48 | 54 | 60 |66 |72 |- | style="font-weight: bold;" | 7 | 7 | 14 | 21 | 28 | 35 | 42 | 49 | 56 | 63 | 70 |77 |84 |- | style="font-weight: bold;" | 8 | 8 | 16 | 24 | 32 | 40 | 48 | 56 | 64 | 72 | 80 |88 |96 |- | style="font-weight: bold;" | 9 | 9 | 18 | 27 | 36 | 45 | 54 | 63 | 72 | 81 | 90 |99 |108 |- | style="font-weight: bold;" | 10 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 |110 |120 |- |'''11''' |11 |22 |33 |44 |55 |66 |77 |88 |99 |110 |121 |132 |- |'''12''' |12 |24 |36 |48 |60 |72 |84 |96 |108 |120 |132 |144 |} ==Dividing Whole Numbers== '''Dividing''' whole numbers is the process of determining how many times one number, called the ''dividend'', contains another number, called the ''divisor''. :<math>12 \div 3</math> In this example, 12 is the dividend and 3 is the divisor. Performing a division gives a ''quotient''. :<math>8 \div 4 = 2</math> In the above example, 4 goes into 8 twice; therefore, the quotient would be 2. What happens when the dividend cannot be evenly split by the divisor? This leftover quantity is called the ''remainder''. It's usually separated from the main part of the answer by a lowercase letter “r”. :<math>13 \div 5 = 2\ \mbox{r}\ 3</math> Divisions are often represented as fractions. For example, :<math>68 \div 43 = \frac{68}{43}</math> Some tips: Any number that ends in 0, 2, 4, 6, or 8 can be divided by 2. Any number that ends in 0 or 5 can be divided by 5. Any number thats digits add to 3, 6, or 9 can be divided by 3. Any number thats digits add to 9 can be divided by 9. Any number that ends in 0 can be divided by 10. If the last two digits of any number are divisible by 4 then the whole number is divisible by 4. For example: <math> 1024 \rightarrow 10\textbf{24} \rightarrow 24 \rightarrow 24 \div 4 = 6 r 0 </math> So 1024 is divisible by four because 24 is divisible by 4. ==Factoring Whole Numbers== '''Factoring''' is the process of determining what prime numbers (numbers that cannot be divided by any number but 1 and itself; 2,3, and 5 are prime numbers) when multiplied will give a specific number. This process of factoring is very important in reducing fractions, which is covered in the Fractions chapter of this book. For example: :<math>4 = 2 \times 2\ </math> Or a more complicated example: :<math>180 = 2 \times 2 \times 3 \times 3 \times 5\ </math> A method of factoring numbers is doing a factor tree. For example: <math> 180 \div \textbf{2} = 90 </math> <math> 90 \div \textbf{2} = 45 </math> <math> 45 \div \textbf{5} = 9 </math> <math> 9 \div \textbf{3} = 3 </math> <math> 3 \div \textbf{3} = 1 </math> All of the numbers in bold, known as the divisors, are the prime factors. {{BookCat}} r6z5d6fykef6uylpw31kxg8hzfzg9ai Basic Math for Adults/Glossary 0 249707 4679822 3283519 2026-11-03T17:06:39Z Chalky282 3630310 /* Glossary */ Added definitions to the glossary(might want to review multiplication definition) 4679822 wikitext text/x-wiki =Glossary= Conversion Greatest Common Factor '''Improper Fraction -''' A fraction whose numerator is greater than, or equal to, it's denominator. Least Common Multiple '''Liter''' - The basic unit of volume in the metric system '''Multiplication -''' One of the four basic arithmetic operations that consists of: repeated addition(using the the ×, ⋅ or * symbol) of the multiplicand, continuously using the multiplier to dictate how many times the multiplicand is repeatedly added on top of itself. '''Meter''' - The basic unit of length in the metric system. {{BookCat}} 8asb81gkb0dhe8px82w7ki2gy9k6vh0 On 2D Inverse Problems 0 279393 4679869 4679745 2026-11-04T01:34:58Z DVD206 724793 chapter titles 4679869 wikitext text/x-wiki __NOTOC__ {{rfd}} [[File:Book cover.jpg|center|frameless]] <!-- EDIT BELOW THIS LINE -->== Medical imaging math notes == * [[On 2D Inverse Problems/About the book|About the book]] * [[On 2D Inverse Problems/Overview|Overview]] ** [[On 2D Inverse Problems/Acknowledgements|Acknowledgements]] ** [[On 2D Inverse Problems/Bibliography|Bibliography]] == The Volume I == * [[On 2D Inverse Problems/Basic definitions and background|Basic definitions and background]]<!--=== [[On 2D Inverse Problems/Graphs and manifolds|Graphs and surfaces]] === === [[On 2D Inverse Problems/Harmonic functions|Harmonic functions]] === === [[On 2D Inverse Problems/On random processes|On random processes]] === === [[On 2D Inverse Problems/Special matrices|Special matrices and determinants]] === === [[On 2D Inverse Problems/Electrical networks|Electrical networks]] === === [[On 2D Inverse Problems/The inverse problems|The inverse problems]] ===--> * [[On 2D Inverse Problems/Classics|Classics and hopscotch]]<!--=== [[On 2D Inverse Problems/On the inverse problem of Calderon|On the inverse problem of Calderon]] === === [[On 2D Inverse Problems/"Can One Hear the Shape of a Drum?"|"Can One Hear the Shape of a Drum?"]] === === [[On 2D Inverse Problems/On inhomogeneous string of Krein|On inhomogeneous string of Krein]] ===--> * [[On 2D Inverse Problems/Embedded|Embedded graphics and printing]] * [[On 2D Inverse Problems/Radial|Radially symmetric inverse problems]] <!--=== [[On 2D Inverse Problems/Fourier coordinates|Fourier transform]] ===> === [[On 2D Inverse Problems/Stieltjes continued fractions|Stieltjes continued fractions]] === === [[On 2D Inverse Problems/Solution of the inverse problem|Solution of the inverse problem]] ===--> * [[On 2D Inverse Problems/The square root case|The square root of the minus operator]]<!--=== [[On 2D Inverse Problems/The case of the unit disc|The case of the unit disc]] === === [[On 2D Inverse Problems/An infinite example|An infinite example]] === === [[On 2D Inverse Problems/Zolotarev problem|Zolotarev problem]] ===--> * [[On 2D Inverse Problems/Two models|Duel maps & naps]] * [[On 2D Inverse Problems/redial|Halloween calendar]] * [[On 2D Inverse Problems/Notation|<math>notation</math>]] == The Volume II:Plane and planar knot == * [[On 2D Inverse Problems/Ai|Harmonic continuation on graph]] * [[On 2D Inverse Problems/Papyrus|Analytic continuation on sphere]] * [[On 2D Inverse Problems/Rotation|Spectrum Disc Spin]] * [[On 2D Inverse Problems/Spatial|Spatial Spectrum Spiritual Geometry]] * [[On 2D Inverse Problems/Characteristic|Characteristic: companion and circulant matrices]] ** [[On 2D Inverse Problems/Area|Energy integral sum]] ** [[On 2D Inverse Problems/Orthogonal|"Gravity is optional"]] ** [[On 2D Inverse Problems/Echo|Echo response]] == The volume III: Piracy!? == * [[On 2D Inverse Problems/4|Ghost Spiderweb]] * [[On 2D Inverse Problems/5|Shape-shifting network]] * [[On 2D Inverse Problems/6|Six colors suffices surface]] * [[On 2D Inverse Problems/Zeta zeros|Zeta-function zeros]] ** [[On 2D Inverse Problems/Eta|Ln(2)]] ** [[On 2D Inverse Problems/Complex|Discrete complex analysis]] ** [[On 2D Inverse Problems/Continuous|Continuum hypothesis]] * [[On 2D Inverse Problems/Genes|Genealogy geometry]] ** [[On 2D Inverse Problems/Inferno|<math>\ln_2(\infty)</math>]] == Conclusions == ===[[On 2D Inverse Problems/The Cure|Complexity of infinity]]=== {{Shelves|Mathematical collections}} {{Alphabetical|2}} {{status|75%}} {{reading level|Beginner}} {{BookCat}} 3bh819y6t2nf40vx0rcvz2ewx2ak5h0 Aros/Platforms/Arm Raspberry Pi support 0 286123 4679794 4679748 2026-11-03T14:27:52Z Jeff1138 301139 4679794 wikitext text/x-wiki {{ArosNav}} [[#Native]] [[#Hosted]] [[#Build]] [[#Hardware]] [[#References]] [[#Future]] ==Introduction== [[File:Scalos00.png|thumb|Scalos on Aros Pi3b]] Aros aims to cover Pi 3 to 5 512Mb+ RAM Options to boot from using a good power source to prevent the yellow lightning symbol. *With Pi3b+ the max you can get is 5.1V 2.5A with micro usb. *With Pi4 5.1V 3A with usb-c *With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c * Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] * Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] * Pi 5 - Quad A76 64bit ARMv8 and RP1 "southbridge" with VideoCore 7 D0 (rev1.1) - untested * Pi 5 - Quad A76 64bit ARMv8 and RP1 "southbridge" with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested * Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - * Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 * Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling * Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], * Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible * Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible * Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible ===Native=== * 2013-03 Kalamatee starts work * 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb * 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi] * 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] * 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5] * 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM] ====64bit==== '''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository] '''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 64bit build works well on a single core LE little endian. [https://aros.sourceforge.io/nightly1.html raspi-aarch64-smp-system multicore is available] [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] *Pi500+ untested usb3 booting or nvme ssd *Pi500 untested usb3 booting *Pi5 untested usb3 booting *Pi400 boots with '''USB3''' port based sata3 ssd *Pi4 untested (may need eeprom update from PiOS or Pi SD Imager) *Pi 3 B+ is pre-configured for USB sata3 boot - untested *Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card Speed write wise (top faster) <pre> *NVME Pi5 untested >1000MB/sec or faster if matched correctly *Sata3 ssd 500MB/sec *SD V90 90MB/sec 4K maybe 8K *SD V60 60MB/sec 1080p *SD U3 V30 30MB/sec 720p *SD C10 U1 V10 A1 A2 10MB/sec minimum should be used now *SD C06 6MB/sec *SD C04 4MB/sec </pre> As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -> View -> All files Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. Esc escape key usually closes open windows even the desktop In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. Like most amiga like OSs the audio and networking need to be setup manually Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++ or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off *if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again *...waiting for an address - Disconnect and try Connect Until, Connected to <router> - 192.168.x.x For lan ethernet port, please use Network prefs and the following hardware is *lan9514 Pi3b Pi2 not supported at the moment *lan7515 Pi3b+ type into Device usblan78xx.device as net0: remove other device(s) *bcmgenet Pi4 Pi400 choose for Device bcmgenet.device *cdnsgem Pi5 Pi500 Pi500+ RP1 i/o for cadencegem (network prefs may forget random information when rebooted) Summary <pre> ̽*Pi3a̹+ wifi works, *Pi3b ethernet not supported, usb ethernet not working but wifi prefs setup works *Pi3b+ wifi working and ethernet works *Pi4 untested *Pi400 wifi and ethernet untested *Pi5 wifi and ethernet untested *Pi500 wifi and ethernet untested *Pi500+ wifi works </pre> Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. [http://archives.arosworld.org/index.php?function=browse&cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT). Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555. You may have to delete the cache (Menu -> Page -> Delete cache) to fully retest big Amelinium updates or free up space. Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly DNS lookup failed... close browser and reboot and setup wifi again - repeat until it works again youtube video and audio - js button for javascript must be on/shaded - Settings -> Soundoutput - AHI Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect up to 480p (wifi) and up to 720p (ethernet). Pi4 expect (wifi) (ethernet). If no separate audio stream error - set settings -> Video quality to 360p or lower as Youtube has a fallback mode at that level https://t.me/s/channel_name for Telegram public messages from [https://t.me/s/AROS_official AROS_official] [https://t.me/s/vamped_amiga vamped_amiga] [https://t.me/s/demoscenecracktros demoscenecracktros] *art local js apps like dpaint.js There is normally no Bluetooth support for most amiga like OSs but that has changed recently [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] *Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W *Bluetooth 4.2 BCM4345C0.hcd Pi3B+, Pi4 *Bluetooth 5.0 BCM4345C5.hcd Pi4B rev, CM4 and maybe Pi5 and CM5 <pre> *bthid keyboard mouse support *btserial serial *btpan short range wireless connecting devices </pre> Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g. date 24-Dec-2026 23:59:59 but this will need to be done again after every reset/power off. Maybe hardware [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. USB classes support from Prefs/Trident is still work in process *usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w *[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&file=audio/misc/timidity.lha timidity], Regarding 680x0 emulation, there are several options that could be considered *[https://github.com/kaffeine1/kaffeine kaffeine m68k with Amiga system OS fɹiendly calls going to Aros ones] *[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones *[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games *[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] *[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] [https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] Some exceptions: *Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used *The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V *For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15). With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented. Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi. In the shell (Cntrl + C to end) GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' *PIN -- (Required) Target GPIO pin number (e.g. 12). *SET -- Set pin output value to 0 (LOW) or 1 (HIGH). *GET -- Read and print current digital input level (0 or 1). *MODE -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate). *PULL -- Configure pull resistor: NONE, UP, DOWN. EXAMPLES <pre> GPIO 12 MODE OUT GPIO 12 SET 1 GPIO 12 GET GPIO 13 PULL UP </pre> [https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&pid=13954#post_13954 discussion] Youtube [https://www.youtube.com/watch?v=8dZwGkUKAmA Pi3A̟+ (plus) with smp build and PiAROS], [], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], [], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], [], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], [], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], [https://www.youtube.com/watch?v=nHt_k_QkHe0 AmiWest 2026 Day 1], [https://www.youtube.com/watch?v=nA2fnaOt1Ik Amiwest 2026 Day 2], [https://www.youtube.com/watch?v=zQM4CD64xDE&t=612s&pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... {| class="wikitable sortable" width="90%" ! width="10%" |Pi ! width="10%" |Single Core 2D ! width="10%" |Single Core 3D ! width="10%" |Single Core 3D ! width="10%" |SMP 2D ! width="10%" |SMP 3D ! width="10%" |SMP 3D ! width="35%" |Comments |- | <!--Pi-->Pi3 | <!--Single Core 2D--> | <!--Single Core 3D--> | <!--Single Core 3D--> | <!--SMP 2D--> | <!--SMP 3D--> | <!--SMP 3D--> | <!--Comments--> |- |} ==== 32bit ==== For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD ===Hosted=== AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon Macs] [https://github.com/jonx/Macaros early alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&pid=13910#post_13910 here] with [https://github.com/pomaros pomaros]. There is a [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2076&highlight=jonx&pid=14193#post_14193 work in progress native Mac Apple silicon M1 M2 M3 version] [http://www.aros.org/snapshots1.html old linux and android hosted 32bit] ==== Hosted ==== =====64bit===== [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&rowstart=80&pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] [https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&rowstart=80 From the Aros Raspberry pi 3 64bit thread] Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources. You will need: - Ubuntu 24.04 or 26.04 - qemu-system-aarch64 installed - Internet connection - rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz) 1) Install prerequisites: sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm 2) Clone sources cd <project-directory> git clone https://github.com/aros-development-team/AROS.git --recurse-submodules 3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have: AROS (the directory with cloned sources) fix-dotdot.py rebuild.sh recreate-sdcard.sh run-qemu.sh update-sdcard.sh 4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64 This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step. 5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64 This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour. 6) Run ./recreate-sdcard.sh This will create an sdcard.img file with contents of previous step. 7) Run ./run-qemu.sh This will start QEMU with SD card image and ROM images. It will boot into AROS. =====32bit===== Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013] ../AROS/configure --target=linux-armhf --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux) *armel - many of the "android" machines require since the entire OS is made for soft float VFP. *armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP) Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI. Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets. *needs an AROS code compiler for ARM target *as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes. with—disable-crosstools $AROS_CC is always a wrapper around $KERNEL_CC ? If so, this is wrong for some ports. This can break Darwin, Windows and Android port. Yes, Android port will build. And even work. But it's not good because the port will not be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example: <pre> enum test {foo, bar}; enum test testvar; </pre> sizeof(testvar) will be equal to sizeof(int) in GNUEABI (Linux and AROS) and sizeof(short) on Android. This affects linking objects from static linklibs, for example. Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts. Android is the same. $KERNEL_CC is incompatible with AROS. compiler=kernel is appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or barebone hardware, if we talk about native). This includes bootstraps, their linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations. No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows, Android) this is not true any more, and compiler=kernel is never going to work. If you want to compile your AROS module against host OS includes, append the following to USER_INCLUDES (or USER_CFLAGS, this is effectively the same): -isystem $(GENINCDIR) $(KERNEL_INCLUDES) $(KERNEL_INCLUDES) expands to: -isystem <your_os_includes> -isystem <host_OS_gcc_private_includes> -nostdinc This makes AROS compiler adhering to host OS APIs. If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH). Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one. Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types. Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but "./configure --target=raspi-armhf" is enough to start, then "make arosboot-raspi" will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc). It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output. *armel = typically Debian 6, Ubuntu Maverick, Android, *armhf = typically Debian 7, Debian 8, Ubuntu Precise, Cross-compiling Ubuntu ARM softfp <pre> sudo sh echo 'foreign-architecture armel' >>/etc/dpkg/dpkg.cfg.d/multiarch echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' >/etc/apt/sources.list.d/armel.list apt-get update apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel </pre> <pre> ./configure --target=linux-arm --x-includes=/usr/include \ --enable-includes=/usr/arm-linux-gnueabi/include </pre> Cross-compiling Ubuntu ARM hard-float <pre> sudo sh echo 'foreign-architecture armhf' >>/etc/dpkg/dpkg.cfg.d/multiarch echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' >/etc/apt/sources.list.d/armhf.list apt-get update apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf </pre> <pre> ./configure --target=linux-armhf --x-includes=/usr/include \ --enable-includes=/usr/arm-linux-gnueabihf/include </pre> Now, the AROS build is configured properly and all you need to do is: make ==Build== ===64bit=== [https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] ===32bit=== # download/checkout the source someplace, e.g. /build/AROS-Src/ # make a directory to store external sources AROS downloads, e.g. /build/Ports # make a build directory, e.g. /build/aros-raspi-armhf # cd into the build dir, configure, and then run make -: <pre> >cd /build/aros-raspi-armhf >/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports >make >make arosboot-raspi </pre> then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it. You should then be able to boot the sdcard on your RasPi. The current W.I.P tree to svn. it can be built as follows .. <pre> ./configure --target=raspi-armhf make arosboot-raspi </pre> That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder. NB - if you have a Linux/other install, backup the existing config.txt first arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console "emulation" via code pinched from our libbootconsole), kernel.resource, and exec.library arosraspi.rom contains all the other components needed to boot AROS. The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom). the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO) Help building AROS hosted on Linux ARM Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device. Compilation stops after build libpopupmenu.a and trying to build libatomic have this error: <pre> Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic configure: WARNING: unrecognized options: --disable-nls, --without-x checking for --enable-version-specific-runtime-libs... no checking for --enable-generated-files-in-srcdir... no checking build system type... arm-unknown-linux-gnu checking host system type... arm-unknown-aros checking target system type... arm-unknown-aros checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc checking whether the C compiler works... no configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic': configure: error: C compiler cannot create executables See config.log' for more details make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77 [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512 [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory make[1]: *** [Makefile:361: linklibs-libatomic] Error 10 make: *** [Makefile:183: crosstools] Error 2 </pre> looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi so do make linklibs-aeabi-arm-quick and the missing lib was built. now the next stop is at fatal error: bits/libc-header-start.h: No such file or directory and fatal error: sys/cdefs.h: No such file or directory in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed? fixed with adding -I/usr/include/arm-linux-gnueabihf to where is missing on mmakefiles like USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES) P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles. Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again. My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a "template" to compare to native compilation under arm linux. Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild). The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC. For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script. Thanks compilation now go forward...changed target.cfg under "toolchain-core-armhf-build/bin/linux-arm/gen/config" and do make on "toolchain-core-armhf-build" dir. Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there: #MM- linklibs-armhd : libklibs-aeabi-arm Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this. Try adding this line (and the variant "linklibs-armhf" instead of hd) but it did not solve the automatic building of the missing lib. I must do "linklibs-aeabi-arm-quick". Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case. With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with "cannot find -laeabi " so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok. == Hardware == ===64bit=== ====BCM2712==== With the Pi5 Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. *Raspberry Pi M.2 HAT+ Expansion Board *Geekworm X1001 PCIe to M.2 Key-M NVMe *Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 *Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 *Hat+ Gen2 Gen3 Nvme *GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2 * *2024 RPI AI HAT - Hailo 20TOPs no LLMs *2026 RPI AI HAT+ 2 - Hailo 40TOPs slightly better? [https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi] *Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor *Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor *Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1 HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates ====BCM2711==== With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 the 2711b line used more power when idle, compared to the 2711c *2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues *2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design *Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE *[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles. The instruction encoding for the QPUs is different, but the core instructions are the same. Instructions for packed 8 bit int math has been dropped, along with most of the pack modes. Instructions for packed 16bit float math has been added (2 floats at in a single operation) With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register. the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of "one read port, one write port" to one "two read ports, one write port" block) The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. *vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers. *vc5 added a four thread per QPU mode, with 16 registers per thread. *vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads. With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer) A MMU, allowing a much simpler/faster kernel driver. Many more texture formats, framebuffer formats. h264/x264 [https://github.com/aros-development-team/AROS/commit/caecd66a9508acb0e9ef0a07169a14c33007b208 VideoCore hardware decoding through VCHIQ/MMAL (Pi 1–4)], H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1 HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates All the features needed for opengl es 3.0 Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised Possible maximum performance <pre> VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s </pre> Faster LPDDR4 memory. ====BCM2837==== With the Pi3 * Broadcom BCM43438 chip provides 2.4&nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. [https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. ===32bit=== === Core Kernel === ====BCM2708(family)==== which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM) *Framebuffer (fb) using mailbox *IRQ scheduler, etc *Arasan based SD Card controller *Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&view=article&id=106:rasperry-pi-usb-controller&catid=45:raspberry-pi&Itemid=54 Unofficial DOCS pdf], [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], *[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip *CMOS RAM *VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc *Audio Driver *Serial Peripheral Interface Bus (SPI) *[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers] *I2S *Universal Asynchronous Receiver Transmitter (UART) *[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO] BCM2836 * For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board *[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features], Implemented so far... # Modify the configure system so that it correctly builds for the arm hardware float raspi target. # Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display. # Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function. # Implemented serial debug support # Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc) # Implemented a timer.device to utilise the hardware timers. # Implemented a very basic gfx driver to expose the hardware's framebuffer. # Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media. # Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The "rom" image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot. # Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else. # fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi .. Improvements... # Implement a USB chipset driver "OR" finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the "virtual" hub code in place to represent the raspi's USB port (from poseidons p.o.v) # Implement a driver for the USB NIC (a few weeks - depends on USB above) # Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI] # fix syscall bug in the current raspi kernel code # Graphics depend on having a decent "bcmdma.resource" implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for "blitting". # [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] # [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 # The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate. Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition. The boot sequence carries out several pre-boot tasks *On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf *The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it *configures the memory split for the CPU and GPU *reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings) *loads the “kernel.img” file, again from the same partition *activates the CPU to begin executing the loaded kernel image The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU. RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named "kernel.img" at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem) Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf. You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling. At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules <pre> ? - alias for 'help' mtest - simple RAM test autoscr - run script from memory base - print or set address offset bbm - BBM sub-system bdinfo - print Board Info structure boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootm - boot application image from memory bootp - boot image via network using BootP/TFTP protocol cmp - memory compare coninfo - print console devices and information cp - memory copy crc32 - checksum calculation echo - echo args to console fatinfo - print information about filesystem fatload - load binary file from a dos filesystem fatls - list files in a directory (default /) go - start application at address 'addr' help - print online help iminfo - print header information for application image itest - return true/false on integer compare jade - loadb - load binary file over serial line (kermit mode) loads - load S-Record file over serial line loady - load binary file over serial line (ymodem mode) loop - infinite loop on address range md - memory display mm - memory modify (auto-incrementing) mtest - simple RAM test mw - memory write (fill) nfs - boot image via network using NFS protocol nm - memory modify (constant address) pci - list and access PCI Configuration Space ping - send ICMP ECHO_REQUEST to network host printenv - print environment variables rarpboot - boot image via network using RARP/TFTP protocol reset - Perform RESET of the CPU run - run commands in an environment variable saveenv - save environment variables to persistent storage saves - save S-Record file over serial line setenv - set environment variables sleep - delay execution for some time tftpboot - boot image via network using TFTP protocol USB - USB sub-system usbboot - boot from USB device version - print monitor version </pre> And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way... u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot. Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1, the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS routed only raw hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt. 1:1 relationship between CPU and hardware interrupts is present only on PC. IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class. PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant to be different, its IRQs are hardware-agnostic, they are plain "Hardware IRQ number X, whatever this means". They are low-level actually, and meaningful only in the context of a particular system. Was that not the transition from irq.hidd to kernel.resource? No. A long time ago there was another hacky bit named INTB_TIMERTICK. It was "abstract timer interrupt", used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea. Can someone please enlighten me a little on how the scheduler is meant to work? Poseidon.library creates its "Poseidon Event Task" during RTF_COLDSTART -> then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example. You miss what happens next... 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch(). 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible: 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run. 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list. My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop. There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures. The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table. The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :) Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this: movw r0, #:lower16:label movt r0, #:upper16:label In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations. There are two options - the first one would be to give up and go back to "fake" executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need. Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. GPU VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU. Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute. The good news about this is that we only need to write our HIDD using the OpenVG API. The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf). That's also the bad news. Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much. It's still probably less difficult and less work, than controlling the GPU directly. The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated. It also has some nice font functions, meaning we can lead into an accelerated text mode later. Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC. If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected. have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled. If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work. L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled. Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics. Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever. I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp). #warning "TODO: lookup optimal mmu table settings for raspi memory" /* Set up an identity-mapping for all 4GB */ for(x = 0; x < 4096; x ++) { pagetable[x] = x<<20 | (0x40002|0x80000|0x010000|0x00C00|0x04); } Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages? Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device). You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached) So .. pagetable[x] = x<<20 | 2; should be enough? No, for RAM you need to change the '| 0x40' to '| 0x80' tell dosboot the correct defaults to use Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead, display drivers should auto-install themselves during own initialization phase. I. e. detect hardware=>instantiate itself. This should make things way simpler. With this approach you only need to add the driver into KS image to get the device autobooted. No hardcoded stuff. Currently VESA and VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it. they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context). AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM marked as chip. BTW, is the video processing code you mention CPU code or GPU code? Also, IIRC we have support for "external memory allocators". Perhaps that's what we need for the allocation of GPU RAM through the mailbox. All hosted and x86 native ports should use proper context formats. trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET). Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units. The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ. Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port? It provides a before-anything-else shell prompt on the serial port. You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource. You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs. So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work. Also make sure to add shell.resource and shellcommands.resource for this. That should have done it. If you set "#define DEBUG 1" in arch/all-native/econsole/econsole.c, do you get any additional serial output? have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display? Im assuming it exposes a fake filesystem that tricks aros into booting? The contents of which are: ECON:AROS.boot Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm. To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen. Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks). have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress.. was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression. Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks. Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right) The _LE versions are for when you have endian swapping taking place. If the graphics are the same endian as the CPU, no swapping should occur. I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian. It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary. They were both little-endian. The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode). What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest? Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems? You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it. So, AROS creates the framebuffer bitmap (verified this) -> so surely it should be capable of then rendeing into it? I don't actually create the framebuffer "bitmap object" myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback. In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) So far have -: vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object. vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer, vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. RasPi has to speak to the "operating system" which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls. The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required. The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied. The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds). must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. For 2D dma, set TDMODE, and the spec says "interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer." so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data. The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out). openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits. Actually MEMF_CHIP has to present, for historical reasons. This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP. Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting. As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there. struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi. AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol. <pre> redmask: 0x0000F800 greenmask: 0x000007E0 bluemask: 0x0000001F alphamask: 0 redshift: 16 greenshift: 21 blueshift: 27 alphashift: 0 </pre> It should likely be vHidd_StdPixFmt_RGB16_LE This stuff is a bit confusing. The "names" of the stdpixfmts are based on the layout in memory, ignoring endianess. So for example: ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines. The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and stdpixfmt_be.h in rom/hidds/graphics/). With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag. (RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to be accessed as GGGBBBBBRRRRRGGGG). The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31). The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered, the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt->stdpixfmt) already in the system, and if so, it uses the already existing one and does not create a new one. In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt tag list based on that. 15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5 (or swapped) but it's actually still using 16 bit R5G6B5 (or swapped). aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count. But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses in the entry where you have looked up shifts/masks/etc. Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you are running on little endian machine) that matches the pixfmt that its meant to be. 0xAA,0xRR,0xGG,0xBB on little endian (->entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32) 0xBB,0xGG,0xRR,0xAA on little endian (->entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32) 0xAA,0xRR,0xGG,0xBB on big endian (->entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32) 0xBB,0xGG,0xRR,0xAA on big endian (->entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32) it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B. read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment . Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening. The output image looks to have too much green/blue, and very weak red. Kickstart The idea is to minimize amount of archirecture-specific modules to make the user's life easier. So, the kickstart was split into 'base' (which does not contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This way, for example, distribution makers can save up space on CD and make CDs with multiple platform support. Different configuration would load the same base with different BSP's. Next there was some part which is entirely missing on hosted. These are filesystems. Hosted ports do not need them to boot up, so on hosted they are left out. At the other hand, they are also architecture-agnostic. So i put them into 'FS' package (standing for 'filesystem'). USB Poseidon is one more big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run on retro PCs without USB). Personally i have one. Again, Poseidon is hardware-agnostic (well, there are USB drivers but HCIs are pretty standard). AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code. Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running. Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong. Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side. Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode & switching modes once it's up and running. Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup. * Model A and B limited to 150 mA per port. * Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub. Implementing the hardware driver that Poseidon uses to interact with the USB components. Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the "virtual" root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals. The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”). There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg]. The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code. The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port). Probably only need provision of relevant changes to dwc_common_port. Other things to consider.... * Provision of necessary headers to get it to compile * Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) ) * Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start. the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB. Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have "prefixed" it with the real location of uncached RAM and booted AROS once again. Trident saw this: Product : Hub: Vdr=0424/PID=9514 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 9 SubClass : 0 DevProto : 2 VendorID : 1060 ProductID : 38164 DevVers : 0200 and this: Product : Vendor: Vdr=0424/PID=EC00 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 255 SubClass : 0 DevProto : 1 VendorID : 1060 ProductID : 60416 DevVers : 0200 and even this: Product : Hub: Vdr=0424/PID=9514 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 9 SubClass : 0 DevProto : 2 VendorID : 1060 ProductID : 38164 DevVers : 0200 What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;) So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. [http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio] Audio The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI. HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface. Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. [https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures Analogue audio Audio over HDMI rev 1.3 & 1.4 Ethernet 10/100 BaseT Ethernet RJ45 socket GPIO GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins) Probably a resource rather than a device... Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p GPU graphics with 2D and 3D acceleration Sadly none yet for 32bit but for 64bit... Miscellanous hdmi issues Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there. You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal. If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to "set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode Do not set hdmi_safe=1 as that overrides many of the previous options. Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA. If you see a problem with the red colour - either absent, or interference - then try a boost composite video changing the RCA cable, then the composite port worked out of the box Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't? Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat What's the result? Put back config.txt What's the result? for PAL mode sdtv_mode=2 dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected <pre> # NOOBS Auto-generated Settings: #hdmi_force_hotplug=1 #config_hdmi_boost=4 #overscan_left=24 #overscan_right=24 #overscan_top=16 #overscan_bottom=16 #disable_overscan=0 start_x=1 gpu_mem=128 </pre> tvservice -c "PAL 4:3" <pre> /opt/vc/bin/tvservice -s or tvservice -s state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive /opt/vc/bin/tvservice -m CEA Group CEA has 1 modes: (native) mode 16: 1920x1080 @ 60 Hz, progressive /opt/vc/bin/tvservice -m DMT Group DMT has 0 modes: </pre> sudo amixer cset numid=3 1 forces the audio to the headphone jack, even with the HDMI video output plugged in config.txt the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others. What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground. The wiring for the 4 pole are: TIP (LEFT AUDIO CHANNEL) RING 1 (RIGHT AUDIO CHANNEL) RING 2 (GROUND/EARTH) RING 3 BASE/SLEEVE (VIDEO) YELLOW Most Apple based Players and the Microsoft Zune (TM) are wired this way. Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug. Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one. External devices * Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&nbsp;nm, peak at 880&nbsp;nm and trails off at 940&nbsp;nm wavelengths * Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - * Branded WIFI usb BCM43143 dongle N.B. dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles. It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board. the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible. currently the only supported sensor is OV5647 and IMX219. The linux drivers are all in the firmware blob, else you'd be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. Static electricity maybe an issue for the camera module and slightly less for the pi board. == References == ===Good sites to visit=== *[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] *[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] *[https://rpilocator.com/ RPiLocator] Linux only *[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] *[https://dietpi.com/ DietPi] *[http://www.tinycorelinux.net/ports.html piCore] *[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] *[https://github.com/armbian/build Armbian] *[ FydeOS] *[ TwisterOS based on ChromiumOS] *[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] *[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] *[ PiMiga for pi4 and pi5] *[ amibian for pi2 and pi3] *[ retropie pi1 and 2] Other alternative lighter smaller than Pi OS *[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] *[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4] *[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] *[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] *[https://github.com/stevereaver/uaos uaOS with Emu68k] *[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] *[ HaikuOS] *[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] *[https://github.com/maxnet/berryboot berryboot] *[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc [https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] *Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested *Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested *Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested *Black DeskPi Super6C Cluster Mini-ITX Board - untested *[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 *Green BentoIO CMX0 - untested *Box EDATec ED-CLAWBOX - untested *Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested *Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested *Box Waveshare [ CM5-POE-BOX-A] - untested *Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested *Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested *Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested *[https://carboncomputers.us/products/pi-flux piFlux] *[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - *Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested *Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested *Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested *Purple Pi Hut Cytron CM4 Maker Board - untested *Black DeskPi Super6C Cluster Mini-ITX Board - untested *[ KubeSail PiBox mini 2] *Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested *[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs *Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted *Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 *Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' *Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested *Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better *Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs *Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob *[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested *[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested *[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed *[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3" HD 1366 x 768 display, small touchpad, *[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS *[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor *[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 <pre> 2008 Trustees collected for Foundation 2009 Pi Foundation charity status gained 2010 2011 First Raspberry prototypes 2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835 2012 First million sold - more than the 10,000 original planned and anticipated 2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 2013 Over two million sold 2014 Over three million sold 2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 2015 Over four million first gen pis sold 2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 2016 Pi0 1.3 released with camera csi connector 2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 2015 Over a million pi2s sold 2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 2016 PIs total over 10 million worldwide 2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 2017 12 million pis sold in total 2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 2019 Over 15 million sold 2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge 2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board CM4101000 1Gb RAM Lite SOM CM4102000 2GB RAM Lite CM4104000 4GB RAM Lite CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules CM4104032 4GB RAM 32GB emmc CM4108000 8GB RAM Lite CM4008016 8GB RAM 16Gb eMMc 2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - CM4S01000 1GB RAM Lite CM4S01008 1GB RAM 8GB eMMC Flash CM4S02000 2GB RAM Lite CM4S04000 4GB RAM Lite CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 CM4S08000 8GB RAM Lite 2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 2021-48 Raspberry Pi 4 model B v1.5 2GB 2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 2024 Pi 5 2GB DDR4 version uses BCM2712D0 2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 2024 Pi 5 v1.1 2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board CM5004000 04GB RAM 0GB eMMC Lite CM5008000 08GB RAM 0GB eMMC Lite CM5016000 16GB RAM 0GB eMMC Lite 2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 2025 Pi5 1GB DDR4 announced 2022 PiOS linux goes 64bit 2024 Pi Trading IPO stockmarket stock exchange listing 2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom 2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 2026 Late July daily 64bit Pi3 LE little endian builds start 2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 2026 2027 2028 Pi 6 </pre> The vcgencmd can be used to inspect and dump the current system configuration. vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called "the firmware". Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc *spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid javascript] [https://github.com/6pac/SlickGrid SlickGrid typescript] [https://github.com/jspreadsheet/ce jspreadsheet ce] probably without xlsx support *presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support *ai office [https://github.com/dream-num/univer/ univer], [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] *weather [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast], [https://github.com/kaushalsahu07/weather weather needs API key], ==Future== [https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2], [https://github.com/Joshua-Riek/armbian-build Linux Armbian builds for old mobile devices], [], [https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], [https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], [ ytdl], [https://github.com/golddominik893/liberatube liberatube] [https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], {{BookCat}} lzmrb7egktmpgrd0jl2wh6lxzll1cfu 4679801 4679794 2026-11-03T14:52:09Z Jeff1138 301139 4679801 wikitext text/x-wiki {{ArosNav}} [[#Native]] [[#Hosted]] [[#Build]] [[#Hardware]] [[#References]] [[#Future]] ==Introduction== [[File:Scalos00.png|thumb|Scalos on Aros Pi3b]] Aros aims to cover Pi 3 to 5 512Mb+ RAM Options to boot from using a good power source to prevent the yellow lightning symbol. *With Pi3b+ the max you can get is 5.1V 2.5A with micro usb. *With Pi4 5.1V 3A with usb-c *With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c * Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] * Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] * Pi 5 - Quad A76 64bit ARMv8 and RP1 "southbridge" with VideoCore 7 D0 (rev1.1) - untested * Pi 5 - Quad A76 64bit ARMv8 and RP1 "southbridge" with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested * Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - * Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 * Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling * Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], * Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible * Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible * Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible ===Native=== * 2013-03 Kalamatee starts work * 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb * 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi] * 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] * 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5] * 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM] ====64bit==== '''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository] '''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 64bit build works well on a single core LE little endian. [https://aros.sourceforge.io/nightly1.html raspi-aarch64-smp-system multicore is available] [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] *Pi500+ untested usb3 booting or nvme ssd *Pi500 untested usb3 booting *Pi5 untested usb3 booting *Pi400 boots with '''USB3''' port based sata3 ssd *Pi4 untested (may need eeprom update from PiOS or Pi SD Imager) *Pi 3 B+ is pre-configured for USB sata3 boot - untested *Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card Speed write wise (top faster) <pre> *NVME Pi5 untested >1000MB/sec or faster if matched correctly *Sata3 ssd 500MB/sec *SD V90 90MB/sec 4K maybe 8K *SD V60 60MB/sec 1080p *SD U3 V30 30MB/sec 720p *SD C10 U1 V10 A1 A2 10MB/sec minimum should be used now *SD C06 6MB/sec *SD C04 4MB/sec </pre> As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -> View -> All files Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. Esc escape key usually closes open windows even the desktop In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. Like most amiga like OSs the audio and networking need to be setup manually Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++ or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off *if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again *...waiting for an address - Disconnect and try Connect Until, Connected to <router> - 192.168.x.x For lan ethernet port, please use Network prefs and the following hardware is *lan9514 Pi3b Pi2 not supported at the moment *lan7515 Pi3b+ type into Device usblan78xx.device as net0: remove other device(s) *bcmgenet Pi4 Pi400 choose for Device bcmgenet.device *cdnsgem Pi5 Pi500 Pi500+ RP1 i/o for cadencegem (network prefs may forget random information when rebooted) Summary <pre> ̽*Pi3a̹+ wifi works, *Pi3b ethernet not supported, usb ethernet not working but wifi prefs setup works *Pi3b+ wifi working and ethernet works *Pi4 untested *Pi400 wifi and ethernet untested *Pi5 wifi and ethernet untested *Pi500 wifi and ethernet untested *Pi500+ wifi works </pre> Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. [http://archives.arosworld.org/index.php?function=browse&cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT). Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555. You may have to delete the cache (Menu -> Page -> Delete cache) to fully retest big Amelinium updates or free up space. Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly DNS lookup failed... close browser and reboot and setup wifi again - repeat until it works again youtube video and audio - js button for javascript must be on/shaded - Settings -> Soundoutput - AHI Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect up to 480p (wifi) and up to 720p (ethernet). Pi4 expect (wifi) (ethernet). If no separate audio stream error - set settings -> Video quality to 360p or lower as Youtube has a fallback mode at that level https://t.me/s/channel_name for Telegram public messages from [https://t.me/s/AROS_official AROS_official] [https://t.me/s/vamped_amiga vamped_amiga] [https://t.me/s/demoscenecracktros demoscenecracktros] *art local js apps like dpaint.js There is normally no Bluetooth support for most amiga like OSs but that has changed recently [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] *Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W *Bluetooth 4.2 BCM4345C0.hcd Pi3B+, Pi4 *Bluetooth 5.0 BCM4345C5.hcd Pi4B rev, CM4 and maybe Pi5 and CM5 <pre> *bthid keyboard mouse support *btserial serial *btpan short range wireless connecting devices </pre> Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g. date 24-Dec-2026 23:59:59 but this will need to be done again after every reset/power off. Maybe hardware [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. USB classes support from Prefs/Trident is still work in process *usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w *[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&file=audio/misc/timidity.lha timidity], Regarding 680x0 emulation, there are several options that could be considered but most not fully implemented *[https://github.com/kaffeine1/kaffeine kaffeine m68k with Amiga system OS fɹiendly calls going to Aros ones] *[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones *[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games *[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] *[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] [https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] Some exceptions: *Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used *The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V *For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15). With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented. Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi. In the shell (Cntrl + C to end) GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' *PIN -- (Required) Target GPIO pin number (e.g. 12). *SET -- Set pin output value to 0 (LOW) or 1 (HIGH). *GET -- Read and print current digital input level (0 or 1). *MODE -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate). *PULL -- Configure pull resistor: NONE, UP, DOWN. EXAMPLES <pre> GPIO 12 MODE OUT GPIO 12 SET 1 GPIO 12 GET GPIO 13 PULL UP </pre> [https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&pid=13954#post_13954 discussion] Youtube [https://www.youtube.com/watch?v=8dZwGkUKAmA Pi3A̟+ (plus) with smp build and PiAROS], [], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], [], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], [], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], [], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], [https://www.youtube.com/watch?v=nHt_k_QkHe0 AmiWest 2026 Day 1], [https://www.youtube.com/watch?v=nA2fnaOt1Ik Amiwest 2026 Day 2], [https://www.youtube.com/watch?v=zQM4CD64xDE&t=612s&pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... {| class="wikitable sortable" width="90%" ! width="10%" |Pi ! width="10%" |Single Core 2D ! width="10%" |Single Core 3D ! width="10%" |Single Core 3D ! width="10%" |SMP 2D ! width="10%" |SMP 3D ! width="10%" |SMP 3D ! width="35%" |Comments |- | <!--Pi-->Pi3 | <!--Single Core 2D--> | <!--Single Core 3D--> | <!--Single Core 3D--> | <!--SMP 2D--> | <!--SMP 3D--> | <!--SMP 3D--> | <!--Comments--> |- |} ==== 32bit ==== For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD ===Hosted=== AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon Macs] [https://github.com/jonx/Macaros early alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&pid=13910#post_13910 here] with [https://github.com/pomaros pomaros]. There is a [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2076&highlight=jonx&pid=14193#post_14193 work in progress native Mac Apple silicon M1 M2 M3 version] [http://www.aros.org/snapshots1.html old linux and android hosted 32bit] ==== Hosted ==== =====64bit===== [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&rowstart=80&pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] [https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&rowstart=80 From the Aros Raspberry pi 3 64bit thread] Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources. You will need: - Ubuntu 24.04 or 26.04 - qemu-system-aarch64 installed - Internet connection - rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz) 1) Install prerequisites: sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm 2) Clone sources cd <project-directory> git clone https://github.com/aros-development-team/AROS.git --recurse-submodules 3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have: AROS (the directory with cloned sources) fix-dotdot.py rebuild.sh recreate-sdcard.sh run-qemu.sh update-sdcard.sh 4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64 This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step. 5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64 This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour. 6) Run ./recreate-sdcard.sh This will create an sdcard.img file with contents of previous step. 7) Run ./run-qemu.sh This will start QEMU with SD card image and ROM images. It will boot into AROS. =====32bit===== Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013] ../AROS/configure --target=linux-armhf --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux) *armel - many of the "android" machines require since the entire OS is made for soft float VFP. *armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP) Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI. Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets. *needs an AROS code compiler for ARM target *as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes. with—disable-crosstools $AROS_CC is always a wrapper around $KERNEL_CC ? If so, this is wrong for some ports. This can break Darwin, Windows and Android port. Yes, Android port will build. And even work. But it's not good because the port will not be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example: <pre> enum test {foo, bar}; enum test testvar; </pre> sizeof(testvar) will be equal to sizeof(int) in GNUEABI (Linux and AROS) and sizeof(short) on Android. This affects linking objects from static linklibs, for example. Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts. Android is the same. $KERNEL_CC is incompatible with AROS. compiler=kernel is appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or barebone hardware, if we talk about native). This includes bootstraps, their linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations. No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows, Android) this is not true any more, and compiler=kernel is never going to work. If you want to compile your AROS module against host OS includes, append the following to USER_INCLUDES (or USER_CFLAGS, this is effectively the same): -isystem $(GENINCDIR) $(KERNEL_INCLUDES) $(KERNEL_INCLUDES) expands to: -isystem <your_os_includes> -isystem <host_OS_gcc_private_includes> -nostdinc This makes AROS compiler adhering to host OS APIs. If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH). Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one. Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types. Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but "./configure --target=raspi-armhf" is enough to start, then "make arosboot-raspi" will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc). It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output. *armel = typically Debian 6, Ubuntu Maverick, Android, *armhf = typically Debian 7, Debian 8, Ubuntu Precise, Cross-compiling Ubuntu ARM softfp <pre> sudo sh echo 'foreign-architecture armel' >>/etc/dpkg/dpkg.cfg.d/multiarch echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' >/etc/apt/sources.list.d/armel.list apt-get update apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel </pre> <pre> ./configure --target=linux-arm --x-includes=/usr/include \ --enable-includes=/usr/arm-linux-gnueabi/include </pre> Cross-compiling Ubuntu ARM hard-float <pre> sudo sh echo 'foreign-architecture armhf' >>/etc/dpkg/dpkg.cfg.d/multiarch echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' >/etc/apt/sources.list.d/armhf.list apt-get update apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf </pre> <pre> ./configure --target=linux-armhf --x-includes=/usr/include \ --enable-includes=/usr/arm-linux-gnueabihf/include </pre> Now, the AROS build is configured properly and all you need to do is: make ==Build== ===64bit=== [https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] ===32bit=== # download/checkout the source someplace, e.g. /build/AROS-Src/ # make a directory to store external sources AROS downloads, e.g. /build/Ports # make a build directory, e.g. /build/aros-raspi-armhf # cd into the build dir, configure, and then run make -: <pre> >cd /build/aros-raspi-armhf >/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports >make >make arosboot-raspi </pre> then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it. You should then be able to boot the sdcard on your RasPi. The current W.I.P tree to svn. it can be built as follows .. <pre> ./configure --target=raspi-armhf make arosboot-raspi </pre> That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder. NB - if you have a Linux/other install, backup the existing config.txt first arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console "emulation" via code pinched from our libbootconsole), kernel.resource, and exec.library arosraspi.rom contains all the other components needed to boot AROS. The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom). the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO) Help building AROS hosted on Linux ARM Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device. Compilation stops after build libpopupmenu.a and trying to build libatomic have this error: <pre> Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic configure: WARNING: unrecognized options: --disable-nls, --without-x checking for --enable-version-specific-runtime-libs... no checking for --enable-generated-files-in-srcdir... no checking build system type... arm-unknown-linux-gnu checking host system type... arm-unknown-aros checking target system type... arm-unknown-aros checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc checking whether the C compiler works... no configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic': configure: error: C compiler cannot create executables See config.log' for more details make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77 [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512 [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory make[1]: *** [Makefile:361: linklibs-libatomic] Error 10 make: *** [Makefile:183: crosstools] Error 2 </pre> looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi so do make linklibs-aeabi-arm-quick and the missing lib was built. now the next stop is at fatal error: bits/libc-header-start.h: No such file or directory and fatal error: sys/cdefs.h: No such file or directory in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed? fixed with adding -I/usr/include/arm-linux-gnueabihf to where is missing on mmakefiles like USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES) P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles. Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again. My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a "template" to compare to native compilation under arm linux. Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild). The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC. For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script. Thanks compilation now go forward...changed target.cfg under "toolchain-core-armhf-build/bin/linux-arm/gen/config" and do make on "toolchain-core-armhf-build" dir. Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there: #MM- linklibs-armhd : libklibs-aeabi-arm Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this. Try adding this line (and the variant "linklibs-armhf" instead of hd) but it did not solve the automatic building of the missing lib. I must do "linklibs-aeabi-arm-quick". Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case. With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with "cannot find -laeabi " so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok. == Hardware == ===64bit=== ====BCM2712==== With the Pi5 Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. *Raspberry Pi M.2 HAT+ Expansion Board *Geekworm X1001 PCIe to M.2 Key-M NVMe *Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 *Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 *Hat+ Gen2 Gen3 Nvme *GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2 * *2024 RPI AI HAT - Hailo 20TOPs no LLMs *2026 RPI AI HAT+ 2 - Hailo 40TOPs slightly better? [https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi] *Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor *Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor *Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1 HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates ====BCM2711==== With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 the 2711b line used more power when idle, compared to the 2711c *2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues *2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design *Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE *[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles. The instruction encoding for the QPUs is different, but the core instructions are the same. Instructions for packed 8 bit int math has been dropped, along with most of the pack modes. Instructions for packed 16bit float math has been added (2 floats at in a single operation) With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register. the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of "one read port, one write port" to one "two read ports, one write port" block) The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. *vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers. *vc5 added a four thread per QPU mode, with 16 registers per thread. *vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads. With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer) A MMU, allowing a much simpler/faster kernel driver. Many more texture formats, framebuffer formats. h264/x264 [https://github.com/aros-development-team/AROS/commit/caecd66a9508acb0e9ef0a07169a14c33007b208 VideoCore hardware decoding through VCHIQ/MMAL (Pi 1–4)], H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1 HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates All the features needed for opengl es 3.0 Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised Possible maximum performance <pre> VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s </pre> Faster LPDDR4 memory. ====BCM2837==== With the Pi3 * Broadcom BCM43438 chip provides 2.4&nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. [https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. ===32bit=== === Core Kernel === ====BCM2708(family)==== which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM) *Framebuffer (fb) using mailbox *IRQ scheduler, etc *Arasan based SD Card controller *Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&view=article&id=106:rasperry-pi-usb-controller&catid=45:raspberry-pi&Itemid=54 Unofficial DOCS pdf], [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], *[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip *CMOS RAM *VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc *Audio Driver *Serial Peripheral Interface Bus (SPI) *[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers] *I2S *Universal Asynchronous Receiver Transmitter (UART) *[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO] BCM2836 * For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board *[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features], Implemented so far... # Modify the configure system so that it correctly builds for the arm hardware float raspi target. # Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display. # Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function. # Implemented serial debug support # Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc) # Implemented a timer.device to utilise the hardware timers. # Implemented a very basic gfx driver to expose the hardware's framebuffer. # Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media. # Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The "rom" image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot. # Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else. # fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi .. Improvements... # Implement a USB chipset driver "OR" finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the "virtual" hub code in place to represent the raspi's USB port (from poseidons p.o.v) # Implement a driver for the USB NIC (a few weeks - depends on USB above) # Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI] # fix syscall bug in the current raspi kernel code # Graphics depend on having a decent "bcmdma.resource" implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for "blitting". # [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] # [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 # The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate. Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition. The boot sequence carries out several pre-boot tasks *On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf *The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it *configures the memory split for the CPU and GPU *reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings) *loads the “kernel.img” file, again from the same partition *activates the CPU to begin executing the loaded kernel image The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU. RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named "kernel.img" at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem) Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf. You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling. At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules <pre> ? - alias for 'help' mtest - simple RAM test autoscr - run script from memory base - print or set address offset bbm - BBM sub-system bdinfo - print Board Info structure boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootm - boot application image from memory bootp - boot image via network using BootP/TFTP protocol cmp - memory compare coninfo - print console devices and information cp - memory copy crc32 - checksum calculation echo - echo args to console fatinfo - print information about filesystem fatload - load binary file from a dos filesystem fatls - list files in a directory (default /) go - start application at address 'addr' help - print online help iminfo - print header information for application image itest - return true/false on integer compare jade - loadb - load binary file over serial line (kermit mode) loads - load S-Record file over serial line loady - load binary file over serial line (ymodem mode) loop - infinite loop on address range md - memory display mm - memory modify (auto-incrementing) mtest - simple RAM test mw - memory write (fill) nfs - boot image via network using NFS protocol nm - memory modify (constant address) pci - list and access PCI Configuration Space ping - send ICMP ECHO_REQUEST to network host printenv - print environment variables rarpboot - boot image via network using RARP/TFTP protocol reset - Perform RESET of the CPU run - run commands in an environment variable saveenv - save environment variables to persistent storage saves - save S-Record file over serial line setenv - set environment variables sleep - delay execution for some time tftpboot - boot image via network using TFTP protocol USB - USB sub-system usbboot - boot from USB device version - print monitor version </pre> And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way... u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot. Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1, the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS routed only raw hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt. 1:1 relationship between CPU and hardware interrupts is present only on PC. IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class. PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant to be different, its IRQs are hardware-agnostic, they are plain "Hardware IRQ number X, whatever this means". They are low-level actually, and meaningful only in the context of a particular system. Was that not the transition from irq.hidd to kernel.resource? No. A long time ago there was another hacky bit named INTB_TIMERTICK. It was "abstract timer interrupt", used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea. Can someone please enlighten me a little on how the scheduler is meant to work? Poseidon.library creates its "Poseidon Event Task" during RTF_COLDSTART -> then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example. You miss what happens next... 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch(). 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible: 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run. 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list. My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop. There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures. The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table. The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :) Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this: movw r0, #:lower16:label movt r0, #:upper16:label In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations. There are two options - the first one would be to give up and go back to "fake" executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need. Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. GPU VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU. Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute. The good news about this is that we only need to write our HIDD using the OpenVG API. The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf). That's also the bad news. Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much. It's still probably less difficult and less work, than controlling the GPU directly. The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated. It also has some nice font functions, meaning we can lead into an accelerated text mode later. Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC. If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected. have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled. If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work. L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled. Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics. Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever. I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp). #warning "TODO: lookup optimal mmu table settings for raspi memory" /* Set up an identity-mapping for all 4GB */ for(x = 0; x < 4096; x ++) { pagetable[x] = x<<20 | (0x40002|0x80000|0x010000|0x00C00|0x04); } Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages? Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device). You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached) So .. pagetable[x] = x<<20 | 2; should be enough? No, for RAM you need to change the '| 0x40' to '| 0x80' tell dosboot the correct defaults to use Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead, display drivers should auto-install themselves during own initialization phase. I. e. detect hardware=>instantiate itself. This should make things way simpler. With this approach you only need to add the driver into KS image to get the device autobooted. No hardcoded stuff. Currently VESA and VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it. they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context). AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM marked as chip. BTW, is the video processing code you mention CPU code or GPU code? Also, IIRC we have support for "external memory allocators". Perhaps that's what we need for the allocation of GPU RAM through the mailbox. All hosted and x86 native ports should use proper context formats. trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET). Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units. The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ. Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port? It provides a before-anything-else shell prompt on the serial port. You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource. You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs. So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work. Also make sure to add shell.resource and shellcommands.resource for this. That should have done it. If you set "#define DEBUG 1" in arch/all-native/econsole/econsole.c, do you get any additional serial output? have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display? Im assuming it exposes a fake filesystem that tricks aros into booting? The contents of which are: ECON:AROS.boot Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm. To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen. Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks). have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress.. was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression. Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks. Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right) The _LE versions are for when you have endian swapping taking place. If the graphics are the same endian as the CPU, no swapping should occur. I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian. It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary. They were both little-endian. The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode). What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest? Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems? You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it. So, AROS creates the framebuffer bitmap (verified this) -> so surely it should be capable of then rendeing into it? I don't actually create the framebuffer "bitmap object" myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback. In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) So far have -: vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object. vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer, vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. RasPi has to speak to the "operating system" which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls. The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required. The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied. The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds). must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. For 2D dma, set TDMODE, and the spec says "interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer." so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data. The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out). openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits. Actually MEMF_CHIP has to present, for historical reasons. This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP. Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting. As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there. struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi. AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol. <pre> redmask: 0x0000F800 greenmask: 0x000007E0 bluemask: 0x0000001F alphamask: 0 redshift: 16 greenshift: 21 blueshift: 27 alphashift: 0 </pre> It should likely be vHidd_StdPixFmt_RGB16_LE This stuff is a bit confusing. The "names" of the stdpixfmts are based on the layout in memory, ignoring endianess. So for example: ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines. The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and stdpixfmt_be.h in rom/hidds/graphics/). With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag. (RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to be accessed as GGGBBBBBRRRRRGGGG). The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31). The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered, the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt->stdpixfmt) already in the system, and if so, it uses the already existing one and does not create a new one. In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt tag list based on that. 15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5 (or swapped) but it's actually still using 16 bit R5G6B5 (or swapped). aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count. But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses in the entry where you have looked up shifts/masks/etc. Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you are running on little endian machine) that matches the pixfmt that its meant to be. 0xAA,0xRR,0xGG,0xBB on little endian (->entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32) 0xBB,0xGG,0xRR,0xAA on little endian (->entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32) 0xAA,0xRR,0xGG,0xBB on big endian (->entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32) 0xBB,0xGG,0xRR,0xAA on big endian (->entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32) it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B. read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment . Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening. The output image looks to have too much green/blue, and very weak red. Kickstart The idea is to minimize amount of archirecture-specific modules to make the user's life easier. So, the kickstart was split into 'base' (which does not contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This way, for example, distribution makers can save up space on CD and make CDs with multiple platform support. Different configuration would load the same base with different BSP's. Next there was some part which is entirely missing on hosted. These are filesystems. Hosted ports do not need them to boot up, so on hosted they are left out. At the other hand, they are also architecture-agnostic. So i put them into 'FS' package (standing for 'filesystem'). USB Poseidon is one more big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run on retro PCs without USB). Personally i have one. Again, Poseidon is hardware-agnostic (well, there are USB drivers but HCIs are pretty standard). AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code. Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running. Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong. Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side. Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode & switching modes once it's up and running. Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup. * Model A and B limited to 150 mA per port. * Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub. Implementing the hardware driver that Poseidon uses to interact with the USB components. Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the "virtual" root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals. The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”). There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg]. The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code. The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port). Probably only need provision of relevant changes to dwc_common_port. Other things to consider.... * Provision of necessary headers to get it to compile * Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) ) * Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start. the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB. Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have "prefixed" it with the real location of uncached RAM and booted AROS once again. Trident saw this: Product : Hub: Vdr=0424/PID=9514 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 9 SubClass : 0 DevProto : 2 VendorID : 1060 ProductID : 38164 DevVers : 0200 and this: Product : Vendor: Vdr=0424/PID=EC00 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 255 SubClass : 0 DevProto : 1 VendorID : 1060 ProductID : 60416 DevVers : 0200 and even this: Product : Hub: Vdr=0424/PID=9514 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 9 SubClass : 0 DevProto : 2 VendorID : 1060 ProductID : 38164 DevVers : 0200 What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;) So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. [http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio] Audio The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI. HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface. Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. [https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures Analogue audio Audio over HDMI rev 1.3 & 1.4 Ethernet 10/100 BaseT Ethernet RJ45 socket GPIO GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins) Probably a resource rather than a device... Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p GPU graphics with 2D and 3D acceleration Sadly none yet for 32bit but for 64bit... Miscellanous hdmi issues Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there. You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal. If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to "set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode Do not set hdmi_safe=1 as that overrides many of the previous options. Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA. If you see a problem with the red colour - either absent, or interference - then try a boost composite video changing the RCA cable, then the composite port worked out of the box Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't? Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat What's the result? Put back config.txt What's the result? for PAL mode sdtv_mode=2 dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected <pre> # NOOBS Auto-generated Settings: #hdmi_force_hotplug=1 #config_hdmi_boost=4 #overscan_left=24 #overscan_right=24 #overscan_top=16 #overscan_bottom=16 #disable_overscan=0 start_x=1 gpu_mem=128 </pre> tvservice -c "PAL 4:3" <pre> /opt/vc/bin/tvservice -s or tvservice -s state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive /opt/vc/bin/tvservice -m CEA Group CEA has 1 modes: (native) mode 16: 1920x1080 @ 60 Hz, progressive /opt/vc/bin/tvservice -m DMT Group DMT has 0 modes: </pre> sudo amixer cset numid=3 1 forces the audio to the headphone jack, even with the HDMI video output plugged in config.txt the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others. What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground. The wiring for the 4 pole are: TIP (LEFT AUDIO CHANNEL) RING 1 (RIGHT AUDIO CHANNEL) RING 2 (GROUND/EARTH) RING 3 BASE/SLEEVE (VIDEO) YELLOW Most Apple based Players and the Microsoft Zune (TM) are wired this way. Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug. Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one. External devices * Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&nbsp;nm, peak at 880&nbsp;nm and trails off at 940&nbsp;nm wavelengths * Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - * Branded WIFI usb BCM43143 dongle N.B. dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles. It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board. the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible. currently the only supported sensor is OV5647 and IMX219. The linux drivers are all in the firmware blob, else you'd be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. Static electricity maybe an issue for the camera module and slightly less for the pi board. == References == ===Good sites to visit=== *[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] *[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] *[https://rpilocator.com/ RPiLocator] Linux only *[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] *[https://dietpi.com/ DietPi] *[http://www.tinycorelinux.net/ports.html piCore] *[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] *[https://github.com/armbian/build Armbian] *[ FydeOS] *[ TwisterOS based on ChromiumOS] *[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] *[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] *[ PiMiga for pi4 and pi5] *[ amibian for pi2 and pi3] *[ retropie pi1 and 2] Other alternative lighter smaller than Pi OS *[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] *[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4] *[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] *[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] *[https://github.com/stevereaver/uaos uaOS with Emu68k] *[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] *[ HaikuOS] *[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] *[https://github.com/maxnet/berryboot berryboot] *[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc [https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] *Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested *Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested *Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested *Black DeskPi Super6C Cluster Mini-ITX Board - untested *[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 *Green BentoIO CMX0 - untested *Box EDATec ED-CLAWBOX - untested *Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested *Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested *Box Waveshare [ CM5-POE-BOX-A] - untested *Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested *Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested *Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested *[https://carboncomputers.us/products/pi-flux piFlux] *[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - *Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested *Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested *Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested *Purple Pi Hut Cytron CM4 Maker Board - untested *Black DeskPi Super6C Cluster Mini-ITX Board - untested *[ KubeSail PiBox mini 2] *Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested *[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs *Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted *Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 *Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' *Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested *Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better *Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs *Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob *[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested *[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested *[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed *[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3" HD 1366 x 768 display, small touchpad, *[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS *[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor *[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 <pre> 2008 Trustees collected for Foundation 2009 Pi Foundation charity status gained 2010 2011 First Raspberry prototypes 2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835 2012 First million sold - more than the 10,000 original planned and anticipated 2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 2013 Over two million sold 2014 Over three million sold 2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 2015 Over four million first gen pis sold 2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 2016 Pi0 1.3 released with camera csi connector 2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 2015 Over a million pi2s sold 2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 2016 PIs total over 10 million worldwide 2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 2017 12 million pis sold in total 2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 2019 Over 15 million sold 2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge 2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board CM4101000 1Gb RAM Lite SOM CM4102000 2GB RAM Lite CM4104000 4GB RAM Lite CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules CM4104032 4GB RAM 32GB emmc CM4108000 8GB RAM Lite CM4008016 8GB RAM 16Gb eMMc 2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - CM4S01000 1GB RAM Lite CM4S01008 1GB RAM 8GB eMMC Flash CM4S02000 2GB RAM Lite CM4S04000 4GB RAM Lite CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 CM4S08000 8GB RAM Lite 2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 2021-48 Raspberry Pi 4 model B v1.5 2GB 2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 2024 Pi 5 2GB DDR4 version uses BCM2712D0 2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 2024 Pi 5 v1.1 2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board CM5004000 04GB RAM 0GB eMMC Lite CM5008000 08GB RAM 0GB eMMC Lite CM5016000 16GB RAM 0GB eMMC Lite 2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 2025 Pi5 1GB DDR4 announced 2022 PiOS linux goes 64bit 2024 Pi Trading IPO stockmarket stock exchange listing 2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom 2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 2026 Late July daily 64bit Pi3 LE little endian builds start 2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 2026 2027 2028 Pi 6 </pre> The vcgencmd can be used to inspect and dump the current system configuration. vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called "the firmware". Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc *spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid javascript] [https://github.com/6pac/SlickGrid SlickGrid typescript] [https://github.com/jspreadsheet/ce jspreadsheet ce] probably without xlsx support *presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support *ai office [https://github.com/dream-num/univer/ univer], [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] *weather [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast], [https://github.com/kaushalsahu07/weather weather needs API key], ==Future== [https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2], [https://github.com/Joshua-Riek/armbian-build Linux Armbian builds for old mobile devices], [], [https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], [https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], [ ytdl], [https://github.com/golddominik893/liberatube liberatube] [https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], {{BookCat}} sqtzvltgfct4rg0chkqfn0r8wnni1rk 4679808 4679801 2026-11-03T15:37:36Z Jeff1138 301139 4679808 wikitext text/x-wiki {{ArosNav}} [[#Native]] [[#Hosted]] [[#Build]] [[#Hardware]] [[#References]] [[#Future]] ==Introduction== [[File:Wanderer00.png|thumb|Wanderer on Aros Pi3b]] [[File:Scalos00.png|thumb|Scalos on Aros Pi3b]] [[File:DOpus5Magellan00.png|thumb|DOpus5 Magellan on Aros Pi3b]] Aros aims to cover Pi 3 to 5 512Mb+ RAM Options to boot from using a good power source to prevent the yellow lightning symbol. *With Pi3b+ the max you can get is 5.1V 2.5A with micro usb. *With Pi4 5.1V 3A with usb-c *With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c * Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] * Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] * Pi 5 - Quad A76 64bit ARMv8 and RP1 "southbridge" with VideoCore 7 D0 (rev1.1) - untested * Pi 5 - Quad A76 64bit ARMv8 and RP1 "southbridge" with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested * Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - * Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 * Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling * Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], * Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible * Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible * Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible ===Native=== * 2013-03 Kalamatee starts work * 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb * 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi] * 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] * 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5] * 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM] ====64bit==== '''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository] '''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 64bit build works well on a single core LE little endian. [https://aros.sourceforge.io/nightly1.html raspi-aarch64-smp-system multicore is available] [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] *Pi500+ untested usb3 booting or nvme ssd *Pi500 untested usb3 booting *Pi5 untested usb3 booting *Pi400 boots with '''USB3''' port based sata3 ssd *Pi4 untested (may need eeprom update from PiOS or Pi SD Imager) *Pi 3 B+ is pre-configured for USB sata3 boot - untested *Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card Speed write wise (top faster) <pre> *NVME Pi5 untested >1000MB/sec or faster if matched correctly *Sata3 ssd 500MB/sec *SD V90 90MB/sec 4K maybe 8K *SD V60 60MB/sec 1080p *SD U3 V30 30MB/sec 720p *SD C10 U1 V10 A1 A2 10MB/sec minimum should be used now *SD C06 6MB/sec *SD C04 4MB/sec </pre> As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -> View -> All files Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. Esc escape key usually closes open windows even the desktop In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. Like most amiga like OSs the audio and networking need to be setup manually Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++ or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off *if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again *...waiting for an address - Disconnect and try Connect Until, Connected to <router> - 192.168.x.x For lan ethernet port, please use Network prefs and the following hardware is *lan9514 Pi3b Pi2 not supported at the moment *lan7515 Pi3b+ type into Device usblan78xx.device as net0: remove other device(s) *bcmgenet Pi4 Pi400 choose for Device bcmgenet.device *cdnsgem Pi5 Pi500 Pi500+ RP1 i/o for cadencegem (network prefs may forget random information when rebooted) Summary <pre> ̽*Pi3a̹+ wifi works, *Pi3b ethernet not supported, usb ethernet not working but wifi prefs setup works *Pi3b+ wifi working and ethernet works *Pi4 untested *Pi400 wifi and ethernet untested *Pi5 wifi and ethernet untested *Pi500 wifi and ethernet untested *Pi500+ wifi works </pre> Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. [http://archives.arosworld.org/index.php?function=browse&cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT). Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555. You may have to delete the cache (Menu -> Page -> Delete cache) to fully retest big Amelinium updates or free up space. Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly DNS lookup failed... close browser and reboot and setup wifi again - repeat until it works again youtube video and audio - js button for javascript must be on/shaded - Settings -> Soundoutput - AHI Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect up to 480p (wifi) and up to 720p (ethernet). Pi4 expect (wifi) (ethernet). If no separate audio stream error - set settings -> Video quality to 360p or lower as Youtube has a fallback mode at that level https://t.me/s/channel_name for Telegram public messages from [https://t.me/s/AROS_official AROS_official] [https://t.me/s/vamped_amiga vamped_amiga] [https://t.me/s/demoscenecracktros demoscenecracktros] *art local js apps like dpaint.js There is normally no Bluetooth support for most amiga like OSs but that has changed recently [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] *Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W *Bluetooth 4.2 BCM4345C0.hcd Pi3B+, Pi4 *Bluetooth 5.0 BCM4345C5.hcd Pi4B rev, CM4 and maybe Pi5 and CM5 <pre> *bthid keyboard mouse support *btserial serial *btpan short range wireless connecting devices </pre> Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g. date 24-Dec-2026 23:59:59 but this will need to be done again after every reset/power off. Maybe hardware [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. USB classes support from Prefs/Trident is still work in process *usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w *[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&file=audio/misc/timidity.lha timidity], Regarding 680x0 emulation, there are several options that could be considered but most not fully implemented *[https://github.com/kaffeine1/kaffeine kaffeine m68k with Amiga system OS fɹiendly calls going to Aros ones] *[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones *[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games *[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] *[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] [https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] Some exceptions: *Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used *The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V *For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15). With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented. Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi. In the shell (Cntrl + C to end) GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' *PIN -- (Required) Target GPIO pin number (e.g. 12). *SET -- Set pin output value to 0 (LOW) or 1 (HIGH). *GET -- Read and print current digital input level (0 or 1). *MODE -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate). *PULL -- Configure pull resistor: NONE, UP, DOWN. EXAMPLES <pre> GPIO 12 MODE OUT GPIO 12 SET 1 GPIO 12 GET GPIO 13 PULL UP </pre> [https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&pid=13954#post_13954 discussion] Youtube [https://www.youtube.com/watch?v=8dZwGkUKAmA Pi3A̟+ (plus) with smp build and PiAROS], [], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], [], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], [], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], [], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], [https://www.youtube.com/watch?v=nHt_k_QkHe0 AmiWest 2026 Day 1], [https://www.youtube.com/watch?v=nA2fnaOt1Ik Amiwest 2026 Day 2], [https://www.youtube.com/watch?v=zQM4CD64xDE&t=612s&pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... {| class="wikitable sortable" width="90%" ! width="10%" |Pi ! width="10%" |Single Core 2D ! width="10%" |Single Core 3D ! width="10%" |Single Core 3D ! width="10%" |SMP 2D ! width="10%" |SMP 3D ! width="10%" |SMP 3D ! width="35%" |Comments |- | <!--Pi-->Pi3 | <!--Single Core 2D--> | <!--Single Core 3D--> | <!--Single Core 3D--> | <!--SMP 2D--> | <!--SMP 3D--> | <!--SMP 3D--> | <!--Comments--> |- |} ==== 32bit ==== For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD ===Hosted=== AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon Macs] [https://github.com/jonx/Macaros early alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&pid=13910#post_13910 here] with [https://github.com/pomaros pomaros]. There is a [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2076&highlight=jonx&pid=14193#post_14193 work in progress native Mac Apple silicon M1 M2 M3 version] [http://www.aros.org/snapshots1.html old linux and android hosted 32bit] ==== Hosted ==== =====64bit===== [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&rowstart=80&pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] [https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&rowstart=80 From the Aros Raspberry pi 3 64bit thread] Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources. You will need: - Ubuntu 24.04 or 26.04 - qemu-system-aarch64 installed - Internet connection - rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz) 1) Install prerequisites: sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm 2) Clone sources cd <project-directory> git clone https://github.com/aros-development-team/AROS.git --recurse-submodules 3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have: AROS (the directory with cloned sources) fix-dotdot.py rebuild.sh recreate-sdcard.sh run-qemu.sh update-sdcard.sh 4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64 This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step. 5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64 This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour. 6) Run ./recreate-sdcard.sh This will create an sdcard.img file with contents of previous step. 7) Run ./run-qemu.sh This will start QEMU with SD card image and ROM images. It will boot into AROS. =====32bit===== Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013] ../AROS/configure --target=linux-armhf --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux) *armel - many of the "android" machines require since the entire OS is made for soft float VFP. *armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP) Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI. Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets. *needs an AROS code compiler for ARM target *as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes. with—disable-crosstools $AROS_CC is always a wrapper around $KERNEL_CC ? If so, this is wrong for some ports. This can break Darwin, Windows and Android port. Yes, Android port will build. And even work. But it's not good because the port will not be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example: <pre> enum test {foo, bar}; enum test testvar; </pre> sizeof(testvar) will be equal to sizeof(int) in GNUEABI (Linux and AROS) and sizeof(short) on Android. This affects linking objects from static linklibs, for example. Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts. Android is the same. $KERNEL_CC is incompatible with AROS. compiler=kernel is appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or barebone hardware, if we talk about native). This includes bootstraps, their linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations. No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows, Android) this is not true any more, and compiler=kernel is never going to work. If you want to compile your AROS module against host OS includes, append the following to USER_INCLUDES (or USER_CFLAGS, this is effectively the same): -isystem $(GENINCDIR) $(KERNEL_INCLUDES) $(KERNEL_INCLUDES) expands to: -isystem <your_os_includes> -isystem <host_OS_gcc_private_includes> -nostdinc This makes AROS compiler adhering to host OS APIs. If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH). Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one. Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types. Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but "./configure --target=raspi-armhf" is enough to start, then "make arosboot-raspi" will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc). It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output. *armel = typically Debian 6, Ubuntu Maverick, Android, *armhf = typically Debian 7, Debian 8, Ubuntu Precise, Cross-compiling Ubuntu ARM softfp <pre> sudo sh echo 'foreign-architecture armel' >>/etc/dpkg/dpkg.cfg.d/multiarch echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' >/etc/apt/sources.list.d/armel.list apt-get update apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel </pre> <pre> ./configure --target=linux-arm --x-includes=/usr/include \ --enable-includes=/usr/arm-linux-gnueabi/include </pre> Cross-compiling Ubuntu ARM hard-float <pre> sudo sh echo 'foreign-architecture armhf' >>/etc/dpkg/dpkg.cfg.d/multiarch echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' >/etc/apt/sources.list.d/armhf.list apt-get update apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf </pre> <pre> ./configure --target=linux-armhf --x-includes=/usr/include \ --enable-includes=/usr/arm-linux-gnueabihf/include </pre> Now, the AROS build is configured properly and all you need to do is: make ==Build== ===64bit=== [https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] ===32bit=== # download/checkout the source someplace, e.g. /build/AROS-Src/ # make a directory to store external sources AROS downloads, e.g. /build/Ports # make a build directory, e.g. /build/aros-raspi-armhf # cd into the build dir, configure, and then run make -: <pre> >cd /build/aros-raspi-armhf >/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports >make >make arosboot-raspi </pre> then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it. You should then be able to boot the sdcard on your RasPi. The current W.I.P tree to svn. it can be built as follows .. <pre> ./configure --target=raspi-armhf make arosboot-raspi </pre> That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder. NB - if you have a Linux/other install, backup the existing config.txt first arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console "emulation" via code pinched from our libbootconsole), kernel.resource, and exec.library arosraspi.rom contains all the other components needed to boot AROS. The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom). the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO) Help building AROS hosted on Linux ARM Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device. Compilation stops after build libpopupmenu.a and trying to build libatomic have this error: <pre> Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic configure: WARNING: unrecognized options: --disable-nls, --without-x checking for --enable-version-specific-runtime-libs... no checking for --enable-generated-files-in-srcdir... no checking build system type... arm-unknown-linux-gnu checking host system type... arm-unknown-aros checking target system type... arm-unknown-aros checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc checking whether the C compiler works... no configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic': configure: error: C compiler cannot create executables See config.log' for more details make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77 [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512 [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory make[1]: *** [Makefile:361: linklibs-libatomic] Error 10 make: *** [Makefile:183: crosstools] Error 2 </pre> looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi so do make linklibs-aeabi-arm-quick and the missing lib was built. now the next stop is at fatal error: bits/libc-header-start.h: No such file or directory and fatal error: sys/cdefs.h: No such file or directory in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed? fixed with adding -I/usr/include/arm-linux-gnueabihf to where is missing on mmakefiles like USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES) P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles. Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again. My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a "template" to compare to native compilation under arm linux. Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild). The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC. For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script. Thanks compilation now go forward...changed target.cfg under "toolchain-core-armhf-build/bin/linux-arm/gen/config" and do make on "toolchain-core-armhf-build" dir. Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there: #MM- linklibs-armhd : libklibs-aeabi-arm Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this. Try adding this line (and the variant "linklibs-armhf" instead of hd) but it did not solve the automatic building of the missing lib. I must do "linklibs-aeabi-arm-quick". Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case. With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with "cannot find -laeabi " so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok. == Hardware == ===64bit=== ====BCM2712==== With the Pi5 Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. *Raspberry Pi M.2 HAT+ Expansion Board *Geekworm X1001 PCIe to M.2 Key-M NVMe *Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 *Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 *Hat+ Gen2 Gen3 Nvme *GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2 * *2024 RPI AI HAT - Hailo 20TOPs no LLMs *2026 RPI AI HAT+ 2 - Hailo 40TOPs slightly better? [https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi] *Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor *Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor *Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1 HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates ====BCM2711==== With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 the 2711b line used more power when idle, compared to the 2711c *2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues *2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design *Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE *[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles. The instruction encoding for the QPUs is different, but the core instructions are the same. Instructions for packed 8 bit int math has been dropped, along with most of the pack modes. Instructions for packed 16bit float math has been added (2 floats at in a single operation) With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register. the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of "one read port, one write port" to one "two read ports, one write port" block) The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. *vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers. *vc5 added a four thread per QPU mode, with 16 registers per thread. *vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads. With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer) A MMU, allowing a much simpler/faster kernel driver. Many more texture formats, framebuffer formats. h264/x264 [https://github.com/aros-development-team/AROS/commit/caecd66a9508acb0e9ef0a07169a14c33007b208 VideoCore hardware decoding through VCHIQ/MMAL (Pi 1–4)], H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1 HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates All the features needed for opengl es 3.0 Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised Possible maximum performance <pre> VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s </pre> Faster LPDDR4 memory. ====BCM2837==== With the Pi3 * Broadcom BCM43438 chip provides 2.4&nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. [https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. ===32bit=== === Core Kernel === ====BCM2708(family)==== which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM) *Framebuffer (fb) using mailbox *IRQ scheduler, etc *Arasan based SD Card controller *Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&view=article&id=106:rasperry-pi-usb-controller&catid=45:raspberry-pi&Itemid=54 Unofficial DOCS pdf], [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], *[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip *CMOS RAM *VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc *Audio Driver *Serial Peripheral Interface Bus (SPI) *[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers] *I2S *Universal Asynchronous Receiver Transmitter (UART) *[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO] BCM2836 * For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board *[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features], Implemented so far... # Modify the configure system so that it correctly builds for the arm hardware float raspi target. # Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display. # Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function. # Implemented serial debug support # Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc) # Implemented a timer.device to utilise the hardware timers. # Implemented a very basic gfx driver to expose the hardware's framebuffer. # Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media. # Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The "rom" image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot. # Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else. # fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi .. Improvements... # Implement a USB chipset driver "OR" finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the "virtual" hub code in place to represent the raspi's USB port (from poseidons p.o.v) # Implement a driver for the USB NIC (a few weeks - depends on USB above) # Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI] # fix syscall bug in the current raspi kernel code # Graphics depend on having a decent "bcmdma.resource" implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for "blitting". # [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] # [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 # The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate. Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition. The boot sequence carries out several pre-boot tasks *On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf *The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it *configures the memory split for the CPU and GPU *reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings) *loads the “kernel.img” file, again from the same partition *activates the CPU to begin executing the loaded kernel image The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU. RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named "kernel.img" at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem) Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf. You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling. At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules <pre> ? - alias for 'help' mtest - simple RAM test autoscr - run script from memory base - print or set address offset bbm - BBM sub-system bdinfo - print Board Info structure boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootm - boot application image from memory bootp - boot image via network using BootP/TFTP protocol cmp - memory compare coninfo - print console devices and information cp - memory copy crc32 - checksum calculation echo - echo args to console fatinfo - print information about filesystem fatload - load binary file from a dos filesystem fatls - list files in a directory (default /) go - start application at address 'addr' help - print online help iminfo - print header information for application image itest - return true/false on integer compare jade - loadb - load binary file over serial line (kermit mode) loads - load S-Record file over serial line loady - load binary file over serial line (ymodem mode) loop - infinite loop on address range md - memory display mm - memory modify (auto-incrementing) mtest - simple RAM test mw - memory write (fill) nfs - boot image via network using NFS protocol nm - memory modify (constant address) pci - list and access PCI Configuration Space ping - send ICMP ECHO_REQUEST to network host printenv - print environment variables rarpboot - boot image via network using RARP/TFTP protocol reset - Perform RESET of the CPU run - run commands in an environment variable saveenv - save environment variables to persistent storage saves - save S-Record file over serial line setenv - set environment variables sleep - delay execution for some time tftpboot - boot image via network using TFTP protocol USB - USB sub-system usbboot - boot from USB device version - print monitor version </pre> And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way... u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot. Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1, the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS routed only raw hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt. 1:1 relationship between CPU and hardware interrupts is present only on PC. IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class. PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant to be different, its IRQs are hardware-agnostic, they are plain "Hardware IRQ number X, whatever this means". They are low-level actually, and meaningful only in the context of a particular system. Was that not the transition from irq.hidd to kernel.resource? No. A long time ago there was another hacky bit named INTB_TIMERTICK. It was "abstract timer interrupt", used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea. Can someone please enlighten me a little on how the scheduler is meant to work? Poseidon.library creates its "Poseidon Event Task" during RTF_COLDSTART -> then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example. You miss what happens next... 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch(). 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible: 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run. 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list. My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop. There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures. The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table. The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :) Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this: movw r0, #:lower16:label movt r0, #:upper16:label In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations. There are two options - the first one would be to give up and go back to "fake" executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need. Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. GPU VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU. Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute. The good news about this is that we only need to write our HIDD using the OpenVG API. The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf). That's also the bad news. Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much. It's still probably less difficult and less work, than controlling the GPU directly. The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated. It also has some nice font functions, meaning we can lead into an accelerated text mode later. Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC. If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected. have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled. If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work. L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled. Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics. Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever. I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp). #warning "TODO: lookup optimal mmu table settings for raspi memory" /* Set up an identity-mapping for all 4GB */ for(x = 0; x < 4096; x ++) { pagetable[x] = x<<20 | (0x40002|0x80000|0x010000|0x00C00|0x04); } Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages? Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device). You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached) So .. pagetable[x] = x<<20 | 2; should be enough? No, for RAM you need to change the '| 0x40' to '| 0x80' tell dosboot the correct defaults to use Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead, display drivers should auto-install themselves during own initialization phase. I. e. detect hardware=>instantiate itself. This should make things way simpler. With this approach you only need to add the driver into KS image to get the device autobooted. No hardcoded stuff. Currently VESA and VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it. they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context). AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM marked as chip. BTW, is the video processing code you mention CPU code or GPU code? Also, IIRC we have support for "external memory allocators". Perhaps that's what we need for the allocation of GPU RAM through the mailbox. All hosted and x86 native ports should use proper context formats. trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET). Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units. The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ. Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port? It provides a before-anything-else shell prompt on the serial port. You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource. You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs. So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work. Also make sure to add shell.resource and shellcommands.resource for this. That should have done it. If you set "#define DEBUG 1" in arch/all-native/econsole/econsole.c, do you get any additional serial output? have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display? Im assuming it exposes a fake filesystem that tricks aros into booting? The contents of which are: ECON:AROS.boot Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm. To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen. Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks). have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress.. was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression. Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks. Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right) The _LE versions are for when you have endian swapping taking place. If the graphics are the same endian as the CPU, no swapping should occur. I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian. It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary. They were both little-endian. The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode). What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest? Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems? You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it. So, AROS creates the framebuffer bitmap (verified this) -> so surely it should be capable of then rendeing into it? I don't actually create the framebuffer "bitmap object" myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback. In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) So far have -: vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object. vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer, vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. RasPi has to speak to the "operating system" which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls. The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required. The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied. The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds). must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. For 2D dma, set TDMODE, and the spec says "interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer." so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data. The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out). openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits. Actually MEMF_CHIP has to present, for historical reasons. This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP. Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting. As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there. struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi. AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol. <pre> redmask: 0x0000F800 greenmask: 0x000007E0 bluemask: 0x0000001F alphamask: 0 redshift: 16 greenshift: 21 blueshift: 27 alphashift: 0 </pre> It should likely be vHidd_StdPixFmt_RGB16_LE This stuff is a bit confusing. The "names" of the stdpixfmts are based on the layout in memory, ignoring endianess. So for example: ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines. The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and stdpixfmt_be.h in rom/hidds/graphics/). With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag. (RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to be accessed as GGGBBBBBRRRRRGGGG). The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31). The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered, the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt->stdpixfmt) already in the system, and if so, it uses the already existing one and does not create a new one. In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt tag list based on that. 15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5 (or swapped) but it's actually still using 16 bit R5G6B5 (or swapped). aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count. But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses in the entry where you have looked up shifts/masks/etc. Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you are running on little endian machine) that matches the pixfmt that its meant to be. 0xAA,0xRR,0xGG,0xBB on little endian (->entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32) 0xBB,0xGG,0xRR,0xAA on little endian (->entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32) 0xAA,0xRR,0xGG,0xBB on big endian (->entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32) 0xBB,0xGG,0xRR,0xAA on big endian (->entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32) it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B. read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment . Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening. The output image looks to have too much green/blue, and very weak red. Kickstart The idea is to minimize amount of archirecture-specific modules to make the user's life easier. So, the kickstart was split into 'base' (which does not contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This way, for example, distribution makers can save up space on CD and make CDs with multiple platform support. Different configuration would load the same base with different BSP's. Next there was some part which is entirely missing on hosted. These are filesystems. Hosted ports do not need them to boot up, so on hosted they are left out. At the other hand, they are also architecture-agnostic. So i put them into 'FS' package (standing for 'filesystem'). USB Poseidon is one more big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run on retro PCs without USB). Personally i have one. Again, Poseidon is hardware-agnostic (well, there are USB drivers but HCIs are pretty standard). AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code. Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running. Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong. Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side. Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode & switching modes once it's up and running. Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup. * Model A and B limited to 150 mA per port. * Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub. Implementing the hardware driver that Poseidon uses to interact with the USB components. Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the "virtual" root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals. The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”). There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg]. The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code. The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port). Probably only need provision of relevant changes to dwc_common_port. Other things to consider.... * Provision of necessary headers to get it to compile * Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) ) * Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start. the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB. Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have "prefixed" it with the real location of uncached RAM and booted AROS once again. Trident saw this: Product : Hub: Vdr=0424/PID=9514 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 9 SubClass : 0 DevProto : 2 VendorID : 1060 ProductID : 38164 DevVers : 0200 and this: Product : Vendor: Vdr=0424/PID=EC00 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 255 SubClass : 0 DevProto : 1 VendorID : 1060 ProductID : 60416 DevVers : 0200 and even this: Product : Hub: Vdr=0424/PID=9514 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 9 SubClass : 0 DevProto : 2 VendorID : 1060 ProductID : 38164 DevVers : 0200 What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;) So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. [http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio] Audio The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI. HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface. Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. [https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures Analogue audio Audio over HDMI rev 1.3 & 1.4 Ethernet 10/100 BaseT Ethernet RJ45 socket GPIO GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins) Probably a resource rather than a device... Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p GPU graphics with 2D and 3D acceleration Sadly none yet for 32bit but for 64bit... Miscellanous hdmi issues Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there. You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal. If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to "set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode Do not set hdmi_safe=1 as that overrides many of the previous options. Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA. If you see a problem with the red colour - either absent, or interference - then try a boost composite video changing the RCA cable, then the composite port worked out of the box Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't? Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat What's the result? Put back config.txt What's the result? for PAL mode sdtv_mode=2 dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected <pre> # NOOBS Auto-generated Settings: #hdmi_force_hotplug=1 #config_hdmi_boost=4 #overscan_left=24 #overscan_right=24 #overscan_top=16 #overscan_bottom=16 #disable_overscan=0 start_x=1 gpu_mem=128 </pre> tvservice -c "PAL 4:3" <pre> /opt/vc/bin/tvservice -s or tvservice -s state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive /opt/vc/bin/tvservice -m CEA Group CEA has 1 modes: (native) mode 16: 1920x1080 @ 60 Hz, progressive /opt/vc/bin/tvservice -m DMT Group DMT has 0 modes: </pre> sudo amixer cset numid=3 1 forces the audio to the headphone jack, even with the HDMI video output plugged in config.txt the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others. What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground. The wiring for the 4 pole are: TIP (LEFT AUDIO CHANNEL) RING 1 (RIGHT AUDIO CHANNEL) RING 2 (GROUND/EARTH) RING 3 BASE/SLEEVE (VIDEO) YELLOW Most Apple based Players and the Microsoft Zune (TM) are wired this way. Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug. Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one. External devices * Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&nbsp;nm, peak at 880&nbsp;nm and trails off at 940&nbsp;nm wavelengths * Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - * Branded WIFI usb BCM43143 dongle N.B. dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles. It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board. the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible. currently the only supported sensor is OV5647 and IMX219. The linux drivers are all in the firmware blob, else you'd be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. Static electricity maybe an issue for the camera module and slightly less for the pi board. == References == ===Good sites to visit=== *[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] *[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] *[https://rpilocator.com/ RPiLocator] Linux only *[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] *[https://dietpi.com/ DietPi] *[http://www.tinycorelinux.net/ports.html piCore] *[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] *[https://github.com/armbian/build Armbian] *[ FydeOS] *[ TwisterOS based on ChromiumOS] *[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] *[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] *[ PiMiga for pi4 and pi5] *[ amibian for pi2 and pi3] *[ retropie pi1 and 2] Other alternative lighter smaller than Pi OS *[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] *[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4] *[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] *[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] *[https://github.com/stevereaver/uaos uaOS with Emu68k] *[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] *[ HaikuOS] *[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] *[https://github.com/maxnet/berryboot berryboot] *[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc [https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] *Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested *Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested *Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested *Black DeskPi Super6C Cluster Mini-ITX Board - untested *[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 *Green BentoIO CMX0 - untested *Box EDATec ED-CLAWBOX - untested *Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested *Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested *Box Waveshare [ CM5-POE-BOX-A] - untested *Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested *Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested *Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested *[https://carboncomputers.us/products/pi-flux piFlux] *[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - *Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested *Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested *Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested *Purple Pi Hut Cytron CM4 Maker Board - untested *Black DeskPi Super6C Cluster Mini-ITX Board - untested *[ KubeSail PiBox mini 2] *Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested *[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs *Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted *Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 *Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' *Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested *Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better *Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs *Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob *[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested *[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested *[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed *[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3" HD 1366 x 768 display, small touchpad, *[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS *[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor *[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 <pre> 2008 Trustees collected for Foundation 2009 Pi Foundation charity status gained 2010 2011 First Raspberry prototypes 2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835 2012 First million sold - more than the 10,000 original planned and anticipated 2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 2013 Over two million sold 2014 Over three million sold 2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 2015 Over four million first gen pis sold 2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 2016 Pi0 1.3 released with camera csi connector 2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 2015 Over a million pi2s sold 2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 2016 PIs total over 10 million worldwide 2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 2017 12 million pis sold in total 2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 2019 Over 15 million sold 2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge 2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board CM4101000 1Gb RAM Lite SOM CM4102000 2GB RAM Lite CM4104000 4GB RAM Lite CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules CM4104032 4GB RAM 32GB emmc CM4108000 8GB RAM Lite CM4008016 8GB RAM 16Gb eMMc 2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - CM4S01000 1GB RAM Lite CM4S01008 1GB RAM 8GB eMMC Flash CM4S02000 2GB RAM Lite CM4S04000 4GB RAM Lite CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 CM4S08000 8GB RAM Lite 2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 2021-48 Raspberry Pi 4 model B v1.5 2GB 2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 2024 Pi 5 2GB DDR4 version uses BCM2712D0 2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 2024 Pi 5 v1.1 2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board CM5004000 04GB RAM 0GB eMMC Lite CM5008000 08GB RAM 0GB eMMC Lite CM5016000 16GB RAM 0GB eMMC Lite 2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 2025 Pi5 1GB DDR4 announced 2022 PiOS linux goes 64bit 2024 Pi Trading IPO stockmarket stock exchange listing 2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom 2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 2026 Late July daily 64bit Pi3 LE little endian builds start 2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 2026 2027 2028 Pi 6 </pre> The vcgencmd can be used to inspect and dump the current system configuration. vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called "the firmware". Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc *spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid javascript] [https://github.com/6pac/SlickGrid SlickGrid typescript] [https://github.com/jspreadsheet/ce jspreadsheet ce] probably without xlsx support *presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support *ai office [https://github.com/dream-num/univer/ univer], [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] *weather [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast], [https://github.com/kaushalsahu07/weather weather needs API key], ==Future== [https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2], [https://github.com/Joshua-Riek/armbian-build Linux Armbian builds for old mobile devices], [], [https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], [https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], [ ytdl], [https://github.com/golddominik893/liberatube liberatube] [https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], {{BookCat}} l2vc62xp26e5f7pcfgqjizclq4x5rti 4679935 4679808 2026-11-04T10:26:46Z Jeff1138 301139 4679935 wikitext text/x-wiki {{ArosNav}} [[#Native]] [[#Hosted]] [[#Build]] [[#Hardware]] [[#References]] [[#Future]] ==Introduction== [[File:Wanderer00.png|thumb|Wanderer on Aros Pi3b]] [[File:Scalos00.png|thumb|Scalos on Aros Pi3b]] [[File:DOpus5Magellan00.png|thumb|DOpus5 Magellan on Aros Pi3b]] Aros aims to cover Pi 3 to 5 512Mb+ RAM Options to boot from using a good power source to prevent the yellow lightning symbol. *With Pi3b+ the max you can get is 5.1V 2.5A with micro usb. *With Pi4 5.1V 3A with usb-c *With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c * Pi500+ keyboard wedge - working but not much tested esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] * Pi500 wedge with up to date bootloader via PiOS - working but not much testing esp [https://github.com/aros-development-team/AROS/commit/48e9c8edcca4b5c1e1fe0b1123f2129f624af67b power button] * Pi 5 - Quad A76 64bit ARMv8 and RP1 "southbridge" with VideoCore 7 D0 (rev1.1) - untested * Pi 5 - Quad A76 64bit ARMv8 and RP1 "southbridge" with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested * Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - * Pi 4 - Quad A72 64bit ARMv8 with VideoCore 6 * Pi 3 - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling * Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], * Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible * Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible * Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible ===Native=== * 2013-03 Kalamatee starts work * 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb * 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi] * 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] * 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5] * 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM] ====64bit==== '''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository] '''Not recommended''' but [https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ and alternative site and nightly2] which is a test version of '''very few''' apps with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 64bit build works well on a single core LE little endian. [https://aros.sourceforge.io/nightly1.html raspi-aarch64-smp-system multicore is available] [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] *Pi500+ untested usb3 booting or nvme ssd *Pi500 untested usb3 booting *Pi5 untested usb3 booting *Pi400 boots with '''USB3''' port based sata3 ssd *Pi4 untested (may need eeprom update from PiOS or Pi SD Imager) *Pi 3 B+ is pre-configured for USB sata3 boot - untested *Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card Speed write wise (top faster) <pre> *NVME Pi5 untested >1000MB/sec or faster if matched correctly *Sata3 ssd 500MB/sec *SD V90 90MB/sec 4K maybe 8K *SD V60 60MB/sec 1080p *SD U3 V30 30MB/sec 720p *SD C10 U1 V10 A1 A2 10MB/sec minimum should be used now *SD C06 6MB/sec *SD C04 4MB/sec </pre> As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -> View -> All files Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. Esc escape key usually closes open windows even the desktop In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. Like most amiga like OSs the audio and networking need to be setup manually Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++ or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off *if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again *...waiting for an address - Disconnect and try Connect Until, Connected to <router> - 192.168.x.x For lan ethernet port, please use Network prefs and the following hardware is *lan9514 Pi3b Pi2 not supported at the moment *lan7515 Pi3b+ type into Device usblan78xx.device as net0: remove other device(s) *bcmgenet Pi4 Pi400 choose for Device bcmgenet.device *cdnsgem Pi5 Pi500 Pi500+ RP1 i/o for cadencegem (network prefs may forget random information when rebooted) Summary <pre> ̽*Pi3a̹+ wifi works, *Pi3b ethernet not supported, usb ethernet not working but wifi prefs setup works *Pi3b+ wifi working and ethernet works *Pi4 untested *Pi400 wifi and ethernet untested *Pi5 wifi and ethernet untested *Pi500 wifi and ethernet untested *Pi500+ wifi works </pre> Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. [http://archives.arosworld.org/index.php?function=browse&cat=network/browser amelinium web browser] (JS 1.6 ES9 ECMASCript 2018) is available with an [https://eab.abime.net/showthread.php?t=122494&page=80 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb] JavaScript 1.5 (ECMAScript 3) as css and javascript websites can be slow to load or resolve (no JIT). Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. Html5test gives 189 (1.29), 300 (1.31), 301 (1.39) out of 555. You may have to delete the cache (Menu -> Page -> Delete cache) to fully retest big Amelinium updates or free up space. Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly DNS lookup failed... close browser and reboot and setup wifi again - repeat until it works again youtube video and audio - js button for javascript must be on/shaded - Settings -> Soundoutput - AHI Any restriction to lower resolutions is due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. Either CPU/GPU, internet speed and/or video quality. Pi3 can expect up to 480p (wifi) and up to 720p (ethernet). Pi4 expect (wifi) (ethernet). If no separate audio stream error - set settings -> Video quality to 360p or lower as Youtube has a fallback mode at that level https://t.me/s/channel_name for Telegram public messages from [https://t.me/s/AROS_official AROS_official] [https://t.me/s/vamped_amiga vamped_amiga] [https://t.me/s/demoscenecracktros demoscenecracktros] *art local js apps like dpaint.js There is normally no Bluetooth support for most amiga like OSs but that has changed recently [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://github.com/RPi-Distro/bluez-firmware/tree/pios/trixie/debian/firmware/broadcom firmware] *Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W *Bluetooth 4.2 BCM4345C0.hcd Pi3B+, Pi4 *Bluetooth 5.0 BCM4345C5.hcd Pi4B rev, CM4 and maybe Pi5 and CM5 <pre> *bthid keyboard mouse support *btserial serial *btpan short range wireless connecting devices </pre> Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g. date 24-Dec-2026 23:59:59 but this will need to be done again after every reset/power off. Maybe hardware [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. USB classes support from Prefs/Trident is still work in process *usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w *[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&file=audio/misc/timidity.lha timidity], Regarding 680x0 emulation, there are several options that could be considered but most not fully implemented *[https://github.com/kaffeine1/kaffeine kaffeine m68k with Amiga system OS fɹiendly calls going to Aros ones] *[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones *[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games *[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] *[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] [https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] Some exceptions: *Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used *The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V *For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15). With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented. Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi. In the shell (Cntrl + C to end) GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' *PIN -- (Required) Target GPIO pin number (e.g. 12). *SET -- Set pin output value to 0 (LOW) or 1 (HIGH). *GET -- Read and print current digital input level (0 or 1). *MODE -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate). *PULL -- Configure pull resistor: NONE, UP, DOWN. EXAMPLES <pre> GPIO 12 MODE OUT GPIO 12 SET 1 GPIO 12 GET GPIO 13 PULL UP </pre> [https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&pid=13954#post_13954 discussion] Youtube [https://www.youtube.com/watch?v=8dZwGkUKAmA Pi3A̟+ (plus) with smp build and PiAROS], [], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], [], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], [], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], [], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], [https://www.youtube.com/watch?v=nHt_k_QkHe0 AmiWest 2026 Day 1], [https://www.youtube.com/watch?v=nA2fnaOt1Ik Amiwest 2026 Day 2], [https://www.youtube.com/watch?v=zQM4CD64xDE&t=612s&pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... {| class="wikitable sortable" width="90%" ! width="10%" |Pi ! width="10%" |Single Core 2D ! width="10%" |Single Core 3D ! width="10%" |Single Core 3D ! width="10%" |SMP 2D ! width="10%" |SMP 3D ! width="10%" |SMP 3D ! width="35%" |Comments |- | <!--Pi-->Pi3 | <!--Single Core 2D--> | <!--Single Core 3D--> | <!--Single Core 3D--> | <!--SMP 2D--> | <!--SMP 3D--> | <!--SMP 3D--> | <!--Comments--> |- |} ==== 32bit ==== For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD ===Hosted=== AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon Macs] [https://github.com/jonx/Macaros early alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&pid=13910#post_13910 here] with [https://github.com/pomaros pomaros]. There is a [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2076&highlight=jonx&pid=14193#post_14193 work in progress native Mac Apple silicon M1 M2 M3 version] [http://www.aros.org/snapshots1.html old linux and android hosted 32bit] ==== Hosted ==== =====64bit===== [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&rowstart=80&pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] [https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&rowstart=80 From the Aros Raspberry pi 3 64bit thread] Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources. You will need: - Ubuntu 24.04 or 26.04 - qemu-system-aarch64 installed - Internet connection - rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz) 1) Install prerequisites: sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm 2) Clone sources cd <project-directory> git clone https://github.com/aros-development-team/AROS.git --recurse-submodules 3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have: AROS (the directory with cloned sources) fix-dotdot.py rebuild.sh recreate-sdcard.sh run-qemu.sh update-sdcard.sh 4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64 This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step. 5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64 This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour. 6) Run ./recreate-sdcard.sh This will create an sdcard.img file with contents of previous step. 7) Run ./run-qemu.sh This will start QEMU with SD card image and ROM images. It will boot into AROS. =====32bit===== Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013] ../AROS/configure --target=linux-armhf --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux) *armel - many of the "android" machines require since the entire OS is made for soft float VFP. *armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP) Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI. Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets. *needs an AROS code compiler for ARM target *as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes. with—disable-crosstools $AROS_CC is always a wrapper around $KERNEL_CC ? If so, this is wrong for some ports. This can break Darwin, Windows and Android port. Yes, Android port will build. And even work. But it's not good because the port will not be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example: <pre> enum test {foo, bar}; enum test testvar; </pre> sizeof(testvar) will be equal to sizeof(int) in GNUEABI (Linux and AROS) and sizeof(short) on Android. This affects linking objects from static linklibs, for example. Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts. Android is the same. $KERNEL_CC is incompatible with AROS. compiler=kernel is appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or barebone hardware, if we talk about native). This includes bootstraps, their linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations. No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows, Android) this is not true any more, and compiler=kernel is never going to work. If you want to compile your AROS module against host OS includes, append the following to USER_INCLUDES (or USER_CFLAGS, this is effectively the same): -isystem $(GENINCDIR) $(KERNEL_INCLUDES) $(KERNEL_INCLUDES) expands to: -isystem <your_os_includes> -isystem <host_OS_gcc_private_includes> -nostdinc This makes AROS compiler adhering to host OS APIs. If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH). Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one. Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types. Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but "./configure --target=raspi-armhf" is enough to start, then "make arosboot-raspi" will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc). It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output. *armel = typically Debian 6, Ubuntu Maverick, Android, *armhf = typically Debian 7, Debian 8, Ubuntu Precise, Cross-compiling Ubuntu ARM softfp <pre> sudo sh echo 'foreign-architecture armel' >>/etc/dpkg/dpkg.cfg.d/multiarch echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' >/etc/apt/sources.list.d/armel.list apt-get update apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel </pre> <pre> ./configure --target=linux-arm --x-includes=/usr/include \ --enable-includes=/usr/arm-linux-gnueabi/include </pre> Cross-compiling Ubuntu ARM hard-float <pre> sudo sh echo 'foreign-architecture armhf' >>/etc/dpkg/dpkg.cfg.d/multiarch echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' >/etc/apt/sources.list.d/armhf.list apt-get update apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf </pre> <pre> ./configure --target=linux-armhf --x-includes=/usr/include \ --enable-includes=/usr/arm-linux-gnueabihf/include </pre> Now, the AROS build is configured properly and all you need to do is: make ==Build== ===64bit=== [https://github.com/aros-development-team/AROS/blob/7016ce28bfdb754182edb16011c98faaf5413c29/arch/aarch64-raspi/boot/mmakefile.src#L180 boot makefile] ===32bit=== # download/checkout the source someplace, e.g. /build/AROS-Src/ # make a directory to store external sources AROS downloads, e.g. /build/Ports # make a build directory, e.g. /build/aros-raspi-armhf # cd into the build dir, configure, and then run make -: <pre> >cd /build/aros-raspi-armhf >/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports >make >make arosboot-raspi </pre> then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it. You should then be able to boot the sdcard on your RasPi. The current W.I.P tree to svn. it can be built as follows .. <pre> ./configure --target=raspi-armhf make arosboot-raspi </pre> That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder. NB - if you have a Linux/other install, backup the existing config.txt first arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console "emulation" via code pinched from our libbootconsole), kernel.resource, and exec.library arosraspi.rom contains all the other components needed to boot AROS. The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom). the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO) Help building AROS hosted on Linux ARM Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device. Compilation stops after build libpopupmenu.a and trying to build libatomic have this error: <pre> Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic configure: WARNING: unrecognized options: --disable-nls, --without-x checking for --enable-version-specific-runtime-libs... no checking for --enable-generated-files-in-srcdir... no checking build system type... arm-unknown-linux-gnu checking host system type... arm-unknown-aros checking target system type... arm-unknown-aros checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc checking whether the C compiler works... no configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic': configure: error: C compiler cannot create executables See config.log' for more details make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77 [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512 [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory make[1]: *** [Makefile:361: linklibs-libatomic] Error 10 make: *** [Makefile:183: crosstools] Error 2 </pre> looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi so do make linklibs-aeabi-arm-quick and the missing lib was built. now the next stop is at fatal error: bits/libc-header-start.h: No such file or directory and fatal error: sys/cdefs.h: No such file or directory in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed? fixed with adding -I/usr/include/arm-linux-gnueabihf to where is missing on mmakefiles like USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES) P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles. Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again. My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a "template" to compare to native compilation under arm linux. Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild). The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC. For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script. Thanks compilation now go forward...changed target.cfg under "toolchain-core-armhf-build/bin/linux-arm/gen/config" and do make on "toolchain-core-armhf-build" dir. Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there: #MM- linklibs-armhd : libklibs-aeabi-arm Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this. Try adding this line (and the variant "linklibs-armhf" instead of hd) but it did not solve the automatic building of the missing lib. I must do "linklibs-aeabi-arm-quick". Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case. With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with "cannot find -laeabi " so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok. == Hardware == ===64bit=== ====BCM2712==== With the Pi5 Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. *Raspberry Pi M.2 HAT+ Expansion Board *Geekworm X1001 PCIe to M.2 Key-M NVMe *Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 *Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 *Hat+ Gen2 Gen3 Nvme *GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2 * *2024 RPI AI HAT - Hailo 20TOPs no LLMs *2026 RPI AI HAT+ 2 - Hailo 40TOPs slightly better? [https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi] *Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor *Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor *Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1 HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates ====BCM2711==== With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 the 2711b line used more power when idle, compared to the 2711c *2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues *2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design *Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE *[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is [https://docs.mesa3d.org/drivers/v3d.html significantly different] The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles. The instruction encoding for the QPUs is different, but the core instructions are the same. Instructions for packed 8 bit int math has been dropped, along with most of the pack modes. Instructions for packed 16bit float math has been added (2 floats at in a single operation) With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register. the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of "one read port, one write port" to one "two read ports, one write port" block) The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. *vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers. *vc5 added a four thread per QPU mode, with 16 registers per thread. *vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads. With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer) A MMU, allowing a much simpler/faster kernel driver. Many more texture formats, framebuffer formats. h264/x264 [https://github.com/aros-development-team/AROS/commit/caecd66a9508acb0e9ef0a07169a14c33007b208 VideoCore hardware decoding through VCHIQ/MMAL (Pi 1–4)], H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1 HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates All the features needed for opengl es 3.0 Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised Possible maximum performance <pre> VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s </pre> Faster LPDDR4 memory. ====BCM2837==== With the Pi3 * Broadcom BCM43438 chip provides 2.4&nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback maybe affected due to the lack of custom support in the GPU with Aros. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. [https://github.com/hermanhermitage/videocoreiv/wiki/VideoCore-IV-Programmers-Manual Dual VDP] and scalable QPU in [https://docs.mesa3d.org/drivers/vc4.html VC4] and x.264/h.264 accelerated untested only and VP9 on cpu or neon help ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. ===32bit=== === Core Kernel === ====BCM2708(family)==== which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM) *Framebuffer (fb) using mailbox *IRQ scheduler, etc *Arasan based SD Card controller *Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&view=article&id=106:rasperry-pi-usb-controller&catid=45:raspberry-pi&Itemid=54 Unofficial DOCS pdf], [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], *[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip *CMOS RAM *VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc *Audio Driver *Serial Peripheral Interface Bus (SPI) *[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers] *I2S *Universal Asynchronous Receiver Transmitter (UART) *[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO] BCM2836 * For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board *[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features], Implemented so far... # Modify the configure system so that it correctly builds for the arm hardware float raspi target. # Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display. # Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function. # Implemented serial debug support # Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc) # Implemented a timer.device to utilise the hardware timers. # Implemented a very basic gfx driver to expose the hardware's framebuffer. # Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media. # Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The "rom" image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot. # Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else. # fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi .. Improvements... # Implement a USB chipset driver "OR" finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the "virtual" hub code in place to represent the raspi's USB port (from poseidons p.o.v) # Implement a driver for the USB NIC (a few weeks - depends on USB above) # Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI] # fix syscall bug in the current raspi kernel code # Graphics depend on having a decent "bcmdma.resource" implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for "blitting". # [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] # [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 # The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate. Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition. The boot sequence carries out several pre-boot tasks *On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf *The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it *configures the memory split for the CPU and GPU *reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings) *loads the “kernel.img” file, again from the same partition *activates the CPU to begin executing the loaded kernel image The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU. RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named "kernel.img" at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem) Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf. You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling. At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules <pre> ? - alias for 'help' mtest - simple RAM test autoscr - run script from memory base - print or set address offset bbm - BBM sub-system bdinfo - print Board Info structure boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootm - boot application image from memory bootp - boot image via network using BootP/TFTP protocol cmp - memory compare coninfo - print console devices and information cp - memory copy crc32 - checksum calculation echo - echo args to console fatinfo - print information about filesystem fatload - load binary file from a dos filesystem fatls - list files in a directory (default /) go - start application at address 'addr' help - print online help iminfo - print header information for application image itest - return true/false on integer compare jade - loadb - load binary file over serial line (kermit mode) loads - load S-Record file over serial line loady - load binary file over serial line (ymodem mode) loop - infinite loop on address range md - memory display mm - memory modify (auto-incrementing) mtest - simple RAM test mw - memory write (fill) nfs - boot image via network using NFS protocol nm - memory modify (constant address) pci - list and access PCI Configuration Space ping - send ICMP ECHO_REQUEST to network host printenv - print environment variables rarpboot - boot image via network using RARP/TFTP protocol reset - Perform RESET of the CPU run - run commands in an environment variable saveenv - save environment variables to persistent storage saves - save S-Record file over serial line setenv - set environment variables sleep - delay execution for some time tftpboot - boot image via network using TFTP protocol USB - USB sub-system usbboot - boot from USB device version - print monitor version </pre> And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way... u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot. Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1, the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS routed only raw hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt. 1:1 relationship between CPU and hardware interrupts is present only on PC. IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class. PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant to be different, its IRQs are hardware-agnostic, they are plain "Hardware IRQ number X, whatever this means". They are low-level actually, and meaningful only in the context of a particular system. Was that not the transition from irq.hidd to kernel.resource? No. A long time ago there was another hacky bit named INTB_TIMERTICK. It was "abstract timer interrupt", used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea. Can someone please enlighten me a little on how the scheduler is meant to work? Poseidon.library creates its "Poseidon Event Task" during RTF_COLDSTART -> then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example. You miss what happens next... 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch(). 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible: 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run. 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list. My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop. There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures. The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table. The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :) Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this: movw r0, #:lower16:label movt r0, #:upper16:label In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations. There are two options - the first one would be to give up and go back to "fake" executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need. Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. GPU VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU. Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute. The good news about this is that we only need to write our HIDD using the OpenVG API. The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf). That's also the bad news. Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much. It's still probably less difficult and less work, than controlling the GPU directly. The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated. It also has some nice font functions, meaning we can lead into an accelerated text mode later. Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC. If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected. have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled. If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work. L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled. Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics. Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever. I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp). #warning "TODO: lookup optimal mmu table settings for raspi memory" /* Set up an identity-mapping for all 4GB */ for(x = 0; x < 4096; x ++) { pagetable[x] = x<<20 | (0x40002|0x80000|0x010000|0x00C00|0x04); } Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages? Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device). You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached) So .. pagetable[x] = x<<20 | 2; should be enough? No, for RAM you need to change the '| 0x40' to '| 0x80' tell dosboot the correct defaults to use Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead, display drivers should auto-install themselves during own initialization phase. I. e. detect hardware=>instantiate itself. This should make things way simpler. With this approach you only need to add the driver into KS image to get the device autobooted. No hardcoded stuff. Currently VESA and VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it. they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context). AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM marked as chip. BTW, is the video processing code you mention CPU code or GPU code? Also, IIRC we have support for "external memory allocators". Perhaps that's what we need for the allocation of GPU RAM through the mailbox. All hosted and x86 native ports should use proper context formats. trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET). Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units. The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ. Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port? It provides a before-anything-else shell prompt on the serial port. You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource. You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs. So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work. Also make sure to add shell.resource and shellcommands.resource for this. That should have done it. If you set "#define DEBUG 1" in arch/all-native/econsole/econsole.c, do you get any additional serial output? have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display? Im assuming it exposes a fake filesystem that tricks aros into booting? The contents of which are: ECON:AROS.boot Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm. To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen. Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks). have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress.. was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression. Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks. Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right) The _LE versions are for when you have endian swapping taking place. If the graphics are the same endian as the CPU, no swapping should occur. I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian. It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary. They were both little-endian. The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode). What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest? Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems? You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it. So, AROS creates the framebuffer bitmap (verified this) -> so surely it should be capable of then rendeing into it? I don't actually create the framebuffer "bitmap object" myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback. In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) So far have -: vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object. vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer, vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. RasPi has to speak to the "operating system" which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls. The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required. The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied. The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds). must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. For 2D dma, set TDMODE, and the spec says "interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer." so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data. The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out). openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits. Actually MEMF_CHIP has to present, for historical reasons. This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP. Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting. As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there. struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi. AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol. <pre> redmask: 0x0000F800 greenmask: 0x000007E0 bluemask: 0x0000001F alphamask: 0 redshift: 16 greenshift: 21 blueshift: 27 alphashift: 0 </pre> It should likely be vHidd_StdPixFmt_RGB16_LE This stuff is a bit confusing. The "names" of the stdpixfmts are based on the layout in memory, ignoring endianess. So for example: ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines. The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and stdpixfmt_be.h in rom/hidds/graphics/). With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag. (RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to be accessed as GGGBBBBBRRRRRGGGG). The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31). The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered, the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt->stdpixfmt) already in the system, and if so, it uses the already existing one and does not create a new one. In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt tag list based on that. 15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5 (or swapped) but it's actually still using 16 bit R5G6B5 (or swapped). aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count. But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses in the entry where you have looked up shifts/masks/etc. Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you are running on little endian machine) that matches the pixfmt that its meant to be. 0xAA,0xRR,0xGG,0xBB on little endian (->entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32) 0xBB,0xGG,0xRR,0xAA on little endian (->entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32) 0xAA,0xRR,0xGG,0xBB on big endian (->entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32) 0xBB,0xGG,0xRR,0xAA on big endian (->entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32) it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B. read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment . Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening. The output image looks to have too much green/blue, and very weak red. Kickstart The idea is to minimize amount of archirecture-specific modules to make the user's life easier. So, the kickstart was split into 'base' (which does not contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This way, for example, distribution makers can save up space on CD and make CDs with multiple platform support. Different configuration would load the same base with different BSP's. Next there was some part which is entirely missing on hosted. These are filesystems. Hosted ports do not need them to boot up, so on hosted they are left out. At the other hand, they are also architecture-agnostic. So i put them into 'FS' package (standing for 'filesystem'). USB Poseidon is one more big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run on retro PCs without USB). Personally i have one. Again, Poseidon is hardware-agnostic (well, there are USB drivers but HCIs are pretty standard). AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code. Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running. Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong. Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side. Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode & switching modes once it's up and running. Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup. * Model A and B limited to 150 mA per port. * Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub. Implementing the hardware driver that Poseidon uses to interact with the USB components. Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the "virtual" root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals. The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”). There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg]. The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code. The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port). Probably only need provision of relevant changes to dwc_common_port. Other things to consider.... * Provision of necessary headers to get it to compile * Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) ) * Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start. the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB. Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have "prefixed" it with the real location of uncached RAM and booted AROS once again. Trident saw this: Product : Hub: Vdr=0424/PID=9514 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 9 SubClass : 0 DevProto : 2 VendorID : 1060 ProductID : 38164 DevVers : 0200 and this: Product : Vendor: Vdr=0424/PID=EC00 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 255 SubClass : 0 DevProto : 1 VendorID : 1060 ProductID : 60416 DevVers : 0200 and even this: Product : Hub: Vdr=0424/PID=9514 Manufacturer: Standard Microsystems Corp. SerialNumber: n/a /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200 Class : 9 SubClass : 0 DevProto : 2 VendorID : 1060 ProductID : 38164 DevVers : 0200 What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;) So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. [http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio] Audio The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI. HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface. Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. [https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures Analogue audio Audio over HDMI rev 1.3 & 1.4 Ethernet 10/100 BaseT Ethernet RJ45 socket GPIO GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins) Probably a resource rather than a device... Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p GPU graphics with 2D and 3D acceleration Sadly none yet for 32bit but for 64bit... Miscellanous hdmi issues Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there. You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal. If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to "set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode Do not set hdmi_safe=1 as that overrides many of the previous options. Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA. If you see a problem with the red colour - either absent, or interference - then try a boost composite video changing the RCA cable, then the composite port worked out of the box Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't? Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat What's the result? Put back config.txt What's the result? for PAL mode sdtv_mode=2 dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected <pre> # NOOBS Auto-generated Settings: #hdmi_force_hotplug=1 #config_hdmi_boost=4 #overscan_left=24 #overscan_right=24 #overscan_top=16 #overscan_bottom=16 #disable_overscan=0 start_x=1 gpu_mem=128 </pre> tvservice -c "PAL 4:3" <pre> /opt/vc/bin/tvservice -s or tvservice -s state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive /opt/vc/bin/tvservice -m CEA Group CEA has 1 modes: (native) mode 16: 1920x1080 @ 60 Hz, progressive /opt/vc/bin/tvservice -m DMT Group DMT has 0 modes: </pre> sudo amixer cset numid=3 1 forces the audio to the headphone jack, even with the HDMI video output plugged in config.txt the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others. What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground. The wiring for the 4 pole are: TIP (LEFT AUDIO CHANNEL) RING 1 (RIGHT AUDIO CHANNEL) RING 2 (GROUND/EARTH) RING 3 BASE/SLEEVE (VIDEO) YELLOW Most Apple based Players and the Microsoft Zune (TM) are wired this way. Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug. Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one. External devices * Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&nbsp;nm, peak at 880&nbsp;nm and trails off at 940&nbsp;nm wavelengths * Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - * Branded WIFI usb BCM43143 dongle N.B. dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles. It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board. the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible. currently the only supported sensor is OV5647 and IMX219. The linux drivers are all in the firmware blob, else you'd be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. Static electricity maybe an issue for the camera module and slightly less for the pi board. == References == ===Good sites to visit=== *[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] *[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] *[https://rpilocator.com/ RPiLocator] Linux only *[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] *[https://dietpi.com/ DietPi] *[http://www.tinycorelinux.net/ports.html piCore] *[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] *[https://github.com/armbian/build Armbian] *[ FydeOS] *[ TwisterOS based on ChromiumOS] *[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] *[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] *[ PiMiga for pi4 and pi5] *[ amibian for pi2 and pi3] *[ retropie pi1 and 2] Other alternative lighter smaller than Pi OS *[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] *[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4] *[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] *[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] *[https://github.com/stevereaver/uaos uaOS with Emu68k] *[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] *[ HaikuOS] *[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] *[https://github.com/maxnet/berryboot berryboot] *[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc [https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] *Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested *Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested *Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested *Black DeskPi Super6C Cluster Mini-ITX Board - untested *[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 *Green BentoIO CMX0 - untested *Box EDATec ED-CLAWBOX - untested *Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested *Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested *Box Waveshare [ CM5-POE-BOX-A] - untested *Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested *Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested *Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested *[https://carboncomputers.us/products/pi-flux piFlux] *[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - *Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested *Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested *Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested *Purple Pi Hut Cytron CM4 Maker Board - untested *Black DeskPi Super6C Cluster Mini-ITX Board - untested *[ KubeSail PiBox mini 2] *Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested *[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs *Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs *Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted *Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 *Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' *Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested *Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better *Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs *Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob *[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested *[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested *[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed *[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3" HD 1366 x 768 display, small touchpad, *[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS *[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor *[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 <pre> 2008 Trustees collected for Foundation 2009 Pi Foundation charity status gained 2010 2011 First Raspberry prototypes 2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835 2012 First million sold - more than the 10,000 original planned and anticipated 2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 2013 Over two million sold 2014 Over three million sold 2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 2015 Over four million first gen pis sold 2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 2016 Pi0 1.3 released with camera csi connector 2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 2015 Over a million pi2s sold 2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 2016 PIs total over 10 million worldwide 2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 2017 12 million pis sold in total 2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 2019 Over 15 million sold 2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge 2019 Pi 4 Model B v1.1 RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board CM4101000 1Gb RAM Lite SOM CM4102000 2GB RAM Lite CM4104000 4GB RAM Lite CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules CM4104032 4GB RAM 32GB emmc CM4108000 8GB RAM Lite CM4008016 8GB RAM 16Gb eMMc 2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - CM4S01000 1GB RAM Lite CM4S01008 1GB RAM 8GB eMMC Flash CM4S02000 2GB RAM Lite CM4S04000 4GB RAM Lite CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 CM4S08000 8GB RAM Lite 2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry 2021-48 Raspberry Pi 4 model B v1.5 2GB 2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 2024 Pi 5 2GB DDR4 version uses BCM2712D0 2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 2024 Pi 5 v1.1 2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board CM5004000 04GB RAM 0GB eMMC Lite CM5008000 08GB RAM 0GB eMMC Lite CM5016000 16GB RAM 0GB eMMC Lite 2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 2025 Pi5 1GB DDR4 announced 2022 PiOS linux goes 64bit 2024 Pi Trading IPO stockmarket stock exchange listing 2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom 2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 2026 Late July daily 64bit Pi3 LE little endian builds start 2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 2026 2027 2028 Pi 6 </pre> The vcgencmd can be used to inspect and dump the current system configuration. vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called "the firmware". Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc *spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid javascript] [https://github.com/6pac/SlickGrid SlickGrid typescript] [https://github.com/jspreadsheet/ce jspreadsheet ce] probably without xlsx support *presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support *ai office [https://github.com/dream-num/univer/ univer], [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] *weather [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast], [https://github.com/kaushalsahu07/weather weather needs API key], ==Future== [https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2], [https://github.com/Joshua-Riek/armbian-build Linux Armbian builds for old mobile devices], [], [https://tube.cadence.moe/ Cloudtube], [https://github.com/TeamPiped/documentation/blob/main/content/docs/public-instances/index.md TeamPiped], [], [], [], [https://hyperpipe.codeberg.page/ hyperpipe], [https://ytify.pp.ua/ ytify], [], [], [ ytdl], [https://github.com/golddominik893/liberatube liberatube] [https://git.lolcat.ca/lolcat/4get 4get], [https://github.com/hnhx/librex librex], [], [], {{BookCat}} ocimyrn2mpm2nwfkfv38hqpjkzizdgc Chess Opening Theory/1. e4/1...e6/2. d4/2...d5/3. exd5/3...exd5/4. Nf3 0 301163 4679803 4020733 2026-11-03T14:56:16Z Atiedebee 3523910 Updated templates and formatting. Added and described the main responses from Black. 4679803 wikitext text/x-wiki {{Chess Position |name=French defence: Exchange variation |eco=[[Chess/ECOC|C01]] |parent=[[../../|Exchange variation]] }} == 4. Nf3 == White develops the kingside knight in the standard position, allowing White to develop and make preparations for kingside castling. Black's next move depends on whether they will try to go for a draw, or try to fight for an advantage. '''[[/4...Nf6/]]''' keeps the status quo. Black keeps mirroring White and the game is likely to turn into a draw. '''[[/4...Bd6/]]''' is Black's attempt to break the symmetry. If White wants to try for an advantage, they should respond with 5. c4, which will lead to an asymmetrical pawn structure with fighting chances for both sides. If White tries to copy Black with 5. Bd3, Black can respond 5...Ne7, breaking the symmetry with the idea of going ...Bf5 to exchange light-squared bishops. '''[[/4...Nc6/]]''' is the most provocative line. If White responds with 5. Bd3, development will no longer be mirrored and Black has prospects of quickly castling queenside with an exciting game to follow. The main line, 5. Bb5, leads to a more complicated game for both sides. == Theory table == {{Chess Opening Theory/Table}} {{Chess/theory table |line1=4. ... Nf6 5. Bd3 Bd6 |line2=4. ... Bd6 5. c4 Nf6 |line3=4. ... Nc6 5. Bb5 Bd6 }} {{ChessMid}} ==References== {{Wikipedia|French Defence}} {{BCO2}} {{Chess Opening Theory/Footer}} nov2v012ktan82olog0vzk2vglwom8j Interesting social sciences/The law as science 0 378026 4679776 4114730 2026-11-03T12:47:18Z Sudrabens 3630297 Inserting comparison of Sheldon's body types 4679776 wikitext text/x-wiki The law as science is a system established by the State of norms and rules of behavior, fulfillment of which is ensured by force of State’s coercion. The law is a norm and the rule of behavior. Branches of criminal justice system (police, court, prison) must apply by sanctions to the culprit in case of violation of law. Corporal punishments (tortures and executions) served such legal sanctions in ancient times usually. The execution is replaced with life imprisonment in prison in modern democratic society often, and tortures are replaced with imprisonment for the term limited to the law, fine, confiscation of property, compensation of damage to the dissatisfied party and so on. But, nevertheless, law were built at the armed control of State over their citizens with antiquity before our days most frequently. Legal norms make behavior of people to a predictable, this is the function and the benefits of the law for society. Legal norms should not be contradictory each to other; otherwise citizens won't know what law citizens should perform. The State must to keep public order, to protect right to private property and free competition. The state has to stop rigidly all attempts of criminals to disturb public order. The state has to stop rigidly all attempts of criminals to seize somebody else’s property unlawfully. The state has to stop rigidly all attempts of criminals to prevent to other citizens to be engaged freely in business activity. People enter the relations in society inevitably, people sign economic contracts with each other, at the same time the state is a guarantor of the fact that both parties have to satisfy conditions of this contract that the violator of terms of the contract will be punished and this violator have to compensate losses to the dissatisfied party. All citizens shall have the identical rights. All citizens shall to keep law irrespectively of social status of these citizens. Even high-ranking officials and governors must keep the law and even governors shouldn't allow of cases of an arbitrariness and lawlessness in own activity. Only published laws should apply, otherwise, citizens will not know the laws for which they may be punished and the power will receive the right to arbitrariness. If a constitution exists in the country that even the governor is obliged to keep of the norms of this constitution. ===The laws as norms of behavior.=== Laws are adopted by the supreme bodies of the government. Laws are adopted by the King or the monarch with help of individual decision under tyranny, the kingdom or a hereditary monarchy, in such a way, for example, the king Hammurabi has accepted for the first time the code of laws known in the history. Laws are adopted under the aristocracy or oligarchy by the senate, a Boyar Duma, the Central Committee or the Politburo of the ruling Communist Party with help of vote of members of this ruling privileged meeting. laws are adopted by vote in people's assembly under direct democracy. Laws are adopted by parliament in the conditions of representative democracy. A hierarchy of laws and codes exist today. The code is a great number of the laws describing norms of behavior in some sphere of activity - in economy, the family sphere and so on. The most important laws are united in the constitution. Laws from other codes shouldn't contradict to constitutional norms. Laws from other codes become invalid according to the decision of the constitutional court in that case when the law from the code is contrary to the norms of the constitution. Along with laws, there are also other legal acts subordinated to laws: decrees of the president, government resolution, instruction, rule, orders and so on. That to live in society, that to make success in affairs, the person has to study lows. '''The causes of criminality.  '''     [[File:Lombroso.JPG|thumb|Cesare Lombroso]]      [[File:Ernst Kretschmer.jpg|thumb|Ernst Kretschmer]] [[File:Comparison of Sheldon's body types.jpg|thumb|Comparison of body types. Asthenic, athletic, pyknic body types.]] Many viewpoints exist on the causes of criminality in science.  Neil Smelser has allocated three approaches in decision of this difficult problem: * biological approach, * psychological approach, * sociological approach.           The essence of '''biological approach''' consist in the following:  the born criminal has the inclination to criminal behavior, the born criminal was born by thief and savage, the born criminal is able to do nothing else, a born criminal can only steal, rob and kill. Caesare Lombroso claimed within this approach that criminals are a result of degradation to earlier steps of human evolution. Cesare Lombroso named such external features of the born criminal, as the protruding lower jaw, rare beard and reduced sensitivity to pain. <ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> By the way, in my opinion, these features are most characteristic for speakers. Similarity of criminal with primitive savage is shown in the passion to tattoo, the weakness of mind and even in degradation of the handwriting accepting character of the hieroglyphic writing. Caesar Lombroso has allocated four types of criminals: murderer, thief, rapist and swindler. And this typology remains to this day. According to Henry H. Goddard, criminals are mentally retarded men, occurring from hereditarily burdened families. My experience of school teaching of criminals on lessons of history in women's prison shows that criminals have different levels of development of intellect like ordinary people from very low level of development of intellect before very high level of development of intellect. V ery high level of development of intellect was discovered at one thief‐women which was sentenced for that crime as thief‐women received trust of men. This thief‐women gave to drink to men vodka with sleeping pills, then this thief‐women plundered this men when this men have slept. This thief-women has remember each my word in lesson of history, each date, each name of hero for history, it is possible, the best memory is necessary feature of character of “thief on trust”.  Level of development of intellect affects to degree of the success of growth for thief’s qualifications.   Stages for such growth for thief’s qualifications exist:   • Specialization in apartment's burglaries.    • Specialization in Pocket thefts.    • Theft is based on trust of victim to criminal.             Thus, the opinion of Henry H. Goddard seems not entirely truth. From the point of view of the theory of "criminal psychodynamics", the criminal in own acts is guided not by mind but only emotions, the criminal is a psychopathic personality who has deviates from the norm, but the criminal isn't neither mentally sick, nor mentally retarded personality. Ernst Kretschmer have given the description of three main body types of man: • asthenic (thin, small, weak); • pyknic (stocky, fat), • athletic (muscular, large–boned); An athlete is person with the developed musculature, inclined to the organization of conflict.   A pyknic is person, inclined to obesity, which attempts to settle conflict with help of peaceful way.   Asthenic is thin person, which is potential victim in the conflict.        William Herbert Sheldon considered that the athletics are most inclined to the crimes. The genetic explanation of the reasons of crime consists that some criminals have chromosomes like XYY whereas ordinary men have chromosomes like XY, and ordinary women have chromosomes like XX. These people with chromosomes like XYY have frightening appearance, high growth and this people are heavy psychopaths sometimes.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> Sigmund Freud has entered concept "criminals with sense of guilt" within the framework of '''psychological approach''', this criminals wish that they were caught and punished because they feel own guilty because of their "inclination to destruction," they believe that imprisonment will help them overcome this inclination. <ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> The essence of '''sociological approach''' consists that the main reason of crime is that thieves are brought up in criminal group purposefully. Edwin Sutherland claimed that the prison corrects nobody, and prison is school of training in criminal behavior often. Émile Durkheim considered that the social anomie or, in other words, lawlessness, is the main reason for criminality in the period of social crisis.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> A similar period was in Russia during government of Mikhail Gorbachev and Boris Eltsin. The a main goal of Vladimir Putin became the establishing of order in the country, that to drive criminal world into an underground. The condition of an anomy is observed in big cities among teenagers where there is a mixture of various ethnic groups to the different systems of values. Robert King Merton considered that the gap between the purposes and the approved means of their achievement is the reason of crime, for example, the purpose is financial success, and means is receiving the higher education, but paid education is often inaccessible today therefore some people can use illegal ways of enrichment.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> According to the theory of stigmatization of Howard S. Becker, influential groups are capable to put stigma of criminal on members of less influential groups and thus train them to consider themselves criminals. For example, whites did with African Americans in the United States this way.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> From the point of view of Marxism and radical criminologists, criminals are rebels against capitalist exploitation.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> The example of such "rebel" is Joseph Stalin who had 6 criminal records for extortion and 5 escapes from exile. It is possible to draw a conclusion that all these theories are partly true and crime is a consequence of many causes. ===An empirical study of the causes of criminality.=== My preliminary forecast before the empirical researches consisted that a potential criminal is the speaker. This forecast has found partial confirmation, but it has turned out that speakers are capable besides that to show resourcefulness, speakers know how to engage other personality types in a criminal group, speakers are able to use of other personality types as performers of own criminal plans, then speakers are capable to avoid criminal punishment and speakers are capable to shift all fault for crimes on other personality types. There is a specialization in the criminal world in various roles, such as organizer, performer, accessory and instigator. Thief in law in Russia is an example of the organizer of the high qualification. Skilled in thieves' affairs speaker is capable to play a role of the organizer. The inexperienced speaker or the technician approach for a role of the performer. A principle: "You mustn't to be by a performer!" esist in criminal world, because performers are arrested by first of all then the performer is obliged under thieves' laws to take all fault on himself and the performer mustn't betray of other members of criminal group, otherwise performer can be killed in prison. The role of the performer is the most unprofitable in comparison with other roles. The psychologist and the speaker can undertake role of the instigator, at the same time the speaker forces of performer to commit to crime by means of threats, and the psychologist persuades by performer to commit to crime by means of deception and cunning, thus, the speaker and psychologist use different coercion methods. The role of the accessory is carried out of different the personality types, for example the technician is capable to make high-quality weapon, the speaker is capable to sell stolen property. Psychologist and speaker are able to provide information about candidates of potential victims of robberies and their property status at apartment's burglaries. The psychologist knows how to rub into the trust of potential victims. By the way, my research has shown that, unlike orders in men's prisons, women having the status of thiefs in law do not exist in women's corrective labor colony of strict regimen and high hierarchy doesn't exist among the prisoner-women. The speaker and the psychologist approach for a role of the drug dealer. The technician can play a role of the cruel killer-executioner or killer-sniper because of inclination of the technician to insensibility and low emotionality. The speaker has the highest inclination to be by leader of criminal world, to make all kinds of serious crimes and to improve thieves' skills, speaker has inclination to adventurism and thoughtless behavior, readiness to submit to pressure of criminal group and inability to foresee heavy consequences of own crimes. This inclination of the speaker to criminal behavior is shown at young age and in state of intoxication especially brightly. The psychologist is the potential victim of crime often because the psychologist provoke of criminals involuntarily thanks to peculiar for psychologists weakness of character. A woman-psychologist provokes involuntarily of a rapist to rape due to the fact that the woman-psychologist has the highest degree of sexuality. This my research was conducted on the basis of women's corrective labor colony of strict regimen of UT 389/28 in town Berezniki during the period from November 2003 to March 2004. The status of colony was changed at the end of this period – the strict regimen was changed on a ordinary regimen. The informal unstructured interview (35 respondents) and the included observation in the course of training of prisoner in 8 and 9 classes of middle school (15 respondents) became forms of carrying out a research. Total, 50 prisoner-women were interviewed and subjected to observation by means of casual selection. 40% were by psychologists, 20% were by technicians, 40% were speakers from this prisoner-women, theorists were not founded among prisoner-women. That to appear in this colony and to conduct a research, I had to get a job of the teacher of history in this prison's school. The generalized results of my research are given in the table given below: {| class="wikitable" |- ! Different categories of prisoners. !! Quantity of prisoners. !! Shares of speakers among prisoners. !! Shares of technicians among prisoners. !! Shares of psychologists among prisoners. |- | 1. Shares of the personality types in this colony. || 50 people.|| 40% || 20% || 40% |- | 2. Prisoners, сonvicted of robbery according to article 162 for criminal code of Russian Federation. || 8 people. || 62% || 25% || 13% |- | 3. Prisoners, сonvicted of causing grievous bodily harm without death of victim according to article 111 of item 1,2,3 of criminal code of Russian Federation.|| 11 people.|| 73% || 18% || 9% |- | 4. The prisoners, сonvicted of causing heavy harm to health with the death of victim according to article 111 of item 4 of criminal code of Russian Federation.|| 0% || 40% || 60% |- | 5. Prisoners, сonvicted of premeditated murder (malice aforethought) according to article 105 of criminal code of Russian Federation. ||10 people. || 30% || 40% || 30% |- | 6. Prisoner, сonvicted of illegal manufacturing, sale, storage and transportation of drugs according to article 228 of criminal code of Russian Federation. || 17 people. || 47% || 6% || 47% |- | 7. Prisoners, сonvicted of theft according to article 158 of criminal code of Russian Federation. || 26 people. || 35% || 23% || 42% |- | 8. Prisoners-drug addicts, сonvicted of illegal manufacturing, sale, storage and transportation of drugs or prisoners-drug addicts, сonvicted of theft according to articles 228 or 158 of criminal code of Russian Federation.. || 13 people. || 45% || 10% || 45% |- | 9. Prisoners-drug addicts, sick HIV, condemned for illegal manufacturing, sale, storage and transportation of drugs according to article 228 of criminal code of Russian Federation. || 2 people. || 50% || 0% || 50% |- | 10. Prisoners, сonvicted of the apartment's thefts according to article 158 of criminal code of Russian Federation. || 9 people. || 33% || 22% || 45% |- | 11. Prisoners, сonvicted of the theft from the pockets according to article 158 of criminal code of Russian Federation. || 2 people. || 50$ || 0% || 50% |- | 12. Prisoners, сonvicted of theft on trust with use of сlophelinum according to article 158 of criminal code of Russian Federation. || 1 people. || 100% || 0% || 0% |- | 13. Prisoners, сonvicted of group crimes. || 25 people. || 52% || 12% || 36% |- | 14. Prisoners, who committed of crimes alone. || 13 people. || 31% || 15% || 54% |- | 15. Prisoners, сonvicted of domestic crimes. ||12 people. || 33% || 42% || 25% |- | 16. Prisoners which hold lead positions among other prisoners in colony – brigadier, the man on duty, chairman of the Council of the Detachment Team.||3 people. || 100% || 0% || 0% |- | 17 Prisoners which consisted in legal or civil marriage. || 24 people. || 20% || 20% || 60% |- | 18. Prisoners which have own children.||22 people. || 14% || 32% || 54% |- | 19. Prisoners which killed of own husband. || 4 people. || 50% || 50% || 0% |- | 20. Average quantity of criminal records to one prisoner. || 50 people. || 2,5 || 2,3 || 2,4 |} It is possible to draw the following conclusions on the basis of these results of a research. Speakers have the highest status in colony. Speakers have the biggest inclination to group crimes though all prisoner-women have noted that prisoner-women executed orders of the man-recidivist in criminal group. Re-education of the speaker is the most difficult task that finds manifestation that the speaker has the most large average amount of criminal records on one prisoner among the personality types. The task of re-education of the speaker is complicated by those circumstances that speaker has the worst marital status – speaker marries more rare, speaker has of children less often than other personality types, speaker has high inclination to the use of drugs, to alcoholism and high probability to ache with HIV. Psychologists specialize in crimes on sale of drugs and apartment's burglaries. Psychologists have high inclination to fall into a state of passion and psychologists have high inclination to finish of victim in the course of causing grievous bodily harm, but psychologists have low inclination to robbery. Psychologists are most of all inclined to commit of crimes alone rather than in a group. The task of re-education of the psychologist is complicated by his inclination to the use of drugs, high probability to ache with HIV. Task of re-education of the psychologist is facilitated by a relatively good marital situation – psychologist marries and psychologist has children more often than others others personality types. Technicians are inclined to commission of crimes much less than other personality types. Technicians make only 20% of prisoners. But technicians have high inclination to commission of deliberate and unintentional domestic murders (malice aforethought murders and manslaughter), technicians are capable to kill as the executioner and to show cold loss of consciousness to agonal sufferings of the victim. Process of their re-education is facilitated by low inclination to the use of drugs and quite good marital status. 1 technician and 1 psychologist have two criminal records for murder each that is an example of unique cruelty. All women of Romani people (5 women) were psychologists and women of Romani people specialize in sale of drugs – 60%, in thefts - 20% and in premeditated murders (malice aforethought) - 20%. A knife (84% of cases), the axe (8% of cases), the noose of (4% of cases}, a rolling pin (4% of cases) have served as the crime tool in 24 cases of women crimes. ===The question about necessity of the capital punishment=== [[File:Exécution de Marie Antoinette le 16 octobre 1793.jpg|right|thumb|300px|Marie Antoinette's execution on October 16, 1793]] [[File:Execution robespierre, saint just....jpg|thumb|right|The execution of Maximilien Robespierre]]       [[File:Badische Guillotine.JPG|right|thumb|250px| Guillotine]] Punishment for the crimes connected with use of violence became much more strict under the new Russian criminal code. The top limits of punishment are raised from 15 to 20 years and to life imprisonment. Russian Federation keeps of conditions of the moratorium on the capital punishment, though such punishment as the capital punishment is prescribed in the criminal code for the most serious crimes, but courts replace of capital punishment to life imprisonment. It is connected with fear to make fatal mistake of justice when a theoretical opportunity remains to sentence of innocent person to death penalty. It is impossible already to return to life of the innocent person in case of detection of such mistake of justice after enforcement of sentence about capital punishment. For example, it has become clear during the investigation of criminal case of the serial killer Andrei Chikatilo who has killed about 50 people that the court has sentenced to capital punishment for one of these murders of innocent person who was executed already. According to sociological polls, most of residents of Russia are sure of need of the capital punishment, especially in connection with threat of the Chechen terrorism. Most of residents of Russia are sure of need of application of the capital punishment to those terrorists who blew up houses in Moscow, Volgodonsk and Buynaksk which cut off heads of russian prisoner of war in Chechnya. To abolish of capital punishment is absurdity during war. Region of Upper river Kama (the cities of Solikamsk, Berezniki, Krasnovishersk, Kizel) was turned into the prison region at the Soviet power. One of leaders of the Chechen terrorists – Salman Raduyev – was sentenced to life imprisonment and Salman Raduyev served sentence in Solikamsk supermax prison "White Swan". Salman Raduyev said in one of an interview that Salman Raduyev hopes to serve sentence in supermax prison 25 years, to receive amnesty and to be released, but Salman Raduyev has died in a year on December 14, 2002 in hospital from old wounds. To survive in prison is very difficult for the former terrorist. Prisoners and security guards put pressure upon terrorist also. Almost all squad of the Perm OMON (Special Purpose Police Unit) – 43 militiamen (from them 32 were killed in battle, and 11 were captured and executed with special cruelty) has died in one of the ambushes made by the Chechen terrorists. This event has taken place on March 29, 2000. It is possible to understand hostility of security guards to the condemned terrorists in these conditions. Many leaders of the Chechen terrorists – Dzhokhar Dudayev, Shamil Basayev, Ibn al-Khattab, Aslan Maskhadov was killed with help of special operations. It is possible to abolish of capital punishment in civilized Europe, but it is impossible to abolish of capital punishment in criminal Russia. The capital punishment remains even in the USA. When the prisoner was sentenced to capital punishment, the prisoner can choose a way execution in the USA – a lethal injection, an electrocution, firing squad, hanging or gas inhalation, and relatives of the victim have an opportunity to watch for this procedure of an execution with help of cable television. ==Michel Foucault about the prison’s reform== [[File:Dieric Bouts 013.jpg|thumb|right|Quartering]]  [[File:Lamanie kolem L 001xx.jpg|thumb|upright|Breaking wheel]] '''Prison’s reform''' Michel Foucault has described a cruel execution of Robert-François Damiens on March 2, 1757 at the beginning of own book "Discipline and Punish: The Birth of the Prison". <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> Prisons in modern understanding have appeared eighty years later after this execution, and a time-table was drawn up in prison for young prisoners already. Prisoners were obliged to work 9 hours in day in workshops, prisoners were obliged to study 2 hours in day in prison school. So, public execution were complemented with imprisonment and a prison day schedule. Public execution and imprisonment became different types of punishment in Europe and America. The prison was just the place earlier where the criminal was interrogated and tortured, and then criminal waited an execution here. The prison became the place of life and work for the prisoner after reform on strict time-table where the prisoner spent a long term of imprisonment. These punishments have become applicable for different kinds of crime and for different types of criminals. This reform was carried out in period just under 100 years. New codes provided new kinds of punishment during this time: in Russia – in 1769, in Prussia – in 1780, In Pennsylvania and Tuscany – in 1786, in Austria – 1788, in France – in 1791, 1808 and 1810.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> '''The essence of prison’s reform (since the late 18th century until the early 19th century) consisted in following:  ''' * Public executions and tortures were cancelled, * Accurate codes, uniform rules of legal proceedings, jury trial were introduced, * The corrective character of the penalty, assignment of various terms of imprisonment and kinds of punishment depending on weight of crime were introduced. Only flogging remain still some time in Russia, Austria and Prussia. * The brand disappeared on the criminal's face or shoulder. A certain discretion has arisen in the art of inflicting pain. The body as the major target of penal repression disappeared. * Amende honorable and pillory were cancelled. * Use of convicts at public works was cancelled – at repair of roads when convicts were chained in shackles and iron collars and convicts exchanged with crowd by curses in response on contempt from this crowd. * Chain-gang were cancelled. While the chain-gang, which had dragged convicts across the whole of France, as far as Brest and Toulon was replaced in 1837 by inconspicuous black-painted cell-carts. This cell-carts was prison on wheels. The central corridor divides of cell-carts on all length, six single cells exist on each side of the corridor where prisoners sit facing a corridor. Legs and hands of criminals are chained by a chain. An iron door with a small window was between a corridor and cell that prevents to communication between prisoners on the way. There are two security guards armed by clubs in a corridor. Punishment had gradually ceased to be a spectacle, a rite and a show for gapers gradually.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> ===Reasons of the abolition of public executions:=== * The execution exceed in savagery the crime itself. * The execution accustomed of spectators to a ferocity from which execution wished to divert them. * The execution makes of the executioner resemble a criminal. The execution makes judges resemble murderers. * The execution caused of admiration and pity to the executed criminal instead of contempt and hatred. Conclusion: Punishment becomes the most hidden part of the penal process gradually. Effectiveness of punishment is seen as resulting from its inevitability, not from its visible intensity. <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> Powers began to apply imprisonment, confinement, forced labour, penal servitude, prohibition from entering certain areas, deportation instead of tortures and executions during modern times.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> Imprisonment is connected somewhat with physical suffering too unlike penalties, but intolerable corporal pain is not connected with criminal penalty any more already. The whole army of warders, doctors, chaplains, psychiatrists, psychologists, educationalists comes to replace the executioner as to the specialist in causing pain.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> ===The shortcomings of modern imprisonment:=== * Imprisonment has no effect on the public. * Imprisonment is incapable of corresponding to the specificity of crimes. * Imprisonment is costly. * Imprisonment maintains convicts in idleness, Imprisonment multiplies their vices. * Work of the jailer is an exercise of tyranny.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART TWO PUNISHMENT. Chapter 2. The gentle way in punishment. Page 114. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> ===Panopticon=== [[File:Panopticon.jpg |thumb|   Elevation, section and plan of Jeremy Bentham's Panopticon penitentiary, drawn by Willey Reveley, 1791 ]]    Possibility of the round-the-clock supervision of prisoners is here a main goal of construction of Panopticon prison according to the plan of Jeremy Bentham. This prison represents the round or crosswise building, for example, Kresty Prison in St. Petersburg represents several crosswise buildings. The central tower is in the center of such building where a supervisor settles down. A supervisor has an opportunity to observe through wide windows for life of prisoners in cells which are located around the circumference of the building as in an aquarium or in a zoo. Two windows exist in each cell, one window comes to light, the second big window leaves inside therefore the cell is looked through. Only one criminal has to sit in each cell that to avoid by bad influence from prisoners at each other. Walls between cell prevent to communication between prisoners. Therefore there is no of danger of a plot, planning of collective escape and the planning of new crimes for the future. This structure of the building of prison is opposite to the principle of a dungeon. Constant supervision eliminates the need for corporal punishment to some extent too. Modern technical means allow to provide constant supervision over prisoners in cells not by means of a special structure of the building of prison, and by means of video supervision. Such projects of prisons as Panopticon are still too expensive for Russia. The available prisons are overcrowded beyond any measure, closeness and insanitary conditions exist in cells in Russia today.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART THREE DISCIPLINE. Chapter 3. Panopticism. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> ===Two systems of keeping of criminals in prison in the West=== Powers in the West wanted to interfere with association of criminals in prison in criminal community. Two systems of keeping of criminals in prison were invented for this purpose in the USA: * '''Auburn system''' in the 19th century which prescribes keeping of the prisoners in individual cell at night, work and meals in common in the afternoon, as in the monastery, but on condition of absolute silence. Prisoners can speak only with warders. * '''Pennsylvania system''' (Separate system) provides keeping of prisoners in the conditions of absolute isolation from each other in the solitary cell that to leave of criminal alone with own conscience. There were discussions about an opportunity to pay of work of prisoners and a possibility of the prisoner to refuse from some kinds of works and to organize of strike.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART FOUR PRISON. Chapter 1. Complete and austere institutions . https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> ===Arguments of opponents of prison reform and of replacement of executions and torture to imprisonment:=== * The prison organizes training of inexperienced criminals to "thieves' professions" and transformation of inexperienced criminals into professional criminals. * Criminals plan future crimes in prison, сriminals plan organization of escapes from prison and collective prison revolts. * Prisons do not diminish the crime rate. Prisons can be extended, multiplied or transformed, the quantity of crime and criminals remains stable or, worse, increases. * Detention causes recidivism, those leaving prison have more chance than before of going back to it. Existence in prison is way of life for recidivists. Recidivists get used to not taking care about food and housing, job and livelihood in prison. * The prison cannot fail to produce delinquents. It does so by the very type of existence that it imposes on its inmates: whether they are isolated in cells or whether they are given useless work. Between 1,000 and 1,500 convicts live under the surveillance of between thirty and forty supervisors, who can preserve some kind of security only by depending on informers. * The prison makes possible, even encourages, the organization of a milieu of delinquents, loyal to one another, hierarchized, ready to aid and abet any future criminal act. The prison gives to "thieves' profession and the prison learns to be the informer. Сriminals find themselves after release from prison in such conditions which doom of criminals to crime repetition. Criminals lose residence during the inprisonment and criminals become homeless tramps after an exit from prison. Imprisonment dooms of family of the criminal to poverty after detention of the only breadwinner. As a result the son of the thief becomes by thief too frequently that leads to new crimes eventually. <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART FOUR PRISON. Chapter 2. Illegalities and delinquency. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> Conclusions: In my opinion, the prison has many shortcomings, but the prison can't be cancelled. It is impossible to return to tortures and executions because such return contradicts to the principles of humanity. Besides, corporal punishments remain in prison system today to some extent. Corporal punishments are the great invention of mankind too and corporal punishments can't be cancelled too completely because such people exist on which only corporal punishments act. It is impossible to replace corporal punishments to administrative punishments completely, that is it is impossible to replace corporal punishments to conversion of the person from the status "free person" to status of "prisoner". The attempt to replace corporal punishments and an executions to administrative punishments (imprisonment) was not quite successful because this attempt has led to emergence of new problems which weren't earlier. If Gleb Zheglov from the movie "The Meeting Place Cannot Be Changed" was guided the principle that "the thief has to be imprisoned" at any cost, then earlier the judge was guided by the principle: the place of recidivists – on the gallows at any cost. Therefore it was possible to reduce number of recidivists with help of executions, it was possible to destroy criminal hierarchy with help of an executions of leaders of criminal world, it was possible to interfere to process of training of the inexperienced criminals to thieves' professions because executions reduced number of similar "teachers" really. The execution of notorious villains allows to reduce costs on keeping of criminals to a minimum. Besides, the execution of terrorists and maniacs allows to satisfy sense of justice at relatives of the victims on the ancient law of retaliation – "Eye for an eye", these relatives are forced to commit murder of the criminal from revenge and these relatives are forced to be exposed to criminal prosecution today sometimes. This example shows that cancellation of any social invention, even corporal punishments and the capital punishment leads to emergence of big problems always. === Citations and references=== {{Reflist}} {{BookCat}} r5xutusjx77j58whspkug9zgktl49lg 4679864 4679776 2026-11-04T01:06:15Z CommonsDelinker 49843 Removing [[:c:File:Comparison_of_Sheldon's_body_types.jpg|Comparison_of_Sheldon's_body_types.jpg]], it has been deleted from Commons by [[:c:User:Thuresson|Thuresson]] because: Recreation of content deleted per community consensus ([[:c:COM:CSD#G4|G4]]): 4679864 wikitext text/x-wiki The law as science is a system established by the State of norms and rules of behavior, fulfillment of which is ensured by force of State’s coercion. The law is a norm and the rule of behavior. Branches of criminal justice system (police, court, prison) must apply by sanctions to the culprit in case of violation of law. Corporal punishments (tortures and executions) served such legal sanctions in ancient times usually. The execution is replaced with life imprisonment in prison in modern democratic society often, and tortures are replaced with imprisonment for the term limited to the law, fine, confiscation of property, compensation of damage to the dissatisfied party and so on. But, nevertheless, law were built at the armed control of State over their citizens with antiquity before our days most frequently. Legal norms make behavior of people to a predictable, this is the function and the benefits of the law for society. Legal norms should not be contradictory each to other; otherwise citizens won't know what law citizens should perform. The State must to keep public order, to protect right to private property and free competition. The state has to stop rigidly all attempts of criminals to disturb public order. The state has to stop rigidly all attempts of criminals to seize somebody else’s property unlawfully. The state has to stop rigidly all attempts of criminals to prevent to other citizens to be engaged freely in business activity. People enter the relations in society inevitably, people sign economic contracts with each other, at the same time the state is a guarantor of the fact that both parties have to satisfy conditions of this contract that the violator of terms of the contract will be punished and this violator have to compensate losses to the dissatisfied party. All citizens shall have the identical rights. All citizens shall to keep law irrespectively of social status of these citizens. Even high-ranking officials and governors must keep the law and even governors shouldn't allow of cases of an arbitrariness and lawlessness in own activity. Only published laws should apply, otherwise, citizens will not know the laws for which they may be punished and the power will receive the right to arbitrariness. If a constitution exists in the country that even the governor is obliged to keep of the norms of this constitution. ===The laws as norms of behavior.=== Laws are adopted by the supreme bodies of the government. Laws are adopted by the King or the monarch with help of individual decision under tyranny, the kingdom or a hereditary monarchy, in such a way, for example, the king Hammurabi has accepted for the first time the code of laws known in the history. Laws are adopted under the aristocracy or oligarchy by the senate, a Boyar Duma, the Central Committee or the Politburo of the ruling Communist Party with help of vote of members of this ruling privileged meeting. laws are adopted by vote in people's assembly under direct democracy. Laws are adopted by parliament in the conditions of representative democracy. A hierarchy of laws and codes exist today. The code is a great number of the laws describing norms of behavior in some sphere of activity - in economy, the family sphere and so on. The most important laws are united in the constitution. Laws from other codes shouldn't contradict to constitutional norms. Laws from other codes become invalid according to the decision of the constitutional court in that case when the law from the code is contrary to the norms of the constitution. Along with laws, there are also other legal acts subordinated to laws: decrees of the president, government resolution, instruction, rule, orders and so on. That to live in society, that to make success in affairs, the person has to study lows. '''The causes of criminality.  '''     [[File:Lombroso.JPG|thumb|Cesare Lombroso]]      [[File:Ernst Kretschmer.jpg|thumb|Ernst Kretschmer]] Many viewpoints exist on the causes of criminality in science.  Neil Smelser has allocated three approaches in decision of this difficult problem: * biological approach, * psychological approach, * sociological approach.           The essence of '''biological approach''' consist in the following:  the born criminal has the inclination to criminal behavior, the born criminal was born by thief and savage, the born criminal is able to do nothing else, a born criminal can only steal, rob and kill. Caesare Lombroso claimed within this approach that criminals are a result of degradation to earlier steps of human evolution. Cesare Lombroso named such external features of the born criminal, as the protruding lower jaw, rare beard and reduced sensitivity to pain. <ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> By the way, in my opinion, these features are most characteristic for speakers. Similarity of criminal with primitive savage is shown in the passion to tattoo, the weakness of mind and even in degradation of the handwriting accepting character of the hieroglyphic writing. Caesar Lombroso has allocated four types of criminals: murderer, thief, rapist and swindler. And this typology remains to this day. According to Henry H. Goddard, criminals are mentally retarded men, occurring from hereditarily burdened families. My experience of school teaching of criminals on lessons of history in women's prison shows that criminals have different levels of development of intellect like ordinary people from very low level of development of intellect before very high level of development of intellect. V ery high level of development of intellect was discovered at one thief‐women which was sentenced for that crime as thief‐women received trust of men. This thief‐women gave to drink to men vodka with sleeping pills, then this thief‐women plundered this men when this men have slept. This thief-women has remember each my word in lesson of history, each date, each name of hero for history, it is possible, the best memory is necessary feature of character of “thief on trust”.  Level of development of intellect affects to degree of the success of growth for thief’s qualifications.   Stages for such growth for thief’s qualifications exist:   • Specialization in apartment's burglaries.    • Specialization in Pocket thefts.    • Theft is based on trust of victim to criminal.             Thus, the opinion of Henry H. Goddard seems not entirely truth. From the point of view of the theory of "criminal psychodynamics", the criminal in own acts is guided not by mind but only emotions, the criminal is a psychopathic personality who has deviates from the norm, but the criminal isn't neither mentally sick, nor mentally retarded personality. Ernst Kretschmer have given the description of three main body types of man: • asthenic (thin, small, weak); • pyknic (stocky, fat), • athletic (muscular, large–boned); An athlete is person with the developed musculature, inclined to the organization of conflict.   A pyknic is person, inclined to obesity, which attempts to settle conflict with help of peaceful way.   Asthenic is thin person, which is potential victim in the conflict.        William Herbert Sheldon considered that the athletics are most inclined to the crimes. The genetic explanation of the reasons of crime consists that some criminals have chromosomes like XYY whereas ordinary men have chromosomes like XY, and ordinary women have chromosomes like XX. These people with chromosomes like XYY have frightening appearance, high growth and this people are heavy psychopaths sometimes.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> Sigmund Freud has entered concept "criminals with sense of guilt" within the framework of '''psychological approach''', this criminals wish that they were caught and punished because they feel own guilty because of their "inclination to destruction," they believe that imprisonment will help them overcome this inclination. <ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> The essence of '''sociological approach''' consists that the main reason of crime is that thieves are brought up in criminal group purposefully. Edwin Sutherland claimed that the prison corrects nobody, and prison is school of training in criminal behavior often. Émile Durkheim considered that the social anomie or, in other words, lawlessness, is the main reason for criminality in the period of social crisis.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> A similar period was in Russia during government of Mikhail Gorbachev and Boris Eltsin. The a main goal of Vladimir Putin became the establishing of order in the country, that to drive criminal world into an underground. The condition of an anomy is observed in big cities among teenagers where there is a mixture of various ethnic groups to the different systems of values. Robert King Merton considered that the gap between the purposes and the approved means of their achievement is the reason of crime, for example, the purpose is financial success, and means is receiving the higher education, but paid education is often inaccessible today therefore some people can use illegal ways of enrichment.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> According to the theory of stigmatization of Howard S. Becker, influential groups are capable to put stigma of criminal on members of less influential groups and thus train them to consider themselves criminals. For example, whites did with African Americans in the United States this way.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> From the point of view of Marxism and radical criminologists, criminals are rebels against capitalist exploitation.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> The example of such "rebel" is Joseph Stalin who had 6 criminal records for extortion and 5 escapes from exile. It is possible to draw a conclusion that all these theories are partly true and crime is a consequence of many causes. ===An empirical study of the causes of criminality.=== My preliminary forecast before the empirical researches consisted that a potential criminal is the speaker. This forecast has found partial confirmation, but it has turned out that speakers are capable besides that to show resourcefulness, speakers know how to engage other personality types in a criminal group, speakers are able to use of other personality types as performers of own criminal plans, then speakers are capable to avoid criminal punishment and speakers are capable to shift all fault for crimes on other personality types. There is a specialization in the criminal world in various roles, such as organizer, performer, accessory and instigator. Thief in law in Russia is an example of the organizer of the high qualification. Skilled in thieves' affairs speaker is capable to play a role of the organizer. The inexperienced speaker or the technician approach for a role of the performer. A principle: "You mustn't to be by a performer!" esist in criminal world, because performers are arrested by first of all then the performer is obliged under thieves' laws to take all fault on himself and the performer mustn't betray of other members of criminal group, otherwise performer can be killed in prison. The role of the performer is the most unprofitable in comparison with other roles. The psychologist and the speaker can undertake role of the instigator, at the same time the speaker forces of performer to commit to crime by means of threats, and the psychologist persuades by performer to commit to crime by means of deception and cunning, thus, the speaker and psychologist use different coercion methods. The role of the accessory is carried out of different the personality types, for example the technician is capable to make high-quality weapon, the speaker is capable to sell stolen property. Psychologist and speaker are able to provide information about candidates of potential victims of robberies and their property status at apartment's burglaries. The psychologist knows how to rub into the trust of potential victims. By the way, my research has shown that, unlike orders in men's prisons, women having the status of thiefs in law do not exist in women's corrective labor colony of strict regimen and high hierarchy doesn't exist among the prisoner-women. The speaker and the psychologist approach for a role of the drug dealer. The technician can play a role of the cruel killer-executioner or killer-sniper because of inclination of the technician to insensibility and low emotionality. The speaker has the highest inclination to be by leader of criminal world, to make all kinds of serious crimes and to improve thieves' skills, speaker has inclination to adventurism and thoughtless behavior, readiness to submit to pressure of criminal group and inability to foresee heavy consequences of own crimes. This inclination of the speaker to criminal behavior is shown at young age and in state of intoxication especially brightly. The psychologist is the potential victim of crime often because the psychologist provoke of criminals involuntarily thanks to peculiar for psychologists weakness of character. A woman-psychologist provokes involuntarily of a rapist to rape due to the fact that the woman-psychologist has the highest degree of sexuality. This my research was conducted on the basis of women's corrective labor colony of strict regimen of UT 389/28 in town Berezniki during the period from November 2003 to March 2004. The status of colony was changed at the end of this period – the strict regimen was changed on a ordinary regimen. The informal unstructured interview (35 respondents) and the included observation in the course of training of prisoner in 8 and 9 classes of middle school (15 respondents) became forms of carrying out a research. Total, 50 prisoner-women were interviewed and subjected to observation by means of casual selection. 40% were by psychologists, 20% were by technicians, 40% were speakers from this prisoner-women, theorists were not founded among prisoner-women. That to appear in this colony and to conduct a research, I had to get a job of the teacher of history in this prison's school. The generalized results of my research are given in the table given below: {| class="wikitable" |- ! Different categories of prisoners. !! Quantity of prisoners. !! Shares of speakers among prisoners. !! Shares of technicians among prisoners. !! Shares of psychologists among prisoners. |- | 1. Shares of the personality types in this colony. || 50 people.|| 40% || 20% || 40% |- | 2. Prisoners, сonvicted of robbery according to article 162 for criminal code of Russian Federation. || 8 people. || 62% || 25% || 13% |- | 3. Prisoners, сonvicted of causing grievous bodily harm without death of victim according to article 111 of item 1,2,3 of criminal code of Russian Federation.|| 11 people.|| 73% || 18% || 9% |- | 4. The prisoners, сonvicted of causing heavy harm to health with the death of victim according to article 111 of item 4 of criminal code of Russian Federation.|| 0% || 40% || 60% |- | 5. Prisoners, сonvicted of premeditated murder (malice aforethought) according to article 105 of criminal code of Russian Federation. ||10 people. || 30% || 40% || 30% |- | 6. Prisoner, сonvicted of illegal manufacturing, sale, storage and transportation of drugs according to article 228 of criminal code of Russian Federation. || 17 people. || 47% || 6% || 47% |- | 7. Prisoners, сonvicted of theft according to article 158 of criminal code of Russian Federation. || 26 people. || 35% || 23% || 42% |- | 8. Prisoners-drug addicts, сonvicted of illegal manufacturing, sale, storage and transportation of drugs or prisoners-drug addicts, сonvicted of theft according to articles 228 or 158 of criminal code of Russian Federation.. || 13 people. || 45% || 10% || 45% |- | 9. Prisoners-drug addicts, sick HIV, condemned for illegal manufacturing, sale, storage and transportation of drugs according to article 228 of criminal code of Russian Federation. || 2 people. || 50% || 0% || 50% |- | 10. Prisoners, сonvicted of the apartment's thefts according to article 158 of criminal code of Russian Federation. || 9 people. || 33% || 22% || 45% |- | 11. Prisoners, сonvicted of the theft from the pockets according to article 158 of criminal code of Russian Federation. || 2 people. || 50$ || 0% || 50% |- | 12. Prisoners, сonvicted of theft on trust with use of сlophelinum according to article 158 of criminal code of Russian Federation. || 1 people. || 100% || 0% || 0% |- | 13. Prisoners, сonvicted of group crimes. || 25 people. || 52% || 12% || 36% |- | 14. Prisoners, who committed of crimes alone. || 13 people. || 31% || 15% || 54% |- | 15. Prisoners, сonvicted of domestic crimes. ||12 people. || 33% || 42% || 25% |- | 16. Prisoners which hold lead positions among other prisoners in colony – brigadier, the man on duty, chairman of the Council of the Detachment Team.||3 people. || 100% || 0% || 0% |- | 17 Prisoners which consisted in legal or civil marriage. || 24 people. || 20% || 20% || 60% |- | 18. Prisoners which have own children.||22 people. || 14% || 32% || 54% |- | 19. Prisoners which killed of own husband. || 4 people. || 50% || 50% || 0% |- | 20. Average quantity of criminal records to one prisoner. || 50 people. || 2,5 || 2,3 || 2,4 |} It is possible to draw the following conclusions on the basis of these results of a research. Speakers have the highest status in colony. Speakers have the biggest inclination to group crimes though all prisoner-women have noted that prisoner-women executed orders of the man-recidivist in criminal group. Re-education of the speaker is the most difficult task that finds manifestation that the speaker has the most large average amount of criminal records on one prisoner among the personality types. The task of re-education of the speaker is complicated by those circumstances that speaker has the worst marital status – speaker marries more rare, speaker has of children less often than other personality types, speaker has high inclination to the use of drugs, to alcoholism and high probability to ache with HIV. Psychologists specialize in crimes on sale of drugs and apartment's burglaries. Psychologists have high inclination to fall into a state of passion and psychologists have high inclination to finish of victim in the course of causing grievous bodily harm, but psychologists have low inclination to robbery. Psychologists are most of all inclined to commit of crimes alone rather than in a group. The task of re-education of the psychologist is complicated by his inclination to the use of drugs, high probability to ache with HIV. Task of re-education of the psychologist is facilitated by a relatively good marital situation – psychologist marries and psychologist has children more often than others others personality types. Technicians are inclined to commission of crimes much less than other personality types. Technicians make only 20% of prisoners. But technicians have high inclination to commission of deliberate and unintentional domestic murders (malice aforethought murders and manslaughter), technicians are capable to kill as the executioner and to show cold loss of consciousness to agonal sufferings of the victim. Process of their re-education is facilitated by low inclination to the use of drugs and quite good marital status. 1 technician and 1 psychologist have two criminal records for murder each that is an example of unique cruelty. All women of Romani people (5 women) were psychologists and women of Romani people specialize in sale of drugs – 60%, in thefts - 20% and in premeditated murders (malice aforethought) - 20%. A knife (84% of cases), the axe (8% of cases), the noose of (4% of cases}, a rolling pin (4% of cases) have served as the crime tool in 24 cases of women crimes. ===The question about necessity of the capital punishment=== [[File:Exécution de Marie Antoinette le 16 octobre 1793.jpg|right|thumb|300px|Marie Antoinette's execution on October 16, 1793]] [[File:Execution robespierre, saint just....jpg|thumb|right|The execution of Maximilien Robespierre]]       [[File:Badische Guillotine.JPG|right|thumb|250px| Guillotine]] Punishment for the crimes connected with use of violence became much more strict under the new Russian criminal code. The top limits of punishment are raised from 15 to 20 years and to life imprisonment. Russian Federation keeps of conditions of the moratorium on the capital punishment, though such punishment as the capital punishment is prescribed in the criminal code for the most serious crimes, but courts replace of capital punishment to life imprisonment. It is connected with fear to make fatal mistake of justice when a theoretical opportunity remains to sentence of innocent person to death penalty. It is impossible already to return to life of the innocent person in case of detection of such mistake of justice after enforcement of sentence about capital punishment. For example, it has become clear during the investigation of criminal case of the serial killer Andrei Chikatilo who has killed about 50 people that the court has sentenced to capital punishment for one of these murders of innocent person who was executed already. According to sociological polls, most of residents of Russia are sure of need of the capital punishment, especially in connection with threat of the Chechen terrorism. Most of residents of Russia are sure of need of application of the capital punishment to those terrorists who blew up houses in Moscow, Volgodonsk and Buynaksk which cut off heads of russian prisoner of war in Chechnya. To abolish of capital punishment is absurdity during war. Region of Upper river Kama (the cities of Solikamsk, Berezniki, Krasnovishersk, Kizel) was turned into the prison region at the Soviet power. One of leaders of the Chechen terrorists – Salman Raduyev – was sentenced to life imprisonment and Salman Raduyev served sentence in Solikamsk supermax prison "White Swan". Salman Raduyev said in one of an interview that Salman Raduyev hopes to serve sentence in supermax prison 25 years, to receive amnesty and to be released, but Salman Raduyev has died in a year on December 14, 2002 in hospital from old wounds. To survive in prison is very difficult for the former terrorist. Prisoners and security guards put pressure upon terrorist also. Almost all squad of the Perm OMON (Special Purpose Police Unit) – 43 militiamen (from them 32 were killed in battle, and 11 were captured and executed with special cruelty) has died in one of the ambushes made by the Chechen terrorists. This event has taken place on March 29, 2000. It is possible to understand hostility of security guards to the condemned terrorists in these conditions. Many leaders of the Chechen terrorists – Dzhokhar Dudayev, Shamil Basayev, Ibn al-Khattab, Aslan Maskhadov was killed with help of special operations. It is possible to abolish of capital punishment in civilized Europe, but it is impossible to abolish of capital punishment in criminal Russia. The capital punishment remains even in the USA. When the prisoner was sentenced to capital punishment, the prisoner can choose a way execution in the USA – a lethal injection, an electrocution, firing squad, hanging or gas inhalation, and relatives of the victim have an opportunity to watch for this procedure of an execution with help of cable television. ==Michel Foucault about the prison’s reform== [[File:Dieric Bouts 013.jpg|thumb|right|Quartering]]  [[File:Lamanie kolem L 001xx.jpg|thumb|upright|Breaking wheel]] '''Prison’s reform''' Michel Foucault has described a cruel execution of Robert-François Damiens on March 2, 1757 at the beginning of own book "Discipline and Punish: The Birth of the Prison". <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> Prisons in modern understanding have appeared eighty years later after this execution, and a time-table was drawn up in prison for young prisoners already. Prisoners were obliged to work 9 hours in day in workshops, prisoners were obliged to study 2 hours in day in prison school. So, public execution were complemented with imprisonment and a prison day schedule. Public execution and imprisonment became different types of punishment in Europe and America. The prison was just the place earlier where the criminal was interrogated and tortured, and then criminal waited an execution here. The prison became the place of life and work for the prisoner after reform on strict time-table where the prisoner spent a long term of imprisonment. These punishments have become applicable for different kinds of crime and for different types of criminals. This reform was carried out in period just under 100 years. New codes provided new kinds of punishment during this time: in Russia – in 1769, in Prussia – in 1780, In Pennsylvania and Tuscany – in 1786, in Austria – 1788, in France – in 1791, 1808 and 1810.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> '''The essence of prison’s reform (since the late 18th century until the early 19th century) consisted in following:  ''' * Public executions and tortures were cancelled, * Accurate codes, uniform rules of legal proceedings, jury trial were introduced, * The corrective character of the penalty, assignment of various terms of imprisonment and kinds of punishment depending on weight of crime were introduced. Only flogging remain still some time in Russia, Austria and Prussia. * The brand disappeared on the criminal's face or shoulder. A certain discretion has arisen in the art of inflicting pain. The body as the major target of penal repression disappeared. * Amende honorable and pillory were cancelled. * Use of convicts at public works was cancelled – at repair of roads when convicts were chained in shackles and iron collars and convicts exchanged with crowd by curses in response on contempt from this crowd. * Chain-gang were cancelled. While the chain-gang, which had dragged convicts across the whole of France, as far as Brest and Toulon was replaced in 1837 by inconspicuous black-painted cell-carts. This cell-carts was prison on wheels. The central corridor divides of cell-carts on all length, six single cells exist on each side of the corridor where prisoners sit facing a corridor. Legs and hands of criminals are chained by a chain. An iron door with a small window was between a corridor and cell that prevents to communication between prisoners on the way. There are two security guards armed by clubs in a corridor. Punishment had gradually ceased to be a spectacle, a rite and a show for gapers gradually.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> ===Reasons of the abolition of public executions:=== * The execution exceed in savagery the crime itself. * The execution accustomed of spectators to a ferocity from which execution wished to divert them. * The execution makes of the executioner resemble a criminal. The execution makes judges resemble murderers. * The execution caused of admiration and pity to the executed criminal instead of contempt and hatred. Conclusion: Punishment becomes the most hidden part of the penal process gradually. Effectiveness of punishment is seen as resulting from its inevitability, not from its visible intensity. <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> Powers began to apply imprisonment, confinement, forced labour, penal servitude, prohibition from entering certain areas, deportation instead of tortures and executions during modern times.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> Imprisonment is connected somewhat with physical suffering too unlike penalties, but intolerable corporal pain is not connected with criminal penalty any more already. The whole army of warders, doctors, chaplains, psychiatrists, psychologists, educationalists comes to replace the executioner as to the specialist in causing pain.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> ===The shortcomings of modern imprisonment:=== * Imprisonment has no effect on the public. * Imprisonment is incapable of corresponding to the specificity of crimes. * Imprisonment is costly. * Imprisonment maintains convicts in idleness, Imprisonment multiplies their vices. * Work of the jailer is an exercise of tyranny.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART TWO PUNISHMENT. Chapter 2. The gentle way in punishment. Page 114. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> ===Panopticon=== [[File:Panopticon.jpg |thumb|   Elevation, section and plan of Jeremy Bentham's Panopticon penitentiary, drawn by Willey Reveley, 1791 ]]    Possibility of the round-the-clock supervision of prisoners is here a main goal of construction of Panopticon prison according to the plan of Jeremy Bentham. This prison represents the round or crosswise building, for example, Kresty Prison in St. Petersburg represents several crosswise buildings. The central tower is in the center of such building where a supervisor settles down. A supervisor has an opportunity to observe through wide windows for life of prisoners in cells which are located around the circumference of the building as in an aquarium or in a zoo. Two windows exist in each cell, one window comes to light, the second big window leaves inside therefore the cell is looked through. Only one criminal has to sit in each cell that to avoid by bad influence from prisoners at each other. Walls between cell prevent to communication between prisoners. Therefore there is no of danger of a plot, planning of collective escape and the planning of new crimes for the future. This structure of the building of prison is opposite to the principle of a dungeon. Constant supervision eliminates the need for corporal punishment to some extent too. Modern technical means allow to provide constant supervision over prisoners in cells not by means of a special structure of the building of prison, and by means of video supervision. Such projects of prisons as Panopticon are still too expensive for Russia. The available prisons are overcrowded beyond any measure, closeness and insanitary conditions exist in cells in Russia today.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART THREE DISCIPLINE. Chapter 3. Panopticism. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> ===Two systems of keeping of criminals in prison in the West=== Powers in the West wanted to interfere with association of criminals in prison in criminal community. Two systems of keeping of criminals in prison were invented for this purpose in the USA: * '''Auburn system''' in the 19th century which prescribes keeping of the prisoners in individual cell at night, work and meals in common in the afternoon, as in the monastery, but on condition of absolute silence. Prisoners can speak only with warders. * '''Pennsylvania system''' (Separate system) provides keeping of prisoners in the conditions of absolute isolation from each other in the solitary cell that to leave of criminal alone with own conscience. There were discussions about an opportunity to pay of work of prisoners and a possibility of the prisoner to refuse from some kinds of works and to organize of strike.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART FOUR PRISON. Chapter 1. Complete and austere institutions . https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> ===Arguments of opponents of prison reform and of replacement of executions and torture to imprisonment:=== * The prison organizes training of inexperienced criminals to "thieves' professions" and transformation of inexperienced criminals into professional criminals. * Criminals plan future crimes in prison, сriminals plan organization of escapes from prison and collective prison revolts. * Prisons do not diminish the crime rate. Prisons can be extended, multiplied or transformed, the quantity of crime and criminals remains stable or, worse, increases. * Detention causes recidivism, those leaving prison have more chance than before of going back to it. Existence in prison is way of life for recidivists. Recidivists get used to not taking care about food and housing, job and livelihood in prison. * The prison cannot fail to produce delinquents. It does so by the very type of existence that it imposes on its inmates: whether they are isolated in cells or whether they are given useless work. Between 1,000 and 1,500 convicts live under the surveillance of between thirty and forty supervisors, who can preserve some kind of security only by depending on informers. * The prison makes possible, even encourages, the organization of a milieu of delinquents, loyal to one another, hierarchized, ready to aid and abet any future criminal act. The prison gives to "thieves' profession and the prison learns to be the informer. Сriminals find themselves after release from prison in such conditions which doom of criminals to crime repetition. Criminals lose residence during the inprisonment and criminals become homeless tramps after an exit from prison. Imprisonment dooms of family of the criminal to poverty after detention of the only breadwinner. As a result the son of the thief becomes by thief too frequently that leads to new crimes eventually. <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART FOUR PRISON. Chapter 2. Illegalities and delinquency. https://zulfahmed.files.wordpress.com/2013/12/disciplineandpunish.pdf </ref> Conclusions: In my opinion, the prison has many shortcomings, but the prison can't be cancelled. It is impossible to return to tortures and executions because such return contradicts to the principles of humanity. Besides, corporal punishments remain in prison system today to some extent. Corporal punishments are the great invention of mankind too and corporal punishments can't be cancelled too completely because such people exist on which only corporal punishments act. It is impossible to replace corporal punishments to administrative punishments completely, that is it is impossible to replace corporal punishments to conversion of the person from the status "free person" to status of "prisoner". The attempt to replace corporal punishments and an executions to administrative punishments (imprisonment) was not quite successful because this attempt has led to emergence of new problems which weren't earlier. If Gleb Zheglov from the movie "The Meeting Place Cannot Be Changed" was guided the principle that "the thief has to be imprisoned" at any cost, then earlier the judge was guided by the principle: the place of recidivists – on the gallows at any cost. Therefore it was possible to reduce number of recidivists with help of executions, it was possible to destroy criminal hierarchy with help of an executions of leaders of criminal world, it was possible to interfere to process of training of the inexperienced criminals to thieves' professions because executions reduced number of similar "teachers" really. The execution of notorious villains allows to reduce costs on keeping of criminals to a minimum. Besides, the execution of terrorists and maniacs allows to satisfy sense of justice at relatives of the victims on the ancient law of retaliation – "Eye for an eye", these relatives are forced to commit murder of the criminal from revenge and these relatives are forced to be exposed to criminal prosecution today sometimes. This example shows that cancellation of any social invention, even corporal punishments and the capital punishment leads to emergence of big problems always. === Citations and references=== {{Reflist}} {{BookCat}} epl34hhupqqnvkaf91sbrl9esg3t6u1 Wikijunior:Transport Alphabet/T 110 405826 4679783 4671718 2026-11-03T13:19:32Z ~2026-58523-79 3630299 /* */ 4679783 wikitext text/x-wiki <div style="text-align: center; font-size: 400%;">'''T''' is for '''T'''rain重播)星期六、日 17:00 - 19:00 <br/> [[File:Kyushu Shinkansen 800 series Shin-Minamata 20041123.jpg|center|500px]] <br/> {{ {{BOOKTEMPLATE}} }} hm44amwp1sxivzs4yp5fwlzs8nkpo1r 4679787 4679783 2026-11-03T13:22:10Z NDG 3510220 [[WB:REVERT|Reverted]] edit by [[Special:Contributions/~2026-58523-79|~2026-58523-79]] ([[User talk:~2026-58523-79|talk]]) to last version by Saroj 4345553 wikitext text/x-wiki <div style="text-align: center; font-size: 400%;">'''T''' is for '''T'''rain</div> <br/> [[File:Kyushu Shinkansen 800 series Shin-Minamata 20041123.jpg|center|500px]] <br/> {{ {{BOOKTEMPLATE}} }} cf8dqzdb0s6djvc177bphjlxwrbjveh Create Vampires 0 415358 4679936 4679659 2026-11-04T11:32:51Z 3MMPEYTON 3393808 4679936 wikitext text/x-wiki <br>''Create Vampires'' is a book intended as a guide to avoid literary pitfalls, and as a nonfiction resource for those fascinated by vampires. This book examines vampires through a cultural, literary, and historical lens to help writers create authentic vampire narratives. == Vampires ''Of The Imagination'' == Although vampires are creatures of folklore, monsters from the ''afterlife'' that are sometimes called the "undead," vampires are uniquely different from ghost, those lingering spirits who refuse to die. Although vampires, by definition, are animated corpses, most vampires ''of the imagination'' must feed on human blood in order to continue their earthly existence. This unique quality makes vampires a popular and original type of fiction, slightly different from other creatures found in folklore. Because of their unique characteristics, vampires have become massively popular in popular culture and in literature. We hope this book will clear up many misconceptions, and common misunderstandings associated with the "undead," especially a common confusion ''about'' the actual people who did inspire vampire folklore, verses the evolved horror creations called vampires of the imagination. '''Create Vampires''' aims to treat vampires as a cultural, literary and historical construct. Perhaps ''Create Vampires'' should be considered a friendly craft-manual for building a believable vampire concept, available across different medias. == Preface: The Factual Roots Of Vampires == <br /> {| class="wikitable" |- ! Factual Basis For Vampires? |- | [[/Factual Basis For Vampires/]] is a special page intended to offer information about the factual bases for vampires. |} <br> '''What Type Of Book Is This?''' <br /> {| class="wikitable" |- ! '''Create Vampires''' is one of many free Wikibooks |- | Wikibooks.org is a part of the Wikimedia project. Writers and contributors are volunteers who cull through websites, <BR> use online search engines to find facts, and volunteer to work on special projects that are open to the public. <BR> Volunteers are people who write, edit, and help people understand the powerful tools at their fingertips. <br> |} <br> "You shall not eat the blood of any flesh at all, because the life of the flesh is in the blood, and whosoever eateth it shall be cut off." - The Bible, Leviticus, chapter 17, verse 14. <br> <br> {| class="wikitable" |- ! Edvard Munch - Love and Pain / Vampire (1895) || "Les Vampires" |- | [[File:Edvard Munch - Vampire (1895) - Google Art Project.jpg|thumb|Edvard Munch - Vampire (1895) - Google Art Project]] || [[File:Les vampires.jpg|thumb|Les vampires]] |} == All About Vampires == '''Create Vampires''' {| class="wikitable" |- ! Table Of Content |- | Introduction: [[Create Vampires/Original Fictional Creations|"Original Fictional Creations"]] |- | Proper Spelling: [[Create Vampires/Vam-Pai-Yer|"How do you spell vampire?]] |- | [[Create Vampires/Alternative Spelling| "Alternative Spellings"]] |- | What ''Is'' A Vampire? [[Create Vampires/A Definition For Vampire|Create Vampires /A Definition For Vampire - Wikibooks, open books for an open world]] |- | Why Create A Vampire? : [[Create Vampires/Why Create Vampires|Create Vampires/Why Create Vampires - Wikibooks, open books for an open world]] |- |- '''Cultural Origins''' |- |'''Cultural Vampire Construct''' |- |What Is A Cultural Construct? - [[Create Vampires/Cultural Construct|Create Vampires/Cultural Construct - Wikibooks, open books for an open world]] |- | '''Vampire Folklore:''' [[Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes|Create Vampires/Historical And Cross Cultural Origins Of Vampire Archetypes - Wikibooks]] |- | African Folklore: [[Create Vampires/African Folklore|Create Vampires/African Folklore - Wikibooks, open books for an open world]] |- | Latin-American Folklore: [[Create Vampires/Latin American Folklore|Create Vampires/Latin American Folklore - Wikibooks, open books for an open world]] |- | Asian Folklore: [[Create Vampires/Asian Folklore#Asian Folklore|Create Vampires/Asian Folklore - Wikibooks, open books for an open world]] |- |[[Create Vampires/Asian Folklore Part Two|Create Vampires/Asian Folklore Part Two - Wikibooks, open books for an open world]] |- |Eastern Folklore: [[Create Vampires/Eastern European Folklore| "Eastern European Folklore"]] |- | Eastern Folklore: [[Create Vampires/Dracula Behind Vlad-The Impaler|Create Vampires/Dracula Behind Vlad-The Impaler - Wikibooks, open books for an open world]] |- |Oceanian Folklore: [[Create Vampires/Oceanian Folklore|Create Vampires/Oceanian Folklore - Wikibooks, open books for an open world]] |- |[[Create Vampires/How Cultural Traditions Shaped Vampire Traits|Create Vampires/How Cultural Traditions Shaped Vampire Traits - Wikibooks, open books for an open world]] |- |[[Create Vampires/Precursors To Modern Vampires|Create Vampires/Precursors To Modern Vampires - Wikibooks, open books for an open world]] |- |- '''Literary Construct''' |- |'''Literary Construct''' |- |[[Create Vampires/Literary Construction|Create Vampires/Literary Construction - Wikibooks, open books for an open world]] |- |What Is A Literary Trope? [[Create Vampires/What Is A Literary Trope]] |- | Literary And Media Pitfalls To Avoid: [[Create Vampires/Examples Of Literary Pitfalls|Create Vampires/Examples Of Literary Pitfalls - Wikibooks, open books for an open world]] |- | Authors Who Created Influential Vampires Of The Imagination: [[Create Vampires/Authors Who Created Vampire Tropes]] |- | [[Create Vampires/writers who did not create vampires| "Writers Who Did Not Create Vampires"]] |- |[[Create Vampires/Vampires In Poetry|Create Vampires/Vampires In Poetry - Wikibooks, open books for an open world]] |- |[[Create Vampires/Vampire Historic Fiction|Create Vampires/Vampire Historic Fiction - Wikibooks, open books for an open world]] |- |[[Create Vampires/Dracula|Create Vampires/Dracula - Wikibooks, open books for an open world]] |- |[[Create Vampires/How Popular Are Vampires|Create Vampires/How Popular Are Vampires - Wikibooks, open books for an open world]] |- | Popular Culture: [[Create Vampires/Vampires In Popular Culture|Create Vampires/Vampires In Popular Culture - Wikibooks, open books for an open world]] |- | Vampire Memes? [[Create Vampires/Vampires Memes|Create Vampires/Vampires Memes - Wikibooks, open books for an open world]] |- |'''Are Vampires Real? Historical Construct''' [[Create Vampires/What Is A Historical Construct|Create Vampires/What Is A Historical Construct - Wikibooks, open books]] |- |[[Create Vampires/Factual Basis For Vampires]] |- |[[Create Vampires/Historical Construction|Create Vampires/Historical Construction - Wikibooks, open books for an open world]] |- |History of Vampires: [[Create Vampires/Vampire History]] |- | [[Create Vampires/Scientific Evidence| "Science and Vampirism"]] |- | For Vampires: [[Create Vampires/Scientific Evidence For Vampires| "Scientific Evidence For Vampires"]] |- | Against Vampires: [[Create Vampires/Scientific Evidence Against Vampirism| "Scientific Evidence Against Vampires"]] |- |- Are Vampires Real? Historical Construct |- | [[Create Vampires/Ethics Of Creating Vampire Lore|Create Vampires/Ethics Of Creating Vampire Lore - Wikibooks, open books for an open world]] |- |'''Women As Vampires:''' [[Create Vampires/Women As Vampires|Create Vampires/Women As Vampires - Wikibooks, open books for an open world]] |- | Closing: [[Create Vampires/All About Vampires|Create Vampires /All About Vampires - Wikibooks, open books for an open world]] |- | Information for Spanish speakers: [[:es:Vampiro|"Vampiro"]] |- | Writing Tips: [[Create Vampires/Writing Vampire Prose| "Writing Vampire Prose"]] |- |Public Domain Primary Sources: [[Create Vampires/PublicDomainPrimarySources]] |- | [[:Category:Book:Create Vampires|List of All Pages in This Book]] |} == Reference == {{WikipediaCredit}} <br /> {{Shelves|Literature|Paranormal|Cultural anthropology}} {{Status|100%}} 6aizpt4eutna7ssqy7dqqmhp1is8rdf Wikijunior:Bird Alphabet/D 110 419705 4679782 4673982 2026-11-03T13:18:31Z ~2026-58523-79 3630299 /* */ 4679782 wikitext text/x-wiki <div style="text-align: center; font-size: 400%;">'''D''' is for '''D'''uck<(重播) 星期六至日 23:30 - 00:30 [[File:Coin-img_2219.jpg|500px|center|A duck]] {{Template:Wikijunior:Bird Alphabet}} {{BookCat}} ekd9woka8bi6psp9stbk35smwiu0lci 4679785 4679782 2026-11-03T13:22:10Z NDG 3510220 [[WB:REVERT|Reverted]] edit by [[Special:Contributions/~2026-58523-79|~2026-58523-79]] ([[User talk:~2026-58523-79|talk]]) to last version by EggRoll97 3996939 wikitext text/x-wiki <div style="text-align: center; font-size: 400%;">'''D''' is for '''D'''uck</div> [[File:Coin-img_2219.jpg|500px|center|A duck]] {{Template:Wikijunior:Bird Alphabet}} {{BookCat}} 2vwsqiyz2ao6du71qgcdiwfdlk5ta9e Wikijunior:Bird Alphabet/U 110 419707 4679784 4671711 2026-11-03T13:20:27Z ~2026-58523-79 3630299 /* */ 4679784 wikitext text/x-wiki <div style="text-align: center; font-size: 400%;">'''U''' is for '''U'''mbrellabird重播) 星期一至五 18:00-19:00 [[File:Cotingidae_-_Cephalopterus_penduliger.jpg|300px|center|An Umbrellabird]] {{Template:Wikijunior:Bird Alphabet}} {{BookCat}} 7h1uslyur76q2p6l5fcgdbdvte2gcsf 4679786 4679784 2026-11-03T13:22:10Z NDG 3510220 [[WB:REVERT|Reverted]] edit by [[Special:Contributions/~2026-58523-79|~2026-58523-79]] ([[User talk:~2026-58523-79|talk]]) to last version by Saroj 3996956 wikitext text/x-wiki <div style="text-align: center; font-size: 400%;">'''U''' is for '''U'''mbrellabird</div> [[File:Cotingidae_-_Cephalopterus_penduliger.jpg|300px|center|An Umbrellabird]] {{Template:Wikijunior:Bird Alphabet}} {{BookCat}} oetgsrwdvxho0cj36x2zlotzo04vptu Interesting social sciences/Jurisprudence 0 436824 4679777 4245953 2026-11-03T12:49:40Z Sudrabens 3630297 Inserting comparison of Sheldon's body types 4679777 wikitext text/x-wiki https://www.youtube.com/watch?v=AMCYrKAh8-I&ab_channel=%D0%92%D0%B0%D0%BB%D0%B5%D1%80%D0%B8%D0%B9%D0%A1%D1%82%D0%B0%D1%80%D0%B8%D0%BA%D0%BE%D0%B2 The causes of criminality. English subtitles exist in this video. On the cover is a thief named Yaponchik (Vyacheslav Ivankov). https://www.youtube.com/watch?v=gHjD4w2Msps&ab_channel=%D0%92%D0%B0%D0%BB%D0%B5%D1%80%D0%B8%D0%B9%D0%A1%D1%82%D0%B0%D1%80%D0%B8%D0%BA%D0%BE%D0%B2 Michel Foucault on prison reform. English subtitles exist in this video. Valery Starikov Interesting social studies. On the cover is a still from the film "Gentlemen of Fortune." The law is a system established by the State of norms and rules of behavior, fulfillment of which is ensured by force of State’s coercion. State-enforced laws are norms and the rules of behavior. Branches of criminal justice system (police, court, prison) must apply by sanctions to the culprit in case of violation of law. Corporal punishments (tortures and executions) served such legal sanctions in ancient times usually. The execution were replaced by life imprisonment in prison in modern democratic society often, and tortures were replaced by imprisonment for the term limited to the law, tortures were replaced by fine, confiscation of property, compensation of damage to the injured party and so on. But, nevertheless, law were built at the armed control of State over their citizens with antiquity before our days most frequently. Legal norms make behavior of people to a predictable, this is the function and the benefits of the law for society. Legal norms should not be contradictory each to other; otherwise, citizens may find themselves in a difficult situation and citizens will not know what law they should perform. The State must to keep public order, to protect right to private property and free competition. The state has to stop rigidly all attempts of criminals to disturb public order. The state has to stop rigidly all attempts of criminals to seize somebody else’s property unlawfully. The state has to stop rigidly all attempts of criminals to prevent to other citizens to be engaged freely in business activity. People enter the relations in society inevitably, people sign economic contracts with each other, at the same time the state is a guarantor of the fact that both parties have to satisfy conditions of this contract that the violator of terms of the contract will be punished and this violator have to compensate losses to the injured party. All citizens shall have the identical rights. All citizens shall to keep law irrespectively of social status of these citizens. Even high-ranking officials and rulers must keep the law and even rulers shouldn't allow of cases of an arbitrariness and lawlessness in own activity. Only published laws should apply, otherwise, citizens will not know the laws for which they may be punished and the power will receive the right to arbitrariness. If a constitution exists in the country that even the ruler is obliged to keep of the norms of this constitution. ===The state-enforced laws as norms of behavior.=== The state-enforced laws are adopted by the supreme bodies of the government. Laws are adopted by the king or the monarch with help of individual decision under tyranny, the kingdom or a hereditary monarchy, in such a way, for example, the king Hammurabi has accepted for the first time the code of laws known in the history. The state-enforced laws are adopted under the aristocracy or oligarchy by the senate, a Boyar Duma, the Central Committee or the Politburo of the ruling Communist Party with help of vote of members of this ruling privileged meeting. The state-enforced laws are adopted by vote in people's assembly under direct democracy. The state-enforced laws are adopted by parliament in the conditions of representative democracy. A hierarchy of the state-enforced laws and codes exist today. The code is a great number of the the state-enforced laws describing norms of behavior in some sphere of activity - in economy, the family sphere and so on. The most important the state-enforced laws are united in the constitution. The state-enforced laws from other codes shouldn't contradict to constitutional norms. The state-enforced laws from other codes become invalid according to the decision of the constitutional court in that case when the state-enforced law from the code is contrary to the norms of the constitution. Along with the state-enforced laws, there are also other legal acts subordinated to laws: decrees of the president, government regulations, instruction, rule, orders and so on. That to live in society, that to make success in affairs, the person has to study the state-enforced laws. '''The causes of criminality.  '''     [[File:Lombroso.JPG|thumb|Cesare Lombroso]]      [[File:Ernst Kretschmer.jpg|thumb|Ernst Kretschmer]] [[File:Comparison of Sheldon's body types.jpg|alt=somatotype|thumb|Comparison of body types. Asthenic, athletic, pyknic body types.]] Many viewpoints exist on the causes of criminality in science.  Neil Smelser has allocated three approaches in decision of this difficult problem: * biological approach, * psychological approach, * sociological approach.           The essence of '''biological approach''' consist in the following:  the born criminal has the inclination to criminal behavior, the born criminal was born by thief and savage, the born criminal is able to do nothing else, a born criminal can only steal, rob and kill. Caesare Lombroso claimed within this approach that criminals are a result of degradation to earlier stages of human evolution. Cesare Lombroso named such external features of the born criminal, as the protruding lower jaw, rare beard and reduced sensitivity to pain. <ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> By the way, in my opinion, these features are most characteristic for speakers on personality type. Similarity of criminal with primitive savage is shown in the passion to tattoo, the weakness of mind and even in degradation of the handwriting similar to hieroglyphic writing. Caesar Lombroso has allocated four types of criminals: murderer, thief, rapist and swindler. And this typology remains to this day. According to Henry H. Goddard, criminals are mentally retarded men, occurring from hereditarily burdened families. My experience of school teaching of criminals on lessons of history in women's prison shows that criminals have different levels of development of intellect like ordinary people from very low level of development of intellect before very high level of development of intellect. Very high level of development of intellect was discovered at one thief‐women which received trust of men. she drank of men by vodka with sleeping pills and she robbed of men when men were sleeping. This thief-women has remember each my word in my lesson on history, each date, each name of hero of history, it is possible, the best memory is necessary feature of character of “thief on trust”.  Level of development of intellect affects to degree of the success of growth for thief’s qualifications.   Stages for such growth for thief’s qualifications exist:   • Specialization on apartment's burglaries.    • Specialization on pocket thefts.    • Theft is based on trust of victim to criminal.             Thus, the opinion of Henry H. Goddard seems not entirely truth. From the point of view of the theory of "criminal psychodynamics", the criminal in own acts is guided not by mind but only emotions, the criminal is a psychopathic personality who has deviates from the norm, but the criminal isn't neither mentally sick, nor mentally retarded personality. Ernst Kretschmer have given the description of three main body types of man: • asthenic (tall and thin); • pyknic (stocky, fat), • athletic (with advanced musculature); An athlete is person with the developed musculature, inclined to the organization of conflict.   A pyknic is person, inclined to obesity, which attempts to settle conflict with help of peaceful way.   Asthenic is thin person, which is potential victim in the conflict.        William Herbert Sheldon considered that the athletics are most inclined to the crimes. The genetic explanation of the reasons of crime consists that some criminals have chromosomes like XYY whereas ordinary men have chromosomes like XY, and ordinary women have chromosomes like XX. These people with chromosomes like XYY have frightening appearance, high growth and this people are heavy psychopaths sometimes.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> Sigmund Freud has entered concept "criminals with sense of guilt" within the framework of '''psychological approach''', this criminals wish that they were caught and punished because this criminals feel own guilty because of their "inclination to destruction," this criminals believe that imprisonment will help them overcome this inclination. <ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> The essence of '''sociological approach''' consists that the main reason of crime is that thieves are brought up in criminal group purposefully. Edwin Sutherland claimed that the prison corrects nobody, and prison is school of training in criminal behavior often. Émile Durkheim considered that the social anomie or, in other words, lawlessness, is the main reason for criminality in the period of social crisis.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> A similar period was in Russia during government of Mikhail Gorbachev and Boris Eltsin. The a main goal of Vladimir Putin became the establishing of order in the country, that to drive of criminal world into an underground. The condition of an anomy is observed in big cities among teenagers where there is a mixture of various ethnic groups to the different systems of values. Robert King Merton considered that the gap between the purposes and the approved means of their achievement is the reason of crime, for example, the purpose is financial success, and means is receiving the higher education, but paid education is often inaccessible today therefore some people can use illegal ways of enrichment.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> According to the theory of stigmatization of Howard S. Becker, influential groups are capable to put stigma of criminal on members of less influential groups and thus influential groups train of members of less influential groups to consider themselves by criminals. For example, whites did with African Americans in the United States this way.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> From the point of view of Marxism and radical criminologists, criminals are rebels against capitalist exploitation.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> The example of such "rebel" is Joseph Stalin who had 6 criminal records for extortion and 5 escapes from exile. It is possible to draw a conclusion that all these theories are partly true and crime is a consequence of many causes. ===An empirical study of the causes of criminality.=== My preliminary forecast before the empirical researches consisted that a potential criminal is the speaker. This forecast has found partial confirmation, but it has turned out that speakers are capable besides that to show resourcefulness, speakers know how to engage other personality types in a criminal group, speakers are able to use of other personality types as performers of own criminal plans, then speakers are capable to avoid criminal punishment and speakers are capable to shift all fault for crimes on other personality types. There is a specialization in the criminal world in various roles, such as organizer, executor, helper and instigator. Thief in law in Russia is an example of the organizer of the high qualification. Skilled in thieves' affairs speaker is capable to play a role of the organizer. The inexperienced speaker or the technician approach for a role of executor. A principle: "You mustn't to be by a executor!" exists in criminal world, because executors are arrested by first of all then the executor is obliged according to thieves' laws to take all fault on himself and executor mustn't betray of other members of criminal group, otherwise executor can be killed in prison. The role of the executor is the most unprofitable in comparison with other roles. The psychologist and the speaker can undertake role of the instigator, at the same time the speaker forces of executor to commit to crime by means of threats, and the psychologist persuades by executor to commit to crime by means of deception and cunning, thus, the speaker and psychologist use different coercion methods. The role of the helper is carried out different the personality types, for example the technician is capable to make high-quality weapon, the speaker is capable to sell stolen property. Psychologist and speaker are able to provide information about candidates of potential victims of robberies and about their property status at apartment's burglaries. The psychologist knows how to rub into the trust to potential victims. By the way, my research has shown that, unlike rules in men's prisons, women having the status of thiefs in law do not exist in women's corrective labor colony of strict regimen and high hierarchy doesn't exist among the prisoner-women. The speaker and the psychologist approach for a role of the drug dealer. The technician can play a role of the cruel killer-executioner or killer-sniper because of inclination of the technician to insensibility and low emotionality. The speaker has the highest inclination to be by leader of criminal world, to make all kinds of serious crimes and to improve thieves' skills, speaker has inclination to adventurism and frivolous behavior, readiness to submit to pressure of criminal group and inability to foresee heavy consequences of own crimes. This inclination of the speaker to criminal behavior is shown at young age and in state of intoxication especially brightly. The psychologist is the potential victim of crime often because the psychologist provoke of criminals involuntarily thanks to peculiar for psychologists weakness of character. A woman-psychologist provokes involuntarily of a rapist to rape due to the fact that the woman-psychologist has the highest degree of sexuality. This my research was conducted on the basis of women's corrective labor colony of strict regimen of UT 389/28 in town Berezniki during the period from November 2003 to March 2004. The status of colony was changed at the end of this period – the strict regimen was changed on a ordinary regimen. The informal unstructured interview (35 respondents) and the included observation in the course of training of prisoner in 8 and 9 classes of middle school (15 respondents) became forms of carrying out a research. Total, 50 prisoner-women were interviewed and subjected to observation by means of casual selection. 40% were by psychologists, 20% were by technicians, 40% were speakers from this prisoner-women, theorists were not found among prisoner-women. That to appear in this colony and to conduct a research, I had to get a job of the teacher of history in this prison's school. The generalized results of my research are given in the table given below: {| class="wikitable" |- ! Different categories of prisoners. !! Quantity of prisoners. !! Shares of speakers among prisoners. !! Shares of technicians among prisoners. !! Shares of psychologists among prisoners. |- | 1. Shares of the personality types in this colony. || 50 people.|| 40% || 20% || 40% |- | 2. Prisoners, сonvicted for robbery according to article 162 of criminal code of Russian Federation. || 8 people. || 62% || 25% || 13% |- | 3. Prisoners, сonvicted for causing grievous bodily harm without death of victim according to article 111 of item 1,2,3 of criminal code of Russian Federation.|| 11 people.|| 73% || 18% || 9% |- | 4. The prisoners, сonvicted for causing heavy harm to health with the death of victim according to article 111 of item 4 of criminal code of Russian Federation.|| 0% || 40% || 60% |- | 5. Prisoners, сonvicted for premeditated murder (malice aforethought) according to article 105 of criminal code of Russian Federation. ||10 people. || 30% || 40% || 30% |- | 6. Prisoners, сonvicted for illegal manufacturing, sale, storage and transportation of drugs according to article 228 of criminal code of Russian Federation. || 17 people. || 47% || 6% || 47% |- | 7. Prisoners, сonvicted for theft according to article 158 of criminal code of Russian Federation. || 26 people. || 35% || 23% || 42% |- | 8. Prisoners-drug addicts, сonvicted for illegal manufacturing, sale, storage and transportation of drugs or prisoners-drug addicts, сonvicted for theft according to articles 228 or 158 of criminal code of Russian Federation.. || 13 people. || 45% || 10% || 45% |- | 9. Prisoners-drug addicts, sick HIV, condemned for illegal manufacturing, sale, storage and transportation of drugs according to article 228 of criminal code of Russian Federation. || 2 people. || 50% || 0% || 50% |- | 10. Prisoners, сonvicted for the apartment's thefts according to article 158 of criminal code of Russian Federation. || 9 people. || 33% || 22% || 45% |- | 11. Prisoners, сonvicted for the theft from the pockets according to article 158 of criminal code of Russian Federation. || 2 people. || 50$ || 0% || 50% |- | 12. Prisoners, сonvicted for theft on trust with use of сlophelinum according to article 158 of criminal code of Russian Federation. || 1 people. || 100% || 0% || 0% |- | 13. Prisoners, сonvicted for group crimes. || 25 people. || 52% || 12% || 36% |- | 14. Prisoners, who committed for crimes alone. || 13 people. || 31% || 15% || 54% |- | 15. Prisoners, сonvicted for domestic crimes. ||12 people. || 33% || 42% || 25% |- | 16. Prisoners which hold lead positions among other prisoners in colony – brigadier, the man on duty, chairman of the Council of the Detachment Team.||3 people. || 100% || 0% || 0% |- | 17. Prisoners which consisted in legal or civil marriage. || 24 people. || 20% || 20% || 60% |- | 18. Prisoners which have own children.||22 people. || 14% || 32% || 54% |- | 19. Prisoners which killed of own husband. || 4 people. || 50% || 50% || 0% |- | 20. Average quantity of criminal records at one prisoner. || 50 people. || 2,5 || 2,3 || 2,4 |} It is possible to draw the following conclusions on the basis of these results of a research. Speakers have the highest status in colony. Speakers have the biggest inclination to group crimes though all prisoner-women have noted that prisoner-women executed orders of the man-recidivist in criminal group. Re-education of the speaker is the most difficult task that finds manifestation that the speaker has the most large average amount of criminal records on one prisoner among the personality types. The task of re-education of the speaker is complicated by those circumstances that speaker has the worst marital status – speaker marries more rare, speaker has of children less often than other personality types, speaker has high inclination to the use of drugs, to alcoholism and high probability to ache by HIV. Psychologists specialize in crimes on sale of drugs and apartment's burglaries. Psychologists have high inclination to fall into a state of passion and psychologists have high inclination to finish off victim in the course of causing grievous bodily harm, but psychologists have low inclination to robbery. Psychologists are most of all inclined to commit of crimes alone rather than in a group. The task of re-education of the psychologist is complicated by his inclination to the use of drugs, high probability to ache by HIV. Task of re-education of the psychologist is facilitated by a relatively good marital situation – psychologist marries more often and psychologist has children more often than others personality types. Technicians are inclined to commission of crimes much less than other personality types. Technicians make only 20% of prisoners. But technicians have high inclination to commission of deliberate and unintentional domestic murders (malice aforethought murders and manslaughter), technicians are capable to kill as the executioner and technicians are capable to be cold insensitive to the death suffering of the victim. Process of re-education of technicians is facilitated by low inclination to the use of drugs and quite good marital status. 1 technician and 1 psychologist have two criminal records for murder each that is an example of unique cruelty. All women of Romani people (5 women) were psychologists and women of Romani people specialize in sale of drugs – 60%, in thefts - 20% and in premeditated murders (malice aforethought) - 20%. A knife (84% of cases), the axe (8% of cases), the noose of (4% of cases}, a rolling pin (4% of cases) have served as the crime tool in 24 cases of women crimes. ===The question about necessity of the capital punishment=== [[File:Exécution de Marie Antoinette le 16 octobre 1793.jpg|right|thumb|300px|Marie Antoinette's execution on October 16, 1793]] [[File:Execution robespierre, saint just....jpg|thumb|right|The execution of Maximilien Robespierre]]       [[File:Badische Guillotine.JPG|right|thumb|250px| Guillotine]] Punishment for the crimes connected with use of violence became much more strict under the new Russian criminal code. The top limits of punishment are raised from 15 to 20 years and to life imprisonment. Russian Federation keeps of conditions of the moratorium on the capital punishment, though such punishment as the capital punishment is prescribed in the criminal code for the most serious crimes, but courts replace of capital punishment to life imprisonment. It is connected with fear to make fatal mistake of justice when a theoretical opportunity remains to sentence of innocent person to death penalty. It is impossible already to return to life of the innocent person in case of detection of such mistake of justice after enforcement of sentence about capital punishment. For example, it has become clear during the investigation of criminal case of the serial killer Andrei Chikatilo who has killed about 50 people that the court has sentenced to capital punishment for one of these murders of innocent person who was executed already. According to sociological polls, most of residents of Russia are sure of need of the capital punishment, especially in connection with threat of the Chechen terrorism. Most of residents of Russia are sure of need of application of the capital punishment to those terrorists who blew up houses in Moscow, Volgodonsk and Buynaksk. Most of residents of Russia are sure of need of application of the capital punishment to those terrorists who cut off heads of russian prisoner of war in Chechnya. To abolish of capital punishment is absurdity during war. Region of Upper river Kama (the cities of Solikamsk, Berezniki, Krasnovishersk, Kizel) was turned into the prison region at the Soviet power. One of leaders of the Chechen terrorists – Salman Raduyev – was sentenced to life imprisonment and Salman Raduyev served sentence in Solikamsk supermax prison "White Swan". Salman Raduyev said in one of an interview that Salman Raduyev hopes to serve sentence in supermax prison 25 years, to receive amnesty and to be released, but Salman Raduyev has died a year later on December 14, 2002 in hospital from old wounds. To survive in prison is very difficult for the former terrorist. Prisoners and security guards put pressure upon terrorist also. Almost all squad of the Perm OMON (Special Purpose Police Unit) – 43 militiamen (from them 32 were killed in battle, and 11 were captured and executed with special cruelty) has died in one of the ambushes made by the Chechen terrorists. This event has taken place on March 29, 2000. It is possible to understand hostility of security guards to the condemned terrorists in these conditions. Many leaders of the Chechen terrorists – Dzhokhar Dudayev, Shamil Basayev, Ibn al-Khattab, Aslan Maskhadov was killed with help of special operations. It is possible to abolish of capital punishment in civilized Europe, but it is impossible to abolish of capital punishment in criminal Russia. The capital punishment remains even in the USA. When the prisoner was sentenced to capital punishment, the prisoner can choose a method of execution in the USA – a lethal injection, an electrocution, firing squad, hanging or gas inhalation, and relatives of the victim have an opportunity to watch for this procedure of an execution with help of cable television. ==Michel Foucault about the prison’s reform== [[File:Dieric Bouts 013.jpg|thumb|right|Quartering]]  [[File:Lamanie kolem L 001xx.jpg|thumb|upright|Breaking wheel]] '''Prison’s reform''' Michel Foucault has described a cruel execution of Robert-François Damiens on March 2, 1757 at the beginning of own book "Discipline and Punish: The Birth of the Prison". <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf</ref> Prisons in modern understanding have appeared eighty years later after this execution, and a daily routine was drawn up in prison for young prisoners already. Prisoners were obliged to work 9 hours in day in workshops, prisoners were obliged to study 2 hours in day in prison school. So, public execution were complemented by imprisonment and a prison daily routine. Public execution and imprisonment became different types of punishment in Europe and America. The prison was just the place earlier where the criminal was interrogated and tortured, and then criminal waited an execution here. The prison became the place of life and work for the prisoner after reform according to strict routine where the prisoner spent a long term of imprisonment. These punishments have become applicable for different kinds of crime and these punishments have become applicable to different types of criminals. This reform was carried out in period just under 100 years. During this time, new codes were drawn up that provided for a new types of punishment: in Russia – in 1769, in Prussia – in 1780, In Pennsylvania and Tuscany – in 1786, in Austria – 1788, in France – in 1791, 1808 and 1810.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> '''The essence of prison’s reform (since the late 18th century until the early 19th century) consisted in following:  ''' * Public executions and tortures were cancelled, * Accurate codes, uniform rules of legal proceedings, jury trial were introduced, * The corrective character of the penalty were introduced, assignment of various terms of imprisonment were introduced, kinds of punishment depending on weight of crime were introduced. Only flagellation remain still some time in Russia, Austria and Prussia. * The human branding disappeared on the criminal's face or shoulder. A certain caution has arisen in the art of inflicting pain. The body disappeared as the major target of punishment. * Amende honorable and pillory were cancelled. * Use of convicts at public works was cancelled – at repair of roads when convicts were chained in shackles and iron collars and convicts exchanged with crowd by curses in response on contempt from this crowd. * Chain-gang were cancelled. While the chain-gang, which had dragged convicts across the whole of France, as far as Brest and Toulon was replaced in 1837 by inconspicuous black-painted cell-carts. This cell-carts was prison on wheels. The central corridor divides of cell-carts on all length, six single cells exist on each side of the corridor where prisoners sit facing a corridor. Legs and hands of criminals are chained by a chain. An iron door with a small window was between a corridor and cell that prevents to communication between prisoners on the way. There are two security guards armed by clubs in a corridor. Punishment had gradually ceased to be a spectacle, a rite and a show for gapers gradually.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> ===Reasons of the abolition of public executions:=== * The execution exceed in savagery the crime itself. * The execution accustomed of spectators to cruelty whereas execution should wean of spectators from cruelty. * The execution makes of the executioner resemble a criminal. The execution makes judges resemble murderers. * The execution caused of admiration and pity to the executed criminal instead of contempt and hatred. Conclusion: Punishment becomes the most hidden part of the penal process gradually. Effectiveness of punishment is seen as resulting from its inevitability, not from its visible intensity. <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> Powers began to apply imprisonment, confinement, forced labour, penal servitude, prohibition from entering certain areas, deportation instead of tortures and executions during modern times.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> Imprisonment is connected somewhat with physical suffering too unlike penalties, but intolerable corporal pain is not connected with criminal penalty any more already. The whole army of warders, doctors, chaplains, psychiatrists, psychologists, educationalists comes to replace the executioner as to the specialist in causing pain.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf</ref> ===The shortcomings of modern imprisonment:=== * Imprisonment has no effect on the public. * Imprisonment is incapable of corresponding to the specificity of crimes. * Imprisonment is costly. * Imprisonment maintains of convicts in idleness. Imprisonment multiplies their vices. * Work of the jailer is an exercise in tyranny.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART TWO PUNISHMENT. Chapter 2. The gentle way in punishment. Page 114. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> ===Panopticon=== [[File:Panopticon.jpg |thumb|   Elevation, section and plan of Jeremy Bentham's Panopticon penitentiary, drawn by Willey Reveley, 1791 ]]    Possibility of the round-the-clock supervision of prisoners is here a main goal of construction of Panopticon prison according to the plan of Jeremy Bentham. This prison represents the round or crosswise building, for example, Kresty Prison in St. Petersburg represents several crosswise buildings. The central tower is in the center of such building where a supervisor settles down. A supervisor has an opportunity to observe through wide windows for life of prisoners in cells which are located around the circumference of the building as in an aquarium or in a zoo. Two windows exist in each cell, one window comes to light, the second big window leaves inside therefore the cell is looked through. Only one criminal has to sit in each cell that to avoid by bad influence from prisoners at each other. Walls between cell prevent to communication between prisoners. Therefore there is no of danger of a plot, planning of collective escape and the planning of new crimes for the future. This structure of the building of prison is opposite to the principle of a dungeon. Constant supervision eliminates the need for corporal punishment to some extent too. Modern technical means allow to provide constant supervision over prisoners in cells not by means of a special structure of the building of prison, and by means of video supervision. Such projects of prisons as Panopticon are still too expensive for Russia. The available prisons are overcrowded beyond any measure, closeness and insanitary conditions exist in cells in Russia today.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART THREE DISCIPLINE. Chapter 3. Panopticism. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf</ref> ===Two systems of keeping of criminals in prison in the West=== Powers in the West wanted to interfere with association of criminals in prison in criminal community. Two systems of keeping of criminals in prison were invented for this purpose in the USA: * '''Auburn system''' in the 19th century which prescribes keeping of the prisoners in individual cell at night, work and meals in common in the afternoon, as in the monastery, but on condition of absolute silence. Prisoners can speak only with warders. * '''Pennsylvania system''' (Separate system) provides keeping of prisoners in the conditions of absolute isolation from each other in the solitary cell that to leave of criminal alone with own conscience. There were discussions about an opportunity to pay of work of prisoners and a possibility of the prisoner to refuse from some kinds of works and to organize of strike.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART FOUR PRISON. Chapter 1. Complete and austere institutions. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> ===Arguments of opponents of prison reform and of replacement of executions and torture to imprisonment:=== * The prison organizes training of inexperienced criminals to "thieves' professions" and the prison organizes transformation of inexperienced criminals into professional criminals. * Criminals plan future crimes in prison, сriminals plan organization of escapes from prison and сriminals plan collective prison revolts. * Prisons don't diminish the crime rate. Prisons can be extended, multiplied or transformed, but the quantity of crime and criminals remains stable or, worse, increases. * Prison generates of recidivists, those criminals leaving prison have more chance than before of going back to prison. Existence in prison is lifestyle for recidivists. Recidivists get used to not taking care about food and housing, job and livelihood in prison. * The prison cannot fail to produce of delinquents. The prison produces more and more criminals, rather than correcting of criminals, whether criminals are in solitary cell or criminals perform useless work for them. Between 1,000 and 1,500 convicts live under the surveillance of between thirty and forty supervisors, who can preserve some kind of security only by depending on informers. * The prison makes possible, even encourages, the organization of a milieu of delinquents, loyal to one another, hierarchized, ready to aid and abet any future criminal act. The prison gives to "thieves' profession and the prison learns to be the informer. Сriminals find themselves after release from prison in such conditions which doom of criminals to crime repetition. Criminals lose residence during the inprisonment and criminals become homeless tramps after an exit from prison. Imprisonment dooms of family of the criminal to poverty after detention of the only breadwinner. As a result the son of the thief becomes by thief too frequently that leads to new crimes eventually. <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART FOUR PRISON. Chapter 2. Illegalities and delinquency. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> Conclusions: In my opinion, the prison has many shortcomings, but the prison can't be cancelled. It is impossible to return to tortures and executions because such return contradicts to the principles of humanity. Besides, corporal punishments remain in prison system today to some extent. Corporal punishments are the great invention of mankind too and corporal punishments can't be cancelled completely too because such people exist on which only corporal punishments act. It is impossible to replace corporal punishments on administrative punishments completely, that is it is impossible to replace corporal punishments on conversion of the person from the status "free person" to status of "prisoner". The attempt to replace corporal punishments and an executions on administrative punishments (imprisonment) was not quite successful because this attempt has led to emergence of new problems which weren't earlier. If Gleb Zheglov from the movie "The Meeting Place Cannot Be Changed" was guided the principle that "the thief has to be imprisoned" at any cost, then the judge was guided earlier by the principle: the place of recidivists – on the gallows at any cost, because it was possible to reduce number of recidivists with help of executions, it was possible to destroy criminal hierarchy with help of an executions of leaders of criminal world, it was possible to interfere to process of training of the inexperienced criminals to thieves' professions because executions reduced number of similar "teachers" really. The execution of notorious villains allows to reduce costs on keeping of criminals to a minimum. Besides, the execution of terrorists and maniacs allows to satisfy sense of justice at relatives of the victims on the ancient law of retaliation – "Eye for an eye", these relatives are forced to commit murder of the criminal from revenge and these relatives are forced to be exposed to criminal prosecution today sometimes. This example shows that cancellation of any social invention, even corporal punishments and the capital punishment leads to emergence of big problems always. === Citations and references=== {{Reflist}} {{BookCat}} kis7tu93fqnxtuc8tvzkumzom39ch94 4679863 4679777 2026-11-04T01:06:12Z CommonsDelinker 49843 Removing [[:c:File:Comparison_of_Sheldon's_body_types.jpg|Comparison_of_Sheldon's_body_types.jpg]], it has been deleted from Commons by [[:c:User:Thuresson|Thuresson]] because: Recreation of content deleted per community consensus ([[:c:COM:CSD#G4|G4]]): 4679863 wikitext text/x-wiki https://www.youtube.com/watch?v=AMCYrKAh8-I&ab_channel=%D0%92%D0%B0%D0%BB%D0%B5%D1%80%D0%B8%D0%B9%D0%A1%D1%82%D0%B0%D1%80%D0%B8%D0%BA%D0%BE%D0%B2 The causes of criminality. English subtitles exist in this video. On the cover is a thief named Yaponchik (Vyacheslav Ivankov). https://www.youtube.com/watch?v=gHjD4w2Msps&ab_channel=%D0%92%D0%B0%D0%BB%D0%B5%D1%80%D0%B8%D0%B9%D0%A1%D1%82%D0%B0%D1%80%D0%B8%D0%BA%D0%BE%D0%B2 Michel Foucault on prison reform. English subtitles exist in this video. Valery Starikov Interesting social studies. On the cover is a still from the film "Gentlemen of Fortune." The law is a system established by the State of norms and rules of behavior, fulfillment of which is ensured by force of State’s coercion. State-enforced laws are norms and the rules of behavior. Branches of criminal justice system (police, court, prison) must apply by sanctions to the culprit in case of violation of law. Corporal punishments (tortures and executions) served such legal sanctions in ancient times usually. The execution were replaced by life imprisonment in prison in modern democratic society often, and tortures were replaced by imprisonment for the term limited to the law, tortures were replaced by fine, confiscation of property, compensation of damage to the injured party and so on. But, nevertheless, law were built at the armed control of State over their citizens with antiquity before our days most frequently. Legal norms make behavior of people to a predictable, this is the function and the benefits of the law for society. Legal norms should not be contradictory each to other; otherwise, citizens may find themselves in a difficult situation and citizens will not know what law they should perform. The State must to keep public order, to protect right to private property and free competition. The state has to stop rigidly all attempts of criminals to disturb public order. The state has to stop rigidly all attempts of criminals to seize somebody else’s property unlawfully. The state has to stop rigidly all attempts of criminals to prevent to other citizens to be engaged freely in business activity. People enter the relations in society inevitably, people sign economic contracts with each other, at the same time the state is a guarantor of the fact that both parties have to satisfy conditions of this contract that the violator of terms of the contract will be punished and this violator have to compensate losses to the injured party. All citizens shall have the identical rights. All citizens shall to keep law irrespectively of social status of these citizens. Even high-ranking officials and rulers must keep the law and even rulers shouldn't allow of cases of an arbitrariness and lawlessness in own activity. Only published laws should apply, otherwise, citizens will not know the laws for which they may be punished and the power will receive the right to arbitrariness. If a constitution exists in the country that even the ruler is obliged to keep of the norms of this constitution. ===The state-enforced laws as norms of behavior.=== The state-enforced laws are adopted by the supreme bodies of the government. Laws are adopted by the king or the monarch with help of individual decision under tyranny, the kingdom or a hereditary monarchy, in such a way, for example, the king Hammurabi has accepted for the first time the code of laws known in the history. The state-enforced laws are adopted under the aristocracy or oligarchy by the senate, a Boyar Duma, the Central Committee or the Politburo of the ruling Communist Party with help of vote of members of this ruling privileged meeting. The state-enforced laws are adopted by vote in people's assembly under direct democracy. The state-enforced laws are adopted by parliament in the conditions of representative democracy. A hierarchy of the state-enforced laws and codes exist today. The code is a great number of the the state-enforced laws describing norms of behavior in some sphere of activity - in economy, the family sphere and so on. The most important the state-enforced laws are united in the constitution. The state-enforced laws from other codes shouldn't contradict to constitutional norms. The state-enforced laws from other codes become invalid according to the decision of the constitutional court in that case when the state-enforced law from the code is contrary to the norms of the constitution. Along with the state-enforced laws, there are also other legal acts subordinated to laws: decrees of the president, government regulations, instruction, rule, orders and so on. That to live in society, that to make success in affairs, the person has to study the state-enforced laws. '''The causes of criminality.  '''     [[File:Lombroso.JPG|thumb|Cesare Lombroso]]      [[File:Ernst Kretschmer.jpg|thumb|Ernst Kretschmer]] Many viewpoints exist on the causes of criminality in science.  Neil Smelser has allocated three approaches in decision of this difficult problem: * biological approach, * psychological approach, * sociological approach.           The essence of '''biological approach''' consist in the following:  the born criminal has the inclination to criminal behavior, the born criminal was born by thief and savage, the born criminal is able to do nothing else, a born criminal can only steal, rob and kill. Caesare Lombroso claimed within this approach that criminals are a result of degradation to earlier stages of human evolution. Cesare Lombroso named such external features of the born criminal, as the protruding lower jaw, rare beard and reduced sensitivity to pain. <ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> By the way, in my opinion, these features are most characteristic for speakers on personality type. Similarity of criminal with primitive savage is shown in the passion to tattoo, the weakness of mind and even in degradation of the handwriting similar to hieroglyphic writing. Caesar Lombroso has allocated four types of criminals: murderer, thief, rapist and swindler. And this typology remains to this day. According to Henry H. Goddard, criminals are mentally retarded men, occurring from hereditarily burdened families. My experience of school teaching of criminals on lessons of history in women's prison shows that criminals have different levels of development of intellect like ordinary people from very low level of development of intellect before very high level of development of intellect. Very high level of development of intellect was discovered at one thief‐women which received trust of men. she drank of men by vodka with sleeping pills and she robbed of men when men were sleeping. This thief-women has remember each my word in my lesson on history, each date, each name of hero of history, it is possible, the best memory is necessary feature of character of “thief on trust”.  Level of development of intellect affects to degree of the success of growth for thief’s qualifications.   Stages for such growth for thief’s qualifications exist:   • Specialization on apartment's burglaries.    • Specialization on pocket thefts.    • Theft is based on trust of victim to criminal.             Thus, the opinion of Henry H. Goddard seems not entirely truth. From the point of view of the theory of "criminal psychodynamics", the criminal in own acts is guided not by mind but only emotions, the criminal is a psychopathic personality who has deviates from the norm, but the criminal isn't neither mentally sick, nor mentally retarded personality. Ernst Kretschmer have given the description of three main body types of man: • asthenic (tall and thin); • pyknic (stocky, fat), • athletic (with advanced musculature); An athlete is person with the developed musculature, inclined to the organization of conflict.   A pyknic is person, inclined to obesity, which attempts to settle conflict with help of peaceful way.   Asthenic is thin person, which is potential victim in the conflict.        William Herbert Sheldon considered that the athletics are most inclined to the crimes. The genetic explanation of the reasons of crime consists that some criminals have chromosomes like XYY whereas ordinary men have chromosomes like XY, and ordinary women have chromosomes like XX. These people with chromosomes like XYY have frightening appearance, high growth and this people are heavy psychopaths sometimes.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> Sigmund Freud has entered concept "criminals with sense of guilt" within the framework of '''psychological approach''', this criminals wish that they were caught and punished because this criminals feel own guilty because of their "inclination to destruction," this criminals believe that imprisonment will help them overcome this inclination. <ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> The essence of '''sociological approach''' consists that the main reason of crime is that thieves are brought up in criminal group purposefully. Edwin Sutherland claimed that the prison corrects nobody, and prison is school of training in criminal behavior often. Émile Durkheim considered that the social anomie or, in other words, lawlessness, is the main reason for criminality in the period of social crisis.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> A similar period was in Russia during government of Mikhail Gorbachev and Boris Eltsin. The a main goal of Vladimir Putin became the establishing of order in the country, that to drive of criminal world into an underground. The condition of an anomy is observed in big cities among teenagers where there is a mixture of various ethnic groups to the different systems of values. Robert King Merton considered that the gap between the purposes and the approved means of their achievement is the reason of crime, for example, the purpose is financial success, and means is receiving the higher education, but paid education is often inaccessible today therefore some people can use illegal ways of enrichment.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> According to the theory of stigmatization of Howard S. Becker, influential groups are capable to put stigma of criminal on members of less influential groups and thus influential groups train of members of less influential groups to consider themselves by criminals. For example, whites did with African Americans in the United States this way.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> From the point of view of Marxism and radical criminologists, criminals are rebels against capitalist exploitation.<ref> Neil Smelser. Sociology. New-Jersey Prentice Hall 1988. Chapter 7. Deviance and social control. </ref> The example of such "rebel" is Joseph Stalin who had 6 criminal records for extortion and 5 escapes from exile. It is possible to draw a conclusion that all these theories are partly true and crime is a consequence of many causes. ===An empirical study of the causes of criminality.=== My preliminary forecast before the empirical researches consisted that a potential criminal is the speaker. This forecast has found partial confirmation, but it has turned out that speakers are capable besides that to show resourcefulness, speakers know how to engage other personality types in a criminal group, speakers are able to use of other personality types as performers of own criminal plans, then speakers are capable to avoid criminal punishment and speakers are capable to shift all fault for crimes on other personality types. There is a specialization in the criminal world in various roles, such as organizer, executor, helper and instigator. Thief in law in Russia is an example of the organizer of the high qualification. Skilled in thieves' affairs speaker is capable to play a role of the organizer. The inexperienced speaker or the technician approach for a role of executor. A principle: "You mustn't to be by a executor!" exists in criminal world, because executors are arrested by first of all then the executor is obliged according to thieves' laws to take all fault on himself and executor mustn't betray of other members of criminal group, otherwise executor can be killed in prison. The role of the executor is the most unprofitable in comparison with other roles. The psychologist and the speaker can undertake role of the instigator, at the same time the speaker forces of executor to commit to crime by means of threats, and the psychologist persuades by executor to commit to crime by means of deception and cunning, thus, the speaker and psychologist use different coercion methods. The role of the helper is carried out different the personality types, for example the technician is capable to make high-quality weapon, the speaker is capable to sell stolen property. Psychologist and speaker are able to provide information about candidates of potential victims of robberies and about their property status at apartment's burglaries. The psychologist knows how to rub into the trust to potential victims. By the way, my research has shown that, unlike rules in men's prisons, women having the status of thiefs in law do not exist in women's corrective labor colony of strict regimen and high hierarchy doesn't exist among the prisoner-women. The speaker and the psychologist approach for a role of the drug dealer. The technician can play a role of the cruel killer-executioner or killer-sniper because of inclination of the technician to insensibility and low emotionality. The speaker has the highest inclination to be by leader of criminal world, to make all kinds of serious crimes and to improve thieves' skills, speaker has inclination to adventurism and frivolous behavior, readiness to submit to pressure of criminal group and inability to foresee heavy consequences of own crimes. This inclination of the speaker to criminal behavior is shown at young age and in state of intoxication especially brightly. The psychologist is the potential victim of crime often because the psychologist provoke of criminals involuntarily thanks to peculiar for psychologists weakness of character. A woman-psychologist provokes involuntarily of a rapist to rape due to the fact that the woman-psychologist has the highest degree of sexuality. This my research was conducted on the basis of women's corrective labor colony of strict regimen of UT 389/28 in town Berezniki during the period from November 2003 to March 2004. The status of colony was changed at the end of this period – the strict regimen was changed on a ordinary regimen. The informal unstructured interview (35 respondents) and the included observation in the course of training of prisoner in 8 and 9 classes of middle school (15 respondents) became forms of carrying out a research. Total, 50 prisoner-women were interviewed and subjected to observation by means of casual selection. 40% were by psychologists, 20% were by technicians, 40% were speakers from this prisoner-women, theorists were not found among prisoner-women. That to appear in this colony and to conduct a research, I had to get a job of the teacher of history in this prison's school. The generalized results of my research are given in the table given below: {| class="wikitable" |- ! Different categories of prisoners. !! Quantity of prisoners. !! Shares of speakers among prisoners. !! Shares of technicians among prisoners. !! Shares of psychologists among prisoners. |- | 1. Shares of the personality types in this colony. || 50 people.|| 40% || 20% || 40% |- | 2. Prisoners, сonvicted for robbery according to article 162 of criminal code of Russian Federation. || 8 people. || 62% || 25% || 13% |- | 3. Prisoners, сonvicted for causing grievous bodily harm without death of victim according to article 111 of item 1,2,3 of criminal code of Russian Federation.|| 11 people.|| 73% || 18% || 9% |- | 4. The prisoners, сonvicted for causing heavy harm to health with the death of victim according to article 111 of item 4 of criminal code of Russian Federation.|| 0% || 40% || 60% |- | 5. Prisoners, сonvicted for premeditated murder (malice aforethought) according to article 105 of criminal code of Russian Federation. ||10 people. || 30% || 40% || 30% |- | 6. Prisoners, сonvicted for illegal manufacturing, sale, storage and transportation of drugs according to article 228 of criminal code of Russian Federation. || 17 people. || 47% || 6% || 47% |- | 7. Prisoners, сonvicted for theft according to article 158 of criminal code of Russian Federation. || 26 people. || 35% || 23% || 42% |- | 8. Prisoners-drug addicts, сonvicted for illegal manufacturing, sale, storage and transportation of drugs or prisoners-drug addicts, сonvicted for theft according to articles 228 or 158 of criminal code of Russian Federation.. || 13 people. || 45% || 10% || 45% |- | 9. Prisoners-drug addicts, sick HIV, condemned for illegal manufacturing, sale, storage and transportation of drugs according to article 228 of criminal code of Russian Federation. || 2 people. || 50% || 0% || 50% |- | 10. Prisoners, сonvicted for the apartment's thefts according to article 158 of criminal code of Russian Federation. || 9 people. || 33% || 22% || 45% |- | 11. Prisoners, сonvicted for the theft from the pockets according to article 158 of criminal code of Russian Federation. || 2 people. || 50$ || 0% || 50% |- | 12. Prisoners, сonvicted for theft on trust with use of сlophelinum according to article 158 of criminal code of Russian Federation. || 1 people. || 100% || 0% || 0% |- | 13. Prisoners, сonvicted for group crimes. || 25 people. || 52% || 12% || 36% |- | 14. Prisoners, who committed for crimes alone. || 13 people. || 31% || 15% || 54% |- | 15. Prisoners, сonvicted for domestic crimes. ||12 people. || 33% || 42% || 25% |- | 16. Prisoners which hold lead positions among other prisoners in colony – brigadier, the man on duty, chairman of the Council of the Detachment Team.||3 people. || 100% || 0% || 0% |- | 17. Prisoners which consisted in legal or civil marriage. || 24 people. || 20% || 20% || 60% |- | 18. Prisoners which have own children.||22 people. || 14% || 32% || 54% |- | 19. Prisoners which killed of own husband. || 4 people. || 50% || 50% || 0% |- | 20. Average quantity of criminal records at one prisoner. || 50 people. || 2,5 || 2,3 || 2,4 |} It is possible to draw the following conclusions on the basis of these results of a research. Speakers have the highest status in colony. Speakers have the biggest inclination to group crimes though all prisoner-women have noted that prisoner-women executed orders of the man-recidivist in criminal group. Re-education of the speaker is the most difficult task that finds manifestation that the speaker has the most large average amount of criminal records on one prisoner among the personality types. The task of re-education of the speaker is complicated by those circumstances that speaker has the worst marital status – speaker marries more rare, speaker has of children less often than other personality types, speaker has high inclination to the use of drugs, to alcoholism and high probability to ache by HIV. Psychologists specialize in crimes on sale of drugs and apartment's burglaries. Psychologists have high inclination to fall into a state of passion and psychologists have high inclination to finish off victim in the course of causing grievous bodily harm, but psychologists have low inclination to robbery. Psychologists are most of all inclined to commit of crimes alone rather than in a group. The task of re-education of the psychologist is complicated by his inclination to the use of drugs, high probability to ache by HIV. Task of re-education of the psychologist is facilitated by a relatively good marital situation – psychologist marries more often and psychologist has children more often than others personality types. Technicians are inclined to commission of crimes much less than other personality types. Technicians make only 20% of prisoners. But technicians have high inclination to commission of deliberate and unintentional domestic murders (malice aforethought murders and manslaughter), technicians are capable to kill as the executioner and technicians are capable to be cold insensitive to the death suffering of the victim. Process of re-education of technicians is facilitated by low inclination to the use of drugs and quite good marital status. 1 technician and 1 psychologist have two criminal records for murder each that is an example of unique cruelty. All women of Romani people (5 women) were psychologists and women of Romani people specialize in sale of drugs – 60%, in thefts - 20% and in premeditated murders (malice aforethought) - 20%. A knife (84% of cases), the axe (8% of cases), the noose of (4% of cases}, a rolling pin (4% of cases) have served as the crime tool in 24 cases of women crimes. ===The question about necessity of the capital punishment=== [[File:Exécution de Marie Antoinette le 16 octobre 1793.jpg|right|thumb|300px|Marie Antoinette's execution on October 16, 1793]] [[File:Execution robespierre, saint just....jpg|thumb|right|The execution of Maximilien Robespierre]]       [[File:Badische Guillotine.JPG|right|thumb|250px| Guillotine]] Punishment for the crimes connected with use of violence became much more strict under the new Russian criminal code. The top limits of punishment are raised from 15 to 20 years and to life imprisonment. Russian Federation keeps of conditions of the moratorium on the capital punishment, though such punishment as the capital punishment is prescribed in the criminal code for the most serious crimes, but courts replace of capital punishment to life imprisonment. It is connected with fear to make fatal mistake of justice when a theoretical opportunity remains to sentence of innocent person to death penalty. It is impossible already to return to life of the innocent person in case of detection of such mistake of justice after enforcement of sentence about capital punishment. For example, it has become clear during the investigation of criminal case of the serial killer Andrei Chikatilo who has killed about 50 people that the court has sentenced to capital punishment for one of these murders of innocent person who was executed already. According to sociological polls, most of residents of Russia are sure of need of the capital punishment, especially in connection with threat of the Chechen terrorism. Most of residents of Russia are sure of need of application of the capital punishment to those terrorists who blew up houses in Moscow, Volgodonsk and Buynaksk. Most of residents of Russia are sure of need of application of the capital punishment to those terrorists who cut off heads of russian prisoner of war in Chechnya. To abolish of capital punishment is absurdity during war. Region of Upper river Kama (the cities of Solikamsk, Berezniki, Krasnovishersk, Kizel) was turned into the prison region at the Soviet power. One of leaders of the Chechen terrorists – Salman Raduyev – was sentenced to life imprisonment and Salman Raduyev served sentence in Solikamsk supermax prison "White Swan". Salman Raduyev said in one of an interview that Salman Raduyev hopes to serve sentence in supermax prison 25 years, to receive amnesty and to be released, but Salman Raduyev has died a year later on December 14, 2002 in hospital from old wounds. To survive in prison is very difficult for the former terrorist. Prisoners and security guards put pressure upon terrorist also. Almost all squad of the Perm OMON (Special Purpose Police Unit) – 43 militiamen (from them 32 were killed in battle, and 11 were captured and executed with special cruelty) has died in one of the ambushes made by the Chechen terrorists. This event has taken place on March 29, 2000. It is possible to understand hostility of security guards to the condemned terrorists in these conditions. Many leaders of the Chechen terrorists – Dzhokhar Dudayev, Shamil Basayev, Ibn al-Khattab, Aslan Maskhadov was killed with help of special operations. It is possible to abolish of capital punishment in civilized Europe, but it is impossible to abolish of capital punishment in criminal Russia. The capital punishment remains even in the USA. When the prisoner was sentenced to capital punishment, the prisoner can choose a method of execution in the USA – a lethal injection, an electrocution, firing squad, hanging or gas inhalation, and relatives of the victim have an opportunity to watch for this procedure of an execution with help of cable television. ==Michel Foucault about the prison’s reform== [[File:Dieric Bouts 013.jpg|thumb|right|Quartering]]  [[File:Lamanie kolem L 001xx.jpg|thumb|upright|Breaking wheel]] '''Prison’s reform''' Michel Foucault has described a cruel execution of Robert-François Damiens on March 2, 1757 at the beginning of own book "Discipline and Punish: The Birth of the Prison". <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf</ref> Prisons in modern understanding have appeared eighty years later after this execution, and a daily routine was drawn up in prison for young prisoners already. Prisoners were obliged to work 9 hours in day in workshops, prisoners were obliged to study 2 hours in day in prison school. So, public execution were complemented by imprisonment and a prison daily routine. Public execution and imprisonment became different types of punishment in Europe and America. The prison was just the place earlier where the criminal was interrogated and tortured, and then criminal waited an execution here. The prison became the place of life and work for the prisoner after reform according to strict routine where the prisoner spent a long term of imprisonment. These punishments have become applicable for different kinds of crime and these punishments have become applicable to different types of criminals. This reform was carried out in period just under 100 years. During this time, new codes were drawn up that provided for a new types of punishment: in Russia – in 1769, in Prussia – in 1780, In Pennsylvania and Tuscany – in 1786, in Austria – 1788, in France – in 1791, 1808 and 1810.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> '''The essence of prison’s reform (since the late 18th century until the early 19th century) consisted in following:  ''' * Public executions and tortures were cancelled, * Accurate codes, uniform rules of legal proceedings, jury trial were introduced, * The corrective character of the penalty were introduced, assignment of various terms of imprisonment were introduced, kinds of punishment depending on weight of crime were introduced. Only flagellation remain still some time in Russia, Austria and Prussia. * The human branding disappeared on the criminal's face or shoulder. A certain caution has arisen in the art of inflicting pain. The body disappeared as the major target of punishment. * Amende honorable and pillory were cancelled. * Use of convicts at public works was cancelled – at repair of roads when convicts were chained in shackles and iron collars and convicts exchanged with crowd by curses in response on contempt from this crowd. * Chain-gang were cancelled. While the chain-gang, which had dragged convicts across the whole of France, as far as Brest and Toulon was replaced in 1837 by inconspicuous black-painted cell-carts. This cell-carts was prison on wheels. The central corridor divides of cell-carts on all length, six single cells exist on each side of the corridor where prisoners sit facing a corridor. Legs and hands of criminals are chained by a chain. An iron door with a small window was between a corridor and cell that prevents to communication between prisoners on the way. There are two security guards armed by clubs in a corridor. Punishment had gradually ceased to be a spectacle, a rite and a show for gapers gradually.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> ===Reasons of the abolition of public executions:=== * The execution exceed in savagery the crime itself. * The execution accustomed of spectators to cruelty whereas execution should wean of spectators from cruelty. * The execution makes of the executioner resemble a criminal. The execution makes judges resemble murderers. * The execution caused of admiration and pity to the executed criminal instead of contempt and hatred. Conclusion: Punishment becomes the most hidden part of the penal process gradually. Effectiveness of punishment is seen as resulting from its inevitability, not from its visible intensity. <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> Powers began to apply imprisonment, confinement, forced labour, penal servitude, prohibition from entering certain areas, deportation instead of tortures and executions during modern times.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> Imprisonment is connected somewhat with physical suffering too unlike penalties, but intolerable corporal pain is not connected with criminal penalty any more already. The whole army of warders, doctors, chaplains, psychiatrists, psychologists, educationalists comes to replace the executioner as to the specialist in causing pain.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART ONE TORTURE. Chapter 1. The body of the condemned. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf</ref> ===The shortcomings of modern imprisonment:=== * Imprisonment has no effect on the public. * Imprisonment is incapable of corresponding to the specificity of crimes. * Imprisonment is costly. * Imprisonment maintains of convicts in idleness. Imprisonment multiplies their vices. * Work of the jailer is an exercise in tyranny.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART TWO PUNISHMENT. Chapter 2. The gentle way in punishment. Page 114. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> ===Panopticon=== [[File:Panopticon.jpg |thumb|   Elevation, section and plan of Jeremy Bentham's Panopticon penitentiary, drawn by Willey Reveley, 1791 ]]    Possibility of the round-the-clock supervision of prisoners is here a main goal of construction of Panopticon prison according to the plan of Jeremy Bentham. This prison represents the round or crosswise building, for example, Kresty Prison in St. Petersburg represents several crosswise buildings. The central tower is in the center of such building where a supervisor settles down. A supervisor has an opportunity to observe through wide windows for life of prisoners in cells which are located around the circumference of the building as in an aquarium or in a zoo. Two windows exist in each cell, one window comes to light, the second big window leaves inside therefore the cell is looked through. Only one criminal has to sit in each cell that to avoid by bad influence from prisoners at each other. Walls between cell prevent to communication between prisoners. Therefore there is no of danger of a plot, planning of collective escape and the planning of new crimes for the future. This structure of the building of prison is opposite to the principle of a dungeon. Constant supervision eliminates the need for corporal punishment to some extent too. Modern technical means allow to provide constant supervision over prisoners in cells not by means of a special structure of the building of prison, and by means of video supervision. Such projects of prisons as Panopticon are still too expensive for Russia. The available prisons are overcrowded beyond any measure, closeness and insanitary conditions exist in cells in Russia today.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART THREE DISCIPLINE. Chapter 3. Panopticism. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf</ref> ===Two systems of keeping of criminals in prison in the West=== Powers in the West wanted to interfere with association of criminals in prison in criminal community. Two systems of keeping of criminals in prison were invented for this purpose in the USA: * '''Auburn system''' in the 19th century which prescribes keeping of the prisoners in individual cell at night, work and meals in common in the afternoon, as in the monastery, but on condition of absolute silence. Prisoners can speak only with warders. * '''Pennsylvania system''' (Separate system) provides keeping of prisoners in the conditions of absolute isolation from each other in the solitary cell that to leave of criminal alone with own conscience. There were discussions about an opportunity to pay of work of prisoners and a possibility of the prisoner to refuse from some kinds of works and to organize of strike.<ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART FOUR PRISON. Chapter 1. Complete and austere institutions. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> ===Arguments of opponents of prison reform and of replacement of executions and torture to imprisonment:=== * The prison organizes training of inexperienced criminals to "thieves' professions" and the prison organizes transformation of inexperienced criminals into professional criminals. * Criminals plan future crimes in prison, сriminals plan organization of escapes from prison and сriminals plan collective prison revolts. * Prisons don't diminish the crime rate. Prisons can be extended, multiplied or transformed, but the quantity of crime and criminals remains stable or, worse, increases. * Prison generates of recidivists, those criminals leaving prison have more chance than before of going back to prison. Existence in prison is lifestyle for recidivists. Recidivists get used to not taking care about food and housing, job and livelihood in prison. * The prison cannot fail to produce of delinquents. The prison produces more and more criminals, rather than correcting of criminals, whether criminals are in solitary cell or criminals perform useless work for them. Between 1,000 and 1,500 convicts live under the surveillance of between thirty and forty supervisors, who can preserve some kind of security only by depending on informers. * The prison makes possible, even encourages, the organization of a milieu of delinquents, loyal to one another, hierarchized, ready to aid and abet any future criminal act. The prison gives to "thieves' profession and the prison learns to be the informer. Сriminals find themselves after release from prison in such conditions which doom of criminals to crime repetition. Criminals lose residence during the inprisonment and criminals become homeless tramps after an exit from prison. Imprisonment dooms of family of the criminal to poverty after detention of the only breadwinner. As a result the son of the thief becomes by thief too frequently that leads to new crimes eventually. <ref> Michel Foucault. DISCIPLINE AND PUNISH. The Birth of the Prison. PART FOUR PRISON. Chapter 2. Illegalities and delinquency. https://monoskop.org/images/4/43/Foucault_Michel_Discipline_and_Punish_The_Birth_of_the_Prison_1977_1995.pdf </ref> Conclusions: In my opinion, the prison has many shortcomings, but the prison can't be cancelled. It is impossible to return to tortures and executions because such return contradicts to the principles of humanity. Besides, corporal punishments remain in prison system today to some extent. Corporal punishments are the great invention of mankind too and corporal punishments can't be cancelled completely too because such people exist on which only corporal punishments act. It is impossible to replace corporal punishments on administrative punishments completely, that is it is impossible to replace corporal punishments on conversion of the person from the status "free person" to status of "prisoner". The attempt to replace corporal punishments and an executions on administrative punishments (imprisonment) was not quite successful because this attempt has led to emergence of new problems which weren't earlier. If Gleb Zheglov from the movie "The Meeting Place Cannot Be Changed" was guided the principle that "the thief has to be imprisoned" at any cost, then the judge was guided earlier by the principle: the place of recidivists – on the gallows at any cost, because it was possible to reduce number of recidivists with help of executions, it was possible to destroy criminal hierarchy with help of an executions of leaders of criminal world, it was possible to interfere to process of training of the inexperienced criminals to thieves' professions because executions reduced number of similar "teachers" really. The execution of notorious villains allows to reduce costs on keeping of criminals to a minimum. Besides, the execution of terrorists and maniacs allows to satisfy sense of justice at relatives of the victims on the ancient law of retaliation – "Eye for an eye", these relatives are forced to commit murder of the criminal from revenge and these relatives are forced to be exposed to criminal prosecution today sometimes. This example shows that cancellation of any social invention, even corporal punishments and the capital punishment leads to emergence of big problems always. === Citations and references=== {{Reflist}} {{BookCat}} q9uwyb5ccgefr38bylf3fkgeq7na68n User talk:Kittycataclysm 3 442343 4679835 4679674 2026-11-03T19:53:34Z Kittycataclysm 3371989 /* Cookbook:Colcannon (Scottish) */ Reply 4679835 wikitext text/x-wiki {| class="wikitable" |+ ! colspan="3" |Talk Page Archives |- |[[User talk:Kittycataclysm/Archive 2022|2022]] |[[User talk:Kittycataclysm/Archive 2023|2023]] |[[User talk:Kittycataclysm/Archive 2024|2024]] |} == That IP range calculator == Following [[phab:T381138|T381138]], I have now become the maintainer of the IP range calculator you like. You can find it [[toolforge:ftools/general/ip-range-calc.html|here]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 23:10, 9 January 2025 (UTC) :Thank you for the heads-up! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:56, 10 January 2025 (UTC) == A merge and unmerge from two years ago == I was browsing through the history merge log when I saw that you merged [[Cookbook:Chicken Bog]] into [[Cookbook:Chicken Bog I]], and then promptly reverted it. What happened here exactly? Could I correct it? [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 15:55, 10 January 2025 (UTC) :Good question! I can't remember what I was trying to do, but it looks like I didn't succeed at what I wanted based on the log comment. You're just trying to history merge to get [[Cookbook:Chicken Bog I]] to have continuity of history? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:35, 10 January 2025 (UTC) ::I think I figured out your mistake: it outright moved the revisions from the first page to the second, rather than copying them. This would have caused the other two [[Cookbook:Chicken Bog]] pages to have incomplete histories. I think the only solution would be to XML import the pre-April 2023 revisions from the first page to the other three, and I'm not sure if that's the best idea, and I am technically unable to do so. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 16:49, 10 January 2025 (UTC) == Undeletion request == I wouldn't be surprised if you expected this, but I'd like to ask you to undelete the subpages of [[Rotorcraft Fundamentals]] you just deleted with the summary "Use of copyrighted work without permission. Please read Terms of Use: page needs to be imported for attribution", so that I can do that. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 19:54, 14 January 2025 (UTC) :Done! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:57, 14 January 2025 (UTC) ::Upon further investigation, this might actually be a rare case where an [[WB:UT|unmerged transwiki]] is ''preferred'' (this is part of why I stopped calling them "bad transwikis"), since only a small portion of the Wikipedia article (with over 2,000 revisions) was copied over. Importation is generally only needed if the ''majority'' of the page is copied across wikis. I'll just leave a null edit providing attribution and add {{tlx|Copied}}. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 21:19, 14 January 2025 (UTC) == Reusing [[Cookbook:8 Desserts in 1 Pan]] on wikiHow == Hi, I am a user on wikiHow, see [[wikihow:User:Xeverything11]]. I would like to create a new recipe on wikiHow. I wanted to let us know if I can give permission to reuse your contributions to this recipe from Wikibooks to wikiHow. I (as a copyright holder) created this recipe on Wikibooks, but you contributed to this recipe. If not, I'll use the revision before you contributed since I was the only author. Wikibooks uses CC-BY-SA 4.0 while wikiHow uses CC-BY-NC-SA 3.0, which both licenses are incompatible due to ShareAlike conditions. Thanks [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 08:27, 15 January 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] I'm personally fine with this as long as proper attribution is given back to the original recipe page here. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:52, 20 January 2025 (UTC) ::I adapted this [[wikihow:Make-8-Desserts-in-1-Pan|recipe]] on wikiHow with attribution, and got a Rising Star (an achievement used for best new articles on wikiHow). Thank you! [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 19:49, 24 January 2025 (UTC) == Wikibooks community == Hi, @[[User:Kittycataclysm|Kittycataclysm]]! I am trying to contribute more to English Wikibooks. My main contributions will focus on the Cookbook, especially on Indonesian recipes. Do you have a community group where we can discuss and share ideas together? I am looking forward to join. Thank you! [[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 08:47, 16 January 2025 (UTC) :@[[User:Raflinoer32|Raflinoer32]] Sorry I missed this, and welcome! Are you asking about a Cookbook-specific area for discussion? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:39, 20 January 2025 (UTC) ::Yes. Do you know place for this? ::Thank you ::[[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 09:41, 21 January 2025 (UTC) :::Honestly, there's not a centralized Cookbook-specific discussion space, especially since there aren't currently a ton of active contributors. Some people ask questions at [[Cookbook talk:Table of Contents]]. I'm currently the most consistently active and involved Cookbook editor, so feel free to ask me questions! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:46, 22 January 2025 (UTC) == Congratulations! == [[File:Admin T-shirt.svg|thumb|You get this now.]] You are now a permanent administrator. Welcome to the team (I am entitled to say this because I technically got the extension a few hours before you did)!{{FBDB}} [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 10:33, 29 January 2025 (UTC) :Thanks :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:29, 29 January 2025 (UTC) == Is there a way to contact a Steward on WikiBooks? == Hi {{PAGENAME}}, Is there a way to contact a Steward on WB? I tried to find who the active Stewards are here at [[Special:ActiveUsers?username=&groups%5B%5D=steward&wpFormIdentifier=specialactiveusers]] but nothing shows up. The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the [[Wikimania-wiki]], but I just visited the [[wikimania 2014 wiki]] and could not find this backward link. I tried to ask about this on the [[Wikimania 2014 main-page talk]] but disovered that the Stewards have protected it. Is there a way wikibookians can communicate with Stewards at WB? Thanks in advance for answering this non-urgent question, and apologies for all the red-links which I can bluify if needed. Cheers [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 16:37, 7 February 2025 (UTC) :@[[User:Ottawahitech|Ottawahitech]] You can ask this on somewhere like [[metawiki:Steward requests/Miscellaneous]]. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 17:01, 7 February 2025 (UTC) <s>:@[[User:Ottawahitech|Ottawahitech]] seconding what Leaderboard said—we no longer have any active stewards at enWB.</s> Had a brain fade there and mixed up stewards with bureaucrats. Yes, meta is the place for this. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 7 February 2025 (UTC) ::@Kittycataclysm,@[[User:Leaderboard|Leaderboard]], or anyone else: ::Some wikibookians prefer for various reasons to post only at wb. I myself am indef-blocked at META so could not participate at [[metawiki:Steward requests/Miscellaneous]] even if I waned to. ::Since [[Wikimania]] is a topic of interest to all members of the [[wikimedia movement]] why can't wikibookians talk to thier elected representatives here? [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:56, 7 February 2025 (UTC) :::@[[User:Ottawahitech|Ottawahitech]] I can check with the blocking admin to see if they'd be willing to unblock you, if you'd like. The reason things like these are done at Meta is that Meta is a cross-project coordination platform - stewards ''cannot'' be expected to watch every project after all. Now you could message any steward here on Wikibooks if you really wanted to, but that is not normally a good idea. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 02:26, 8 February 2025 (UTC) ::::Wikimania is the annual conference celebrating all the free knowledge projects hosted by the Wikimedia Foundation (WMF). It is a wikimedia initiative which is meant to help all of our projects (including wikibooks), gain more readership, educate more wiki-editors, foster better communications, and much more. The wmf has been hosting a Wikimania-wiki dedicated to each Wikimania annual event since 2004. These wikis contain a wealth of information, but can benefit from wiki-improvements, starting from spelling and grammar errors that detract from their to appeal to the general membership. It would be nice if Stewards paid more attention to it. ::::@[[User:Leaderboard|Leaderboard]], I truly appreciate your offer, but I posted this here not in order to get someone to advocate for one unblocking at META. As I said earlier: ::::* "Some wikibookians prefer for various reasons to post only at wb" ::::* "The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the Wikimania-wiki, but I just visited the wikimania 2014 wiki and could not find this backward link. I tried to ask about this on the Wikimania 2014 main-page talk but disovered that the Stewards have protected it" ::::I would much rather see more wikimedia members question blocking in general at META. One cannot run such large movement of people from different backgrounds and nationalities simply by silencing minorities IMIO. [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:12, 8 February 2025 (UTC) == [[Crystal ball]] == That page appears to be a mixture of isolated paragraphs from [[w:Crystal ball|Crystal ball]], hence my tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 03:04, 9 February 2025 (UTC) :Yep, that seems correct! I also queried it simply because it does not seem suitable for inclusion at all. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:09, 9 February 2025 (UTC) == Question about an edit suggestion == Hi Kittycataclysm, Thanks for the great work you do as an admin! I wanted to clarify a suggestion you made on a recently published page I’m working on. You recommended splitting it into smaller sections—would you suggest creating separate pages for these sections, or would a higher-level header for some topics be sufficient? Any specific recommendations you have would be greatly appreciated! Here’s the link to the page I’m referring to: [[Funding and Finance of Transportation Projects in the United States of America]] Thank you! [[User:Svrmustafa|Svrmustafa]] ([[User talk:Svrmustafa|discuss]] • [[Special:Contributions/Svrmustafa|contribs]]) 18:19, 18 February 2025 (UTC) :Hi @[[User:Svrmustafa|Svrmustafa]], and thanks for asking! Splitting refers to creating new pages, each with a smaller amount of content. The main page should then contain a table of contents, and each page can contain a navigation template for easier navigation. I'll create the table of contents based on the current work and move some content to one of those pages as an example for you; then, you can do the rest. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:26, 19 February 2025 (UTC) ::Following up on this—I noticed that you use the term "paper". However, technically Wikibooks hosts books not papers, so you should probably change this wording. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:38, 19 February 2025 (UTC) == Talkback == {{Talkback|Cookbook talk:Chilli Crab|Recipe Questions}} [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 09:54, 19 February 2025 (UTC) :@[[User:Kittycataclysm|Kittycataclysm]] I also made [[Cookbook:Prata|this]] [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:15, 19 February 2025 (UTC) == Hello == Can you look at my latest recipe? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 00:10, 28 February 2025 (UTC) :I saw it! It needs a few corrections, which I'll note. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:23, 28 February 2025 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]] How do you write recipe summary, correct headers [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 06:04, 28 February 2025 (UTC) :::Please see [[Cookbook:Policy/Recipe template]]. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:08, 28 February 2025 (UTC) ::::ok [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 02:33, 1 March 2025 (UTC) == Cookbook == Hi there, Kittycataclysm. I wandered over here from Wikipedia, and I'm quite enamoured with this cookbook. I noticed you seem to be the one maintaining it, and I thought I'd reach out. Can I really just start cranking out recipes from public domain cookbooks and my family recipes? It's that simple? I was also wondering about the featured recipes section. There's not very many in there, and I imagine there's not very many folks around to do reviews compared to GAR on Wikipedia. How do you handle content review? Thanks. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:51, 1 March 2025 (UTC) :Hi @[[User:MediaKyle|MediaKyle]] and welcome! For some context, the Cookbook has been around since the very beginning of Wikibooks, but it had gotten into a bit of disarray over the course of about two decades by the time I found it. I started the long process of overhauling, standardizing, and expanding it just over four years ago—I finished standardizing the recipe formatting and quality a while back and am currently working my way through the ingredient pages before moving on to equipment, techniques, and cuisines. You can absolutely add any public domain recipes as well as your own recipes—they just need to conform to the [[Cookbook:Policy/Recipe template|recipe template]] and [[Cookbook:Policy|Cookbook policy overall]]. It's even better if you've made the recipe and can contribute a nice picture and specific guidance/instructions/notes! Please feel free to ask me any questions. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:27, 1 March 2025 (UTC) ::Oh, and regarding the featured recipes section, I actually haven't gotten around to looking into that yet—there's been a lot to do! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:28, 1 March 2025 (UTC) ::That's great, thanks a lot for your response. This is just delightful. Maybe content review is something that we could collaborate on. There's a lot of recipes in here and it would be nice to know which ones are the best. Question for you, [[:Category:Brown sauces]] is really bothering me. How can I move that to Brown sauce recipes? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:29, 1 March 2025 (UTC) :::Good catch on that category! It seems like it was created two decades ago and never got corrected—feel free to recategorize those recipes. Thank you also for introducing the hideprefix parameter to the category trees—I didn't realize that was an option, and it reduces the visual clutter! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:38, 1 March 2025 (UTC) ::::My pleasure! As I continue to look at the categories, this is actually worse than I thought. We have both [[:Category:Sauce recipes]] and [[:Category:Recipes for condiments]] and I suspect that's just the beginning. I want to go through and categorize everything properly, but the bones aren't even there... How long do I have to be here before it'll let me create and move around categories? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:40, 1 March 2025 (UTC) :::::Regarding the categories, the category overhauling is in progress, since I address the category when I overhaul the associated page. The variation in titling is actually somewhat deliberate—I started changing it from "____ recipes" in certain cases to solve a particular categorization problem. Sometimes, there is an item that is used in recipes as an ingredient but for which there are also recipes. For example, [[:Category:Recipes for bread]] versus [[:Category:Recipes using bread]]. The different naming scheme is necessary to properly delineate the categories, and I'm working on implementing it a bit more consistently as I go. While you're still getting started, it would be great if you could check with me when something looks odd or out of place—that way I can take a look and weigh in on whether that's normal or not and maybe provide some context. Just off the top of my head, I think you will have to wait for autoreview status to make move changes. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:56, 1 March 2025 (UTC) ::::::I see what you're saying, I've been trying to wrap my head around that. Maybe it would be beneficial to try to put together some sort of a Cookbook MOS regarding category structure? It's kind of all over the place right now. Using your bread example, would it perhaps make more sense to have [[:Category:Bread recipes]] and [[:Category:Recipes using bread]]? There would be no ambiguity with just those two categories, but when you add the extra [[:Category:Recipes for bread]], that's when things start getting a little whacky. What do you think? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:05, 1 March 2025 (UTC) :::::::Either that or get rid of [[:Category:Bread recipes]] and keep the other two. But one of these categories gotta go, I reckon. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:07, 1 March 2025 (UTC) ::::::::I see you already had the same thought as me. I think all categories should include "for" or "using". Take for example, [[:Category:Recipes for pancakes]] as opposed to [[:Category:Pancake recipes]]. Well obviously there's no recipes using pancakes. But for something like [[:Category:Recipes for gravy]], there may also be a need for [[:Category:Recipes using gravy]]. The lack of consistency in this regard means the only way to achieve consistency across the categories is by changing them over to that format. Sorry for clogging up your talk page! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:18, 1 March 2025 (UTC) :::::::::Same heads-up as below—migrating this over to [[Cookbook talk:Table of Contents]] —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:10, 4 March 2025 (UTC) :Also, on [[Cookbook:Table of Contents]], could you please add a wikilink for [[Cookbook:Breakfast]], and maybe add cooknav to the top for seamless navigation between all the top level articles? Can't edit that article yet. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:47, 1 March 2025 (UTC) == More Table of Content Edits == Hello again. I've been going through everything and this is my list of suggestions for edits to the table of contents. Unfortunately there's not much else I can do for now, because without autoconfirmed my ability to change anything is very limited. I was going to ask for someone to check off the confirmed box for me at RfP but I can't post there either, so I guess I'll be back in four days. * Fix Bread wikilink * Remove "Creaming" from techniques, redirected to Mixing * [[Cookbook:History of Food and Cooking]] points to redirect, needs capitalized * [[Cookbook:Low-Carb]] points to redirect, needs capitalized * [[Cookbook:Cuisine of the Mediterranean]] to [[Cookbook:Mediterranean Cuisine]] for parity * Remove the S from the cuisine wikilinks on ToC, currently redirecting * Create [[:Category:Lunch recipes]], wikilink to ToC * Wikilink [[Cookbook:Dessert]] under Meals * Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category * Create [[Cookbook:East Asian Cuisine]] so I can add the recipes from [[:Category:East Asian recipes]] to it; currently is a redlink on the ToC * Change "Introductory Matter" header to just "Introduction" * Appendix and Equipment sections switch places Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:46, 1 March 2025 (UTC) :I took the liberty of doing it myself in my userspace. You can just copy it over from [[User:MediaKyle/sandbox]]. Figured I'd save you the trouble of trying to figure out what I'm talking about. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 14:15, 1 March 2025 (UTC) :Circling back to this! It seems like your suggestions are getting at a couple different things. I'll try to go through them point-by-point below: :* {{xt|Fix Bread wikilink}} {{done}} :* {{xt|Remove "Creaming" from techniques, redirected to Mixing}} see below comments on TOC. :* {{xt|Cookbook:History of Food and Cooking points to redirect, needs capitalized}} {{not done}} for now because I don't fully understand the urgency and I want to triage/prioritize things for you, but please feel free to make this change yourself once you can! :* {{xt|Cookbook:Low-Carb points to redirect, needs capitalized}} {{not done}} for same reason as above. :* {{xt|Cookbook:Cuisine of the Mediterranean to Cookbook:Mediterranean Cuisine for parity}} {{not done}} for now just because we do have a lot of cuisine pages that follow the form "Cuisine of ____". It could be good to standardize, and I had been planning to do that once I got around to the cuisines. :* {{xt|Remove the S from the cuisine wikilinks on ToC, currently redirecting}} {{not done}} for same reason as other redirects :* {{xt|Create Category:Lunch recipes, wikilink to ToC}} Not quite sure what you mean here, and I didn't see what it corresponded to in your linked sandbox page :* {{xt|Wikilink Cookbook:Dessert under Meals}} {{done}} :* {{xt|Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category}} I'm not sure about this—brunch is in many places considered a separate entity, and I don't necessarily think it would cause confusion. But, overall it's hard to determine whether it should have its own page and TOC link because I haven't actually gotten around to evaluating the meal pages and what role they should play. See also the TOC notes below. :* {{xt|Create Cookbook:East Asian Cuisine so I can add the recipes from Category:East Asian recipes to it; currently is a redlink on the ToC}} {{done}} for now; however, I'm not sure yet whether it will ultimately make sense to keep that as a content page. I think content pages should be reasonably focused, and it may not be the best to have a cuisine page that is so broad. This is something I planned to consider once I made my way around the overhauling the cuisines. :* {{xt|Change "Introductory Matter" header to just "Introduction"}} The reason I made it "Introductory Matter" instead of "Introduction" is because there's already a chapter itself titled "Introduction"—it felt odd to have the entire section titled that as well. Happy to discuss other header options (e.g. "Front Matter", which is a generally accepted book term) :* {{xt|Appendix and Equipment sections switch places}} see below comments on TOC. :* '''Comments on the TOC:''' So, I think a fundamental issue with the current TOC is that it somewhat arbitrarily picks and chooses individual pages to link. It also sometimes direct-links to categories and sometimes to content pages, which I don't think we should do. Because the cookbook is so expansive, it's been established that manual indices intending to capture detail in large areas don't really make sense and quickly get bulky and out-of-date. This is why categorytree is such a useful tool! After thinking on it for a while and making some small tweaks, I think I'd ultimately like to overhaul the TOC and come to a solution that keeps a few broad headers/links to the small handful of the primary content pages while perhaps stashing away more detailed and self-updating lists in a collapsible way to reduce clutter but allow for customizable user navigation. Much to think about, and I'll probably workshop some things on the side to see how they feel. :Let me know if I've misunderstood anything! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:24, 3 March 2025 (UTC) ::Thanks for the notes! Here's my thoughts: ::* On the Cuisine titling, it actually seems like [[Cookbook:Cuisine of the Mediterranean]] and [[Cookbook:East Asian cuisines]] are the only ones that don't follow the naming scheme, i.e. "[[Cookbook:African Cuisine]]", and I think that shorter titles are preferable where it makes sense. ::* On your note about East Asian Cuisine, I actually had the same thought after going through the cuisine pages. Having three separate pages for different kinds of Asian cuisine does seem a little silly, doesn't it? Do you think it might be better to combine all of them under one "Asian Cuisine", but put the different locales under separate headers? ::* On Brunch - I honestly think there's way too much ambiguity around what exactly constitutes as "brunch" to keep that in. I feel as though the term brunch more applies to the time you're eating, rather than the kind of food. I think it would be easier to keep meals that include commonly accepted breakfast foods in the Breakfast category, and things that don't fit neatly into that, into the Lunch category. This would prevent any dilemmas in the future where we can't decide whether something is breakfast or brunch. ::* You're right that it looks a little awkward to have the header as Introduction when there's a page called introduction. I still think that to say "Introductory Matter", or "Front Matter" as you mentioned, is a little long-winded and reflects a more academic tone than needed for a cookbook. Upon further reflection, I think maybe rather than worrying about the header at this point, we should perhaps think about trying to compile all of those short introductory type pages into one comprehensive introductory page. Then we likely won't even need a header for it on the ToC. ::* The ToC is definitely a bit cluttered, and it bothers me too that there's a real lack of consistency across whether the wikilinks lead to a page or a category. I'm not sure how I would feel about cutting away too much of the navigation from it, though, because just about every page on there does have a reason to be there, it's just that they're not presented very nicely. Some of it can certainly get nested or combined though. I'll play around with it over the next few days in my sandbox as well and let you know if I come up with anything. ::* As an aside, the first thing on my to-do list once my autoconfirmed comes through is to start subcategorizing all of the recipes so that they're all nicely sorted in the category trees. When you have a chance, I'd love to hear your thoughts on what we should use as the standard naming for categories. Once we determine this, I think we can also take the liberty of updating the cookbook MoS to reflect it. ::Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:33, 3 March 2025 (UTC) :::Note: After writing this, I realized what you were getting at about slashing away some of the subpages. Maybe we can come up with a system where all of those subpages are under their main subpage rather than on the ToC. For example, all the Cuisines are under [[Cookbook:Cuisines]], all techniques under [[Cookbook:Cooking Techniques]], to keep the subpages off the main ToC. Also, I wonder if maybe we should try to make a centralized discussion for this somewhere, in case anyone else wants to join in at some point? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:45, 3 March 2025 (UTC) ::::Heads-up: to make it easier to keep track of these and since I think they deserve their own discussions, I'm going to gradually migrate them over individually to [[Cookbook talk:Table of Contents]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:52, 4 March 2025 (UTC) :::::Good idea. Can you remove the semi-protection from that talk page? I see no reason why it should be protected. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:23, 4 March 2025 (UTC) == Cookbook ToC == Hi [[User:Kittycataclysm|Kittycataclysm]]. I was just wondering why you didn't respond to my above message, and started a separate sandbox for the ToC instead? It seems as though you don't really want to collaborate. It would be nice if we could work on this together. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 22:43, 2 March 2025 (UTC) :@[[User:MediaKyle|MediaKyle]] thanks for the ping! I'm sorry you feel like I don't want to collaborate—the opposite is true, and please understand that this is good-faith editing. The reason I haven't responded to the above points is mostly since you've been modifying a bunch of content and adding suggestions lately, and I've been working my way through these while continuing with my routine contributions and real life as well—things happen a little more slowly here than on other projects, and I'm the one person dedicated to the cookbook right now. The reason I created that sandbox was because I saw [[Wikibooks:Reading room/General#Modernize the shelves|your comment]] at the reading room and wanted to play around and think about your suggestion without touching the actual TOC. You're right that it's not the best, and it's been something I've been thinking about for a bit now. Please understand also that it can be overwhelming when a new editor unfamiliar with the Cookbook begins making a high volume of edits and suggestions without having much experience with it or its history—this isn't to say that you don't have good ideas or things worth contributing. In fact, you have already made a few helpful changes, as I've mentioned. I just want to do this properly and take the time to evaluate your suggestions together with the current efforts that are underway, and that can take a bit. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:03, 2 March 2025 (UTC) ::Thanks for getting back to me. While I may be new to Wikibooks, I'm certainly not new to MediaWiki, and I've been working with small wiki projects for a number of years. Perhaps it's been a misunderstanding to some degree, but I've found my reception here to be unusually unwelcoming. The way to do this properly, as you said, would be to have discussions and form consensus. Yesterday, when you reached out to me about adding hideroot to the pages, I gave you my rationale and was more than happy to have a discussion about it, but you did not reply. I noticed a similar situation happened with [https://en.wikibooks.org/wiki/User_talk:Ottawahitech#Category_sorting Ottawahitech], regarding category sorting. I'm aware that you're the main person looking after the cookbook right now, which is why I reached out to you right from the get go. ::I understand why you would want to create your own sandbox to play around with options for the ToC, but I'm sure you can understand why it would draw my attention that you would do this without implementing any of the wikilink fixes I mentioned, or making an attempt to discuss it further. This came across to me as not wanting my help. ::I invite you to check out my page on Wikipedia. I've made contributions across quite a wide area of topics there, as well as the other Wikimedia projects, and this is the first time I've encountered any sort of resistance to my contributions. I think Wikibooks has enormous potential, and I'm very excited to contribute to helping it grow. On most projects, this would be something to be encouraged. I don't feel like "I'm sorry that you feel that way" was really an appropriate response. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:59, 2 March 2025 (UTC) :::I think you're right that this has been a mix of misunderstanding and miscommunication, and I think I can understand how things came across as unwelcoming! For whatever it's worth, I absolutely plan on circling back to the various discussions at hand (I have all the relevant pages open to return to), but it seems like the order I did things made it seem like I was ignoring you (if I'm understanding correctly). I am pretty busy, so sometimes items on my to-do list do get lost/shunted or it takes me a bit to get around to something—please don't hesitate to give me a ping if it seems like I'm taking a while to get back to something. Looking forward to more collaboration! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:49, 3 March 2025 (UTC) ::::I'm glad you can understand where I'm coming from. To clarify, my intent is not to try to rush you, or to try to push you to make changes that you don't agree with. It's really easy to misinterpret things over the Internet, and I think a short message can go a long way. I apologize if I've caused you any undue stress by coming into the cookbook and unleashing a flurry of alterations, but do rest assured that I'm not married to any of my changes, I'm always open for discussion, and I want to see the cookbook improve just like you do. The great thing about wikis is that no change is permanent. I think we'll have it in tip-top shape in no time! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:19, 3 March 2025 (UTC) == [[Cookbook:Polish Doughnuts (Paczki)]] == Do you see any reason not to just add this to Featured Recipes? At least we know this one works, and it seems like this is now one of the few recipes to have a picture that actually aligns with the recipe used. I was thinking later on we'll come up with a content review system where a couple editors will actually try the recipes nominated for FR, but in the absence of that I'd just add it to the list. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 12:25, 4 March 2025 (UTC) :I'm fine with adding it to the featured recipes. You're right that we'll want to come up with a good system for this going forward, though it's lower down on my personal priority list at moment. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 March 2025 (UTC) == [[Cookbook:Cream Cheese American Buttercream]] == Hi! I am a wikiHow user and I am planning to adapt this recipe to wikiHow. Since you contributed to this recipe, I wanted to know if I can get permission to reuse your contributions to this recipe. Thanks. [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 21:41, 4 March 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] that's fine with me as long as proper attribution and linking back to the original recipe page here are included at the top. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 4 March 2025 (UTC) == [[A Companion to Our Literary Journey]] == Hi! I feel that we have started to outline the scope in a clearer and more precise way and that’s the work we are going to do with the students this and for the next years, adding more sections and content. Do you think that would be enough? [[User:Ferdi2005|Ferdi2005]] ([[User talk:Ferdi2005|discuss]] • [[Special:Contributions/Ferdi2005|contribs]]) 22:43, 6 March 2025 (UTC) :Hi @[[User:Ferdi2005|Ferdi2005]]! Yes, this seems to be reasonably outlined. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:51, 7 March 2025 (UTC) == Exercising care with copyright == When deleting a page as a copyright violation, it is important that you '''do not quote any content from the deleted page'''. If you do, then your log entry is itself a copyright violation. I have redacted a recent deletion that you performed because of this. If you want to make sure that none of your past deletions have been problematic for this reason, you can [[quarry:query/90444|run this SQL query]] to get a list of every deletion that could be eligible for redaction. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 18:32, 21 March 2025 (UTC) :Hi @[[User:JJPMaster|JJPMaster]] and thank you for the message. In the most recent instance that I think you're referencing, I do not see any material in the edit summary that posed a significant risk—I don't believe the few listed words would be a copyright concern. However, I do understand your concern! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:31, 21 March 2025 (UTC) == Splitting Pages == Hi I have recently made the book on the [[History of the Nawabs of Bengal]] and you gave a notice on how you believe it should be split into smaller bits. As I am still new to wikibooks I don't know how to do this. Can you please assist me on renaming the page so I can split the page into multiple pages? @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 19:47, 29 March 2025 (UTC) :@[[User:Greatswrd|Greatswrd]]: You did it. I've removed the tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 22:44, 29 March 2025 (UTC) :Like @[[User:JJPMaster|JJPMaster]] said, you're all set! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 29 March 2025 (UTC) ::Thanks! @[[User:JJPMaster|JJPMaster]] @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 10:24, 30 March 2025 (UTC) == Minecraft book == Is it good creating pages like this, [[Minecraft#Husk]]? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 12:43, 9 May 2025 (UTC) :@[[User:Cactusisme|Cactusisme]] what do you mean? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:18, 10 May 2025 (UTC) ::are we allowed to create pages like that? like for every mob [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:02, 11 May 2025 (UTC) :::To be honest, I don't think the structure and formatting of the book is very good. Several of the mob pages, for example, have very little information and aren't particularly helpful on their own. If I were working on it, I would restructure the book. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:09, 11 May 2025 (UTC) ::::I am planning to do that. [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 04:19, 12 May 2025 (UTC) == Request to Review Adjusted User Page (XoriantTeam) == Hello [[User:Kittycataclysm|Kittycataclysm]], I hope you're well. I noticed that my user page ([[User:XoriantTeam]]) was recently deleted for appearing promotional or inappropriate for Wikibooks. Thank you for keeping the community standards in check. I’ve since revised the content with closer attention to neutrality and compliance with Wikibooks guidelines. My intent is to participate constructively, especially in areas related to digital engineering and educational content creation. If possible, I’d appreciate your help reviewing the revised version. I'm happy to share it or upload it as a file if there’s a preferred method. Please let me know how best to proceed. I welcome any suggestions and will gladly make further adjustments. Best regards, XoriantTeam [[User:XoriantTeam|XoriantTeam]] ([[User talk:XoriantTeam|discuss]] • [[Special:Contributions/XoriantTeam|contribs]]) 11:02, 15 May 2025 (UTC) :Hi there—you can publish an updated user page, but I'd caution you against talking about your company. Keep it limited to your involvement with Wikibooks. You may contribute productively here, but further promotional materials are grounds for an indefinite block. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:30, 15 May 2025 (UTC) == Planning to use AWB to update categories on the cookbook == Hello. I noticed in recent changes that you were moving some categories using HotCat (e.g. moving Category:Chile recipes to Category:Recipes using chile), which can be time-consuming. Therefore, I plan to help you with moving the cookbook categories by adding myself to enabledusers and enabledbots in [[Wikibooks:AutoWikiBrowser/CheckPageJSON]]. Would this be fine if I assist you and to add myself to the check page? I am familiar with using AWB after testing on a non-Wikimedia project. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:42, 8 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—thank you for the tip! I just installed JWB, so this should make my mass cat changes much faster. Thanks again! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:11, 8 June 2025 (UTC) :: Thank you for the information. Also, is it okay if I change (for example) [[:Category:Vinegar recipes]] to [[:Category:Recipes using vinegar]] (I can redirect the former category to the latter), given that we should move {{tq|Category:[ingredient] recipes}} to {{tq|Category:Recipes using [ingredient]}} for consistency? [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:57, 8 June 2025 (UTC) :::Sure thing—go ahead! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:53, 8 June 2025 (UTC) == Tool for even faster category changes == See [[:c:Help:Gadget-Cat-a-lot#As_your_user_gadget]]. I just [https://en.wikibooks.org/w/index.php?title=User:Koavf/common.js&action=history installed it] and used it dozens of times in a click. Let me know if you need any help. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:36, 19 June 2025 (UTC) :@[[User:Koavf|Koavf]] Thanks! I'm having a little trouble activating it, but I'll keep trying. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:54, 19 June 2025 (UTC) ::A lot of times, a purge will do the trick. See [[:mw:Purge]]. Usually just <kbd>Ctrl+Shift+R</kbd> once or twice. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:55, 19 June 2025 (UTC) :::Took several purges, but we're set now! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:16, 19 June 2025 (UTC) == Advice on when I should run for adminship == Hi, I hope you are doing well. I am asking for some advice on when I should run for enwikibooks adminship, given the following below: Currently, I am doing some optimizations for dark mode on this project, and some of the message box/MediaWiki interface/template pages might be outdated, fully protected, or can use a little help using mw-parser-output. These unfortunately might hinder the process of updating these pages/templates for Vector 2022's dark mode.<br> Additionally, I have a solid expertise with edit filters, as I have requested some administrators to update deprecated filter variables, switching filters from warn and disallow to disallow only, and I can also monitor the filter log for potential false positives (from local or global filters). A fellow English Wikibooks administrator also said to me that they are willing to support me in a few months when I run for adminship, as I am generally trusted. I hold two advanced global permissions, and I hold an edit filter helper permission on the English Wikipedia, to be sure. Thank you for your consideration. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:02, 23 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—good question! I agree that you are a trusted user, and I think it would be reasonable for you to run for adminship, especially given our need to fix up technical aspects of the project. If you don't plan to commit to Wikibooks long-term (i.e. you have some projects you'd like to take a few months to complete and then be done), you can always request temporary adminship. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:30, 23 June 2025 (UTC) :: Thank you for your feedback, but I also plan to monitor for vandalism/spam, and to commit to reduce the administrative assistance reading room backlog, should I be elected for adminship (and I forgot to mention those). Anyway, regarding your feedback, I might run by August or even July, given that I've lately started contributing more often to Wikibooks. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:29, 23 June 2025 (UTC) ::: [[User:Kittycataclysm|Kittycataclysm]], I am pinging you one more time to see if you have read my response above yours. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:34, 26 June 2025 (UTC) ::::Hi @[[User:Codename Noreste|Codename Noreste]]! I'm not sure what you mean—was there an additional question you had? Everything you've outlined seems quite reasonable. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:26, 26 June 2025 (UTC) ::::: Apologies for the confusion, I don't have any questions to ask. I was clarifying that I can help with implementing edit requests and to block obvious vandals and spammers, aside from the skills I mentioned earlier. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:32, 26 June 2025 (UTC) == how is it you feel able to interfere in my sandbox? == you deleted a page in my sandbox that was my way of providing my response to a request from an OpenSCAD dev team leader for a couple of text blurbs for use on a web page of the OpenSCAD site. now that you have deleted my page i have to recreate the texts from a screenshot to be able to offer the suggestions, which i will This kind of high handed treatment is what keeps me from being a wiki-anything contributor .. If it is Wiki policy to interfere in the documentation of an open source project because it is hosted on Wikibooks then i will take up the task of moving our online docs to a site where you cannot interfere. -- [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 21:56, 29 June 2025 (UTC) :Hi @[[User:VulcanWikiEdit|VulcanWikiEdit]]—thanks for bringing this to my attention. I now understand that this was intended to be in your user namespace—I've undeleted it and moved it to the correct namespace for you. Let me know if anything else comes up! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:05, 30 June 2025 (UTC) ::ah .. err .. umm .. well that is a gentle answer to my ire. Thanks for being so gracious [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:29, 30 June 2025 (UTC) ::and .. isn't my sandbox in my namespace by default? [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:30, 30 June 2025 (UTC) :::No worries—it looks like you didn't add the prefix "User:" before writing out the full page titles, so the pages you created were technically in the project's Main space with the official published materials. Going forward, you can just double-check that the page title starts with "'''User:'''VulcanWikiEdit/sandbox", and that should keep everything in the right place! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:36, 30 June 2025 (UTC) ::::BTW .. i love the play on cat lover name [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 15:35, 1 July 2025 (UTC) :::::Thank you! That's very kind. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:46, 1 July 2025 (UTC) == Regarding the user Codename Tameirao == Could this be Matthew again (the Unicode LTA)? I believe it might be him based on his usage of edit summaries, and his usual edits to [[Unicode/Versions]]. I just blocked his recent account, and then I protected and stabilized that Unicode book. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 23:51, 12 August 2025 (UTC) :I suspect you're right! That seems like a reasonable course of action. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:56, 13 August 2025 (UTC) :: I recently encountered another possible LTA, see [[Special:Contributions/~2025-55706-6]] (as well as [[Unicode/Roadmap Blocks]]). I can email you more details if you want. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 16:30, 9 September 2025 (UTC) :::I think this is the same LTA, yes! I've protected [[Unicode/Roadmap Blocks]], but I think it would be a good idea if we could automate this monitoring somewhat using the edit filter. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:07, 9 September 2025 (UTC) :::: I don't think that was Matthew, as he typically uses edit summaries. The deleted page was not protected, as it was protected before you deleted it; I salted it from creation for one year. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:22, 9 September 2025 (UTC) ::::: You might want to look at [[Special:Contributions/Freddy Fazbearing Others]]. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:18, 26 October 2025 (UTC) ::::::Thank you! I went ahead and blocked them. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:54, 28 October 2025 (UTC) == IP block exempt == Hi Kitty, I currently have IP block exemption on enwiki, Commons and Wikidata as I use VPNs connected to my internet security software. Can you please grant me the right on wikibooks. I have a strong password and use two factor authentication. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 10:51, 22 August 2025 (UTC) :Hi @[[User:TarnishedPath|TarnishedPath]]! This doesn't sound unreasonable to me, but I think it would be good if you requested at [[Wikibooks:Requests for permissions]] so we can have a discussion—I have not granted this right before. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:50, 23 August 2025 (UTC) ::Kitty, thanks for pointing me in the right direction. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:25, 23 August 2025 (UTC) ::See [[Wikibooks:Requests_for_permissions#TarnishedPath_(discuss_·_contribs_·_count_·_logs_·_block_log_·_rfp_·_rights)_(IP_Block_Exemption)]] ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:35, 23 August 2025 (UTC) == You've got mail! == {{You've got mail|sig=<span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 00:20, 6 September 2025 (UTC)}} :Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:06, 6 September 2025 (UTC) == Are you able to import? == I made a few requests over at https://en.wikibooks.org/wiki/Wikibooks:Requests_for_import . [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 22:32, 4 October 2025 (UTC) : [[User:2005-Fan|2005-Fan]], I'll go ahead and start the imports. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:29, 5 October 2025 (UTC) ::Thank you for your help [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 16:51, 5 October 2025 (UTC) ::: My apologies for not doing this sooner, because some database error appears when I am trying to mass import. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:39, 5 October 2025 (UTC) ::::I also tried to make this import earlier and ran into issues with the software. I was hoping it was a temporary bug, but it seems to be persisting. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:01, 6 October 2025 (UTC) :::::This seems like I should get involved. {{working}}... [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 13:11, 6 October 2025 (UTC) :::::: I believe there are five pages that have massive page histories they fail to import here. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:13, 6 October 2025 (UTC) :::::::I backed up the XMLs of them locally but im unsure how much that'd do. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 15:18, 6 October 2025 (UTC) ::::::::Just became an importer. The reason is prob understandable but I cannot upload the XML file to here locally. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 17:23, 10 October 2025 (UTC) == About the category parameter in the recipe summary template == When it uses a "recipe by type" category, should it use a "[type/food] recipes" name or "Recipes for [type/food]"? I recently operated JWB to change from [[:Category:Dessert recipes]] to [[:Category:Recipes for dessert]] in multiple Cookbook recipes, and from what I've said before, I've changed to ''Recipes for dessert'' in the category parameter of Cookbook recipes. Hope you don't mind that this was over more than 250 changes (not counting the recent category changes after moving some recipe categories). Thanks. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:07, 27 October 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—those JWB changes you made seem fine to me! I'm not quite sure what you're asking in your first sentence, though. Assuming I understand correctly: in general, I think the default format should be whatever the actual category name is. BUT if there is a redirect, it ultimately shouldn't matter too much. And, because I'm not convinced of the utility of that infobox parameter in the first place (thinking of removing it), I'm not hugely concerned about it for the time being. Does this help? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:21, 27 October 2025 (UTC) :: Probably, but I will say the following below (for my first sentence) to clarify: :: On the <code>|category =</code> parameter, when placing a recipe category name, should it either be {{tq|Sandwich recipes}} or {{tq|Recipes for sandwiches}}? I hope this clears the confusion. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:39, 27 October 2025 (UTC) == Please no more Unicode LTA == Please don't block me again. I promise I will edit Unicode stuff and add correct information. [[Special:Contributions/&#126;2025-30839-28|&#126;2025-30839-28]] ([[User talk:&#126;2025-30839-28|talk]]) 20:54, 1 November 2025 (UTC) :<small>I am a bit out of the loop, so correct me if I'm wrong - I'm assuming here</small> I think the point is that they want you to ''not'' edit the Unicode stuff? Also hi kitty, it's been a ... very long time.. <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:13, 5 November 2025 (UTC) ::Ok so apparently not as long as I thought, but it feels like I've been away for at least a year lol <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:23, 5 November 2025 (UTC) :::Nice to see you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:41, 5 November 2025 (UTC) == Administrator and reviewer user right combinations are not needed anymore == Given that administrators can review edits in addition to reviewers, I would suggest for you (and other administrators) to kindly remove the reviewer permission from (own) accounts. What I'm saying is that if one holds administrator and reviewer permissions together, they can remove the reviewer permission from their own account and retain their administrator permission. Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:06, 11 November 2025 (UTC) :Gotcha—is there a reason it's bad for one user to have both these rights? If so, I can remove my reviewer right. Otherwise, it seems fairly harmless? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:26, 11 November 2025 (UTC) :: The thing is, administrators have the <code>review</code> user right, as well as some permissions in the reviewer user group in the administrator toolset. That means that having the reviewer user group together with the admin user group is redundant. Hope this explains it. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:59, 11 November 2025 (UTC) ::: @[[User:Kittycataclysm|Kittycataclysm]] <s>I'll do this tomorrow morning, as well as to remove autoreviewed user permissions from users who are reviewers.</s> ({{doing}}) [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:24, 12 November 2025 (UTC) : I have removed the autoreviewed user permission from users who are reviewers. As for administrators, I will do so later today. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:40, 13 November 2025 (UTC) == Nesting in Open Book of Ecovillages and Eco Communities == Hi Kittycataclysm, I am editor of wikipedia since 2004. We have the habit if we have a concern using the talk page to clarify the case. I am not sure to delete meaningful content without previous notification and doing major redirection without agreeing the main contributor(s) is an adequate admin act and sign of good manner of host (see [[W:Wikipedia:Etiquette|Wikipedia:Etiquette]].) Yes, It will be not an average book but above the regular. This is the exact case: ''"this may be appropriate, such as with large textbooks that contain subsections with a lot of content."'' ''for to establish good structural and stylistic practices'' I have a data management certification. If you asking it will have 4 nest level on strict purpose. If you saw the introduction of the [[Open Book of Ecovillages and Eco Communities]] is/will be a global collection making effective collaboration over borders and continents. One structured + categorized(!) page for each community willing to show up. The Postal addresses has also same or larger deepness, this is unavoidable (Country/Postal Code/Location/Street/House/floor/door). Here will looks like: '''Eco-comm/Continent/Regio code/Community name''' The goal of this system to open bridge + experience highway for the communities using the same permaculture technics what collected parallelly in [[Open Book of Permaculture]]. That is also part of this knowledge base please dont do simplification steps on that without discussion. I am kindly asking to revert your edits in this book. After that I will put a notification template about "This book is under construction with major changes. Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History. Common clarifications/ guides are on the primary talk page." Thanks: [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 02:22, 12 November 2025 (UTC) :Hi @[[User:Rodrigo|Rodrigo]], and thank you both for your contributions and for reaching out! Yes, I did make the following changes to [[Open Book of Ecovillages and Eco Communities]]: :* I moved the pages from the [[Eco-comm]] namespace to the [[Open Book of Ecovillages and Eco Communities]] namespace, since the table of contents and pages for a given book should be under that book's namespace. :* I removed the links to Wikipedia that were on [[Open Book of Ecovillages and Eco Communities]], since outlinking has been discouraged at en.Wikibooks as a matter of practice. Compilations of links may not fall into WB scope as an instructional text, and [[Wikibooks:Requests for deletion/Piano Solo Music: An Encyclopedia|there is precedent for deleting them]]. But, I do see that the tool I used didn't just remove links to enWP, so I will restore the prior revision and ping the tool developer. :* I flagged it as needing denesting—you're right that nested entries can sometimes be appropriate. In this case, I was primarily flagging for a denest because the table of contents needs to be moved onto the main page, and it shouldn't have hidden navigation within the nested portions. :Could you clarify which of these edits you do not agree with so I can make sure they are individually addressed? As an aside, it could be helpful to create a [[Help:Local manuals of style|local manual of style]] for the book in order to clearly outline the expectations. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:59, 12 November 2025 (UTC) ::My main concern not about moving and flagging but '''deleting''' [[Eco-comm]] against [[Wikibooks:Deletion policy]] and not mentioning in the clarification even after my notification. Should I note all administrators [[Wikibooks:Please do not bite the newcomers]] - or will they do speedy deleting one by one until I make them individually addressed? :::The <u> local manual of style</u> development is ongoing together with the sample pages. ::'''MAIN PAGE''' ::The '''Main page''' and '''Namespace''' is the [[Eco-comm]]. The '''Full Title''' or '''Cover''' is [[Open Book of Ecovillages and Eco Communities]]. Because of the high level of nesting the below extra-long-full-text-title to be avoided the Cover page is a redirection with preface/intro etc. ::'''NESTING ''' :::Featured book with 3 level nesting: [[Social and Cultural Foundations of American Education/Educational Change/Theory]] :::5 level nesting example: [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] ::'''Categories''' The [[:Category:Eco-comm]] will let the users make practical sub-categories e.g. [[:Category:Eco-comm/Project/numundo]] [[:Category:Eco-comm/]] ::: ::[[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 03:44, 18 November 2025 (UTC) :::Thank you for elaborating! I'm unfortunately not sure what you mean about deleting [[Eco-comm]]—are you referring to the fact that I moved it without leaving a redirect? Regarding the nesting, I do honestly think those other books you linked should have their navigation denested since I find their format difficult to parse, and they have some navigation issues. Looping in some other active admins (@[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:Codename Noreste|Codename Noreste]] (@[[User:SHB2000|SHB2000]]) so they can get eyes on this and voice anything they think is important. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 04:12, 18 November 2025 (UTC) ::::It makes no sense to have some crazy abbreviation as a "main page" or "namespace" (whatever that means in this context) for a book in order to allow it to be deep nested. Nobody needs to type the whole name of the nesting because that's what navigation templates do, and it is a simple matter to override the page title. I also take issue with the statement, above, "Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History." Anybody can edit, and nobody gets to own and control any work. Taken together, this complaint looks like a case of attempting to assert ownership and to operate against the normal practices of Wikibooks. As such, I am completely aligned with the changes made. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:49, 18 November 2025 (UTC) :::::That. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 14:59, 18 November 2025 (UTC) ::::Thanks @[[User:MarcGarver|MarcGarver]]@[[User:Leaderboard|Leaderboard]] for the contribution, btw the [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] also looks crazy long, is'nt it? Lets continue in the [[Wikibooks:Reading_room/General]] keeping this page for personal messages. [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 23:07, 20 November 2025 (UTC) == Deletions of Wikibook subpages == Hello @[[User:Kittycataclysm|Kittycataclysm]], regarding the [[Thesis Writing Guide]] subpage deletions, should I just recreate them when I keep working on them or was there an automatic deletion that we could undo? This document will grow, but really slowly. Best, Tim [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 11:37, 16 December 2025 (UTC) :Hi @[[User:TimBorgNetzWerk|TimBorgNetzWerk]]! Since there was so little content on the deleted pages, my recommendation would just be for you to gradually recreate the chapters as you go. Does that make sense? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:54, 17 December 2025 (UTC) ::Makes sense, not my ideal solution, but also not far from it :) The end result will be the same, the in-between will just feel a little bit weird from time to time. ::Thank you for taking time to curate and quality-control Wikibooks - wishing wonderful holidays and a happy new year! [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 20:43, 17 December 2025 (UTC) :::Thank you, and happy holidays to you as well :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:13, 17 December 2025 (UTC) == help with "Media Literacy and You" == {{re|Kittycataclysm}} What do I need to do to get a quality review of ''[[Media Literacy and You]]'', or whatever is needed to remove <nowiki>{{Qr-em|not clear how this is to be structured as a book}}</nowiki>? I ask, because you added that flag just over 2 hours after I created it. I later found that I had accidentally created it as an anonymous user. I've since started using my standard Wikiname, and I tried to respond to the requests both by creating a discussion on the "Discussion" page associated with that book and by upgrading the content. The upgrades included adding the "Introduction" chapter by revising an article on Wikiversity that convinced me to start this Wikibook. I have other articles that I plan to rewrite to create 9 of the remaining 11 chapters in the current table of contents, as indicated in this table of contents. ??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:23, 8 February 2026 (UTC) :Hi @[[User:DavidMCEddy|DavidMCEddy]]! I removed the query flag, since this is clearly not a test page. I do have concerns about the suitability of this book for Wikibooks, since it seems to be more in line with essays and original research/analysis (which are [[Wikibooks:WIW|out of scope here]]). Wikiversity seems like a very suitable place for them—is there a specific reason you want to move them here? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:24, 8 February 2026 (UTC) ::{{re|Kittycataclysm}} ::This book is intended to accelerate the diffusion of [[w:Media literacy|media literacy]] by making it easier for humans to (a) access training materials and (b) connect with research on the most important issues that concern them and (c) discuss those issues with others who may believe differently in a nonthreatening context that encourages dialogue and a shared search for what can honestly be said about any particular issue. This is an extension of "The wisdom of polarized crowds" discussed in [[Wikipedia:Reliability of Wikipedia]]. ::I don't know about you, but I'm frightened by the collapse of nuclear arms control agreements since the year 2000, by global warming, by the threats of the Trump administration to invade Canada and Greenland, etc. If this book project is successful, it will make a material contribution to reversing these trends -- unless this kind of dialogue is [[v:Responding to a nuclear attack|interrupted by a nuclear war]]. === Who is DavidMCEddy === ::I'm a [[w:Vietnam veteran|Vietnam-era veteran]] with a PhD in statistics and a publication record for which [https://www.researchgate.net/profile/Spencer-Graves-3 ReserchGate has found over 1,200 academic publications that have cited my work.] Since [https://xtools.wmcloud.org/ec/en.wikipedia.org/DavidMCEddy 2010 I have logged] * 6,000+ edits in each of Wikipedia and Wikiversity, * 1,000+ in Wikimedia Commons, * 30,000+ in Wikidata, and * almost 1,000 in other Wikimedia Foundation projects like Wikiquote and edits to the Spanish, French and German Wikipedias. This includes dozens of research reports posted to Wikiversity under [[v:Category:Freedom and abundance]] and 44 posts under [[v:Category:Media reform to improve democracy]] that provide a platform for documenting and discussing 44 episodes of a fortnightly "Media & Democracy" series of 29:00 mm:ss podcasts syndicated for the [https://pacificanetwork.org/stations-2/ Pacifica Radio Network] featuring the opinions of leading experts on the increase in political polarization and violence and what those experts think should be done about this. I've just posted another chapter to [[Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. I hope you will agree that this book can make a positive contribution to Wikibooks and to [[w:Jimmy Wales|Jimbo Wales]]' [[w:Wikipedia:Prime objective|Prime Directive]] to create "a world in which every single person on the planet is given free access to the sum of all human knowledge." Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 01:19, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Thank you and I understand this, but I am asking why you think this material is more suitable at Wikibooks rather than at Wikiversity. From what I can see, Wikiversity seems like the more appropriate home for it given our [[Wikibooks:WIW|scope]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:59, 9 February 2026 (UTC) ::{{re|Kittycataclysm}} ::"Media Literacy and You" is textbook to support both self study and classes on media literacy. ::I have been posting content to Wikiversity since 2014 and have not encountered support there for books. A search just now turned up a hint of a book on Wikiversity, but I could not easily find anything on how to do it, etc. ::I think this "Media Literacy and You" project would lose the vast majority of its potential if it were not on Wikibooks. ::??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:22, 9 February 2026 (UTC) {{outdent}} {{re|Kittycataclysm}} Will you please help me with the protocols of creating a book on Wikiversity? 1. I have found documentation that claims that Wikiversity supports such. However, the documentation seems incomplete, potentially out of date, etc. For example, I could not see how to follow the instructions for [[Wikiversity:Help:Books#Step 1: Enable the "Book creator" tool]]. So I posted a question to [[Wikiversity:Help talk:Books]]. 2. What do you suggest I do next? :I can create an article on Wikiversity titled, "Media Literacy and You", and port everything I've posted to Wikibooks there, then replace the pages on Wikibooks with redirects to [[Wikiversity:Media Literacy and You]], [[Wikiversity:Media Literacy and You/Introduction]], and [[Wikiversity:Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. :If you think that's the best way to build this book project, great. It would actually be easier for me, because there would be less translation between what I already have on Wikiversity and a version for Wikibooks. (Also, Wikiversity supports <nowiki>{{cite Q|...}}</nowiki>, which I have used extensively for years.) :Thanks for your help. [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 13:26, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Unfortunately, I am not familiar with the exact workings of Wikiversity, so I can't be much help there. My personal recommendation is that you ask there for help on how best to structure your materials to match the WV requirements. If you'd like some additional opinions/insight, please feel free to also check in at the [[Wikibooks:Reading room/General|reading room]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:22, 10 February 2026 (UTC) ::{{re|Kittycataclysm}} I believe I have finished migrating all of ''Media Literacy and You'' to Wikiversity and replacing the parts of it on Wikibooks with redirects. Comments? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 17:32, 10 February 2026 (UTC) == Thank you! == Heya, thanks for reviewing my stuff! Just to note, the first lesson page was done and so that'll need moving. If you want to discuss anything with me, I am easily reachable on Discord @ xiluosi233. I can explain philosophy, approach, and so on from my teaching experience if you want anything regarding that. [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:48, 17 February 2026 (UTC) :It appears [[An Introduction to the Han Script]] was moved wrong - should it not be [[General Literary Chinese from Scratch/An Introduction to the Han Script]]? [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:52, 17 February 2026 (UTC) ::@[[User:Shira the Mogul|Shira the Mogul]] good catch! I accidentally removed more of the title than intended. I've fixed this now. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:18, 18 February 2026 (UTC) == A test request == Just to see whether a recent Luna update turned out as intended, could you briefly revert your [[User:Kittycataclysm/lunaoptions.json|Luna preferences page]] to the first revision? Since you don't appear to have any custom preferences in the first place, I don't think there should be any conflicts. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 01:49, 30 March 2026 (UTC) :Done! But, it seems to have perhaps auto-updated again immediately afterwards. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:39, 10 April 2026 (UTC) == Linking == Hi,<br> For my edification, why is a link from [[Cookbook:nettle|nettle]] to [[w:Urtica_dioica|Urtica dioica]] not appropriate? The Wikipedia article has more information & seems relevant.<br> Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 01:53, 24 April 2026 (UTC) :@[[User:PeterEasthope|PeterEasthope]] good question! Wikibooks discourages outlinking, since books should be self-contained units. Instead of linking to [[w:Urtica dioica]], the correct approach would be to flesh out the actual chapter here at Wikibooks. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:34, 24 April 2026 (UTC) ::Should all material in the Wikipedia article about Urtica dioica relevant to cooking be duplicated into the nettle article in the cookbook? Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 02:30, 2 May 2026 (UTC) :::@[[User:PeterEasthope|PeterEasthope]] you could do that, although you should only include information that is sourced. However, I recommend that you wait, because I am coincidentally working on the page right now and fleshing it out significantly. I should publish today. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:40, 2 May 2026 (UTC) ::::The nettle page is better now. Thanks. ::::I still wonder, given that the link to ''The Complete Guide to Edible Wild Plants, ...'' is permitted, why not a link to the botanically oriented page in Wikipedia. What if someone reads the Cookbook article and is interested in the toxin for example? Seems that non-Wikimedia references are more privileged than Wikimedia references. ::::Also, by chance, just noticed the [[w:Nettle_soup|Nettle soup]] article in Wikipedia. Better in the Cookbook? ::::Thx, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 19:10, 5 May 2026 (UTC) :::::Another good question. The reason those books are linked is because they are reputable and topical sources for the subject matter (nettles as used in cooking from an instructional perspective), and the links are part of the citations—this makes it different from a simple outlink to a Wikipedia page. Wikipedia pages should also not be cited themselves as sources. Regarding nettle soup, I don't think it makes sense to have that as a standalone page here in the cookbook due to its encyclopedic tone, and I don't see any recipes there. Does this make sense? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:21, 6 May 2026 (UTC) ::::::Somewhat. Certainly a recipe wouldn't be incongruous in a cookbook. Still seems unhelpful that relevant information in Wikipedia is inaccessible from a Wikibook. In effect there's a "Berlin Wall" between two Wikimedia projects. Would a "See also" section be permissible? ::::::Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 14:00, 7 May 2026 (UTC) == You may be an eligible candidate for the U4C election == <div lang="en" dir="ltr" class="mw-content-ltr"> Greetings, The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years. This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required. The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run. In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) </div> <!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&oldid=30471751 --> == Undeletion request == Hello, I am writing to request an undeletion of the page Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad. You stated you are a frequent visitor of the Lentis page and are thus familiar with it. This page was part of a class assignment and was in progress at the time of deletion. The work deleted is what we will be graded on for our class, so we would appreciate the restoration. [[User:Yqj3km|Yqj3km]] ([[User talk:Yqj3km|discuss]] • [[Special:Contributions/Yqj3km|contribs]]) 19:36, 4 May 2026 (UTC) :@[[User:Yqj3km|Yqj3km]] see my response below regarding undeletion. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 May 2026 (UTC) == Undeletion request == About the page on Lentis called Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad: I, too, request undeletion, please. If the authors made any msitakes, the fault is 100 percent mine, for failing to guide them correctly. Like all chapters in this book, this team's chapter is a class assignment. I will be interested also in the reason for deletion so that I can guide authors better. I want to help my students be constructive contributors. Many thanks! [[User:Norton|Norton]] ([[User talk:Norton|discuss]] • [[Special:Contributions/Norton|contribs]]) 20:03, 4 May 2026 (UTC) :Hi @[[User:Norton|Norton]] and thanks for the ping! I deleted it because it was not titled/filed correctly, so I didn't realize it was part of [[Lentis]]. I have undeleted it and moved it to [[Lentis/Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:14, 4 May 2026 (UTC) ::Many, many thanks, @[[User:Kittycataclysm|Kittycataclysm]]! I am very grateful as always for everything you do for Wikibooks! ::[[User:Norton|Norton]] ([[User talk:Norton|discuss]] • [[Special:Contributions/Norton|contribs]]) 22:27, 4 May 2026 (UTC) == Log in issues == Hi, messaging you as you seem to be the most active admin at the moment. I can't log in (as posted at <bdi>[[Wikibooks:Reading room/Administrative Assistance]] and also on my WP page at</bdi> [[w:User_talk:Xania]]). Seems to be an issue with extra security for admins? I am asked to use my authenticator app (which I can't as I have never set it up for Wikibooks) or a recovery code (which I don't have). Any idea what I should do in this situation? Xania [[Special:Contributions/&#126;2026-28255-89|&#126;2026-28255-89]] ([[User talk:&#126;2026-28255-89|talk]]) 18:21, 10 May 2026 (UTC) :Apologies for missing this yesterday! It seems like we have a few people working on it over in the reading room, and I'll keep track there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:37, 11 May 2026 (UTC) == Splitting pages == FYI, I untagged [[Art Print Production Methods]] as for splitting: the page is rather small with its 20 KB and does not need splitting, in my view. Ideally, there would be an operationalized, fairly detailed policy on the matter, but I do not know of one. Single-page books are in [[:Category:One-page books]]. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 04:45, 20 May 2026 (UTC) == <s>Slander</s> == <S>Your tag is slanderous and very easily proven wrong.</s>[https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&diff=prev&oldid=4654455] Given you likely didn't bother to look at the edit history, I would remind you that your given reason that you think it was AI is because you see the chapter is "numbered". That however was 100% my own personal decision after I reviewed my work and thought to myself that I later wrote in the introduction that there is a first to fourth chapter. However I thought to myself that the readers would not be easily made aware of what is meant by first to fourth as I didn't number them - so is why I dedicated an entire edit to make it less ambiguous [https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&diff=prev&oldid=4654328]. I should not have to be falsely penalized because I wanted to be more considerate and ensure better clarity. I do however request AI to help me figure out coding like this - [https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&diff=prev&oldid=4654329] as I don't know how to link. But I intentionally take great efforts to not rely on AI to write that book and find your wrongful presumptions troubling. [[User:JaredMcKenzie|JaredMcKenzie]] ([[User talk:JaredMcKenzie|discuss]] • [[Special:Contributions/JaredMcKenzie|contribs]]) 06:00, 15 July 2026 (UTC) :@[[User:JaredMcKenzie|JaredMcKenzie]] thank you for clarifying! I flagged it for review because it matched a common pattern we see associated with LLM use here. If that is not the case, then nothing needs to happen in that respect; however, you will likely want to fix the lists so that they are correctly formatted in the Wikitext and not hard-written—let me know if you have any questions about that. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:14, 16 July 2026 (UTC) ::Yeah, I don't instantly understand what you mean by "correctly formatted" list. At first, I assumed you were referring to chapter 4 - (''Further reading'')? But I think I know what you mean. I made this edit here [https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&diff=prev&oldid=4654738] to align with how I see wikibooks typically do lists. Did I fix it? If not, feel free to clarify.[[User:JaredMcKenzie|JaredMcKenzie]] ([[User talk:JaredMcKenzie|discuss]] • [[Special:Contributions/JaredMcKenzie|contribs]]) 18:35, 16 July 2026 (UTC) ::I thought about how I responded earlier. Even tho I still disagree, I probably shouldn't have used such a tone. I imagine admins like yourself do a lot of work overseeing wiki and the project owes a lot to you guys. So I take back my harsh words, and I hope we're good.[[User:JaredMcKenzie|JaredMcKenzie]] ([[User talk:JaredMcKenzie|discuss]] • [[Special:Contributions/JaredMcKenzie|contribs]]) 03:38, 17 July 2026 (UTC) :::@[[User:JaredMcKenzie|JaredMcKenzie]] I appreciate that—thank you! And thank you for [[Special:Diff/4654738|making those changes to the lists]], which was indeed what I was referring to. Happy editing! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:31, 17 July 2026 (UTC) == The Geoguide == I literally wrote all of this myself I used no AI if you want to you can highlight the areas that seem way too formal and ill fix them [[User:Kayden Swanson|Kayden Swanson]] ([[User talk:Kayden Swanson|discuss]] • [[Special:Contributions/Kayden Swanson|contribs]]) 04:22, 18 July 2026 (UTC) :Thank you! I have removed the flag. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:41, 20 July 2026 (UTC) == Vandalism == your recent changes may not be constructive. {{Warning}} [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:39, 2 August 2026 (UTC) == Your recent revert == Could you explain [[Special:Diff/4670314]]? This seems to be you ''restoring'' vandalism, which was originally introduced by [[Special:Diff/4669920]]. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 20:06, 15 September 2026 (UTC) :Good catch! Somehow I didn't have the most recent version of a page loaded, and it seems like Luna reverts the most recent edit of a page and not the specific edit you're viewing. The edit in question should be fixed now. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:11, 15 September 2026 (UTC) ::Sorry {{PAGENAME}} for butting in here, I hope you don't mind. ::Just wanted to mention that I have had a few similar experiences when editing (not having the most recent version of a page loaded). Once this caused me friction with an admin who was convinced I was willfully undoing their edit. This happened years ago on another wikimedia project. ::Ottawahitech [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 01:18, 16 September 2026 (UTC) == Confirmed user == <s>If this is one, could I perhaps be a confirmed user? The software has not granted me autoconfirmed, despite me having the requirements.</s> [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:50, 22 September 2026 (UTC) :This is not needed anymore, thank you! [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:58, 22 September 2026 (UTC) == Vandalism on Unicode/Character reference/1F000-1FFFF == I caught the LTA adding Unicode characters which aren't even approved, I undid it, and they reverted. Please semi-protect this page.[[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 15:33, 27 September 2026 (UTC) == Pages by [[User:Ruth Bulyaba M]] == Hello Kittycataclysm, I would like to bring to your attention the pages created by this user. I have used AI checkers to check if the page was created by AI, and it turned out to be positive. I have reached out to the user, to no response. Could you perhaps verify if their pages were created by AI? Thank you. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 11:26, 29 September 2026 (UTC) :Could you perhaps also check [[User:Matovu_Trevor/sandbox|this page]]? Many thanks. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 11:28, 29 September 2026 (UTC) ::After a cursory look, I do agree that these are LLM-generated. I'm starting to see an influx of editors who add LLM generated content to their sandboxes to take advantage of the fact that we are typically much more lenient about what editors do in their sandboxes. However, because I can't see any way for them to edit the material and publish it in a way that still complies with our policy, I'm inclined to delete them—we ban AI-generated ideas, and there is no way to alter the existing material in a way that circumvents that. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:33, 1 October 2026 (UTC) :::I will note, as an aside, that we do not rely on automated AI checkers, which have their own flaws—rather, we should be able to articulate exactly why we believe something to be in violation of the policy. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:34, 1 October 2026 (UTC) == Recipe == Hello Kittycataclysm, I have created a [https://en.wikibooks.org/w/index.php?title=User:MathsScienceNerd1/sandbox&oldid=4678337 recipe] that has been translated from nlwikibooks, and I do not know whether it is suitable for enwikibooks, other than it is a recipe of nlwikibooks and thus may conform to the Cookbook MoS over there. Could you perhaps check the page? Regards, --[[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 12:29, 26 October 2026 (UTC) ==[[:Cookbook:Colcannon (Scottish)]]== {{tmbox|type=delete|text='''Kittycataclysm, please [[Wikibooks:Requests for deletion#Cookbook:Colcannon (Scottish)|share your thoughts]] about whether to [[WB:WIW|keep]] or [[WB:DP|delete]] "[[:Cookbook:Colcannon (Scottish)|Cookbook:Colcannon (Scottish)]]".'''<br />You are being notified because you have contributed to this work. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 11:33, 30 October 2026 (UTC)}} :Thank you for the flag! What was the reasoning for deletion here? I don't see it on the page itself. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:53, 3 November 2026 (UTC) == I have added a tag to a page you created == Hi! I'm MathsScienceNerd1, and I recently reviewed your page, [[:Cookbook:Curry Paste]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. If you believe that your page should not be deleted, please post a message on [[Cookbook talk:Curry Paste|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathsScienceNerd1|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 22:23, 2 November 2026 (UTC) == I have added a tag to a page you created == Hi! I'm MathsScienceNerd1, and I recently reviewed your page, [[:Cookbook:Doubanjiang]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. If you believe that your page should not be deleted, please post a message on [[Cookbook talk:Doubanjiang|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathsScienceNerd1|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 22:29, 2 November 2026 (UTC) == I have added a tag to a page you created == Hi! I'm MathsScienceNerd1, and I recently reviewed your page, [[:Cookbook:Seitan]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. If you believe that your page should not be deleted, please post a message on [[Cookbook talk:Seitan|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathsScienceNerd1|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 22:30, 2 November 2026 (UTC) 7ryfnf0bd7o2r8cettwtjq0pcob85dr 4679836 4679835 2026-11-03T19:55:17Z Kittycataclysm 3371989 /* Cookbook:Colcannon (Scottish) */ Reply 4679836 wikitext text/x-wiki {| class="wikitable" |+ ! colspan="3" |Talk Page Archives |- |[[User talk:Kittycataclysm/Archive 2022|2022]] |[[User talk:Kittycataclysm/Archive 2023|2023]] |[[User talk:Kittycataclysm/Archive 2024|2024]] |} == That IP range calculator == Following [[phab:T381138|T381138]], I have now become the maintainer of the IP range calculator you like. You can find it [[toolforge:ftools/general/ip-range-calc.html|here]]. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 23:10, 9 January 2025 (UTC) :Thank you for the heads-up! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:56, 10 January 2025 (UTC) == A merge and unmerge from two years ago == I was browsing through the history merge log when I saw that you merged [[Cookbook:Chicken Bog]] into [[Cookbook:Chicken Bog I]], and then promptly reverted it. What happened here exactly? Could I correct it? [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 15:55, 10 January 2025 (UTC) :Good question! I can't remember what I was trying to do, but it looks like I didn't succeed at what I wanted based on the log comment. You're just trying to history merge to get [[Cookbook:Chicken Bog I]] to have continuity of history? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:35, 10 January 2025 (UTC) ::I think I figured out your mistake: it outright moved the revisions from the first page to the second, rather than copying them. This would have caused the other two [[Cookbook:Chicken Bog]] pages to have incomplete histories. I think the only solution would be to XML import the pre-April 2023 revisions from the first page to the other three, and I'm not sure if that's the best idea, and I am technically unable to do so. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 16:49, 10 January 2025 (UTC) == Undeletion request == I wouldn't be surprised if you expected this, but I'd like to ask you to undelete the subpages of [[Rotorcraft Fundamentals]] you just deleted with the summary "Use of copyrighted work without permission. Please read Terms of Use: page needs to be imported for attribution", so that I can do that. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 19:54, 14 January 2025 (UTC) :Done! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:57, 14 January 2025 (UTC) ::Upon further investigation, this might actually be a rare case where an [[WB:UT|unmerged transwiki]] is ''preferred'' (this is part of why I stopped calling them "bad transwikis"), since only a small portion of the Wikipedia article (with over 2,000 revisions) was copied over. Importation is generally only needed if the ''majority'' of the page is copied across wikis. I'll just leave a null edit providing attribution and add {{tlx|Copied}}. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 21:19, 14 January 2025 (UTC) == Reusing [[Cookbook:8 Desserts in 1 Pan]] on wikiHow == Hi, I am a user on wikiHow, see [[wikihow:User:Xeverything11]]. I would like to create a new recipe on wikiHow. I wanted to let us know if I can give permission to reuse your contributions to this recipe from Wikibooks to wikiHow. I (as a copyright holder) created this recipe on Wikibooks, but you contributed to this recipe. If not, I'll use the revision before you contributed since I was the only author. Wikibooks uses CC-BY-SA 4.0 while wikiHow uses CC-BY-NC-SA 3.0, which both licenses are incompatible due to ShareAlike conditions. Thanks [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 08:27, 15 January 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] I'm personally fine with this as long as proper attribution is given back to the original recipe page here. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:52, 20 January 2025 (UTC) ::I adapted this [[wikihow:Make-8-Desserts-in-1-Pan|recipe]] on wikiHow with attribution, and got a Rising Star (an achievement used for best new articles on wikiHow). Thank you! [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 19:49, 24 January 2025 (UTC) == Wikibooks community == Hi, @[[User:Kittycataclysm|Kittycataclysm]]! I am trying to contribute more to English Wikibooks. My main contributions will focus on the Cookbook, especially on Indonesian recipes. Do you have a community group where we can discuss and share ideas together? I am looking forward to join. Thank you! [[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 08:47, 16 January 2025 (UTC) :@[[User:Raflinoer32|Raflinoer32]] Sorry I missed this, and welcome! Are you asking about a Cookbook-specific area for discussion? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:39, 20 January 2025 (UTC) ::Yes. Do you know place for this? ::Thank you ::[[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 09:41, 21 January 2025 (UTC) :::Honestly, there's not a centralized Cookbook-specific discussion space, especially since there aren't currently a ton of active contributors. Some people ask questions at [[Cookbook talk:Table of Contents]]. I'm currently the most consistently active and involved Cookbook editor, so feel free to ask me questions! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:46, 22 January 2025 (UTC) == Congratulations! == [[File:Admin T-shirt.svg|thumb|You get this now.]] You are now a permanent administrator. Welcome to the team (I am entitled to say this because I technically got the extension a few hours before you did)!{{FBDB}} [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 10:33, 29 January 2025 (UTC) :Thanks :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:29, 29 January 2025 (UTC) == Is there a way to contact a Steward on WikiBooks? == Hi {{PAGENAME}}, Is there a way to contact a Steward on WB? I tried to find who the active Stewards are here at [[Special:ActiveUsers?username=&groups%5B%5D=steward&wpFormIdentifier=specialactiveusers]] but nothing shows up. The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the [[Wikimania-wiki]], but I just visited the [[wikimania 2014 wiki]] and could not find this backward link. I tried to ask about this on the [[Wikimania 2014 main-page talk]] but disovered that the Stewards have protected it. Is there a way wikibookians can communicate with Stewards at WB? Thanks in advance for answering this non-urgent question, and apologies for all the red-links which I can bluify if needed. Cheers [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 16:37, 7 February 2025 (UTC) :@[[User:Ottawahitech|Ottawahitech]] You can ask this on somewhere like [[metawiki:Steward requests/Miscellaneous]]. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 17:01, 7 February 2025 (UTC) <s>:@[[User:Ottawahitech|Ottawahitech]] seconding what Leaderboard said—we no longer have any active stewards at enWB.</s> Had a brain fade there and mixed up stewards with bureaucrats. Yes, meta is the place for this. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 7 February 2025 (UTC) ::@Kittycataclysm,@[[User:Leaderboard|Leaderboard]], or anyone else: ::Some wikibookians prefer for various reasons to post only at wb. I myself am indef-blocked at META so could not participate at [[metawiki:Steward requests/Miscellaneous]] even if I waned to. ::Since [[Wikimania]] is a topic of interest to all members of the [[wikimedia movement]] why can't wikibookians talk to thier elected representatives here? [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:56, 7 February 2025 (UTC) :::@[[User:Ottawahitech|Ottawahitech]] I can check with the blocking admin to see if they'd be willing to unblock you, if you'd like. The reason things like these are done at Meta is that Meta is a cross-project coordination platform - stewards ''cannot'' be expected to watch every project after all. Now you could message any steward here on Wikibooks if you really wanted to, but that is not normally a good idea. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 02:26, 8 February 2025 (UTC) ::::Wikimania is the annual conference celebrating all the free knowledge projects hosted by the Wikimedia Foundation (WMF). It is a wikimedia initiative which is meant to help all of our projects (including wikibooks), gain more readership, educate more wiki-editors, foster better communications, and much more. The wmf has been hosting a Wikimania-wiki dedicated to each Wikimania annual event since 2004. These wikis contain a wealth of information, but can benefit from wiki-improvements, starting from spelling and grammar errors that detract from their to appeal to the general membership. It would be nice if Stewards paid more attention to it. ::::@[[User:Leaderboard|Leaderboard]], I truly appreciate your offer, but I posted this here not in order to get someone to advocate for one unblocking at META. As I said earlier: ::::* "Some wikibookians prefer for various reasons to post only at wb" ::::* "The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the Wikimania-wiki, but I just visited the wikimania 2014 wiki and could not find this backward link. I tried to ask about this on the Wikimania 2014 main-page talk but disovered that the Stewards have protected it" ::::I would much rather see more wikimedia members question blocking in general at META. One cannot run such large movement of people from different backgrounds and nationalities simply by silencing minorities IMIO. [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:12, 8 February 2025 (UTC) == [[Crystal ball]] == That page appears to be a mixture of isolated paragraphs from [[w:Crystal ball|Crystal ball]], hence my tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 03:04, 9 February 2025 (UTC) :Yep, that seems correct! I also queried it simply because it does not seem suitable for inclusion at all. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:09, 9 February 2025 (UTC) == Question about an edit suggestion == Hi Kittycataclysm, Thanks for the great work you do as an admin! I wanted to clarify a suggestion you made on a recently published page I’m working on. You recommended splitting it into smaller sections—would you suggest creating separate pages for these sections, or would a higher-level header for some topics be sufficient? Any specific recommendations you have would be greatly appreciated! Here’s the link to the page I’m referring to: [[Funding and Finance of Transportation Projects in the United States of America]] Thank you! [[User:Svrmustafa|Svrmustafa]] ([[User talk:Svrmustafa|discuss]] • [[Special:Contributions/Svrmustafa|contribs]]) 18:19, 18 February 2025 (UTC) :Hi @[[User:Svrmustafa|Svrmustafa]], and thanks for asking! Splitting refers to creating new pages, each with a smaller amount of content. The main page should then contain a table of contents, and each page can contain a navigation template for easier navigation. I'll create the table of contents based on the current work and move some content to one of those pages as an example for you; then, you can do the rest. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:26, 19 February 2025 (UTC) ::Following up on this—I noticed that you use the term "paper". However, technically Wikibooks hosts books not papers, so you should probably change this wording. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:38, 19 February 2025 (UTC) == Talkback == {{Talkback|Cookbook talk:Chilli Crab|Recipe Questions}} [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 09:54, 19 February 2025 (UTC) :@[[User:Kittycataclysm|Kittycataclysm]] I also made [[Cookbook:Prata|this]] [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:15, 19 February 2025 (UTC) == Hello == Can you look at my latest recipe? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 00:10, 28 February 2025 (UTC) :I saw it! It needs a few corrections, which I'll note. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:23, 28 February 2025 (UTC) ::@[[User:Kittycataclysm|Kittycataclysm]] How do you write recipe summary, correct headers [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 06:04, 28 February 2025 (UTC) :::Please see [[Cookbook:Policy/Recipe template]]. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:08, 28 February 2025 (UTC) ::::ok [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 02:33, 1 March 2025 (UTC) == Cookbook == Hi there, Kittycataclysm. I wandered over here from Wikipedia, and I'm quite enamoured with this cookbook. I noticed you seem to be the one maintaining it, and I thought I'd reach out. Can I really just start cranking out recipes from public domain cookbooks and my family recipes? It's that simple? I was also wondering about the featured recipes section. There's not very many in there, and I imagine there's not very many folks around to do reviews compared to GAR on Wikipedia. How do you handle content review? Thanks. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:51, 1 March 2025 (UTC) :Hi @[[User:MediaKyle|MediaKyle]] and welcome! For some context, the Cookbook has been around since the very beginning of Wikibooks, but it had gotten into a bit of disarray over the course of about two decades by the time I found it. I started the long process of overhauling, standardizing, and expanding it just over four years ago—I finished standardizing the recipe formatting and quality a while back and am currently working my way through the ingredient pages before moving on to equipment, techniques, and cuisines. You can absolutely add any public domain recipes as well as your own recipes—they just need to conform to the [[Cookbook:Policy/Recipe template|recipe template]] and [[Cookbook:Policy|Cookbook policy overall]]. It's even better if you've made the recipe and can contribute a nice picture and specific guidance/instructions/notes! Please feel free to ask me any questions. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:27, 1 March 2025 (UTC) ::Oh, and regarding the featured recipes section, I actually haven't gotten around to looking into that yet—there's been a lot to do! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:28, 1 March 2025 (UTC) ::That's great, thanks a lot for your response. This is just delightful. Maybe content review is something that we could collaborate on. There's a lot of recipes in here and it would be nice to know which ones are the best. Question for you, [[:Category:Brown sauces]] is really bothering me. How can I move that to Brown sauce recipes? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:29, 1 March 2025 (UTC) :::Good catch on that category! It seems like it was created two decades ago and never got corrected—feel free to recategorize those recipes. Thank you also for introducing the hideprefix parameter to the category trees—I didn't realize that was an option, and it reduces the visual clutter! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:38, 1 March 2025 (UTC) ::::My pleasure! As I continue to look at the categories, this is actually worse than I thought. We have both [[:Category:Sauce recipes]] and [[:Category:Recipes for condiments]] and I suspect that's just the beginning. I want to go through and categorize everything properly, but the bones aren't even there... How long do I have to be here before it'll let me create and move around categories? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:40, 1 March 2025 (UTC) :::::Regarding the categories, the category overhauling is in progress, since I address the category when I overhaul the associated page. The variation in titling is actually somewhat deliberate—I started changing it from "____ recipes" in certain cases to solve a particular categorization problem. Sometimes, there is an item that is used in recipes as an ingredient but for which there are also recipes. For example, [[:Category:Recipes for bread]] versus [[:Category:Recipes using bread]]. The different naming scheme is necessary to properly delineate the categories, and I'm working on implementing it a bit more consistently as I go. While you're still getting started, it would be great if you could check with me when something looks odd or out of place—that way I can take a look and weigh in on whether that's normal or not and maybe provide some context. Just off the top of my head, I think you will have to wait for autoreview status to make move changes. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:56, 1 March 2025 (UTC) ::::::I see what you're saying, I've been trying to wrap my head around that. Maybe it would be beneficial to try to put together some sort of a Cookbook MOS regarding category structure? It's kind of all over the place right now. Using your bread example, would it perhaps make more sense to have [[:Category:Bread recipes]] and [[:Category:Recipes using bread]]? There would be no ambiguity with just those two categories, but when you add the extra [[:Category:Recipes for bread]], that's when things start getting a little whacky. What do you think? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:05, 1 March 2025 (UTC) :::::::Either that or get rid of [[:Category:Bread recipes]] and keep the other two. But one of these categories gotta go, I reckon. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:07, 1 March 2025 (UTC) ::::::::I see you already had the same thought as me. I think all categories should include "for" or "using". Take for example, [[:Category:Recipes for pancakes]] as opposed to [[:Category:Pancake recipes]]. Well obviously there's no recipes using pancakes. But for something like [[:Category:Recipes for gravy]], there may also be a need for [[:Category:Recipes using gravy]]. The lack of consistency in this regard means the only way to achieve consistency across the categories is by changing them over to that format. Sorry for clogging up your talk page! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:18, 1 March 2025 (UTC) :::::::::Same heads-up as below—migrating this over to [[Cookbook talk:Table of Contents]] —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:10, 4 March 2025 (UTC) :Also, on [[Cookbook:Table of Contents]], could you please add a wikilink for [[Cookbook:Breakfast]], and maybe add cooknav to the top for seamless navigation between all the top level articles? Can't edit that article yet. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:47, 1 March 2025 (UTC) == More Table of Content Edits == Hello again. I've been going through everything and this is my list of suggestions for edits to the table of contents. Unfortunately there's not much else I can do for now, because without autoconfirmed my ability to change anything is very limited. I was going to ask for someone to check off the confirmed box for me at RfP but I can't post there either, so I guess I'll be back in four days. * Fix Bread wikilink * Remove "Creaming" from techniques, redirected to Mixing * [[Cookbook:History of Food and Cooking]] points to redirect, needs capitalized * [[Cookbook:Low-Carb]] points to redirect, needs capitalized * [[Cookbook:Cuisine of the Mediterranean]] to [[Cookbook:Mediterranean Cuisine]] for parity * Remove the S from the cuisine wikilinks on ToC, currently redirecting * Create [[:Category:Lunch recipes]], wikilink to ToC * Wikilink [[Cookbook:Dessert]] under Meals * Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category * Create [[Cookbook:East Asian Cuisine]] so I can add the recipes from [[:Category:East Asian recipes]] to it; currently is a redlink on the ToC * Change "Introductory Matter" header to just "Introduction" * Appendix and Equipment sections switch places Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:46, 1 March 2025 (UTC) :I took the liberty of doing it myself in my userspace. You can just copy it over from [[User:MediaKyle/sandbox]]. Figured I'd save you the trouble of trying to figure out what I'm talking about. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 14:15, 1 March 2025 (UTC) :Circling back to this! It seems like your suggestions are getting at a couple different things. I'll try to go through them point-by-point below: :* {{xt|Fix Bread wikilink}} {{done}} :* {{xt|Remove "Creaming" from techniques, redirected to Mixing}} see below comments on TOC. :* {{xt|Cookbook:History of Food and Cooking points to redirect, needs capitalized}} {{not done}} for now because I don't fully understand the urgency and I want to triage/prioritize things for you, but please feel free to make this change yourself once you can! :* {{xt|Cookbook:Low-Carb points to redirect, needs capitalized}} {{not done}} for same reason as above. :* {{xt|Cookbook:Cuisine of the Mediterranean to Cookbook:Mediterranean Cuisine for parity}} {{not done}} for now just because we do have a lot of cuisine pages that follow the form "Cuisine of ____". It could be good to standardize, and I had been planning to do that once I got around to the cuisines. :* {{xt|Remove the S from the cuisine wikilinks on ToC, currently redirecting}} {{not done}} for same reason as other redirects :* {{xt|Create Category:Lunch recipes, wikilink to ToC}} Not quite sure what you mean here, and I didn't see what it corresponded to in your linked sandbox page :* {{xt|Wikilink Cookbook:Dessert under Meals}} {{done}} :* {{xt|Get rid of "Brunch"; will just be confusing alongside a breakfast and lunch category}} I'm not sure about this—brunch is in many places considered a separate entity, and I don't necessarily think it would cause confusion. But, overall it's hard to determine whether it should have its own page and TOC link because I haven't actually gotten around to evaluating the meal pages and what role they should play. See also the TOC notes below. :* {{xt|Create Cookbook:East Asian Cuisine so I can add the recipes from Category:East Asian recipes to it; currently is a redlink on the ToC}} {{done}} for now; however, I'm not sure yet whether it will ultimately make sense to keep that as a content page. I think content pages should be reasonably focused, and it may not be the best to have a cuisine page that is so broad. This is something I planned to consider once I made my way around the overhauling the cuisines. :* {{xt|Change "Introductory Matter" header to just "Introduction"}} The reason I made it "Introductory Matter" instead of "Introduction" is because there's already a chapter itself titled "Introduction"—it felt odd to have the entire section titled that as well. Happy to discuss other header options (e.g. "Front Matter", which is a generally accepted book term) :* {{xt|Appendix and Equipment sections switch places}} see below comments on TOC. :* '''Comments on the TOC:''' So, I think a fundamental issue with the current TOC is that it somewhat arbitrarily picks and chooses individual pages to link. It also sometimes direct-links to categories and sometimes to content pages, which I don't think we should do. Because the cookbook is so expansive, it's been established that manual indices intending to capture detail in large areas don't really make sense and quickly get bulky and out-of-date. This is why categorytree is such a useful tool! After thinking on it for a while and making some small tweaks, I think I'd ultimately like to overhaul the TOC and come to a solution that keeps a few broad headers/links to the small handful of the primary content pages while perhaps stashing away more detailed and self-updating lists in a collapsible way to reduce clutter but allow for customizable user navigation. Much to think about, and I'll probably workshop some things on the side to see how they feel. :Let me know if I've misunderstood anything! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:24, 3 March 2025 (UTC) ::Thanks for the notes! Here's my thoughts: ::* On the Cuisine titling, it actually seems like [[Cookbook:Cuisine of the Mediterranean]] and [[Cookbook:East Asian cuisines]] are the only ones that don't follow the naming scheme, i.e. "[[Cookbook:African Cuisine]]", and I think that shorter titles are preferable where it makes sense. ::* On your note about East Asian Cuisine, I actually had the same thought after going through the cuisine pages. Having three separate pages for different kinds of Asian cuisine does seem a little silly, doesn't it? Do you think it might be better to combine all of them under one "Asian Cuisine", but put the different locales under separate headers? ::* On Brunch - I honestly think there's way too much ambiguity around what exactly constitutes as "brunch" to keep that in. I feel as though the term brunch more applies to the time you're eating, rather than the kind of food. I think it would be easier to keep meals that include commonly accepted breakfast foods in the Breakfast category, and things that don't fit neatly into that, into the Lunch category. This would prevent any dilemmas in the future where we can't decide whether something is breakfast or brunch. ::* You're right that it looks a little awkward to have the header as Introduction when there's a page called introduction. I still think that to say "Introductory Matter", or "Front Matter" as you mentioned, is a little long-winded and reflects a more academic tone than needed for a cookbook. Upon further reflection, I think maybe rather than worrying about the header at this point, we should perhaps think about trying to compile all of those short introductory type pages into one comprehensive introductory page. Then we likely won't even need a header for it on the ToC. ::* The ToC is definitely a bit cluttered, and it bothers me too that there's a real lack of consistency across whether the wikilinks lead to a page or a category. I'm not sure how I would feel about cutting away too much of the navigation from it, though, because just about every page on there does have a reason to be there, it's just that they're not presented very nicely. Some of it can certainly get nested or combined though. I'll play around with it over the next few days in my sandbox as well and let you know if I come up with anything. ::* As an aside, the first thing on my to-do list once my autoconfirmed comes through is to start subcategorizing all of the recipes so that they're all nicely sorted in the category trees. When you have a chance, I'd love to hear your thoughts on what we should use as the standard naming for categories. Once we determine this, I think we can also take the liberty of updating the cookbook MoS to reflect it. ::Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:33, 3 March 2025 (UTC) :::Note: After writing this, I realized what you were getting at about slashing away some of the subpages. Maybe we can come up with a system where all of those subpages are under their main subpage rather than on the ToC. For example, all the Cuisines are under [[Cookbook:Cuisines]], all techniques under [[Cookbook:Cooking Techniques]], to keep the subpages off the main ToC. Also, I wonder if maybe we should try to make a centralized discussion for this somewhere, in case anyone else wants to join in at some point? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:45, 3 March 2025 (UTC) ::::Heads-up: to make it easier to keep track of these and since I think they deserve their own discussions, I'm going to gradually migrate them over individually to [[Cookbook talk:Table of Contents]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:52, 4 March 2025 (UTC) :::::Good idea. Can you remove the semi-protection from that talk page? I see no reason why it should be protected. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:23, 4 March 2025 (UTC) == Cookbook ToC == Hi [[User:Kittycataclysm|Kittycataclysm]]. I was just wondering why you didn't respond to my above message, and started a separate sandbox for the ToC instead? It seems as though you don't really want to collaborate. It would be nice if we could work on this together. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 22:43, 2 March 2025 (UTC) :@[[User:MediaKyle|MediaKyle]] thanks for the ping! I'm sorry you feel like I don't want to collaborate—the opposite is true, and please understand that this is good-faith editing. The reason I haven't responded to the above points is mostly since you've been modifying a bunch of content and adding suggestions lately, and I've been working my way through these while continuing with my routine contributions and real life as well—things happen a little more slowly here than on other projects, and I'm the one person dedicated to the cookbook right now. The reason I created that sandbox was because I saw [[Wikibooks:Reading room/General#Modernize the shelves|your comment]] at the reading room and wanted to play around and think about your suggestion without touching the actual TOC. You're right that it's not the best, and it's been something I've been thinking about for a bit now. Please understand also that it can be overwhelming when a new editor unfamiliar with the Cookbook begins making a high volume of edits and suggestions without having much experience with it or its history—this isn't to say that you don't have good ideas or things worth contributing. In fact, you have already made a few helpful changes, as I've mentioned. I just want to do this properly and take the time to evaluate your suggestions together with the current efforts that are underway, and that can take a bit. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:03, 2 March 2025 (UTC) ::Thanks for getting back to me. While I may be new to Wikibooks, I'm certainly not new to MediaWiki, and I've been working with small wiki projects for a number of years. Perhaps it's been a misunderstanding to some degree, but I've found my reception here to be unusually unwelcoming. The way to do this properly, as you said, would be to have discussions and form consensus. Yesterday, when you reached out to me about adding hideroot to the pages, I gave you my rationale and was more than happy to have a discussion about it, but you did not reply. I noticed a similar situation happened with [https://en.wikibooks.org/wiki/User_talk:Ottawahitech#Category_sorting Ottawahitech], regarding category sorting. I'm aware that you're the main person looking after the cookbook right now, which is why I reached out to you right from the get go. ::I understand why you would want to create your own sandbox to play around with options for the ToC, but I'm sure you can understand why it would draw my attention that you would do this without implementing any of the wikilink fixes I mentioned, or making an attempt to discuss it further. This came across to me as not wanting my help. ::I invite you to check out my page on Wikipedia. I've made contributions across quite a wide area of topics there, as well as the other Wikimedia projects, and this is the first time I've encountered any sort of resistance to my contributions. I think Wikibooks has enormous potential, and I'm very excited to contribute to helping it grow. On most projects, this would be something to be encouraged. I don't feel like "I'm sorry that you feel that way" was really an appropriate response. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:59, 2 March 2025 (UTC) :::I think you're right that this has been a mix of misunderstanding and miscommunication, and I think I can understand how things came across as unwelcoming! For whatever it's worth, I absolutely plan on circling back to the various discussions at hand (I have all the relevant pages open to return to), but it seems like the order I did things made it seem like I was ignoring you (if I'm understanding correctly). I am pretty busy, so sometimes items on my to-do list do get lost/shunted or it takes me a bit to get around to something—please don't hesitate to give me a ping if it seems like I'm taking a while to get back to something. Looking forward to more collaboration! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:49, 3 March 2025 (UTC) ::::I'm glad you can understand where I'm coming from. To clarify, my intent is not to try to rush you, or to try to push you to make changes that you don't agree with. It's really easy to misinterpret things over the Internet, and I think a short message can go a long way. I apologize if I've caused you any undue stress by coming into the cookbook and unleashing a flurry of alterations, but do rest assured that I'm not married to any of my changes, I'm always open for discussion, and I want to see the cookbook improve just like you do. The great thing about wikis is that no change is permanent. I think we'll have it in tip-top shape in no time! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:19, 3 March 2025 (UTC) == [[Cookbook:Polish Doughnuts (Paczki)]] == Do you see any reason not to just add this to Featured Recipes? At least we know this one works, and it seems like this is now one of the few recipes to have a picture that actually aligns with the recipe used. I was thinking later on we'll come up with a content review system where a couple editors will actually try the recipes nominated for FR, but in the absence of that I'd just add it to the list. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 12:25, 4 March 2025 (UTC) :I'm fine with adding it to the featured recipes. You're right that we'll want to come up with a good system for this going forward, though it's lower down on my personal priority list at moment. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 March 2025 (UTC) == [[Cookbook:Cream Cheese American Buttercream]] == Hi! I am a wikiHow user and I am planning to adapt this recipe to wikiHow. Since you contributed to this recipe, I wanted to know if I can get permission to reuse your contributions to this recipe. Thanks. [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 21:41, 4 March 2025 (UTC) :@[[User:Xeverything11|Xeverything11]] that's fine with me as long as proper attribution and linking back to the original recipe page here are included at the top. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 4 March 2025 (UTC) == [[A Companion to Our Literary Journey]] == Hi! I feel that we have started to outline the scope in a clearer and more precise way and that’s the work we are going to do with the students this and for the next years, adding more sections and content. Do you think that would be enough? [[User:Ferdi2005|Ferdi2005]] ([[User talk:Ferdi2005|discuss]] • [[Special:Contributions/Ferdi2005|contribs]]) 22:43, 6 March 2025 (UTC) :Hi @[[User:Ferdi2005|Ferdi2005]]! Yes, this seems to be reasonably outlined. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:51, 7 March 2025 (UTC) == Exercising care with copyright == When deleting a page as a copyright violation, it is important that you '''do not quote any content from the deleted page'''. If you do, then your log entry is itself a copyright violation. I have redacted a recent deletion that you performed because of this. If you want to make sure that none of your past deletions have been problematic for this reason, you can [[quarry:query/90444|run this SQL query]] to get a list of every deletion that could be eligible for redaction. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 18:32, 21 March 2025 (UTC) :Hi @[[User:JJPMaster|JJPMaster]] and thank you for the message. In the most recent instance that I think you're referencing, I do not see any material in the edit summary that posed a significant risk—I don't believe the few listed words would be a copyright concern. However, I do understand your concern! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:31, 21 March 2025 (UTC) == Splitting Pages == Hi I have recently made the book on the [[History of the Nawabs of Bengal]] and you gave a notice on how you believe it should be split into smaller bits. As I am still new to wikibooks I don't know how to do this. Can you please assist me on renaming the page so I can split the page into multiple pages? @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 19:47, 29 March 2025 (UTC) :@[[User:Greatswrd|Greatswrd]]: You did it. I've removed the tag. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 22:44, 29 March 2025 (UTC) :Like @[[User:JJPMaster|JJPMaster]] said, you're all set! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 29 March 2025 (UTC) ::Thanks! @[[User:JJPMaster|JJPMaster]] @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 10:24, 30 March 2025 (UTC) == Minecraft book == Is it good creating pages like this, [[Minecraft#Husk]]? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 12:43, 9 May 2025 (UTC) :@[[User:Cactusisme|Cactusisme]] what do you mean? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:18, 10 May 2025 (UTC) ::are we allowed to create pages like that? like for every mob [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:02, 11 May 2025 (UTC) :::To be honest, I don't think the structure and formatting of the book is very good. Several of the mob pages, for example, have very little information and aren't particularly helpful on their own. If I were working on it, I would restructure the book. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:09, 11 May 2025 (UTC) ::::I am planning to do that. [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 04:19, 12 May 2025 (UTC) == Request to Review Adjusted User Page (XoriantTeam) == Hello [[User:Kittycataclysm|Kittycataclysm]], I hope you're well. I noticed that my user page ([[User:XoriantTeam]]) was recently deleted for appearing promotional or inappropriate for Wikibooks. Thank you for keeping the community standards in check. I’ve since revised the content with closer attention to neutrality and compliance with Wikibooks guidelines. My intent is to participate constructively, especially in areas related to digital engineering and educational content creation. If possible, I’d appreciate your help reviewing the revised version. I'm happy to share it or upload it as a file if there’s a preferred method. Please let me know how best to proceed. I welcome any suggestions and will gladly make further adjustments. Best regards, XoriantTeam [[User:XoriantTeam|XoriantTeam]] ([[User talk:XoriantTeam|discuss]] • [[Special:Contributions/XoriantTeam|contribs]]) 11:02, 15 May 2025 (UTC) :Hi there—you can publish an updated user page, but I'd caution you against talking about your company. Keep it limited to your involvement with Wikibooks. You may contribute productively here, but further promotional materials are grounds for an indefinite block. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:30, 15 May 2025 (UTC) == Planning to use AWB to update categories on the cookbook == Hello. I noticed in recent changes that you were moving some categories using HotCat (e.g. moving Category:Chile recipes to Category:Recipes using chile), which can be time-consuming. Therefore, I plan to help you with moving the cookbook categories by adding myself to enabledusers and enabledbots in [[Wikibooks:AutoWikiBrowser/CheckPageJSON]]. Would this be fine if I assist you and to add myself to the check page? I am familiar with using AWB after testing on a non-Wikimedia project. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:42, 8 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—thank you for the tip! I just installed JWB, so this should make my mass cat changes much faster. Thanks again! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:11, 8 June 2025 (UTC) :: Thank you for the information. Also, is it okay if I change (for example) [[:Category:Vinegar recipes]] to [[:Category:Recipes using vinegar]] (I can redirect the former category to the latter), given that we should move {{tq|Category:[ingredient] recipes}} to {{tq|Category:Recipes using [ingredient]}} for consistency? [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:57, 8 June 2025 (UTC) :::Sure thing—go ahead! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:53, 8 June 2025 (UTC) == Tool for even faster category changes == See [[:c:Help:Gadget-Cat-a-lot#As_your_user_gadget]]. I just [https://en.wikibooks.org/w/index.php?title=User:Koavf/common.js&action=history installed it] and used it dozens of times in a click. Let me know if you need any help. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:36, 19 June 2025 (UTC) :@[[User:Koavf|Koavf]] Thanks! I'm having a little trouble activating it, but I'll keep trying. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:54, 19 June 2025 (UTC) ::A lot of times, a purge will do the trick. See [[:mw:Purge]]. Usually just <kbd>Ctrl+Shift+R</kbd> once or twice. —[[User:Koavf|Justin (<span style="color:grey">ko'''a'''vf</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 00:55, 19 June 2025 (UTC) :::Took several purges, but we're set now! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:16, 19 June 2025 (UTC) == Advice on when I should run for adminship == Hi, I hope you are doing well. I am asking for some advice on when I should run for enwikibooks adminship, given the following below: Currently, I am doing some optimizations for dark mode on this project, and some of the message box/MediaWiki interface/template pages might be outdated, fully protected, or can use a little help using mw-parser-output. These unfortunately might hinder the process of updating these pages/templates for Vector 2022's dark mode.<br> Additionally, I have a solid expertise with edit filters, as I have requested some administrators to update deprecated filter variables, switching filters from warn and disallow to disallow only, and I can also monitor the filter log for potential false positives (from local or global filters). A fellow English Wikibooks administrator also said to me that they are willing to support me in a few months when I run for adminship, as I am generally trusted. I hold two advanced global permissions, and I hold an edit filter helper permission on the English Wikipedia, to be sure. Thank you for your consideration. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:02, 23 June 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—good question! I agree that you are a trusted user, and I think it would be reasonable for you to run for adminship, especially given our need to fix up technical aspects of the project. If you don't plan to commit to Wikibooks long-term (i.e. you have some projects you'd like to take a few months to complete and then be done), you can always request temporary adminship. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:30, 23 June 2025 (UTC) :: Thank you for your feedback, but I also plan to monitor for vandalism/spam, and to commit to reduce the administrative assistance reading room backlog, should I be elected for adminship (and I forgot to mention those). Anyway, regarding your feedback, I might run by August or even July, given that I've lately started contributing more often to Wikibooks. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:29, 23 June 2025 (UTC) ::: [[User:Kittycataclysm|Kittycataclysm]], I am pinging you one more time to see if you have read my response above yours. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:34, 26 June 2025 (UTC) ::::Hi @[[User:Codename Noreste|Codename Noreste]]! I'm not sure what you mean—was there an additional question you had? Everything you've outlined seems quite reasonable. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:26, 26 June 2025 (UTC) ::::: Apologies for the confusion, I don't have any questions to ask. I was clarifying that I can help with implementing edit requests and to block obvious vandals and spammers, aside from the skills I mentioned earlier. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:32, 26 June 2025 (UTC) == how is it you feel able to interfere in my sandbox? == you deleted a page in my sandbox that was my way of providing my response to a request from an OpenSCAD dev team leader for a couple of text blurbs for use on a web page of the OpenSCAD site. now that you have deleted my page i have to recreate the texts from a screenshot to be able to offer the suggestions, which i will This kind of high handed treatment is what keeps me from being a wiki-anything contributor .. If it is Wiki policy to interfere in the documentation of an open source project because it is hosted on Wikibooks then i will take up the task of moving our online docs to a site where you cannot interfere. -- [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 21:56, 29 June 2025 (UTC) :Hi @[[User:VulcanWikiEdit|VulcanWikiEdit]]—thanks for bringing this to my attention. I now understand that this was intended to be in your user namespace—I've undeleted it and moved it to the correct namespace for you. Let me know if anything else comes up! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:05, 30 June 2025 (UTC) ::ah .. err .. umm .. well that is a gentle answer to my ire. Thanks for being so gracious [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:29, 30 June 2025 (UTC) ::and .. isn't my sandbox in my namespace by default? [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:30, 30 June 2025 (UTC) :::No worries—it looks like you didn't add the prefix "User:" before writing out the full page titles, so the pages you created were technically in the project's Main space with the official published materials. Going forward, you can just double-check that the page title starts with "'''User:'''VulcanWikiEdit/sandbox", and that should keep everything in the right place! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:36, 30 June 2025 (UTC) ::::BTW .. i love the play on cat lover name [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 15:35, 1 July 2025 (UTC) :::::Thank you! That's very kind. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:46, 1 July 2025 (UTC) == Regarding the user Codename Tameirao == Could this be Matthew again (the Unicode LTA)? I believe it might be him based on his usage of edit summaries, and his usual edits to [[Unicode/Versions]]. I just blocked his recent account, and then I protected and stabilized that Unicode book. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 23:51, 12 August 2025 (UTC) :I suspect you're right! That seems like a reasonable course of action. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:56, 13 August 2025 (UTC) :: I recently encountered another possible LTA, see [[Special:Contributions/~2025-55706-6]] (as well as [[Unicode/Roadmap Blocks]]). I can email you more details if you want. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 16:30, 9 September 2025 (UTC) :::I think this is the same LTA, yes! I've protected [[Unicode/Roadmap Blocks]], but I think it would be a good idea if we could automate this monitoring somewhat using the edit filter. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:07, 9 September 2025 (UTC) :::: I don't think that was Matthew, as he typically uses edit summaries. The deleted page was not protected, as it was protected before you deleted it; I salted it from creation for one year. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:22, 9 September 2025 (UTC) ::::: You might want to look at [[Special:Contributions/Freddy Fazbearing Others]]. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:18, 26 October 2025 (UTC) ::::::Thank you! I went ahead and blocked them. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:54, 28 October 2025 (UTC) == IP block exempt == Hi Kitty, I currently have IP block exemption on enwiki, Commons and Wikidata as I use VPNs connected to my internet security software. Can you please grant me the right on wikibooks. I have a strong password and use two factor authentication. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 10:51, 22 August 2025 (UTC) :Hi @[[User:TarnishedPath|TarnishedPath]]! This doesn't sound unreasonable to me, but I think it would be good if you requested at [[Wikibooks:Requests for permissions]] so we can have a discussion—I have not granted this right before. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:50, 23 August 2025 (UTC) ::Kitty, thanks for pointing me in the right direction. ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:25, 23 August 2025 (UTC) ::See [[Wikibooks:Requests_for_permissions#TarnishedPath_(discuss_·_contribs_·_count_·_logs_·_block_log_·_rfp_·_rights)_(IP_Block_Exemption)]] ''[[User:TarnishedPath|<b style="color:#ff0000;">Tar</b><b style="color:#ff7070;">nis</b><b style="color:#ffa0a0;">hed</b><b style="color:#420000;">Path</b>]]''<sup>[[User talk:TarnishedPath|<b style="color:#bd4004;">talk</b>]]</sup> 03:35, 23 August 2025 (UTC) == You've got mail! == {{You've got mail|sig=<span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 00:20, 6 September 2025 (UTC)}} :Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:06, 6 September 2025 (UTC) == Are you able to import? == I made a few requests over at https://en.wikibooks.org/wiki/Wikibooks:Requests_for_import . [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 22:32, 4 October 2025 (UTC) : [[User:2005-Fan|2005-Fan]], I'll go ahead and start the imports. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:29, 5 October 2025 (UTC) ::Thank you for your help [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 16:51, 5 October 2025 (UTC) ::: My apologies for not doing this sooner, because some database error appears when I am trying to mass import. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:39, 5 October 2025 (UTC) ::::I also tried to make this import earlier and ran into issues with the software. I was hoping it was a temporary bug, but it seems to be persisting. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:01, 6 October 2025 (UTC) :::::This seems like I should get involved. {{working}}... [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 13:11, 6 October 2025 (UTC) :::::: I believe there are five pages that have massive page histories they fail to import here. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:13, 6 October 2025 (UTC) :::::::I backed up the XMLs of them locally but im unsure how much that'd do. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 15:18, 6 October 2025 (UTC) ::::::::Just became an importer. The reason is prob understandable but I cannot upload the XML file to here locally. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 17:23, 10 October 2025 (UTC) == About the category parameter in the recipe summary template == When it uses a "recipe by type" category, should it use a "[type/food] recipes" name or "Recipes for [type/food]"? I recently operated JWB to change from [[:Category:Dessert recipes]] to [[:Category:Recipes for dessert]] in multiple Cookbook recipes, and from what I've said before, I've changed to ''Recipes for dessert'' in the category parameter of Cookbook recipes. Hope you don't mind that this was over more than 250 changes (not counting the recent category changes after moving some recipe categories). Thanks. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:07, 27 October 2025 (UTC) :Hi @[[User:Codename Noreste|Codename Noreste]]—those JWB changes you made seem fine to me! I'm not quite sure what you're asking in your first sentence, though. Assuming I understand correctly: in general, I think the default format should be whatever the actual category name is. BUT if there is a redirect, it ultimately shouldn't matter too much. And, because I'm not convinced of the utility of that infobox parameter in the first place (thinking of removing it), I'm not hugely concerned about it for the time being. Does this help? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:21, 27 October 2025 (UTC) :: Probably, but I will say the following below (for my first sentence) to clarify: :: On the <code>|category =</code> parameter, when placing a recipe category name, should it either be {{tq|Sandwich recipes}} or {{tq|Recipes for sandwiches}}? I hope this clears the confusion. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:39, 27 October 2025 (UTC) == Please no more Unicode LTA == Please don't block me again. I promise I will edit Unicode stuff and add correct information. [[Special:Contributions/&#126;2025-30839-28|&#126;2025-30839-28]] ([[User talk:&#126;2025-30839-28|talk]]) 20:54, 1 November 2025 (UTC) :<small>I am a bit out of the loop, so correct me if I'm wrong - I'm assuming here</small> I think the point is that they want you to ''not'' edit the Unicode stuff? Also hi kitty, it's been a ... very long time.. <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:13, 5 November 2025 (UTC) ::Ok so apparently not as long as I thought, but it feels like I've been away for at least a year lol <sup>&#8212; [[User:L10nM4st3r|<span style="color:#c71300">L10nM4st3r</span>]]</sup> / <sub>[[User talk:L10nM4st3r|<span style="color:#ce3f00">'''ROAR''' at me!</span>]]</sub> 01:23, 5 November 2025 (UTC) :::Nice to see you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:41, 5 November 2025 (UTC) == Administrator and reviewer user right combinations are not needed anymore == Given that administrators can review edits in addition to reviewers, I would suggest for you (and other administrators) to kindly remove the reviewer permission from (own) accounts. What I'm saying is that if one holds administrator and reviewer permissions together, they can remove the reviewer permission from their own account and retain their administrator permission. Thanks. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:06, 11 November 2025 (UTC) :Gotcha—is there a reason it's bad for one user to have both these rights? If so, I can remove my reviewer right. Otherwise, it seems fairly harmless? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:26, 11 November 2025 (UTC) :: The thing is, administrators have the <code>review</code> user right, as well as some permissions in the reviewer user group in the administrator toolset. That means that having the reviewer user group together with the admin user group is redundant. Hope this explains it. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:59, 11 November 2025 (UTC) ::: @[[User:Kittycataclysm|Kittycataclysm]] <s>I'll do this tomorrow morning, as well as to remove autoreviewed user permissions from users who are reviewers.</s> ({{doing}}) [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:24, 12 November 2025 (UTC) : I have removed the autoreviewed user permission from users who are reviewers. As for administrators, I will do so later today. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:40, 13 November 2025 (UTC) == Nesting in Open Book of Ecovillages and Eco Communities == Hi Kittycataclysm, I am editor of wikipedia since 2004. We have the habit if we have a concern using the talk page to clarify the case. I am not sure to delete meaningful content without previous notification and doing major redirection without agreeing the main contributor(s) is an adequate admin act and sign of good manner of host (see [[W:Wikipedia:Etiquette|Wikipedia:Etiquette]].) Yes, It will be not an average book but above the regular. This is the exact case: ''"this may be appropriate, such as with large textbooks that contain subsections with a lot of content."'' ''for to establish good structural and stylistic practices'' I have a data management certification. If you asking it will have 4 nest level on strict purpose. If you saw the introduction of the [[Open Book of Ecovillages and Eco Communities]] is/will be a global collection making effective collaboration over borders and continents. One structured + categorized(!) page for each community willing to show up. The Postal addresses has also same or larger deepness, this is unavoidable (Country/Postal Code/Location/Street/House/floor/door). Here will looks like: '''Eco-comm/Continent/Regio code/Community name''' The goal of this system to open bridge + experience highway for the communities using the same permaculture technics what collected parallelly in [[Open Book of Permaculture]]. That is also part of this knowledge base please dont do simplification steps on that without discussion. I am kindly asking to revert your edits in this book. After that I will put a notification template about "This book is under construction with major changes. Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History. Common clarifications/ guides are on the primary talk page." Thanks: [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 02:22, 12 November 2025 (UTC) :Hi @[[User:Rodrigo|Rodrigo]], and thank you both for your contributions and for reaching out! Yes, I did make the following changes to [[Open Book of Ecovillages and Eco Communities]]: :* I moved the pages from the [[Eco-comm]] namespace to the [[Open Book of Ecovillages and Eco Communities]] namespace, since the table of contents and pages for a given book should be under that book's namespace. :* I removed the links to Wikipedia that were on [[Open Book of Ecovillages and Eco Communities]], since outlinking has been discouraged at en.Wikibooks as a matter of practice. Compilations of links may not fall into WB scope as an instructional text, and [[Wikibooks:Requests for deletion/Piano Solo Music: An Encyclopedia|there is precedent for deleting them]]. But, I do see that the tool I used didn't just remove links to enWP, so I will restore the prior revision and ping the tool developer. :* I flagged it as needing denesting—you're right that nested entries can sometimes be appropriate. In this case, I was primarily flagging for a denest because the table of contents needs to be moved onto the main page, and it shouldn't have hidden navigation within the nested portions. :Could you clarify which of these edits you do not agree with so I can make sure they are individually addressed? As an aside, it could be helpful to create a [[Help:Local manuals of style|local manual of style]] for the book in order to clearly outline the expectations. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:59, 12 November 2025 (UTC) ::My main concern not about moving and flagging but '''deleting''' [[Eco-comm]] against [[Wikibooks:Deletion policy]] and not mentioning in the clarification even after my notification. Should I note all administrators [[Wikibooks:Please do not bite the newcomers]] - or will they do speedy deleting one by one until I make them individually addressed? :::The <u> local manual of style</u> development is ongoing together with the sample pages. ::'''MAIN PAGE''' ::The '''Main page''' and '''Namespace''' is the [[Eco-comm]]. The '''Full Title''' or '''Cover''' is [[Open Book of Ecovillages and Eco Communities]]. Because of the high level of nesting the below extra-long-full-text-title to be avoided the Cover page is a redirection with preface/intro etc. ::'''NESTING ''' :::Featured book with 3 level nesting: [[Social and Cultural Foundations of American Education/Educational Change/Theory]] :::5 level nesting example: [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] ::'''Categories''' The [[:Category:Eco-comm]] will let the users make practical sub-categories e.g. [[:Category:Eco-comm/Project/numundo]] [[:Category:Eco-comm/]] ::: ::[[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 03:44, 18 November 2025 (UTC) :::Thank you for elaborating! I'm unfortunately not sure what you mean about deleting [[Eco-comm]]—are you referring to the fact that I moved it without leaving a redirect? Regarding the nesting, I do honestly think those other books you linked should have their navigation denested since I find their format difficult to parse, and they have some navigation issues. Looping in some other active admins (@[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:Codename Noreste|Codename Noreste]] (@[[User:SHB2000|SHB2000]]) so they can get eyes on this and voice anything they think is important. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 04:12, 18 November 2025 (UTC) ::::It makes no sense to have some crazy abbreviation as a "main page" or "namespace" (whatever that means in this context) for a book in order to allow it to be deep nested. Nobody needs to type the whole name of the nesting because that's what navigation templates do, and it is a simple matter to override the page title. I also take issue with the statement, above, "Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History." Anybody can edit, and nobody gets to own and control any work. Taken together, this complaint looks like a case of attempting to assert ownership and to operate against the normal practices of Wikibooks. As such, I am completely aligned with the changes made. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:49, 18 November 2025 (UTC) :::::That. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 14:59, 18 November 2025 (UTC) ::::Thanks @[[User:MarcGarver|MarcGarver]]@[[User:Leaderboard|Leaderboard]] for the contribution, btw the [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] also looks crazy long, is'nt it? Lets continue in the [[Wikibooks:Reading_room/General]] keeping this page for personal messages. [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 23:07, 20 November 2025 (UTC) == Deletions of Wikibook subpages == Hello @[[User:Kittycataclysm|Kittycataclysm]], regarding the [[Thesis Writing Guide]] subpage deletions, should I just recreate them when I keep working on them or was there an automatic deletion that we could undo? This document will grow, but really slowly. Best, Tim [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 11:37, 16 December 2025 (UTC) :Hi @[[User:TimBorgNetzWerk|TimBorgNetzWerk]]! Since there was so little content on the deleted pages, my recommendation would just be for you to gradually recreate the chapters as you go. Does that make sense? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:54, 17 December 2025 (UTC) ::Makes sense, not my ideal solution, but also not far from it :) The end result will be the same, the in-between will just feel a little bit weird from time to time. ::Thank you for taking time to curate and quality-control Wikibooks - wishing wonderful holidays and a happy new year! [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 20:43, 17 December 2025 (UTC) :::Thank you, and happy holidays to you as well :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:13, 17 December 2025 (UTC) == help with "Media Literacy and You" == {{re|Kittycataclysm}} What do I need to do to get a quality review of ''[[Media Literacy and You]]'', or whatever is needed to remove <nowiki>{{Qr-em|not clear how this is to be structured as a book}}</nowiki>? I ask, because you added that flag just over 2 hours after I created it. I later found that I had accidentally created it as an anonymous user. I've since started using my standard Wikiname, and I tried to respond to the requests both by creating a discussion on the "Discussion" page associated with that book and by upgrading the content. The upgrades included adding the "Introduction" chapter by revising an article on Wikiversity that convinced me to start this Wikibook. I have other articles that I plan to rewrite to create 9 of the remaining 11 chapters in the current table of contents, as indicated in this table of contents. ??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:23, 8 February 2026 (UTC) :Hi @[[User:DavidMCEddy|DavidMCEddy]]! I removed the query flag, since this is clearly not a test page. I do have concerns about the suitability of this book for Wikibooks, since it seems to be more in line with essays and original research/analysis (which are [[Wikibooks:WIW|out of scope here]]). Wikiversity seems like a very suitable place for them—is there a specific reason you want to move them here? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:24, 8 February 2026 (UTC) ::{{re|Kittycataclysm}} ::This book is intended to accelerate the diffusion of [[w:Media literacy|media literacy]] by making it easier for humans to (a) access training materials and (b) connect with research on the most important issues that concern them and (c) discuss those issues with others who may believe differently in a nonthreatening context that encourages dialogue and a shared search for what can honestly be said about any particular issue. This is an extension of "The wisdom of polarized crowds" discussed in [[Wikipedia:Reliability of Wikipedia]]. ::I don't know about you, but I'm frightened by the collapse of nuclear arms control agreements since the year 2000, by global warming, by the threats of the Trump administration to invade Canada and Greenland, etc. If this book project is successful, it will make a material contribution to reversing these trends -- unless this kind of dialogue is [[v:Responding to a nuclear attack|interrupted by a nuclear war]]. === Who is DavidMCEddy === ::I'm a [[w:Vietnam veteran|Vietnam-era veteran]] with a PhD in statistics and a publication record for which [https://www.researchgate.net/profile/Spencer-Graves-3 ReserchGate has found over 1,200 academic publications that have cited my work.] Since [https://xtools.wmcloud.org/ec/en.wikipedia.org/DavidMCEddy 2010 I have logged] * 6,000+ edits in each of Wikipedia and Wikiversity, * 1,000+ in Wikimedia Commons, * 30,000+ in Wikidata, and * almost 1,000 in other Wikimedia Foundation projects like Wikiquote and edits to the Spanish, French and German Wikipedias. This includes dozens of research reports posted to Wikiversity under [[v:Category:Freedom and abundance]] and 44 posts under [[v:Category:Media reform to improve democracy]] that provide a platform for documenting and discussing 44 episodes of a fortnightly "Media & Democracy" series of 29:00 mm:ss podcasts syndicated for the [https://pacificanetwork.org/stations-2/ Pacifica Radio Network] featuring the opinions of leading experts on the increase in political polarization and violence and what those experts think should be done about this. I've just posted another chapter to [[Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. I hope you will agree that this book can make a positive contribution to Wikibooks and to [[w:Jimmy Wales|Jimbo Wales]]' [[w:Wikipedia:Prime objective|Prime Directive]] to create "a world in which every single person on the planet is given free access to the sum of all human knowledge." Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 01:19, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Thank you and I understand this, but I am asking why you think this material is more suitable at Wikibooks rather than at Wikiversity. From what I can see, Wikiversity seems like the more appropriate home for it given our [[Wikibooks:WIW|scope]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:59, 9 February 2026 (UTC) ::{{re|Kittycataclysm}} ::"Media Literacy and You" is textbook to support both self study and classes on media literacy. ::I have been posting content to Wikiversity since 2014 and have not encountered support there for books. A search just now turned up a hint of a book on Wikiversity, but I could not easily find anything on how to do it, etc. ::I think this "Media Literacy and You" project would lose the vast majority of its potential if it were not on Wikibooks. ::??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:22, 9 February 2026 (UTC) {{outdent}} {{re|Kittycataclysm}} Will you please help me with the protocols of creating a book on Wikiversity? 1. I have found documentation that claims that Wikiversity supports such. However, the documentation seems incomplete, potentially out of date, etc. For example, I could not see how to follow the instructions for [[Wikiversity:Help:Books#Step 1: Enable the "Book creator" tool]]. So I posted a question to [[Wikiversity:Help talk:Books]]. 2. What do you suggest I do next? :I can create an article on Wikiversity titled, "Media Literacy and You", and port everything I've posted to Wikibooks there, then replace the pages on Wikibooks with redirects to [[Wikiversity:Media Literacy and You]], [[Wikiversity:Media Literacy and You/Introduction]], and [[Wikiversity:Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. :If you think that's the best way to build this book project, great. It would actually be easier for me, because there would be less translation between what I already have on Wikiversity and a version for Wikibooks. (Also, Wikiversity supports <nowiki>{{cite Q|...}}</nowiki>, which I have used extensively for years.) :Thanks for your help. [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 13:26, 9 February 2026 (UTC) :@[[User:DavidMCEddy|DavidMCEddy]] Unfortunately, I am not familiar with the exact workings of Wikiversity, so I can't be much help there. My personal recommendation is that you ask there for help on how best to structure your materials to match the WV requirements. If you'd like some additional opinions/insight, please feel free to also check in at the [[Wikibooks:Reading room/General|reading room]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:22, 10 February 2026 (UTC) ::{{re|Kittycataclysm}} I believe I have finished migrating all of ''Media Literacy and You'' to Wikiversity and replacing the parts of it on Wikibooks with redirects. Comments? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 17:32, 10 February 2026 (UTC) == Thank you! == Heya, thanks for reviewing my stuff! Just to note, the first lesson page was done and so that'll need moving. If you want to discuss anything with me, I am easily reachable on Discord @ xiluosi233. I can explain philosophy, approach, and so on from my teaching experience if you want anything regarding that. [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:48, 17 February 2026 (UTC) :It appears [[An Introduction to the Han Script]] was moved wrong - should it not be [[General Literary Chinese from Scratch/An Introduction to the Han Script]]? [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:52, 17 February 2026 (UTC) ::@[[User:Shira the Mogul|Shira the Mogul]] good catch! I accidentally removed more of the title than intended. I've fixed this now. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:18, 18 February 2026 (UTC) == A test request == Just to see whether a recent Luna update turned out as intended, could you briefly revert your [[User:Kittycataclysm/lunaoptions.json|Luna preferences page]] to the first revision? Since you don't appear to have any custom preferences in the first place, I don't think there should be any conflicts. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 01:49, 30 March 2026 (UTC) :Done! But, it seems to have perhaps auto-updated again immediately afterwards. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:39, 10 April 2026 (UTC) == Linking == Hi,<br> For my edification, why is a link from [[Cookbook:nettle|nettle]] to [[w:Urtica_dioica|Urtica dioica]] not appropriate? The Wikipedia article has more information & seems relevant.<br> Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 01:53, 24 April 2026 (UTC) :@[[User:PeterEasthope|PeterEasthope]] good question! Wikibooks discourages outlinking, since books should be self-contained units. Instead of linking to [[w:Urtica dioica]], the correct approach would be to flesh out the actual chapter here at Wikibooks. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:34, 24 April 2026 (UTC) ::Should all material in the Wikipedia article about Urtica dioica relevant to cooking be duplicated into the nettle article in the cookbook? Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 02:30, 2 May 2026 (UTC) :::@[[User:PeterEasthope|PeterEasthope]] you could do that, although you should only include information that is sourced. However, I recommend that you wait, because I am coincidentally working on the page right now and fleshing it out significantly. I should publish today. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:40, 2 May 2026 (UTC) ::::The nettle page is better now. Thanks. ::::I still wonder, given that the link to ''The Complete Guide to Edible Wild Plants, ...'' is permitted, why not a link to the botanically oriented page in Wikipedia. What if someone reads the Cookbook article and is interested in the toxin for example? Seems that non-Wikimedia references are more privileged than Wikimedia references. ::::Also, by chance, just noticed the [[w:Nettle_soup|Nettle soup]] article in Wikipedia. Better in the Cookbook? ::::Thx, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 19:10, 5 May 2026 (UTC) :::::Another good question. The reason those books are linked is because they are reputable and topical sources for the subject matter (nettles as used in cooking from an instructional perspective), and the links are part of the citations—this makes it different from a simple outlink to a Wikipedia page. Wikipedia pages should also not be cited themselves as sources. Regarding nettle soup, I don't think it makes sense to have that as a standalone page here in the cookbook due to its encyclopedic tone, and I don't see any recipes there. Does this make sense? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:21, 6 May 2026 (UTC) ::::::Somewhat. Certainly a recipe wouldn't be incongruous in a cookbook. Still seems unhelpful that relevant information in Wikipedia is inaccessible from a Wikibook. In effect there's a "Berlin Wall" between two Wikimedia projects. Would a "See also" section be permissible? ::::::Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 14:00, 7 May 2026 (UTC) == You may be an eligible candidate for the U4C election == <div lang="en" dir="ltr" class="mw-content-ltr"> Greetings, The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years. This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required. The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run. In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) </div> <!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&oldid=30471751 --> == Undeletion request == Hello, I am writing to request an undeletion of the page Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad. You stated you are a frequent visitor of the Lentis page and are thus familiar with it. This page was part of a class assignment and was in progress at the time of deletion. The work deleted is what we will be graded on for our class, so we would appreciate the restoration. [[User:Yqj3km|Yqj3km]] ([[User talk:Yqj3km|discuss]] • [[Special:Contributions/Yqj3km|contribs]]) 19:36, 4 May 2026 (UTC) :@[[User:Yqj3km|Yqj3km]] see my response below regarding undeletion. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 May 2026 (UTC) == Undeletion request == About the page on Lentis called Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad: I, too, request undeletion, please. If the authors made any msitakes, the fault is 100 percent mine, for failing to guide them correctly. Like all chapters in this book, this team's chapter is a class assignment. I will be interested also in the reason for deletion so that I can guide authors better. I want to help my students be constructive contributors. Many thanks! [[User:Norton|Norton]] ([[User talk:Norton|discuss]] • [[Special:Contributions/Norton|contribs]]) 20:03, 4 May 2026 (UTC) :Hi @[[User:Norton|Norton]] and thanks for the ping! I deleted it because it was not titled/filed correctly, so I didn't realize it was part of [[Lentis]]. I have undeleted it and moved it to [[Lentis/Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:14, 4 May 2026 (UTC) ::Many, many thanks, @[[User:Kittycataclysm|Kittycataclysm]]! I am very grateful as always for everything you do for Wikibooks! ::[[User:Norton|Norton]] ([[User talk:Norton|discuss]] • [[Special:Contributions/Norton|contribs]]) 22:27, 4 May 2026 (UTC) == Log in issues == Hi, messaging you as you seem to be the most active admin at the moment. I can't log in (as posted at <bdi>[[Wikibooks:Reading room/Administrative Assistance]] and also on my WP page at</bdi> [[w:User_talk:Xania]]). Seems to be an issue with extra security for admins? I am asked to use my authenticator app (which I can't as I have never set it up for Wikibooks) or a recovery code (which I don't have). Any idea what I should do in this situation? Xania [[Special:Contributions/&#126;2026-28255-89|&#126;2026-28255-89]] ([[User talk:&#126;2026-28255-89|talk]]) 18:21, 10 May 2026 (UTC) :Apologies for missing this yesterday! It seems like we have a few people working on it over in the reading room, and I'll keep track there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:37, 11 May 2026 (UTC) == Splitting pages == FYI, I untagged [[Art Print Production Methods]] as for splitting: the page is rather small with its 20 KB and does not need splitting, in my view. Ideally, there would be an operationalized, fairly detailed policy on the matter, but I do not know of one. Single-page books are in [[:Category:One-page books]]. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 04:45, 20 May 2026 (UTC) == <s>Slander</s> == <S>Your tag is slanderous and very easily proven wrong.</s>[https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&diff=prev&oldid=4654455] Given you likely didn't bother to look at the edit history, I would remind you that your given reason that you think it was AI is because you see the chapter is "numbered". That however was 100% my own personal decision after I reviewed my work and thought to myself that I later wrote in the introduction that there is a first to fourth chapter. However I thought to myself that the readers would not be easily made aware of what is meant by first to fourth as I didn't number them - so is why I dedicated an entire edit to make it less ambiguous [https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&diff=prev&oldid=4654328]. I should not have to be falsely penalized because I wanted to be more considerate and ensure better clarity. I do however request AI to help me figure out coding like this - [https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&diff=prev&oldid=4654329] as I don't know how to link. But I intentionally take great efforts to not rely on AI to write that book and find your wrongful presumptions troubling. [[User:JaredMcKenzie|JaredMcKenzie]] ([[User talk:JaredMcKenzie|discuss]] • [[Special:Contributions/JaredMcKenzie|contribs]]) 06:00, 15 July 2026 (UTC) :@[[User:JaredMcKenzie|JaredMcKenzie]] thank you for clarifying! I flagged it for review because it matched a common pattern we see associated with LLM use here. If that is not the case, then nothing needs to happen in that respect; however, you will likely want to fix the lists so that they are correctly formatted in the Wikitext and not hard-written—let me know if you have any questions about that. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:14, 16 July 2026 (UTC) ::Yeah, I don't instantly understand what you mean by "correctly formatted" list. At first, I assumed you were referring to chapter 4 - (''Further reading'')? But I think I know what you mean. I made this edit here [https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&diff=prev&oldid=4654738] to align with how I see wikibooks typically do lists. Did I fix it? If not, feel free to clarify.[[User:JaredMcKenzie|JaredMcKenzie]] ([[User talk:JaredMcKenzie|discuss]] • [[Special:Contributions/JaredMcKenzie|contribs]]) 18:35, 16 July 2026 (UTC) ::I thought about how I responded earlier. Even tho I still disagree, I probably shouldn't have used such a tone. I imagine admins like yourself do a lot of work overseeing wiki and the project owes a lot to you guys. So I take back my harsh words, and I hope we're good.[[User:JaredMcKenzie|JaredMcKenzie]] ([[User talk:JaredMcKenzie|discuss]] • [[Special:Contributions/JaredMcKenzie|contribs]]) 03:38, 17 July 2026 (UTC) :::@[[User:JaredMcKenzie|JaredMcKenzie]] I appreciate that—thank you! And thank you for [[Special:Diff/4654738|making those changes to the lists]], which was indeed what I was referring to. Happy editing! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:31, 17 July 2026 (UTC) == The Geoguide == I literally wrote all of this myself I used no AI if you want to you can highlight the areas that seem way too formal and ill fix them [[User:Kayden Swanson|Kayden Swanson]] ([[User talk:Kayden Swanson|discuss]] • [[Special:Contributions/Kayden Swanson|contribs]]) 04:22, 18 July 2026 (UTC) :Thank you! I have removed the flag. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:41, 20 July 2026 (UTC) == Vandalism == your recent changes may not be constructive. {{Warning}} [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:39, 2 August 2026 (UTC) == Your recent revert == Could you explain [[Special:Diff/4670314]]? This seems to be you ''restoring'' vandalism, which was originally introduced by [[Special:Diff/4669920]]. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 20:06, 15 September 2026 (UTC) :Good catch! Somehow I didn't have the most recent version of a page loaded, and it seems like Luna reverts the most recent edit of a page and not the specific edit you're viewing. The edit in question should be fixed now. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:11, 15 September 2026 (UTC) ::Sorry {{PAGENAME}} for butting in here, I hope you don't mind. ::Just wanted to mention that I have had a few similar experiences when editing (not having the most recent version of a page loaded). Once this caused me friction with an admin who was convinced I was willfully undoing their edit. This happened years ago on another wikimedia project. ::Ottawahitech [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 01:18, 16 September 2026 (UTC) == Confirmed user == <s>If this is one, could I perhaps be a confirmed user? The software has not granted me autoconfirmed, despite me having the requirements.</s> [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:50, 22 September 2026 (UTC) :This is not needed anymore, thank you! [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:58, 22 September 2026 (UTC) == Vandalism on Unicode/Character reference/1F000-1FFFF == I caught the LTA adding Unicode characters which aren't even approved, I undid it, and they reverted. Please semi-protect this page.[[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 15:33, 27 September 2026 (UTC) == Pages by [[User:Ruth Bulyaba M]] == Hello Kittycataclysm, I would like to bring to your attention the pages created by this user. I have used AI checkers to check if the page was created by AI, and it turned out to be positive. I have reached out to the user, to no response. Could you perhaps verify if their pages were created by AI? Thank you. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 11:26, 29 September 2026 (UTC) :Could you perhaps also check [[User:Matovu_Trevor/sandbox|this page]]? Many thanks. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 11:28, 29 September 2026 (UTC) ::After a cursory look, I do agree that these are LLM-generated. I'm starting to see an influx of editors who add LLM generated content to their sandboxes to take advantage of the fact that we are typically much more lenient about what editors do in their sandboxes. However, because I can't see any way for them to edit the material and publish it in a way that still complies with our policy, I'm inclined to delete them—we ban AI-generated ideas, and there is no way to alter the existing material in a way that circumvents that. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:33, 1 October 2026 (UTC) :::I will note, as an aside, that we do not rely on automated AI checkers, which have their own flaws—rather, we should be able to articulate exactly why we believe something to be in violation of the policy. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:34, 1 October 2026 (UTC) == Recipe == Hello Kittycataclysm, I have created a [https://en.wikibooks.org/w/index.php?title=User:MathsScienceNerd1/sandbox&oldid=4678337 recipe] that has been translated from nlwikibooks, and I do not know whether it is suitable for enwikibooks, other than it is a recipe of nlwikibooks and thus may conform to the Cookbook MoS over there. Could you perhaps check the page? Regards, --[[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 12:29, 26 October 2026 (UTC) ==[[:Cookbook:Colcannon (Scottish)]]== {{tmbox|type=delete|text='''Kittycataclysm, please [[Wikibooks:Requests for deletion#Cookbook:Colcannon (Scottish)|share your thoughts]] about whether to [[WB:WIW|keep]] or [[WB:DP|delete]] "[[:Cookbook:Colcannon (Scottish)|Cookbook:Colcannon (Scottish)]]".'''<br />You are being notified because you have contributed to this work. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 11:33, 30 October 2026 (UTC)}} :Thank you for the flag! What was the reasoning for deletion here? I don't see it on the page itself. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:53, 3 November 2026 (UTC) ::Ah, my bad! I see it over at RfD. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:55, 3 November 2026 (UTC) == I have added a tag to a page you created == Hi! I'm MathsScienceNerd1, and I recently reviewed your page, [[:Cookbook:Curry Paste]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. If you believe that your page should not be deleted, please post a message on [[Cookbook talk:Curry Paste|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathsScienceNerd1|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 22:23, 2 November 2026 (UTC) == I have added a tag to a page you created == Hi! I'm MathsScienceNerd1, and I recently reviewed your page, [[:Cookbook:Doubanjiang]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. If you believe that your page should not be deleted, please post a message on [[Cookbook talk:Doubanjiang|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathsScienceNerd1|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 22:29, 2 November 2026 (UTC) == I have added a tag to a page you created == Hi! I'm MathsScienceNerd1, and I recently reviewed your page, [[:Cookbook:Seitan]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. If you believe that your page should not be deleted, please post a message on [[Cookbook talk:Seitan|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathsScienceNerd1|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 22:30, 2 November 2026 (UTC) d34p914bor4qmy5v36qama5amcwqyte User talk:Xeverything11/updates 3 452115 4679792 4679526 2026-11-03T14:23:48Z MediaWiki message delivery 1188004 /* Tech News: 2026-45 */ new section 4679792 wikitext text/x-wiki <noinclude> {{User:Xeverything11/tabs}} {{User:Xeverything11/header|Welcome to|Xeverything11's|updates talk page!|archives= * [[User talk:Xeverything11/archives/2022|2022]] * [[User talk:Xeverything11/archives/2023|2023]] }} </noinclude> __NOTOC__ {{User:MiszaBot/config |archive = User talk:Xeverything11/archives/%(year)d |algo = old(60d) |counter = 1 |minthreadsleft = 1 |minthreadstoarchive = 1 }} == Tech News: 2023-03 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/03|Translations]] are available. '''Problems''' * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] The URLs in "{{int:last}}" links on page history now contain <bdi lang="zxx" dir="ltr"><code><nowiki>diff=prev&oldid=[revision ID]</nowiki></code></bdi> in place of <bdi lang="zxx" dir="ltr"><code><nowiki>diff=[revision ID]&oldid=[revision ID]</nowiki></code></bdi>. This is to fix a problem with links pointing to incorrect diffs when history was filtered by a tag. Some user scripts may break as a result of this change. [https://phabricator.wikimedia.org/T243569] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.19|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-01-17|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-01-18|en}}. It will be on all wikis from {{#time:j xg|2023-01-19|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * Some [[mw:Special:MyLanguage/Talk pages project/Usability|changes to the appearance of talk pages]] have only been available on <code>{{ns:1}}:</code> and <code>{{ns:3}}:</code> namespaces. These will be extended to other talk namespaces, such as <code>{{ns:5}}:</code>. They will continue to be unavailable in non-talk namespaces, including <code>{{ns:4}}:</code> pages (e.g., at the Village Pump). You can [[Special:Preferences#mw-prefsection-editing-discussion|change your preferences]] ([[Special:Preferences#mw-prefsection-betafeatures|beta feature]]). [https://phabricator.wikimedia.org/T325417] *On Wikisources, when an image is zoomed or panned in the Page: namespace, the same zoom and pan settings will be remembered for all Page: namespace pages that are linked to a particular Index: namespace page. [https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ProofreadPage/+/868841] * The Vector 2022 skin will become the default for the English Wikipedia desktop users. The change will take place on January 18 at 15:00 UTC. [[:en:w:Wikipedia:Vector 2022|Learn more]]. '''Future changes''' * The 2023 edition of the [[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey]], which invites contributors to make technical proposals and vote for tools and improvements, starts next week on 23 January 2023 at 18:00 UTC. You can start drafting your proposals in [[m:Community Wishlist Survey/Sandbox|the CWS sandbox]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:11, 17 January 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24381020 --> == Tech News: 2023-04 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/04|Translations]] are available. '''Problems''' * Last week, for ~15 minutes, all wikis were unreachable for logged-in users and non-cached pages. This was caused by a timing issue. [https://wikitech.wikimedia.org/wiki/Incidents/2023-01-17_MediaWiki] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.20|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-01-24|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-01-25|en}}. It will be on all wikis from {{#time:j xg|2023-01-26|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * If you have the Beta Feature for [[mw:Special:MyLanguage/Talk pages project|DiscussionTools]] enabled, the appearance of talk pages will add more information about discussion activity. [https://www.mediawiki.org/wiki/Special:MyLanguage/Talk_pages_project/Usability#Status][https://phabricator.wikimedia.org/T317907] * The 2023 edition of the [[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey]] (CWS), which invites contributors to make technical proposals and vote for tools and improvements, starts on Monday 23 January 2023 at [https://zonestamp.toolforge.org/1674496814 18:00 UTC]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:46, 23 January 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24418874 --> == Tech News: 2023-05 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/05|Translations]] are available. '''Problems''' * Last week, for ~15 minutes, some users were unable to log in or edit pages. This was caused by a problem with session storage. [https://wikitech.wikimedia.org/wiki/Incidents/2023-01-24_sessionstore_quorum_issues] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.21|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-01-31|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-01|en}}. It will be on all wikis from {{#time:j xg|2023-02-02|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). '''Future changes''' * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] Wikis that use localized numbering schemes for references need to add new CSS. This will help to show citation numbers the same way in all reading and editing modes. If your wiki would prefer to do it yourselves, please see the [[mw:Special:MyLanguage/Parsoid/Parser Unification/Cite CSS|details and example CSS to copy from]], and also add your wiki to the list. Otherwise, the developers will directly help out starting the week of February 5. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:06, 31 January 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24455949 --> == Wikipedia translation of the week: 2023-06 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sweden Finns' Day]] '''<br /> <small>''([[:fi:Ruotsinsuomalaisten päivä]]) ([[:sv:Sverigefinnarnas dag]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sverigefinskaflaggan.svg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Sweden Finns' Day''' (Finnish: Ruotsinsuomalaisten päivä, Swedish: Sverigefinnarnas dag) is an anniversary celebrated in Sweden on 24 February. The anniversary of the calendar was approved by the Swedish Academy in 2010 and was celebrated for the first time in 2011. February 24 was chosen as the birthday of Carl Axel Gottlund, a collector of folk poetry and a defender of the status of the Finnish language. The purpose of the day is to celebrate the Sweden Finns and to recognize their history, language and culture as a prominent part of Sweden's cultural heritage. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:04, 6 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24491747 --> == Tech News: 2023-06 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/06|Translations]] are available. '''Recent changes''' * In the [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements|Vector 2022 skin]], logged-out users using the full-width toggle will be able to see the setting of their choice even after refreshing pages or opening new ones. This only applies to wikis where Vector 2022 is the default. [https://phabricator.wikimedia.org/T321498] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.22|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-08|en}}. It will be on all wikis from {{#time:j xg|2023-02-09|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * Previously, we announced when some wikis would be in read-only for a few minutes because of a switch of their main database. These switches will not be announced any more, as the read-only time has become non-significant. Switches will continue to happen at 7AM UTC on Tuesdays and Thursdays. [https://phabricator.wikimedia.org/T292543#8568433] * Across all the wikis, in the Vector 2022 skin, logged-in users will see the page-related links such as "What links here" in a [[mw:Special:MyLanguage/Reading/Web/Desktop_Improvements/Features/Page_tools|new side menu]]. It will be displayed on the other side of the screen. This change had previously been made on Czech, English, and Vietnamese Wikipedias. [https://phabricator.wikimedia.org/T328692] *[[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey 2023]] will stop receiving new proposals on [https://zonestamp.toolforge.org/1675706431 Monday, 6 February 2023, at 18:00 UTC]. Proposers should complete any edits by then, to give time for [[m:Special:MyLanguage/Community_Wishlist_Survey/Help_us|translations]] and review. Voting will begin on Friday, 10 February. '''Future changes''' * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] Gadgets and user scripts will be changing to load on desktop and mobile sites. Previously they would only load on the desktop site. It is recommended that wiki administrators audit the [[MediaWiki:Gadgets-definition|gadget definitions]] prior to this change, and add <bdi lang="zxx" dir="ltr"><code>skins=…</code></bdi> for any gadgets which should not load on mobile. [https://phabricator.wikimedia.org/T328610 More details are available]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 10:21, 6 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24491749 --> == Wikipedia translation of the week: 2023-07 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Delivery robot]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Woman Takes Groceries from Dax Delivery Robot.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> A '''delivery robot''' is an autonomous robot that provides "last mile" delivery services. An operator may monitor and take control of the robot remotely in certain situations that the robot cannot resolve by itself such as when it is stuck in an obstacle. Delivery robots can be used in different settings such as food delivery, package delivery, hospital delivery, and room service. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:26, 13 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24515453 --> == Tech News: 2023-07 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/07|Translations]] are available. '''Problems''' * On wikis where patrolled edits are enabled, changes made to the [[mw:Special:MyLanguage/Growth/Communities/How to configure the mentors' list|mentor list]] by autopatrolled mentors are not correctly marked as patrolled. It will be fixed later this week. [https://phabricator.wikimedia.org/T328444] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-15|en}}. It will be on all wikis from {{#time:j xg|2023-02-16|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * The Reply tool and other parts of [[mw:Special:MyLanguage/Help:DiscussionTools#Mobile|DiscussionTools]] will be deployed for all editors using the mobile site. You can [[mw:Special:MyLanguage/Talk_pages_project/Mobile#Status_Updates|read more about this decision]]. [https://phabricator.wikimedia.org/T298060] '''Future changes''' * All wikis will be read-only for a few minutes on March 1. This is planned for [https://zonestamp.toolforge.org/1677679222 14:00 UTC]. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T328287][https://phabricator.wikimedia.org/T327920][https://wikitech.wikimedia.org/wiki/Deployments] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:49, 14 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24540832 --> == Wikipedia translation of the week: 2023-08 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Buddha Dhatu Jadi]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Swarno Mandir.JPG|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Buddha Dhatu Jadi''' (Bengali: বুদ্ধ ধাতু জাদি; Burmese: ဗုဒ္ဓဓာတုစေတီ also known as the Bandarban Golden Temple) is located close to Balaghata town, in Bandarban City, in Bangladesh. Dhatu are the material remains of a holy person, and in this temple the relics belong to Buddha. It is the largest Theravada Buddhist temple in Bangladesh and has the second-largest Buddha statue in the country. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:18, 20 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24581813 --> == Tech News: 2023-08 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/08|Translations]] are available. '''Problems''' * Last week, during planned maintenance of Cloud Services, unforeseen complications forced the team to turn off all tools for 2–3 hours to prevent data corruption. Work is ongoing to prevent similar problems in the future. [https://phabricator.wikimedia.org/T329535] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-21|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-02-22|en}}. It will be on all wikis from {{#time:j xg|2023-02-23|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). *The voting phase for the [[m:Special:MyLanguage/Community Wishlist Survey 2023|Community Wishlist Survey 2023]] ends on [https://zonestamp.toolforge.org/1677261621 24 February at 18:00 UTC]. The results of the survey will be announced on 28 February. '''Future changes''' * All wikis will be read-only for a few minutes on March 1. This is planned for [https://zonestamp.toolforge.org/1677679222 14:00 UTC]. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T328287][https://phabricator.wikimedia.org/T327920][https://wikitech.wikimedia.org/wiki/Deployments] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:58, 21 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24570514 --> == Wikipedia translation of the week: 2023-09 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Alina Scholtz]] '''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Alina Scholtz''' (24 September 1908 – 25 February 1996) was a Polish landscape architect, known as one of country's pioneers in developing the field. Throughout her career she worked on various public and private projects for cemeteries, parks and green spaces. Some of her most noted works include the grounds of a villa on Kielecka Street in Warsaw for which she won a Silver Medal at the 1937 World Exhibition in Paris, the memorial cemetery to the victims of the Palmiry massacre, and landscaping projects along the East-West traffic route of Warsaw. In addition to her design work, she served as one of the founding members of the International Federation of Landscape Architects. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:04, 27 February 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24617511 --> == Tech News: 2023-09 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/09|Translations]] are available. '''Problems''' * Last week, in some areas of the world, there were problems with loading pages for 20 minutes and saving edits for 55 minutes. These issues were caused by a problem with our caching servers due to unforseen events during a routine maintenance task. [https://wikitech.wikimedia.org/wiki/Incidents/2023-02-22_wiki_outage][https://wikitech.wikimedia.org/wiki/Incidents/2023-02-22_read_only] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.25|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-02-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-01|en}}. It will be on all wikis from {{#time:j xg|2023-03-02|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * All wikis will be read-only for a few minutes on March 1. This is planned for [https://zonestamp.toolforge.org/1677679222 14:00 UTC]. [https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:47, 27 February 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24634242 --> == Wikipedia translation of the week: 2023-10 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Mary Nzimiro]] '''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Mary Nzimiro''', birthname Mary Nwametu Onumonu, MBE (1898–1993) was a pioneering Nigerian businesswoman, politician and women's activist. In 1948, she was appointed principal representative of the United Africa Company (UAC) for Eastern Nigeria, while maintaining textile and cosmetics retail outlets of her own in Port Harcourt, Aba and Owerri. By the early 1950s, she was among the richest individuals in West Africa, becoming a resident of the exclusive Bernard Carr Street in Port Harcourt. On the political front, she was a member of the influential National Council of Nigeria and the Cameroons, becoming a member of its executive committee in 1957 and vice-president of the NCNC Estern Women's Association in 1962. During the Nigerian Civil War (1967–1970), she organized Igbo women in support of the Biafrans. As a result she lost most of her property in Port Harcourt and returned to her native Oguta where she died in 1993. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:47, 6 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24636259 --> == Tech News: 2023-10 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/10|Translations]] are available. '''Recent changes''' * The Community Wishlist Survey 2023 edition has been concluded. Community Tech has [[m:Special:MyLanguage/Community Wishlist Survey 2023/Results|published the results]] of the survey and will provide an update on what is next in April 2023. * On wikis which use [[mw:Special:MyLanguage/Writing_systems|LanguageConverter]] to handle multiple writing systems, articles which used custom conversion rules in the wikitext (primarily on Chinese Wikipedia) would have these rules applied inconsistently in the table of contents, especially in the Vector 2022 skin. This has now been fixed. [https://phabricator.wikimedia.org/T306862] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.26|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-08|en}}. It will be on all wikis from {{#time:j xg|2023-03-09|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * A search system has been added to the [[Special:Preferences|Preferences screen]]. This will let you find different options more easily. Making it work on mobile devices will happen soon. [https://phabricator.wikimedia.org/T313804] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:50, 6 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24676916 --> == Wikipedia translation of the week: 2023-11 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Elizabeth Langdon Williams]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Elizabeth Langdon Williams.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Elizabeth Langdon Williams''' (February 8, 1879 in Putnam, Connecticut – 1981 in Enfield, New Hampshire) was an American human computer and astronomer whose work helped lead to the discovery of Pluto, or Planet X. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:21, 13 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24700408 --> == Tech News: 2023-11 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/11|Translations]] are available. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.40/wmf.27|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-15|en}}. It will be on all wikis from {{#time:j xg|2023-03-16|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-cbk_zamwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cdowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cebwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-chwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-chrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-chywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ckbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-csbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cuwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-itwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T304542][https://phabricator.wikimedia.org/T304550] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:20, 13 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24700189 --> == Wikipedia translation of the week: 2023-12 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:I Didn't Raise My Boy to Be a Soldier]] '''<br /> </div> Please be bold and help translate this article! ---- [[File:Peerless Quartet - I Didn't Raise my Boy to be a Soldier.ogg|300px|center]] <div style="text-align:left; padding: .4em;"> an American anti-war song that was influential within the pacifist movement that existed in the United States before it entered World War I. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:31, 20 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24720571 --> == Tech News: 2023-12 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/12|Translations]] are available. '''Problems''' * Last week, some users experienced issues loading image thumbnails. This was due to incorrectly cached images. [https://phabricator.wikimedia.org/T331820] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.1|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-21|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-22|en}}. It will be on all wikis from {{#time:j xg|2023-03-23|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] A link to the user's [[{{#special:CentralAuth}}]] page will appear on [[{{#special:Contributions}}]] — some user scripts which previously added this link may cause conflicts. This feature request was [[:m:Community Wishlist Survey 2023/Admins and patrollers/Add link to CentralAuth on Special:Contributions|voted #17 in the 2023 Community Wishlist Survey]]. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The [[{{#special:AbuseFilter}}]] edit window will be resizable and larger by default. This feature request was [[:m:Community Wishlist Survey 2023/Anti-harassment/Make the AbuseFilter edit window resizable and larger by default|voted #80 in the 2023 Community Wishlist Survey]]. * There will be a new option for Administrators when they are unblocking a user, to add the unblocked user’s user page to their watchlist. This will work both via [[{{#special:Unblock}}]] and via the API. [https://phabricator.wikimedia.org/T257662] '''Meetings''' * You can join the next meeting with the Wikipedia mobile apps teams. During the meeting, we will discuss the current features and future roadmap. The meeting will be on [https://zonestamp.toolforge.org/1679677204 24 March at 17:00 (UTC)]. See [[mw:Special:MyLanguage/Wikimedia Apps/Office Hours|details and how to join]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:26, 21 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24732558 --> == Wikipedia translation of the week: 2023-13 {{User:Xeverything11/tags/updates}} == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:es:Diana Aguavil]]'''<br /> <small>''([[:en:Diana Aguavil]]) ([[:pt:Diana Aguavil]]) ''</small> </div> Please be bold and help translate this article! ---- [[File:Diana Aguavil.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Diana Alexandra Aguavil Calazacón''' (born 7 August 1983) is an Ecuadorian indigenous leader, since 25 August 2018, the first female governor of the Tsáchila nationality after 104 years of male administrations and winning the 2018 Tsáchila election. She was also the second woman to become a candidate. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:39, 27 March 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24758626 --> == Tech News: 2023-13 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/13|Translations]] are available. '''Recent changes''' * The [[:mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilter]] condition limit was increased from 1000 to 2000. [https://phabricator.wikimedia.org/T309609] * [[:m:Special:MyLanguage/Global AbuseFilter#Locally disabled actions|Some Global AbuseFilter]] actions will no longer apply to local projects. [https://phabricator.wikimedia.org/T332521] * Desktop users are now able to subscribe to talk pages by clicking on the {{int:discussiontools-newtopicssubscription-button-subscribe-label}} link in the {{int:toolbox}} menu. If you subscribe to a talk page, you receive [[mw:Special:MyLanguage/Notifications|notifications]] when new topics are started on that talk page. This is separate from putting the page on your watchlist or subscribing to a single discussion. [https://phabricator.wikimedia.org/T263821] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.2|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-03-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-03-29|en}}. It will be on all wikis from {{#time:j xg|2023-03-30|en}} ([[mw:MediaWiki 1.40/Roadmap|calendar]]). '''Future changes''' * You will be able to choose [[mw:Special:MyLanguage/VisualEditor/Diffs|visual diffs]] on all [[m:Special:MyLanguage/Help:Page history|history pages]] at the Wiktionaries and Wikipedias. [https://phabricator.wikimedia.org/T314588] * [[File:Octicons-tools.svg|15px|link=|alt=|Advanced item]] The legacy [[mw:Mobile Content Service|Mobile Content Service]] is going away in July 2023. Developers are encouraged to switch to Parsoid or another API before then to ensure service continuity. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/4MVQQTONJT7FJAXNVOFV3WWVVMCHRINE/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:14, 28 March 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24780854 --> == Tech News: 2023-14 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/14|Translations]] are available. '''Recent changes''' * The system for automatically creating categories for the [[mw:Special:MyLanguage/Extension:Babel|Babel]] extension has had several important changes and fixes. One of them allows you to insert templates for automatic category descriptions on creation, allowing you to categorize the new categories. [https://phabricator.wikimedia.org/T211665][https://phabricator.wikimedia.org/T64714][https://phabricator.wikimedia.org/T170654][https://phabricator.wikimedia.org/T184941][https://phabricator.wikimedia.org/T33074] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.3|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-04|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-05|en}}. It will be on all wikis from {{#time:j xg|2023-04-06|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Some older [[w:en:Web browser|Web browsers]] will stop being able to use [[w:en:JavaScript|JavaScript]] on Wikimedia wikis from this week. This mainly affects users of Internet Explorer 11. If you have an old web browser on your computer you can try to upgrade to a newer version. [https://phabricator.wikimedia.org/T178356] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The deprecated <bdi lang="zxx" dir="ltr"><code>jquery.hoverIntent</code></bdi> module has been removed. This module could be used by gadgets and user scripts, to create an artificial delay in how JavaScript responds to a hover event. Gadgets and user scripts should now use jQuery <bdi lang="zxx" dir="ltr"><code>hover()</code></bdi> or <bdi lang="zxx" dir="ltr"><code>on()</code></bdi> instead. Examples can be found in the [[mw:Special:MyLanguage/ResourceLoader/Migration_guide_(users)#jquery.hoverIntent|migration guide]]. [https://phabricator.wikimedia.org/T311194] * Some of the links in [[{{#special:SpecialPages}}]] will be re-arranged. There will be a clearer separation between links that relate to all users, and links related to your own user account. [https://phabricator.wikimedia.org/T333242] * You will be able to hide the [[mw:Special:MyLanguage/Talk pages project/Replying|Reply button]] in archived discussion pages with a new <bdi lang="zxx" dir="ltr"><code><nowiki>__ARCHIVEDTALK__</nowiki></code></bdi> magic word. There will also be a new <bdi lang="zxx" dir="ltr"><code>.mw-archivedtalk</code></bdi> CSS class for hiding the Reply button in individual sections on a page. [https://phabricator.wikimedia.org/T249293][https://phabricator.wikimedia.org/T295553][https://gerrit.wikimedia.org/r/c/mediawiki/extensions/DiscussionTools/+/738221] '''Future changes''' * The Vega software that creates data visualizations in pages, such as graphs, will be upgraded to the newest version in the future. Graphs that still use the very old version 1.5 syntax may stop working properly. Most existing uses have been found and updated, but you can help to check, and to update any local documentation. [[phab:T260542|Examples of how to find and fix these graphs are available]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:40, 3 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24820268 --> == Tech News: 2023-15 {{User:Xeverything11/tags/updates}} == <section begin="technews-2023-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/15|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] In the visual editor, it is now possible to edit captions of images in galleries without opening the gallery dialog. This feature request was [[:m:Community Wishlist Survey 2023/Editing/Editable gallery captions in Visual Editor|voted #61 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T190224] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] You can now receive notifications when another user edits your user page. See the "{{int:Echo-category-title-edit-user-page}}" option in [[Special:Preferences#mw-prefsection-echo|your Preferences]]. This feature request was [[:m:Community Wishlist Survey 2023/Anti-harassment/Notifications for user page edits|voted #3 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T3876] '''Problems''' * There was a problem with all types of CentralNotice banners still being shown to logged-in users even if they had [[Special:Preferences#mw-prefsection-centralnotice-banners|turned off]] specific banner types. This has now been fixed. [https://phabricator.wikimedia.org/T331671] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.4|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-11|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-12|en}}. It will be on all wikis from {{#time:j xg|2023-04-13|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-arywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dinwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dsbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-eewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-elwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-emlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-eowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-etwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-euwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-extwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tumwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ffwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fiu_vrowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fjwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frpwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-furwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gcrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-glwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-glkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gomwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gotwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-guwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-gvwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T304551][https://phabricator.wikimedia.org/T308133] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:05, 10 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24851886 --> == Wikipedia translation of the week: 2023-16 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Lucy Salani]]'''<br /> <small>''([[:en:Lucy Salani]]) ([[:fr:Lucy Salani]]) ''</small> </div> Please be bold and help translate this article! ---- [[File:Lucy Salani.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Lucy Salani''' was an Italian activist and is considered the only Italian transgender person to have survived the Nazi concentration camps. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:06, 17 April 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24872966 --> == Tech News: 2023-16 == <section begin="technews-2023-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/16|Translations]] are available. '''Recent changes''' * You can now see [[mw:Special:MyLanguage/Help:Extension:Kartographer#Show_nearby_articles|nearby articles on a Kartographer map]] with the button for the new feature "{{int:Kartographer-sidebar-nearbybutton}}". Six wikis have been testing this feature since October. [https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Geoinformation/Nearby_articles#Implementation][https://phabricator.wikimedia.org/T334079] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The [[m:Special:GlobalWatchlist|Special:GlobalWatchlist]] page now has links for "{{int:globalwatchlist-markpageseen}}" for each entry. This feature request was [[m:Community Wishlist Survey 2023/Notifications, Watchlists and Talk Pages/Button to mark a single change as read in the global watch list|voted #161 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334246] '''Problems''' * At Wikimedia Commons, some thumbnails have not been getting replaced correctly after a new version of the image is uploaded. This should be fixed later this week. [https://phabricator.wikimedia.org/T331138][https://phabricator.wikimedia.org/T333042] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] For the last few weeks, some external tools had inconsistent problems with logging-in with OAuth. This has now been fixed. [https://phabricator.wikimedia.org/T332650] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.5|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-18|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-19|en}}. It will be on all wikis from {{#time:j xg|2023-04-20|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:55, 18 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24881071 --> == Wikipedia translation of the week: 2023-17 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:ca:María Fernanda Castro Maya]]'''<br /> <small>''([[:pt:María Fernanda Castro Maya]]) ([[:eu:María Fernanda Castro Maya]]) ''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''María Fernanda Castro Maya''' is a Mexican self-advocate disability rights activist. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:55, 24 April 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24872966 --> == Tech News: 2023-17 == <section begin="technews-2023-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/17|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The date-selection menu on pages such as [[{{#special:Contributions}}]] will now show year-ranges that are in the current and past decade, instead of the current and future decade. This feature request was [[m:Community Wishlist Survey 2023/Miscellaneous/Change year range shown in date selection popup|voted #145 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334316] '''Problems''' * Due to security issues with the [[mw:Special:MyLanguage/Extension:Graph|Graph extension]], graphs have been disabled in all Wikimedia projects. Wikimedia Foundation teams are working to respond to these vulnerabilities. [https://phabricator.wikimedia.org/T334940] * For a few days, it was not possible to save some kinds of edits on the mobile version of a wiki. This has been fixed. [https://phabricator.wikimedia.org/T334797][https://phabricator.wikimedia.org/T334799][https://phabricator.wikimedia.org/T334794] '''Changes later this week''' * All wikis will be read-only for a few minutes on April 26. This is planned for [https://zonestamp.toolforge.org/1682517653 14:00 UTC]. [https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.6|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-04-25|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-04-26|en}}. It will be on all wikis from {{#time:j xg|2023-04-27|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * The Editing team plans an A/B test for [[mw:Special:MyLanguage/Talk pages project/Usability|a usability analysis of the Talk page project]]. The [[mw:Special:MyLanguage/Talk pages project/Usability/Analysis|planned measurements are available]]. Your wiki [[phab:T332946|may be invited to participate]]. Please suggest improvements to the measurement plan at [[mw:Talk:Talk pages project/Usability|the discussion page]]. * [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2023-2024|The Wikimedia Foundation annual plan 2023-2024 draft is open for comment and input]] until May 19. The final plan will be published in July 2023 on Meta-wiki. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:04, 24 April 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24933592 --> == Wikipedia translation of the week: 2023-18 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sonia Orbuch]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Sonia Shainwald Orbuch''' (born Sarah Shainwald, May 24, 1925 – September 30, 2018) was an American Holocaust educator. During the Second World War she was a Jewish resistance fighter in eastern Poland. Orbuch hid in the forests of Poland with her family during the Second World War. She joined a group of Soviet partisans, being renamed Sonia in case she was captured, and helped fight against the Germans. After the war, she returned home, where she met her future husband. After having a daughter in a refugee camp in Germany, the family eventually emigrated to the United States. She spent the rest of life in public engagement, speaking about her experiences and in 2009, published her autobiography, Here, There Are No Sarahs: A Woman's Courageous Fight Against the Nazis and Her Bittersweet Fulfillment of the American Dream. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 06:24, 1 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24872966 --> == Tech News: 2023-18 == <section begin="technews-2023-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/18|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The content attribution tools [[mw:Special:MyLanguage/Who Wrote That?|Who Wrote That?]], [[xtools:authorship|XTools Authorship]], and [[xtools:blame|XTools Blame]] now support the French and Italian Wikipedias. More languages will be added in the near future. This is part of the [[m:Community Wishlist Survey 2023/Reading/Extend "Who Wrote That?" tool to more wikis|#7 wish in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T243711][https://phabricator.wikimedia.org/T270490][https://phabricator.wikimedia.org/T334891] * The [[:commons:Special:MyLanguage/Commons:Video2commons|Video2commons]] tool has been updated. This fixed several bugs related to YouTube uploads. [https://github.com/toolforge/video2commons/pull/162/commits] * The [[{{#special:Preferences}}]] page has been redesigned on mobile web. The new design makes it easier to browse the different categories and settings at low screen widths. You can also now access the page via a link in the Settings menu in the mobile web sidebar. [https://www.mediawiki.org/wiki/Moderator_Tools/Content_moderation_on_mobile_web/Preferences] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.7|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-02|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-03|en}}. It will be on all wikis from {{#time:j xg|2023-05-04|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:45, 2 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24966974 --> == Wikipedia translation of the week: 2023-19 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Nadia Ghulam]]'''<br /><small>''([[:fr:Nadia Ghulam]]) ([[:es:Nadia Ghulam]]) ([[:ca:Nadia Ghulam]])''</small> </div> Please be bold and help translate this article! ---- [[File:Nadia Ghulam (cropped).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Nadia Ghulam Dastgir''' is an Afghan woman who spent ten years posing as her dead brother to evade the Taliban's strictures against women. Her book about her experiences, written with Agnès Rotger and published in 2010, El secret del meu turbant (The Secret of My Turban), won the Prudenci Bertrana Prize for fiction. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:37, 8 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=24966177 --> == Tech News: 2023-19 == <section begin="technews-2023-W19"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/19|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] Last week, Community Tech released the first update for providing [[m:Special:MyLanguage/Community Wishlist Survey 2022/Better diff handling of paragraph splits|better diffs]], the #1 request in the 2022 Community Wishlist Survey. [[phab:T324759|This update]] adds legends and tooltips to inline diffs so that users unfamiliar with the blue and yellow highlights can better understand the type of edits made. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] When you close an image that is displayed via MediaViewer, it will now return to the wiki page instead of going back in your browser history. This feature request was [[m:Community Wishlist Survey 2023/Reading/Return to the article when closing the MediaViewer|voted #65 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T236591] * The [[mw:Special:MyLanguage/Extension:SyntaxHighlight|SyntaxHighlight]] extension now supports <bdi lang="en" dir="ltr"><code>wikitext</code></bdi> as a selected language. Old alternatives that were used to highlight wikitext, such as <bdi lang="en" dir="ltr"><code>html5</code></bdi>, <bdi lang="en" dir="ltr"><code>moin</code></bdi>, and <bdi lang="en" dir="ltr"><code>html+handlebars</code></bdi>, can now be replaced. [https://phabricator.wikimedia.org/T29828] * [[mw:Special:MyLanguage/Manual:Creating pages with preloaded text|Preloading text to new pages/sections]] now supports preloading from localized MediaWiki interface messages. [https://cs.wikipedia.org/wiki/User_talk:Martin_Urbanec_(WMF)?action=edit&section=new&preload=MediaWiki:July Here is an example] at the {{int:project-localized-name-cswiki/en}} that uses <bdi lang="zxx" dir="ltr"><code><nowiki>preload=MediaWiki:July</nowiki></code></bdi>. [https://phabricator.wikimedia.org/T330337] '''Problems''' * Graph Extension update: Foundation developers have completed upgrading the visualization software to Vega5. Existing community graphs based on Vega2 are no longer compatible. Communities need to update local graphs and templates, and shared lua modules like <bdi lang="de" dir="ltr">[[:de:Modul:Graph]]</bdi>. The [https://vega.github.io/vega/docs/porting-guide/ Vega Porting guide] provides the most comprehensive detail on migration from Vega2 and [https://www.mediawiki.org/w/index.php?title=Template:Graph:PageViews&action=history here is an example migration]. Vega5 has currently just been enabled on mediawiki.org to provide a test environment for communities. [https://phabricator.wikimedia.org/T334940#8813922] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.8|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-09|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-10|en}}. It will be on all wikis from {{#time:j xg|2023-05-11|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Until now, all new OAuth apps went through manual review. Starting this week, apps using identification-only or basic authorizations will not require review. [https://phabricator.wikimedia.org/T67750] '''Future changes''' * During the next year, MediaWiki will stop using IP addresses to identify logged-out users, and will start automatically assigning unique temporary usernames. Read more at [[m:Special:MyLanguage/IP Editing: Privacy Enhancement and Abuse Mitigation/Updates|IP Editing: Privacy Enhancement and Abuse Mitigation/Updates]]. You can [[m:Talk:IP Editing: Privacy Enhancement and Abuse Mitigation#What should it look like?|join the discussion]] about the [[m:Special:MyLanguage/IP Editing: Privacy Enhancement and Abuse Mitigation/Updates#What will temporary usernames look like?|format of the temporary usernames]]. [https://phabricator.wikimedia.org/T332805] * There will be an [[:w:en:A/B testing|A/B test]] on 10 Wikipedias where the Vector 2022 skin is the default skin. Half of logged-in desktop users will see an interface where the different parts of the page are more clearly separated. You can [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements/Updates/2023-05 Zebra9 A/B test|read more]]. [https://phabricator.wikimedia.org/T333180][https://phabricator.wikimedia.org/T335972] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] <code>jquery.tipsy</code> will be removed from the MediaWiki core. This will affect some user scripts. Many lines with <code>.tipsy(</code> can be commented out. <code>OO.ui.PopupWidget</code> can be used to keep things working like they are now. You can [[phab:T336019|read more]] and [[:mw:Help:Locating broken scripts|read about how to find broken scripts]]. [https://phabricator.wikimedia.org/T336019] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/19|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W19"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:36, 9 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=24998636 --> == Wikipedia translation of the week: 2023-20 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Purple Day]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Epilepsy Warrior Brooch May 2018 Purple Day.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Purple Day''' is a global grassroots event that was formed with the intention to increase worldwide awareness of epilepsy, and to dispel common myths and fears of this neurological disorder. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:17, 15 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25000361 --> == Tech News: 2023-20 == <section begin="technews-2023-W20"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/20|Translations]] are available. '''Problems''' * Citations that are automatically generated based on [[d:Q33057|ISBN]] are currently broken. This affects citations made with the [[mw:Special:MyLanguage/Help:VisualEditor/User_guide/Citations-Full#Automatic|VisualEditor Automatic tab]], and the use of the citoid API in gadgets and user scripts. Work is ongoing to restore this feature. [https://phabricator.wikimedia.org/T336298] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.9|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-16|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-17|en}}. It will be on all wikis from {{#time:j xg|2023-05-18|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-gorwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hakwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hawwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hifwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hsbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-htwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-igwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ilowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-inhwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iuwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jamwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jvwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308134] '''Future changes''' * There is a recently formed team at the Wikimedia Foundation which will be focusing on experimenting with new tools. Currently they are building [[m:Wikimedia_Foundation_Annual_Plan/2023-2024/Draft/Future_Audiences#FA2.2_Conversational_AI|a prototype ChatGPT plugin that allows information generated by ChatGPT to be properly attributed]] to the Wikimedia projects. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Gadget and userscript developers should replace <bdi lang="zxx" dir="ltr"><code>jquery.cookie</code></bdi> with <bdi lang="zxx" dir="ltr"><code>mediawiki.cookie</code></bdi>. The <bdi lang="zxx" dir="ltr"><code>jquery.cookie</code></bdi> library will be removed in ~1 month, and staff developers will run a script to replace any remaining uses at that time. [https://phabricator.wikimedia.org/T336018] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/20|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W20"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:45, 15 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25011501 --> == Tech News: 2023-21 == <section begin="technews-2023-W21"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/21|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The "recent edits" time period for page watchers is now 30 days. It used to be 180 days. This was a [[m:Community Wishlist Survey 2023/Notifications, Watchlists and Talk Pages/Change information about the number of watchers on a page|Community Wishlist Survey proposal]]. [https://phabricator.wikimedia.org/T336250] '''Changes later this week''' * An [[mw:special:MyLanguage/Growth/Positive reinforcement#Impact|improved impact module]] will be available at Wikipedias. The impact module is a feature available to newcomers [[mw:Special:MyLanguage/Growth/Feature summary#Newcomer homepage|at their personal homepage]]. It will show their number of edits, how many readers their edited pages have, how many thanks they have received and similar things. It is also accessible by accessing Special:Impact. [https://phabricator.wikimedia.org/T336203] * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.10|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-23|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-24|en}}. It will be on all wikis from {{#time:j xg|2023-05-25|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/21|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W21"/> 16:55, 22 May 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25028325 --> == Wikipedia translation of the week: 2023-22 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Valencian Art Nouveau]]'''<br /> <small>''([[:es:Modernismo valenciano]])''</small> </div> Please be bold and help translate this article! ---- [[File:Santuario Novelda.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Valencian Art Nouveau''' (Spanish: modernismo valenciano, Valencian: modernisme valencià), is the historiographic denomination given to an art and literature movement associated with the Art Nouveau in the Valencian Community, in Spain. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:46, 29 May 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25074014 --> == Tech News: 2023-22 == <section begin="technews-2023-W22"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/22|Translations]] are available. '''Recent changes''' * Citations can once again be added automatically from ISBNs, thanks to Zotero's ISBN searches. The current data sources are the Library of Congress (United States), the Bibliothèque nationale de France (French National Library), and K10plus ISBN (German repository). Additional data source searches can be [[mw:Citoid/Creating Zotero translators|proposed to Zotero]]. The ISBN labels in the [[mw:Special:MyLanguage/Help:VisualEditor/User_guide/Citations-Full#Automatic|VisualEditor Automatic tab]] will reappear later this week. [https://phabricator.wikimedia.org/T336298#8859917] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The page [[{{#special:EditWatchlist}}]] now has "{{int:watchlistedit-normal-check-all}}" options to select all the pages within a namespace. This feature request was [[m:Community Wishlist Survey 2023/Notifications, Watchlists and Talk Pages/Watchlist edit - "check all" checkbox|voted #161 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334252] '''Problems''' * For a few days earlier this month, the "Add interlanguage link" item in the Tools menu did not work properly. This has now been fixed. [https://phabricator.wikimedia.org/T337081] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.11|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-05-30|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-05-31|en}}. It will be on all wikis from {{#time:j xg|2023-06-01|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * VisualEditor will be switched to a new backend on [https://phabricator.wikimedia.org/source/mediawiki-config/browse/master/dblists/small.dblist small] and [https://phabricator.wikimedia.org/source/mediawiki-config/browse/master/dblists/medium.dblist medium] wikis this week. Large wikis will follow in the coming weeks. This is part of the effort to move Parsoid into MediaWiki core. The change should have no noticeable effect on users, but if you experience any slow loading or other strangeness when using VisualEditor, please report it on the phabricator ticket linked here. [https://phabricator.wikimedia.org/T320529] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/22|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W22"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:04, 29 May 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25079963 --> == Wikipedia translation of the week: 2023-23 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:pt:Alessandra Korap]]'''<br /> <small>''([[:en:Alessandra Korap]]) ''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Alessandra Korap''' is an indigenous leader and Brazilian environmental activist from the Munduruku ethnic group. Her main work is defending the demarcation of indigenous territory and denouncing the illegal exploitation and activities of the mining and logging industries. Alessandra is internationally recognized for her work. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:33, 5 June 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25111481 --> == Tech News: 2023-23 == <section begin="technews-2023-W23"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/23|Translations]] are available. '''Recent changes''' * The [[:mw:Special:MyLanguage/Help:Extension:RealMe|RealMe]] extension allows you to mark URLs on your user page as verified for Mastodon and similar software. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] Citation and footnote editing can now be started from the reference list when using the visual editor. This feature request was [[m:Community Wishlist Survey 2023/Citations/Allow citations to be edited in the references section with VisualEditor|voted #2 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T54750] * Previously, clicking on someone else's link to Recent Changes with filters applied within the URL could unintentionally change your preference for "{{int:Rcfilters-group-results-by-page}}". This has now been fixed. [https://phabricator.wikimedia.org/T202916#8874081] '''Problems''' * For a few days last week, some tools and bots returned outdated information due to database replication problems, and may have been down entirely while it was being fixed. These issues have now been fixed. [https://phabricator.wikimedia.org/T337446] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.12|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-06-06|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-06-07|en}}. It will be on all wikis from {{#time:j xg|2023-06-08|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Bots will no longer be prevented from making edits because of URLs that match the [[mw:Special:MyLanguage/Extension:SpamBlacklist|spam blacklist]]. [https://phabricator.wikimedia.org/T313107] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/23|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W23"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:52, 5 June 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25114640 --> == Wikipedia translation of the week: 2023-24 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cassinga Day]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Cassinga Day''' is a national public holiday in Namibia remembering the Cassinga Massacre. Commemorated annually on 4 May, the date "remembers those (approximately 600) killed in 1978 when the South African Defence Force attacked a SWAPO base at Cassinga in southern Angola". <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:07, 12 June 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25111481 --> == Tech News: 2023-24 == <section begin="technews-2023-W24"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/24|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] The content attribution tools [[mw:Special:MyLanguage/Who Wrote That?|Who Wrote That?]], [[xtools:authorship|XTools Authorship]], and [[xtools:blame|XTools Blame]] now support the Dutch, German, Hungarian, Indonesian, Japanese, Polish and Portuguese Wikipedias. This was the [[m:Community Wishlist Survey 2023/Reading/Extend "Who Wrote That?" tool to more wikis|#7 wish in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334891] * The [[mw:Special:MyLanguage/Structured Data Across Wikimedia/Search Improvements#Search Preview panel|Search Preview panel]] has been deployed on four Wikipedias (Catalan, Dutch, Hungarian and Norwegian). The panel will show an image related to the article (if existing), the top sections of the article, related images (coming from MediaSearch on Commons), and eventually the sister projects associated with the article. [https://phabricator.wikimedia.org/T306341] * The [[:mw:Special:MyLanguage/Help:Extension:RealMe#Verifying_a_link_on_non-user_pages|RealMe]] extension now allows administrators to verify URLs for any page, for Mastodon and similar software. [https://phabricator.wikimedia.org/T324937] * The default project license [https://lists.wikimedia.org/hyperkitty/list/wikimediaannounce-l@lists.wikimedia.org/thread/7G6XPWZPQFLZ2JANN3ZX6RT4DVUI3HZQ/ has been officially upgraded] to CC BY-SA 4.0. The software interface messages have been updated. Communities should feel free to start updating any mentions of the old CC BY-SA 3.0 licensing within policies and related documentation pages. [https://phabricator.wikimedia.org/T319064] '''Problems''' * For three days last month, some Wikipedia pages edited with VisualEditor or DiscussionTools had an unintended <code><nowiki>__TOC__</nowiki></code> (or its localized form) added during an edit. There is [[mw:Parsoid/Deployments/T336101_followup|a listing of affected pages sorted by wiki]], that may still need to be fixed. [https://phabricator.wikimedia.org/T336101] * Currently, the "{{int:Visualeditor-dialog-meta-categories-defaultsort-label}}" feature in VisualEditor is broken. Existing <code><nowiki>{{DEFAULTSORT:...}}</nowiki></code> keywords incorrectly appear as missing templates in VisualEditor. Developers are exploring how to fix this. In the meantime, those wishing to edit the default sortkey of a page are advised to switch to source editing. [https://phabricator.wikimedia.org/T337398] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Last week, an update to the delete form may have broken some gadgets or user scripts. If you need to manipulate (empty) the reason field, replace <bdi lang="zxx" dir="ltr"><code>#wpReason</code></bdi> with <bdi lang="zxx" dir="ltr" style="white-space: nowrap;"><code>#wpReason > input</code></bdi>. See [https://cs.wikipedia.org/w/index.php?title=MediaWiki%3AGadget-CleanDeleteReasons.js&diff=22859956&oldid=12794189 an example fix]. [https://phabricator.wikimedia.org/T337809] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.13|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-06-13|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-06-14|en}}. It will be on all wikis from {{#time:j xg|2023-06-15|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * VisualEditor will be switched to a new backend on English Wikipedia on Monday, and all other [https://phabricator.wikimedia.org/source/mediawiki-config/browse/master/dblists/large.dblist large] wikis on Thursday. The change should have no noticeable effect on users, but if you experience any slow loading or other strangeness when using VisualEditor, please report it on the phabricator ticket linked here. [https://phabricator.wikimedia.org/T320529] '''Future changes''' * From 5 June to 17 July, the Foundation's [[:mw:Wikimedia Security Team|Security team]] is holding a consultation with contributors regarding a draft policy to govern the use of third-party resources in volunteer-developed gadgets and scripts. Feedback and suggestions are warmly welcome at [[m:Special:MyLanguage/Third-party resources policy|Third-party resources policy]] on meta-wiki. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/24|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W24"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 14:52, 12 June 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25133779 --> == Tech News: 2023-25 == <section begin="technews-2023-W25"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/25|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Flame graphs are now available in WikimediaDebug. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/JXNQD3EHG5V5QW5UXFDPSHQG4MJ3FWJQ/][https://techblog.wikimedia.org/2023/06/08/flame-graphs-arrive-in-wikimediadebug/] '''Changes later this week''' * There is no new MediaWiki version this week. * There is now a toolbar search popup in the visual editor. You can trigger it by typing <code>\</code> or pressing <code>ctrl + shift + p</code>. It can help you quickly access most tools in the editor. [https://commons.wikimedia.org/wiki/File:Visual_editor_toolbar_search_feature.png][https://phabricator.wikimedia.org/T66905] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/25|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W25"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:09, 19 June 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25159510 --> == Wikipedia translation of the week: 2023-26 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Rawon]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Rawon Setan.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Rawon''' (Javanese: ꦫꦮꦺꦴꦤ꧀) is an Indonesian beef soup. Originating from East Java, rawon utilizes the black keluak nut as the main seasoning, which gives a dark color and nutty flavor to the soup. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:18, 26 June 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25177056 --> == Tech News: 2023-26 == <section begin="technews-2023-W26"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/26|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Action API modules and Special:LinkSearch will now add a trailing <bdi lang="zxx" dir="ltr"><code>/</code></bdi> to all <bdi lang="zxx" dir="ltr"><code>prop=extlinks</code></bdi> responses for bare domains. This is part of the work to remove duplication in the <code>externallinks</code> database table. [https://phabricator.wikimedia.org/T337994] '''Problems''' * Last week, search was broken on Commons and Wikidata for 23 hours. [https://phabricator.wikimedia.org/T339810][https://wikitech.wikimedia.org/wiki/Incidents/2023-06-18_search_broken_on_wikidata_and_commons] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.15|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-06-27|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-06-28|en}}. It will be on all wikis from {{#time:j xg|2023-06-29|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Minerva skin now applies more predefined styles to the <bdi lang="zxx" dir="ltr"><code>.mbox-text</code></bdi> CSS class. This enables support for mbox templates that use divs instead of tables. Please make sure that the new styles won't affect other templates in your wiki. [https://gerrit.wikimedia.org/r/c/mediawiki/skins/MinervaNeue/+/930901/][https://phabricator.wikimedia.org/T339040] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Gadgets will now load on both desktop and mobile by default. Previously, gadgets loaded only on desktop by default. Changing this default using the <bdi lang="zxx" dir="ltr"><code>|targets=</code></bdi> parameter is also deprecated and should not be used. You should make gadgets work on mobile or disable them based on the skin (with the <bdi lang="zxx" dir="ltr"><code>|skins=</code></bdi> parameter in <bdi lang="en" dir="ltr">MediaWiki:Gadgets-definition</bdi>) rather than whether the user uses the mobile or the desktop website. Popular gadgets that create errors on mobile will be disabled by developers on the Minerva skin as a temporary solution. [https://phabricator.wikimedia.org/T127268] * All namespace tabs now have the same browser [[m:Special:MyLanguage/Help:Keyboard_shortcuts|access key]] by default. Previously, custom and extension-defined namespaces would have to have their access keys set manually on-wiki, but that is no longer necessary. [https://phabricator.wikimedia.org/T22126] * The review form of the Flagged Revisions extension now uses the standardized [[mw:Special:MyLanguage/Codex|user interface components]]. [https://phabricator.wikimedia.org/T191156] '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] How media is structured in the parser's HTML output will change in the coming weeks at [[:wikitech:Deployments/Train#Thursday|group2 wikis]]. This change improves the accessibility of content. You may need to update your site-CSS, or userscripts and gadgets. There are [[mw:Special:MyLanguage/Parsoid/Parser_Unification/Media_structure/FAQ|details on what code to check, how to update the code, and where to report any related problems]]. [https://phabricator.wikimedia.org/T314318] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/26|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W26"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:19, 26 June 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25202311 --> == Wikipedia translation of the week: 2023-27 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Hook echo]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Tornadic classic supercell radar.gif|center|300px]] <div style="text-align:left; padding: .4em;"> A '''hook echo''' is a pendant or hook-shaped weather radar signature as part of some supercell thunderstorms. It is found in the lower portions of a storm as air and precipitation flow into a mesocyclone, resulting in a curved feature of reflectivity. The echo is produced by rain, hail, or even debris being wrapped around the supercell <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:18, 3 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25241057 --> == Tech News: 2023-27 == <section begin="technews-2023-W27"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/27|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the rolling out of the [[m:Community Wishlist Survey 2022/Multimedia and Commons/Audio links that play on click|audio links that play on click]] wishlist proposal, [https://noc.wikimedia.org/conf/highlight.php?file=dblists/small.dblist small wikis] will now be able to use the [[mw:Special:MyLanguage/Help:Extension:Phonos#Inline audio player mode|inline audio player]] that is implemented by the [[mw:Extension:Phonos|Phonos]] extension. [https://phabricator.wikimedia.org/T336763] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] From this week all gadgets automatically load on mobile and desktop sites. If you see any problems with gadgets on your wikis, please adjust the [[mw:Special:MyLanguage/Extension:Gadgets#Options|gadget options]] in your gadget definitions file. [https://phabricator.wikimedia.org/T328610] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.16|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-04|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-05|en}}. It will be on all wikis from {{#time:j xg|2023-07-06|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/27|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W27"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:51, 3 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25231546 --> == Tech News: 2023-28 == <section begin="technews-2023-W28"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/28|Translations]] are available. '''Recent changes''' * The [[:mw:Special:MyLanguage/Structured Data Across Wikimedia/Section-level Image Suggestions|Section-level Image Suggestions feature]] has been deployed on seven Wikipedias (Portuguese, Russian, Indonesian, Catalan, Hungarian, Finnish and Norwegian Bokmål). The feature recommends images for articles on contributors' watchlists that are a good match for individual sections of those articles. * [[:m:Special:MyLanguage/Global AbuseFilter|Global abuse filters]] have been enabled on all Wikimedia projects, except English and Japanese Wikipedias (who opted out). This change was made following a [[:m:Requests for comment/Make global abuse filters opt-out|global request for comments]]. [https://phabricator.wikimedia.org/T341159] * [[{{#special:BlockedExternalDomains}}]] is a new tool for administrators to help fight spam. It provides a clearer interface for blocking plain domains (and their subdomains), is more easily searchable, and is faster for the software to process for each edit on the wiki. It does not support regex (for complex cases), nor URL path-matching, nor the [[MediaWiki:Spam-whitelist|MediaWiki:Spam-whitelist]], but otherwise it replaces most of the functionalities of the existing [[MediaWiki:Spam-blacklist|MediaWiki:Spam-blacklist]]. There is a Python script to help migrate all simple domains into this tool, and more feature details, within [[mw:Special:MyLanguage/Manual:BlockedExternalDomains|the tool's documentation]]. It is available at all wikis except for Meta-wiki, Commons, and Wikidata. [https://phabricator.wikimedia.org/T337431] * The WikiEditor extension was updated. It includes some of the most frequently used features of wikitext editing. In the past, many of its messages could only be translated by administrators, but now all regular translators on translatewiki can translate them. Please check [https://translatewiki.net/wiki/Special:MessageGroupStats?group=ext-wikieditor&messages=&x=D#sortable:0=asc the state of WikiEditor localization into your language], and if the "Completion" for your language shows anything less than 100%, please complete the translation. See [https://lists.wikimedia.org/hyperkitty/list/wikitech-ambassadors@lists.wikimedia.org/thread/D4YELU2DXMZ75PGELUOKXXMFF3FH45XA/ a more detailed explanation]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.17|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-11|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-12|en}}. It will be on all wikis from {{#time:j xg|2023-07-13|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * The default protocol of [[{{#special:LinkSearch}}]] and API counterparts has changed from http to both http and https. [https://phabricator.wikimedia.org/T14810] * [[{{#special:LinkSearch}}]] and its API counterparts will now search for all of the URL provided in the query. It used to be only the first 60 characters. This feature was requested fifteen years ago. [https://phabricator.wikimedia.org/T17218] '''Future changes''' * There is an experiment with a [[:w:en:ChatGPT|ChatGPT]] plugin. This is to show users where the information is coming from when they read information from Wikipedia. It has been tested by Wikimedia Foundation staff and other Wikimedians. Soon all ChatGPT plugin users can use the Wikipedia plugin. This is the same plugin which was mentioned in [[m:Special:MyLanguage/Tech/News/2023/20|Tech News 2023/20]]. [https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2023-2024/Draft/Future_Audiences#FA2.2_Conversational_AI] * There is an ongoing discussion on a [[m:Special:MyLanguage/Third-party resources policy|proposed Third-party resources policy]]. The proposal will impact the use of third-party resources in gadgets and userscripts. Based on the ideas received so far, policy includes some of the risks related to user scripts and gadgets loading third-party resources, some best practices and exemption requirements such as code transparency and inspectability. Your feedback and suggestions are warmly welcome until July 17, 2023 on [[m:Talk:Third-party resources policy|on the policy talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/28|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W28"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:54, 10 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25278797 --> == Wikipedia translation of the week: 2023-29 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Esther Cooper Jackson]]'''<br /> <small>''([[:fr:Esther Cooper Jackson]]) ([[:simple:Esther Cooper Jackson]])''</small> </div> Please be bold and help translate this article! ---- [[File:Esther Cooper Jackson, 1968, Great Barrington.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Esther Victoria Cooper Jackson''' was an American civil rights activist and social worker. She was one of the founding editors of the magazine Freedomways. She also was an organizational and executive secretary at the Southern Negro Youth Congress. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:14, 17 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25266525 --> == Tech News: 2023-29 == <section begin="technews-2023-W29"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/29|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] We are now serving 1% of all global user traffic from [[w:en:Kubernetes|Kubernetes]] (you can [[wikitech:MediaWiki On Kubernetes|read more technical details]]). We are planning to increment this percentage regularly. You can [[phab:T290536|follow the progress of this work]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.18|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-18|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-19|en}}. It will be on all wikis from {{#time:j xg|2023-07-20|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] MediaWiki [[mw:Special:MyLanguage/Help:System_message|system messages]] will now look for available local fallbacks, instead of always using the default fallback defined by software. This means wikis no longer need to override each language on the [[mw:Special:MyLanguage/Manual:Language#Fallback_languages|fallback chain]] separately. For example, English Wikipedia doesn't have to create <bdi lang="zxx" dir="ltr"><code>en-ca</code></bdi> and <bdi lang="zxx" dir="ltr"><code>en-gb</code></bdi> subpages with a transclusion of the base pages anymore. This makes it easier to maintain local overrides. [https://phabricator.wikimedia.org/T229992] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The <bdi lang="zxx" dir="ltr"><code>action=growthsetmentorstatus</code></bdi> API will be deprecated with the new MediaWiki version. Bots or scripts calling that API should use the <bdi lang="zxx" dir="ltr"><code>action=growthmanagementorlist</code></bdi> API now. [https://phabricator.wikimedia.org/T321503] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/29|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W29"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:08, 17 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25289122 --> == Wikipedia translation of the week: 2023-30 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cut of pork]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:American Pork Cuts.svg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''cuts of pork''' are the different parts of the pig which are consumed as food by humans. The terminology and extent of each cut varies from country to country. There are between four and six primal cuts, which are the large parts in which the pig is first cut: the shoulder (blade and picnic), loin, belly (spare ribs and side) and leg <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:21, 24 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25318972 --> == Tech News: 2023-30 == <section begin="technews-2023-W30"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/30|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] On July 18, the Wikimedia Foundation launched a survey about the [[:mw:Technical_decision_making|technical decision making process]] for people who do technical work that relies on software that is maintained by the Foundation or affiliates. If this applies to you, [https://wikimediafoundation.limesurvey.net/885471 please take part in the survey]. The survey will be open for three weeks, until August 7. You can find more information in [[listarchive:list/wikitech-l@lists.wikimedia.org/thread/Q7DUCFA75DXG3G2KHTO7CEWMLCYTSDB2/|the announcement e-mail on wikitech-l]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.19|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-07-25|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-07-26|en}}. It will be on all wikis from {{#time:j xg|2023-07-27|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/30|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W30"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:20, 25 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25332248 --> == Wikipedia translation of the week: 2023-31 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Gunhild Cross]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Gunhildkorset.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Gunhild Cross''' (Danish: Gunhildkorset), named for its first owner, Gunhild, a daughter of Svend III of Denmark, is a mid-12th-century crucifix carved in walrus tusk and with both Latin and Runic inscriptions. It is now in the collection of the National Museum of Denmark. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:48, 31 July 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25380210 --> == Tech News: 2023-31 == <section begin="technews-2023-W31"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/31|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[mw:Synchronizer|Synchronizer]] tool is now available to keep Lua modules synced across Wikimedia wikis, along with [[mw:Multilingual Templates and Modules|updated documentation]] to develop global Lua modules and templates. * The tag filter on [[{{#special:NewPages}}]] and revision history pages can now be inverted. For example, you can hide edits that were made using an automated tool. [https://phabricator.wikimedia.org/T334337][https://phabricator.wikimedia.org/T334338] * The Wikipedia [[:w:en:ChatGPT|ChatGPT]] plugin experiment can now be used by ChatGPT users who can use plugins. You can participate in a [[:m:Talk:Wikimedia Foundation Annual Plan/2023-2024/Draft/Future Audiences#Announcing monthly Future Audiences open "office hours"|video call]] if you want to talk about this experiment or similar work. [https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2023-2024/Draft/Future_Audiences#FA2.2_Conversational_AI] '''Problems''' * It was not possible to generate a PDF for pages with non-Latin characters in the title, for the last two weeks. This has now been fixed. [https://phabricator.wikimedia.org/T342442] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.20|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-01|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-02|en}}. It will be on all wikis from {{#time:j xg|2023-08-03|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Tuesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-kawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kaawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kabwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kbdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kbpwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-knwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kshwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kuwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kwwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308135] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/31|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W31"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:54, 31 July 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25362228 --> == Wikipedia translation of the week: 2023-32 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Polyura athamas]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Close wing mud-puddling position of Charaxes bharata (C.& R. Felder,1867) - Indian Nawab.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''''Polyura athamas''''', the common nawab, is a species of fast-flying canopy butterfly found in tropical Asia. It belongs to the Charaxinae (rajahs and nawabs) in the brush-footed butterfly family (Nymphalidae). <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 03:14, 7 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25410866 --> == Tech News: 2023-32 == <section begin="technews-2023-W32"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/32|Translations]] are available. '''Recent changes''' * Mobile Web editors can now [[mw:Special:MyLanguage/Reading/Web/Advanced_mobile_contributions#August_1,_2023_-_Full-page_editing_added_on_mobile|edit a whole page at once]]. To use this feature, turn on "{{int:Mobile-frontend-mobile-option-amc}}" in your settings and use the "{{int:Minerva-page-actions-editfull}}" button in the "{{int:Minerva-page-actions-overflow}}" menu. [https://phabricator.wikimedia.org/T203151] '''Changes later this week''' * There is no new MediaWiki version this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/32|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W32"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:21, 7 August 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25420038 --> == Wikipedia translation of the week: 2023-33 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Women's page]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:"Doings in Pittsburg Society" The Pittsburg Press February 1, 1920.png|center|300px]] <div style="text-align:left; padding: .4em;"> The '''women's page''' (sometimes called home page or women's section) of a newspaper was a section devoted to covering news assumed to be of interest to women. Women's pages started out in the 19th century as society pages and eventually morphed into features sections in the 1970s. Although denigrated during much of that period, they had a significant impact on journalism and in their communities. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:51, 14 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-33 == <section begin="technews-2023-W33"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/33|Translations]] are available. '''Recent changes''' * The Content translation system is no longer using Youdao's [[mw:Special:MyLanguage/Help:Content_translation/Translating/Initial_machine_translation|machine translation service]]. The service was in place for several years, but due to no usage, and availability of alternatives, it was deprecated to reduce maintenance overheads. Other services which cover the same languages are still available. [https://phabricator.wikimedia.org/T329137] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.22|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-15|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-16|en}}. It will be on all wikis from {{#time:j xg|2023-08-17|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-lawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ladwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lbewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lezwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lfnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-liwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lijwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lmowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ltgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-maiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-map_bmswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mdfwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kywiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308136] <!-- TODO replace wiki codes --> '''Future changes''' * A few gadgets/user scripts which add icons to the Minerva skin need to have their CSS updated. There are more details available including a [[phab:T344067|search for all existing instances and how to update them]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/33|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W33"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 06:00, 15 August 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25428668 --> == Wikipedia translation of the week: 2023-34 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Insect toxin]]'''<br /> <small>''([[:de:Insektengift]])''</small> </div> Please be bold and help translate this article! ---- [[File:PDB 1lmr EBI.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Insect toxins''' are various protein toxins produced by insect species. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:32, 21 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-34 == <section begin="technews-2023-W34"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/34|Translations]] are available. '''Recent changes''' * The [https://gdrive-to-commons.toolforge.org/ GDrive to Commons Uploader] tool is now available. It enables [[m:Special:MyLanguage/GDrive to Commons Uploader|securely selecting and uploading files]] from your Google Drive directly to Wikimedia Commons. [https://phabricator.wikimedia.org/T267868] * From now on, we will announce new Wikimedia wikis in Tech News, so you can update any tools or pages. ** Since the last edition, two new wikis have been created: *** a Wiktionary in [[d:Q7121294|Pa'O]] ([[wikt:blk:|<code>wikt:blk:</code>]]) [https://phabricator.wikimedia.org/T343540] *** a Wikisource in [[d:Q34002|Sundanese]] ([[s:su:|<code>s:su:</code>]]) [https://phabricator.wikimedia.org/T343539] ** To catch up, the next most recent six wikis are: *** Wikifunctions ([[f:|<code>f:</code>]]) [https://phabricator.wikimedia.org/T275945] *** a Wiktionary in [[d:Q2891049|Mandailing]] ([[wikt:btm:|<code>wikt:btm:</code>]]) [https://phabricator.wikimedia.org/T335216] *** a Wikipedia in [[d:Q5555465|Ghanaian Pidgin]] ([[w:gpe:|<code>w:gpe:</code>]]) [https://phabricator.wikimedia.org/T335969] *** a Wikinews in [[d:Q3111668|Gungbe]] ([[n:guw:|<code>n:guw:</code>]]) [https://phabricator.wikimedia.org/T334394] *** a Wiktionary in [[d:Q33522|Kabardian]] ([[wikt:kbd:|<code>wikt:kbd:</code>]]) [https://phabricator.wikimedia.org/T333266] *** a Wikipedia in [[d:Q35570|Fante]] ([[w:fat:|<code>w:fat:</code>]]) [https://phabricator.wikimedia.org/T335016] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-22|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-23|en}}. It will be on all wikis from {{#time:j xg|2023-08-24|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] There is an existing [[mw:Stable interface policy|stable interface policy]] for MediaWiki backend code. There is a [[mw:User:Jdlrobson/Stable interface policy/frontend|proposed stable interface policy for frontend code]]. This is relevant for anyone who works on gadgets or Wikimedia frontend code. You can read it, discuss it, and let the proposer know if there are any problems. [https://phabricator.wikimedia.org/T344079] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/34|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W34"/> 15:25, 21 August 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25497111 --> == Wikipedia translation of the week: 2023-35 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Manchester Blitz]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Air Raid Damage in Britain- Manchester HU49833.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Manchester Blitz''' (also known as the Christmas Blitz) was the heavy bombing of the city of Manchester and its surrounding areas in North West England during the Second World War by the German Luftwaffe. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:16, 28 August 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-35 == <section begin="technews-2023-W35"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/35|Translations]] are available. '''Recent changes''' * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the changes for the [[m:Community Wishlist Survey 2022/Better diff handling of paragraph splits|better diff handling of paragraph splits]], improved detection of splits is being rolled out. Over the last two weeks, we deployed this support to [[wikitech:Deployments/Train#Groups|group0]] and group1 wikis. This week it will be deployed to group2 wikis. [https://phabricator.wikimedia.org/T341754] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] All [[{{#special:Contributions}}]] pages now show the user's local edit count and the account's creation date. [https://phabricator.wikimedia.org/T324166] * Wikisource users can now use the <bdi lang="zxx" dir="ltr"><code>prpbengalicurrency</code></bdi> label to denote Bengali currency characters as page numbers inside the <bdi lang="zxx" dir="ltr"><code><nowiki><pagelist></nowiki></code></bdi> tag. [https://phabricator.wikimedia.org/T268932] * Two preferences have been relocated. The preference "{{int:visualeditor-preference-visualeditor}}" is now shown on the [[Special:Preferences#mw-prefsection-editing|"{{int:prefs-editing}}" tab]] at all wikis. Previously it was shown on the "{{int:prefs-betafeatures}}" tab at some wikis. The preference "{{int:visualeditor-preference-newwikitexteditor-enable}}" is now also shown on the "{{int:prefs-editing}}" tab at all wikis, instead of the "{{int:prefs-betafeatures}}" tab. [https://phabricator.wikimedia.org/T335056][https://phabricator.wikimedia.org/T344158] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.24|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-08-29|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-08-30|en}}. It will be on all wikis from {{#time:j xg|2023-08-31|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] New signups for a Wikimedia developer account will start being pushed towards <bdi lang="en" dir="ltr">[https://idm.wikimedia.org/ idm.wikimedia.org]</bdi>, rather than going via Wikitech. [[wikitech:IDM|Further information about the new system is available]]. * All right-to-left language wikis, plus Korean, Armenian, Ukrainian, Russian, and Bulgarian Wikipedias, will have a link in the sidebar that provides a short URL of that page, using the [[m:Special:MyLanguage/Wikimedia URL Shortener|Wikimedia URL Shortener]]. This feature will come to more wikis in future weeks. [https://phabricator.wikimedia.org/T267921] '''Future changes''' * The removal of the [[mw:Special:MyLanguage/Extension:DoubleWiki|DoubleWiki extension]] is being discussed. This extension currently allows Wikisource users to view articles from multiple language versions side by side when the <bdi lang="zxx" dir="ltr"><code><=></code></bdi> symbol next to a specific language edition is selected. Comments on this are welcomed at [[phab:T344544|the phabricator task]]. * A proposal has been made to merge the second hidden-categories list (which appears below the wikitext editing form) with the main list of categories (which is further down the page). [[phab:T340606|More information is available on Phabricator]]; feedback is welcome! '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/35|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W35"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 14:00, 28 August 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25510866 --> == Wikipedia translation of the week: 2023-36 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ghana Independence Act 1957]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> The '''Ghana Independence Act 1957''' is an Act of the Parliament of the United Kingdom that granted the Gold Coast fully responsible government within the British Commonwealth of Nations under the name of Ghana <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:18, 4 September 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-36 == <section begin="technews-2023-W36"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/36|Translations]] are available. '''Recent changes''' * [[m:Wikisource_EditInSequence|EditInSequence]], a feature that allows users to edit pages faster on Wikisource has been moved to a Beta Feature based on community feedback. To enable it, you can navigate to the [[Special:Preferences#mw-prefsection-betafeatures|beta features tab in Preferences]]. [https://phabricator.wikimedia.org/T308098] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the changes for the [[m:Special:MyLanguage/Community Wishlist Survey 2022/Generate Audio for IPA|Generate Audio for IPA]] and [[m:Community Wishlist Survey 2022/Multimedia and Commons/Audio links that play on click|Audio links that play on click]] wishlist proposals, the [[mw:Special:MyLanguage/Help:Extension:Phonos#Inline_audio_player_mode|inline audio player mode]] of [[mw:Extension:Phonos|Phonos]] has been deployed to all projects. [https://phabricator.wikimedia.org/T336763] * There is a new option for Administrators when they are changing the usergroups for a user, to add the user’s user page to their watchlist. This works both via [[{{#special:UserRights}}]] and via the API. [https://phabricator.wikimedia.org/T272294] * One new wiki has been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q34318|Talysh]] ([[w:tly:|<code>w:tly:</code>]]) [https://phabricator.wikimedia.org/T345166] '''Problems''' * The [[mw:Special:MyLanguage/Extension:LoginNotify|LoginNotify extension]] was not sending notifications since January. It has now been fixed, so going forward, you may see notifications for failed login attempts, and successful login attempts from a new device. [https://phabricator.wikimedia.org/T344785] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.25|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-05|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-06|en}}. It will be on all wikis from {{#time:j xg|2023-09-07|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-mhrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-miwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-minwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mrjwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mtwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mwlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-myvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mznwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nahwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-napwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ndswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nds_nlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-newiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-newwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-novwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nqowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nrmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nsowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ocwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-olowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-omwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-orwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-oswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pagwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pamwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-papwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pcdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pdcwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pflwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pihwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pmswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pnbwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pntwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pswiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308137][https://phabricator.wikimedia.org/T308138] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/36|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W36"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:34, 4 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25566983 --> == Wikipedia translation of the week: 2023-37 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Betrayal trauma]]'''<br /> <small>''([[:sv:Svektrauma]]) ([[:ar:صدمة الخيانة]]) ([[:ko:배신 트라우마]])''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Betrayal trauma''' is defined as a trauma perpetrated by someone with whom the victim is close to and reliant upon for support and survival. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:49, 11 September 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25427472 --> == Tech News: 2023-37 == <section begin="technews-2023-W37"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/37|Translations]] are available. '''Recent changes''' * [[mw:Special:MyLanguage/ORES|ORES]], the revision evaluation service, is now using a new open-source infrastructure on all wikis except for English Wikipedia and Wikidata. These two will follow this week. If you notice any unusual results from the Recent Changes filters that are related to ORES (for example, "{{int:ores-rcfilters-damaging-title}}" and "{{int:ores-rcfilters-goodfaith-title}}"), please [[mw:Talk:Machine Learning|report them]]. [https://phabricator.wikimedia.org/T342115] * When you are logged in on one Wikimedia wiki and visit a different Wikimedia wiki, the system tries to log you in there automatically. This has been unreliable for a long time. You can now visit the login page to make the system try extra hard. If you feel that made logging in better or worse than it used to be, your feedback is appreciated. [https://phabricator.wikimedia.org/T326281] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.26|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-12|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-13|en}}. It will be on all wikis from {{#time:j xg|2023-09-14|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[mw:Special:MyLanguage/Technical decision making|Technical Decision-Making Forum Retrospective]] team invites anyone involved in the technical field of Wikimedia projects to signup to and join [[mw:Technical decision making/Listening Sessions|one of their listening sessions]] on 13 September. Another date will be scheduled later. The goal is to improve the technical decision-making processes. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] As part of the changes for the [[m:Special:MyLanguage/Community Wishlist Survey 2022/Better diff handling of paragraph splits|Better diff handling of paragraph splits]] wishlist proposal, the inline switch widget in diff pages is being rolled out this week to all wikis. The inline switch will allow viewers to toggle between a unified inline or two-column diff wikitext format. [https://phabricator.wikimedia.org/T336716] '''Future changes''' * All wikis will be read-only for a few minutes on 20 September. [[m:Special:MyLanguage/Tech/Server switch|This is planned at 14:00 UTC.]] More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T345263] * The Enterprise API is launching a new feature called "[http://breakingnews-beta.enterprise.wikimedia.com/ breaking news]". Currently in BETA, this attempts to identify likely "newsworthy" topics as they are currently being written about in any Wikipedia. Your help is requested to improve the accuracy of its detection model, especially on smaller language editions, by recommending templates or identifiable editing patterns. See more information at [[mw:Special:MyLanguage/Wikimedia Enterprise/Breaking news|the documentation page]] on MediaWiki or [[m:Special:MyLanguage/Wikimedia Enterprise/FAQ#What is Breaking News|the FAQ]] on Meta. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/37|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W37"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:08, 11 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25589064 --> == Wikipedia translation of the week: 2023-38 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:es:Genocidio del Putumayo]]'''<br /> <small>''([[:en:Putumayo genocide]]) ([[:ca:Genocidi del Putumayo]])''</small></div> Please be bold and help translate this article! ---- [[File:The Putumayo - the devil's paradise, travels in the Peruvian Amazon Region and an account of the atrocities committed upon the Indians therein (1913) (14782203995).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Putumayo genocide''' is the term which is used in reference to the enslavement, massacres and ethnocide of the indigenous population of the Amazon at the hands of the Peruvian Amazon Company, specifically in the area between the Putumayo River and the Caquetá River during the Amazon rubber boom period from 1879 to 1912. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 03:38, 18 September 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25599361 --> == Tech News: 2023-38 == <section begin="technews-2023-W38"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/38|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] MediaWiki now has a [[mw:Stable interface policy/frontend|stable interface policy for frontend code]] that more clearly defines how we deprecate MediaWiki code and wiki-based code (e.g. gadgets and user scripts). Thank you to everyone who contributed to the content and discussions. [https://phabricator.wikimedia.org/T346467][https://phabricator.wikimedia.org/T344079] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.27|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-19|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-20|en}}. It will be on all wikis from {{#time:j xg|2023-09-21|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * All wikis will be read-only for a few minutes on September 20. [[m:Special:MyLanguage/Tech/Server switch|This is planned at 14:00 UTC.]] [https://phabricator.wikimedia.org/T345263] * All wikis will have a link in the sidebar that provides a short URL of that page, using the [[m:Special:MyLanguage/Wikimedia URL Shortener|Wikimedia URL Shortener]]. [https://phabricator.wikimedia.org/T267921] '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The team investigating the Graph Extension posted [[mw:Extension:Graph/Plans#Proposal|a proposal for reenabling it]] and they need your input. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/38|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W38"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:20, 18 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25623533 --> == Tech News: 2023-39 == <section begin="technews-2023-W39"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/39|Translations]] are available. '''Recent changes''' * The Vector 2022 skin will now remember the pinned/unpinned status for the Table of Contents for all logged-out users. [https://phabricator.wikimedia.org/T316060] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.28|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-09-26|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-09-27|en}}. It will be on all wikis from {{#time:j xg|2023-09-28|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The ResourceLoader <bdi lang="zxx" dir="ltr"><code><nowiki>mediawiki.ui</nowiki></code></bdi> modules are now deprecated as part of the move to Vue.js and Codex. There is a [[mw:Codex/Migrating_from_MediaWiki_UI|guide for migrating from MediaWiki UI to Codex]] for any tools that use it. More [[phab:T346468|details are available in the task]] and your questions are welcome there. * Gadget definitions will have a [[mw:Special:MyLanguage/Extension:Gadgets#Options|new "namespaces" option]]. The option takes a list of namespace IDs. Gadgets that use this option will only load on pages in the given namespaces. '''Future changes''' * New variables will be added to [[mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilter]]: <code><bdi lang="zxx" dir="ltr">global_account_groups</bdi></code> and <code><bdi lang="zxx" dir="ltr">global_account_editcount</bdi></code>. They are available only when an account is being created. You can use them to prevent blocking automatic creation of accounts when users with many edits elsewhere visit your wiki for the first time. [https://phabricator.wikimedia.org/T345632][https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:AbuseFilter/Rules_format] '''Meetings''' * You can join the next meeting with the Wikipedia mobile apps teams. During the meeting, we will discuss the current features and future roadmap. The meeting will be on [https://zonestamp.toolforge.org/1698426015 27 October at 17:00 (UTC)]. See [[mw:Special:MyLanguage/Wikimedia_Apps/Office_Hours#October_2023|details and how to join]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/39|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W39"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:51, 26 September 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25655264 --> == Tech News: 2023-40 == <section begin="technews-2023-W40"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/40|Translations]] are available. '''Recent changes''' * There is a new [[Special:Preferences#mw-prefsection-rendering-advancedrendering|user preference]] for "{{int:tog-forcesafemode}}". This setting will make pages load without including any on-wiki JavaScript or on-wiki stylesheet pages. It can be useful for debugging broken JavaScript gadgets. [https://phabricator.wikimedia.org/T342347] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Gadget definitions now have a [[mw:Special:MyLanguage/Extension:Gadgets#Options|new "<var>contentModels</var>" option]]. The option takes a list of page content models, like <code><bdi lang="zxx" dir="ltr">wikitext</bdi></code> or <code><bdi lang="zxx" dir="ltr">css</bdi></code>. Gadgets that use this option will only load on pages with the given content models. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.29|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-03|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-04|en}}. It will be on all wikis from {{#time:j xg|2023-10-05|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Vector 2022 skin will no longer use the custom styles and scripts of Vector legacy (2010). The change will be made later this year or in early 2024. See [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Loading Vector 2010 scripts|how to adjust the CSS and JS pages on your wiki]]. [https://phabricator.wikimedia.org/T331679] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/40|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W40"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:27, 3 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25686930 --> == Tech News: 2023-41 == <section begin="technews-2023-W41"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/41|Translations]] are available. '''Recent changes''' * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q33291|Fon]] ([[w:fon:|<code>w:fon:</code>]]) [https://phabricator.wikimedia.org/T347935] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.41/wmf.30|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-10|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-11|en}}. It will be on all wikis from {{#time:j xg|2023-10-12|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-swwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-wawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-warwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-wowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-xalwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-xhwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-xmfwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-yiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-yowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zeawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zh_min_nanwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zuwiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308139] * At some wikis, newcomers are suggested images from Commons to add to articles without any images. Starting on Tuesday, newcomers at these wikis will be able to add images to unillustrated article sections. The specific wikis are listed under "Images recommendations" [[mw:Special:MyLanguage/Growth/Deployment table|at the Growth team deployment table]]. You can [[mw:Special:MyLanguage/Help:Growth/Tools/Add an image|learn more about this feature.]] [https://phabricator.wikimedia.org/T345940] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] In the mobile web skin (Minerva) the CSS ID <bdi lang="zxx" dir="ltr"><code><nowiki>#page-actions</nowiki></code></bdi> will be replaced with <bdi lang="zxx" dir="ltr"><code><nowiki>#p-views</nowiki></code></bdi>. This change is to make it consistent with other skins and to improve support for gadgets and extensions in the mobile skin. A few gadgets may need to be updated; there are [https://phabricator.wikimedia.org/T348267 details and search-links in the task]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/41|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W41"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 14:39, 9 October 2023 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25712895 --> == Wikipedia translation of the week: 2023-42 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Athyma nefte]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:VB 019 Color Sergeant UP.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''''Athyma nefte''''', the colour sergeant, is a species of brush-footed butterfly found in tropical South and Southeast Asia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:58, 16 October 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25693965 --> == Tech News: 2023-42 == <section begin="technews-2023-W42"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/42|Translations]] are available. '''Recent changes''' * The [[m:Special:MyLanguage/Help:Unified login|Unified login]] system's edge login should now be fixed for some browsers (Chrome, Edge, Opera). This means that if you visit a new sister project wiki, you should be logged in automatically without the need to click "Log in" or reload the page. Feedback on whether it's working for you is welcome. [https://phabricator.wikimedia.org/T347889] * [[mw:Special:MyLanguage/Manual:Interface/Edit_notice|Edit notices]] are now available within the MobileFrontend/Minerva skin. This feature was inspired by [[w:en:Wikipedia:EditNoticesOnMobile|the gadget on English Wikipedia]]. See more details in [[phab:T316178|T316178]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.1|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-17|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-18|en}}. It will be on all wikis from {{#time:j xg|2023-10-19|en}} ([[mw:MediaWiki 1.41/Roadmap|calendar]]). '''Future changes''' * In 3 weeks, in the Vector 2022 skin, code related to <bdi lang="zxx" dir="ltr"><code><nowiki>addPortletLink</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>#p-namespaces</nowiki></code></bdi> that was deprecated one year ago will be removed. If you notice tools that should appear next to the "Discussion" tab are then missing, please tell the gadget's maintainers to see [[phab:T347907|instructions in the Phabricator task]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/42|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W42"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:47, 16 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25745824 --> == Wikipedia translation of the week: 2023-43 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Typhoon Rusa]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Rusa 2002-08-27 0350Z.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Typhoon Rusa''' was the most powerful typhoon to strike South Korea in 43 years. It was the 21st JTWC tropical depression, the 15th named storm, and the 10th typhoon of the 2002 Pacific typhoon season. It developed on August 22 from the monsoon trough in the northwestern Pacific Ocean, well to the southeast of Japan. For several days, Rusa moved to the northwest, eventually intensifying into a powerful typhoon. On August 26, the storm moved across the Amami Islands of Japan, where Rusa left 20,000 people without power and caused two fatalities. Across Japan, the typhoon dropped torrential rainfall peaking at 902 mm (35.5 in) in Tokushima Prefecture. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:50, 23 October 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25693965 --> == Tech News: 2023-43 == <section begin="technews-2023-W43"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/43|Translations]] are available. '''Recent changes''' * There is a new [[mw:Special:MyLanguage/Wikimedia Language engineering/Newsletter/2023/October|Language and internationalization newsletter]], written quarterly. It contains updates on new feature development, improvements in various language-related technical projects, and related support work. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Source map support has been enabled on all wikis. When you open the debugger in your browser's developer tools, you should be able to see the unminified JavaScript source code. [https://phabricator.wikimedia.org/T47514] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.2|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-24|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-10-25|en}}. It will be on all wikis from {{#time:j xg|2023-10-26|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/43|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W43"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:17, 23 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25782286 --> == Wikipedia translation of the week: 2023-44 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Hein Eersel]]'''<br /> <small>''([[:nl:Hein Eersel]]) ([[:it:Hein Eersel]])''</small> </div> Please be bold and help translate this article! ---- [[File:HeinEersel.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Christiaan Hendrik "Hein" Eersel''' was a Surinamese linguist and cultural researcher. He served as Minister of Education and Population Development in the cabinet of acting Prime Minister Arthur Johan May. He was also the first chancellor of the University of Suriname. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:09, 30 October 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-44 == <section begin="technews-2023-W44"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/44|Translations]] are available. '''Recent changes''' * The Structured Content team, as part of its project of [[:commons:Commons:WMF support for Commons/Upload Wizard Improvements|improving UploadWizard on Commons]], made some UX improvements to the upload step of choosing own vs not own work ([[phab:T347590|T347590]]), as well as to the licensing step for own work ([[phab:T347756|T347756]]). * The Design Systems team has released version 1.0.0 of [[wmdoc:codex/latest/|Codex]], the new design system for Wikimedia. See the [[mw:Special:MyLanguage/Design_Systems_Team/Announcing_Codex_1.0|full announcement about the release of Codex 1.0.0]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.3|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-10-31|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-01|en}}. It will be on all wikis from {{#time:j xg|2023-11-02|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). * Listings on category pages are sorted on each wiki for that language using a [[:w:en:International Components for Unicode|library]]. For a brief period on 2 November, changes to categories will not be sorted correctly for many languages. This is because the developers are upgrading to a new version of the library. They will then use a script to fix the existing categories. This will take a few hours or a few days depending on how big the wiki is. You can [[mw:Special:MyLanguage/Wikimedia Technical Operations/ICU announcement|read more]]. [https://phabricator.wikimedia.org/T345561][https://phabricator.wikimedia.org/T267145] * Starting November 1, the impact module (Special:Impact) will be upgraded by the Growth team. The new impact module shows newcomers more data regarding their impact on the wiki. It was tested by a few wikis during the last few months. [https://phabricator.wikimedia.org/T336203] '''Future changes''' * There is [[mw:Special:MyLanguage/Extension:Graph/Plans#Roadmap|a proposed plan]] for re-enabling the Graph Extension. You can help by reviewing this proposal and [[mw:Extension_talk:Graph/Plans#c-PPelberg_(WMF)-20231020221600-Update:_20_October|sharing what you think about it]]. * The WMF is working on making it possible for administrators to [[mw:Special:MyLanguage/Community_configuration_2.0|edit MediaWiki configuration directly]]. This is similar to previous work on Special:EditGrowthConfig. [[phab:T349757|A technical RfC is running until November 08, where you can provide feedback.]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/44|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W44"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:21, 30 October 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25801989 --> == Tech News: 2023-45 == <section begin="technews-2023-W45"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/45|Translations]] are available. '''Recent changes''' * In the Vector 2022 skin, the default font-size of a number of navigational elements (tagline, tools menu, navigational links, and more) has been increased slightly to match the font size used in page content. [https://phabricator.wikimedia.org/T346062] '''Problems''' * Last week, there was a problem displaying some recent edits on [https://noc.wikimedia.org/conf/highlight.php?file=dblists/s5.dblist a few wikis], for 1-6 hours. The edits were saved but not immediately shown. This was due to a database problem. [https://phabricator.wikimedia.org/T350443] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.4|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-11-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-08|en}}. It will be on all wikis from {{#time:j xg|2023-11-09|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). * The Growth team will reassign newcomers from former mentors to [[mw:Special:MyLanguage/Growth/Structured mentor list|the currently active mentors]]. They have also changed the notification language to be more user-friendly. [https://phabricator.wikimedia.org/T330071][https://phabricator.wikimedia.org/T327493] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/45|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W45"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:06, 6 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25838105 --> == Wikipedia translation of the week: 2023-45 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Reclaim the Night]]'''<br /> <small>''([[:de:Reclaim the Night]])''</small> </div> Please be bold and help translate this article! ---- [[File:Reclaim the Night 2014.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Reclaim the Night''' is a movement started in Leeds in 1977 as part of the Women's Liberation Movement. Marches demanding that women be able to move throughout public spaces at night took place across England until the 1990s. Later, the organisation was revived and sponsors annual and national marches against rape and violence against women. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 00:40, 8 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Wikipedia translation of the week: 2023-46 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ishe Komborera Africa]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Ishe Komborera Africa.mp3|center|300px|]] <div style="text-align:left; padding: .4em;"> "'''Ishe Komborera Africa'''" (Shona for: God Bless Africa), also called "Ishe Komborera Zimbabwe" (Shona for: God Bless Zimbabwe), was the Zimbabwean national anthem from 1980 to 1994. It was the country's first national anthem after gaining independence in 1980. It is a translation of 19th-century South African schoolteacher Enoch Sontonga's popular African hymn "Nkosi Sikelel' iAfrika" into Zimbabwe's native Shona and Ndebele languages. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 00:38, 13 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-46 == <section begin="technews-2023-W46"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/46|Translations]] are available. '''Recent changes''' * Four new wikis have been created: ** a Wikipedia in [[d:Q7598268|Moroccan Amazigh]] ([[w:zgh:|<code>w:zgh:</code>]]) [https://phabricator.wikimedia.org/T350216] ** a Wikipedia in [[d:Q35159|Dagaare]] ([[w:dga:|<code>w:dga:</code>]]) [https://phabricator.wikimedia.org/T350218] ** a Wikipedia in [[d:Q33017|Toba Batak]] ([[w:bbc:|<code>w:bbc:</code>]]) [https://phabricator.wikimedia.org/T350320] ** a Wikiquote in [[d:Q33151|Banjar]] ([[q:bjn:|<code>q:bjn:</code>]]) [https://phabricator.wikimedia.org/T350217] '''Problems''' * Last week, users who previously visited Meta-Wiki or Wikimedia Commons and then became logged out on those wikis could not log in again. The problem is now resolved. [https://phabricator.wikimedia.org/T350695] * Last week, some pop-up dialogs and menus were shown with the wrong font size. The problem is now resolved. [https://phabricator.wikimedia.org/T350544] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.5|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-11-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-15|en}}. It will be on all wikis from {{#time:j xg|2023-11-16|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). '''Future changes''' * Reference Previews are coming to many wikis as a default feature. They are popups for references, similar to the [[mw:Special:MyLanguage/Page Previews|PagePreviews feature]]. [[m:WMDE Technical Wishes/ReferencePreviews#Opt-out feature|You can opt out]] of seeing them. If you are [[Special:Preferences#mw-prefsection-gadgets|using the gadgets]] Reference Tooltips or Navigation Popups, you won’t see Reference Previews. [[phab:T282999|Deployment]] is planned for November 22, 2023. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Canary (also known as heartbeat) events will be produced into [https://stream.wikimedia.org/?doc#/streams Wikimedia event streams] from December 11. Streams users are advised to filter out these events, by discarding all events where <bdi lang="zxx" dir="ltr"><code><nowiki>meta.domain == "canary"</nowiki></code></bdi>. Updates to [[mw:Special:MyLanguage/Manual:Pywikibot|Pywikibot]] or [https://github.com/ChlodAlejandro/wikimedia-streams wikimedia-streams] will discard these events by default. [https://phabricator.wikimedia.org/T266798] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/46|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W46"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:52, 13 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25859263 --> == Wikipedia translation of the week: 2023-47 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Bhagavata Mela]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Bhagavata Mela''' is a classical Indian dance that is performed in Tamil Nadu, particularly the Thanjavur area. It is choreographed as an annual Vaishnavism tradition in Melattur and nearby regions, and celebrated as a dance-drama performance art. The dance art has roots in a historic migration of practitioners of Kuchipudi, another Indian classical dance art, from Andhra Pradesh to the kingdom of Tanjavur. The term Bhagavata, state Brandon and Banham, refers to the Hindu text Bhagavata Purana. Mela is a Sanskrit word that means "gathering, meeting of a group" and connotes a folk festival. The traditional Bhagavata Mela performance acts out the legends of Hinduism, set to the Carnatic style music. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 00:38, 04:07, 20 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-47 == <section begin="technews-2023-W47"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/47|Translations]] are available. '''Changes later this week''' * There is no new MediaWiki version this week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting on Wednesday, a new set of Wikipedias will get "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]" ({{int:project-localized-name-quwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rmywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-roa_rupwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-roa_tarawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ruewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rwwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sahwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-satwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-scwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-scnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-scowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sdwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-shwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-siwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-skwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-slwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-smwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sqwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-srwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-srnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-sswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-stwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-stqwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-suwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-szlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tcywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tetwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tgwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-thwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-towiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tpiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ttwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-twwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tyvwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-udmwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ugwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-uzwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vecwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vepwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vlswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-vowiki/en}}). This is part of the [[phab:T304110|progressive deployment of this tool to more Wikipedias]]. The communities can [[mw:Special:MyLanguage/Growth/Community configuration|configure how this feature works locally]]. [https://phabricator.wikimedia.org/T308141][https://phabricator.wikimedia.org/T308142][https://phabricator.wikimedia.org/T308143] * The Vector 2022 skin will have some minor visual changes to drop-down menus, column widths, and more. These changes were added to four Wikipedias last week. If no issues are found, these changes will proceed to all wikis this week. These changes will make it possible to add new menus for readability and dark mode. [[mw:Special:MyLanguage/Reading/Web/Desktop_Improvements/Updates#November_2023:_Visual_changes,_more_deployments,_and_shifting_focus|Learn more]]. [https://phabricator.wikimedia.org/T347711] '''Future changes''' * There is [[mw:Extension talk:Graph/Plans#Update: 15 November|an update on re-enabling the Graph Extension]]. To speed up the process, Vega 2 will not be supported and only [https://phabricator.wikimedia.org/T335325 some protocols] will be available at launch. You can help by sharing what you think about the plan. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/47|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W47"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:55, 21 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25884616 --> == Wikipedia translation of the week: 2023-48 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:fr:Zanskari]]'''<br /> <small>''([[:en:Zaniskari]])''</small> </div> Please be bold and help translate this article! ---- [[File:Zaniskari Horse in Ladakh, India.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Zaniskari''' or '''Zanskari''' is a breed of small mountain horse or pony from Ladakh, in northern India. It is named for the Zanskar valley or region in Kargil district. It is similar to the Spiti breed of Himachal Pradesh, but is better adapted to work at high altitude. Like the Spiti, it shows similarities to the Tibetan breeds of neighbouring Tibet. It is of medium size, and is often grey in colour. The breed is considered endangered, as there are only a few hundred alive today, and a conservation programme has been started at Padum, Zanskar, in the Kargil district of Ladakh. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:44, 27 November 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25797248 --> == Tech News: 2023-48 == <section begin="technews-2023-W48"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/48|Translations]] are available. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.7|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-11-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-11-29|en}}. It will be on all wikis from {{#time:j xg|2023-11-30|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). There is no new MediaWiki version next week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] MediaWiki's JavaScript system will now allow <bdi lang="zxx" dir="ltr"><code>async</code>/<code>await</code></bdi> syntax in gadgets and user scripts. Gadget authors should remember that users' browsers may not support it, so it should be used appropriately. [https://phabricator.wikimedia.org/T343499] * The deployment of "[[mw:Special:MyLanguage/Help:Growth/Tools/Add_a_link|Add a link]]" announced [[m:Special:MyLanguage/Tech/News/2023/47|last week]] was postponed. It will resume this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/48|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W48"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:09, 27 November 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25906379 --> == Wikipedia translation of the week: 2023-49 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sheikh Hussein]]'''<br /> <small>''([[:fr:Sheikh Hussein]]) ([[:it:Scec Hussèn]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sheikh Hussein.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Sheikh Hussein''' is a town in south-eastern Ethiopia. The site has been recorded in the tentative list for UNESCO World Heritage List since 2011 as a religious, cultural and historical site. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:34, 4 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25921616 --> == Tech News: 2023-49 == <section begin="technews-2023-W49"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/49|Translations]] are available. '''Recent changes''' * The spacing between paragraphs on Vector 2022 has been changed from 7px to 14px to match the size of the text. This will make it easier to distinguish paragraphs from sentences. [https://phabricator.wikimedia.org/T351754] * The "{{int:Visualeditor-dialog-meta-categories-defaultsort-label}}" feature in VisualEditor is working again. You no longer need to switch to source editing to edit <bdi lang="zxx" dir="ltr"><code><nowiki>{{DEFAULTSORT:...}}</nowiki></code></bdi> keywords. [https://phabricator.wikimedia.org/T337398] '''Changes later this week''' * There is no new MediaWiki version this week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * On 6 December, people who have the enabled the preference for "{{int:Discussiontools-preference-visualenhancements}}" will notice the [[mw:Special:MyLanguage/Talk pages project/Usability|talk page usability improvements]] appear on pages that include the <bdi lang="zxx" dir="ltr"><code><nowiki>__NEWSECTIONLINK__</nowiki></code></bdi> magic word. If you notice any issues, please [[phab:T352232|share them with the team on Phabricator]]. '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Toolforge [[wikitech:News/Toolforge Grid Engine deprecation|Grid Engine shutdown process]] will start on December 14. Maintainers of [[toolforge:grid-deprecation|tools that still use this old system]] should plan to migrate to Kubernetes, or tell the team your plans on Phabricator in the task about your tool, before that date. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/VIWWQKMSQO2ED3TVUR7KPPWRTOBYBVOA/] * Communities using [[mw:Special:MyLanguage/Structured_Discussions|Structured Discussions]] are being contacted regarding [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|the upcoming deprecation of Structured Discussions]]. You can read more about this project, and share your comments, [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|on the project's page]]. '''Events''' * Registration & Scholarship applications are now open for the [[mw:Special:MyLanguage/Wikimedia Hackathon 2024|Wikimedia Hackathon 2024]] that will take place from 3–5 May in Tallinn, Estonia. Scholarship applications are open until 5 January 2024. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/49|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W49"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:50, 4 December 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25914435 --> == Wikipedia translation of the week: 2023-50 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:fr:Applaudissements aux fenêtres pendant la pandémie de Covid-19]]'''<br /> <small>''([[:es:Aplauso por los trabajadores de la salud]]) ([[:gl:Aplauso ao persoal sanitario]])''</small> </div> Please be bold and help translate this article! ---- [[File:Koronabirus konfinamendua Lasarten 2020-03-29.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> During the COVID-19 pandemic, applauding daily at a scheduled hour was a gesture of acclamation, recognition and gratitude towards health professionals in tribute to their work at the time. This habit emerged in January 2020 in Wuhan, where the pandemic originated, and then spread to several cities around the world during the quarantines and sanitary cordons ordered as preventive measures, Italy being the first one. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:26, 11 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25925561 --> == Tech News: 2023-50 == <section begin="technews-2023-W50"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/50|Translations]] are available. '''Recent changes''' * On Wikimedia Commons, there are some minor user-interface improvements for the "choosing own vs not own work" step in the UploadWizard. This is part of the Structured Content team's project of [[:commons:Commons:WMF support for Commons/Upload Wizard Improvements|improving UploadWizard on Commons]]. [https://phabricator.wikimedia.org/T352707][https://phabricator.wikimedia.org/T352709] '''Problems''' * There was a problem showing the [[mw:Special:MyLanguage/Growth/Personalized first day/Newcomer homepage|Newcomer homepage]] feature with the "impact module" and their page-view graphs, for a few days in early December. This has now been fixed. [https://phabricator.wikimedia.org/T352352][https://phabricator.wikimedia.org/T352349] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.9|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-12-12|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-12-13|en}}. It will be on all wikis from {{#time:j xg|2023-12-14|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * [[File:Octicons-tools.svg|15px|link=]] The [https://wikimediafoundation.limesurvey.net/796964 2023 Developer Satisfaction Survey] is seeking the opinions of the Wikimedia developer community. Please take the survey if you have any role in developing software for the Wikimedia ecosystem. The survey is open until 5 January 2024, and has an associated [[foundation:Legal:December_2023_Developer_Satisfaction_Survey|privacy statement]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/50|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W50"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:13, 12 December 2023 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25945501 --> == Wikipedia translation of the week: 2023-51 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Jamaica Bay Wildlife Refuge]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Aerial view of Subway Island, July 2019.JPG|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Jamaica Bay Wildlife Refuge''' is a wildlife refuge in New York City managed by the National Park Service as part of Gateway National Recreation Area. It is composed of the open water and intertidal salt marshes of Jamaica Bay. It lies entirely within the boundaries of New York City, divided between the boroughs of Brooklyn to the west and Queens to the east. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:05, 18 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25951007 --> == Tech News: 2023-51 == <section begin="technews-2023-W51"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2023/51|Translations]] are available. '''Tech News''' * The next issue of Tech News will be sent out on 8 January 2024 because of [[w:en:Christmas and holiday season|the holidays]]. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.10|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2023-12-19|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2023-12-20|en}}. It will be on all wikis from {{#time:j xg|2023-12-21|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). There is no new MediaWiki version next week. [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting December 18, it won't be possible to activate Structured Discussions on a user's own talk page using the Beta feature. The Beta feature option remains available for users who want to deactivate Structured Discussions. This is part of [[mw:Structured Discussions/Deprecation|Structured Discussions' deprecation work]]. [https://phabricator.wikimedia.org/T248309] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] There will be full support for redirects in the Module namespace. The "Move Page" feature will leave an appropriate redirect behind, and such redirects will be appropriately recognized by the software (e.g. hidden from [[{{#special:UnconnectedPages}}]]). There will also be support for [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#Renaming or moving modules|manual redirects]]. [https://phabricator.wikimedia.org/T120794] '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The MediaWiki JavaScript documentation is moving to a new format. During the move, you can read the old docs using [https://doc.wikimedia.org/mediawiki-core/REL1_41/js/ version 1.41]. Feedback about [https://doc.wikimedia.org/mediawiki-core/master/js/ the new site] is welcome on the [[mw:Talk:JSDoc_WMF_theme|project talk page]]. * The Wishathon is a new initiative that encourages collaboration across the Wikimedia community to develop solutions for wishes collected through the [[m:Special:MyLanguage/Community Wishlist Survey|Community Wishlist Survey]]. The first community Wishathon will take place from 15–17 March. If you are interested in a project proposal as a user, developer, designer, or product lead, you can [[m:Special:MyLanguage/Event:WishathonMarch2024|register for the event and read more]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2023/51|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2023-W51"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:18, 18 December 2023 (UTC) <!-- Message sent by User:Johan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=25959059 --> == Wikipedia translation of the week: 2023-52 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Plant blindness]]'''<br /> <small>''([[:fr:Cécité botanique]]) ([[:de:Pflanzenblindheit]])''</small> </div> Please be bold and help translate this article! ---- [[File:Plant blindness 0323.png|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Plant blindness''' is an informally-proposed form of cognitive bias, which in its broadest meaning, is a human tendency to ignore plant species. This includes such phenomena as not noticing plants in the surrounding environment, not recognizing the importance of plant life to the whole biosphere and to human affairs, a philosophical view of plants as an inferior form of life to animals and/or the inability to appreciate the unique features or aesthetics of plants. Related terms include plant‐neglect, zoo-centrism, and zoo‐chauvinism. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:58, 25 December 2023 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=25971304 --> == Wikipedia translation of the week: 2024-02 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pax airship disaster]]'''<br /> <small>''([[:pt:Catástrofe do dirigível Pax]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sim new-mcclures-magazine 1902-09 19 5 (page 75 crop).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''''Pax''''' '''airship disaster''' was the explosion of the ''Pax'' airship on May 12, 1902, in Paris, which killed the Brazilian inventor Augusto Severo and the French mechanic Georges Saché. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 12:14, 8 January 2024 (UTC)'' </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26033876 --> == Tech News: 2024-02 == <section begin="technews-2024-W02"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/02|Translations]] are available. '''Recent changes''' * [https://mediawiki2latex.wmflabs.org/ mediawiki2latex] is a tool that converts wiki content into the formats of LaTeX, PDF, ODT, and EPUB. The code now runs many times faster due to recent improvements. There is also an optional Docker container you can [[b:de:Benutzer:Dirk_Hünniger/wb2pdf/install#Using_Docker|install]] on your local machine. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The way that Random pages are selected has been updated. This will slowly reduce the problem of some pages having a lower chance of appearing. [https://phabricator.wikimedia.org/T309477] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.13|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-09|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-10|en}}. It will be on all wikis from {{#time:j xg|2024-01-11|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/02|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W02"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:20, 9 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26026251 --> == Wikipedia translation of the week: 2024-03 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Conversion to Islam]]'''<br /> <small>''([[:fr:Conversion à l'islam]])''</small> </div> Please be bold and help translate this article! ---- [[File:Sahadah-Topkapi-Palace.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Conversion to Islam''' is accepting Islam as a religion or faith and rejecting any other religion or irreligion. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:11, 15 January 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26044632 --> == Tech News: 2024-03 == <section begin="technews-2024-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/03|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Pages that use the JSON [[mw:Special:MyLanguage/Manual:ContentHandler|contentmodel]] will now use tabs instead of spaces for auto-indentation. This will significantly reduce the page size. [https://phabricator.wikimedia.org/T326065] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[mw:Special:MyLanguage/Extension:Gadgets|Gadgets]] and personal user scripts may now use JavaScript syntax introduced in ES6 (also known as "ES2015") and ES7 ("ES2016"). MediaWiki validates the source code to protect other site functionality from syntax errors, and to ensure scripts are valid in all [[mw:Special:MyLanguage/Compatibility#Browsers|supported browsers]]. Previously, Gadgets could use the <bdi lang="zxx" dir="ltr"><code><nowiki>requiresES6</nowiki></code></bdi> option. This option is no longer needed and will be removed in the future. [https://phabricator.wikimedia.org/T75714] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[mw:Special:MyLanguage/Manual:Bot passwords|Bot passwords]] and [[mw:Special:MyLanguage/OAuth/Owner-only consumers|owner-only OAuth consumers]] can now be restricted to allow editing only specific pages. [https://phabricator.wikimedia.org/T349957] * You can now [[mw:Special:MyLanguage/Extension:Thanks|thank]] edits made by bots. [https://phabricator.wikimedia.org/T341388] * An update on the status of the Community Wishlist Survey for 2024 [[m:Special:MyLanguage/Community Wishlist Survey/Future Of The Wishlist/January 4, 2024 Update|has been published]]. Please read and give your feedback. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.14|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-16|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-17|en}}. It will be on all wikis from {{#time:j xg|2024-01-18|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting on January 17, it will not be possible to login to Wikimedia wikis from some specific old versions of the Chrome browser (versions 51–66, released between 2016 and 2018). Additionally, users of iOS 12, or Safari on Mac OS 10.14, may need to login to each wiki separately. [https://phabricator.wikimedia.org/T344791] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The <bdi lang="zxx" dir="ltr"><code>jquery.cookie</code></bdi> module was deprecated and replaced with the <bdi lang="zxx" dir="ltr"><code>mediawiki.cookie</code></bdi> module last year. A script has now been run to replace any remaining uses, and this week the temporary alias will be removed. [https://phabricator.wikimedia.org/T354966] '''Future changes''' * Wikimedia Deutschland is working to [[m:WMDE Technical Wishes/Reusing references|make reusing references easier]]. They are looking for people who are interested in participating in [https://wikimedia.sslsurvey.de/User-research-into-Reusing-References-Sign-up-Form-2024/en/ individual video calls for user research in January and February]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:13, 16 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26074460 --> == Wikipedia translation of the week: 2024-04 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Kinder der Landstrasse]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Kinderdlandstrasse plakat.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Kinder der Landstrasse''' (literally: Children of the Country Road) was a project implemented by the Swiss foundation Pro Juventute from 1926 to 1973. The project aimed to assimilate the itinerant Yenish people in Switzerland by forcibly removing their children from their parents and placing them in orphanages or foster homes. Approximately 590 children were affected by this program. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 02:02, 22 January 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26044632 --> == Tech News: 2024-04 == <section begin="technews-2024-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/04|Translations]] are available. '''Problems''' * A bug in UploadWizard prevented linking to the userpage of the uploader when uploading. It has now been fixed. [https://phabricator.wikimedia.org/T354529] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.15|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-23|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-24|en}}. It will be on all wikis from {{#time:j xg|2024-01-25|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:04, 23 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26096197 --> == Wikipedia translation of the week: 2024-05 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Qurm Nature Reserve]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Al-Qurm Wetlands.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Qurm Nature Reserve''' is a national nature reserve in Muscat Governorate, Oman. Located on the Gulf of Oman coast, the reserve protects a mangrove forest and the surrounding wetland in a small estuary within the urban area of Qurm. Established in 1975, the reserve has been designated as an Important Bird Area since 1994, and as a protected Ramsar site since 2013. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:03, 29 January 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26149847 --> == Tech News: 2024-05 == <section begin="technews-2024-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/05|Translations]] are available. '''Recent changes''' * Starting Monday January 29, all talk pages messages' timestamps will become a link. This link is a permanent link to the comment. It allows users to find the comment they are looking for, even if this comment was moved elsewhere. This will affect all wikis except for the English Wikipedia. You can read more about this change [https://diff.wikimedia.org/2024/01/29/talk-page-permalinks-dont-lose-your-threads/ on Diff] or [[mw:Special:MyLanguage/Help:DiscussionTools#Talk_pages_permalinking|on Mediawiki.org]].<!-- The Diff post will be published on Monday morning UTC--> [https://phabricator.wikimedia.org/T302011] * There are some improvements to the CAPTCHA to make it harder for spam bots and scripts to bypass it. If you have feedback on this change, please comment on [[phab:T141490|the task]]. Staff are monitoring metrics related to the CAPTCHA, as well as secondary metrics such as account creations and edit counts. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.16|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-01-30|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-01-31|en}}. It will be on all wikis from {{#time:j xg|2024-02-01|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] On February 1, a link will be added to the "Tools" menu to download a [[w:en:QR code|QR code]] that links to the page you are viewing. There will also be a new [[{{#special:QrCode}}]] page to create QR codes for any Wikimedia URL. This addresses the [[m:Community Wishlist Survey 2023/Mobile and apps/Add ability to share QR code for a page in any Wikimedia project|#19 most-voted wish]] from the [[m:Community Wishlist Survey 2023/Results|2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T329973] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[mw:Special:MyLanguage/Extension:Gadgets|Gadgets]] which only work in some skins have sometimes used the <bdi lang="zxx" dir="ltr"><code>targets</code></bdi> option to limit where you can use them. This will stop working this week. You should use the <bdi lang="zxx" dir="ltr"><code>skins</code></bdi> option instead. [https://phabricator.wikimedia.org/T328497] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:31, 29 January 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26137870 --> == Wikipedia translation of the week: 2024-06 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Timurid architecture]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Gur-e-Amir Mausolueum - Samarkand - Uzbekistan (7488414078).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Timurid architecture''' was an important stage in the architectural history of Iran and Central Asia during the late 14th and 15th centuries. The Timurid Empire (1370–1507), founded by Timur (d. 1405) and conquering most of this region, oversaw a cultural renaissance. In architecture, the Timurid dynasty patronized the construction of palaces, mausoleums, and religious monuments across the region. Their architecture is distinguished by its grand scale, luxurious decoration in tilework, and sophisticated geometric vaulting. This architectural style, along with other aspects of Timurid art, spread across the empire and subsequently influenced the architecture of other empires from the Middle East to the Indian subcontinent. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:23, 5 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26169542 --> == Tech News: 2024-06 == <section begin="technews-2024-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/06|Translations]] are available. '''Recent changes''' *The mobile site history pages now use the same HTML as the desktop history pages. If you hear of any problems relating to mobile history usage please point them to [[phab:T353388|the phabricator task]]. *On most wikis, admins can now block users from making specific actions. These actions are: uploading files, creating new pages, moving (renaming) pages, and sending thanks. The goal of this feature is to allow admins to apply blocks that are adequate to the blocked users' activity. [[m:Special:MyLanguage/Community health initiative/Partial blocks#action-blocks|Learn more about "action blocks"]]. [https://phabricator.wikimedia.org/T242541][https://phabricator.wikimedia.org/T280531] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.17|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-06|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-07|en}}. It will be on all wikis from {{#time:j xg|2024-02-08|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Talk pages permalinks that included diacritics and non-Latin script were malfunctioning. This issue is fixed. [https://phabricator.wikimedia.org/T356199] '''Future changes''' * [[m:WMDE Technical Wishes/ReferencePreviews#24WPs|24 Wikipedias]] with [[mw:Special:MyLanguage/Reference_Tooltips|Reference Tooltips]] as a default gadget are encouraged to remove that default flag. This would make [[mw:Special:MyLanguage/Help:Reference_Previews|Reference Previews]] the new default for reference popups, leading to a more consistent experience across wikis. For [[m:WMDE Technical Wishes/ReferencePreviews#46WPs|46 Wikipedias]] with less than 4 interface admins, the change is already scheduled for mid-February, [[m:Talk:WMDE Technical Wishes/ReferencePreviews#Reference Previews to become the default for previewing references on more wikis.|unless there are concerns]]. The older Reference Tooltips gadget will still remain usable and will override this feature, if it is available on your wiki and you have enabled it in your settings. [https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/ReferencePreviews#Reference_Previews_to_become_the_default_for_previewing_references_on_more_wikis][https://phabricator.wikimedia.org/T355312] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:22, 5 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26180971 --> == Wikipedia translation of the week: 2024-07 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Adoration of the Magi (Fra Angelico and Filippo Lippi)]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Fra Angelico, Fra Filippo Lippi, The Adoration of the Magi.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''''Adoration of the Magi''''' is a tondo, or circular painting, of the Adoration of the Magi assumed to be that recorded in 1492 in the Palazzo Medici Riccardi in Florence as by Fra Angelico. It dates from the mid-15th century and is now in the National Gallery of Art in Washington D.C. Most art historians think that Filippo Lippi painted more of the original work, and that it was added to some years after by other artists, as well as including work by assistants in the workshops of both the original masters. It has been known as the Washington Tondo and Cook Tondo after Herbert Cook, and this latter name in particular continues to be used over 50 years after the painting left the Cook collection. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 07:00, 12 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26187446 --> == Tech News: 2024-07 == <section begin="technews-2024-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/07|Translations]] are available. '''Recent changes''' * The [[d:Wikidata:SPARQL query service/WDQS graph split|WDQS Graph Split experiment]] is working and loaded onto 3 test servers. The team in charge is testing the split's impact and requires feedback from WDQS users through the UI or programmatically in different channels. [https://www.wikidata.org/wiki/Wikidata_talk:SPARQL_query_service/WDQS_graph_split][https://phabricator.wikimedia.org/T356773][https://www.wikidata.org/wiki/User:Sannita_(WMF)] Users' feedback will validate the impact of various use cases and workflows around the Wikidata Query service. [https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/October_2023_scaling_update][https://www.mediawiki.org/wiki/Wikidata_Query_Service/User_Manual#Federation] '''Problems''' *There was a bug that affected the appearance of visited links when using mobile device to access wiki sites. It made the links appear black; [[phab:T356928|this issue]] is fixed. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.18|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-13|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-14|en}}. It will be on all wikis from {{#time:j xg|2024-02-15|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] As work continues on the grid engine deprecation,[https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation] tools on the grid engine will be stopped starting on February 14th, 2024. If you have tools actively migrating you can ask for an extension so they are not stopped. [https://wikitech.wikimedia.org/wiki/Portal:Toolforge/About_Toolforge#Communication_and_support] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 05:49, 13 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26223994 --> == Wikipedia translation of the week: 2024-08 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:nl:Graf met de handjes]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Weg langs het kerkhof tegenover 1, Roermond.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The monument '''Van Gorkum-Van Aefferden''', more well known as the "'''grave with the little hands'''" is a monumental Tombstone in the Dutch city of Roermond. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 13:24, 19 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26260848 --> == Tech News: 2024-08 == <section begin="technews-2024-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/08|Translations]] are available. '''Recent changes''' * If you have the "{{int:Tog-enotifwatchlistpages}}" option enabled, edits by bot accounts no longer trigger notification emails. Previously, only minor edits would not trigger the notification emails. [https://phabricator.wikimedia.org/T356984] * There are changes to how user and site scripts load for [[mw:Special:MyLanguage/Skin:Vector/2022| Vector 2022]] on specific wikis. The changes impacted the following Wikis: all projects with [[mw:Special:MyLanguage/Skin:Vector|Vector legacy]] as the default skin, Wikivoyage, and Wikibooks. Other wikis will be affected over the course of the next three months. Gadgets are not impacted. If you have been affected or want to minimize the impact on your project, see [[Phab:T357580| this ticket]]. Please coordinate and take action proactively. *Newly auto-created accounts (the accounts you get when you visit a new wiki) now have the same local notification preferences as users who freshly register on that wiki. It is effected in four notification types listed in the [[phab:T353225|task's description]]. *The maximum file size when using [[c:Special:MyLanguage/Commons:Upload_Wizard|Upload Wizard]] is now 5 GiB. [https://phabricator.wikimedia.org/T191804] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.19|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-20|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-21|en}}. It will be on all wikis from {{#time:j xg|2024-02-22|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Selected tools on the grid engine have been [[wikitech:News/Toolforge_Grid_Engine_deprecation|stopped]] as we prepare to shut down the grid on March 14th, 2024. The tool's code and data have not been deleted. If you are a maintainer and you want your tool re-enabled reach out to the [[wikitech:Portal:Toolforge/About_Toolforge#Communication_and_support|team]]. Only tools that have asked for extension are still running on the grid. * The CSS <bdi lang="zxx" dir="ltr"><code>[https://developer.mozilla.org/en-US/docs/Web/CSS/filter filter]</code></bdi> property can now be used in HTML <bdi lang="zxx" dir="ltr"><code>style</code></bdi> attributes in wikitext. [https://phabricator.wikimedia.org/T308160] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:37, 19 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26254282 --> == Wikipedia translation of the week: 2024-09 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Doorway effect]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> The '''doorway effect''' is a known psychological event where a person's short-term memory declines when passing through a doorway moving from one location to another when it would not if they had remained in the same place. People experience this effect by forgetting what they were going to do, thinking about, or planning upon entering a different room. This is thought to be due to the change in one's physical environment, which is used to distinguish boundaries between remembered events: memories of events encountered in the present environment are more accessible than those beyond it. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:30, 26 February 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26260848 --> == Tech News: 2024-09 == <section begin="technews-2024-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/09|Translations]] are available. '''Recent changes''' * The [[mw:Special:MyLanguage/VisualEditor_on_mobile|mobile visual editor]] is now the default editor for users who never edited before, at a small group of wikis. [[mw:Special:MyLanguage/VisualEditor_on_mobile/VE_mobile_default#A/B_test_results| Research ]] shows that users using this editor are slightly more successful publishing the edits they started, and slightly less successful publishing non-reverted edits. Users who defined the wikitext editor as their default on desktop will get the wikitext editor on mobile for their first edit on mobile as well. [https://phabricator.wikimedia.org/T352127] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[mw:Special:MyLanguage/ResourceLoader/Core modules#mw.config|mw.config]] value <code>wgGlobalGroups</code> now only contains groups that are active in the wiki. Scripts no longer have to check whether the group is active on the wiki via an API request. A code example of the above is: <bdi lang="zxx" dir="ltr"><code>if (/globalgroupname/.test(mw.config.get("wgGlobalGroups")))</code></bdi>. [https://phabricator.wikimedia.org/T356008] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.20|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-02-27|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-02-28|en}}. It will be on all wikis from {{#time:j xg|2024-02-29|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * The right to change [[mw:Special:MyLanguage/Manual:Tags|edit tags]] (<bdi lang="zxx" dir="ltr"><code>changetags</code></bdi>) will be removed from users in Wikimedia sites, keeping it by default for admins and bots only. Your community can ask to retain the old configuration on your wiki before this change happens. Please indicate in [[phab:T355639|this ticket]] to keep it for your community before the end of March 2024. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:23, 26 February 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26294125 --> == Wikipedia translation of the week: 2024-10 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Sissieretta Jones]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:1899 poster of Mme. M. Sissieretta Jones.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Matilda Sissieretta Joyner Jones''' (January 5, 1868, or 1869 – June 24, 1933) was an American soprano. She sometimes was called "The Black Patti" in reference to Italian opera singer Adelina Patti. Jones' repertoire included grand opera, light opera, and popular music <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:33, 4 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26313143 --> == Tech News: 2024-10 == <section begin="technews-2024-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/10|Translations]] are available. '''Recent changes''' * The <bdi lang="zxx" dir="ltr"><code>Special:Book</code></bdi> page (as well as the associated "Create a book" functionality) provided by the old [[mw:Special:MyLanguage/Extension:Collection|Collection extension]] has been removed from all Wikisource wikis, as it was broken. This does not affect the ability to download normal books, which is provided by the [[mw:Special:MyLanguage/Extension:Wikisource|Wikisource extension]]. [https://phabricator.wikimedia.org/T358437] * [[m:Wikitech|Wikitech]] now uses the next-generation [[mw:Special:MyLanguage/Parsoid|Parsoid]] wikitext parser by default to generate all pages in the Talk namespace. Report any problems on the [[mw:Talk:Parsoid/Parser_Unification/Known_Issues|Known Issues discussion page]]. You can use the [[mw:Special:MyLanguage/Extension:ParserMigration|ParserMigration]] extension to control the use of Parsoid; see the [[mw:Special:MyLanguage/Help:Extension:ParserMigration|ParserMigration help documentation]] for more details. * Maintenance on [https://etherpad.wikimedia.org etherpad] is completed. If you encounter any issues, please indicate in [[phab:T316421|this ticket]]. * [[File:Octicons-tools.svg|12px|link=|alt=| Advanced item]] [[mw:Special:MyLanguage/Extension:Gadgets|Gadgets]] allow interface admins to create custom features with CSS and JavaScript. The <bdi lang="zxx" dir="ltr"><code>Gadget</code></bdi> and <bdi lang="zxx" dir="ltr"><code>Gadget_definition</code></bdi> namespaces and <bdi lang="zxx" dir="ltr"><code>gadgets-definition-edit</code></bdi> user right were reserved for an experiment in 2015, but were never used. These were visible on Special:Search and Special:ListGroupRights. The unused namespaces and user rights are now removed. No pages are moved, and no changes need to be made. [https://phabricator.wikimedia.org/T31272] * A usability improvement to the "Add a citation" in Wikipedia workflow has been made, the insert button was moved to the popup header. [https://phabricator.wikimedia.org/T354847] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.21|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-05|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-06|en}}. It will be on all wikis from {{#time:j xg|2024-03-07|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * All wikis will be read-only for a few minutes on March 20. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T358233] * The HTML markup of headings and section edit links will be changed later this year to improve accessibility. See [[mw:Special:MyLanguage/Heading_HTML_changes|Heading HTML changes]] for details. The new markup will be the same as in the new Parsoid wikitext parser. You can test your gadget or stylesheet with the new markup if you add <bdi lang="zxx" dir="ltr"><code>?useparsoid=1</code></bdi> to your URL ([[mw:Special:MyLanguage/Help:Extension:ParserMigration#Selecting_a_parser_using_a_URL_query_string|more info]]) or turn on Parsoid read views in your user options ([[mw:Special:MyLanguage/Help:Extension:ParserMigration#Enabling_via_user_preference|more info]]). * '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:47, 4 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26329807 --> == Wikipedia translation of the week: 2024-11 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Preventative Coup of November 11]]'''<br /> <small>''([[:es:Golpe de Estado en Brasil de 1955]])''</small> </div> Please be bold and help translate this article! ---- [[File:Exército na casa de Café Filho.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Preventative Coup of November 11''' sometimes called the '''1955 Brazilian coup d'état''' or referred to as an "anti-coup" or a "counter-coup" (Portuguese: ''Novembrada, Movimento de 11 de Novembro, Contragolpe, Golpe Preventivo do Marechal Lott'') was a series of military and political events led by Henrique Teixeira Lott that resulted in Nereu Ramos assuming the presidency of Brazil until being peacefully succeeded by Juscelino Kubitschek a few months later. The bloodless coup removed Carlos Luz from the presidency because he was suspected of plotting to prevent Kubitschek from taking office. As a result of the tensions, Brazil had three presidents in the span of a single week. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:04, 11 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26366849 --> == Tech News: 2024-11 == <section begin="technews-2024-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/11|Translations]] are available. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.22|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-12|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-13|en}}. It will be on all wikis from {{#time:j xg|2024-03-14|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * After consulting with various communities, the line height of the text on the [[mw:Special:MyLanguage/Skin:Minerva Neue|Minerva skin]] will be increased to its previous value of 1.65. Different options for typography can also be set using the options in the menu, as needed. [https://phabricator.wikimedia.org/T358498] *The active link color in [[mw:Special:MyLanguage/Skin:Minerva Neue|Minerva]] will be changed to provide more consistency with our other platforms and best practices. [https://phabricator.wikimedia.org/T358516] * [[c:Special:MyLanguage/Commons:Structured data|Structured data on Commons]] will no longer ask whether you want to leave the page without saving. This will prevent the “information you’ve entered may not be saved” popups from appearing when no information have been entered. It will also make file pages on Commons load faster in certain cases. However, the popups will be hidden even if information has indeed been entered. If you accidentally close the page before saving the structured data you entered, that data will be lost. [https://phabricator.wikimedia.org/T312315] '''Future changes''' * All wikis will be read-only for a few minutes on March 20. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T358233][https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:04, 11 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26374013 --> == Wikipedia translation of the week: 2024-12 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Hojang Taret]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Hojang Taret''' is a classical Meitei language play based on Euripides's ancient Greek tragedy The Phoenician Women. It is directed by Oasis Sougaijam and produced by The Umbilical Theatre in Imphal, Kangleipak. It depicts the moral ambiguities of conflict between brothers resulting to the ruination of the ancient city of Thebes. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:52, 18 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26366849 --> == Tech News: 2024-12 == <section begin="technews-2024-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/12|Translations]] are available. '''Recent changes''' * The notice "Language links are at the top of the page" that appears in the [[mw:Special:MyLanguage/Skin:Vector/2022|Vector 2022 skin]] main menu has been removed now that users have learned the new location of the Language switcher. [https://phabricator.wikimedia.org/T353619] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[m:Special:MyLanguage/IP_Editing:_Privacy_Enhancement_and_Abuse_Mitigation/IP_Info_feature|IP info feature]] displays data from Spur, an IP addresses database. Previously, the only data source for this feature was MaxMind. Now, IP info is more useful for patrollers. [https://phabricator.wikimedia.org/T341395] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The Toolforge Grid Engine services have been shut down after the final migration process from Grid Engine to Kubernetes. [https://wikitech.wikimedia.org/wiki/Obsolete:Toolforge/Grid][https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation][https://techblog.wikimedia.org/2022/03/14/toolforge-and-grid-engine/] * Communities can now customize the default reasons for undeleting a page by creating [[MediaWiki:Undelete-comment-dropdown]]. [https://phabricator.wikimedia.org/T326746] '''Problems''' * [[m:Special:MyLanguage/WMDE_Technical_Wishes/RevisionSlider|RevisionSlider]] is an interface to interactively browse a page's history. Users in [[mw:Special:MyLanguage/Extension:RevisionSlider/Developing_a_RTL-accessible_feature_in_MediaWiki_-_what_we%27ve_learned_while_creating_the_RevisionSlider|right-to-left]] languages reported RevisionSlider reacting wrong to mouse clicks. This should be fixed now. [https://phabricator.wikimedia.org/T352169] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.23|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-19|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-20|en}}. It will be on all wikis from {{#time:j xg|2024-03-21|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * All wikis will be read-only for a few minutes on March 20. This is planned at [https://zonestamp.toolforge.org/1710943200 14:00 UTC]. [https://phabricator.wikimedia.org/T358233][https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/Server_switch] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:40, 18 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26410165 --> == Wikipedia translation of the week: 2024-13 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Magna Lykseth-Skogman]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Magna Lykseth in Tristan och Isolde at Kungliga Operan 1909 - SMV - GL164.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Magna Elvine Lykseth-Skogman''' (6 February 1874 – 13 November 1949), also known as Magna Lykseth-Schjerven, was a Norwegian-born Swedish operatic soprano. After making her début at the Royal Swedish Opera in 1901 as Santuzza in Cavalleria rusticana, she was engaged there until 1918 becoming the company's prima donna. She performed leading roles in a wide range of operas but is remembered in particular for her Wagnerian interpretations, creating Brünnhilde in the Swedish premières of Siegfried and Götterdämmerung, and Isolde in 1909. Considered to be one of the most outstanding Swedish opera singers of her generation, she was awarded the Litteris et Artibus medal in 1907 and became a member of the Royal Swedish Academy of Music in 1912 <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:00, 25 March 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26447450 --> == Tech News: 2024-13 == <section begin="technews-2024-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/13|Translations]] are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] An update was made on March 18th 2024 to how various projects load site, user JavaScript and CSS in [[mw:Special:MyLanguage/Skin:Vector/2022|Vector 2022 skin]]. A [[phab:T360384|checklist]] is provided for site admins to follow. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.24|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-03-26|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-03-27|en}}. It will be on all wikis from {{#time:j xg|2024-03-28|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:57, 25 March 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26446209 --> == Wikipedia translation of the week: 2024-14 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lidder Valley]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Pahalgam Valley.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Lidder Valley''' or Liddar Valley is a Himalayan sub-valley that forms the southeastern corner of Anantnag district in Indian-administered Kashmir. The Lidder River flows down the valley. The entrance to the valley lies 7 km northeast from Anantnag town and 62 km southeast from Srinagar, the summer capital of Jammu and Kashmir. It is a 40-km-long gorge valley with an average width of 3 km. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:15, 1 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26509189 --> == Tech News: 2024-14 == <section begin="technews-2024-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/14|Translations]] are available. '''Recent changes''' * Users of the [[mw:Special:MyLanguage/Reading/Web/Accessibility_for_reading|reading accessibility]] beta feature will notice that the default line height for the standard and large text options has changed. [https://phabricator.wikimedia.org/T359030] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.25|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-02|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-03|en}}. It will be on all wikis from {{#time:j xg|2024-04-04|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * The Wikimedia Foundation has an annual plan. The annual plan decides what the Wikimedia Foundation will work on. You can now read [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2024-2025/Product & Technology OKRs#Draft Key Results|the draft key results]] for the Product and Technology department. They are suggestions for what results the Foundation wants from big technical changes from July 2024 to June 2025. You can [[m:Talk:Wikimedia Foundation Annual Plan/2024-2025/Product & Technology OKRs|comment on the talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 03:36, 2 April 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26462933 --> == Wikipedia translation of the week: 2024-15 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Operation Kraai]]'''<br /> </div> Please be bold and help translate this article! ---- [[File:Overzicht van het vliegveld te Djokja vanuit de 'Control Tower', Bestanddeelnr 5128.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Operation Kraai''' (Operation Crow) was a Dutch military offensive against the de facto Republic of Indonesia in December 1948 after negotiations failed. With the advantage of surprise the Dutch managed to capture the Indonesian Republic's temporary capital, Yogyakarta, and seized Indonesian leaders such as de facto Republican President Sukarno. This apparent military success was however followed by guerrilla warfare, while the violation of the Renville Agreement ceasefire diplomatically isolated the Dutch, leading to the Dutch–Indonesian Round Table Conference and recognition of the United States of Indonesia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:47, 8 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26550154 --> == Tech News: 2024-15 == <section begin="technews-2024-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/15|Translations]] are available. '''Recent changes''' * Web browsers can use tools called [[:w:en:Browser extension|extensions]]. There is now a Chrome extension called [[m:Future Audiences/Experiment:Citation Needed|Citation Needed]] which you can use to see if an online statement is supported by a Wikipedia article. This is a small experiment to see if Wikipedia can be used this way. Because it is a small experiment, it can only be used in Chrome in English. * [[File:Octicons-gift.svg|12px|link=|alt=|Wishlist item]] A new [[mw:Special:MyLanguage/Help:Edit Recovery|Edit Recovery]] feature has been added to all wikis, available as a [[Special:Preferences#mw-prefsection-editing|user preference]]. Once you enable it, your in-progress edits will be stored in your web browser, and if you accidentally close an editing window or your browser or computer crashes, you will be prompted to recover the unpublished text. Please leave any feedback on the [[m:Special:MyLanguage/Talk:Community Wishlist Survey 2023/Edit-recovery feature|project talk page]]. This was the #8 wish in the 2023 Community Wishlist Survey. * Initial results of [[mw:Special:MyLanguage/Edit check|Edit check]] experiments [[mw:Special:MyLanguage/Edit_check#4_April_2024|have been published]]. Edit Check is now deployed as a default feature at [[phab:T342930#9538364|the wikis that tested it]]. [[mw:Talk:Edit check|Let us know]] if you want your wiki to be part of the next deployment of Edit check. [https://phabricator.wikimedia.org/T342930][https://phabricator.wikimedia.org/T361727] * Readers using the [[mw:Special:MyLanguage/Skin:Minerva Neue|Minerva skin]] on mobile will notice there has been an improvement in the line height across all typography settings. [https://phabricator.wikimedia.org/T359029] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.42/wmf.26|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-09|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-10|en}}. It will be on all wikis from {{#time:j xg|2024-04-11|en}} ([[mw:MediaWiki 1.42/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * New accounts and logged-out users will get the [[mw:Special:MyLanguage/VisualEditor|visual editor]] as their default editor on mobile. This deployment is made at all wikis except for the English Wikipedia. [https://phabricator.wikimedia.org/T361134] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:38, 8 April 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26564838 --> == Wikipedia translation of the week: 2024-16 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:ru:Павильон Росси]]'''<br /> <small>''([[:en:Rossi Pavilion]])&#32;([[:fr:Pavillon Rossi]])''</small> </div> Please be bold and help translate this article! ---- [[File:Rossi's Pavilion in Mikhailovsky Garden. Saint-Petersburg. 1825..jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Rossi Pavilion''' (Russian: Павильон Росси) is a pavilion on the bank of the Moyka River in the Mikhailovsky Garden in Saint Petersburg. It was designed by architect Carlo Rossi in the early 1820s and built in 1825 during his redevelopment of the garden. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:53, 15 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26565118 --> == Tech News: 2024-16 == <section begin="technews-2024-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/16|Translations]] are available. '''Problems''' * Between 2 April and 8 April, on wikis using [[mw:Special:MyLanguage/Extension:FlaggedRevs|Flagged Revisions]], the "{{Int:tag-mw-reverted}}" tag was not applied to undone edits. In addition, page moves, protections and imports were not autoreviewed. This problem is now fixed. [https://phabricator.wikimedia.org/T361918][https://phabricator.wikimedia.org/T361940] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.1|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-16|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-17|en}}. It will be on all wikis from {{#time:j xg|2024-04-18|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[mw:Special:MyLanguage/Help:Magic words#DEFAULTSORT|Default category sort keys]] will now affect categories added by templates placed in [[mw:Special:MyLanguage/Help:Cite|footnotes]]. Previously footnotes used the page title as the default sort key even if a different default sort key was specified (category-specific sort keys already worked). [https://phabricator.wikimedia.org/T40435] * A new variable <bdi lang="zxx" dir="ltr"><code>page_last_edit_age</code></bdi> will be added to [[Special:AbuseFilter|abuse filters]]. It tells how many seconds ago the last edit to a page was made. [https://phabricator.wikimedia.org/T269769] '''Future changes''' * Volunteer developers are kindly asked to update the code of their tools and features to handle [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]]. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers/2024-04 CTA|Learn more]]. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Four database fields will be removed from database replicas (including [[quarry:|Quarry]]). This affects only the <bdi lang="zxx" dir="ltr"><code>abuse_filter</code></bdi> and <bdi lang="zxx" dir="ltr"><code>abuse_filter_history</code></bdi> tables. Some queries might need to be updated. [https://phabricator.wikimedia.org/T361996] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:29, 15 April 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26564838 --> == Wikipedia translation of the week: 2024-17 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Devorà Ascarelli]]'''<br /> <small>''([[:it:Debora Ascarelli]])&#32;([[:es:Devorà Ascarelli]])''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Devorà Ascarelli''' was a 16th-century Italian poet living in Rome, Italy. Ascarelli may have been the first Jewish woman to have a book of her own work published. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] 01:35, 22 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26624302 --> == Tech News: 2024-17 == <section begin="technews-2024-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/17|Translations]] are available. '''Recent changes''' * Starting this week, newcomers editing Wikipedia [[mw:Special:MyLanguage/Growth/Positive reinforcement#Leveling up 3|will be encouraged]] to try structured tasks. [[mw:Special:MyLanguage/Growth/Feature summary#Newcomer tasks|Structured tasks]] have been shown to [[mw:Special:MyLanguage/Growth/Personalized first day/Structured tasks/Add a link/Experiment analysis, December 2021|improve newcomer activation and retention]]. [https://phabricator.wikimedia.org/T348086] * You can [[m:Special:MyLanguage/Coolest Tool Award|nominate your favorite tools]] for the fifth edition of the Coolest Tool Award. Nominations will be open until May 10. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.2|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-23|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-04-24|en}}. It will be on all wikis from {{#time:j xg|2024-04-25|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * This is the last warning that by the end of May 2024 the Vector 2022 skin will no longer share site and user scripts/styles with old Vector. For user-scripts that you want to keep using on Vector 2022, copy the contents of [[{{#special:MyPage}}/vector.js]] to [[{{#special:MyPage}}/vector-2022.js]]. There are [[mw:Special:MyLanguage/Reading/Web/Desktop Improvements/Features/Loading Vector 2010 scripts|more technical details]] available. Interface administrators who foresee this leading to lots of technical support questions may wish to send a mass message to your community, as was done on French Wikipedia. [https://phabricator.wikimedia.org/T362701] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:28, 22 April 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26647188 --> == Wikipedia translation of the week: 2024-18 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:1989 Serbian general election]]'''<br /> <small>''([[:sr:Председнички избори у Србији 1989.]])&#32;([[:vi:Tổng tuyển cử Serbia 1989]])''</small></div> Please be bold and help translate this article! ---- [[File:Parliament of SR Serbia (1989–1991).svg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''General elections were held in Serbia''', a constituent federal unit of SFR Yugoslavia, on 12 November 1989 to elect the president of the presidency of the Socialist Republic of Serbia and delegates of the Assembly of SR Serbia. Voting for delegates also took place on 10 and 30 November 1989. In addition to the general elections, local elections were held simultaneously. These were the first direct elections conducted after the adoption of the 1974 Yugoslav Constitution and the delegate electoral system, and the last elections conducted under a one-party system. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:32, 29 April 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26624302 --> == Tech News: 2024-18 == <section begin="technews-2024-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/18|Translations]] are available. '''Recent changes''' [[File:Talk_pages_default_look_(April_2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * The appearance of talk pages changed for the following wikis: {{int:project-localized-name-azwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-bnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hiwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-idwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ptwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-rowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-thwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ukwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-viwiki/en}}. These wikis participated to a test, where 50% of users got the new design, for one year. As this test [[Mw:Special:MyLanguage/Talk pages project/Usability/Analysis|gave positive results]], the new design is deployed on these wikis as the default design. It is possible to opt-out these changes [[Special:Preferences#mw-prefsection-editing|in user preferences]] ("{{int:discussiontools-preference-visualenhancements}}"). The deployment will happen at all wikis in the coming weeks. [https://phabricator.wikimedia.org/T341491] * Seven new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q33014|Betawi]] ([[w:bew:|<code>w:bew:</code>]]) [https://phabricator.wikimedia.org/T357866] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q35708|Kusaal]] ([[w:kus:|<code>w:kus:</code>]]) [https://phabricator.wikimedia.org/T359757] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q35513|Igala]] ([[w:igl:|<code>w:igl:</code>]]) [https://phabricator.wikimedia.org/T361644] ** a {{int:project-localized-name-group-wiktionary}} in [[d:Q33541|Karakalpak]] ([[wikt:kaa:|<code>wikt:kaa:</code>]]) [https://phabricator.wikimedia.org/T362135] ** a {{int:project-localized-name-group-wikisource}} in [[d:Q9228|Burmese]] ([[s:my:|<code>s:my:</code>]]) [https://phabricator.wikimedia.org/T361085] ** a {{int:project-localized-name-group-wikisource}} in [[d:Q9237|Malay]] ([[s:ms:|<code>s:ms:</code>]]) [https://phabricator.wikimedia.org/T363039] ** a {{int:project-localized-name-group-wikisource}} in [[d:Q8108|Georgian]] ([[s:ka:|<code>s:ka:</code>]]) [https://phabricator.wikimedia.org/T363085] * You can now [https://translatewiki.net/wiki/Support#Early_access:_Watch_Message_Groups_on_Translatewiki.net watch message groups/projects] on [[m:Special:MyLanguage/translatewiki.net|Translatewiki.net]]. Initially, this feature will notify you of added or deleted messages in these groups. [https://phabricator.wikimedia.org/T348501] * Dark mode is now available on all wikis, on mobile web for logged-in users who opt into the [[Special:MobileOptions|advanced mode]]. This is the early release of the feature. Technical editors are invited to [https://night-mode-checker.wmcloud.org/ check for accessibility issues on wikis]. See [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-04|more detailed guidelines]]. '''Problems''' * [[mw:Special:MyLanguage/Help:Extension:Kartographer|Kartographer]] maps can use an alternative visual style without labels, by using <bdi lang="zxx" dir="ltr"><code><nowiki>mapstyle="osm"</nowiki></code></bdi>. This wasn't working in previews, creating the wrong impression that it wasn't supported. This has now been fixed. [https://phabricator.wikimedia.org/T362531] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.3|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-04-30|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-01|en}}. It will be on all wikis from {{#time:j xg|2024-05-02|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 03:34, 30 April 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26689057 --> == Wikipedia translation of the week: 2024-19 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Heinrich Bünting]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Heinrich Bünting''' (1545 – 1606) was a Protestant pastor and theologian. He is best known for his book of woodcut maps titled Itinerarium Sacrae Scripturae (Travel book through Holy Scripture) first published in 1581. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:27, 6 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26624302 --> == Tech News: 2024-19 == <section begin="technews-2024-W19"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/19|Translations]] are available. '''Recent changes''' [[File:Talk_pages_default_look_(April_2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * The appearance of talk pages changed for all wikis, except for Commons, Wikidata and most Wikipedias ([[m:Special:MyLanguage/Tech/News/2024/18|a few]] have already received this design change). You can read the detail of the changes [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|on ''Diff'']]. It is possible to opt-out these changes [[Special:Preferences#mw-prefsection-editing|in user preferences]] ("{{int:discussiontools-preference-visualenhancements}}"). The deployment will happen at remaining wikis in the coming weeks. [https://phabricator.wikimedia.org/T352087][https://phabricator.wikimedia.org/T319146] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Interface admins now have greater control over the styling of article components on mobile with the introduction of the <code>SiteAdminHelper</code>. More information on how styles can be disabled can be found [[mw:Special:MyLanguage/Extension:WikimediaMessages#Site_admin_helper|at the extension's page]]. [https://phabricator.wikimedia.org/T363932] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]] has added article body sections in JSON format and a curated short description field to the existing parsed Infobox. This expansion to the API is also available via Wikimedia Cloud Services. [https://enterprise.wikimedia.com/blog/article-sections-and-description/] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.4|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-07|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-08|en}}. It will be on all wikis from {{#time:j xg|2024-05-09|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * When you look at the Special:Log page, the first view is labelled "All public logs", but it only shows some logs. This label will now say "Main public logs". [https://phabricator.wikimedia.org/T237729] '''Future changes''' * A new service will be built to replace [[mw:Special:MyLanguage/Extension:Graph|Extension:Graph]]. Details can be found in [[mw:Special:MyLanguage/Extension:Graph/Plans|the latest update]] regarding this extension. * Starting May 21, English Wikipedia and German Wikipedia will get the possibility to activate "[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]". This is part of the [[phab:T304110|progressive deployment of this tool to all Wikipedias]]. These communities can [[mw:Special:MyLanguage/Growth/Community configuration|activate and configure the feature locally]]. [https://phabricator.wikimedia.org/T308144] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/19|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W19"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:45, 6 May 2024 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26729363 --> == Wikipedia translation of the week: 2024-20 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background:var(--background-color-backdrop-dark, #DDDDDD); border:1px solid #BBBBBB; color:var(--color-inverted, #000000); padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ruyan (district)]]'''<br /> <small>''([[:fa:رویان (طبرستان)]])''</small> </div> Please be bold and help translate this article! ---- [[File:Northern Iran and its surroundings during the Iranian intermezzo.svg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Ruyan''' (Persian: رویان), later known as Rustamdar (رستمدار), was the name of a mountainous district that encompassed the western part of Tabaristan/Mazandaran, a region on the Caspian coast of northern Iran. In Iranian mythology, Ruyan appears as one of the places that the legendary archer Arash shot his arrow from, reaching the edge of Khorasan to mark the border between Iran and Turan. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:39, 13 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26755244 --> == Tech News: 2024-20 == <section begin="technews-2024-W20"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/20|Translations]] are available. '''Recent changes''' * On Wikisource there is a special page listing pages of works without corresponding scan images. Now you can use the new magic word <bdi lang="zxx" dir="ltr"><code>__EXPECTWITHOUTSCANS__</code></bdi> to exclude certain pages (list of editions or translations of works) from that list. [https://phabricator.wikimedia.org/T344214] * If you use the [[Special:Preferences#mw-prefsection-editing|user-preference]] "{{int:tog-uselivepreview}}", then the template-page feature "{{int:Templatesandbox-editform-legend}}" will now also work without reloading the page. [https://phabricator.wikimedia.org/T136907] * [[mw:Special:Mylanguage/Extension:Kartographer|Kartographer]] maps can now specify an alternative text via the <bdi lang="zxx" dir="ltr"><code><nowiki>alt=</nowiki></code></bdi> attribute. This is identical in usage to the <bdi lang="zxx" dir="ltr"><code><nowiki>alt=</nowiki></code></bdi> attribute in the [[mw:Special:MyLanguage/Help:Images#Syntax|image and gallery syntax]]. An exception for this feature is wikis like Wikivoyage where the miniature maps are interactive. [https://phabricator.wikimedia.org/T328137] * The old [[mw:Special:MyLanguage/Extension:GuidedTour|Guided Tour]] for the "[[mw:Special:MyLanguage/Edit Review Improvements/New filters for edit review|New Filters for Edit Review]]" feature has been removed. It was created in 2017 to show people with older accounts how the interface had changed, and has now been seen by most of the intended people. [https://phabricator.wikimedia.org/T217451] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.5|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-14|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-15|en}}. It will be on all wikis from {{#time:j xg|2024-05-16|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The [[{{#special:search}}]] results page will now use CSS flex attributes, for better accessibility, instead of a table. If you have a gadget or script that adjusts search results, you should update your script to the new HTML structure. [https://phabricator.wikimedia.org/T320295] '''Future changes''' * In the Vector 2022 skin, main pages will be displayed at full width (like special pages). The goal is to keep the number of characters per line large enough. This is related to the coming changes to typography in Vector 2022. [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates|Learn more]]. [https://phabricator.wikimedia.org/T357706] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Two columns of the <bdi lang="zxx" dir="ltr"><code>[[mw:Special:MyLanguage/Manual:pagelinks table|pagelinks]]</code></bdi> database table (<bdi lang="zxx" dir="ltr"><code>pl_namespace</code></bdi> and <bdi lang="zxx" dir="ltr"><code>pl_title</code></bdi>) are being dropped soon. Users must use two columns of the new <bdi lang="zxx" dir="ltr"><code>[[mw:special:MyLanguage/Manual:linktarget table|linktarget]]</code></bdi> table instead (<bdi lang="zxx" dir="ltr"><code>lt_namespace</code></bdi> and <bdi lang="zxx" dir="ltr"><code>lt_title</code></bdi>). In your existing SQL queries: *# Replace <bdi lang="zxx" dir="ltr"><code>JOIN pagelinks</code></bdi> with <bdi lang="zxx" dir="ltr"><code>JOIN linktarget</code></bdi> and <bdi lang="zxx" dir="ltr"><code>pl_</code></bdi> with <bdi lang="zxx" dir="ltr"><code>lt_</code></bdi> in the <bdi lang="zxx" dir="ltr"><code>ON</code></bdi> statement *# Below that add <bdi lang="zxx" dir="ltr"><code>JOIN pagelinks ON lt_id = pl_target_id</code></bdi> ** See <bdi lang="en" dir="ltr">[[phab:T222224]]</bdi> for technical reasoning. [https://phabricator.wikimedia.org/T222224][https://phabricator.wikimedia.org/T299947] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/20|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W20"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:59, 13 May 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26762074 --> == Wikipedia translation of the week: 2024-21 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Turlough (lake)]]'''<br /> <small>''([[:de:Turlough]])&#32;([[:no:Turlough]])''</small> </div> Please be bold and help translate this article! ---- [[File:Carran Turlough.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''turlough''' is a seasonal or periodic water body found mostly in limestone karst areas of Ireland, west of the River Shannon. [...] The water bodies fill and empty with the changes in the level of the water table, usually being very low or empty during summer and autumn and full in the winter. As groundwater levels drop the water drains away underground through cracks in the karstic limestone. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:31, 20 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26789673 --> == Tech News: 2024-21 == <section begin="technews-2024-W21"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/21|Translations]] are available. '''Recent changes''' * The [[mw:Special:MyLanguage/Extension:Nuke|Nuke]] feature, which enables administrators to mass delete pages, will now correctly delete pages which were moved to another title. [https://phabricator.wikimedia.org/T43351] * New changes have been made to the UploadWizard in Wikimedia Commons: the overall layout has been improved, by following new styling and spacing for the form and its fields; the headers and helper text for each of the fields was changed; the Caption field is now a required field, and there is an option for users to copy their caption into the media description. [https://commons.wikimedia.org/wiki/Commons:WMF_support_for_Commons/Upload_Wizard_Improvements#Changes_to_%22Describe%22_workflow][https://phabricator.wikimedia.org/T361049] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.6|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-21|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-22|en}}. It will be on all wikis from {{#time:j xg|2024-05-23|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The HTML used to render all headings [[mw:Heading_HTML_changes|is being changed to improve accessibility]]. It will change on 22 May in some skins (Timeless, Modern, CologneBlue, Nostalgia, and Monobook). Please test gadgets on your wiki on these skins and [[phab:T13555|report any related problems]] so that they can be resolved before this change is made in all other skins. The developers are also considering the introduction of a [[phab:T337286|Gadget API for adding buttons to section titles]] if that would be helpful to tool creators, and would appreciate any input you have on that. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/21|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W21"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:04, 20 May 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26786311 --> == Wikipedia translation of the week: 2024-22 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Geiranger Church]]'''<br /> <small>''([[:no:Geiranger kirke]])''</small> </div> Please be bold and help translate this article! ---- [[File:Iglesia parroquial, Geiranger, Noruega, 2019-09-07, DD 84-97 PAN.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Geiranger Church''' (Norwegian: Geiranger kyrkje) is a parish church of the Church of Norway in Stranda Municipality in Møre og Romsdal county, Norway. It is located in the village of Geiranger, and the end of the famous Geirangerfjorden. It is the church for the Geiranger parish which is part of the Nordre Sunnmøre prosti (deanery) in the Diocese of Møre. The white, wooden church was built in an octagonal design in 1842 using plans drawn up by the architect Hans Klipe. The church seats about 165 people. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:48, 27 May 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26828106 --> == Tech News: 2024-22 == <section begin="technews-2024-W22"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/22|Translations]] are available. '''Recent changes''' * Several bugs related to the latest updates to the UploadWizard on Wikimedia Commons have been fixed. For more information, see [[:phab:T365107|T365107]] and [[:phab:T365119|T365119]]. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] In March 2024 a new [[mw:ResourceLoader/Core_modules#addPortlet|addPortlet]] API was added to allow gadgets to create new portlets (menus) in the skin. In certain skins this can be used to create dropdowns. Gadget developers are invited to try it and [[phab:T361661|give feedback]]. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Some CSS in the Minerva skin has been removed to enable easier community configuration. Interface editors should check the rendering on mobile devices for aspects related to the classes: <bdi lang="zxx" dir="ltr"><code>.collapsible</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.multicol</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.reflist</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.coordinates</code></bdi>{{int:comma-separator/en}}<bdi lang="zxx" dir="ltr"><code>.topicon</code></bdi>. [[phab:T361659|Further details are available on replacement CSS]] if it is needed. '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.7|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-05-28|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-05-29|en}}. It will be on all wikis from {{#time:j xg|2024-05-30|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * When you visit a wiki where you don't yet have a local account, local rules such as edit filters can sometimes prevent your account from being created. Starting this week, MediaWiki takes your global rights into account when evaluating whether you can override such local rules. [https://phabricator.wikimedia.org/T316303] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/22|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W22"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:15, 28 May 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26832205 --> == Wikipedia translation of the week: 2024-23 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Guillermo Larrazábal]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Guillermo Larrazábal Arzubide''' (10 February 1907 – 1983) was a Spanish stained glass artist who was active in Ecuador. He is considered Ecuador's most important stained glass artist. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:14, 3 June 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26828106 --> == Tech News: 2024-23 == <section begin="technews-2024-W23"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/23|Translations]] are available. '''Recent changes''' * It is now possible for local administrators to add new links to the bottom of the site Tools menu without JavaScript. [[mw:Manual:Interface/Sidebar#Add or remove toolbox sections|Documentation is available]]. [https://phabricator.wikimedia.org/T6086] * The message name for the definition of the tracking category of WikiHiero has changed from "<bdi lang="zxx" dir="ltr"><code>MediaWiki:Wikhiero-usage-tracking-category</code></bdi>" to "<bdi lang="zxx" dir="ltr"><code>MediaWiki:Wikihiero-usage-tracking-category</code></bdi>". [https://gerrit.wikimedia.org/r/c/mediawiki/extensions/wikihiero/+/1035855] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q5317225|Kadazandusun]] ([[w:dtp:|<code>w:dtp:</code>]]) [https://phabricator.wikimedia.org/T365220] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.8|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-04|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-05|en}}. It will be on all wikis from {{#time:j xg|2024-06-06|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Future changes''' * Next week, on wikis with the Vector 2022 skin as the default, logged-out desktop users will be able to choose between different font sizes. The default font size will also be increased for them. This is to make Wikimedia projects easier to read. [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-06 deployments|Learn more]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/23|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W23"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:35, 3 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26844397 --> == Tech News: 2024-24 == <section begin="technews-2024-W24"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/24|Translations]] are available. '''Recent changes''' * The software used to render SVG files has been updated to a new version, fixing many longstanding bugs in SVG rendering. [https://phabricator.wikimedia.org/T265549] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The HTML used to render all headings [[mw:Heading HTML changes|is being changed to improve accessibility]]. It was changed last week in some skins (Vector legacy and Minerva). Please test gadgets on your wiki on these skins and [[phab:T13555|report any related problems]] so that they can be resolved before this change is made in Vector-2022. The developers are still considering the introduction of a [[phab:T337286|Gadget API for adding buttons to section titles]] if that would be helpful to tool creators, and would appreciate any input you have on that. * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The HTML markup used for citations by [[mw:Special:MyLanguage/Parsoid|Parsoid]] changed last week. In places where Parsoid previously added the <bdi lang="zxx" dir="ltr"><code>mw-reference-text</code></bdi> class, Parsoid now also adds the <bdi lang="zxx" dir="ltr"><code>reference-text</code></bdi> class for better compatibility with the legacy parser. [[mw:Specs/HTML/2.8.0/Extensions/Cite/Announcement|More details are available]]. [https://gerrit.wikimedia.org/r/1036705] '''Problems''' * There was a bug with the Content Translation interface that caused the tools menus to appear in the wrong location. This has now been fixed. [https://phabricator.wikimedia.org/T366374] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.9|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-11|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-12|en}}. It will be on all wikis from {{#time:j xg|2024-06-13|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The new version of MediaWiki includes another change to the HTML markup used for citations: [[mw:Special:MyLanguage/Parsoid|Parsoid]] will now generate a <bdi lang="zxx" dir="ltr"><code><nowiki><span class="mw-cite-backlink"></nowiki></code></bdi> wrapper for both named and unnamed references for better compatibility with the legacy parser. Interface administrators should verify that gadgets that interact with citations are compatible with the new markup. [[mw:Specs/HTML/2.8.0/Extensions/Cite/Announcement|More details are available]]. [https://gerrit.wikimedia.org/r/1035809] * On multilingual wikis that use the <bdi lang="zxx" dir="ltr"><code><nowiki><translate></nowiki></code></bdi> system, there is a feature that shows potentially-outdated translations with a pink background until they are updated or confirmed. From this week, confirming translations will be logged, and there is a new user-right that can be required for confirming translations if the community [[m:Special:MyLanguage/Requesting wiki configuration changes|requests it]]. [https://phabricator.wikimedia.org/T49177] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/24|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W24"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:20, 10 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26893898 --> == Wikipedia translation of the week: 2024-25 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:de:Magdalena Zeger]]'''<br /> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Magdalena Zeger''' ([mak.da.ˈleː.na ˈt͡seː.gɐ], * 1491; † 16. January 1568 in Kolding) was a calendar maker, astronomer and astrologist. Her Hamburg almanacs and forecasts from 1561 and 1563 have been preserved. Zeger's calendars are the first independent publications by a woman in the field of astronomy. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:29, 17 June 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26940351 --> == Tech News: 2024-25 == <section begin="technews-2024-W25"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/25|Translations]] are available. '''Recent changes''' * People who attempt to add an external link in the visual editor will now receive immediate feedback if they attempt to link to a domain that a project has decided to block. Please see [[mw:Special:MyLanguage/Edit_check#11_June_2024|Edit check]] for more details. [https://phabricator.wikimedia.org/T366751] * The new [[mw:Special:MyLanguage/Extension:CommunityConfiguration|Community Configuration extension]] is available [[testwiki:Special:CommunityConfiguration|on Test Wikipedia]]. This extension allows communities to customize specific features to meet their local needs. Currently only Growth features are configurable, but the extension will support other [[mw:Special:MyLanguage/Community_configuration#Use_cases|Community Configuration use cases]] in the future. [https://phabricator.wikimedia.org/T323811][https://phabricator.wikimedia.org/T360954] * The dark mode [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] is now available on category and help pages, as well as more special pages. There may be contrast issues. Please report bugs on the [[mw:Talk:Reading/Web/Accessibility_for_reading|project talk page]]. [https://phabricator.wikimedia.org/T366370] '''Problems''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] Cloud Services tools were not available for 25 minutes last week. This was caused by a faulty hardware cable in the data center. [https://wikitech.wikimedia.org/wiki/Incidents/2024-06-11_WMCS_Ceph] * Last week, styling updates were made to the Vector 2022 skin. This caused unforeseen issues with templates, hatnotes, and images. Changes to templates and hatnotes were reverted. Most issues with images were fixed. If you still see any, [[phab:T367463|report them here]]. [https://phabricator.wikimedia.org/T367480] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.10|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-18|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-19|en}}. It will be on all wikis from {{#time:j xg|2024-06-20|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting June 18, the [[mw:Special:MyLanguage/Help:Edit check#ref|Reference Edit Check]] will be deployed to [[phab:T361843|a new set of Wikipedias]]. This feature is intended to help newcomers and to assist edit-patrollers by inviting people who are adding new content to a Wikipedia article to add a citation when they do not do so themselves. During [[mw:Special:MyLanguage/Edit_check#Reference_Check_A/B_Test|a test at 11 wikis]], the number of citations added [https://diff.wikimedia.org/?p=127553 more than doubled] when Reference Check was shown to people. Reference Check is [[mw:Special:MyLanguage/Edit check/Configuration|community configurable]]. [https://phabricator.wikimedia.org/T361843]<!-- NOTE: THE DIFF BLOG WILL BE PUBLISHED ON MONDAY --> * [[m:Special:MyLanguage/Mailing_lists|Mailing lists]] will be unavailable for roughly two hours on Tuesday 10:00–12:00 UTC. This is to enable migration to a new server and upgrade its software. [https://phabricator.wikimedia.org/T367521] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/25|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W25"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:49, 17 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26911987 --> == Wikipedia translation of the week: 2024-26 == {| class="plainlinks mw-content-ltr" lang="en" dir="ltr" style="width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;" |- |style="text-align:center;"| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Koreans in Micronesia]]'''<br /> <small>''([[:zh:朝鮮裔密克羅尼西亞人]])''</small> </div> Please be bold and help translate this article! ---- <div style="text-align:left; padding: .4em;"> '''Koreans in Micronesia''' used to form a significant population before World War II, when most of the region was ruled as the South Seas Mandate of the Empire of Japan; for example, they formed 7.3% of the population of Palau in 1943. However, after the area came under the control of the United States as the Trust Territory of the Pacific Islands, most Koreans returned to their homeland. As of 2013, about seven thousand South Korean expatriates & immigrants and Korean Americans reside in the Marianas (Guam and the Commonwealth of the Northern Mariana Islands), which have remained under U.S. control, while only around two hundred South Korean expatriates reside in the independent countries of Micronesia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 04:03, 24 June 2024 (UTC)'' </div> |} <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=26940351 --> == Tech News: 2024-26 == <section begin="technews-2024-W26"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/26|Translations]] are available. '''Recent changes''' * Editors will notice that there have been some changes to the background color of text in the diff view, and the color of the byte-change numbers, last week. These changes are intended to make text more readable in both light mode and dark mode, and are part of a larger effort to increase accessibility. You can share your comments or questions [[mw:Talk:Reading/Web/Accessibility for reading|on the project talkpage]]. [https://phabricator.wikimedia.org/T361717] * The text colors that are used for visited-links, hovered-links, and active-links, were also slightly changed last week to improve their accessibility in both light mode and dark mode. [https://phabricator.wikimedia.org/T366515] '''Problems''' * You can [[mw:Special:MyLanguage/Help:DiscussionTools#Talk pages permalinking|copy permanent links to talk page comments]] by clicking on a comment's timestamp. [[mw:Talk pages project/Permalinks|This feature]] did not always work when the topic title was very long and the link was used as a wikitext link. This has been fixed. Thanks to Lofhi for submitting the bug. [https://phabricator.wikimedia.org/T356196] '''Changes later this week''' * [[File:Octicons-sync.svg|12px|link=|alt=|Recurrent item]] The [[mw:MediaWiki 1.43/wmf.11|new version]] of MediaWiki will be on test wikis and MediaWiki.org from {{#time:j xg|2024-06-25|en}}. It will be on non-Wikipedia wikis and some Wikipedias from {{#time:j xg|2024-06-26|en}}. It will be on all wikis from {{#time:j xg|2024-06-27|en}} ([[mw:MediaWiki 1.43/Roadmap|calendar]]). [https://wikitech.wikimedia.org/wiki/Deployments/Train][https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] * Starting 26 June, all talk pages messages' timestamps will become a link at English Wikipedia, making this feature available for you to use at all wikis. This link is a permanent link to the comment. It allows users to find the comment they were linked to, even if this comment has since been moved elsewhere. You can read more about this feature [[DiffBlog:/2024/01/29/talk-page-permalinks-dont-lose-your-threads/|on Diff]] or [[mw:Special:MyLanguage/Help:DiscussionTools#Talk pages permalinking|on Mediawiki.org]]. [https://phabricator.wikimedia.org/T365974] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/26|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W26"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:33, 24 June 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=26989424 --> == Wikipedia translation of the week: 2024-27 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Roller printing on textiles]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Silverstudio.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Roller printing''' on fabrics is a textile printing process patented by Thomas Bell of Scotland in 1783 in an attempt to reduce the cost of the earlier copperplate printing. This method was used in Lancashire fabric mills to produce cotton dress fabrics from the 1790s, most often reproducing small monochrome patterns characterized by striped motifs and tiny dotted patterns called "machine grounds". Improvements in the technology resulted in more elaborate roller prints in bright, rich colours from the 1820s; Turkey red and chrome yellow were particularly popular. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:44, 1 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-27 == <section begin="technews-2024-W27"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/27|Translations]] are available. '''Recent changes''' * Over the next three weeks, dark mode will become available for all users, both logged-in and logged-out, starting with the mobile web version. This fulfils one of the [[m:Special:MyLanguage/Community_Wishlist_Survey_2023/Reading/Dark_mode|top-requested community wishes]], and improves low-contrast reading and usage in low-light settings. As part of these changes, dark mode will also work on User-pages and Portals. There is more information in [[mw:Special:MyLanguage/Reading/Web/Accessibility_for_reading/Updates#June_2024:_Typography_and_dark_mode_deployments,_new_global_preferences|the latest Web team update]]. [https://phabricator.wikimedia.org/T366364] * Logged-in users can now set [[m:Special:GlobalPreferences#mw-prefsection-rendering-skin-skin-prefs|global preferences for the text-size and dark-mode]], thanks to a combined effort across Foundation teams. This allows Wikimedians using multiple wikis to set up a consistent reading experience easily, for example by switching between light and dark mode only once for all wikis. [https://phabricator.wikimedia.org/T341278] * If you use a very old web browser some features might not work on the Wikimedia wikis. This affects Internet Explorer 11 and versions of Chrome, Firefox and Safari older than 2016. This change makes it possible to use new [[d:Q46441|CSS]] features and to send less code to all readers. [https://phabricator.wikimedia.org/T288287][https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:How_to_make_a_MediaWiki_skin#Using_CSS_variables_for_supporting_different_themes_e.g._dark_mode] * Wikipedia Admins can customize local wiki configuration options easily using [[mw:Special:MyLanguage/Community Configuration|Community Configuration]]. Community Configuration was created to allow communities to customize how some features work, because each language wiki has unique needs. At the moment, admins can configure [[mw:Special:MyLanguage/Growth/Feature_summary|Growth features]] on their home wikis, in order to better recruit and retain new editors. More options will be provided in the coming months. [https://phabricator.wikimedia.org/T366458] * Editors interested in language issues that are related to [[w:en:Unicode|Unicode standards]], can now discuss those topics at [[mw:Talk:WMF membership with Unicode Consortium|a new conversation space in MediaWiki.org]]. The Wikimedia Foundation is now a [[mw:Special:MyLanguage/WMF membership with Unicode Consortium|member of the Unicode Consortium]], and the coordination group can collaboratively review the issues discussed and, where appropriate, bring them to the attention of the Unicode Consortium. * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q2891049|Mandailing]] ([[w:btm:|<code>w:btm:</code>]]) [https://phabricator.wikimedia.org/T368038] '''Problems''' * Editors can once again click on links within the visual editor's citation-preview, thanks to a bug fix by the Editing Team. [https://phabricator.wikimedia.org/T368119] '''Future changes''' * Please [https://wikimediafoundation.limesurvey.net/758713?lang=en help us to improve Tech News by taking this short survey]. The goal is to better meet the needs of the various types of people who read Tech News. The survey will be open for 2 weeks. The survey is covered by [https://foundation.wikimedia.org/wiki/Legal:Tech_News_Survey_2024_Privacy_Statement this privacy statement]. Some translations are available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/27|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W27"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:59, 1 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27038456 --> == Wikipedia translation of the week: 2024-28 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:simple:India naming dispute]]'''<br /> <small>''([[:ur:انڈیا نام کا تنازعہ]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''India naming dispute''' in 1947 refers to the argument over the use of the name India during and after the partition of British Raj, between the countries of Pakistan and the Republic of India. This dispute involved key figures such as Lord Mountbatten, the last Viceroy of British Raj, and Muhammad Ali Jinnah, the leader of the Muslim League and a founder of Pakistan. By 1947, the British Raj was going to be divided into two new nation states – Hindustan and Pakistan. Jinnah was initially convinced that Hindustan would not use the term India, since it lacked indigenous pedigree, etymologically and historically India meant the Indus Valley (modern-Pakistan). He also opposed the use of the name India as it would cause confusion regarding history. The disagreement had significant implications for national identity and international recognition. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 8 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-28 == <section begin="technews-2024-W28"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/28|Translations]] are available. '''Recent changes''' * At the Wikimedia Foundation a new task force was formed to replace the disabled Graph with [[mw:Special:MyLanguage/Extension:Chart/Project|more secure, easy to use, and extensible Chart]]. You can [[mw:Special:MyLanguage/Newsletter:Chart Project|subscribe to the newsletter]] to get notified about new project updates and other news about Chart. * The [[m:Special:MyLanguage/CampaignEvents|CampaignEvents]] extension is now available on Meta-wiki, Igbo Wikipedia, and Swahili Wikipedia, and can be requested on your wiki. This extension helps in managing and making events more visible, giving Event organizers the ability to use tools like the Event registration tool. To learn more about the deployment status and how to request this extension for your wiki, visit the [[m:Special:MyLanguage/CampaignEvents/Deployment_status|CampaignEvents page on Meta-wiki]]. * Editors using the iOS Wikipedia app who have more than 50 edits can now use the [[mw:Special:MyLanguage/Wikimedia Apps/iOS Suggested edits#Add an image|Add an Image]] feature. This feature presents opportunities for small but useful contributions to Wikipedia. * Thank you to [[mw:MediaWiki Product Insights/Contributor retention and growth/Celebration|all of the authors]] who have contributed to MediaWiki Core. As a result of these contributions, the [[mw:MediaWiki Product Insights/Contributor retention and growth|percentage of authors contributing more than 5 patches has increased by 25% since last year]], which helps ensure the sustainability of the platform for the Wikimedia projects. '''Problems''' * A problem with the color of the talkpage tabs always showing as blue, even for non-existent pages which should have been red, affecting the Vector 2022 skin, [[phab:T367982|has been fixed]]. '''Future changes''' * The Trust and Safety Product team wants to introduce [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] with as little disruption to tools and workflows as possible. Volunteer developers, including gadget and user-script maintainers, are kindly asked to update the code of their tools and features to handle temporary accounts. The team has [[mw:Trust and Safety Product/Temporary Accounts/For developers|created documentation]] explaining how to do the update. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers/2024-04 CTA|Learn more]]. '''Tech News survey''' * Please [https://wikimediafoundation.limesurvey.net/758713?lang=en help us to improve Tech News by taking this short survey]. The goal is to better meet the needs of the various types of people who read Tech News. The survey will be open for 1 more week. The survey is covered by [https://foundation.wikimedia.org/wiki/Legal:Tech_News_Survey_2024_Privacy_Statement this privacy statement]. Some translations are available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/28|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W28"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:32, 8 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27080357 --> == Wikipedia translation of the week: 2024-29 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Adumu]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Maasai 2012 05 31 2782 (7522645058).jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Adumu''', is a type of dance that the Maasai people of Kenya and Tanzania practice. Young Maasai warriors generally perform the energetic and acrobatic dance at ceremonial occasions including weddings, religious rites, and other significant cultural events. The Adumu dance is characterized by a sequence of jumps performed by the dancers, who stand in a circle and alternately jump while keeping their bodies as straight and upright as possible. In addition to wearing vividly colored shúkàs (clothes) and beaded jewelry, the dancers are typically clad in traditional Maasai costume. Traditional Maasai songs and chants are also performed during the dance. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:15, 15 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-29 == <section begin="technews-2024-W29"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/29|Translations]] are available. '''Tech News survey''' * Please [https://wikimediafoundation.limesurvey.net/758713?lang=en help us to improve Tech News by taking this short survey]. The goal is to better meet the needs of the various types of people who read Tech News. The survey will be open for 3 more days. The survey is covered by [https://foundation.wikimedia.org/wiki/Legal:Tech_News_Survey_2024_Privacy_Statement this privacy statement]. Some translations are available. '''Recent changes''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Wikimedia developers can now officially continue to use both [[mw:Special:MyLanguage/Gerrit|Gerrit]] and [[mw:Special:MyLanguage/GitLab|GitLab]], due to a June 24 decision by the Wikimedia Foundation to support software development on both platforms. Gerrit and GitLab are both code repositories used by developers to write, review, and deploy the software code that supports the MediaWiki software that the wiki projects are built on, as well as the tools used by editors to create and improve content. This decision will safeguard the productivity of our developers and prevent problems in code review from affecting our users. More details are available in the [[mw:GitLab/Migration status|Migration status]] page. * The Wikimedia Foundation seeks applicants for the [[m:Special:MyLanguage/Product and Technology Advisory Council/Proposal|Product and Technology Advisory Council]] (PTAC). This group will bring technical contributors and Wikimedia Foundation together to co-define a more resilient, future-proof technological platform. Council members will evaluate and consult on the movement's product and technical activities, so that we develop multi-generational projects. We are looking for a range of technical contributors across the globe, from a variety of Wikimedia projects. [[m:Special:MyLanguage/Product and Technology Advisory Council/Proposal#Joining the PTAC as a technical volunteer|Please apply here by August 10]]. * Editors with rollback user-rights who use the Wikipedia App for Android can use the new [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/Anti Vandalism|Edit Patrol]] features. These features include a new feed of Recent Changes, related links such as Undo and Rollback, and the ability to create and save a personal library of user talk messages to use while patrolling. If your wiki wants to make these features available to users who do not have rollback rights but have reached a certain edit threshold, [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android#Contact us|you can contact the team]]. You can [[diffblog:2024/07/10/ِaddressing-vandalism-with-a-tap-the-journey-of-introducing-the-patrolling-feature-in-the-mobile-app/|read more about this project on Diff blog]]. * Editors who have access to [[m:Special:MyLanguage/The_Wikipedia_Library|The Wikipedia Library]] can once again use non-open access content in SpringerLinks, after the Foundation [[phab:T368865|contacted]] them to restore access. You can read more about [[m:Tech/News/Recently_resolved_community_tasks|this and 21 other community-submitted tasks that were completed last week]]. '''Changes later this week''' * This week, [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-07 deployments|dark mode will be available on a number of Wikipedias]], both desktop and mobile, for logged-in and logged-out users. Interface admins and user script maintainers are encouraged to check gadgets and user scripts in the dark mode, to find any hard-coded colors and fix them. There are some [[mw:Special:MyLanguage/Recommendations for night mode compatibility on Wikimedia wikis|recommendations for dark mode compatibility]] to help. '''Future changes''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Next week, functionaries, volunteers maintaining tools, and software development teams are invited to test the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] feature on testwiki. Temporary accounts is a feature that will help improve privacy on the wikis. No further temporary account deployments are scheduled yet. Please [[mw:Talk:Trust and Safety Product/Temporary Accounts|share your opinions and questions on the project talk page]]. [https://phabricator.wikimedia.org/T348895] * Editors who upload files cross-wiki, or teach other people how to do so, may wish to join a Wikimedia Commons discussion. The Commons community is discussing limiting who can upload files through the cross-wiki upload/Upload dialog feature to users auto-confirmed on Wikimedia Commons. This is due to the large amount of copyright violations uploaded this way. There is a short summary at [[c:Special:MyLanguage/Commons:Cross-wiki upload|Commons:Cross-wiki upload]] and [[c:Commons:Village pump/Proposals#Deactivate cross-wiki uploads for new users|discussion at Commons:Village Pump]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/29|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' You can also get other news from the [[m:Special:MyLanguage/Wikimedia Foundation Bulletin|Wikimedia Foundation Bulletin]]. </div><section end="technews-2024-W29"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:31, 16 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27124561 --> == Wikipedia translation of the week: 2024-30 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Rathaus-Glockenspiel]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:2019-11-16, Glockenspiel, Neues Münchner Rathaus, IMG 7463 edit Christoph Braun.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Rathaus-Glockenspiel''' is a large mechanical clock located in Marienplatz Square, in the heart of Munich, Germany. Famous for its life-size characters, the clock twice daily re-enacts scenes from Munich's history. First is the story of the marriage of Duke Wilhelm V to Renata of Lorraine in 1568, followed by the story of the Schäfflerstanz, also known as the coopers' dance. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:56, 22 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27031540 --> == Tech News: 2024-30 == <section begin="technews-2024-W30"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/30|Translations]] are available. '''Feature News''' * Stewards can now [[:m:Special:MyLanguage/Global_blocks|globally block]] accounts. Before [[phab:T17294|the change]] only IP addresses and IP ranges could be blocked globally. Global account blocks are useful when the blocked user should not be logged out. [[:m:Special:MyLanguage/Global_locks|Global locks]] (a similar tool logging the user out of their account) are unaffected by this change. The new global account block feature is related to the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|Temporary Accounts]] project, which is a new type of user account that replaces IP addresses of unregistered editors that are no longer made public. * Later this week, Wikimedia site users will notice that the Interface of [[mw:Special:MyLanguage/Extension:FlaggedRevs|FlaggedRevs]] (also known as "Pending Changes") is improved and consistent with the rest of the MediaWiki interface and [[mw:Special:MyLanguage/Codex|Wikimedia's design system]]. The FlaggedRevs interface experience on mobile and [[mw:Special:MyLanguage/Skin:MinervaNeue|Minerva skin]] was inconsistent before it was fixed and ported to [[mw:Special:MyLanguage/Codex|Codex]] by the WMF Growth team and some volunteers. [https://phabricator.wikimedia.org/T191156] * Wikimedia site users can now submit account vanishing requests via [[m:Special:GlobalVanishRequest|GlobalVanishRequest]]. This feature is used when a contributor wishes to stop editing forever. It helps you hide your past association and edit to protect your privacy. Once processed, the account will be locked and renamed. [https://phabricator.wikimedia.org/T367329] * Have you tried monitoring and addressing vandalism in Wikipedia using your phone? [https://diff.wikimedia.org/2024/07/10/%d9%90addressing-vandalism-with-a-tap-the-journey-of-introducing-the-patrolling-feature-in-the-mobile-app/ A Diff blog post on Patrolling features in the Mobile App] highlights some of the new capabilities of the feature, including swiping through a feed of recent changes and a personal library of user talk messages for use when patrolling from your phone. * Wikimedia contributors and GLAM (galleries, libraries, archives, and museums) organisations can now learn and measure the impact Wikimedia Commons is having towards creating quality encyclopedic content using the [https://doc.wikimedia.org/generated-data-platform/aqs/analytics-api/reference/commons.html Commons Impact Metrics] analytics dashboard. The dashboard offers organizations analytics on things like monthly edits in a category, the most viewed files, and which Wikimedia articles are using Commons images. As a result of these new data dumps, GLAM organisation can more reliably measure their return on investment for programs bringing content into the digital Commons. [https://diff.wikimedia.org/2024/07/19/commons-impact-metrics-now-available-via-data-dumps-and-api/] '''Project Updates''' * Come share your ideas for improving the wikis on the newly reopened [[m:Special:MyLanguage/Community Wishlist|Community Wishlist]]. The Community Wishlist is Wikimedia’s forum for volunteers to share ideas (called wishes) to improve how the wikis work. The new version of the wishlist is always open, works with both wikitext and Visual Editor, and allows wishes in any language. '''Learn more''' * Have you ever wondered how Wikimedia software works across over 300 languages? This is 253 languages more than the Google Chrome interface, and it's no accident. The Language and Product Localization Team at the Wikimedia Foundation supports your work by adapting all the tools and interfaces in the MediaWiki software so that contributors in our movement who translate pages and strings can translate them and have the sites in all languages. Read more about the team and their upcoming work on [https://diff.wikimedia.org/2024/07/17/building-towards-a-robust-multilingual-knowledge-ecosystem-for-the-wikimedia-movement/ Diff]. * How can Wikimedia build innovative and experimental products while maintaining such heavily used websites? A recent [https://diff.wikimedia.org/2024/07/09/on-the-value-of-experimentation/ blog post] by WMF staff Johan Jönsson highlights the work of the [[m:Future Audiences#Objectives and Key Results|WMF Future Audience initiative]], where the goal is not to build polished products but test out new ideas, such as a [[m:Future_Audiences/Experiments: conversational/generative AI|ChatGPT plugin]] and [[m:Future_Audiences/Experiment:Add a Fact|Add a Fact]], to help take Wikimedia into the future. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/30|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' You can also get other news from the [[m:Special:MyLanguage/Wikimedia Foundation Bulletin|Wikimedia Foundation Bulletin]]. </div><section end="technews-2024-W30"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:05, 23 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27142915 --> == Wikipedia translation of the week: 2024-31 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Nederlandsche Cocaïnefabriek]]'''<br /> <small>''([[:es:Nederlandsche Cocaïnefabriek]])&#32;([[:nl:Nederlandsche Cocaïnefabriek]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Nederlandsche Cocainefabriek Schinkelstraat Amsterdam architect HH Baanders 1902.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Nederlandsche Cocaïnefabriek''' (Dutch pronunciation: [ˈneːdərlɑntsə koːkaːˈinəfaːˌbrik]; English: Dutch Cocaine Factory) or NCF was an Amsterdam-based company producing cocaine for medical purposes in the 20th century. It imported its raw materials mainly from the Dutch East Indies and sold its products across Europe, making good profits especially in the early years of World War I. The NCF produced morphine, heroin and ephedrine as well. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:44, 29 July 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27150339 --> == Tech News: 2024-31 == <section begin="technews-2024-W31"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/31|Translations]] are available. '''Feature news''' * Editors using the Visual Editor in languages that use non-Latin characters for numbers, such as Hindi, Manipuri and Eastern Arabic, may notice some changes in the formatting of reference numbers. This is a side effect of preparing a new sub-referencing feature, and will also allow fixing some general numbering issues in Visual Editor. If you notice any related problems on your wiki, please share details at the [[m:Talk:WMDE Technical Wishes/Sub-referencing|project talkpage]]. '''Bugs status''' * Some logged-in editors were briefly unable to edit or load pages last week. [[phab:T370304|These errors]] were mainly due to the addition of new [[mw:Special:MyLanguage/Help:Extension:Linter|linter]] rules which led to caching problems. Fixes have been applied and investigations are continuing. * Editors can use the [[mw:Special:MyLanguage/Trust and Safety Product/IP Info|IP Information tool]] to get information about IP addresses. This tool is available as a Beta Feature in your preferences. The tool was not available for a few days last week, but is now working again. Thank you to Shizhao for filing the bug report. You can read about that, and [[m:Tech/News/Recently resolved community tasks#2024-07-25|28 other community-submitted tasks]] that were resolved last week. '''Project updates''' * There are new features and improvements to Phabricator from the Release Engineering and Collaboration Services teams, and some volunteers, including: the search systems, the new task creation system, the login systems, the translation setup which has resulted in support for more languages (thanks to Pppery), and fixes for many edge-case errors. You can [[phab:phame/post/view/316/iterative_improvements/|read details about these and other improvements in this summary]]. * There is an [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|update on the Charts project]]. The team has decided which visualization library to use, which chart types to start focusing on, and where to store chart definitions. * One new wiki has been created: a {{int:project-localized-name-group-wikivoyage}} in [[d:Q9056|Czech]] ([[voy:cs:|<code>voy:cs:</code>]]) [https://phabricator.wikimedia.org/T370905] '''Learn more''' * There is a [[diffblog:2024/07/26/the-journey-to-open-our-first-data-center-in-south-america/|new Wikimedia Foundation data center]] in São Paulo, Brazil which helps to reduce load times. * There is new [[diffblog:2024/07/22/the-perplexing-process-of-uploading-images-to-wikipedia/|user research]] on problems with the process of uploading images. * Commons Impact Metrics are [[diffblog:2024/07/19/commons-impact-metrics-now-available-via-data-dumps-and-api/|now available]] via data dumps and API. * The latest quarterly [[mw:Technical Community Newsletter/2024/July|Technical Community Newsletter]] is now available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/31|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W31"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:11, 29 July 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27164109 --> == Wikipedia translation of the week: 2024-32 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Suffrage drama]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Pamphlet from NAWSA for women's suffrage plays, page 1.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Suffrage drama''' (also known as suffrage plays or suffrage theatre) is a form of dramatic literature that emerged during the British women's suffrage movement in the early twentieth century. Suffrage performances lasted approximately from 1907-1914. Many suffrage plays called for a predominant or all female cast. Suffrage plays served to reveal issues behind the suffrage movement. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 5 August 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27150339 --> == Tech News: 2024-32 == <section begin="technews-2024-W32"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/32|Translations]] are available. '''Feature news''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Two new parser functions will be available this week: <code><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic_words#dir|#dir]]<nowiki>}}</nowiki></code> and <code><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic_words#bcp47|#bcp47]]<nowiki>}}</nowiki></code>. These will reduce the need for <code>Template:Dir</code> and <code>Template:BCP47</code> on Commons and allow us to [[phab:T343131|drop 100 million rows]] from the "what links here" database. Editors at any wiki that use these templates, can help by replacing the templates with these new functions. The templates at Commons will be updated during the Hackathon at Wikimania. [https://phabricator.wikimedia.org/T359761][https://phabricator.wikimedia.org/T366623] * Communities can request the activation of the visual editor on entire namespaces where discussions sometimes happen (for instance ''Wikipedia:'' or ''Wikisource:'' namespaces) if they understand the [[mw:Special:MyLanguage/Help:VisualEditor/FAQ#WPNS|known limitations]]. For discussions, users can already use [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]] in these namespaces. * The tracking category "Pages using Timeline" has been renamed to "Pages using the EasyTimeline extension" [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3ATimeline-tracking-category&namespace=8 in TranslateWiki]. Wikis that have created the category locally should rename their local creation to match. '''Project updates''' * Editors who help to organize WikiProjects and similar on-wiki collaborations, are invited to share ideas and examples of successful collaborations with the Campaigns and Programs teams. You can fill out [[m:Special:MyLanguage/Campaigns/WikiProjects|a brief survey]] or share your thoughts [[m:Talk:Campaigns/WikiProjects|on the talkpage]]. The teams are particularly looking for details about successful collaborations on non-English wikis. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The new parser is being rolled out on {{int:project-localized-name-group-wikivoyage}} wikis over the next few months. The {{int:project-localized-name-enwikivoyage}} and {{int:project-localized-name-hewikivoyage}} were [[phab:T365367|switched]] to Parsoid last week. For more information, see [[mw:Parsoid/Parser_Unification|Parsoid/Parser Unification]]. '''Learn more''' * There will be more than 200 sessions at Wikimania this week. Here is a summary of some of the [[diffblog:2024/08/05/interested-in-product-and-tech-here-are-some-wikimania-sessions-you-dont-want-to-miss/|key sessions related to the product and technology area]]. * The latest [[m:Special:MyLanguage/Wikimedia Foundation Bulletin/2024/07-02|Wikimedia Foundation Bulletin]] is available. * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2024/July|Language and Internationalization newsletter]] is available. It includes: New design previews for Translatable pages; Updates about MinT for Wiki Readers; the release of Translation dumps; and more. * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/31|Growth newsletter]] is available. * The latest monthly [[mw:Special:MyLanguage/MediaWiki Product Insights/Reports/July 2024|MediaWiki Product Insights newsletter]] is available. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/32|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W32"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:44, 5 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27233905 --> == Wikipedia translation of the week: 2024-33 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Karatgurk]]'''<br /> <small>''([[:it:Karatgurk]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> In the Australian Aboriginal mythology of the Aboriginal people of south-eastern Australian state of Victoria, the '''Karatgurk''' were seven sisters who represented the constellation known in western astronomy as the Pleiades. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]] --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 12 August 2024 (UTC)'' </div> </div> <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27264174 --> == Tech News: 2024-33 == <section begin="technews-2024-W33"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/33|Translations]] are available. '''Feature news''' * [[mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilter]] editors and maintainers can now [[mw:Special:MyLanguage/Extension:AbuseFilter/Actions#Show a CAPTCHA|make a CAPTCHA show if a filter matches an edit]]. This allows communities to quickly respond to spamming by automated bots. [https://phabricator.wikimedia.org/T20110] * [[m:Special:MyLanguage/Stewards|Stewards]] can now specify if global blocks should prevent account creation. Before [[phab:T17273|this change]] by the [[mw:Special:MyLanguage/Trust and Safety Product|Trust and Safety Product]] Team, all global blocks would prevent account creation. This will allow stewards to reduce the unintended side-effects of global blocks on IP addresses. '''Project updates''' * [[wikitech:Help talk:Toolforge/Toolforge standards committee#August_2024_committee_nominations|Nominations are open on Wikitech]] for new members to refresh the [[wikitech:Help:Toolforge/Toolforge standards committee|Toolforge standards committee]]. The committee oversees the Toolforge [[wikitech:Help:Toolforge/Right to fork policy|Right to fork policy]] and [[wikitech:Help:Toolforge/Abandoned tool policy|Abandoned tool policy]] among other duties. Nominations will remain open until at least 2024-08-26. * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q2880037|West Coast Bajau]] ([[w:bdr:|<code>w:bdr:</code>]]) [https://phabricator.wikimedia.org/T371757] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/33|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W33"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:22, 12 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27253654 --> == Wikipedia translation of the week: 2024-34 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:B1 (classification)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''B1''' is a medical-based Paralympic classification for blind sport. Athletes in this classification are totally or almost totally blind. It is used by a number of blind sports including blind tennis, para-alpine skiing, para-Nordic skiing, blind cricket, blind golf, five-a-side football, goalball and judo. Some other sports, including adaptive rowing, athletics and swimming, have equivalents to this class. The B1 classification was first created by the IBSA in the 1970s, and has largely remained unchanged since despite an effort by the International Paralympic Committee (IPC) to move towards a more functional and evidence-based classification system. Classification is often handled on the international level by the International Blind Sports Federation (IBSA) but it sometimes handled by national sport federations. There are exceptions for sports like athletics and cycling, where classification is handled by their own governing bodies. Equipment utilized by competitors in this class may differ from sport to sport, and may include sighted guides, guide rails, beeping balls and clapsticks. There may be some modifications related to equipment and rules to specifically address needs of competitors in this class to allow them to compete in specific sports. Some sports specifically do not allow a guide, whereas cycling and skiing require one. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:56, 19 August 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27278917 --> == Tech News: 2024-34 == <section begin="technews-2024-W34"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/34|Translations]] are available. '''Feature news''' * Editors who want to re-use references but with different details such as page numbers, will be able to do so by the end of 2024, using a new [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#Sub-referencing in a nutshell|sub-referencing]] feature. You can read more [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|about the project]] and [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#Test|how to test the prototype]]. * Editors using tracking categories to identify which pages use specific extensions may notice that six of the categories have been renamed to make them more easily understood and consistent. These categories are automatically added to pages that use specialized MediaWiki extensions. The affected names are for: [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Aintersection-category&namespace=8 DynamicPageList], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Akartographer-tracking-category&namespace=8 Kartographer], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Aphonos-tracking-category&namespace=8 Phonos], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Arss-tracking-category&namespace=8 RSS], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Ascore-use-category&namespace=8 Score], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Awikihiero-usage-tracking-category&namespace=8 WikiHiero]. Wikis that have created the category locally should rename their local creation to match. Thanks to Pppery for these improvements. [https://phabricator.wikimedia.org/T347324] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Technical volunteers who edit modules and want to get a list of the categories used on a page, can now do so using the <code><bdi lang="zxx" dir="ltr">categories</bdi></code> property of <code><bdi lang="zxx" dir="ltr">[[mediawikiwiki:Special:MyLanguage/Extension:Scribunto/Lua reference manual#Title objects|mw.title objects]]</bdi></code>. This enables wikis to configure workflows such as category-specific edit notices. Thanks to SD001 for these improvements. [https://phabricator.wikimedia.org/T50175][https://phabricator.wikimedia.org/T85372] '''Bugs status''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Your help is needed to check if any pages need to be moved or deleted. A maintenance script was run to clean up unreachable pages (due to Unicode issues or introduction of new namespaces/namespace aliases). The script tried to find appropriate names for the pages (e.g. by following the Unicode changes or by moving pages whose titles on Wikipedia start with <code>Talk:WP:</code> so that their titles start with <code>Wikipedia talk:</code>), but it may have failed for some pages, and moved them to <bdi lang="zxx" dir="ltr">[[Special:PrefixIndex/T195546/]]</bdi> instead. Your community should check if any pages are listed there, and move them to the correct titles, or delete them if they are no longer needed. A full log (including pages for which appropriate names could be found) is available in [[phab:P67388]]. * Editors who volunteer as [[mw:Special:MyLanguage/Help:Growth/Mentorship|mentors]] to newcomers on their wiki are once again able to access lists of potential mentees who they can connect with to offer help and guidance. This functionality was restored thanks to [[phab:T372164|a bug fix]]. Thank you to Mbch331 for filing the bug report. You can read about that, and 18 other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Project updates''' * The application deadline for the [[m:Special:MyLanguage/Product and Technology Advisory Council/Proposal|Product & Technology Advisory Council]] (PTAC) has been extended to September 16. Members will help by providing advice to Foundation Product and Technology leadership on short and long term plans, on complex strategic problems, and help to get feedback from more contributors and technical communities. Selected members should expect to spend roughly 5 hours per month for the Council, during the one year pilot. Please consider applying, and spread the word to volunteers you think would make a positive contribution to the committee. '''Learn more''' * The [[m:Special:MyLanguage/Coolest Tool Award#2024 Winners|2024 Coolest Tool Awards]] were awarded at Wikimania, in seven categories. For example, one award went to the ISA Tool, used for adding structured data to files on Commons, which was recently improved during the [[m:Event:Wiki Mentor Africa ISA Hackathon 2024|Wiki Mentor Africa Hackathon]]. You can see video demonstrations of each tool at the awards page. Congratulations to this year's recipients, and thank you to all tool creators and maintainers. * The latest [[m:Special:MyLanguage/Wikimedia Foundation Bulletin/2024/08-01|Wikimedia Foundation Bulletin]] is available, and includes some highlights from Wikimania, an upcoming Language community meeting, and other news from the movement. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/34|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W34"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:54, 20 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27307284 --> == Wikipedia translation of the week: 2024-35 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Erzi (village)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Caucasus, Ingushetia, Ингушские боевые и смотровые башни, горы Кавказа.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Erzi''' (Russian: Эрзи; Ingush: Аьрзи, romanized: Ärzi, lit. 'Eagle') is a medieval village (aul) in the Dzheyrakhsky District of Ingushetia. It is part of the rural settlement (administrative center) of Olgeti. The entire territory of the settlement is included in the Dzheyrakh-Assa State Historical-Architectural and Natural Museum-Reserve and is under state protection. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:19, 26 August 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27345183 --> == Tech News: 2024-35 == <section begin="technews-2024-W35"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/35|Translations]] are available. '''Feature news''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Administrators can now test the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] feature on test2wiki. This was done to allow cross-wiki testing of temporary accounts, for when temporary accounts switch between projects. The feature was enabled on testwiki a few weeks ago. No further temporary account deployments are scheduled yet. Temporary Accounts is a project to create a new type of user account that replaces IP addresses of unregistered editors which are no longer made public. Please [[mw:Talk:Trust and Safety Product/Temporary Accounts|share your opinions and questions on the project talk page]]. * Later this week, editors at wikis that use [[mw:Special:MyLanguage/Extension:FlaggedRevs|FlaggedRevs]] (also known as "Pending Changes") may notice that the indicators at the top of articles have changed. This change makes the system more consistent with the rest of the MediaWiki interface. [https://phabricator.wikimedia.org/T191156] '''Bugs status''' * Editors who use the 2010 wikitext editor, and use the Character Insert buttons, will [[phab:T361465|no longer]] experience problems with the buttons adding content into the edit-summary instead of the edit-window. You can read more about that, and 26 other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Project updates''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] Please review and vote on [[m:Special:MyLanguage/Community Wishlist/Focus areas|Focus Areas]], which are groups of wishes that share a problem. Focus Areas were created for the newly reopened Community Wishlist, which is now open year-round for submissions. The first batch of focus areas are specific to moderator workflows, around welcoming newcomers, minimizing repetitive tasks, and prioritizing tasks. Once volunteers have reviewed and voted on focus areas, the Foundation will then review and select focus areas for prioritization. * Do you have a project and are willing to provide a three (3) month mentorship for an intern? [[mw:Special:MyLanguage/Outreachy|Outreachy]] is a twice a year program for people to participate in a paid internship that will start in December 2024 and end in early March 2025, and they need mentors and projects to work on. Projects can be focused on coding or non-coding (design, documentation, translation, research). See the Outreachy page for more details, and a list of past projects since 2013. '''Learn more''' * If you're curious about the product and technology improvements made by the Wikimedia Foundation last year, read [[diffblog:2024/08/21/wikimedia-foundation-product-technology-improving-the-user-experience/|this recent highlights summary on Diff]]. * To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out: ** [[c:File:Wikimania 2024 - Ohrid - Day 2 - Community Configuration - Shaping On-Wiki Functionality Together.webm|Community Configuration - Shaping On-Wiki Functionality Together]] (55 mins) - about the [[mw:Special:MyLanguage/Community Configuration|Community Configuration]] project. ** [[c:File:Wikimania 2024 - Belgrade - Day 1 - Future of MediaWiki. A sustainable platform to support a collaborative user base and billions of page views.webm|Future of MediaWiki. A sustainable platform to support a collaborative user base and billions of page views]] (30 mins) - an overview for both technical and non technical audiences, covering some of the challenges and open questions, related to the [[mw:MediaWiki Product Insights|platform evolution, stewardship and developer experiences]] research. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/35|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W35"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:34, 26 August 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27341211 --> == Tech News: 2024-36 == <section begin="technews-2024-W36"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/36|Translations]] are available. '''Weekly highlight''' * Editors and volunteer developers interested in data visualisation can now test the new software for charts. Its early version is available on beta Commons and beta Wikipedia. This is an important milestone before making charts available on regular wikis. You can [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|read more about this project update]] and help to test the charts. '''Feature news''' * Editors who use the [[{{#special:Unusedtemplates}}]] page can now filter out pages which are expected to be there permanently, such as sandboxes, test-cases, and templates that are always substituted. Editors can add the new magic word [[mw:Special:MyLanguage/Help:Magic words#EXPECTUNUSEDTEMPLATE|<code dir="ltr"><nowiki>__EXPECTUNUSEDTEMPLATE__</nowiki></code>]] to a template page to hide it from the listing. Thanks to Sophivorus and DannyS712 for these improvements. [https://phabricator.wikimedia.org/T184633] * Editors who use the New Topic tool on discussion pages, will [[phab:T334163|now be reminded]] to add a section header, which should help reduce the quantity of newcomers who add sections without a header. You can read more about that, and {{formatnum:28}} other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. * Last week, some Toolforge tools had occasional connection problems. The cause is still being investigated, but the problems have been resolved for now. [https://phabricator.wikimedia.org/T373243] * Translation administrators at multilingual wikis, when editing multiple translation units, can now easily mark which changes require updates to the translation. This is possible with the [[phab:T298852#10087288|new dropdown menu]]. '''Project updates''' * A new draft text of a policy discussing the use of Wikimedia's APIs [[m:Special:MyLanguage/API Policy Update 2024|has been published on Meta-Wiki]]. The draft text does not reflect a change in policy around the APIs; instead, it is an attempt to codify existing API rules. Comments, questions, and suggestions are welcome on [[m:Talk:API Policy Update 2024|the proposed update’s talk page]] until September 13 or until those discussions have concluded. '''Learn more''' * To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out: ** [[c:File:Wikimania 2024 - Ohrid - Day 2 - Charts, the successor of Graphs - A secure and extensible tool for data visualization.webm|Charts, the successor of Graphs - A secure and extensible tool for data visualization]] (25 mins) – about the above-mentioned Charts project. ** [[c:File:Wikimania 2024 - Ohrid - Day 3 - State of Language Technology and Onboarding at Wikimedia.webm|State of Language Technology and Onboarding at Wikimedia]] (90 mins) – about some of the language tools that support Wikimedia sites, such as [[mw:Special:MyLanguage/Content translation|Content]]/[[mw:Special:MyLanguage/Content translation/Section translation|Section Translation]], [[mw:Special:MyLanguage/MinT|MinT]], and LanguageConverter; also the current state and future of languages onboarding. [https://phabricator.wikimedia.org/T368772] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/36|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W36"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:08, 3 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27390268 --> == Wikipedia translation of the week: 2024-37 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cappadocian calendar]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''Cappadocian calendar''' was a solar calendar that was derived from the Persian Zoroastrian calendar. It is named after the historic region Cappadocia in present-day Turkey, where it was used. The calendar, which had 12 months of 30 days each and five epagomenal days, originated between 550 and 330 BC, when Cappadocia was part of the Persian Achaemenid Empire. The Cappadocian calendar was identical to the Zoroastrian calendar; this can be seen in its structure, in the Avestan names and in the order of the months. The Cappadocian calendar reflects the Iranian cultural influence in the region. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:42, 9 September 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27357319 --> == Tech News: 2024-37 == <section begin="technews-2024-W37"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/37|Translations]] are available. '''Feature news''' * Starting this week, the standard [[mw:Special:MyLanguage/Extension:CodeMirror|syntax highlighter]] will receive new colors that make them compatible in dark mode. This is the first of many changes to come as part of a major upgrade to syntax highlighting. You can learn more about what's to come on the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|help page]]. [https://phabricator.wikimedia.org/T365311][https://phabricator.wikimedia.org/T259059] * Editors of wikis using Wikidata will now be notified of only relevant Wikidata changes in their watchlist. This is because the Lua functions <bdi lang="zxx" dir="ltr"><code>entity:getSitelink()</code></bdi> and <bdi lang="zxx" dir="ltr"><code>mw.wikibase.getSitelink(qid)</code></bdi> will have their logic unified for tracking different aspects of sitelinks to reduce junk notifications from [[m:Wikidata For Wikimedia Projects/Projects/Watchlist Wikidata Sitelinks Tracking|inconsistent sitelinks tracking]]. [https://phabricator.wikimedia.org/T295356] '''Project updates''' * Users of all Wikis will have access to Wikimedia sites as read-only for a few minutes on September 25, starting at 15:00 UTC. This is a planned datacenter switchover for maintenance purposes. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T370962] * Contributors of [[phab:T363538#10123348|11 Wikipedias]], including English will have a new <bdi lang="zxx" dir="ltr"><code>MOS</code></bdi> namespace added to their Wikipedias. This improvement ensures that links beginning with <bdi lang="zxx" dir="ltr"><code>MOS:</code></bdi> (usually shortcuts to the [[w:en:Wikipedia:Manual of Style|Manual of Style]]) are not broken by [[w:en:Mooré|Mooré]] Wikipedia (language code <bdi lang="zxx" dir="ltr"><code>mos</code></bdi>). [https://phabricator.wikimedia.org/T363538] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/37|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W37"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:53, 9 September 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27424457 --> == Tech News: 2024-38 == <section begin="technews-2024-W38"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/38|Translations]] are available. '''Improvements and Maintenance''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] Editors interested in templates can help by reading the latest Wishlist focus area, [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|Template recall and discovery]], and share your feedback on the talkpage. This input helps the Community Tech team to decide the right technical approach to build. Everyone is also encouraged to continue adding [[m:Special:MyLanguage/Community Wishlist|new wishes]]. * The new automated [[{{#special:NamespaceInfo}}]] page helps editors understand which [[mw:Special:MyLanguage/Help:Namespaces|namespaces]] exist on each wiki, and some details about how they are configured. Thanks to DannyS712 for these improvements. [https://phabricator.wikimedia.org/T263513] * [[mw:Special:MyLanguage/Help:Edit check#Reference check|References Check]] is a feature that encourages editors to add a citation when they add a new paragraph to a Wikipedia article. For a short time, the corresponding tag "Edit Check (references) activated" was erroneously being applied to some edits outside of the main namespace. This has been fixed. [https://phabricator.wikimedia.org/T373692] * It is now possible for a wiki community to change the order in which a page’s categories are displayed on their wiki. By default, categories are displayed in the order they appear in the wikitext. Now, wikis with a consensus to do so can [[m:Special:MyLanguage/Requesting wiki configuration changes|request]] a configuration change to display them in alphabetical order. [https://phabricator.wikimedia.org/T373480] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Tool authors can now access ToolsDB's [[wikitech:Portal:Data Services#ToolsDB|public databases]] from both [[m:Special:MyLanguage/Research:Quarry|Quarry]] and [[wikitech:Superset|Superset]]. Those databases have always been accessible to every [[wikitech:Portal:Toolforge|Toolforge]] user, but they are now more broadly accessible, as Quarry can be accessed by anyone with a Wikimedia account. In addition, Quarry's internal database can now be [[m:Special:MyLanguage/Research:Quarry#Querying Quarry's own database|queried from Quarry itself]]. This database contains information about all queries that are being run and starred by users in Quarry. This information was already public through the web interface, but you can now query it using SQL. You can read more about that, and {{formatnum:20}} other community-submitted tasks that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. * Any pages or tools that still use the very old CSS classes <bdi lang="zxx" dir="ltr"><code>mw-message-box</code></bdi> need to be updated. These old classes will be removed next week or soon afterwards. Editors can use a [https://global-search.toolforge.org/?q=mw-message-box&regex=1&namespaces=&title= global-search] to determine what needs to be changed. It is possible to use the newer <bdi lang="zxx" dir="ltr"><code>cdx-message</code></bdi> group of classes as a replacement (see [https://doc.wikimedia.org/codex/latest/components/demos/message.html#css-only-version the relevant Codex documentation], and [https://meta.wikimedia.org/w/index.php?title=Tech/Header&diff=prev&oldid=27449042 an example update]), but using locally defined onwiki classes would be best. [https://phabricator.wikimedia.org/T374499] '''Technical project updates''' * Next week, all Wikimedia wikis will be read-only for a few minutes. This will start on September 25 at [https://zonestamp.toolforge.org/1727276400 15:00 UTC]. This is a planned datacenter switchover for maintenance purposes. [[m:Special:MyLanguage/Tech/Server switch|This maintenance process also targets other services.]] The previous switchover took 3 minutes, and the Site Reliability Engineering teams use many tools to make sure that this essential maintenance work happens as quickly as possible. [https://phabricator.wikimedia.org/T370962] '''Tech in depth''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The latest monthly [[mw:Special:MyLanguage/MediaWiki Product Insights/Reports/August 2024|MediaWiki Product Insights newsletter]] is available. This edition includes details about: research about [[mw:Special:MyLanguage/Manual:Hooks|hook]] handlers to help simplify development, research about performance improvements, work to improve the REST API for end-users, and more. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out: ** [[c:File:Wikimania 2024 - Auditorium Kyiv - Day 4 - Hackathon Showcase.webm|Hackathon Showcase]] (45 mins) - 19 short presentations by some of the Hackathon participants, describing some of the projects they worked on, such as automated testing of maintenance scripts, a video-cutting command line tool, and interface improvements for various tools. There are [[phab:T369234|more details and links available]] in the Phabricator task. ** [[c:File:Co-Creating a Sustainable Future for the Toolforge Ecosystem.webm|Co-Creating a Sustainable Future for the Toolforge Ecosystem]] (40 mins) - a roundtable discussion for tool-maintainers, users, and supporters of Toolforge about how to make the platform sustainable and how to evaluate the tools available there. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/38|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W38"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:03, 17 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27460876 --> == Wikipedia translation of the week: 2024-39 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Independence Day (Albania)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Independence Day''' (Albanian: Dita e Pavarësisë) is a public holiday in Albania observed on 28 November. It commemorates the Albanian Declaration of Independence (from the Ottoman Empire), which was ratified by the All-Albanian Congress on 28 November 1912, establishing the state of Albania. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:29, 23 September 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27456350 --> == Tech News: 2024-39 == <section begin="technews-2024-W39"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/39|Translations]] are available. '''Weekly highlight''' * All wikis will be [[m:Special:MyLanguage/Tech/Server switch|read-only]] for a few minutes on Wednesday September 25 at [https://zonestamp.toolforge.org/1727276400 15:00 UTC]. Reading the wikis will not be interrupted, but editing will be paused. These twice-yearly processes allow WMF's site reliability engineering teams to remain prepared to keep the wikis functioning even in the event of a major interruption to one of our data centers. '''Updates for editors''' [[File:Add alt text from a halfsheet, with the article behind.png|thumb|A screenshot of the interface for the Alt Text suggested-edit feature]] * Editors who use the iOS Wikipedia app in Spanish, Portuguese, French, or Chinese, may see the [[mw:Special:MyLanguage/Wikimedia Apps/iOS Suggested edits project/Alt Text Experiment|Alt Text suggested-edit experiment]] after editing an article, or completing a suggested edit using "[[mw:Special:MyLanguage/Wikimedia Apps/iOS Suggested edits project#Hypothesis 2 Add an Image Suggested Edit|Add an image]]". Alt-text helps people with visual impairments to read Wikipedia articles. The team aims to learn if adding alt-text to images is a task that editors can be successful with. Please share any feedback on [[mw:Talk:Wikimedia Apps/iOS Suggested edits project/Alt Text Experiment|the discussion page]]. * The Codex color palette has been updated with new and revised colors for the MediaWiki user interfaces. The [[mw:Special:MyLanguage/Design System Team/Color/Design documentation#Updates|most noticeable changes]] for editors include updates for: dark mode colors for Links and for quiet Buttons (progressive and destructive), visited Link colors for both light and dark modes, and background colors for system-messages in both light and dark modes. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] It is now possible to include clickable wikilinks and external links inside code blocks. This includes links that are used within <code><nowiki><syntaxhighlight></nowiki></code> tags and on code pages (JavaScript, CSS, Scribunto and Sanitized CSS). Uses of template syntax <code><nowiki>{{…}}</nowiki></code> are also linked to the template page. Thanks to SD0001 for these improvements. [https://phabricator.wikimedia.org/T368166] * Two bugs were fixed in the [[m:Special:MyLanguage/Account vanishing|GlobalVanishRequest]] system by improving the logging and by removing an incorrect placeholder message. [https://phabricator.wikimedia.org/T370595][https://phabricator.wikimedia.org/T372223] * View all {{formatnum:25}} community-submitted {{PLURAL:25|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] From [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]]: ** The API now enables 5,000 on-demand API requests per month and twice-monthly HTML snapshots freely (gratis and libre). More information on the updates and also improvements to the software development kits (SDK) are explained on [https://enterprise.wikimedia.com/blog/enhanced-free-api/ the project's blog post]. While Wikimedia Enterprise APIs are designed for high-volume commercial reusers, this change enables many more community use-cases to be built on the service too. ** The Snapshot API (html dumps) have added beta Structured Contents endpoints ([https://enterprise.wikimedia.com/blog/structured-contents-snapshot-api/ blog post on that]) as well as released two beta datasets (English and French Wikipedia) from that endpoint to Hugging Face for public use and feedback ([https://enterprise.wikimedia.com/blog/hugging-face-dataset/ blog post on that]). These pre-parsed data sets enable new options for researchers, developers, and data scientists to use and study the content. '''In depth''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The Wikidata Query Service (WDQS) is used to get answers to questions using the Wikidata data set. As Wikidata grows, we had to make a major architectural change so that WDQS could remain performant. As part of the [[d:Special:MyLanguage/Wikidata:SPARQL query service/WDQS graph split|WDQS Graph Split project]], we have new SPARQL endpoints available for serving the "[https://query-scholarly.wikidata.org scholarly]" and "[https://query-main.wikidata.org main]" subgraphs of Wikidata. The [http://query.wikidata.org query.wikidata.org endpoint] will continue to serve the full Wikidata graph until March 2025. After this date, it will only serve the main graph. For more information, please see [[d:Special:MyLanguage/Wikidata:SPARQL query service/WDQS backend update/September 2024 scaling update|the announcement on Wikidata]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/39|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W39"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:37, 23 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27493779 --> == Wikipedia translation of the week: 2024-40 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Wildlife of Bahrain]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Birds in Al-Areen Wildlife Park.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The wildlife of the archipelago of Bahrain, is more varied than might be expected of this small group of islands in the Persian Gulf. Apart from a strip of the north and west of the main island, where crops are grown with irrigation, the land is arid. With a very hot dry summer, a mild winter, and brackish groundwater, the plants need adaptations in order to survive. Nevertheless, 196 species of higher plant have been recorded here, as well as about seventeen species of terrestrial mammals, many birds and reptiles, and many migratory birds visit the islands in autumn and spring. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:57, 30 September 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27456350 --> == Tech News: 2024-40 == <section begin="technews-2024-W40"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/40|Translations]] are available. '''Updates for editors''' * Readers of [[phab:T375401|42 more wikis]] can now use Dark Mode. If the option is not yet available for logged-out users of your wiki, this is likely because many templates do not yet display well in Dark Mode. Please use the [https://night-mode-checker.wmcloud.org/ night-mode-checker tool] if you are interested in helping to reduce the number of issues. The [[mw:Special:MyLanguage/Recommendations for night mode compatibility on Wikimedia wikis|recommendations page]] provides guidance on this. Dark Mode is enabled on additional wikis once per month. * Editors using the 2010 wikitext editor as their default can access features from the 2017 wikitext editor by adding <code dir=ltr>?veaction=editsource</code> to the URL. If you would like to enable the 2017 wikitext editor as your default, it can be set in [[Special:Preferences#mw-input-wpvisualeditor-newwikitext|your preferences]]. [https://phabricator.wikimedia.org/T239796] * For logged-out readers using the Vector 2022 skin, the "donate" link has been moved from a collapsible menu next to the content area into a more prominent top menu, next to "Create an account". This restores the link to the level of prominence it had in the Vector 2010 skin. [[mw:Readers/2024 Reader and Donor Experiences#Donor Experiences (Key Result WE 3.2 and the related hypotheses)|Learn more]] about the changes related to donor experiences. [https://phabricator.wikimedia.org/T373585] * The CampaignEvents extension provides tools for organizers to more easily manage events, communicate with participants, and promote their events on the wikis. The extension has been [[m:Special:MyLanguage/CampaignEvents/Deployment status|enabled]] on Arabic Wikipedia, Igbo Wikipedia, Swahili Wikipedia, and Meta-Wiki. [[w:zh:Wikipedia:互助客栈/其他#引進CampaignEvents擴充功能|Chinese Wikipedia has decided]] to enable the extension, and discussions on the extension are in progress [[w:es:Wikipedia:Votaciones/2024/Sobre la política de Organizadores de Eventos|on Spanish Wikipedia]] and [[d:Wikidata:Project chat#Enabling the CampaignEvents Extention on Wikidata|on Wikidata]]. To learn how to enable the extension on your wiki, you can visit [[m:Special:MyLanguage/CampaignEvents|the CampaignEvents page on Meta-Wiki]]. * View all {{formatnum:22}} community-submitted {{PLURAL:22|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Developers with an account on Wikitech-wiki should [[wikitech:Wikitech/SUL-migration|check if any action is required]] for their accounts. The wiki is being changed to use the single-user-login (SUL) system, and other configuration changes. This change will help reduce the overall complexity for the weekly software updates across all our wikis. '''In depth''' * The [[m:Special:MyLanguage/Tech/Server switch|server switch]] was completed successfully last week with a read-only time of [[wikitech:Switch Datacenter#Past Switches|only 2 minutes 46 seconds]]. This periodic process makes sure that engineers can switch data centers and keep all of the wikis available for readers, even if there are major technical issues. It also gives engineers a chance to do maintenance and upgrades on systems that normally run 24 hours a day, and often helps to reveal weaknesses in the infrastructure. The process involves dozens of software services and hundreds of hardware servers, and requires multiple teams working together. Work over the past few years has reduced the time from 17 minutes down to 2–3 minutes. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/66ZW7B2MG63AESQVTXDIFQBDBS766JGW/] '''Meetings and events''' * October 4–6: [[m:Special:MyLanguage/WikiIndaba conference 2024|WikiIndaba Conference's Hackathon]] in Johannesburg, South Africa * November 4–6: [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Fall 2024|MediaWiki Users and Developers Conference Fall 2024]] in Vienna, Austria '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/40|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W40"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:21, 30 September 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27530062 --> == Tech News: 2024-41 == <section begin="technews-2024-W41"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/41|Translations]] are available. '''Weekly highlight''' * Communities can now request installation of [[mw:Special:MyLanguage/Moderator Tools/Automoderator|Automoderator]] on their wiki. Automoderator is an automated anti-vandalism tool that reverts bad edits based on scores from the new "Revert Risk" machine learning model. You can [[mw:Special:MyLanguage/Extension:AutoModerator/Deploying|read details about the necessary steps]] for installation and configuration. [https://phabricator.wikimedia.org/T336934] '''Updates for editors''' * Translators in wikis where [[mw:Special:MyLanguage/Content translation/Section translation#Try the tool|the mobile experience of Content Translation is available]], can now customize their articles suggestion list from 41 filtering options when using the tool. This topic-based article suggestion feature makes it easy for translators to self-discover relevant articles based on their area of interest and translate them. You can [https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&active-list=suggestions try it with your mobile device]. [https://phabricator.wikimedia.org/T368422] * View all {{formatnum:12}} community-submitted {{PLURAL:12|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * It is now possible for <bdi lang="zxx" dir="ltr"><code><nowiki><syntaxhighlight></nowiki></code></bdi> code blocks to offer readers a "Copy" button if the <bdi lang="zxx" dir="ltr"><code><nowiki>copy=1</nowiki></code></bdi> attribute is [[mw:Special:MyLanguage/Extension:SyntaxHighlight#copy|set on the tag]]. Thanks to SD0001 for these improvements. [https://phabricator.wikimedia.org/T40932] * Customized copyright footer messages on all wikis will be updated. The new versions will use wikitext markup instead of requiring editing raw HTML. [https://phabricator.wikimedia.org/T375789] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Later this month, [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] will be rolled out on several pilot wikis. The final list of the wikis will be published in the second half of the month. If you maintain any tools, bots, or gadgets on [[phab:T376499|these 11 wikis]], and your software is using data about IP addresses or is available for logged-out users, please check if it needs to be updated to work with temporary accounts. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers|Guidance on how to update the code is available]]. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Rate limiting has been enabled for the code review tools [[Wikitech:Gerrit|Gerrit]] and [[Wikitech:GitLab|GitLab]] to address ongoing issues caused by malicious traffic and scraping. Clients that open too many concurrent connections will be restricted for a few minutes. This rate limiting is managed through [[Wikitech:nftables|nftables]] firewall rules. For more details, see Wikitech's pages on [[Wikitech:Firewall#Throttling with nftables|Firewall]], [[Wikitech:GitLab/Abuse and rate limiting|GitLab limits]] and [[Wikitech:Gerrit/Operations#Throttling IPs|Gerrit operations]]. * Five new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q49224|Komering]] ([[w:kge:|<code>w:kge:</code>]]) [https://phabricator.wikimedia.org/T374813] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q36096|Mooré]] ([[m:mos:|<code>m:mos:</code>]]) [https://phabricator.wikimedia.org/T374641] ** a {{int:project-localized-name-group-wiktionary}} in [[d:Q36213|Madurese]] ([[wikt:mad:|<code>wikt:mad:</code>]]) [https://phabricator.wikimedia.org/T374968] ** a {{int:project-localized-name-group-wikiquote}} in [[d:Q2501174|Gorontalo]] ([[q:gor:|<code>q:gor:</code>]]) [https://phabricator.wikimedia.org/T375088] ** a {{int:project-localized-name-group-wikinews}} in [[d:Q56482|Shan]] ([[n:shn:|<code>n:shn:</code>]]) [https://phabricator.wikimedia.org/T375430] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/41|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W41"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:43, 7 October 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27557422 --> == Wikipedia translation of the week: 2024-42 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Little Danes experiment]]'''<br /> <small>''([[:fa:آزمایش دانمارکی‌های کوچک]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Children play at a Danish Red Cross-run orphanage in Greenland.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''little Danes experiment''' was a 1951 Danish operation where 22 Greenlandic Inuit children were sent to Danish foster families in an attempt to re-educate them as "little Danes". While the children were all supposed to be orphans, most were not. Six children were adopted while in Denmark, and sixteen returned to Greenland, only to be placed in Danish-speaking orphanages and never live with their families again. Half of the children experienced mental health disturbances, and half of them died in young adulthood. The government of Denmark officially apologised in 2020, after several years of demands from Greenlandic officials. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:16, 14 October 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27572997 --> == Tech News: 2024-42 == <section begin="technews-2024-W42"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/42|Translations]] are available. '''Updates for editors''' * The Structured Discussion extension (also known as Flow) is starting to be removed. This extension is unmaintained and causes issues. It will be replaced by [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]], which is used on any regular talk page. [[mw:Special:MyLanguage/Structured Discussions/Deprecation#Deprecation timeline|A first set of wikis]] are being contacted. These wikis are invited to stop using Flow, and to move all Flow boards to sub-pages, as archives. At these wikis, a script will move all Flow pages that aren't a sub-page to a sub-page automatically, starting on 22 October 2024. On 28 October 2024, all Flow boards at these wikis will be set in read-only mode. [https://www.mediawiki.org/wiki/Structured_Discussions/Deprecation][https://phabricator.wikimedia.org/T370722] * WMF's Search Platform team is working on making it easier for readers to perform text searches in their language. A [[phab:T332342|change last week]] on over 30 languages makes it easier to find words with accents and other diacritics. This applies to both full-text search and to types of advanced search such as the <bdi lang="en" dir="ltr">''hastemplate''</bdi> and <bdi lang="en" dir="ltr">''incategory''</bdi> keywords. More technical details (including a few other minor search upgrades) are available. [https://www.mediawiki.org/wiki/User:TJones_%28WMF%29/Notes/Language_Analyzer_Harmonization_Notes#ASCII-folding/ICU-folding_%28T332342%29] * View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. For example, [[mw:Special:MyLanguage/Help:Edit check|EditCheck]] was installed at Russian Wikipedia, and fixes were made for some missing user interface styles. '''Updates for technical contributors''' * Editors who use the Toolforge tool [[toolforge:copyvios|Earwig's Copyright Violation Detector]] will now be required to log in with their Wikimedia account before running checks using the "search engine" option. This change is needed to help prevent external bots from misusing the system. Thanks to Chlod for these improvements. [https://en.wikipedia.org/wiki/Wikipedia_talk:New_pages_patrol/Reviewers#Authentication_is_now_required_for_search_engine_checks_on_Earwig's_Copyvio_Tool] * [[m:Special:MyLanguage/Phabricator|Phabricator]] users can create tickets and add comments on existing tickets via Email again. [[mw:Special:MyLanguage/Phabricator/Help#Using email|Sending email to Phabricator]] has been fixed. [https://phabricator.wikimedia.org/T356077] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Some HTML elements in the interface are now wrapped with a <code><nowiki><bdi></nowiki></code> element, to make our HTML output more aligned with Web standards. More changes like this will be coming in future weeks. This change might break some tools that rely on the previous HTML structure of the interface. Note that relying on the HTML structure of the interface is [[mw:Special:MyLanguage/Stable interface policy/Frontend#What is not stable?|not recommended]] and might break at any time. [https://phabricator.wikimedia.org/T375975] '''In depth''' * The latest monthly [[mw:Special:MyLanguage/MediaWiki Product Insights/Reports/September 2024|MediaWiki Product Insights newsletter]] is available. This edition includes: updates on Wikimedia's authentication system, research to simplify feature development in the MediaWiki platform, updates on Parser Unification and MathML rollout, and more. * The latest quarterly [[mw:Technical Community Newsletter/2024/October|Technical Community Newsletter]] is now available. This edition include: research about improving topic suggestions related to countries, improvements to PHPUnit tests, and more. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/42|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W42"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:22, 14 October 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27597254 --> == Wikipedia translation of the week: 2024-43 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Kharayeb]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Muharram 1Oth-Ashouraa 2007 in Kharayeb - panoramio.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Kharayeb''' (Arabic: الخرايب) is a historic town in the Sidon District in the South Governorate, Lebanon. The town is 77 km (48 mi) south of Beirut, and stands at an average altitude of 190 m (620 ft) above sea level. The town boasts a rich historical legacy, with archaeological excavations revealing a complex settlement history spanning from Prehistory to the Ottoman period. Notably, Kharayeb's origins can be traced back to the Persian period (539–330 BC), when it played a pivotal role in the region's agricultural and economic landscape, culminating in the construction of its Phoenician temple around the 6th century BC. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:38, 21 October 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27572997 --> == Tech News: 2024-43 == <section begin="technews-2024-W43"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/43|Translations]] are available. '''Weekly highlight''' * The Mobile Apps team has released an [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Navigation Refresh#Phase 1: Creating a user Profile Menu (T373714)|update]] to the iOS app's navigation, and it is now available in the latest App store version. The team added a new Profile menu that allows for easy access to editor features like Notifications and Watchlist from the Article view, and brings the "Donate" button into a more accessible place for users who are reading an article. This is the first phase of a larger planned [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Navigation Refresh|navigation refresh]] to help the iOS app transition from a primarily reader-focused app, to an app that fully supports reading and editing. The Wikimedia Foundation has added more editing features and support for on-wiki communication based on volunteer requests in recent years. [[File:IOS App Navigation refresh first phase 05.png|thumb|iOS Wikipedia App's profile menu and contents]] '''Updates for editors''' * Wikipedia readers can now download a browser extension to experiment with some early ideas on potential features that recommend articles for further reading, automatically summarize articles, and improve search functionality. For more details and to stay updated, check out the Web team's [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments|Content Discovery Experiments page]] and [[mw:Special:MyLanguage/Newsletter:Web team's projects|subscribe to their newsletter]]. * Later this month, logged-out editors of [[phab:T376499|these 12 wikis]] will start to have [[mw:Special:Mylanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] created. The list may slightly change - some wikis may be removed but none will be added. Temporary account is a new [[mw:Special:MyLanguage/User account types|type of user account]]. It enhances the logged-out editors' privacy and makes it easier for community members to communicate with them. If you maintain any tools, bots, or gadgets on these 12 wikis, and your software is using data about IP addresses or is available for logged-out users, please check if it needs to be updated to work with temporary accounts. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers|Guidance on how to update the code is available]]. Read more about the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Updates|deployment plan across all wikis]]. * View all {{formatnum:33}} community-submitted {{PLURAL:33|task|tasks}} that were [[m:Tech/News/Recently resolved community tasks|resolved last week]]. For example, the [[w:nr:Main Page|South Ndebele]], [[w:rsk:Главни бок|Pannonian Rusyn]], [[w:ann:Uwu|Obolo]], [[w:iba:Lambar Keterubah|Iban]] and [[w:tdd:ᥞᥨᥝᥴ ᥘᥣᥲ ᥖᥥᥰ|Tai Nüa]] Wikipedia languages were created last week. [https://www.wikidata.org/wiki/Q36785][https://www.wikidata.org/wiki/Q35660][https://www.wikidata.org/wiki/Q36614][https://www.wikidata.org/wiki/Q33424][https://www.wikidata.org/wiki/Q36556] * It is now possible to create functions on Wikifunctions using Wikidata lexemes, through the new [[f:Z6005|Wikidata lexeme type]] launched last week. When you go to one of these functions, the user interface provides a lexeme selector that helps you pick a lexeme from Wikidata that matches the word you type. After hitting run, your selected lexeme is retrieved from Wikidata, transformed into a Wikidata lexeme type, and passed into the selected function. Read more about this in [[f:Special:MyLanguage/Wikifunctions:Status updates/2024-10-17#Function of the Week: select representation from lexeme|the latest Wikifunctions newsletter]]. '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Users of the Wikimedia sites can now format dates more easily in different languages with the new <code dir="ltr">{{[[mw:Special:MyLanguage/Help:Extension:ParserFunctions##timef|#timef]]:…}}</code> parser function. For example, <code dir="ltr"><nowiki>{{#timef:now|date|en}}</nowiki></code> will show as "<bdi lang="en" dir="ltr">{{#timef:now|date|en}}</bdi>". Previously, <code dir="ltr"><nowiki>{{#time:…}}</nowiki></code> could be used to format dates, but this required knowledge of the order of the time and date components and their intervening punctuation. <code dir="ltr">#timef</code> (or <code dir="ltr">#timefl</code> for local time) provides access to the standard date formats that MediaWiki uses in its user interface. This may help to simplify some templates on multi-lingual wikis like Commons and Meta. [https://phabricator.wikimedia.org/T223772][https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Extension:ParserFunctions##timef] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Commons and Meta users can now efficiently [[mw:Special:MyLanguage/Help:Magic words#Localization|retrieve the user's language]] using <code dir="ltr"><nowiki>{{USERLANGUAGE}}</nowiki></code> instead of using <code dir="ltr"><nowiki>{{int:lang}}</nowiki></code>. [https://phabricator.wikimedia.org/T4085] * The [[m:Special:MyLanguage/Product and Technology Advisory Council|Product and Tech Advisory Council]] (PTAC) now has its pilot members with representation across Africa, Asia, Europe, North America and South America. They will work to address the [[Special:MyLanguage/Movement Strategy/Initiatives/Technology Council|Movement Strategy's Technology Council]] initiative of having a co-defined and more resilient technological platform. [https://meta.wikimedia.org/wiki/Movement_Strategy/Initiatives/Technology_Council] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/32|Growth newsletter]] is available. It includes: an upcoming Newcomer Homepage Community Updates module, new Community Configuration options, and details on new projects. * The Wikimedia Foundation is [[mw:Special:MyLanguage/Wikimedia Security Team#CNA Partnership|now an official partner of the CVE program]], which is an international effort to catalog publicly disclosed cybersecurity vulnerabilities. This partnership will allow the Security Team to instantly publish [[w:en:Common Vulnerabilities and Exposures|common vulnerabilities and exposures]] (CVE) records that are affecting MediaWiki core, extensions, and skins, along with any other code the Foundation is a steward of. * The [[m:Special:MyLanguage/Community Wishlist|Community Wishlist]] is now [[m:Community Wishlist/Updates#October 16, 2024: Conversations Made Easier: Machine-Translated Wishes Are Here!|testing machine translations]] for Wishlist content. Volunteers can now read machine-translated versions of wishes and dive into discussions even before translators arrive to translate content. '''Meetings and events''' * 24 October - Wiki Education Speaker Series Webinar - [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/N4XTB4G55BUY3M3PNGUAKQWJ7A4UOPAK/ Open Source Tech: Building the Wiki Education Dashboard], featuring Wikimedia interns and a Web developer in the panel. * 20–22 December 2024 - [[m:Special:MyLanguage/Indic Wikimedia Hackathon Bhubaneswar 2024|Indic Wikimedia Hackathon Bhubaneswar 2024]] in Odisha, India. A hackathon for community members, including developers, designers and content editors, to build technical solutions that improve contributors' experiences. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/43|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W43"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:53, 21 October 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27634672 --> == Wikipedia translation of the week: 2024-44 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Christmas horror]]'''<br /> <small>''([[:es:Terror navideño]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Christmascarol1843 -- 169.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Christmas horror''' is a fiction genre and film genre that incorporates horror elements into a seasonal setting. It is popular in multiple countries. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:05, 28 October 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27647428 --> == Tech News: 2024-44 == <section begin="technews-2024-W44"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/44|Translations]] are available. '''Updates for editors''' * Later in November, the Charts extension will be deployed to the test wikis in order to help identify and fix any issue. A security review is underway to then enable deployment to pilot wikis for broader testing. You can read [[mw:Special:MyLanguage/Extension:Chart/Project/Updates#October 2024: Working towards production deployment|the October project update]] and see the [https://en.wikipedia.beta.wmflabs.org/wiki/Charts latest documentation and examples on Beta Wikipedia]. * View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, [[w:en:PediaPress|Pediapress.com]], an external service that creates books from Wikipedia, can now use [[mw:Special:MyLanguage/Wikimedia Maps|Wikimedia Maps]] to include existing pre-rendered infobox map images in their printed books on Wikipedia. [https://phabricator.wikimedia.org/T375761] '''Updates for technical contributors''' * Wikis can use [[:mw:Special:MyLanguage/Extension:GuidedTour|the Guided Tour extension]] to help newcomers understand how to edit. The Guided Tours extension now works with [[mw:Special:MyLanguage/Manual:Dark mode|dark mode]]. Guided Tour maintainers can check their tours to see that nothing looks odd. They can also set <code>emitTransitionOnStep</code> to <code>true</code> to fix an old bug. They can use the new flag <code>allowAutomaticBack</code> to avoid back-buttons they don't want. [https://phabricator.wikimedia.org/T73927#10241528] * Administrators in the Wikimedia projects who use the [[mw:Special:MyLanguage/Help:Extension:Nuke|Nuke Extension]] will notice that mass deletions done with this tool have the "Nuke" tag. This change will make reviewing and analyzing deletions performed with the tool easier. [https://phabricator.wikimedia.org/T366068] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/44|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W44"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:57, 28 October 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27668811 --> == Wikipedia translation of the week: 2024-45 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Placenta cake]]'''<br /> <small>''([[:simple:Placenta cake]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Bucharest, Greek pie-maker, 1880.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Placenta cake''' is a dish from ancient Greece and Rome consisting of many dough layers interspersed with a mixture of cheese and honey and flavored with bay leaves, baked and then covered in honey. The dessert is mentioned in classical texts such as the Greek poems of Archestratos and Antiphanes, as well as the De agri cultura of Cato the Elder. It is often seen as the predecessor of baklava and börek. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:16, 4 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27647428 --> == Tech News: 2024-45 == <section begin="technews-2024-W45"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/45|Translations]] are available. '''Updates for editors''' * Stewards can now make [[m:Special:MyLanguage/Global blocks|global account blocks]] cause global [[mw:Special:MyLanguage/Autoblock|autoblocks]]. This will assist stewards in preventing abuse from users who have been globally blocked. This includes preventing globally blocked temporary accounts from exiting their session or switching browsers to make subsequent edits for 24 hours. Previously, temporary accounts could exit their current session or switch browsers to continue editing. This is an anti-abuse tool improvement for the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|Temporary Accounts]] project. You can read more about the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Updates|progress on key features for temporary accounts]]. [https://phabricator.wikimedia.org/T368949] * Wikis that have the [[m:Special:MyLanguage/CampaignEvents/Deployment status|CampaignEvents extension enabled]] can now use the [[m:Special:MyLanguage/Campaigns/Foundation Product Team/Event list#October 29, 2024: Collaboration List launched|Collaboration List]] feature. This list provides a new, easy way for contributors to learn about WikiProjects on their wikis. Thanks to the Campaign team for this work that is part of [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2024-2025/Product %26 Technology OKRs#WE KRs|the 2024/25 annual plan]]. If you are interested in bringing the CampaignEvents extension to your wiki, you can [[m:Special:MyLanguage/CampaignEvents/Deployment status#How to Request the CampaignEvents Extension for your wiki|follow these steps]] or you can reach out to User:Udehb-WMF for help. * The text color for red links will be slightly changed later this week to improve their contrast in light mode. [https://phabricator.wikimedia.org/T370446] * View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, on multilingual wikis, users [[phab:T216368|can now]] hide translations from the WhatLinksHere special page. '''Updates for technical contributors''' * XML [[m:Special:MyLanguage/Data dumps|data dumps]] have been temporarily paused whilst a bug is investigated. [https://lists.wikimedia.org/hyperkitty/list/xmldatadumps-l@lists.wikimedia.org/message/BXWJDPO5QI2QMBCY7HO36ELDCRO6HRM4/] '''In depth''' * Temporary Accounts have been deployed to six wikis; thanks to the Trust and Safety Product team for [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|this work]], you can read about [[phab:T340001|the deployment plans]]. Beginning next week, Temporary Accounts will also be enabled on [[phab:T378336|seven other projects]]. If you are active on these wikis and need help migrating your tools, please reach out to [[m:User:Udehb-WMF|User:Udehb-WMF]] for assistance. * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2024/October|Language and Internationalization newsletter]] is available. It includes: New languages supported in translatewiki or in MediaWiki; New keyboard input methods for some languages; details about recent and upcoming meetings, and more. '''Meetings and events''' * [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Fall 2024|MediaWiki Users and Developers Conference Fall 2024]] is happening in Vienna, Austria and online from 4 to 6 November 2024. The conference will feature discussions around the usage of MediaWiki software by and within companies in different industries and will inspire and onboard new users. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/45|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W45"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:51, 4 November 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27693917 --> == Wikipedia translation of the week: 2024-46 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Trisomy 16]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Chromosome 16.svg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Trisomy 16''' is a chromosomal abnormality in which there are 3 copies of chromosome 16 rather than two. It is the most common trisomy leading to miscarriage and the second most common chromosomal cause of it, closely following X-chromosome monosomy. About 6% of miscarriages have trisomy 16. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:09, 11 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27708700 --> == Tech News: 2024-46 == <section begin="technews-2024-W46"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/46|Translations]] are available. '''Updates for editors''' * On wikis with the [[mw:Special:MyLanguage/Help:Extension:Translate|Translate extension]] enabled, users will notice that the FuzzyBot will now automatically create translated versions of categories used on translated pages. [https://phabricator.wikimedia.org/T285463] * View all {{formatnum:29}} community-submitted {{PLURAL:29|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the submitted task to use the [[mw:Special:MyLanguage/Extension:SecurePoll|SecurePoll extension]] for English Wikipedia's special [[w:en:Wikipedia:Administrator elections|administrator election]] was resolved on time. [https://phabricator.wikimedia.org/T371454] '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] In <code dir="ltr">[[mw:MediaWiki_1.44/wmf.2|1.44.0-wmf-2]]</code>, the logic of Wikibase function <code>getAllStatements</code> changed to behave like <code>getBestStatements</code>. Invoking the function now returns a copy of values which are immutable. [https://phabricator.wikimedia.org/T270851] * [https://en.wikipedia.org/api/rest_v1/ Wikimedia REST API] users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. The API will be rerouting some page content endpoints from RESTbase to the newer [[mw:Special:MyLanguage/API:REST API|MediaWiki REST API]] endpoints. The [[phab:T374683|impacted endpoints]] include getting page/revision metadata and rendered HTML content. These changes will be available on testwiki later this week, with other projects to follow. This change should not affect existing functionality, but active users of the impacted endpoints should verify behavior on testwiki, and raise any concerns on the related [[phab:T374683|Phabricator ticket]]. '''In depth''' * Admins and users of the Wikimedia projects [[mw:Special:MyLanguage/Moderator_Tools/Automoderator#Usage|where Automoderator is enabled]] can now monitor and evaluate important metrics related to Automoderator's actions. [https://superset.wmcloud.org/superset/dashboard/unified-automoderator-activity-dashboard/ This Superset dashboard] calculates and aggregates metrics about Automoderator's behaviour on the projects in which it is deployed. Thanks to the Moderator Tools team for this Dashboard; you can visit [[mw:Special:MyLanguage/Moderator Tools/Automoderator/Unified Activity Dashboard|the documentation page]] for more information about this work. [https://phabricator.wikimedia.org/T369488] '''Meetings and events''' * 21 November 2024 ([[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 8:00 UTC|8:00 UTC]] & [[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 16:00 UTC|16:00 UTC]]) - [[c:Commons:WMF support for Commons/Commons community calls|Community call]] with Wikimedia Commons volunteers and stakeholders to help prioritize support efforts for 2025-2026 Fiscal Year. The theme of this call is how content should be organised on Wikimedia Commons. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/46|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W46"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:08, 12 November 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27732268 --> == Wikipedia translation of the week: 2024-47 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Boana platanera]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Rana platanera - Boana platanera.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Boana platanera''''', commonly known as the banana tree dwelling frog, is a species of tree frog in the family Hylidae. It is distributed within Venezuela, Colombia, Panama, and Trinidad and Tobago. Boana platanera was described in 2021, and individuals of the species were previously classified as Boana crepitans or Boana xerophylla. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:53, 18 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27735014 --> == Tech News: 2024-47 == <section begin="technews-2024-W47"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/47|Translations]] are available. '''Updates for editors''' * Users of Wikimedia sites will now be warned when they create a [[mw:Special:MyLanguage/Help:Redirects|redirect]] to a page that doesn't exist. This will reduce the number of broken redirects to red links in our projects. [https://phabricator.wikimedia.org/T326057] * View all {{formatnum:42}} community-submitted {{PLURAL:42|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, [[mw:Special:MyLanguage/Manual:Pywikibot/Overview|Pywikibot]], which automates work on MediaWiki sites, was upgraded to 9.5.0 on Toolforge. [https://phabricator.wikimedia.org/T378676] '''Updates for technical contributors''' * On wikis that use the [[mw:Special:MyLanguage/Extension:FlaggedRevs|FlaggedRevs extension]], pages created or moved by users with the appropriate permissions are marked as flagged automatically. This feature has not been working recently, and changes fixing it should be deployed this week. Thanks to Daniel and Wargo for working on this. [https://phabricator.wikimedia.org/T379218][https://phabricator.wikimedia.org/T368380] '''In depth''' * There is a new [https://diff.wikimedia.org/2024/11/05/say-hi-to-temporary-accounts-easier-collaboration-with-logged-out-editors-with-better-privacy-protection Diff post] about Temporary Accounts, available in more than 15 languages. Read it to learn about what Temporary Accounts are, their impact on different groups of users, and the plan to introduce the change on all wikis. '''Meetings and events''' * Technical volunteers can now register for the [[mw:Special:MyLanguage/Wikimedia Hackathon 2025|2025 Wikimedia Hackathon]], which will take place in Istanbul, Turkey. [https://pretix.eu/wikimedia/hackathon2025/ Application for travel and accommodation scholarships] is open from '''November 12 to December 10 2024'''. The registration for the event will close in mid-April 2025. The Wikimedia Hackathon is an annual gathering that unites the global technical community to collaborate on existing projects and explore new ideas. * Join the [[C:Special:MyLanguage/Commons:WMF%20support%20for%20Commons/Commons%20community%20calls|Wikimedia Commons community calls]] this week to help prioritize support for Commons which will be planned for 2025–2026. The theme will be how content should be organised on Wikimedia Commons. This is an opportunity for volunteers who work on different things to come together and talk about what matters for the future of the project. The calls will take place '''November 21, 2024, [[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 8:00 UTC|8:00 UTC]] and [[m:Special:MyLanguage/Event:Commons community discussion - 21 November 2024 16:00 UTC|16:00 UTC]]'''. * A [[mw:Special:MyLanguage/Wikimedia_Language_and_Product_Localization/Community meetings#29 November 2024|Language community meeting]] will take place '''November 29, 16:00 UTC''' to discuss updates and technical problem-solving. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/47|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W47"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:01, 19 November 2024 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27806858 --> == Wikipedia translation of the week: 2024-48 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Wang Su-bok]]'''<br /> <small>''([[:fa:وانگ سو بوک]])&#32;([[:ko:왕수복]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Wang Su-bok''' was a singer from North Korea, who was the most popular singer in Japanese-occupied Korea in 1935. She was credited as a ground-breaking female artist, whose work led the way for the modern K-pop phenomenon. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:57, 25 November 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27846897 --> == Tech News: 2024-48 == <section begin="technews-2024-W48"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/48|Translations]] are available. '''Updates for editors''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] A new version of the standard wikitext editor-mode [[mw:Special:MyLanguage/Extension:CodeMirror|syntax highlighter]] will be available as a [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] later this week. This brings many new features and bug fixes, including right-to-left support, [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Template folding|template folding]], [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Autocompletion|autocompletion]], and an improved search panel. You can learn more on the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|help page]]. * The 2010 wikitext editor now supports common keyboard shortcuts such <bdi lang="zxx" dir="ltr"><code>Ctrl</code>+<code>B</code></bdi> for bold and <bdi lang="zxx" dir="ltr"><code>Ctrl</code>+<code>I</code></bdi> for italics. A full [[mw:Help:Extension:WikiEditor#Keyboard shortcuts|list of all six shortcuts]] is available. Thanks to SD0001 for this improvement. [https://phabricator.wikimedia.org/T62928] * Starting November 28, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: <bdi>bswiki</bdi>{{int:comma-separator/en}}<bdi>elwiki</bdi>{{int:comma-separator/en}}<bdi>euwiki</bdi>{{int:comma-separator/en}}<bdi>fawiki</bdi>{{int:comma-separator/en}}<bdi>fiwiki</bdi>{{int:comma-separator/en}}<bdi>frwikiquote</bdi>{{int:comma-separator/en}}<bdi>frwikisource</bdi>{{int:comma-separator/en}}<bdi>frwikiversity</bdi>{{int:comma-separator/en}}<bdi>frwikivoyage</bdi>{{int:comma-separator/en}}<bdi>idwiki</bdi>{{int:comma-separator/en}}<bdi>lvwiki</bdi>{{int:comma-separator/en}}<bdi>plwiki</bdi>{{int:comma-separator/en}}<bdi>ptwiki</bdi>{{int:comma-separator/en}}<bdi>urwiki</bdi>{{int:comma-separator/en}}<bdi>viwikisource</bdi>{{int:comma-separator/en}}<bdi>zhwikisource</bdi>. This is done as part of [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|StructuredDiscussions deprecation work]]. If you need any assistance to archive your page in advance, please contact [[m:User:Trizek (WMF)|Trizek (WMF)]]. * View all {{formatnum:25}} community-submitted {{PLURAL:25|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a user creating a new AbuseFilter can now only set the filter to "protected" [[phab:T377765|if it includes a protected variable]]. '''Updates for technical contributors''' * The [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]], which can be used in JavaScript, CSS, JSON, and Lua pages, [[phab:T377663|now offers]] live autocompletion. Thanks to SD0001 for this improvement. The feature can be temporarily disabled on a page by pressing <bdi lang="zxx" dir="ltr"><code>Ctrl</code>+<code>,</code></bdi> and un-selecting "<bdi lang="en" dir="ltr">Live Autocompletion</bdi>". * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Tool-maintainers who use the Graphite system for tracking metrics, need to migrate to the newer Prometheus system. They can check [https://grafana.wikimedia.org/d/K6DEOo5Ik/grafana-graphite-datasource-utilization?orgId=1 this dashboard] and the list in the Description of the [[phab:T350592|task T350592]] to see if their tools are listed, and they should claim metrics and dashboards connected to their tools. They can then disable or migrate all existing metrics by following the instructions in the task. The Graphite service will become read-only in April. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/KLUV4IOLRYXPQFWD6WKKJUHMWE77BMSZ/] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The [[mw:Special:MyLanguage/NewPP parser report|New PreProcessor parser performance report]] has been fixed to give an accurate count for the number of Wikibase entities accessed. It had previously been resetting after 400 entities. [https://phabricator.wikimedia.org/T279069] '''Meetings and events''' * A [[mw:Special:MyLanguage/Wikimedia_Language_and_Product_Localization/Community meetings#29 November 2024|Language community meeting]] will take place November 29 at [https://zonestamp.toolforge.org/1732896000 16:00 UTC]. There will be presentations on topics like developing language keyboards, the creation of the Mooré Wikipedia, the language support track at [[m:Wiki Indaba|Wiki Indaba]], and a report from the Wayuunaiki community on their experiences with the Incubator and as a new community over the last 3 years. This meeting will be in English and will also have Spanish interpretation. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/48|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W48"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:42, 25 November 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27847039 --> == Wikipedia translation of the week: 2024-49 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Storm Filomena]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Spain’s chilly blanket ESA22415247.jpeg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Storm Filomena''' was an extratropical cyclone in early January 2021 that was most notable for bringing unusually heavy snowfall to parts of Spain, with Madrid recording its heaviest snowfall in over a century, and with Portugal being hit less severely. The eighth named storm of the 2020–21 European windstorm season, Filomena formed over the Atlantic Ocean close to the Canary Islands on 7 January, subsequently taking a slow track north-eastwards towards the Iberian Peninsula and then eastwards across the Mediterranean Sea. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:48, 2 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27846897 --> == Tech News: 2024-49 == <section begin="technews-2024-W49"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/49|Translations]] are available. '''Updates for editors''' * Two new parser functions were added this week. The <code dir="ltr"><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic words#interwikilink|#interwikilink]]<nowiki>}}</nowiki></code> function adds an [[mw:Special:MyLanguage/Help:Links#Interwiki links|interwiki link]] and the <code dir="ltr"><nowiki>{{</nowiki>[[mw:Special:MyLanguage/Help:Magic words#interlanguagelink|#interlanguagelink]]<nowiki>}}</nowiki></code> function adds an [[mw:Special:MyLanguage/Help:Links#Interlanguage links|interlanguage link]]. These parser functions are useful on wikis where namespaces conflict with interwiki prefixes. For example, links beginning with <bdi lang="zxx" dir="ltr"><code>MOS:</code></bdi> on English Wikipedia [[phab:T363538|conflict with the <code>mos</code> language code prefix of Mooré Wikipedia]]. * Starting this week, Wikimedia wikis no longer support connections using old RSA-based HTTPS certificates, specifically rsa-2048. This change is to improve security for all users. Some older, unsupported browser or smartphone devices will be unable to connect; Instead, they will display a connectivity error. See the [[wikitech:HTTPS/Browser_Recommendations|HTTPS Browser Recommendations page]] for more-detailed information. All modern operating systems and browsers are always able to reach Wikimedia projects. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/CTYEHVNSXUD3NFAAMG3BLZVTVQWJXJAH/] * Starting December 16, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: <bdi>arwiki</bdi>{{int:comma-separator/en}}<bdi>cawiki</bdi>{{int:comma-separator/en}}<bdi>frwiki</bdi>{{int:comma-separator/en}}<bdi>mediawikiwiki</bdi>{{int:comma-separator/en}}<bdi>orwiki</bdi>{{int:comma-separator/en}}<bdi>wawiki</bdi>{{int:comma-separator/en}}<bdi>wawiktionary</bdi>{{int:comma-separator/en}}<bdi>wikidatawiki</bdi>{{int:comma-separator/en}}<bdi>zhwiki</bdi>. This is done as part of [[mw:Special:MyLanguage/Structured_Discussions/Deprecation|StructuredDiscussions deprecation work]]. If you need any assistance to archive your page in advance, please contact [[m:User:Trizek (WMF)|Trizek (WMF)]]. [https://phabricator.wikimedia.org/T380910] * This month the Chart extension was deployed to production and is now available on Commons and Testwiki. With the security review complete, pilot wiki deployment is expected to start in the first week of December. You can see a working version [[testwiki:Charts|on Testwiki]] and read [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|the November project update]] for more details. * View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug with the "Download as PDF" system was fixed. [https://phabricator.wikimedia.org/T376438] '''Updates for technical contributors''' * In late February, temporary accounts will be rolled out on at least 10 large wikis. This deployment will have a significant effect on the community-maintained code. This is about Toolforge tools, bots, gadgets, and user scripts that use IP address data or that are available for logged-out users. The Trust and Safety Product team wants to identify this code, monitor it, and assist in updating it ahead of the deployment to minimize disruption to workflows. The team asks technical editors and volunteer developers to help identify such tools by adding them to [[mw:Trust and Safety Product/Temporary Accounts/For developers/Impacted tools|this list]]. In addition, review the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/For developers|updated documentation]] to learn how to adjust the tools. Join the discussions on the [[mw:Talk:Trust and Safety Product/Temporary Accounts|project talk page]] or in the [[discord:channels/221049808784326656/1227616742340034722|dedicated thread]] on the [[w:Wikipedia:Discord|Wikimedia Community Discord server (in English)]] for support and to share feedback. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/49|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W49"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:23, 2 December 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27873992 --> == Wikipedia translation of the week: 2024-50 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Syrian literature]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Poem about Baybars page 1 from Hakawati book.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Syrian literature''' is modern fiction written or orally performed in Arabic by writers from Syria since the independence of the Syrian Arab Republic in 1946. It is part of the historically and geographically wider Arabic literature. The modern states of Syria, Lebanon, Jordan, Israel as well as the Palestinian autonomous areas only came into being in the mid-20th century. Therefore, Syrian literature has since been referred to by literary scholarship as the national literature of the Syrian Arab Republic, as well as the works created in Arabic by Syrian writers in the diaspora. This literature has been influenced by the country's political history, the literature of other Arabic-speaking countries and, especially in its early days, by French literature. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:59, 9 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27846897 --> == Tech News: 2024-50 == <section begin="technews-2024-W50"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/50|Translations]] are available. '''Weekly highlight''' * Technical documentation contributors can find updated resources, and new ways to connect with each other and the Wikimedia Technical Documentation Team, at the [[mw:Special:MyLanguage/Documentation|Documentation hub]] on MediaWiki.org. This page links to: resources for writing and improving documentation, a new <bdi lang="zxx" dir="ltr">#wikimedia-techdocs</bdi> IRC channel on libera.chat, a listing of past and upcoming documentation events, and ways to request a documentation consultation or review. If you have any feedback or ideas for improvements to the documentation ecosystem, please [[mw:Wikimedia Technical Documentation Team#Contact us|contact the Technical Documentation Team]]. '''Updates for editors''' [[File:Edit Check on Desktop.png|thumb|Layout change for the Edit Check feature]] * Later this week, [[mw:Special:MyLanguage/Edit check|Edit Check]] will be relocated to a sidebar on desktop. Edit check is the feature for new editors to help them follow policies and guidelines. This layout change creates space to present people with [[mw:Edit check#1 November 2024|new Checks]] that appear ''while'' they are typing. The [[mw:Special:MyLanguage/Edit check#Reference Check A/B Test|initial results]] show newcomers encountering Edit Check are 2.2 times more likely to publish a new content edit that includes a reference and is not reverted. * The Chart extension, which enables editors to create data visualizations, was successfully made available on MediaWiki.org and three pilot wikis (Italian, Swedish, and Hebrew Wikipedias). You can see a working examples [[testwiki:Charts|on Testwiki]] and read [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|the November project update]] for more details. * Translators in wikis where the [[mw:Special:MyLanguage/Content translation/Section translation#Try the tool|mobile experience of Content Translation is available]], can now discover articles in Wikiproject campaigns of their interest from the "[https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&campaign=specialcx&filter-type=automatic&filter-id=collections&active-list=suggestions&from=es&to=en All collection]" category in the articles suggestion feature. Wikiproject Campaign organizers can use this feature, to help translators to discover articles of interest, by adding the <code dir=ltr><nowiki><page-collection> </page-collection></nowiki></code> tag to their campaign article list page on Meta-wiki. This will make those articles discoverable in the Content Translation tool. For more detailed information on how to use the tool and tag, please refer to [[mw:Special:MyLanguage/Translation suggestions: Topic-based & Community-defined lists/How to use the features|the step-by-step guide]]. [https://phabricator.wikimedia.org/T378958] * The [[mw:Special:MyLanguage/Extension:Nuke|Nuke]] feature, which enables administrators to mass delete pages, now has a [[phab:T376379#10310998|multiselect filter for namespace selection]]. This enables users to select multiple specific namespaces, instead of only one or all, when fetching pages for deletion. * The Nuke feature also now [[phab:T364225#10371365|provides links]] to the userpage of the user whose pages were deleted, and to the pages which were not selected for deletion, after page deletions are queued. This enables easier follow-up admin-actions. Thanks to Chlod and the Moderator Tools team for both of these improvements. [https://phabricator.wikimedia.org/T364225#10371365] * The Editing Team is working on making it easier to populate citations from archive.org using the [[mw:Special:MyLanguage/Citoid/Enabling Citoid on your wiki|Citoid]] tool, the auto-filled citation generator. They are asking communities to add two parameters preemptively, <code dir=ltr>archiveUrl</code> and <code dir=ltr>archiveDate</code>, within the TemplateData for each citation template using Citoid. You can see an [https://en.wikipedia.org/w/index.php?title=Template%3ACite_web%2Fdoc&diff=1261320172&oldid=1260788022 example of a change in a template], and a [https://global-search.toolforge.org/?namespaces=10&q=%5C%22citoid%5C%22%3A%20%5C%7B&regex=1&title= list of all relevant templates]. [https://phabricator.wikimedia.org/T374831] * One new wiki has been created: a {{int:project-localized-name-group-wikivoyage}} in [[d:Q9240|Indonesian]] ([[voy:id:|<code>voy:id:</code>]]) [https://phabricator.wikimedia.org/T380726] * Last week, all wikis had problems serving pages to logged-in users and some logged-out users for 30–45 minutes. This was caused by a database problem, and investigation is ongoing. [https://www.wikimediastatus.net/incidents/3g2ckc7bp6l9] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:19}} community-submitted {{PLURAL:19|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug in the [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add Link]] feature has been fixed. Previously, the list of sections which are excluded from Add Link was partially ignored in certain cases. [https://phabricator.wikimedia.org/T380455][https://phabricator.wikimedia.org/T380329] '''Updates for technical contributors''' * [[mw:Special:MyLanguage/Codex|Codex]], the design system for Wikimedia, now has an early-stage [[gitiles:design/codex-php|implementation in PHP]]. It is available for general use in MediaWiki extensions and Toolforge apps through [https://packagist.org/packages/wikimedia/codex Composer], with use in MediaWiki core coming soon. More information is available in [[wmdoc:design-codex-php/main/index.html|the documentation]]. Thanks to Doğu for the inspiration and many contributions to the library. [https://phabricator.wikimedia.org/T379662] * [https://en.wikipedia.org/api/rest_v1/ Wikimedia REST API] users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. On December 4, the MediaWiki Interfaces team began rerouting page/revision metadata and rendered HTML content endpoints on [[testwiki:|testwiki]] from RESTbase to comparable MediaWiki REST API endpoints. The team encourages active users of these endpoints to verify their tool's behavior on testwiki and raise any concerns on the related [[phab:T374683|Phabricator ticket]] before the end of the year, as they intend to roll out the same change across all Wikimedia projects in early January. These changes are part of the work to replace the outdated [[mw:RESTBase/deprecation|RESTBase]] system. * The [https://wikimediafoundation.limesurvey.net/986172 2024 Developer Satisfaction Survey] is seeking the opinions of the Wikimedia developer community. Please take the survey if you have any role in developing software for the Wikimedia ecosystem. The survey is open until 3 January 2025, and has an associated [[foundation:Legal:Developer Satisfaction Survey 2024 Privacy Statement|privacy statement]]. * There is no new MediaWiki version this week. [https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar] '''Meetings and events''' * The next meeting in the series of [[c:Commons:WMF support for Commons/Commons community calls|Wikimedia Foundation discussions with the Wikimedia Commons community]] will take place on [[m:Event:Commons community discussion - 12 December 2024 08:00 UTC|December 12 at 8:00 UTC]] and [[m:Event:Commons community discussion - 12_December 2024 16:00 UTC|at 16:00 UTC]]. The topic of this call is new media and new contributors. Contributors from all wikis are welcome to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/50|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W50"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:16, 9 December 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27919424 --> == Wikipedia translation of the week: 2024-51 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Mars ocean theory]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:AncientMars.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Mars ocean theory''' states that nearly a third of the surface of Mars was covered by an ocean of liquid water early in the planet's geologic history. This primordial ocean, dubbed Paleo-Ocean or Oceanus Borealis (/oʊˈsiːənəs ˌbɒriˈælɪs/ oh-SEE-ə-nəs BORR-ee-AL-iss), would have filled the basin Vastitas Borealis in the northern hemisphere, a region that lies 4–5 km (2.5–3 miles) below the mean planetary elevation, at a time period of approximately 4.1–3.8 billion years ago. Evidence for this ocean includes geographic features resembling ancient shorelines, and the chemical properties of the Martian soil and atmosphere <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:44, 16 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27933909 --> == Tech News: 2024-51 == <section begin="technews-2024-W51"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2024/51|Translations]] are available. '''Weekly highlight''' * Interested in improving event management on your home wiki? The [[m:Special:MyLanguage/CampaignEvents|CampaignEvents extension]] offers organizers features like event registration management, event/wikiproject promotion, finding potential participants, and more - all directly on-wiki. If you are an organizer or think your community would benefit from this extension, start a discussion to enable it on your wiki today. To learn more about how to enable this extension on your wiki, visit the [[m:CampaignEvents/Deployment status#How to Request the CampaignEvents Extension for your wiki|deployment status page]]. '''Updates for editors''' * Users of the iOS Wikipedia App in Italy and Mexico on the Italian, Spanish, and English Wikipedias, can see a [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Personalized Wikipedia Year in Review|personalized Year in Review]] with insights based on their reading and editing history. * Users of the Android Wikipedia App in Sub-Saharan Africa and South Asia can see the new [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/Rabbit Holes|Rabbit Holes]] feature. This feature shows a suggested search term in the Search bar based on the current article being viewed, and a suggested reading list generated from the user’s last two visited articles. * The [[m:Special:MyLanguage/Global reminder bot|global reminder bot]] is now active and running on nearly 800 wikis. This service reminds most users holding temporary rights when they are about to expire, so that they can renew should they want to. See [[m:Global reminder bot/Technical details|the technical details page]] for more information. * The next issue of Tech News will be sent out on 13 January 2025 because of the end of year holidays. Thank you to all of the translators, and people who submitted content or feedback, this year. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was [[phab:T374988|fixed]] in the Android Wikipedia App which had caused translatable SVG images to show the wrong language when they were tapped. '''Updates for technical contributors''' * There is no new MediaWiki version next week. The next deployments will start on 14 January. [https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar/2025] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2024/51|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2024-W51"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:25, 16 December 2024 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=27942374 --> == Wikipedia translation of the week: 2024-52 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:2023 Slovenia floods]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Sava v Tacnu 4. avgusta ob 16h.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> In August 2023, major floods occurred in large part of Slovenia and neighbouring areas of Austria and Croatia due to heavy rain. Amongst others, the level of rivers Sava, Mur and Drava was exceptionally high. Several settlements and transport links in Slovene Littoral, Upper Carniola and Slovenian Carinthia were flooded. Due to the amount of rain, the streams in Idrija, Cerkno and Škofja Loka Hills overflowed. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:55, 23 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=27933909 --> == Wikipedia translation of the week: 2025-01 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Uganda Railways Corporation]]'''<br /> <small>''([[:de:Schienenverkehr in Uganda]])&#32;([[:no:Uganda Railways Corporation]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:9620 mit Güterzug.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Uganda Railways Corporation''' (URC) is the parastatal railway of Uganda. It was formed after the breakup of the East African Railways Corporation (EARC) in 1977 when it took over the Ugandan part of the East African railways. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:37, 30 December 2024 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28019313 --> == Wikipedia translation of the week: 2025-02 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Internment of Japanese Canadians]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Japanese road camp.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> From 1942 to 1949, Canada forcibly relocated and incarcerated over 22,000 Japanese Canadians—comprising over 90% of the total Japanese Canadian population—from British Columbia in the name of "national security". The majority were Canadian citizens by birth and were targeted based on their ancestry. This decision followed the events of the Japanese Empire's war in the Pacific against the Western Allies, such as the invasion of Hong Kong, the attack on Pearl Harbor in Hawaii, and the Fall of Singapore which led to the Canadian declaration of war on Japan during World War II. Similar to the actions taken against Japanese Americans in neighbouring United States, this forced relocation subjected many Japanese Canadians to government-enforced curfews and interrogations, job and property losses, and forced repatriation to Japan <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:56, 6 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28070038 --> == Wikipedia translation of the week: 2025-03 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Christmas seals]]'''<br /> <small>''([[:no:Julemerke]])&#32;([[:ru:Рождественская виньетка]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:1915 US Christmas Seal.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Christmas seals''' are adhesive labels that are similar in appearance to postage stamps that are sold then affixed to mail during the Christmas season to raise funds and awareness for charitable programs. Christmas seals have become particularly associated with lung diseases such as tuberculosis, and with child welfare in general. They were first issued in Denmark beginning in 1904, with Sweden and Iceland following with issues that same year. Thereafter the use of Christmas seals proved to be popular and spread quickly around the world, with 130 countries producing their own issues. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:24, 13 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28086717 --> == Tech News: 2025-03 == <section begin="technews-2025-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/03|Translations]] are available. '''Weekly highlight''' * The Single User Login system is being updated over the next few months. This is the system which allows users to fill out the login form on one Wikimedia site and get logged in on all others at the same time. It needs to be updated because of the ways that browsers are increasingly restricting cross-domain cookies. To accommodate these restrictions, login and account creation pages will move to a central domain, but it will still appear to the user as if they are on the originating wiki. The updated code will be enabled this week for users on test wikis. This change is planned to roll out to all users during February and March. See [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3#Deployment|the SUL3 project page]] for more details and a timeline. '''Updates for editors''' * On wikis with [[mw:Special:MyLanguage/Extension:PageAssessments|PageAssessments]] installed, you can now [[mw:Special:MyLanguage/Extension:PageAssessments#Search|filter search results]] to pages in a given WikiProject by using the <code dir=ltr>inproject:</code> keyword. (These wikis: {{int:project-localized-name-arwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-enwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-enwikivoyage/en}}{{int:comma-separator/en}}{{int:project-localized-name-frwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-huwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-newiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zhwiki/en}}) [https://phabricator.wikimedia.org/T378868] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia}} in [[d:Q34129|Tigre]] ([[w:tig:|<code>w:tig:</code>]]) [https://phabricator.wikimedia.org/T381377] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:35}} community-submitted {{PLURAL:35|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a bug with updating a user's edit-count after making a rollback edit, which is now fixed. [https://phabricator.wikimedia.org/T382592] '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Wikimedia REST API users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. Starting the week of January 13, we will begin rerouting [[phab:T374683|some page content endpoints]] from RESTbase to the newer MediaWiki REST API endpoints for all wiki projects. This change was previously available on testwiki and should not affect existing functionality, but active users of the impacted endpoints may raise issues directly to the [[phab:project/view/6931/|MediaWiki Interfaces Team]] in Phabricator if they arise. * Toolforge tool maintainers can now share their feedback on Toolforge UI, an initiative to provide a web platform that allows creating and managing Toolforge tools through a graphic interface, in addition to existing command-line workflows. This project aims to streamline active maintainers’ tasks, as well as make registration and deployment processes more accessible for new tool creators. The initiative is still at a very early stage, and the Cloud Services team is in the process of collecting feedback from the Toolforge community to help shape the solution to their needs. [[wikitech:Wikimedia Cloud Services team/EnhancementProposals/Toolforge UI|Read more and share your thoughts about Toolforge UI]]. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] For tool and library developers who use the OAuth system: The identity endpoint used for [[mw:Special:MyLanguage/OAuth/For Developers#Identifying the user|OAuth 1]] and [[mw:Special:MyLanguage/OAuth/For Developers#Identifying the user 2|OAuth 2]] returned a JSON object with an integer in its <code>sub</code> field, which was incorrect (the field must always be a string). This has been fixed; the fix will be deployed to Wikimedia wikis on the week of January 13. [https://phabricator.wikimedia.org/T382139] * Many wikis currently use [[:mw:Parsoid/Parser Unification/Cite CSS|Cite CSS]] to render custom footnote markers in Parsoid output. Starting January 20 these rules will be disabled, but the developers ask you to ''not'' clean up your <bdi lang="en" dir="ltr">[[MediaWiki:Common.css]]</bdi> until February 20 to avoid issues during the migration. Your wikis might experience some small changes to footnote markers in Visual Editor and when using experimental Parsoid read mode, but if there are changes these are expected to bring the rendering in line with the legacy parser output. [https://phabricator.wikimedia.org/T370027] '''Meetings and events''' * The next meeting in the series of [[c:Special:MyLanguage/Commons:WMF support for Commons/Commons community calls|Wikimedia Foundation Community Conversations with the Wikimedia Commons community]] will take place on [[m:Special:MyLanguage/Event:Commons community discussion - 15 January 2025 08:00 UTC|January 15 at 8:00 UTC]] and [[m:Special:MyLanguage/Event:Commons community discussion - 15 January 2025 16:00 UTC|at 16:00 UTC]]. The topic of this call is defining the priorities in tool investment for Commons. Contributors from all wikis, especially users who are maintaining tools for Commons, are welcome to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:42, 14 January 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28048614 --> == Wikipedia translation of the week: 2025-04 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:2010 Nagorno-Karabakh clashes]]'''<br /> <small>''([[:it:Scontri del Nagorno Karabakh del 2010]])&#32;([[:tr:2010 Dağlık Karabağ çatışmaları]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''2010 Nahorno karabakh war''' were a series of exchanges of gunfire that took place on February 18 on the line of contact dividing Azerbaijani and the Karabakh Armenian military forces. Azerbaijan accused the Armenian forces of firing on the Azerbaijani positions near Tap Qaraqoyunlu, Qızıloba, Qapanlı, Yusifcanlı and Cavahirli villages, as well as in uplands of Agdam Rayon with small arms fire including snipers. As a result, three Azerbaijani soldiers were killed and one wounded. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:20, 20 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28099770 --> == Tech News: 2025-04 == <section begin="technews-2025-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/04|Translations]] are available. '''Updates for editors''' * Administrators can mass-delete multiple pages created by a user or IP address using [[mw:Special:MyLanguage/Extension:Nuke|Extension:Nuke]]. It previously only allowed deletion of pages created in the last 30 days. It can now delete pages from the last 90 days, provided it is targeting a specific user or IP address. [https://phabricator.wikimedia.org/T380846] * On [[phab:P72148|wikis that use]] the [[mw:Special:MyLanguage/Help:Patrolled edits|Patrolled edits]] feature, when the rollback feature is used to revert an unpatrolled page revision, that revision will now be marked as "manually patrolled" instead of "autopatrolled", which is more accurate. Some editors that use [[mw:Special:MyLanguage/Help:New filters for edit review/Filtering|filters]] on Recent Changes may need to update their filter settings. [https://phabricator.wikimedia.org/T302140] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the Visual Editor's "Insert link" feature did not always suggest existing pages properly when an editor started typing, which has now been [[phab:T383497|fixed]]. '''Updates for technical contributors''' * The Structured Discussion extension (also known as Flow) is being progressively removed from the wikis. This extension is unmaintained and causes issues. It will be replaced by [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]], which is used on any regular talk page. [[mw:Special:MyLanguage/Structured Discussions/Deprecation#Deprecation timeline|The last group of wikis]] ({{int:project-localized-name-cawikiquote/en}}{{int:comma-separator/en}}{{int:project-localized-name-fiwikimedia/en}}{{int:comma-separator/en}}{{int:project-localized-name-gomwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kabwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ptwikibooks/en}}{{int:comma-separator/en}}{{int:project-localized-name-sewikimedia/en}}) will soon be contacted. If you have questions about this process, please ping [[m:User:Trizek (WMF)|Trizek (WMF)]] at your wiki. [https://phabricator.wikimedia.org/T380912] * The latest quarterly [[mw:Technical_Community_Newsletter/2025/January|Technical Community Newsletter]] is now available. This edition includes: updates about services from the Data Platform Engineering teams, information about Codex from the Design System team, and more. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:37, 21 January 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28129769 --> == Wikipedia translation of the week: 2025-05 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Jinnah's birthday]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Yorkstatue.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Jinnah's Birthday''', officially Quaid-e-Azam Day and sometimes known as Quaid Day, is a public holiday in Pakistan observed annually on 25 December to celebrate the birthday of the founder of Pakistan, Muhammad Ali Jinnah, known as Quaid-i-Azam ("Great Leader"). A major holiday, commemorations for Jinnah began during his lifetime in 1942, and have continued ever since. The event is primarily observed by the government and the citizens of the country where the national flag is hoisted at major architectural structures such as private and public buildings, particularly at the top of Quaid-e-Azam House in Karachi. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:30, 27 January 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28156501 --> == Tech News: 2025-05 == <section begin="technews-2025-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/05|Translations]] are available. '''Weekly highlight''' * Patrollers and admins - what information or context about edits or users could help you to make patroller or admin decisions more quickly or easily? The Wikimedia Foundation wants to hear from you to help guide its upcoming annual plan. Please consider sharing your thoughts on this and [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Product & Technology OKRs|13 other questions]] to shape the technical direction for next year. '''Updates for editors''' * iOS Wikipedia App users worldwide can now access a [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Personalized Wikipedia Year in Review/How your data is used|personalized Year in Review]] feature, which provides insights based on their reading and editing history on Wikipedia. This project is part of a broader effort to help welcome new readers as they discover and interact with encyclopedic content. * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] Edit patrollers now have a new feature available that can highlight potentially problematic new pages. When a page is created with the same title as a page which was previously deleted, a tag ('Recreated') will now be added, which users can filter for in [[{{#special:RecentChanges}}]] and [[{{#special:NewPages}}]]. [https://phabricator.wikimedia.org/T56145] * Later this week, there will be a new warning for editors if they attempt to create a redirect that links to another redirect (a [[mw:Special:MyLanguage/Help:Redirects#Double redirects|double redirect]]). The feature will recommend that they link directly to the second redirect's target page. Thanks to the user SomeRandomDeveloper for this improvement. [https://phabricator.wikimedia.org/T326056] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Wikimedia wikis allow [[w:en:WebAuthn|WebAuthn]]-based second factor checks (such as hardware tokens) during login, but the feature is [[m:Community Wishlist Survey 2023/Miscellaneous/Fix security key (WebAuthn) support|fragile]] and has very few users. The MediaWiki Platform team is temporarily disabling adding new WebAuthn keys, to avoid interfering with the rollout of [[mw:MediaWiki Platform Team/SUL3|SUL3]] (single user login version 3). Existing keys are unaffected. [https://phabricator.wikimedia.org/T378402] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * For developers that use the [[wikitech:Data Platform/Data Lake/Edits/MediaWiki history dumps|MediaWiki History dumps]]: The Data Platform Engineering team has added a couple of new fields to these dumps, to support the [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|Temporary Accounts]] initiative. If you maintain software that reads those dumps, please review your code and the updated documentation, since the order of the fields in the row will change. There will also be one field rename: in the <bdi lang="zxx" dir="ltr"><code>mediawiki_user_history</code></bdi> dump, the <bdi lang="zxx" dir="ltr"><code>anonymous</code></bdi> field will be renamed to <bdi lang="zxx" dir="ltr"><code>is_anonymous</code></bdi>. The changes will take effect with the next release of the dumps in February. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/LKMFDS62TXGDN6L56F4ABXYLN7CSCQDI/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:15, 27 January 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28149374 --> == Wikipedia translation of the week: 2025-06 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:French conquest of Corsica]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Bataille de Ponte Novu.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''French conquest of Corsica''' was a successful expedition by French forces of the Kingdom of France under Comte de Vaux, against Corsican forces under Pasquale Paoli of the Corsican Republic. The expedition was launched in May 1768, in the aftermath of the Seven Years' War. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:20, 3 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28200320 --> == Tech News: 2025-06 == <section begin="technews-2025-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/06|Translations]] are available. '''Updates for editors''' * Editors who use the "Special characters" editing-toolbar menu can now see the 32 special characters you have used most recently, across editing sessions on that wiki. This change should help make it easier to find the characters you use most often. The feature is in both the 2010 wikitext editor and VisualEditor. [https://phabricator.wikimedia.org/T110722] * Editors using the 2010 wikitext editor can now create sublists with correct indentation by selecting the line(s) you want to indent and then clicking the toolbar buttons.[https://phabricator.wikimedia.org/T380438] You can now also insert <code><nowiki><code></nowiki></code> tags using a new toolbar button.[https://phabricator.wikimedia.org/T383010] Thanks to user stjn for these improvements. * Help is needed to ensure the [[mw:Special:MyLanguage/Citoid/Enabling Citoid on your wiki|citation generator]] works properly on each wiki. ** (1) Administrators should update the local versions of the page <code dir=ltr>MediaWiki:Citoid-template-type-map.json</code> to include entries for <code dir=ltr>preprint</code>, <code dir=ltr>standard</code>, and <code dir=ltr>dataset</code>; Here are example diffs to replicate [https://en.wikipedia.org/w/index.php?title=MediaWiki%3ACitoid-template-type-map.json&diff=1189164774&oldid=1165783565 for 'preprint'] and [https://en.wikipedia.org/w/index.php?title=MediaWiki%3ACitoid-template-type-map.json&diff=1270832208&oldid=1270828390 for 'standard' and 'dataset']. ** (2.1) If the citoid map in the citation template used for these types of references is missing, [[mediawikiwiki:Citoid/Enabling Citoid on your wiki#Step 2.a: Create a 'citoid' maps value for each citation template|one will need to be added]]. (2.2) If the citoid map does exist, the TemplateData will need to be updated to include new field names. Here are example updates [https://en.wikipedia.org/w/index.php?title=Template%3ACitation%2Fdoc&diff=1270829051&oldid=1262470053 for 'preprint'] and [https://en.wikipedia.org/w/index.php?title=Template%3ACitation%2Fdoc&diff=1270831369&oldid=1270829480 for 'standard' and 'dataset']. The new fields that may need to be supported are <code dir=ltr>archiveID</code>, <code dir=ltr>identifier</code>, <code dir=ltr>repository</code>, <code dir=ltr>organization</code>, <code dir=ltr>repositoryLocation</code>, <code dir=ltr>committee</code>, and <code dir=ltr>versionNumber</code>. [https://phabricator.wikimedia.org/T383666] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q15637215|Central Kanuri]] ([[w:knc:|<code>w:knc:</code>]]) [https://phabricator.wikimedia.org/T385181] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the [[mediawikiwiki:Special:MyLanguage/Help:Extension:Wikisource/Wikimedia OCR|OCR (optical character recognition) tool]] used for Wikisource now supports a new language, Church Slavonic. [https://phabricator.wikimedia.org/T384782] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:09, 4 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28203495 --> == Wikipedia translation of the week: 2025-07 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Assassination of Spencer Perceval]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:PercevalShooting.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> On 11 May 1812, at about 5:15 pm, Spencer Perceval, the prime minister of the United Kingdom of Great Britain and Ireland, was shot dead in the lobby of the House of Commons by John Bellingham, a Liverpool merchant with a grievance against the government. Bellingham was detained; four days after the murder, he was tried, convicted and sentenced to death. He was hanged at Newgate Prison on 18 May, one week after the assassination and one month before the start of the War of 1812. Perceval remains the sole British prime minister to have been assassinated. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 10 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28200320 --> == Tech News: 2025-07 == <section begin="technews-2025-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/07|Translations]] are available. '''Weekly highlight''' * The Product and Technology Advisory Council (PTAC) has published [[m:Special:MyLanguage/Product and Technology Advisory Council/February 2025 draft PTAC recommendation for feedback|a draft of their recommendations]] for the Wikimedia Foundation's Product and Technology department. They have recommended focusing on [[m:Special:MyLanguage/Product and Technology Advisory Council/February 2025 draft PTAC recommendation for feedback/Mobile experiences|mobile experiences]], particularly contributions. They request community [[m:Talk:Product and Technology Advisory Council/February 2025 draft PTAC recommendation for feedback|feedback at the talk page]] by 21 February. '''Updates for editors''' * The "Special pages" portlet link will be moved from the "Toolbox" into the "Navigation" section of the main menu's sidebar by default. This change is because the Toolbox is intended for tools relating to the current page, not tools relating to the site, so the link will be more logically and consistently located. To modify this behavior and update CSS styling, administrators can follow the instructions at [[phab:T385346|T385346]]. [https://phabricator.wikimedia.org/T333211] * As part of this year's work around improving the ways readers discover content on the wikis, the Web team will be running an experiment with a small number of readers that displays some suggestions for related or interesting articles within the search bar. Please check out [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments#Experiment 1: Display article recommendations in more prominent locations, search|the project page]] for more information. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Template editors who use TemplateStyles can now customize output for users with specific accessibility needs by using accessibility related media queries (<code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion prefers-reduced-motion]</code>, <code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-transparency prefers-reduced-transparency]</code>, <code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-contrast prefers-contrast]</code>, and <code dir=ltr>[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/forced-colors forced-colors]</code>). Thanks to user Bawolff for these improvements. [https://phabricator.wikimedia.org/T384175] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:22}} community-submitted {{PLURAL:22|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the global blocks log will now be shown directly on the {{#special:CentralAuth}} page, similarly to global locks, to simplify the workflows for stewards. [https://phabricator.wikimedia.org/T377024] '''Updates for technical contributors''' * Wikidata [[d:Special:MyLanguage/Help:Default values for labels and aliases|now supports a special language as a "default for all languages"]] for labels and aliases. This is to avoid excessive duplication of the same information across many languages. If your Wikidata queries use labels, you may need to update them as some existing labels are getting removed. [https://phabricator.wikimedia.org/T312511] * The function <code dir="ltr">getDescription</code> was invoked on every Wiki page read and accounts for ~2.5% of a page's total load time. The calculated value will now be cached, reducing load on Wikimedia servers. [https://phabricator.wikimedia.org/T383660] * As part of the RESTBase deprecation [[mw:RESTBase/deprecation|effort]], the <code dir="ltr">/page/related</code> endpoint has been blocked as of February 6, 2025, and will be removed soon. This timeline was chosen to align with the deprecation schedules for older Android and iOS versions. The stable alternative is the "<code dir="ltr">morelike</code>" action API in MediaWiki, and [[gerrit:c/mediawiki/services/mobileapps/+/982154/13/pagelib/src/transform/FooterReadMore.js|a migration example]] is available. The MediaWiki Interfaces team [[phab:T376297|can be contacted]] for any questions. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/GFC2IJO7L4BWO3YTM7C5HF4MCCBE2RJ2/] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/January|Language and Internationalization newsletter]] is available. It includes: Updates about the "Contribute" menu; details on some of the newest language editions of Wikipedia; details on new languages supported by the MediaWiki interface; updates on the Community-defined lists feature; and more. * The latest [[mw:Extension:Chart/Project/Updates#January 2025: Better visibility into charts and tabular data usage|Chart Project newsletter]] is available. It includes updates on the progress towards bringing better visibility into global charts usage and support for categorizing pages in the Data namespace on Commons. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:12, 11 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28231022 --> == Wikipedia translation of the week: 2025-08 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:2010 Malagasy constitutional referendum]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> A constitutional referendum was held in Madagascar on 17 November 2010, in which voters approved a proposal for the state's fourth Constitution. The Malagasy people were asked to answer "Yes" or "No" to the proposed new constitution, which was considered to help consolidate Andry Rajoelina's grip on power. At the time of the referendum, Rajoelina headed the governing Highest Transitional Authority (HAT), an interim junta established following the military-backed coup d'état against then President Marc Ravalomanana in March 2009. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:21, 17 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28245290 --> == Tech News: 2025-08 == <section begin="technews-2025-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/08|Translations]] are available. '''Weekly highlight''' * Communities using growth tools can now showcase one event on the <code>{{#special:Homepage}}</code> for newcomers. This feature will help newcomers to be informed about editing activities they can participate in. Administrators can create a new event to showcase at <code>{{#special:CommunityConfiguration}}</code>. To learn more about this feature, please read [[diffblog:2025/02/12/community-updates-module-connecting-newcomers-to-your-initiatives/|the Diff post]], have a look [[mw:Special:MyLanguage/Help:Growth/Tools/Community updates module|at the documentation]], or contact [[mw:Talk:Growth|the Growth team]]. '''Updates for editors''' [[File:Page Frame Features on desktop.png|thumb|Highlighted talk pages improvements]] * Starting next week, talk pages at these wikis – {{int:project-localized-name-eswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-itwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jawiki/en}} – will get [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|a new design]]. This change was extensively tested as a Beta feature and is the last step of [[mw:Special:MyLanguage/Talk pages project/Feature summary|talk pages improvements]]. [https://phabricator.wikimedia.org/T379102] * You can now navigate to view a redirect page directly from its action pages, such as the history page. Previously, you were forced to first go to the redirect target. This change should help editors who work with redirects a lot. Thanks to user stjn for this improvement. [https://phabricator.wikimedia.org/T5324] * When a Cite reference is reused many times, wikis currently show either numbers like "1.23" or localized alphabetic markers like "a b c" in the reference list. Previously, if there were so many reuses that the alphabetic markers were all used, [[MediaWiki:Cite error references no backlink label|an error message]] was displayed. As part of the work to [[phab:T383036|modernize Cite customization]], these errors will no longer be shown and instead the backlinks will fall back to showing numeric markers like "1.23" once the alphabetic markers are all used. * The log entries for each change to an editor's user-groups are now clearer by specifying exactly what has changed, instead of the plain before and after listings. Translators can [[phab:T369466|help to update the localized versions]]. Thanks to user Msz2001 for these improvements. * A new filter has been added to the [[{{#special:Nuke}}]] tool, which allows administrators to mass delete pages, to enable users to filter for pages in a range of page sizes (in bytes). This allows, for example, deleting pages only of a certain size or below. [https://phabricator.wikimedia.org/T378488] * Non-administrators can now check which pages are able to be deleted using the [[{{#special:Nuke}}]] tool. Thanks to user MolecularPilot for this and the previous improvements. [https://phabricator.wikimedia.org/T376378] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:25}} community-submitted {{PLURAL:25|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed in the configuration for the AV1 video file format, which enables these files to play again. [https://phabricator.wikimedia.org/T382193] '''Updates for technical contributors''' * Parsoid Read Views is going to be rolling out to most Wiktionaries over the next few weeks, following the successful transition of Wikivoyage to Parsoid Read Views last year. For more information, see the [[mw:Special:MyLanguage/Parsoid/Parser Unification|Parsoid/Parser Unification]] project page. [https://phabricator.wikimedia.org/T385923][https://phabricator.wikimedia.org/T371640] * Developers of tools that run on-wiki should note that <code dir=ltr>mw.Uri</code> is deprecated. Tools requiring <code dir=ltr>mw.Uri</code> must explicitly declare <code dir=ltr>mediawiki.Uri</code> as a ResourceLoader dependency, and should migrate to the browser native <code dir=ltr>URL</code> API soon. [https://phabricator.wikimedia.org/T384515] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:17, 17 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28275610 --> == Wikipedia translation of the week: 2025-09 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cooler Heads Coalition]]'''<br /> <small>''([[:de:Cooler Heads Coalition]])&#32;([[:fr:Cooler Heads Coalition]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''Cooler Heads Coalition''' is a politically conservative "informal and ad-hoc group" in the United States, financed and operated by the Competitive Enterprise Institute. The group, which rejects the scientific consensus on climate change, made efforts to stop the government from addressing climate change. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:23, 24 February 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28300238 --> == Tech News: 2025-09 == <section begin="technews-2025-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/09|Translations]] are available. '''Updates for editors''' * Administrators can now customize how the [[m:Special:MyLanguage/User language|Babel feature]] creates categories using [[{{#special:CommunityConfiguration/Babel}}]]. They can rename language categories, choose whether they should be auto-created, and adjust other settings. [https://phabricator.wikimedia.org/T374348] * The <bdi lang="en" dir="ltr">[https://www.wikimedia.org/ wikimedia.org]</bdi> portal has been updated – and is receiving some ongoing improvements – to modernize and improve the accessibility of our portal pages. It now has better support for mobile layouts, updated wording and links, and better language support. Additionally, all of the Wikimedia project portals, such as <bdi lang="en" dir="ltr">[https://wikibooks.org wikibooks.org]</bdi>, now support dark mode when a reader is using that system setting. [https://phabricator.wikimedia.org/T373204][https://phabricator.wikimedia.org/T368221][https://meta.wikimedia.org/wiki/Project_portals] * One new wiki has been created: a {{int:project-localized-name-group-wiktionary/en}} in [[d:Q33965|Santali]] ([[wikt:sat:|<code>wikt:sat:</code>]]) [https://phabricator.wikimedia.org/T386619] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that prevented clicking on search results in the web-interface for some Firefox for Android phone configurations. [https://phabricator.wikimedia.org/T381289] '''Meetings and events''' * The next Language Community Meeting is happening soon, February 28th at [https://zonestamp.toolforge.org/1740751200 14:00 UTC]. This week's meeting will cover: highlights and technical updates on keyboard and tools for the Sámi languages, Translatewiki.net contributions from the Bahasa Lampung community in Indonesia, and technical Q&A. If you'd like to join, simply [[mw:Wikimedia Language and Product Localization/Community meetings#28 February 2025|sign up on the wiki page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:42, 25 February 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28296129 --> == Wikipedia translation of the week: 2025-10 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:pt:Transmissor de Ondas]]'''<br /> <small>''([[:en:Wave Transmitter]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Esq eletr transm ondas color.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Transmissor de Ondas''' é um equipamento precursor do rádio, desenvolvido por Roberto Landell de Moura na década de 1890, capaz de transmitir áudio via ondas eletromagnéticas, com sua primeira demonstração pública documentada tendo ocorrido no dia 16 de julho de 1899. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:49, 3 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28317097 --> == Tech News: 2025-10 == <section begin="technews-2025-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/10|Translations]] are available. '''Updates for editors''' * All logged-in editors using the mobile view can now edit a full page. The "{{int:Minerva-page-actions-editfull}}" link is accessible from the "{{int:minerva-page-actions-overflow}}" menu in the toolbar. This was previously only available to editors using the [[mw:Special:MyLanguage/Reading/Web/Advanced mobile contributions|Advanced mobile contributions]] setting. [https://phabricator.wikimedia.org/T387180] * Interface administrators can now help to remove the deprecated Cite CSS code matching "<code dir="ltr">mw-ref</code>" from their local <bdi lang="en" dir="ltr">[[MediaWiki:Common.css]]</bdi>. The list of wikis in need of cleanup, and the code to remove, [https://global-search.toolforge.org/?q=mw-ref%5B%5E-a-z%5D&regex=1&namespaces=8&title=.*css can be found with this global search] and in [https://ace.wikipedia.org/w/index.php?title=MediaWiki:Common.css&oldid=145662#L-139--L-144 this example], and you can learn more about how to help on the [[mw:Parsoid/Parser Unification/Cite CSS|CSS migration project page]]. The Cite footnote markers ("<code dir="ltr">[1]</code>") are now rendered by [[mw:Special:MyLanguage/Parsoid|Parsoid]], and the deprecated CSS is no longer needed. The CSS for backlinks ("<code dir="ltr">mw:referencedBy</code>") should remain in place for now. This cleanup is expected to cause no visible changes for readers. Please help to remove this code before March 20, after which the development team will do it for you. * When editors embed a file (e.g. <code><nowiki>[[File:MediaWiki.png]]</nowiki></code>) on a page that is protected with cascading protection, the software will no longer restrict edits to the file description page, only to new file uploads.[https://phabricator.wikimedia.org/T24521] In contrast, transcluding a file description page (e.g. <code><nowiki>{{:File:MediaWiki.png}}</nowiki></code>) will now restrict edits to the page.[https://phabricator.wikimedia.org/T62109] * When editors revert a file to an earlier version it will now require the same permissions as ordinarily uploading a new version of the file. The software now checks for 'reupload' or 'reupload-own' rights,[https://phabricator.wikimedia.org/T304474] and respects cascading protection.[https://phabricator.wikimedia.org/T140010] * When administrators are listing pages for deletion with the Nuke tool, they can now also list associated talk pages and redirects for deletion, alongside pages created by the target, rather than needing to manually delete these pages afterwards. [https://phabricator.wikimedia.org/T95797] * The [[m:Special:MyLanguage/Tech/News/2025/03|previously noted]] update to Single User Login, which will accommodate browser restrictions on cross-domain cookies by moving login and account creation to a central domain, will now roll out to all users during March and April. The team plans to enable it for all new account creation on [[wikitech:Deployments/Train#Tuesday|Group0]] wikis this week. See [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3#Deployment|the SUL3 project page]] for more details and an updated timeline. * Since last week there has been a bug that shows some interface icons as black squares until the page has fully loaded. It will be fixed this week. [https://phabricator.wikimedia.org/T387351] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q2044560|Sylheti]] ([[w:syl:|<code>w:syl:</code>]]) [https://phabricator.wikimedia.org/T386441] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed with loading images in very old versions of the Firefox browser on mobile. [https://phabricator.wikimedia.org/T386400] '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.19|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 02:31, 4 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28334563 --> == Wikipedia translation of the week: 2025-11 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Smoky (mascotte olimpica)]]'''<br /> <small>''([[:en:Smoky (Olympic mascot)]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Smoky 1932 Olympic Village Mascot.webp|center|300px]] <div style="text-align:left; padding: .4em;"> '''Smoky''' (Los Angeles, 1931 o 1932 - Los Angeles, aprile 1934), occasionalmente scritto Smokey, è stato un cane che divenne la mascotte del villaggio olimpico estivo del 1932 e, successivamente, dell'evento generale. Pur non essendo oggi riconosciuto dal CIO, è stato, seppur non in modo ufficiale, la prima mascotte olimpica dei Giochi, oltre che a essere attualmente l'unica a essere stata un animale vero. Le successive edizioni non ebbero mascotte, dovendo aspettare i X Giochi olimpici invernali di Grenoble nel 1968 per ritrovarne una ufficialmente riconosciuta, lo sciatore stilizzato Schuss, allora non considerato ufficiale ma successivamente riconosciuto come tale. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:50, 10 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28317097 --> == Tech News: 2025-11 == <section begin="technews-2025-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/11|Translations]] are available. '''Updates for editors''' * Editors who use password managers at multiple wikis may notice changes in the future. The way that our wikis provide information to password managers about reusing passwords across domains has recently been updated, so some password managers might now offer you login credentials that you saved for a different Wikimedia site. Some password managers already did this, and are now doing it for more Wikimedia domains. This is part of the [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3|SUL3 project]] which aims to improve how our unified login works, and to keep it compatible with ongoing changes to the web-browsers we use. [https://phabricator.wikimedia.org/T385520][https://phabricator.wikimedia.org/T384844] * The Wikipedia Apps Team is inviting interested users to help improve Wikipedia’s offline and limited internet use. After discussions in [[m:Afrika Baraza|Afrika Baraza]] and the last [[m:Special:MyLanguage/ESEAP Hub/Meetings|ESEAP call]], key challenges like search, editing, and offline access are being explored, with upcoming focus groups to dive deeper into these topics. All languages are welcome, and interpretation will be available. Want to share your thoughts? [[mw:Special:MyLanguage/Wikimedia Apps/Improving Wikipedia Mobile Apps for Offline & Limited Internet Use|Join the discussion]] or email <bdi lang="en" dir="ltr">aramadan@wikimedia.org</bdi>! * All wikis will be read-only for a few minutes on March 19. This is planned at [https://zonestamp.toolforge.org/1742392800 14:00 UTC]. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.20|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/33|Growth newsletter]] is available. It includes: the launch of the Community Updates module, the most recent changes in Community Configuration, and the upcoming test of in-article suggestions for first-time editors. * An old API that was previously used in the Android Wikipedia app is being removed at the end of March. There are no current software uses, but users of the app with a version that is older than 6 months by the time of removal (2025-03-31), will no longer have access to the Suggested Edits feature, until they update their app. You can [[diffblog:2025/02/24/sunset-of-wikimedia-recommendation-api/|read more details about this change]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:10, 10 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28372257 --> == Wikipedia translation of the week: 2025-12 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Amazonas, o maior rio do mundo]]'''<br /> <small>''([[:pt:Amazonas, o maior rio do mundo]])&#32;([[:es:Amazonas, o maior rio do mundo]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Frame A from Amazonas, o maior rio do mundo.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''''Amazonas, o maior rio do mundo''''' (lit. 'Amazon: The Greatest River in the World') is a 1922 Brazilian silent documentary film produced in 1918 by Silvino Santos. It is a black-and-white film that portrays life in the Amazon rainforest. Completed in 1920, it is considered one of the oldest cinematic records of the Amazon. It was presumed lost in 1931 and only rediscovered in 2023 at the Czech Film Archive. Silvino Santos produced the work over three years using sophisticated cinematic techniques, which led it to be deemed of "immense artistic value" by Le Monde. It has also been described as the "Holy Grail of Brazilian silent cinema" by The Guardian. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:57, 17 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28392163 --> == Tech News: 2025-12 == <section begin="technews-2025-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/12|Translations]] are available. '''Weekly highlight''' * Twice a year, around the equinoxes, the Wikimedia Foundation's Site Reliability Engineering (SRE) team performs [[m:Special:MyLanguage/Tech/Server switch|a datacenter server switchover]], redirecting all traffic from one primary server to its backup. This provides reliability in case of a crisis, as we can always fall back on the other datacenter. [http://listen.hatnote.com/ Thanks to the Listen to Wikipedia] tool, you can hear the switchover take place: Before it begins, you'll hear the steady stream of edits; Then, as the system enters a brief read-only phase, the sound stops for a couple of minutes, before resuming after the switchover. You can [[diffblog:2025/03/12/hear-that-the-wikis-go-silent-twice-a-year/|read more about the background and details of this process on the Diff blog]]. If you want to keep an ear out for the next server switchover, listen to the wikis on [https://zonestamp.toolforge.org/1742392800 March 19 at 14:00 UTC]. '''Updates for editors''' * The [https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&filter-type=automatic&filter-id=previous-edits&active-list=suggestions&from=en&to=es improved Content Translation tool dashboard] is now available in [[phab:T387820|10 Wikipedias]] and will be available for all Wikipedias [[phab:T387821|soon]]. With [[mw:Special:MyLanguage/Content translation#Improved translation experience|the unified dashboard]], desktop users can now: Translate new sections of an article; Discover and access topic-based [https://ig.m.wikipedia.org/w/index.php?title=Special:ContentTranslation&active-list=suggestions&from=en&to=ig&filter-type=automatic&filter-id=previous-edits article suggestion filters] (initially available only for mobile device users); Discover and access the [[mw:Special:MyLanguage/Translation suggestions: Topic-based & Community-defined lists|Community-defined lists]] filter, also known as "Collections", from wiki-projects and campaigns. * On Wikimedia Commons, a [[c:Commons:WMF support for Commons/Upload Wizard Improvements#Improve category selection|new system to select the appropriate file categories]] has been introduced: if a category has one or more subcategories, users will be able to click on an arrow that will open the subcategories directly within the form, and choose the correct one. The parent category name will always be shown on top, and it will always be possible to come back to it. This should decrease the amount of work for volunteers in fixing/creating new categories. The change is also available on mobile. These changes are part of planned improvements to the UploadWizard. * The Community Tech team is seeking wikis to join a pilot for the [[m:Special:MyLanguage/Community Wishlist Survey 2023/Multiblocks|Multiblocks]] feature and a refreshed Special:Block page in late March. Multiblocks enables administrators to impose multiple different types of blocks on the same user at the same time. If you are an admin or steward and would like us to discuss joining the pilot with your community, please leave a message on the [[m:Talk:Community Wishlist Survey 2023/Multiblocks|project talk page]]. * Starting March 25, the Editing team will test a new feature for Edit Check at [[phab:T384372|12 Wikipedias]]: [[mw:Special:MyLanguage/Help:Edit check#Multi-check|Multi-Check]]. Half of the newcomers on these wikis will see all [[mw:Special:MyLanguage/Help:Edit check#ref|Reference Checks]] during their edit session, while the other half will continue seeing only one. The goal of this test is to see if users are confused or discouraged when shown multiple Reference Checks (when relevant) within a single editing session. At these wikis, the tags used on edits that show References Check will be simplified, as multiple tags could be shown within a single edit. Changes to the tags are documented [[phab:T373949|on Phabricator]]. [https://phabricator.wikimedia.org/T379131] * The [[m:Special:MyLanguage/Global reminder bot|Global reminder bot]], which is a service for notifying users that their temporary user-rights are about to expire, now supports using the localized name of the user-rights group in the message heading. Translators can see the [[m:Global reminder bot/Translation|listing of existing translations and documentation]] to check if their language needs updating or creation. * The [[Special:GlobalPreferences|GlobalPreferences]] gender setting, which is used for how the software should refer to you in interface messages, now works as expected by overriding the local defaults. [https://phabricator.wikimedia.org/T386584] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:26}} community-submitted {{PLURAL:26|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the Wikipedia App for Android had a bug fixed for when a user is browsing and searching in multiple languages. [https://phabricator.wikimedia.org/T379777] '''Updates for technical contributors''' * Later this week, the way that Codex styles are loaded will be changing. There is a small risk that this may result in unstyled interface message boxes on certain pages. User generated content (e.g. templates) is not impacted. Gadgets may be impacted. If you see any issues [[phab:T388847|please report them]]. See the linked task for details, screenshots, and documentation on how to fix any affected gadgets. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.21|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:48, 17 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28412594 --> == Wikipedia translation of the week: 2025-13 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ali of the Eretnids]]'''<br /> <small>''([[:tr:Alaaddin Ali Bey]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Ala al-Din Ali''' (January 1353 – August 1380) was the third Sultan of the Eretnids ruling from 1366 until his death. He inherited the throne at a very early age and was removed from administrative matters. He was characterized as particularly keen on personal pleasures, which later discredited his authority. During his rule, emirs under the Eretnids enjoyed considerable autonomy, and the state continued to shrink as neighboring powers captured several towns. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:59, 24 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28433698 --> == Tech News: 2025-13 == <section begin="technews-2025-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/13|Translations]] are available. '''Weekly highlight''' * The Wikimedia Foundation is seeking your feedback on the [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Product & Technology OKRs|drafts of the objectives and key results that will shape the Foundation's Product and Technology priorities]] for the next fiscal year (starting in July). The objectives are broad high-level areas, and the key-results are measurable ways to track the success of their objectives. Please share your feedback on the talkpage, in any language, ideally before the end of April. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] will be released to multiple wikis (see [[m:Special:MyLanguage/CampaignEvents/Deployment status#Global Deployment Plan|deployment plan]] for details) in April 2025, and the team has begun the process of engaging communities on the identified wikis. The extension provides tools to organize, manage, and promote collaborative activities (like events, edit-a-thons, and WikiProjects) on the wikis. The extension has three tools: [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], [[m:Special:MyLanguage/CampaignEvents/Collaboration list|Collaboration List]], and [[m:Special:MyLanguage/Campaigns/Foundation Product Team/Invitation list|Invitation Lists]]. It is currently on 13 Wikipedias, including English Wikipedia, French Wikipedia, and Spanish Wikipedia, as well as Wikidata. Questions or requests can be directed to the [[mw:Help talk:Extension:CampaignEvents|extension talk page]] or in Phabricator (with <bdi lang="en" dir="ltr" style="white-space: nowrap;">#campaigns-product-team</bdi> tag). * Starting the week of March 31st, wikis will be able to set which user groups can view private registrants in [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], as part of the [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents]] extension. By default, event organizers and the local wiki admins will be able to see private registrants. This is a change from the current behavior, in which only event organizers can see private registrants. Wikis can change the default setup by [[m:Special:MyLanguage/Requesting wiki configuration changes|requesting a configuration change]] in Phabricator (and adding the <bdi lang="en" dir="ltr" style="white-space: nowrap;">#campaigns-product-team</bdi> tag). Participants of past events can cancel their registration at any time. * Administrators at wikis that have a customized <bdi lang="en" dir="ltr">[[MediaWiki:Sidebar]]</bdi> should check that it contains an entry for the {{int:specialpages}} listing. If it does not, they should add it using <code dir=ltr style="white-space: nowrap;">* specialpages-url|specialpages</code>. Wikis with a default sidebar will see the link moved from the page toolbox into the sidebar menu in April. [https://phabricator.wikimedia.org/T388927] * The Minerva skin (mobile web) combines both Notice and Alert notifications within the bell icon ([[File:OOjs UI icon bell.svg|16px|link=|class=skin-invert]]). There was a long-standing bug where an indication for new notifications was only shown if you had unseen Alerts. This bug is now fixed. In the future, Minerva users will notice a counter atop the bell icon when you have 1 or more unseen Notices and/or Alerts. [https://phabricator.wikimedia.org/T344029] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * VisualEditor has introduced a [[mw:VisualEditor/Hooks|new client-side hook]] for developers to use when integrating with the VisualEditor target lifecycle. This hook should replace the existing lifecycle-related hooks, and be more consistent between different platforms. In addition, the new hook will apply to uses of VisualEditor outside of just full article editing, allowing gadgets to interact with the editor in DiscussionTools as well. The Editing Team intends to deprecate and eventually remove the old lifecycle hooks, so any use cases that this new hook does not cover would be of interest to them and can be [[phab:T355555|shared in the task]]. * Developers who use the <code dir=ltr>mw.Api</code> JavaScript library, can now identify the tool using it with the <code dir=ltr>userAgent</code> parameter: <code dir=ltr>var api = new mw.Api( { userAgent: 'GadgetNameHere/1.0.1' } );</code>. If you maintain a gadget or user script, please set a user agent, because it helps with library and server maintenance and with differentiating between legitimate and illegitimate traffic. [https://phabricator.wikimedia.org/T373874][https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_User-Agent_Policy] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.22|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:43, 24 March 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28443127 --> == Wikipedia translation of the week: 2025-14 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Chilembwe uprising]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Chilembwe supporters being led to be executed (cropped).jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Chilembwe uprising''' was a rebellion against British colonial rule in Nyasaland (modern-day Malawi) which took place in January 1915. It was led by John Chilembwe, an American-educated Baptist minister. Based around his church in the village of Mbombwe in the south-east of the colony, the leaders of the revolt were mainly from an emerging black middle class. They were motivated by grievances against the British colonial system, which included forced labour, racial discrimination and new demands imposed on the African population following the outbreak of World War I. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:52, 31 March 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28454663 --> == Tech News: 2025-14 == <section begin="technews-2025-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/14|Translations]] are available. '''Updates for editors''' * The Editing team is working on a new [[mw:Special:MyLanguage/Edit Check|Edit check]]: [[mw:Special:MyLanguage/Edit check#26 March 2025|Peacock check]]. This check's goal is to identify non-neutral terms while a user is editing a wikipage, so that they can be informed that their edit should perhaps be changed before they publish it. This project is at the early stages, and the team is looking for communities' input: [[phab:T389445|in this Phabricator task]], they are gathering on-wiki policies, templates used to tag non-neutral articles, and the terms (jargon and keywords) used in edit summaries for the languages they are currently researching. You can participate by editing the table on Phabricator, commenting on the task, or directly messaging [[m:user:Trizek (WMF)|Trizek (WMF)]]. * [[mw:Special:MyLanguage/MediaWiki Platform Team/SUL3|Single User Login]] has now been updated on all wikis to move login and account creation to a central domain. This makes user login compatible with browser restrictions on cross-domain cookies, which have prevented users of some browsers from staying logged in. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:35}} community-submitted {{PLURAL:35|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Starting on March 31st, the MediaWiki Interfaces team will begin a limited release of generated OpenAPI specs and a SwaggerUI-based sandbox experience for [[mw:Special:MyLanguage/API:REST API|MediaWiki REST APIs]]. They invite developers from a limited group of non-English Wikipedia communities (Arabic, German, French, Hebrew, Interlingua, Dutch, Chinese) to review the documentation and experiment with the sandbox in their preferred language. In addition to these specific Wikipedia projects, the sandbox and OpenAPI spec will be available on the [[testwiki:Special:RestSandbox|on the test wiki REST Sandbox special page]] for developers with English as their preferred language. During the preview period, the MediaWiki Interfaces Team also invites developers to [[mw:MediaWiki Interfaces Team/Feature Feedback/REST Sandbox|share feedback about your experience]]. The preview will last for approximately 2 weeks, after which the sandbox and OpenAPI specs will be made available across all wiki projects. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.23|MediaWiki]] '''In depth''' * Sometimes a small, [[gerrit:c/operations/cookbooks/+/1129184|one line code change]] can have great significance: in this case, it means that for the first time in years we're able to run all of the stack serving <bdi lang="en" dir="ltr">[http://maps.wikimedia.org/ maps.wikimedia.org]</bdi> - a host dedicated to serving our wikis and their multi-lingual maps needs - from a single core datacenter, something we test every time we perform a [[m:Special:MyLanguage/Tech/Server switch|datacenter switchover]]. This is important because it means that in case one of our datacenters is affected by a catastrophe, we'll still be able to serve the site. This change is the result of [[phab:T216826|extensive work]] by two developers on porting the last component of the maps stack over to [[w:en:Kubernetes|kubernetes]], where we can allocate resources more efficiently than before, thus we're able to withstand more traffic in a single datacenter. This work involved a lot of complicated steps because this software, and the software libraries it uses, required many long overdue upgrades. This type of work makes the Wikimedia infrastructure more sustainable. '''Meetings and events''' * [[mw:Special:MyLanguage/MediaWiki Users and Developers Workshop Spring 2025|MediaWiki Users and Developers Workshop Spring 2025]] is happening in Sandusky, USA, and online, from 14–16 May 2025. The workshop will feature discussions around the usage of MediaWiki software by and within companies in different industries and will inspire and onboard new users. Registration and presentation signup is now available at the workshop's website. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:06, 1 April 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28473566 --> == Wikipedia translation of the week: 2025-15 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:1930 Bago earthquake]]'''<br /> <small>''([[:my:၁၉၃၀ ပဲခူးငလျင်]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Thiao Mueang Phama (1955, p. 165).jpg|center|300px]] <div style="text-align:left; padding: .4em;"> An earthquake affected Myanmar on 5 May 1930 with a moment magnitude (Mw ) 7.4. The shock occurred 35 km (22 mi) beneath the surface with a maximum Rossi–Forel intensity of IX (Devastating tremor). The earthquake was the result of rupture along a 131 km (81 mi) segment of the Sagaing Fault—a major strike-slip fault that runs through the country. Extensive damage was reported in the southern part of the country, particularly in Bago and Yangon, where buildings collapsed and fires erupted. At least 550, and possibly up to 7,000 people were killed. A moderate tsunami struck the Burmese coast which caused minor damage to ships and a port. It was felt for over 570,000 km2 (220,000 sq mi) and as far as Shan State and Thailand. The mainshock was followed by many aftershocks; several were damaging. The December earthquake was similarly sized which also occurred along the Sagaing Fault. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:54, 7 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28454663 --> == Tech News: 2025-15 == <section begin="technews-2025-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/15|Translations]] are available. '''Updates for editors''' * From now on, [[m:Special:MyLanguage/Interface administrators|interface admins]] and [[m:Special:MyLanguage/Central notice administrators|centralnotice admins]] are technically required to enable [[m:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]] before they can use their privileges. In the future this might be expanded to more groups with advanced user-rights. [https://phabricator.wikimedia.org/T150898] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The Design System Team is preparing to release the next major version of Codex (v2.0.0) on April 29. Editors and developers who use CSS from Codex should see the [[mw:Codex/Release Timeline/2.0|2.0 overview documentation]], which includes guidance related to a few of the breaking changes such as <code dir=ltr style="white-space: nowrap;">font-size</code>, <code dir=ltr style="white-space: nowrap;">line-height</code>, and <code dir=ltr style="white-space: nowrap;">size-icon</code>. * The results of the [[mw:Developer Satisfaction Survey/2025|Developer Satisfaction Survey (2025)]]  are now available. Thank you to all participants. These results help the Foundation decide what to work on next and to review what they recently worked on. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.24|MediaWiki]] '''Meetings and events''' * The [[mw:Special:MyLanguage/Wikimedia Hackathon 2025|2025 Wikimedia Hackathon]] will take place in Istanbul, Turkey, between 2–4 May. Registration for attending the in-person event will close on 13 April. Before registering, please note the potential need for a [https://www.mfa.gov.tr/turkish-representations.en.mfa visa] or [https://www.mfa.gov.tr/visa-information-for-foreigners.en.mfa e-visa] to enter the country. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:53, 7 April 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28507470 --> == Wikipedia translation of the week: 2025-16 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Museum of Zoology of the University of São Paulo]]'''<br /> <small>''([[:pt:Museu de Zoologia da Universidade de São Paulo]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Museu de Zoologia da USP 02.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Museum of Zoology of the University of São Paulo''' (Portuguese: Museu de Zoologia da Universidade de São Paulo, abbreviated MZUSP) is a public natural history museum located in the historic Ipiranga district of São Paulo, Brazil. The MZUSP is an educational and research institution that is part of the University of São Paulo. The museum began at the end of the 19th century as part of the Museu Paulista; in 1941, it moved into a dedicated building. In 1969 the museum became a part of the University of São Paulo, receiving its current name. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:27, 14 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28454663 --> == Tech News: 2025-16 == <section begin="technews-2025-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/16|Translations]] are available. '''Weekly highlight''' * Later this week, the default thumbnail size will be increased from 220px to 250px. This changes how pages are shown in all wikis and has been requested by some communities for many years, but wasn't previously possible due to technical limitations. [https://phabricator.wikimedia.org/T355914] * File thumbnails are now stored in discrete sizes. If a page specifies a thumbnail size that's not among the standard sizes (20, 40, 60, 120, 250, 330, 500, 960), then MediaWiki will pick the closest larger thumbnail size but will tell the browser to downscale it to the requested size. In these cases, nothing will change visually but users might load slightly larger images. If it doesn't matter which thumbnail size is used in a page, please pick one of the standard sizes to avoid the extra in-browser down-scaling step. [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Images#Thumbnail_sizes][https://phabricator.wikimedia.org/T355914] '''Updates for editors''' * The Wikimedia Foundation are working on a system called [[m:Edge Uniques|Edge Uniques]] which will enable [[:w:en:A/B testing|A/B testing]], help protect against [[:w:en:Denial-of-service attack|Distributed denial-of-service attacks]] (DDoS attacks), and make it easier to understand how many visitors the Wikimedia sites have. This is so that they can more efficiently build tools which help readers, and make it easier for readers to find what they are looking for. * To improve security for users, a small percentage of logins will now require that the account owner input a one-time password [[mw:Special:MyLanguage/Help:Extension:EmailAuth|emailed to their account]]. It is recommended that you [[Special:Preferences#mw-prefsection-personal-email|check]] that the email address on your account is set correctly, and that it has been confirmed, and that you have an email set for this purpose. [https://phabricator.wikimedia.org/T390662] * "Are you interested in taking a short survey to improve tools used for reviewing or reverting edits on your Wiki?" This question will be [[phab:T389401|asked at 7 wikis starting next week]], on Recent Changes and Watchlist pages. The [[mw:Special:MyLanguage/Moderator Tools|Moderator Tools team]] wants to know more about activities that involve looking at new edits made to your Wikimedia project, and determining whether they adhere to your project's policies. * On April 15, the full Wikidata graph will no longer be supported on <bdi lang="zxx" dir="ltr">[https://query.wikidata.org/ query.wikidata.org]</bdi>. After this date, scholarly articles will be available through <bdi lang="zxx" dir="ltr" style="white-space:nowrap;">[https://query-scholarly.wikidata.org/ query-scholarly.wikidata.org]</bdi>, while the rest of the data hosted on Wikidata will be available through the <bdi lang="zxx" dir="ltr">[https://query.wikidata.org/ query.wikidata.org]</bdi> endpoint. This is part of the scheduled split of the Wikidata Graph, which was [[d:Special:MyLanguage/Wikidata:SPARQL query service/WDQS backend update/September 2024 scaling update|announced in September 2024]]. More information is [[d:Wikidata:SPARQL query service/WDQS graph split|available on Wikidata]]. * The latest quarterly [[m:Special:MyLanguage/Wikimedia Apps/Newsletter/First quarter of 2025|Wikimedia Apps Newsletter]] is now available. It covers updates, experiments, and improvements made to the Wikipedia mobile apps. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The latest quarterly [[mw:Technical Community Newsletter/2025/April|Technical Community Newsletter]] is now available. This edition includes: an invitation for tool maintainers to attend the Toolforge UI Community Feedback Session on April 15th; recent community metrics; and recent technical blog posts. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.25|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:25, 15 April 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28540654 --> == Wikipedia translation of the week: 2025-17 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Fear of crime]]'''<br /> <small>''([[:ar:الخوف من الجريمة]])&#32;([[:it:Criminofobia]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Fear of crime''' refers to the fear of being a victim of crime, which is not necessarily reflective of the actual probability of being such a victim. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:23, 21 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28559524 --> == Tech News: 2025-17 == <section begin="technews-2025-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/17|Translations]] are available. '''Updates for editors''' * [[f:Special:MyLanguage/Wikifunctions:Main Page|Wikifunctions]] is now integrated with [[w:dag:Solɔɣu|Dagbani Wikipedia]] since April 15. It is the first project that will be able to call [[f:Special:MyLanguage/Wikifunctions:Introduction|functions from Wikifunctions]] and integrate them in articles. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of [[f:Special:MyLanguage/Wikifunctions:Catalogue|a stable and global function]], rather than via a local template. [https://www.wikifunctions.org/wiki/Special:MyLanguage/Wikifunctions:Status_updates/2025-04-16] * A new type of lint error has been created: [[Special:LintErrors/empty-heading|{{int:linter-category-empty-heading}}]] ([[mw:Special:MyLanguage/Help:Lint errors/empty-heading|documentation]]). The [[mw:Special:MyLanguage/Help:Extension:Linter|Linter extension]]'s purpose is to identify wikitext patterns that must or can be fixed in pages and provide some guidance about what the problems are with those patterns and how to fix them. [https://phabricator.wikimedia.org/T368722] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:37}} community-submitted {{PLURAL:37|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Following its publication on HuggingFace, the "Structured Contents" dataset, developed by Wikimedia Enterprise, is [https://enterprise.wikimedia.com/blog/kaggle-dataset/ now also available on Kaggle]. This Beta initiative is focused on making Wikimedia data more machine-readable for high-volume reusers. They are releasing this beta version in a location that open dataset communities already use, in order to seek feedback, to help improve the product for a future wider release. You can read more about the overall [https://enterprise.wikimedia.com/blog/structured-contents-snapshot-api/#open-datasets Structured Contents project], and about the [https://enterprise.wikimedia.com/blog/structured-contents-wikipedia-infobox/ first release that's freely usable]. * There is no new MediaWiki version this week. '''Meetings and events''' * The Editing and Machine Learning Teams invite interested volunteers to a video meeting to discuss [[mw:Special:MyLanguage/Edit check/Peacock check|Peacock check]], which is the latest [[mw:Special:MyLanguage/Edit check|Edit check]] that will detect "peacock" or "overly-promotional" or "non-neutral" language whilst an editor is typing. Editors who work with newcomers, or help to fix this kind of writing, or are interested in how we use artificial intelligence in our projects are encouraged to attend. The [[mw:Special:MyLanguage/Editing team/Community Conversations#Next Conversation|meeting will be on April 28, 2025]] at [https://zonestamp.toolforge.org/1745863200 18:00–19:00 UTC] and hosted on Zoom. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:01, 21 April 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28578245 --> == Wikipedia translation of the week: 2025-18 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Heritage preservation in South Korea]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Korean.Dance-03.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The heritage preservation system of South Korea is a multi-level program aiming to preserve and cultivate Korean cultural heritage. The program is administered by the Cultural Heritage Administration (CHA), and the legal framework is provided by the Cultural Heritage Protection Act of 1962, last updated in 2012. The program started in 1962 and has gradually been extended and upgraded since then. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:57, 28 April 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28583422 --> == Tech News: 2025-18 == <section begin="technews-2025-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/18|Translations]] are available. '''Updates for editors''' * Event organizers who host collaborative activities on [[m:Special:MyLanguage/CampaignEvents/Deployment status#Global Deployment Plan|multiple wikis]], including Bengali, Japanese, and Korean Wikipedias, will have access to the [[mw:Special:MyLanguage/Extension:CampaignEvents|CampaignEvents extension]] this week. Also, admins in the Wikipedia where the extension is enabled will automatically be granted the event organizer right soon. They won't have to manually grant themselves the right before they can manage events as [[phab:T386861|requested by a community]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:19}} community-submitted {{PLURAL:19|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The release of the next major version of [[mw:Special:MyLanguage/Codex|Codex]], the design system for Wikimedia, is scheduled for 29 April 2025. Technical editors will have access to the release by the week of 5 May 2025. This update will include a number of [[mw:Special:MyLanguage/Codex/Release_Timeline/2.0#Breaking_changes|breaking changes]] and minor [[mw:Special:MyLanguage/Codex/Release_Timeline/2.0#Visual_changes|visual changes]]. Instructions on handling the breaking and visual changes are documented on [[mw:Special:MyLanguage/Codex/Release Timeline/2.0#|this page]]. Pre-release testing is reported in [[phab:T386298|T386298]], with post-release issues tracked in [[phab:T392379|T392379]] and [[phab:T392390|T392390]]. * Users of [[wikitech:Special:MyLanguage/Help:Wiki_Replicas|Wiki Replicas]] will notice that the database views of <code dir="ltr">ipblocks</code>, <code dir="ltr">ipblocks_ipindex</code>, and <code dir="ltr">ipblocks_compat</code> are [[phab:T390767|now deprecated]]. Users can query the <code dir="ltr">[[mw:Special:MyLanguage/Manual:Block_table|block]]</code> and <code dir="ltr">[[mw:Special:MyLanguage/Manual:Block_target_table|block_target]]</code> new views that mirror the new tables in the production database instead. The deprecated views will be removed entirely from Wiki Replicas in June, 2025. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.27|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/April|Language and Internationalization Newsletter]] is now available. This edition includes an overview of the improved [https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&campaign=contributionsmenu&to=es&filter-type=automatic&filter-id=previous-edits&active-list=suggestions&from=en#/ Content Translation Dashboard Tool], [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/April#Language Support for New and Existing Languages|support for new languages]], [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/April#Wiki Loves Ramadan Articles Made In Content Translation Mobile Workflow|highlights from the Wiki Loves Ramadan campaign]], [[m:Special:MyLanguage/Research:Languages Onboarding Experiment 2024 - Executive Summary|results from the Language Onboarding Experiment]], an analysis of topic diversity in articles, and information on upcoming community meetings and events. '''Meetings and events''' * The [[Special:MyLanguage/Grants:Knowledge_Sharing/Connect/Calendar|Let's Connect Learning Clinic]] will take place on [https://zonestamp.toolforge.org/1745937000 April 29 at 14:30 UTC]. This edition will focus on "Understanding and Navigating Conflict in Wikimedia Projects". You can [[m:Special:MyLanguage/Event:Learning Clinic %E2%80%93 Understanding and Navigating Conflict in Wikimedia Projects (Part_1)|register now]] to attend. * The [[mw:Special:MyLanguage/Wikimedia Hackathon 2025|2025 Wikimedia Hackathon]], which brings the global technical community together to connect, brainstorm, and hack existing projects, will take place from May 2 to 4th, 2025, at Istanbul, Turkey. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:32, 28 April 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28585685 --> == Wikipedia translation of the week: 2025-19 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lhamana]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:We-Wa, a Zuni berdache, weaving - NARA - 523796 (cropped).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Lhamana''', in traditional Zuni culture, are biologically male people who take on the social and ceremonial roles usually performed by women in their culture, at least some of the time. They wear a mixture of women's and men's clothing and much of their work is in the areas usually occupied by Zuni women. Some contemporary lhamana participate in the pan-Indian two-spirit community. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 07:28, 5 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28583422 --> == Tech News: 2025-19 == <section begin="technews-2025-W19"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/19|Translations]] are available. '''Weekly highlight''' * The Wikimedia Foundation has shared the latest draft update to their [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026|annual plan]] for next year (July 2025–June 2026). This includes an [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026|executive summary]] (also on [[diffblog:2025/04/25/sharing-the-wikimedia-foundations-2025-2026-draft-annual-plan/|Diff]]), details about the three main [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Goals|goals]] ([[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Product & Technology OKRs|Infrastructure]], [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Goals/Volunteer Support|Volunteer Support]], and [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Goals/Effectiveness|Effectiveness]]), [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Global Trends|global trends]], and the [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Budget Overview|budget]] and [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026/Financial Model|financial model]]. Feedback and questions are welcome on the [[m:Talk:Wikimedia Foundation Annual Plan/2025-2026|talk page]] until the end of May. '''Updates for editors''' * For wikis that have the [[m:Special:MyLanguage/CampaignEvents/Deployment status|CampaignEvents extension enabled]], two new feature improvements have been released: ** Admins can now choose which namespaces are permitted for [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] via [[mw:Special:MyLanguage/Community Configuration|Community Configuration]] ([[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Registration/Permitted namespaces|documentation]]). The default setup is for event registration to be permitted in the Event namespace, but other namespaces (such as the project namespace or WikiProject namespace) can now be added. With this change, communities like WikiProjects can now more easily use Event Registration for their collaborative activities. ** Editors can now [[mw:Special:MyLanguage/Transclusion|transclude]] the Collaboration List on a wiki page ([[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Collaboration list/Transclusion|documentation]]). The Collaboration List is an automated list of events and WikiProjects on the wikis, accessed via {{#special:AllEvents}} ([[w:en:Special:AllEvents|example]]). Now, the Collaboration List can be added to all sorts of wiki pages, such as: a wiki mainpage, a WikiProject page, an affiliate page, an event page, or even a user page. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Developers who use the <code dir=ltr>moment</code> library in gadgets and user scripts should revise their code to use alternatives like the <code dir=ltr>Intl</code> library or the new <code dir=ltr>mediawiki.DateFormatter</code> library. The <code dir=ltr>moment</code> library has been deprecated and will begin to log messages in the developer console. You can see a global search for current uses, and [[phab:T392532|ask related questions in this Phabricator task]]. * Developers who maintain a tool that queries the Wikidata term store tables (<code dir=ltr style="white-space: nowrap;">wbt_*</code>) need to update their code to connect to a separate database cluster. These tables are being split into a separate database cluster. Tools that query those tables via the wiki replicas must be adapted to connect to the new cluster instead. [[wikitech:News/2025 Wikidata term store database split|Documentation and related links are available]]. [https://phabricator.wikimedia.org/T390954] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.44/wmf.28|MediaWiki]] '''In depth''' * The latest [[mw:Special:MyLanguage/Extension:Chart/Project/Updates|Chart Project newsletter]] is available. It includes updates on preparing to expand the deployment to additional wikis as soon as this week (starting May 6) and scaling up over the following weeks, plus exploring filtering and transforming source data. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/19|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W19"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:15, 6 May 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28665011 --> == Wikipedia translation of the week: 2025-20 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Gruppo del Sileno]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Parco3.JPG|300px|center]] <div style="text-align:left; padding: .4em;"> '''Sileno ed Egle con Mnasilo e Cromi''', meglio noto come Gruppo del Sileno, è un monumento in marmo di Carrara, realizzato da Jean-Baptiste Boudard nel 1765 per il Giardino Ducale di Parma; sostituito nel 1991 con una copia in polvere di marmo e resina, l'originale si trova provvisoriamente nel chiostro della Fontana del monastero di San Paolo, in attesa della definitiva collocazione prevista all'interno del palazzetto Eucherio Sanvitale nel parco Ducale. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:28, 12 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28709947 --> == Tech News: 2025-20 == <section begin="technews-2025-W20"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/20|Translations]] are available. '''Weekly highlight''' * The [[m:Special:MyLanguage/Wikimedia URL Shortener|"Get shortened URL"]] link on the sidebar now includes a [[phab:T393309|QR code]]. Wikimedia site users can now use it by scanning or downloading it to quickly share and access shared content from Wikimedia sites, conveniently. '''Updates for editors''' * The Wikimedia Foundation is working on a system called [[m:Edge Uniques|Edge Uniques]], which will enable [[w:en:A/B testing|A/B testing]], help protect against [[w:en:Denial-of-service attack|distributed denial-of-service attacks]] (DDoS attacks), and make it easier to understand how many visitors the Wikimedia sites have. This is to help more efficiently build tools which help readers, and make it easier for readers to find what they are looking for. Tech News has [[m:Special:MyLanguage/Tech/News/2025/16|previously written about this]]. The deployment will be gradual. Some might see the Edge Uniques cookie the week of 19 May. You can discuss this on the [[m:Talk:Edge Uniques|talk page]]. * Starting May 19, 2025, Event organisers in wikis with the [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] enabled can use [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] in the project namespace (e.g., Wikipedia namespace, Wikidata namespace). With this change, communities don't need admins to use the feature. However, wikis that don't want this change can remove and add the permitted namespaces at [[Special:CommunityConfiguration/CampaignEvents]]. * The Wikipedia project now has a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q36720|Nupe]] ([[w:nup:|<code>w:nup:</code>]]). This is a language primarily spoken in the North Central region of Nigeria. Speakers of this language are invited to contribute to [[w:nup:Tatacin feregi|new Wikipedia]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Developers can now access pre-parsed Dutch Wikipedia, amongst others (English, German, French, Spanish, Italian, and Portuguese) through the [https://enterprise.wikimedia.com/docs/snapshot/#structured-contents-snapshot-bundle-info-beta Structured Contents snapshots (beta)]. The content includes parsed Wikipedia abstracts, descriptions, main images, infoboxes, article sections, and references. * The <code dir="ltr">/page/data-parsoid</code> REST API endpoint is no longer in use and will be deprecated. It is [[phab:T393557|scheduled to be turned off]] on June 7, 2025. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.1|MediaWiki]] '''In depth''' * The [https://wikitech.wikimedia.org/wiki/News/2025_Cloud_VPS_VXLAN_IPv6_migration IPv6 support] is a newly introduced Cloud virtual network that significantly boosts Wikimedia platforms' scalability, security, and readiness for the future. If you are a technical contributor eager to learn more, check out [https://techblog.wikimedia.org/2025/05/06/wikimedia-cloud-vps-ipv6-support/ this blog post] for an in-depth look at the journey to IPv6. '''Meetings and events''' * The 2nd edition of 2025 of [[m:Special:MyLanguage/Afrika Baraza|Afrika Baraza]], a virtual platform for African Wikimedians to connect, will take place on [https://zonestamp.toolforge.org/1747328400 May 15 at 17:00 UTC]. This edition will focus on discussions regarding [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2025-2026|Wikimedia Annual planning and progress]]. * The [[m:Special:MyLanguage/MENA Connect Community Call|MENA Connect Community Call]], a virtual meeting for [[w:en:Middle East and North Africa|MENA]] Wikimedians to connect, will take place on [https://zonestamp.toolforge.org/1747501200 May 17 at 17:00 UTC]. You can [[m:Event:MENA Connect (Wiki_Diwan) APP Call|register now]] to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/20|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W20"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:38, 12 May 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28714188 --> == Wikipedia translation of the week: 2025-21 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lorrin A. Thurston]]'''<br /> <small>''([[:fi:Lorrin Thurston]])&#32;([[:ko:로린 A. 서스턴]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Lorrinandrewsthurston1892.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Lorrin Andrews Thurston''' (July 31, 1858 – May 11, 1931) was a Hawaiian citizen lawyer, politician, and businessman. Thurston played a prominent role in the revolution that overthrew the Hawaiian Kingdom to replace Queen Liliʻuokalani with the Republic of Hawaii, with discreet US support for which Congress much later apologized. He published the Pacific Commercial Advertiser (a forerunner of the present-day Honolulu Star-Advertiser), and owned other enterprises. From 1906 to 1916, he and his network lobbied with national politicians to create a national park to preserve the Hawaiian volcanoes. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:33, 19 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28731710 --> == Tech News: 2025-21 == <section begin="technews-2025-W21"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/21|Translations]] are available. '''Weekly highlight''' * The Editing Team and the Machine Learning Team are working on a new check for newcomers: [[mw:Edit check/Peacock check|Peacock check]]. Using a prediction model, this check will encourage editors to improve the tone of their edits, using artificial intelligence. We invite volunteers to review the first version of the Peacock language model for the following languages: Arabic, Spanish, Portuguese, English, and Japanese. Users from these wikis interested in reviewing this model are [[mw:Edit check/Peacock check/model test|invited to sign up at MediaWiki.org]]. The deadline to sign up is on May 23, which will be the start date of the test. '''Updates for editors''' * From May 20, 2025, [[m:Special:MyLanguage/Oversight policy|oversighters]] and [[m:Special:MyLanguage/Meta:CheckUsers|checkusers]] will need to have their accounts secured with two-factor authentication (2FA) to be able to use their advanced rights. All users who belong to these two groups and do not have 2FA enabled have been informed. In the future, this requirement may be extended to other users with advanced rights. [[m:Special:MyLanguage/Mandatory two-factor authentication for users with some extended rights|Learn more]]. * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] [[m:Special:MyLanguage/Community Wishlist Survey 2023/Multiblocks|Multiblocks]] will begin mass deployment by the end of the month: all non-Wikipedia projects plus Catalan Wikipedia will adopt Multiblocks in the week of May 26, while all other Wikipedias will adopt it in the week of June 2. Please [[m:Talk:Community Wishlist Survey 2023/Multiblocks|contact the team]] if you have concerns. Administrators can test the new user interface now on your own wiki by browsing to [{{fullurl:Special:Block|usecodex=1}} {{#special:Block}}?usecodex=1], and can test the full multiblocks functionality [[testwiki:Special:Block|on testwiki]]. Multiblocks is the feature that makes it possible for administrators to impose different types of blocks on the same user at the same time. See the [[mw:Special:MyLanguage/Help:Manage blocks|help page]] for more information. [https://phabricator.wikimedia.org/T377121] * Later this week, the [[{{#special:SpecialPages}}]] listing of almost all special pages will be updated with a new design. This page has been [[phab:T219543|redesigned]] to improve the user experience in a few ways, including: The ability to search for names and aliases of the special pages, sorting, more visible marking of restricted special pages, and a more mobile-friendly look. The new version can be [https://meta.wikimedia.beta.wmflabs.org/wiki/Special:SpecialPages previewed] at Beta Cluster now, and feedback shared in the task. [https://phabricator.wikimedia.org/T219543] * The [[mw:Special:MyLanguage/Extension:Chart|Chart extension]] is being enabled on more wikis. For a detailed list of when the extension will be enabled on your wiki, please read the [[mw:Special:MyLanguage/Extension:Chart/Project#Deployment Timeline|deployment timeline]]. * [[f:Special:MyLanguage/Wikifunctions:Main Page|Wikifunctions]] will be deployed on May 27 on five Wiktionaries: [[wikt:ha:|Hausa]], [[wikt:ig:|Igbo]], [[wikt:bn:|Bengali]], [[wikt:ml:|Malayalam]], and [[wikt:dv:|Dhivehi/Maldivian]]. This is the second batch of deployment planned for the project. After deployment, the projects will be able to call [[f:Special:MyLanguage/Wikifunctions:Introduction|functions from Wikifunctions]] and integrate them in their pages. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of [[f:Special:MyLanguage/Wikifunctions:Catalogue|a stable and global function]], rather than via a local template. * Later this week, the Wikimedia Foundation will publish a hub for [[diffblog:2024/07/09/on-the-value-of-experimentation/|experiments]]. This is to showcase and get user feedback on product experiments. The experiments help the Wikimedia movement [[diffblog:2023/07/13/exploring-paths-for-the-future-of-free-knowledge-new-wikipedia-chatgpt-plugin-leveraging-rich-media-social-apps-and-other-experiments/|understand new users]], how they interact with the internet and how it could affect the Wikimedia movement. Some examples are [[m:Special:MyLanguage/Future Audiences/Generated Video|generated video]], the [[m:Special:MyLanguage/Future Audiences/Roblox game|Wikipedia Roblox speedrun game]] and [[m:Special:MyLanguage/Future Audiences/Discord bot|the Discord bot]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:29}} community-submitted {{PLURAL:29|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a bug with creating an account using the API, which has now been fixed. [https://phabricator.wikimedia.org/T390751] '''Updates for technical contributors''' * Gadgets and user scripts that interact with [[{{#special:Block}}]] may need to be updated to work with the new [[mw:Special:MyLanguage/Help:Manage blocks|manage blocks interface]]. Please review the [[mw:Help:Manage blocks/Developers|developer guide]] for more information. If you need help or are unable to adapt your script to the new interface, please let the team know on the [[mw:Help talk:Manage blocks/Developers|talk page]]. [https://phabricator.wikimedia.org/T377121] * The <code dir=ltr>mw.title</code> object allows you to get information about a specific wiki page in the [[w:en:Wikipedia:Lua|Lua]] programming language. Starting this week, a new property will be added to the object, named <code dir=ltr>isDisambiguationPage</code>. This property allows you to check if a page is a disambiguation page, without the need to write a custom function. [https://phabricator.wikimedia.org/T71441] * [[File:Octicons-tools.svg|15px|link=|class=skin-invert|Advanced item]] User script developers can use a [[toolforge:gitlab-content|new reverse proxy tool]] to load javascript and css from [[gitlab:|gitlab.wikimedia.org]] with <code dir=ltr>mw.loader.load</code>. The tool's author hopes this will enable collaborative development workflows for user scripts including linting, unit tests, code generation, and code review on <bdi lang="zxx" dir="ltr">gitlab.wikimedia.org</bdi> without a separate copy-and-paste step to publish scripts to a Wikimedia wiki for integration and acceptance testing. See [[wikitech:Tool:Gitlab-content|Tool:Gitlab-content on Wikitech]] for more information. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.2|MediaWiki]] '''Meetings and events''' * The 12th edition of [[m:Special:MyLanguage/Wiki Workshop 2025|Wiki Workshop 2025]], a forum that brings together researchers that explore all aspects of Wikimedia projects, will be held virtually on 21-22 May. Researchers can [https://pretix.eu/wikimedia/wikiworkshop2025/ register now]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/21|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W21"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:13, 19 May 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28724712 --> == Wikipedia translation of the week: 2025-22 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Lamiera bugnata]]'''<br /> <small>''([[:en:Tread plate]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Diamond Plate.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Una '''lamiera bugnata''' o mandorlata è una lamiera di metallo ottenuta dalla laminazione di una bramma attraverso rulli che, tramite punzonatura o goffratura, imprimono sulla lamina rilievi a forma di rombo o ellisse, detti bugne. Nel caso questi rilievi siano alternati singolarmente nei due assi, si parla di lamiera diamantata, mentre se le forme sono predisposte in maniera parallela per formare piccoli quadranti tra di loro tangenti, questo pattern viene identificato con il nome di mandorlato. We tend to ignore the fact that this type of plate is the only reason we don't slip when we walk on steel and wet or frozen surfaces. The Italian article it's short but quite complete, and has just the right amount of citations, unlike other poor languages' versions. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 06:03, 26 May 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28751788 --> == Tech News: 2025-22 == <section begin="technews-2025-W22"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/22|Translations]] are available. '''Weekly highlight''' * A community-wide discussion about a very delicate issue for the development of [[m:Special:MyLanguage/Abstract Wikipedia|Abstract Wikipedia]] is now open on Meta: where to store the abstract content that will be developed through functions from Wikifunctions and data from Wikidata. The discussion is open until June 12 at [[m:Special:MyLanguage/Abstract Wikipedia/Location of Abstract Content|Abstract Wikipedia/Location of Abstract Content]], and every opinion is welcomed. The decision will be made and communicated after the consultation period by the Foundation. '''Updates for editors''' * Since last week, on all wikis except [[phab:T388604|the largest 20]], people using the mobile visual editor will have [[phab:T385851|additional tools in the menu bar]], accessed using the new <code>+</code> toolbar button. To start, the new menu will include options to add: citations, hieroglyphs, and code blocks. Deployment to the remaining wikis is [[phab:T388605|scheduled]] to happen in June. * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] The <code dir=ltr>[[mw:Special:MyLanguage/Help:Extension:ParserFunctions##ifexist|#ifexist]]</code> parser function will no longer register a link to its target page. This will improve the usefulness of [[{{#special:WantedPages}}]], which will eventually only list pages that are the target of an actual red link. This change will happen gradually as the source pages are updated. [https://phabricator.wikimedia.org/T14019] * This week, the Moderator Tools team will launch [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|a new filter to Recent Changes]], starting at Indonesian Wikipedia. This new filter highlights edits that are likely to be reverted. The goal is to help Recent Changes patrollers identify potentially problematic edits. Other wikis will benefit from this filter in the future. * Upon clicking an empty search bar, logged-out users will see suggestions of articles for further reading. The feature will be available on both desktop and mobile. Readers of Catalan, Hebrew, and Italian Wikipedias and some sister projects will receive the change between May 21 and mid-June. Readers of other wikis will receive the change later. The goal is to encourage users to read the wikis more. [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments/Search Suggestions|Learn more]]. * Some users of the Wikipedia Android app can use a new feature for readers, [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/TrivaGame|WikiGames]], a daily trivia game based on real historical events. The release has started as an A/B test, available to 50% of users in the following languages: English, French, Portuguese, Russian, Spanish, Arabic, Chinese, and Turkish. * The [[mw:Special:MyLanguage/Extension:Newsletter|Newsletter extension]] that is available on MediaWiki.org allows the creation of [[mw:Special:Newsletters|various newsletters]] for global users. The extension can now publish new issues as section links on an existing page, instead of requiring a new page for each issue. [https://phabricator.wikimedia.org/T393844] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The previously deprecated <code dir=ltr>[[mw:Special:MyLanguage/Manual:Ipblocks table|ipblocks]]</code> views in [[wikitech:Help:Wiki Replicas|Wiki Replicas]] will be removed in the beginning of June. Users are encouraged to query the new <code dir=ltr>[[mw:Special:MyLanguage/Manual:Block table|block]]</code> and <code dir=ltr>[[mw:Special:MyLanguage/Manual:Block target table|block_target]]</code> views instead. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.3|MediaWiki]] '''Meetings and events''' * [[d:Special:MyLanguage/Event:Wikidata and Sister Projects|Wikidata and Sister Projects]] is a multi-day online event that will focus on how Wikidata is integrated to Wikipedia and the other Wikimedia projects. The event runs from May 29 – June 1. You can [[d:Special:MyLanguage/Event:Wikidata and Sister Projects#Sessions|read the Program schedule]] and [[d:Special:RegisterForEvent/1291|register]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/22|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W22"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:05, 26 May 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28788673 --> == Wikipedia translation of the week: 2025-23 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Angelo azzurro (cocktail)]]'''<br /> <small>''([[:es:Ángel azul (cóctel)]])&#32;([[:fr:Ange bleu (cocktail)]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Angelo Azzurro Cocktail.png|300px|center]] <div style="text-align:left; padding: .4em;"> L''''angelo azzurro''' è un cocktail alcolico italiano. È considerato uno dei cocktail più popolari in Italia negli anni novanta, insieme al B-52 e all'Invisibile. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 05:39, 2 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-23 == <section begin="technews-2025-W23"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/23|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Extension:Chart|Chart extension]] is now available on all Wikimedia wikis. Editors can use this new extension to create interactive data visualizations like bar, line, area, and pie charts. Charts are designed to replace many of the uses of the legacy [[mw:Special:MyLanguage/Extension:Graph|Graph extension]]. '''Updates for editors''' * It is now easier to configure automatic citations for your wiki within the visual editor's [[mw:Special:MyLanguage/Citoid/Enabling Citoid on your wiki|citation generator]]. Administrators can now set a default template by using the <code dir=ltr>_default</code> key in the local <bdi lang="en" dir="ltr">[[MediaWiki:Citoid-template-type-map.json]]</bdi> page ([[mw:Special:Diff/6969653/7646386|example diff]]). Setting this default will also help to future-proof your existing configurations when [[phab:T347823|new item types]] are added in the future. You can still set templates for individual item types as they will be preferred to the default template. [https://phabricator.wikimedia.org/T384709] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Starting the week of June 2, bots logging in using <code dir=ltr>action=login</code> or <code dir=ltr>action=clientlogin</code> will fail more often. This is because of stronger protections against suspicious logins. Bots using [[mw:Special:MyLanguage/Manual:Bot passwords|bot passwords]] or using a loginless authentication method such as [[mw:Special:MyLanguage/OAuth/Owner-only consumers|OAuth]] are not affected. If your bot is not using one of those, you should update it; using <code dir=ltr>action=login</code> without a bot password was deprecated [[listarchive:list/wikitech-l@lists.wikimedia.org/message/3EEMN7VQX5G7WMQI5K2GP5JC2336DPTD/|in 2016]]. For most bots, this only requires changing what password the bot uses. [https://phabricator.wikimedia.org/T395205] * From this week, Wikimedia wikis will allow ES2017 features in JavaScript code for official code, gadgets, and user scripts. The most visible feature of ES2017 is <bdi lang="zxx" dir="ltr"><code>async</code>/<code>await</code></bdi> syntax, allowing for easier-to-read code. Until this week, the platform only allowed up to ES2016, and a few months before that, up to ES2015. [https://phabricator.wikimedia.org/T381537] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.4|MediaWiki]] '''Meetings and events''' * Scholarship applications to participate in the [[m:Special:MyLanguage/GLAM Wiki 2025|GLAM Wiki Conference 2025]] are now open. The conference will take place from 30 October to 1 November, in Lisbon, Portugal. GLAM contributors who lack the means to support their participation can [[m:Special:MyLanguage/GLAM Wiki 2025/Scholarships|apply here]]. Scholarship applications close on June 7th. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/23|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W23"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:55, 2 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28819186 --> == Wikipedia translation of the week: 2025-24 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:fi:Kotiryssä]]'''<br /> <small>''([[:en:Kotiryssä]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> A '''kotiryssä''' (jocular Finnish: one’s home Russky or home Russian) was a Soviet or Russian contact person of a Finnish politician, bureaucrat, businessman or other important person. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:33, 9 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-24 == <section begin="technews-2025-W24"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/24|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Trust and Safety Product|Trust and Safety Product team]] is finalizing work needed to roll out [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] on large Wikipedias later this month. The team has worked with stewards and other users with extended rights to predict and address many use cases that may arise on larger wikis, so that community members can continue to effectively moderate and patrol temporary accounts. This will be the second of three phases of deployment – the last one will take place in September at the earliest. For more information about the recent developments on the project, [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Updates|see this update]]. If you have any comments or questions, write on the [[mw:Talk:Trust and Safety Product/Temporary Accounts|talk page]], and [[m:Event:CEE Catch up Nr. 10 (June 2025)|join a CEE Catch Up]] this Tuesday. '''Updates for editors''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] The [[mw:Special:MyLanguage/Help:Watchlist expiry|watchlist expiry]] feature allows editors to watch pages for a limited period of time. After that period, the page is automatically removed from your watchlist. Starting this week, you can set a preference for the default period of time to watch pages. The [[Special:Preferences#mw-prefsection-watchlist-pageswatchlist|preferences]] also allow you to set different default watch periods for editing existing pages, pages you create, and when using rollback. [https://phabricator.wikimedia.org/T265716] [[File:Talk pages default look (April 2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * The appearance of talk pages will change at almost all Wikipedias ([[m:Special:MyLanguage/Tech/News/2024/19|some]] have already received this design change, [[phab:T379264|a few]] will get these changes later). You can read details about the changes [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|on ''Diff'']]. It is possible to opt out of these changes [[Special:Preferences#mw-prefsection-editing-discussion|in user preferences]] ("{{int:discussiontools-preference-visualenhancements}}"). [https://phabricator.wikimedia.org/T319146][https://phabricator.wikimedia.org/T392121] * Users with specific extended rights (including administrators, bureaucrats, checkusers, oversighters, and stewards) can now have IP addresses of all temporary accounts [[phab:T358853|revealed automatically]] during time-limited periods where they need to combat high-speed account-hopping vandalism. This feature was requested by stewards. [https://phabricator.wikimedia.org/T386492] * This week, the Moderator Tools and Machine Learning teams will continue the rollout of [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|a new filter to Recent Changes]], releasing it to several more Wikipedias. This filter utilizes the Revert Risk model, which was created by the Research team, to highlight edits that are likely to be reverted and help Recent Changes patrollers identify potentially problematic contributions. The feature will be rolled out to the following Wikipedias: {{int:project-localized-name-afwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-bewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-bnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cywiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hawwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-iswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-simplewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}. The rollout will continue in the coming weeks to include [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|the rest of the Wikipedias in this project]]. [https://phabricator.wikimedia.org/T391964] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * AbuseFilter editors active on Meta-Wiki and large Wikipedias are kindly asked to update AbuseFilter to make it compatible with temporary accounts. A link to the instructions and the private lists of filters needing verification are [[phab:T369611|available on Phabricator]]. * Lua modules now have access to the name of a page's associated thumbnail image, and on [https://gerrit.wikimedia.org/g/operations/mediawiki-config/+/2e4ab14aa15bb95568f9c07dd777065901eb2126/wmf-config/InitialiseSettings.php#10849 some wikis] to the WikiProject assessment information. This is possible using two new properties on [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#added-by-extensions|mw.title objects]], named <code dir=ltr>pageImage</code> and <code dir=ltr>pageAssessments</code>. [https://phabricator.wikimedia.org/T131911][https://phabricator.wikimedia.org/T380122] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.5|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/24|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W24"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:17, 10 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28846858 --> == Wikipedia translation of the week: 2025-25 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Future self]]'''<br /> <small>''([[:pl:Przyszła jaźń]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> In the psychology of self, the '''future self''' concerns the processes and consequences associated with thinking about oneself in the future. People think about their future selves similarly to how they think about other people. The extent to which people feel psychologically connected (e.g., similarity, closeness) to their future self influences how well they treat their future self. When people feel connected to their future self, they are more likely to save for retirement, make healthy decisions, and avoid ethical transgressions. Interventions that increase feelings of connectedness with future selves can improve future-oriented decision making across these domains. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 16 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-25 == <section begin="technews-2025-W25"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/25|Translations]] are available. '''Updates for editors''' * You can [https://wikimediafoundation.limesurvey.net/359761?lang=en nominate your favorite tools] for the sixth edition of the [[m:Special:MyLanguage/Coolest Tool Award|Coolest Tool Award]]. Nominations are anonymous and will be open until June 25. You can re-use the survey to nominate multiple tools. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:33}} community-submitted {{PLURAL:33|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.6|MediaWiki]] '''In depth''' * Foundation staff and technical volunteers use Wikimedia APIs to build the tools, applications, features, and integrations that enhance user experiences. Over the coming years, the MediaWiki Interfaces team will be investing in Wikimedia web (HTTP) APIs to better serve technical volunteer needs and protect Wikimedia infrastructure from potential abuse. You can [https://techblog.wikimedia.org/2025/06/12/apis-as-a-product-investing-in-the-current-and-next-generation-of-technical-contributors/ read more about their plans to evolve the APIs in this Techblog post]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/25|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W25"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:39, 16 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28870688 --> == Wikipedia translation of the week: 2025-26 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pictorial map]]'''<br /> <small>''([[:fa:نقشه تصویری]])&#32;([[:ja:絵地図]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Blake Britain Spearhead of Attack.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> '''Pictorial maps''' (also known as illustrated maps, panoramic maps, perspective maps, bird's-eye view maps, and geopictorial maps) depict a given territory with a more artistic rather than technical style. It is a type of map in contrast to road map, atlas, or topographic map. The cartography can be a sophisticated 3-D perspective landscape or a simple map graphic enlivened with illustrations of buildings, people and animals. They can feature all sorts of varied topics like historical events, legendary figures or local agricultural products and cover anything from an entire continent to a college campus. Drawn by specialized artists and illustrators, pictorial maps are a rich, centuries-old tradition and a diverse art form that ranges from cartoon maps on restaurant placemats to treasured art prints in museums. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:18, 23 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-26 == <section begin="technews-2025-W26"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/26|Translations]] are available. '''Weekly highlight''' * This week, the Moderator Tools and Machine Learning teams will continue the rollout of [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|a new filter to Recent Changes]], releasing it to the third and last batch of Wikipedias. This filter utilizes the Revert Risk model, which was created by the Research team, to highlight edits that are likely to be reverted and help Recent Changes patrollers identify potentially problematic contributions. The feature will be rolled out to the following Wikipedias: {{int:project-localized-name-azwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-lawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mkwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-mrwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nnwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-pawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-swwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-tlwiki/en}}. The rollout will continue in the coming weeks to include [[mw:Special:MyLanguage/2025 RecentChanges Language Agnostic Revert Risk Filtering|the rest of the Wikipedias in this project]]. [https://phabricator.wikimedia.org/T391964] '''Updates for editors''' * Last week, [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] were rolled out on Czech, Korean, and Turkish Wikipedias. This and next week, deployments on larger Wikipedias will follow. [[mw:Talk:Trust and Safety Product/Temporary Accounts|Share your thoughts]] about the project. [https://phabricator.wikimedia.org/T340001] * Later this week, the Editing team will release [[mw:Special:MyLanguage/Help:Edit check#Multi check|Multi Check]] to all Wikipedias (except English Wikipedia). This feature shows multiple [[mw:Special:MyLanguage/Help:Edit check#Reference check|Reference checks]] within the editing experience. This encourages users to add citations when they add multiple new paragraphs to a Wikipedia article. This feature was previously available as an A/B test. [https://analytics.wikimedia.org/published/reports/editing/multi_check_ab_test_report_final.html#summary-of-results The test shows] that users who are shown multiple checks are 1.3 times more likely to add a reference to their edit, and their edit is less likely to be reverted (-34.7%). [https://phabricator.wikimedia.org/T395519] * A few pages need to be renamed due to software updates and to match more recent Unicode standards. All of these changes are related to title-casing changes. Approximately 71 pages and 3 files will be renamed, across 15 wikis; the complete list is in [[phab:T396903|the task]]. The developers will rename these pages next week, and they will fix redirects and embedded file links a few minutes later via a system settings update. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:24}} community-submitted {{PLURAL:24|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that had caused pages to scroll upwards when text near the top was selected. [https://phabricator.wikimedia.org/T364023] '''Updates for technical contributors''' * Editors can now use Lua modules to filter and transform tabular data for use with [[mw:Special:MyLanguage/Extension:Chart|Extension:Chart]]. This can be used for things like selecting a subset of rows or columns from the source data, converting between units, statistical processing, and many other useful transformations. [[mw:Special:MyLanguage/Extension:Chart/Transforms|Information on how to use transforms is available]]. [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Chart/Project/Updates] * The <code dir=ltr>all_links</code> variable in [[Special:AbuseFilter|AbuseFilter]] is now renamed to <code dir=ltr>new_links</code> for consistency with other variables. Old usages will still continue to work. [https://phabricator.wikimedia.org/T391811] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.7|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Growth/Newsletters/34|Growth newsletter]] is available. It includes: the recent updates for the "Add a Link" Task, two new Newcomer Engagement Features, and updates to Community Configuration. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/26|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W26"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:21, 23 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28870688 --> == Wikipedia translation of the week: 2025-27 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Queen Elizabeth University Hospital]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:QEUH.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Queen Elizabeth University Hospital''' (QEUH) is a 1,677-bed acute hospital located in Govan, in the south-west of Glasgow, Scotland. The hospital is built on the site of the former Southern General Hospital and opened at the end of April 2015. The hospital comprises a 1,109-bed adult hospital, a 256-bed children's hospital and two major Emergency Departments; one for adults and one for children. There is also an Immediate Assessment Unit for local GPs and out-of-hours services, to send patients directly, without having to be processed through the Emergency Department. The retained buildings from the former Southern General Hospital include the Maternity Unit, the Institute of Neurological Sciences, the Langlands Unit for medicine of the elderly and the laboratory. The whole facility is operated by NHS Greater Glasgow and Clyde, and is one of the largest acute hospital campuses in Europe. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:05, 30 June 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-27 == <section begin="technews-2025-W27"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/27|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] has been enabled on all Wikipedias. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. The extension has three features: [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], [[m:Special:MyLanguage/CampaignEvents/Collaboration list|Collaboration List]], and [[m:Campaigns/Foundation Product Team/Invitation list|Invitation List]]. To request the extension for your wiki, visit the [[m:Special:MyLanguage/CampaignEvents/Deployment status#How to Request the CampaignEvents Extension for your wiki|Deployment information page]]. '''Updates for editors''' * AbuseFilter maintainers can now [[mw:Special:MyLanguage/Extension:IPReputation/AbuseFilter variables|match against IP reputation data]] in [[mw:Special:MyLanguage/Extension:AbuseFilter|AbuseFilters]]. IP reputation data is information about the proxies and VPNs associated with the user's IP address. This data is not shown publicly and is not generated for actions performed by registered accounts. [https://phabricator.wikimedia.org/T354599] * Hidden content that is within [[mw:Special:MyLanguage/Manual:Collapsible elements|collapsible parts of wikipages]] will now be revealed when someone searches the page using the web browser's "Find in page" function (Ctrl+F or ⌘F) in supporting browsers. [https://phabricator.wikimedia.org/T327893][https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/hidden#browser_compatibility] * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] A new feature, called [[mw:Special:MyLanguage/Help:TemplateData/Template discovery|Favourite Templates]], will be deployed later this week on all projects (except English Wikipedia, which will receive the feature next week), following a piloting phase on Polish and Arabic Wikipedia, and Italian and English Wikisource. The feature will provide a better way for new and experienced contributors to recall and discover templates via the template dialog, by allowing users to put templates on a special "favourite list". The feature works with both the visual editor and the wikitext editor. The feature is a [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|community wishlist focus area]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that had caused some Notifications to be sent multiple times. [https://phabricator.wikimedia.org/T397103] '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.8|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/27|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W27"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:41, 30 June 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28917415 --> == Wikipedia translation of the week: 2025-28 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Non-constituency Member of Parliament]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> A '''Non-constituency Member of Parliament''' (NCMP) is a member of an opposition political party in Singapore who, as stipulated in Article 39 of the Constitution and the Parliamentary Elections Act, is declared to have been elected a Member of Parliament (MP) without constituency representation, despite having lost in a general election, by virtue of having been one of the opposition candidates with the highest vote shares among the unelected. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:10, 7 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28788623 --> == Tech News: 2025-28 == <section begin="technews-2025-W28"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/28|Translations]] are available. '''Weekly highlight''' * [[mw:Special:MyLanguage/Help:Temporary accounts|Temporary accounts]] have been rolled out on 18 large and medium-sized Wikipedias, including German, Japanese, French, and Chinese. Now, about 1/3 of all logged-out activity across wikis is coming from temporary accounts. Users involved in patrolling may be interested in two new documentation pages: [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Access to IP|Access to IP]], explaining everything related to access to temporary account IP addresses, and [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts/Repository|Repository]] with a list of new gadgets and user scripts. '''Updates for editors''' * Anyone can play an experimental new game, [[mw:Special:MyLanguage/New Engagement Experiments/WikiRun|WikiRun]], that lets you race through Wikipedia by clicking from one article to another, aiming to reach a target page in as few steps and in as little time as possible. The project's goal is to explore new ways of engaging readers. [https://wikirun-game.toolforge.org/ Try playing the game] and let the team know what you think [[mw:Talk:New Engagement Experiments/WikiRun|on the talk page]]. * Users of the Wikipedia Android app in some languages can now play the new [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/TrivaGame|trivia game]]. ''Which came first?'' is a simple history game where you guess which of two events happened earlier on today's date. It was previously available as an A/B test. It is now available to all users in English, German, French, Spanish, Portuguese, Russian, Arabic, Turkish, and Chinese. The goal of the feature is to help engage with new generations of readers. [https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2025/22] * Users of the iOS Wikipedia App in some languages may see a new tabbed browsing feature that enables you to open multiple tabs while reading. This feature makes it easier to explore related topics and switch between articles. The A/B test is currently running in Arabic, English, and Japanese in selected regions. More details are available on the [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Tabbed Browsing (Tabs)|Tabbed Browsing project page]]. * Bureaucrats on Wikimedia wikis can now use [[{{#special:VerifyOATHForUser}}]] to check if users have enabled [[mw:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]]. [https://phabricator.wikimedia.org/T265726] * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] A new feature related to [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|Template Recall and Discovery]] will be deployed later this week to all Wikimedia projects: a [[mw:Special:MyLanguage/Help:TemplateData/Template discovery#Template categories|template category browser]] will be introduced to assist users in finding templates to put in their “favourite” list. The browser will allow users to browse a list of templates which have been organised into a given category tree. The feature has been requested by the community [[m:Special:MyLanguage/Community Wishlist/Wishes/Select templates by categories|through the Community Wishlist]]. * It is now possible to access watchlist preferences from the watchlist page. Also the redundant button to edit the watchlist has been removed. [https://www.mediawiki.org/wiki/Moderator_Tools/Watchlist] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * As part of [[mw:MediaWiki_1.44|MediaWiki 1.44]] there is now a unified built-in Notifications system that makes it easier for developers to send, manage, and customize notifications. Check out the updated documentation at [[mw:Manual:Notifications|Manual:Notifications]], information about migration in [[phab:T388663|T388663]] and details on deprecated hooks in [[phab:T389624|T389624]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.9|MediaWiki]] '''Meetings and events''' * [[d:Special:MyLanguage/Event:WikidataCon 2025|WikidataCon 2025]], the conference dedicated to Wikidata is now open for [https://pretalx.com/wikidatacon-2025/cfp session proposals] and for [[d:Special:RegisterForEvent/1340|registration]]. This year's event will be held online from October 31 – November 02 and will explore on the theme of "Connecting People through Linked Open Data". '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/28|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W28"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:06, 8 July 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28930584 --> == Wikipedia translation of the week: 2025-29 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Immunolabeling]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Immunolabeling process image.png|300px|center]] <div style="text-align:left; padding: .4em;"> '''Immunolabeling''' is a biochemical process that enables the detection and localization of an antigen to a particular site within a cell, tissue, or organ. Antigens are organic molecules, usually proteins, capable of binding to an antibody. These antigens can be visualized using a combination of antigen-specific antibody as well as a means of detection, called a tag, that is covalently linked to the antibody <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> ---[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 13:44, 14 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28945528 --> == Tech News: 2025-29 == <section begin="technews-2025-W29"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/29|Translations]] are available. '''Updates for editors''' * [[mw:Special:MyLanguage/Help:TemplateData/Template discovery#Featured templates|Featured templates]], a new feature related to [[m:Special:MyLanguage/Community Wishlist/Focus areas/Template recall and discovery|Template Recall and Discovery]] will be deployed this week to all Wikimedia projects: With this feature, editors will be able to quickly access a list of templates that are likely to be useful. These templates will be displayed in a list, under the "featured" tab of the template discovery interface. Administrators can define the list via the Community Configuration interface. The feature fulfills a request by the community [[m:Special:MyLanguage/Community Wishlist/Wishes/Easy access Templates|through the Community Wishlist]]. [https://phabricator.wikimedia.org/T367428][https://phabricator.wikimedia.org/T392896] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the request to add Malayalam fonts in the [[oldWikisource:Special:MyLanguage/Wikisource:WS Export|Wikisource Book Export Tool]] was resolved and now, the rendering of Malayalam letters in exported Wikisource books are accurate. [https://phabricator.wikimedia.org/T374457] '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.10|MediaWiki]] '''In depth''' * Developers, designers, and all Wikimedians are invited to [https://phabricator.wikimedia.org/project/board/7953/ submit a project idea] for the Wikimania Hackathon 2025. Read [https://diff.wikimedia.org/2025/06/30/call-for-projects-wikimania-hackathon-2025-is-coming-to-nairobi/ this Diff blog post] for more details. '''Meetings and events''' * [[m:WikiIndaba conference 2025|WikiIndaba 2025]] scholarship application and program submission is open until 23:59 GMT on July 20. WikiIndaba is a regional conference for African Wikimedians both on the continent and in the diaspora to unite and grow together. Submit [https://docs.google.com/forms/d/e/1FAIpQLSdJTv68R1OPASXXDfpIl8EWiMLTM-TDwh6_5gNVvFuWccFZ2Q/viewform your scholarship application] and [https://ee.kobotoolbox.org/x/BI3omIfH program proposal] now! * [https://br.wikimedia.org/wiki/WikiCon_Brasil_2025 WikiCon Brasil 2025] will take place on July 19-20 in Salvador, Bahia, Brazil. The Brazilian community members are encouraged to register and attend! '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/29|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W29"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:10, 14 July 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=28980963 --> == Wikipedia translation of the week: 2025-30 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Vespa analis]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Plumpy hornet on the ground - 1.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Vespa analis''''', the yellow-vented hornet, is a species of common hornet found in Southeast Asia <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:28, 21 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=28984647 --> == Tech News: 2025-30 == <section begin="technews-2025-W30"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/30|Translations]] are available. '''Updates for editors''' * The Translation Suggestions feature in the [[mw:Special:MyLanguage/Content translation|Content Translation tool]] now has another level of article filters added to the "[https://en.wikipedia.org/w/index.php?title=Special:ContentTranslation&filter-type=automatic&filter-id=previous-edits&active-list=suggestions&from=en&to=fi#/ ... More]" category. Translators who use the Suggestions feature can now select and receive article suggestions that are customized to geographical locations of their interest using the new "{{int:Cx-sx-suggestions-filters-tab-regions}}" filter. [https://phabricator.wikimedia.org/T113257] * Administrators can now limit "Add a Link" to newcomers. The [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|"Add a Link"]] Structured Task [[mw:Special:MyLanguage/Growth/Constructive activation experimentation#Enwiki A/B test & "Add a Link" Improvements (Wiki Experiences 1.2.11 & 1.2.16)|helps new account holders start editing]], but some communities have requested the ability to restrict it to its intended audience: newcomers. Administrators can configure this setting within the [[Special:CommunityConfiguration/GrowthSuggestedEdits|Community Configuration]] feature. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:29}} community-submitted {{PLURAL:29|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * For AbuseFilter editors on [[phab:T392144|some wikis]], it is now possible to filter edits based on the RevertRisk score of the edit being attempted. It is only populated if the action being evaluated is an edit. For more information, please see the [[mw:Special:MyLanguage/Extension:ORES/AbuseFilter variables#What variables are available for use|ORES/AbuseFilter variables]] documentation. * The [[mw:Special:MyLanguage/Beta Cluster|Beta Cluster]] wikis have [[listarchive:list/wikitech-l@lists.wikimedia.org/thread/YDABPV75LADRQCXMJAFWUP256N4EQ25B/|been moved]] from <code dir=ltr>beta.wmflabs.org</code> to <code dir=ltr>beta.wmcloud.org</code>. Users may need to update URLs in any tools, or in their password managers. Any related issues can be [[phab:T289318|reported in the task]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.11|MediaWiki]] '''Meetings and events''' * [[m:Special:MyLanguage/WikiCite 2025|WikiCite 2025]] will take place from 29–31 August, both online and in-person in Bern, Switzerland. The event's goals are to reconnect communities, institutions, and individuals working with open citations, bibliographic data, and the Wikidata/Wikibase ecosystem. Registration is open and the call for proposals will be announced soon. [https://lists.wikimedia.org/hyperkitty/list/wikidata@lists.wikimedia.org/message/KQZUG3ETKLBWPBYSB2YAWZIRPWHS24TG/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/30|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W30"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:43, 21 July 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29005283 --> == Wikipedia translation of the week: 2025-31 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Fernando de Noronha Marine National Park]]'''<br /> <small>''([[:pt:Parque Nacional Marinho de Fernando de Noronha]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Baía dos Porcos - Fernando de Noronha (32811749914).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Fernando de Noronha Marine National Park''' (Portuguese: Parque Nacional Marinho de Fernando de Noronha) is a national park in the state of Pernambuco, Brazil. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:40, 28 July 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29047614 --> == Tech News: 2025-31 == <section begin="technews-2025-W31"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/31|Translations]] are available. '''Weekly highlight''' * The Community Tech team will be focusing on wishes related to Watchlists and Recent Changes pages, over the next few months. They are looking for feedback. Please [[m:Special:MyLanguage/Community Wishlist/Updates#July 24, 2025: Watchlists and Recent Changes pages|read the latest update]], and if you have ideas, please [[m:Special:MyLanguage/Community Wishlist|submit a wish]] on the topic. '''Updates for editors''' * The Wikimedia Commons community has decided to block [[:mw:Special:MyLanguage/Upload dialog|cross-wiki uploads]] to Wikimedia Commons, for all users without autoconfirmed rights on that wiki, starting on August 16. This is because of [[:c:Commons:Cross-wiki media upload tool/History|widespread problems]] related to files that are uploaded by newcomers. Users who are affected by this will get an error message with a link to the less restrictive UploadWizard on Commons. Please help translating the [[:c:Special:MyLanguage/MediaWiki:Abusefilter-disallowed-cross-wiki-upload|message]] or give feedback on the message text. Please also update your local help pages to explain this restriction. [https://phabricator.wikimedia.org/T370598] * On wikis with temporary accounts enabled and Meta-Wiki, administrators may now set up a footer for the Special:Contributions pages of temporary accounts, similar to those which can be shown on IP and user-account pages. They may do it by creating the page named <code dir=ltr>MediaWiki:Sp-contributions-footer-temp</code>. [https://phabricator.wikimedia.org/T398347] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.12|MediaWiki]] '''Meetings and events''' * [[wmania:Special:MyLanguage/2025:Wikimania|Wikimania 2025]] will run from August 6–9. The [https://wikimedia.eventyay.com/talk/wikimania2025/schedule/ program is available] for you to plan which sessions you want to attend. Most sessions will be live-streamed, with exceptions for those that show the "no camera" icon. If you are joining online to watch live-streams and use the interactive features, please [[wmania:Special:MyLanguage/2025:Registration|register]] for a free virtual ticket. For example, you may be interested in technical sessions such as: ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/KFEFVG/ Temporary Accounts: Enhancing privacy for our unregistered editors] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/TVCVAB/ Building a Sustainable Future for Wikimedia Contributors] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/WTRQCJ/ A dozen visions for wikitext!] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/8YKKP9/ Coordinate Across Stakeholders with the Product and Technology Advisory Council] * The [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Fall 2025|MediaWiki Users and Developers Conference, Fall 2025]] will be held 28–30 October 2025 in Hanover, Germany. This event is organized by and for the third-party MediaWiki community. You can propose sessions and register to attend. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/31|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W31"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:27, 29 July 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29051727 --> == Wikipedia translation of the week: 2025-32 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Xie Zhiliu]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Xie Zhiliu''' (Chinese: 谢稚柳; 1910–1997) was a leading traditional painter, calligrapher, and art connoisseur of modern China. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:21, 4 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29077280 --> == Tech News: 2025-32 == <section begin="technews-2025-W32"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/32|Translations]] are available. '''Updates for editors''' * Editors can now enable the [[mw:Special:MyLanguage/Product Safety and Integrity/Anti-abuse signals/User Info|User Info card]]. This feature adds an icon next to usernames on history pages and similar user-contribution log pages. When you tap or click on the icon, it displays data related to that user account such as the number of edits, reverted edits, blocks, and more. It's part of a broader project to make it easier for moderators to evaluate account trustworthiness. The feature can be enabled in [[testwiki:Special:GlobalPreferences#mw-prefsection-rendering|your global preferences]], and later this week it will be available in local preferences. [https://phabricator.wikimedia.org/T386439] * Everybody is invited to share comments on [[m:Special:MyLanguage/CampaignEvents/Collaborative contributions|Collaborative Contributions]], a project recently launched by the [[m:Special:MyLanguage/Connection Team|Connection team]]. The project aims to create a new way to display the impact of collaborative editing activities (such as edit-a-thons, backlog drives, and WikiProjects) on the wikis. Post your comments on the [[m:Talk:CampaignEvents/Collaborative contributions|project talk page]]. [https://phabricator.wikimedia.org/T378035] * Administrators can now define the default block duration for temporary accounts. To do that, they need to create a page named <code dir=ltr>MediaWiki:Ipb-default-expiry-temporary-account</code> and use a value defined in <code dir=ltr>MediaWiki:Ipboptions</code>. This allows administrators to easily block temporary accounts for 90 days, which is functionally equivalent to an indefinite block. The advantage of this solution is that it does not clutter Special:BlockList. [[mw:Special:MyLanguage/Manual:Block and unblock#Default block duration options|More documentation]] is available. [https://phabricator.wikimedia.org/T398626] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Gadgets can now include <code dir=ltr>.vue</code> files. This makes it easier to develop modern user interfaces using [[mw:Vue.js|Vue.js]], in particular using [[mw:Special:MyLanguage/Codex|Codex]], the official design system of Wikimedia. [[wmdoc:codex/latest/icons/overview.html|Codex icons]] can be loaded through the gadget definition. [[mw:Special:MyLanguage/Extension:Gadgets#Pages|The documentation]] has examples. For user scripts that use Vue.js, an [[mw:API:CodexIcons|API module]] now exists to load Codex icons. [https://phabricator.wikimedia.org/T340460][https://phabricator.wikimedia.org/T311099] * Module developers can now use a [[mw:Help:Extension:Translate/Message Bundles/Lua reference|Lua interface]] to simplify the preparation of Lua modules for translation on Meta-Wiki. This improvement makes it easier for translators to find and edit module strings without dealing with raw Lua code. It helps prevent mistakes that could break the module during translation. Module developers and translators are invited to [[commons:File:Translatable modules video demo July 2025.webm|watch the demo video]], read more about [[mw:Special:MyLanguage/Translatable modules|translatable modules]] to understand how it works, refer to Meta-Wiki's [[m:Module:User Wikimedia project|Module:User Wikimedia project]] for example usage, and [[mw:Talk:Translatable modules|share their feedback]] on how well it addresses the challenges in their workflow. The interface still has some performance issues, so it should not be used in widely used modules yet. [https://phabricator.wikimedia.org/T359918] * Developers of external tools that connect to Wikimedia pages must set a user-agent that complies with [[foundation:Special:MyLanguage/Policy:Wikimedia Foundation User-Agent Policy|the user-agent policy]]. This policy will start to be more strongly enforced in August because of external crawlers that are [[diffblog:2025/04/01/how-crawlers-impact-the-operations-of-the-wikimedia-projects/|overusing]] Wikimedia's resources. Tools that are hosted on Wikimedia's Toolforge or Cloud VPS will not be affected by this for now, but should still set a user-agent. [[phab:T400119|More technical details are available]], and related questions are welcome in that task. * Parsoid Read Views is going to be rolling out to some smaller Wikipedias over the next few weeks, following the successful transition of Wikivoyages and Wiktionaries to Parsoid Read Views. For more information, see the [[mw:Special:MyLanguage/Parsoid/Parser Unification|Parsoid/Parser Unification]] project page. [https://phabricator.wikimedia.org/project/profile/7694/] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.13|MediaWiki]] '''Meetings and events''' * [[wmania:Special:MyLanguage/2025:Wikimania|Wikimania 2025]] will run from August 6–9. The [https://wikimedia.eventyay.com/talk/wikimania2025/schedule/ program is available] for you to plan which sessions you want to attend. Most sessions will be live-streamed, with exceptions for those that show the "no camera" icon. If you are joining online to watch live-streams and use the interactive features, please [[wmania:Special:MyLanguage/2025:Registration|register]] for a free virtual ticket. For example, you may be interested in technical sessions such as: ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/GEH9DH/ Wikimedia’s knowledge infrastructure in a changing internet: Establishing sustainable pathways for content reuse] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/7ELN9Q/ Wikifunctions is coming soon to a wiki near you!] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/ZMGVJV/ Shaping the Future of Wikipedia’s Reader Experience] ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/KCKTFZ/ Making Wikipedia More Readable: What Comes Next] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/32|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W32"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 03:41, 5 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29083927 --> == Wikipedia translation of the week: 2025-33 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lethocerus patruelis]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Lethocerus patruelis.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Lethocerus patruelis''''' is a giant water bug in the family Belostomatidae. It is native to southeastern Europe, through Southwest Asia, to Pakistan, India and Burma. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:20, 11 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29085671 --> == Tech News: 2025-33 == <section begin="technews-2025-W33"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/33|Translations]] are available. '''Updates for editors''' * The WikiEditor toolbar now includes [[mw:Special:MyLanguage/Help:Extension:WikiEditor#Keyboard shortcuts|its keyboard shortcuts]] in the tooltips for its buttons. This will help to improve the discoverability of this feature. [https://phabricator.wikimedia.org/T400583] * The [[m:Special:MyLanguage/Product and Technology Advisory Council|Product and Technology Advisory Council]] published a set of [[m:Special:MyLanguage/Product and Technology Advisory Council/August 2025 draft PTAC proposals for feedback|proposed experiments]] the Wikimedia Foundation can try to improve communication with community. Feedback on the proposals are welcomed until August 22 on [[m:Talk:Product and Technology Advisory Council/August 2025 draft PTAC proposals for feedback|this talk page]]. * The search bar on the Minerva skin (mobile) has been updated to use the same type-ahead search component that is used on the Vector 2022 skin. There are no changes in search functionality but there are minor visual changes. Specifically, the close-search button has been changed from an "X" to a back arrow. This helps to distinguish it from the other "X" button that is used to clear any text. [https://phabricator.wikimedia.org/T393944] * Editors on some wikis will see a new toggle for "Group results by page" on watchlist, related changes, and recent changes pages. This is [[mw:Special:MyLanguage/Moderator Tools/Watchlist/Experiment|an A/B experiment]] that is planned to start on August 11, and will run for 3–6 weeks on the Bengali, Chinese, Czech, French, Greek, Portuguese, and Urdu Wikipedias. The experiment will examine how making this feature more discoverable might affect editors' ability to find the edits they are looking for. [https://phabricator.wikimedia.org/T396789] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * The multiwiki datasets of [[:wikt:en:Module:Unicode data|Unicode data]] have been moved to [[c:Category:Unicode Module Datasets|Category:Unicode Module Datasets]] on Wikimedia Commons, to follow the idea of "One common data source, multiple local wikis". Most wikis have been updated to use the Commons version. You can ask questions at [[c:Category talk:Unicode Module Datasets|the talkpage]]. [https://en.wiktionary.org/wiki/Module_talk:Unicode_data#Data_from_commons] * Lua code can add warnings when something is wrong, by using the <code dir=ltr>mw.addWarning()</code> function. It is now possible to add more than one warning, instead of new warnings replacing old ones. If you maintain a Lua module that used warnings, you should check it still works as expected. [https://phabricator.wikimedia.org/T398390] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.14|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/33|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W33"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:30, 11 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29106516 --> == Wikipedia translation of the week: 2025-34 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Ikiza]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:CIA map of Burundi and surrounding countries during 1972 killings.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Ikiza''' (variously translated from Kirundi as the Catastrophe, the Great Calamity, and the Scourge), or the Ubwicanyi (Killings), was a series of mass killings—often characterised as a genocide—which were committed in Burundi in 1972 by the Tutsi-dominated army and government, primarily against educated and elite Hutus who lived in the country. Conservative estimates place the death toll of the event between 100,000 and 150,000 killed, while some estimates of the death toll go as high as 300,000. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:43, 18 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29115447 --> == Tech News: 2025-34 == <section begin="technews-2025-W34"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/34|Translations]] are available. '''Updates for editors''' * Later this week, people who are logged-in and have the "[[mw:Special:MyLanguage/Talk pages project/Feature summary|Discussion tools]]" [[Special:Preferences#mw-prefsection-betafeatures|Beta Feature]] enabled will gain the ability to "Thank" individual comments directly from talk pages, rather than needing to navigate to page history. [[mw:Special:MyLanguage/Talk pages project/Feature summary#Comment actions|Learn more about this feature]]. [https://phabricator.wikimedia.org/T400849] * An A/B test comparing two versions of the desktop donate link launched on testwiki on 12 August and on English Wikipedia 14 August for 0.1% of logged out users on the desktop site. The experiment will run for three weeks, ending on 12 September. [https://phabricator.wikimedia.org/T395716] * An A/A test to measure the baseline for reader retention was launched 12 August using [[wikitech:Experimentation Lab|Experimentation Lab]]. This measures the percentage of users who revisit a wiki after their initial visit over a 14-day period. No visual changes are expected. The experiment will run through 31 August. [https://phabricator.wikimedia.org/T399227] * Five new wikis have been created: ** a {{int:project-localized-name-group-wikisource/en}} in [[d:Q34057|Tagalog]] ([[s:tl:|<code>s:tl:</code>]]) [https://phabricator.wikimedia.org/T388639] ** a {{int:project-localized-name-group-wikisource/en}} in [[d:Q36213|Madurese]] ([[s:mad:|<code>s:mad:</code>]]) [https://phabricator.wikimedia.org/T391747] ** a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q3450749|Rakhine]] ([[w:rki:|<code>w:rki:</code>]]) [https://phabricator.wikimedia.org/T392490] ** a {{int:project-localized-name-group-wikibooks/en}} in [[d:Q13324|Minangkabau]] ([[b:min:|<code>b:min:</code>]]) [https://phabricator.wikimedia.org/T395452] ** a {{int:project-localized-name-group-wiktionary/en}} in [[d:Q7598268|Standard Moroccan Amazigh]] ([[wikt:zgh:|<code>wikt:zgh:</code>]]) [https://phabricator.wikimedia.org/T399684] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:46}} community-submitted {{PLURAL:46|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.15|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/34|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W34"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:39, 19 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29127690 --> == Wikipedia translation of the week: 2025-35 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Corallite]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Recent azooxanthellate Scleractinia (Cnidaria, Anthozoa) - ZooKeys-227-001-g004.jpeg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''corallite''' is the skeletal cup, formed by an individual stony coral polyp, in which the polyp sits and into which it can retract. The cup is composed of aragonite, a crystalline form of calcium carbonate, and is secreted by the polyp. Corallites vary in size, but in most colonial corals they are less than 3 mm (0.12 in) in diameter. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 25 August 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29115447 --> == Tech News: 2025-35 == <section begin="technews-2025-W35"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/35|Translations]] are available. '''Updates for editors''' * [[File:Octicons-gift.svg|12px|link=|class=skin-invert|Wishlist item]] [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Template authors can now use additional CSS properties, since the CSS sanitizer used by [[mw:Special:MyLanguage/Help:TemplateStyles|TemplateStyles]] was updated. For example: <code>width: fit-content</code>; <code>ruby-align</code>; relative units such as <code>lh</code>; and custom strings in <code>list-style-type</code>. These improvements are a [[m:Special:MyLanguage/Community Wishlist/Wishes/Allow use of modern CSS in templates by updating the TemplateStyles CSS sanitizer|Community Wishlist wish]]. [https://phabricator.wikimedia.org/T271958][https://phabricator.wikimedia.org/T277755][https://phabricator.wikimedia.org/T293633][https://phabricator.wikimedia.org/T295088][https://phabricator.wikimedia.org/T326906][https://phabricator.wikimedia.org/T340057][https://phabricator.wikimedia.org/T360725][https://phabricator.wikimedia.org/T371809][https://phabricator.wikimedia.org/T375344][https://phabricator.wikimedia.org/T394619] * On large wikis, the default time period to display edits from, within the Special:RecentChanges page, has been changed from 7 days to 1 day. This is part of a performance improvement project. This should have no user-facing impact due to the quantity of edits on these wikis. [https://phabricator.wikimedia.org/T399455] * Administrators can now access the [[{{#special:BlockedExternalDomains}}]] page from the [[{{#special:CommunityConfiguration}}]] list page. This makes it easier to find. [https://phabricator.wikimedia.org/T393240] * Wikimedia Commons videos were not shown in the Videos tab in Google Search. The problem was investigated and reported to Google who have now fixed the issue. [https://phabricator.wikimedia.org/T396168][https://meta.wikimedia.org/wiki/Community_Wishlist/Wishes/Do_something_about_Google_%26_DuckDuckGo_search_not_indexing_media_files_and_categories_on_Commons] * One new wiki has been created: a {{int:project-localized-name-group-wiktionary/en}} in [[d:Q33014|Betawi]] ([[wikt:bew:|<code>wikt:bew:</code>]]) [https://phabricator.wikimedia.org/T402130] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:39}} community-submitted {{PLURAL:39|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Two fields of the [[mw:Special:MyLanguage/Manual:Recentchanges table|recentchanges database table]] are being removed. <code>rc_new</code> and <code>rc_type</code> are being removed in favor of <code>rc_source</code>. Queries to these older fields will start to fail starting this week and developers should use <code>rc_source</code> instead. These older fields were deprecated over 10 years ago and should not be in use. This is part of work to improve the performance and stability of queries to the recentchanges table. [https://phabricator.wikimedia.org/T400696] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.16|MediaWiki]] '''In depth''' * The latest quarterly [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Newsletter/2025/July|Language and Internationalization Newsletter]] is now available. This edition includes: support for new languages in MediaWiki and translatewiki; the start of the Language Onboarding and Development project to help support the growth of new and small wikis; updates on research projects; and more. '''Meetings and events''' * The next [[mw:Special:MyLanguage/Wikimedia Language and Product Localization/Community meetings#29 August 2025|Language Community Meeting]] is happening soon, August 29th at [https://zonestamp.toolforge.org/1756479600 15:00 UTC]. This week's meeting will cover: the Avro keyboard developers from Wikimedia Bangladesh, who were recently awarded a national award for their contributions to this keyboard; and other topics. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/35|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W35"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 00:13, 26 August 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29175124 --> == Wikipedia translation of the week: 2025-36 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Diksam Plateau]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Dixam plateau (6407168437).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Diksam Plateau''' or Dixam Plateau (Arabic: دكسم) is a limestone plateau in Socotra, Yemen. The Firmihin forest, located east of the Dirhur canyon within the plateau, has the highest concentration of Dragon's Blood Trees on the entire island. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:40, 1 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29195081 --> == Tech News: 2025-36 == <section begin="technews-2025-W36"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/36|Translations]] are available. '''Weekly highlight''' * The Editing team wants to compile a list of templates, jargon terms, and policies used in edit summaries when a copyright violation is removed. This will help them identify the number of edits reverted due to copyright issues. We invite community members from the following Wikis to list these terms in [[Phab:T402601|T402601]], or to share their list with [[User:Trizek (WMF)|Trizek_(WMF)]]: {{int:project-localized-name-arwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-cswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-dewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-enwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-eswiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-fawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-frwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-hewiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-idwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-itwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-jawiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-kowiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-nlwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-plwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ptwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-trwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-ukwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-viwiki/en}}{{int:comma-separator/en}}{{int:project-localized-name-zhwiki/en}}. This project is open until September 9th 2025. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] has been enabled for all Wikisources. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. The extension has three features: [[m:Special:MyLanguage/Event Center/Registration|Event Registration]], [[m:Special:MyLanguage/CampaignEvents/Collaboration list|Collaboration List]], and [[m:Special:MyLanguage/Connection Team/Invitation list|Invitation List]]. To request the extension for your wiki, visit the Deployment information page. [https://meta.wikimedia.org/wiki/CampaignEvents/Deployment_status#How_to_Request_the_CampaignEvents_Extension_for_your_wiki] * The lists in the footer of the editing interface, such as "Templates used on this page," will now be organized into columns when there is enough space. This enhancement minimizes scrolling when editing lengthy articles on Wikipedia. [https://phabricator.wikimedia.org/T401066] * On September 3rd, 2025 we will increase the sampling percentages of our [[mw:Special:MyLanguage/Moderator Tools/Watchlist/Experiment#Scope of the experiment|group by toggle experiment]] of the <code>Special:RecentChanges</code>, <code>Special:Watchlist</code>, and <code>Special:RelatedChanges</code> pages on the Chinese, French, and Portuguese Wikipedias to 100 percent, allowing more editors to be part of this experiment. This adjustment is intended to ensure we have sufficient data to make informed decisions when evaluating the experiment results. [https://phabricator.wikimedia.org/T402958][https://phabricator.wikimedia.org/T396789] * Upon clicking an empty search bar, logged-out users will see suggestions of articles for further reading on English Wikipedia beginning the week of September 22. The feature will be available on both desktop and mobile. All non-English wikis received this change in June and July. The goal is to make it easier for users to find articles. [[mw:Special:MyLanguage/Reading/Web/Content Discovery Experiments/Search Suggestions|Learn more]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:37}} community-submitted {{PLURAL:37|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.17|MediaWiki]] '''In depth''' * Wikifunctions now has a new capability called "lightweight enumeration types", an enumeration type is simply a fixed set of values that's in the type's definition. This capability makes it quick and easy to define such a type, and allows for the reuse of values that are already present in Wikidata. Here is [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-07-19|a newsletter]] to learn more. * The latest [[mw:Special:MyLanguage/Readers/Newsletter updates#August 2025: Newsletter #1|Readers Newsletter]] is now available. This edition includes: the formation of two new teams — Reader Growth and Reader Experience; insights into declining pageviews and account creations; highlights from the Wikimania Nairobi panel on improving the reading experience; upcoming experiments to engage new and existing readers; and more. '''Meetings and events''' * Spotlight on some Wikimania 2025 Sessions: ** Identifying AI-generated text by searching for ISBNs whose checksums fail: Mathias Schindler of WMDE [https://www.youtube.com/watch?v=Dw9o8Lsl974&t=15910s shared tools to help communities search for these]. ** [https://wikimedia.eventyay.com/talk/wikimania2025/talk/TCHZKH/ La durabilité du mouvement Wikimedia face aux défis actuels et futurs]: This session explored how Wikimedia can stay a trusted source of knowledge in the age of generative AI, information overload, and disinformation. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/36|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W36"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:51, 1 September 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29196010 --> == Wikipedia translation of the week: 2025-37 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Ttongsul]]'''<br /> <small>''([[:ja:トンスル]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Ttongsul (imitation).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Il '''ttongsul''' (똥술), o vino di feci, è una tradizionale preparazione medicinale coreana con gradazione alcolica al 9% a base di feci, solitamente umane e preferibilmente di bambino. Nato probabilmente traendo spunto dalla medicina tradizionale cinese, nelle credenze popolari il vino di feci avrebbe proprietà benefiche per molti tipi di malesseri: sarebbe un rimedio per dolori muscolari, ustioni, infiammazioni, epilessia e fratture ossee. Sebbene alcuni media occidentali abbiano in passato riportato che questa bevanda sia diffusa tra la popolazione coreana, al giorno d'oggi un numero molto limitato di persone ne fa uso, dopo aver subito un declino di popolarità nei secoli scorsi, tanto che la maggioranza dei giovani coreani non ne ha mai sentito parlare. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:28, 8 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29195081 --> == Tech News: 2025-37 == <section begin="technews-2025-W37"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/37|Translations]] are available. '''Weekly highlight''' * The Editing team is working on a new check: [[mw:Special:MyLanguage/Paste check|Paste check]]. This check informs newcomers who paste text into Wikipedia that the content might not be accepted. This check is an effort to increase the likelihood that the new content people are adding to Wikipedia is aligned with the Movement's commitment to offering information under a free content license. This check will soon be tested at a few wikis. If your community is interested in this test, please [[phab:T403680|tell us in this task]], or [[mw:Talk:Edit check|contact the team]]. '''Updates for editors''' * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] Later this week, users of the "{{int:codemirror-beta-feature-title}}" [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] will be able to use a [[w:en:Lint (software)|linting tool]] to see errors or other potential problems in wikitext in real time. See the [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Linting|help page for more information]]. [https://phabricator.wikimedia.org/T381577] * [[File:Octicons-tools.svg|12px|link=|class=skin-invert|Advanced item]] When browsing a wiki (like <code dir=ltr>en.wikipedia.org</code>), the software responds in one of two ways: a desktop page, or a redirect to a mobile version on an "m" domain (like <code dir=ltr>en.m.wikipedia.org</code>). Over the next three weeks, MediaWiki will start displaying the mobile version to mobile devices directly on the standard domain, without this redirect. This change does not affect existing m-dot URLs, or the "Desktop view" opt-out. [[mw:Requests for comment/Mobile domain sunsetting/2025 Announcement|Learn more]]. [https://phabricator.wikimedia.org/T214998] * When an edit changes the categories of a page, the changes to the category membership counts are now happening asynchronously. This improves the speed of saving edits, especially when moving many pages to or from the same category, and reduces the risk of site outages, but it means that the counts can show outdated information for a few minutes. [https://phabricator.wikimedia.org/T365303] * Edits on Wikidata to qualifiers (properties and values) and references (properties and values) in a Wikidata item statement will now not add entries to the RecentChanges or Watchlist pages on all other Wikis. This is a temporary change to improve performance while other solutions are created. Wikidata's own pages remain unchanged. [[m:Wikidata For Wikimedia Projects/Reduce change propagation noise#Phase 1: Turn off (temporarily) Qualifiers and References Wikidata edits to the Recent Changes tables|Learn more]]. [https://phabricator.wikimedia.org/T401286][https://phabricator.wikimedia.org/T400698] * Japanese-language wikis have had a major upgrade to the way that search works. The new search should generally give more accurate and more relevant search results. [https://phabricator.wikimedia.org/T318269] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.18|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/37|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W37"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 01:15, 9 September 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29238161 --> == Wikipedia translation of the week: 2025-38 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pak Kum-chol]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Pak Kum-chol in 1961 (cropped).jpg|center]] <div style="text-align:left; padding: .4em;"> '''Pak Kum-chol''' was a North Korean politician. Having been a guerrilla during the anti-Japanese struggle, he became a high-ranking politician after the liberation of Korea. Pak aligned himself with his former guerrilla brothers in arms from the Kapsan Operation Committee to form a faction within the ruling Workers' Party of Korea (WPK) called the "Kapsan faction". This faction sought to replace Kim Il Sung with Pak. Kim retaliated by purging the faction in 1967 in what is known as the Kapsan faction incident. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 15 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29249252 --> == Tech News: 2025-38 == <section begin="technews-2025-W38"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/38|Translations]] are available. '''Updates for editors''' * References lists that are made using the <code dir=ltr><nowiki><references/></nowiki></code> [[mw:Special:MyLanguage/Help:Cite#references-tag|tag]] will now automatically display with columns in Vector 2022 when readers are using its 'standard' settings for text-size and page-width. [https://phabricator.wikimedia.org/T334941] * Starting in the week of October 6, on [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/small.dblist|small wikis]] and [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/medium.dblist|medium wikis]] that have the [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] enabled, all autoconfirmed users will be able to use [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] as an organizer. No changes will be made for [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/large.dblist|large wikis]] unless requested in Phabricator. This change is being made to make it easier for more people to use Event Registration, especially on wikis that are less likely to have policies related to the Event Organizer right. [[m:Special:MyLanguage/CampaignEvents/Proposal to grant autoconfirmed users on small and medium wikis the organizer access to the event registration tool|Learn more]]. * Users that search using regular expressions (regex) can now use additional features including: ** for the <code dir=ltr>intitle:</code> keyword: [[mw:Special:MyLanguage/Help:CirrusSearch#Metacharacters|metacharacters]] for start-of-line (<code dir=ltr>^</code>) and end-of-line (<code dir=ltr>$</code>) anchors [https://phabricator.wikimedia.org/T317599] ** for both <code dir=ltr>intitle:</code> and <code dir=ltr>insource:</code> keywords: shorthand [[mw:Special:MyLanguage/Help:CirrusSearch#Character_Classes|character classes]] for digits (<code dir=ltr>\d</code>), whitespace (<code dir=ltr>\s</code>), and word characters (<code dir=ltr>\w</code>); and [[mw:Special:MyLanguage/Help:CirrusSearch#Escape codes|escape codes]] for line feed (<code dir=ltr>\r</code>), newline (<code dir=ltr>\n</code>), tab (<code dir=ltr>\t</code>), and unicode (e.g. <code dir=ltr>\uHHHH</code>). [https://phabricator.wikimedia.org/T403212] * When you search for text that looks like an IP, the system will now show search results. It used to take you to the contributions for that IP instead of showing search results. [https://phabricator.wikimedia.org/T306325] * [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on September 24. This is planned at [https://zonestamp.toolforge.org/1758726000 15:00 UTC]. This is for the datacenter server switchover backup tests which happen twice a year. You can [[diffblog:2025/03/12/hear-that-the-wikis-go-silent-twice-a-year/|read more about the background and details of this process on the Diff blog]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:24}} community-submitted {{PLURAL:24|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug was fixed that affected users who used the page-tabs to switch from wikitext editing of a section into the visualeditor. [https://phabricator.wikimedia.org/T401043] '''Updates for technical contributors''' * The MediaWiki Interfaces team is redesigning the Wikimedia REST API Sandbox with Codex. If you have feedback on improvements for the API documentation or what makes developer experiences smooth (or frustrating), you’re invited to [https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ2aZzbXeQvjOF7gB1fJXiwAYemQjKf4sXNaRODPA7_obFyNBwkzNkoVCoTF-aeov89kIjXHbCQm join an upcoming discovery interview], or [[mw:MediaWiki Interfaces Team/Developer Feedback/Wikimedia Web APIs|leave feedback onwiki]]. [[listarchive:list/wikitech-l@lists.wikimedia.org/thread/C4FBAOA57PH6G5ORVMAUF5TGYBLZDU5Q/|Learn more]]. * Edits to Wikidata aliases (an alternative name for an item or a property) will now be shown in RecentChanges and Watchlist entries on other wikis less often, reducing unnecessary notifications. This will reduce the overall quantity of 'noisy' entries. Wikidata's own pages remain unchanged. [[m:Wikidata For Wikimedia Projects/Reduce change propagation noise#Phase 1: More granular Alias tracking|Learn more]]. [https://phabricator.wikimedia.org/T401288] * The new [https://www.unicode.org/versions/Unicode17.0.0/ Unicode 17.0] version has been released. The [[:c:Category:Unicode Module Datasets|datasets on Commons]] for the [[:d:Q39301585|Module:Unicode data]] have been updated. Wikipedias that do not use the Commons datasets should either update their own data or switch to the Commons datasets. * Users of the [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]] Structured Contents endpoints can now access [https://enterprise.wikimedia.com/blog/parsed-wikipedia-tables/ Parsed Tables]. The new Parsed Tables feature extracts and represents Wikipedia tables in structured JSON. This improves machine accessibility as part of the [https://enterprise.wikimedia.com/api/structured-contents/ Structured Contents initiative]. Structured Contents output is freely available through the [https://enterprise.wikimedia.com/docs/on-demand/#article-structured-contents-beta On-demand API], or through Wikimedia Cloud Services. * A [https://www.kaggle.com/datasets/wikimedia-foundation/english-wikipedia-people-dataset dataset of English Wikipedia biographical information] from [[m:Special:MyLanguage/Wikimedia Enterprise|Wikimedia Enterprise]] has been published on Kaggle, for evaluation and research. This provides structured data from more than 1.5 million biographies, including birth and death dates, education, affiliations, careers, awards, and more (from a June 2024 snapshot). * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.19|MediaWiki]] '''Meetings and events''' * [[wmania:Special:MyLanguage/2026:Scholarships|Scholarship applications]] for Wikimania 2026 in Paris, France, are open until October 31. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/38|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W38"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:08, 15 September 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29263921 --> == Wikipedia translation of the week: 2025-39 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Federation of Central America (1921–1922)]]'''<br /> <small>''([[:es:Federación de Centro América (1921-1922)]])&#32;([[:ar:اتحاد أمريكا الوسطى (1921-1922)]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Central America's Northern Triangle (orthographic projection).png|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Federation of Central America''' (Spanish: Federación de Centro América)[1] was a short-lived federal republic that existed in Central America between 1921 and 1922. The federation consisted of the Central American nations of El Salvador, Guatemala, and Honduras. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:45, 22 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29311347 --> == Tech News: 2025-39 == <section begin="technews-2025-W39"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/39|Translations]] are available. '''Weekly highlight''' * [https://zonestamp.toolforge.org/1758726000 On September 24th at 15:00 UTC], all Wikimedia sites users will experience a brief read-only period due to a scheduled [[m:Special:MyLanguage/Tech/Server switch|datacenter server switchover]]. The Wikimedia Foundation's Site Reliability Engineering (SRE) team will redirect all traffic from one primary server to its backup. You can listen to the switchover using the [http://listen.hatnote.com/ "Listen to Wikipedia"] tool, where you will hear edits stop for a few minutes during the read-only phase, then resume. This twice-yearly datacenter server switchover ensures reliability by testing the backup datacenter, so that our sites can stay online even if the primary datacenter fails. You can [[diffblog:2025/03/12/hear-that-the-wikis-go-silent-twice-a-year/|read more about the process on the Diff blog]]. '''Updates for editors''' * Editors of [[f:Special:Mylanguage/Wikifunctions:Status updates/2025-09-12#Next round of Wiktionaries to receive embedded Wikifunctions calls|60 more Wiktionaries]] will soon be able to call [[f:Special:MyLanguage/Wikifunctions:Introduction|functions from Wikifunctions]] and integrate them into their pages. A function takes one or more inputs and transforms them into a desired output, like adding numbers, converting miles to meters, calculating elapsed time, or declining a word into a case. They will join the other [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-08-29#Wikifunctions available on 65 Wiktionaries|65 Wiktionary language editions]], which already have access to embedded Wikifunctions calls. Later this year, plans are in place to expand to more Wiktionaries and the Incubator. * A new [[mw:Special:MyLanguage/Help:Magic words#Technical metadata of another page|parser function]] has been added: <code><nowiki>{{#contentmodel}}</nowiki></code>. Template editors and admins can use it to get the localized or canonical name of the [[mw:Special:MyLanguage/Help:ChangeContentModel|content model]] of a specific page. The function makes it easier to create and edit system messages, such as ''MediaWiki:editinginterface'', even when you switch types of pages, like wiki, JavaScript, CSS or JSON page. [https://phabricator.wikimedia.org/T328254] * Adding or editing a <code>DISPLAYTITLE</code> for an article using VisualEditor will no longer be broken. Editors who use VisualEditor mode to modify the <code><nowiki>{{DISPLAYTITLE}}</nowiki></code> would no longer have the literal text "DISPLAYTITLE" or its localized variant added to their articles. A list of pages that may have been affected and might need cleanup is documented in [[phab:P83438|this ticket]]. * Beta users of the Wikipedia Android app can now try the redesigned [[mw:Special:MyLanguage/Wikimedia Apps/Team/Android/Activity Tab Experiment|Activity tab]], which replaces the Edits tab. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:12}} community-submitted {{PLURAL:12|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.20|MediaWiki]] '''In depth''' * Wikifunctions users can now import many essential facts involving [[f:Special:MyLanguage/Z6011|geo-coordinates]], [[f:Special:MyLanguage/Z6010|quantities]] and [[f:Special:MyLanguage/Z6064|time]] values from Wikidata. This is made possible by the creation of Wikifunctions types for these values, which makes them available for use by functions in Wikifunctions. Learn more about how this works in [[c:File:ImportingWikidataDatatypesIntoWikifunctions.webm|this video]] and Wikifunctions' [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-08-01#News in Types I: Wikidata quantity|August 1 newsletter]] (for quantities) and [[f:Special:MyLanguage/Wikifunctions:Status updates/2025-08-22#News in Types: Wikidata geo-coordinate|August 22 newsletter]] (for geo-coordinates). '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/39|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W39"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 22:56, 22 September 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29305556 --> == Wikipedia translation of the week: 2025-40 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Palazzo delle Poste (Latina)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Postelittoria2.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Il '''Palazzo delle Poste''', fino al 1945 Ricevitoria Postelegrafonica di Littoria, è un edificio postale di Latina, situato in piazzale dei Bonificatori. Costruito nel 1932 in stile razionalista con influenze futuriste, riscontrabili nell'utilizzo di ampie superfici vetrate e di volumi verticali, oltre che per la presenza di l’utilizzo di materiali e scelte di design molto in voga all'epoca come, come i mattoni a vista, il travertino di Tivoli e l'Anticorodal (una lega di alluminio), ospita l'ufficio postale Latina Centro. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:58, 29 September 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29341788 --> == Tech News: 2025-40 == <section begin="technews-2025-W40"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/40|Translations]] are available. '''Weekly highlight''' * A major software upgrade has been made to [[phab:|Phabricator]]. The update introduces performance improvements, a refreshed search interface, enhancements to Maniphest task search, updates to user profile pages and project workboards, new Herald automation features, as well as general text input, mobile experience improvements and more. [https://phabricator.wikimedia.org/phame/post/view/321/iterative_improvements_september_2025/] '''Updates for editors''' * The Community Tech team will release the new Community Wishlist extension on October 1, that will improve the way wishes will be submitted. The new extension will allow users to add tags to their wishes to better categorise them, and (in a future iteration) to filter them by status, tags and focus areas. It will also be possible to support individual wishes again, as requested by the community in many instances. The old system will be retired. There will be a brief period of downtime while the extension is deployed and wishes are migrated to the new system. You can read more about this [[:m:Special:MyLanguage/Community Wishlist/Updates|in the latest update]] or you can consult the [[:mw:Special:MyLanguage/Help:Extension:CommunityRequests|current documentation on MediaWiki]]. * As announced [[diffblog:2025/09/02/better-detecting-bots-and-replacing-our-captcha/|on Diff blog]], the production trial of the [[mw:Special:MyLanguage/Product Safety and Integrity/Anti-abuse signals/hCaptcha|hCaptcha]] service for bot detection has begun. The trial is currently using hCaptcha to protect account creation on Chinese, Persian, Portuguese, Indonesian, Japanese, and Turkish Wikipedias, where it will replace our existing [[mw:Special:MyLanguage/Extension:ConfirmEdit#FancyCaptcha|CAPTCHA]] (FancyCaptcha). The goal with the trial is to better block bots while also improving usability and accessibility for users who encounter CAPTCHA challenges. * The [[mw:Special:MyLanguage/Extension:CampaignEvents|CampaignEvents]] extension has been [[m:Special:MyLanguage/CampaignEvents/Deployment status|deployed]] to Wikimedia Commons. The extension makes it easier to organize and participate in collaborative activities, like edit-a-thons and WikiProjects, on the wikis. On Commons, anyone who is a registered user can use it as an event participant. To use it as an organizer, someone needs to have the [[c:Special:MyLanguage/Commons:Event organizers|event organizer right]]. * [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]], a new feature to re-use references with different details has been released to German Wikipedia. You can [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#test|test the feature]] on testwiki or [https://en.wikipedia.beta.wmcloud.org/wiki/Sub-referencing on betawiki] as well. Please share your thoughts on [[:m:Talk:WMDE Technical Wishes/Sub-referencing#Templates used in sub-references|using templates in sub-references]] or [[:m:Talk:WMDE Technical Wishes/Sub-referencing#Pilot wikis|volunteer to become a pilot wiki]]. * On wikis using the [[mw:Special:MyLanguage/Help:Growth/Mentorship|Mentorship]] system, communities can now opt experienced editors out of Mentorship through [[{{#special:CommunityConfiguration/Mentorship}}]]. Within this setting, communities may define thresholds, based on edit count and account age, to decide when an editor is considered experienced enough to no longer receive Mentorship. [https://phabricator.wikimedia.org/T403563] * The Editing Team and the Machine Learning Team are working on a new check for newcomers: [[mw:Special:MyLanguage/Edit check/Tone Check|Tone check]]. Using a prediction model, this check will encourage editors to improve the tone of their edits, using artificial intelligence. We invite volunteers to review the first version of the Tone language model for the following languages: Arabic, Czech, German, Hebrew, Indonesian, Dutch, Polish, Russian, Turkish, Chinese, Farsi, Italian, Norwegian, Romanian and Latvian. Users from these wikis interested in reviewing this model are [[mw:Special:MyLanguage/Edit_check/Tone_Check/Model_evaluation|invited to sign up at MediaWiki.org]]. The deadline to sign up is on October 3, which will be the start date of the test. * The rollout of [[:mw:Special:MyLanguage/Help:Manage blocks|multiblocks]] had the side effect that non-active block logs may have been shown on {{#special:Contributions}} and on blocked users' user and user_talk pages. This issue will be fully resolved in a few days. As part of the fix, [{{fullurl:Special:Allmessages|prefix=sp-contributions-blocked-notice}} messages prefixed with <code>sp-contributions-blocked-notice</code>] will be removed and replaced with [{{fullurl:Special:Allmessages|prefix=blocked-notice-logextract}} those prefixed with <code>blocked-notice-logextract</code>] in a few weeks. Please help translate the new messages and update any local overrides if needed. * There was a bug with links added using visual editor if they included characters such as <code dir=ltr><nowiki>[ ] |</nowiki></code> after the fragment identifier (<code><nowiki>#</nowiki></code>). They were not encoded properly creating an incorrect link. This has been fixed. [https://phabricator.wikimedia.org/T404823] * One new wiki has been created: a {{int:project-localized-name-group-wikiquote/en}} in [[d:Q9237|Malay]] ([[q:ms:|<code>q:ms:</code>]]) [https://phabricator.wikimedia.org/T404698] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the [[mw:Special:MyLanguage/Product Safety and Integrity/Anti-abuse signals/User Info|User Info Card]] now displays currently active global lock/blocks. [https://phabricator.wikimedia.org/T401128] '''Updates for technical contributors''' * Later this week, editors using Lua modules will be able to use the <code>[[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#mw.title.newBatch|mw.title.newBatch]]</code> function to look up the existence of up to 25 pages at once, in a way that only increases the [[mw:Special:MyLanguage/Manual:Parser functions#Expensive parser functions|expensive function]] count once. * A new [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group|Unsupported Tools Working Group]] has been formed as part of ongoing efforts to collectively determine technical work priorities, similar to the [[m:Special:MyLanguage/Product and Technology Advisory Council|Product & Technology Advisory Council]] (PTAC). The working group will help prioritize and review requests for support of unmaintained extensions, gadgets, bots, and tools. For the first cycle, the group will be prioritizing an unsupported Wikimedia Commons tool. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.21|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/40|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W40"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:54, 29 September 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29355230 --> == Wikipedia translation of the week: 2025-41 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Majed Abu Maraheel]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Majed Abu Maraheel''' was a Palestinian long-distance runner, football player, security officer, and athletics coach, who was the first Palestinian to compete at the Olympic Games. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:48, 6 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29341788 --> == Tech News: 2025-41 == <section begin="technews-2025-W41"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/41|Translations]] are available. '''Weekly highlight''' * [[mw:Special:MyLanguage/Help:Edit check#paste|Paste Check]] is a new Edit Check feature to help avoid and fight copyright violations. When editors paste text into an article, Paste Check prompts them to confirm the origin and licensing of the content. Starting Wednesday, 8 October, [[phab:T403680|22 wikis will test Paste Check]]. Paste Check will help new volunteers understand and follow the policies and guidelines necessary to make constructive contributions to Wikipedia projects. '''Updates for editors''' * Mobile devices will receive mobile articles directly on the standard domain (like <code>en.wikipedia.org</code>), instead of via a redirect to an "m" domain (like <code>en.m.wikipedia.org</code>). This change improves performance. This week it will be enabled on Wikipedias. The existing mobile URLs and the "Desktop view" opt-out remain available. [[mw:Requests for comment/Mobile domain sunsetting/2025 Announcement|Learn more]]. [https://phabricator.wikimedia.org/T214998] * New [[mw:Special:MyLanguage/Help:CirrusSearch#creationdate and lasteditdate|date filters]], <code dir=ltr>creationdate:</code> and <code dir=ltr>lasteditdate:</code>, are now available in the wiki search engine. This allows users to filter search results by a page's first or last revision date. The filters support comparison operators (e.g. <code dir=ltr>>2024</code>) and relative dates (e.g. <code dir=ltr>today-1d</code>), making it easier to find recently updated content or pages within specific age ranges. [https://phabricator.wikimedia.org/T403593] * [[f:|Wikifunctions]] now supports rich text in embedded calls across the 150 wikis where it's enabled. To showcase this, the team created a [[f:Z26333|Latin declination table]] that Wiktionary editors can use to automatically generate noun forms, producing clear, formatted results — see an [[f:Wikifunctions:Embedded function calls/Wiktionary tables demonstration|example output]]. If you need any help or have any feedback, please [[f:Wikifunctions:Project chat|contact the Wikifunctions Team]]. [https://phabricator.wikimedia.org/T397402] * An edit link will now appear inside the categories box on article pages for logged in users, which will directly launch the VisualEditor category dialog. [https://phabricator.wikimedia.org/T291691] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:34}} community-submitted {{PLURAL:34|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a problem downloading pdf files last week and that has been resolved. [https://phabricator.wikimedia.org/T405957] '''Updates for technical contributors''' * The field <code dir=ltr>rev_sha1</code> in the revision database table is being removed in favor of <code dir=ltr>content_sha1</code> in the content database table. See [https://lists.wikimedia.org/hyperkitty/list/cloud@lists.wikimedia.org/thread/2D2M3SP4WHR6BXXKTZ2PBLZQYR3EGQVR/ the announcement] for more information. * The [[mw:Special:MyLanguage/Reading/Web|Reader Experience team]] will roll out [[w:en:Light-on-dark color scheme|Dark Mode]] user interface on all Wikimedia sites on October 29, 2025. All anonymous users of Wikimedia sites will have the option to activate a color scheme that features light-colored text on a dark background. This is designed to provide a more comfortable reading experience, especially in low-light situations. Template authors and technical contributors are encouraged to [[mw:Special:MyLanguage/Reading/Web/Accessibility for reading/Updates/2024-04|learn how to make pages ready for Dark mode]] and address any compatibility issues found in templates in their wiki before the enablement. Please contact the Web team for questions or any support on [[mw:Talk:Reading/Web/Accessibility for reading#|this talk page]] before the enablement. [https://phabricator.wikimedia.org/T395628] * Starting on Monday, October 6, API endpoints under the <code>rest.php</code> path will be rerouted through a new internal API Gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to the [[phab:tag/serviceops/|Service Ops team board]]. [https://phabricator.wikimedia.org/T400130] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.22|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/41|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W41"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:24, 6 October 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29400897 --> == Wikipedia translation of the week: 2025-42 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Abortion in Eritrea]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> In Eritrea, abortion is banned except on the grounds of pregnancy from rape or incest, pregnancy of a minor, or risk to physical or mental health. Legal abortions require medical or judicial approval. Prior to Eritrea's independence, it applied Ethiopia's abortion law of the 1950s, which banned abortion unless life-saving. After independence, the 1991 penal code adapted this law to lift punishments on abortions on the grounds of rape, incest, or risk to life or health, but legal abortions did not exist in effect. The penal codes of 2001 and 2015 required physicians to prove health grounds for abortion. Unsafe abortion is common and contributes to maternal mortality in Eritrea. Post-abortion care is unavailable in some regions. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:06, 13 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29341788 --> == Tech News: 2025-42 == <section begin="technews-2025-W42"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/42|Translations]] are available. '''Weekly highlight''' * Last week, improvements to account security and two-factor authentication (2FA) features were enabled across all wikis. These changes include user interface improvements for [https://auth.wikimedia.org/metawiki/wiki/Special:AccountSecurity Special:AccountSecurity], the support of multiple 2FA methods via authenticator apps and portable security keys (previously users could only enable one method), and a new Recovery Codes module which facilitates fewer account lockouts due to lost two-factor apps and devices. As part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] project, work is continuing through the rest of 2025 on further user experience improvements, and support for passkeys as an alternate second factor. '''Updates for editors''' * Another part of the Account security project is making 2FA generally available to all users. Along with editors with advanced privileges, such as administrators and bureaucrats, 40% of editors now have access to 2FA. You can check if you have access at [https://auth.wikimedia.org/metawiki/wiki/Special:AccountSecurity Special:AccountSecurity]. Instructions for activation are on the linked page. The plan is to continue increasing availability if it is determined that the user support capabilities are able to support global usage. [https://phabricator.wikimedia.org/T400579] * This week, users at wikis where talk page [[mw:Special:MyLanguage/Talk pages project/Usability|Usability Improvements]] are already available by default (everywhere ''except'' the 12 wikis listed in [[phab:T379264|T379264]]) will gain the ability to Thank a comment directly from the talk page it appears on. Before this change, Thanking could only be done by visiting the revision history of the talk page. You can [[diffblog:2025/10/13/revolutionizing-gratitude-a-new-era-of-thanking-comments/|learn more about this change]]. [https://phabricator.wikimedia.org/T366095] * Users who have not [[Special:Preferences#mw-prefsection-personal-email|verified their email address]] will soon be receiving monthly Notification reminders to do so. This is because users who have verified their email can more easily recover their account. These reminders will not be sent if the user is inactive or removes the unverified email from their account. [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Email_confirmation][https://phabricator.wikimedia.org/T58074] * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a fix was made for an occasional error with saving translated paragraphs in the Content Translation tool, and the related error messages are now easier to see. [https://phabricator.wikimedia.org/T376531] '''Updates for technical contributors''' * The Unsupported Tools Working Group has chosen [[c:Special:MyLanguage/Commons:Video2commons|Video2Commons]] as the first tool for its pilot cycle. The group will explore ways to improve and sustain the tool over the coming months. [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group|Learn more on Meta]]. * [[File:Octicons-sync.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.23|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/42|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W42"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:00, 13 October 2025 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29434481 --> == Wikipedia translation of the week: 2025-43 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Liberation of Auschwitz concentration camp]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Auschwitz Liberated January 1945.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> On 27 January 1945, Auschwitz—a Nazi concentration camp and extermination camp in occupied Poland where more than a million people were murdered as part of the Nazis' "Final Solution" to the Jewish question—was liberated by the Soviet Red Army during the Vistula–Oder Offensive. Although most of the prisoners had been forced onto a death march, about 7,000 had been left behind. The Soviet soldiers attempted to help the survivors and were shocked at the scale of Nazi crimes. The date is recognized as International Holocaust Remembrance Day. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:04, 20 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29452019 --> == Tech News: 2025-43 == <section begin="technews-2025-W43"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/43|Translations]] are available. '''Updates for editors''' * To optimize how user data is stored in our databases, the saved preferences of users who haven't logged in for over five years and have fewer than 100 edits will be cleared. When those users return, default settings will apply. [https://phabricator.wikimedia.org/T406724] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, there was a broken link from the GlobalContributions interface message to the XTools GlobalContributions page which has now been fixed. [https://phabricator.wikimedia.org/T406415] '''Updates for technical contributors''' * The work to reroute all traffic to API endpoints under the <code dir=ltr><nowiki>rest.php</nowiki></code> route through a common API gateway is now complete. If any issues are observed, please file a phabricator ticket to the [[phab:tag/serviceops/|Service Ops team board]]. * Edits to Wikidata references or qualifiers will now be shown in RecentChanges and Watchlist entries on other wikis less often, reducing unnecessary notifications. This will reduce the overall quantity of 'noisy' entries. Wikidata's own pages remain unchanged. [https://phabricator.wikimedia.org/T401290] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.24|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/43|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W43"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:37, 20 October 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29478670 --> == Wikipedia translation of the week: 2025-44 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Black Diaries]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''Black Diaries''' are diaries purported to have been written by the Irish revolutionary Roger Casement, which contained accounts of homosexual liaisons with young men. They cover the years 1903, 1910 and 1911 (two) and were handed in to Scotland Yard after his capture in April 1916. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:51, 27 October 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29487357 --> == Tech News: 2025-44 == <section begin="technews-2025-W44"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/44|Translations]] are available. '''Updates for editors''' * The Wikipedia iOS app has launched an A/B/C test of improvements made to the tabbed browsing feature for select regions and languages. The test, named “More dynamic tabs”, explores new tab experiences and includes “Did you know” and “Because you read” article recommendations. You can [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/Tabbed Browsing (Tabs)/New Tab Experience and Recommendations Experiment|read more on the project page]]. * Autoconfirmed users on [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/small.dblist|small]] and [[gitiles:operations/mediawiki-config/+/a2d2aaab9ace84280dd2f4c70a33bb69cd73850f/dblists/medium.dblist|medium wikis]] with the CampaignEvents extension can now use [[m:Special:MyLanguage/Event Center/Registration|Event Registration]] without the Event Organizer right. This feature lets organizers enable registration, manage participants, and lets users register with one click instead of signing event pages. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue of flashing colors when holding or pressing the arrow keys under the dark mode settings in Vector 2022 has been fixed. [https://phabricator.wikimedia.org/T402285] '''Updates for technical contributors''' * The CampaignEvents extension will be deployed to all remaining wikis during the week of 17 November 2025. The extension currently includes three features: Event Registration, Collaboration List, and Invitation List. For this rollout, Invitation List will not be enabled on Wikifunctions and MediaWiki unless requested by those communities. [[m:Special:MyLanguage/CampaignEvents/Deployment status|Visit the deployment page to learn more]]. * The SwaggerUI-based REST sandbox experience is now live on all wiki projects. The sandbox can be accessed through the [[{{#special:RestSandbox}}]] page. Please report any issues to the MediaWiki Interfaces team board, or join the discussion on the [[mw:Special:MyLanguage/MediaWiki Interfaces Team/Feature Feedback/REST Sandbox|project launch]] page. [https://phabricator.wikimedia.org/project/board/6931/] * Transform endpoints with a trailing slash path in the MediaWiki REST API are now marked as deprecated. They will remain functional during this time, but removal is expected by the end of January 2026. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found and tested using the [https://test.wikipedia.org/w/index.php?api=mw-extra&title=Special%3ARestSandbox REST Sandbox]. See the [[mw:API/Deprecation|MediaWiki REST API Deprecation]] page for more detailed information about the API deprecation policies and procedures. * A dedicated [[mw:API:REST API/Changelog|changelog now exists for the MediaWiki REST API]]. The changelog provides an overview of these changes, making it easier for developers to keep track of improvements and iterations. Announcements will also continue to flow through the standard communication channels, including Tech News and email distribution lists, but can now be more easily referenced from a central location. If you have feedback about the style, structure, or content of this changelog, please [[mw:API talk:REST API/Changelog|join the discussion]]. * Administrators can delete the tracking category which was previously added by the JsonConfig extension, as it is no longer used. See the categories linked from [[d:Q130635582#sitelinks-wikipedia|Q130635582]]. It is OK if there are still pages listed in the category as that is just a caching issue, and they will be automatically cleared out the next time each page is edited. [https://phabricator.wikimedia.org/T378352] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.25|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/44|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W44"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:32, 27 October 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29513638 --> |} == Wikipedia translation of the week: 2025-45 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Consolations (Liszt)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Franz Liszt - Consolation No. 3, Lento placido.ogg|center|300px|]] <div style="text-align:left; padding: .4em;"> The '''Consolations''', S. 171a/172 (German: Tröstungen) are a set of six solo piano works by Franz Liszt. The compositions take the musical style of nocturnes with each having its own distinctive style. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:52, 3 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29558323 --> == Tech News: 2025-45 == <section begin="technews-2025-W45"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/45|Translations]] are available. '''Updates for editors''' * Administrators will now find that [[{{#special:MergeHistory}}]] is now significantly more flexible about what it can merge. It can now merge sections taken from the middle of the history of the source (rather than only the start) and insert revisions anywhere in the history of the destination page (rather than only the start). [https://phabricator.wikimedia.org/T382958] * For users with "{{int:discussiontools-preference-autotopicsub}}" [[Special:Preferences#mw-prefsection-editing|enabled in their preferences]], starting a new topic or adding a reply to an existing topic will now subscribe them to replies to that topic. Previously, this would only happen if the DiscussionTools "{{int:Skin-action-addsection}}" or "{{int:Discussiontools-replybutton}}" widgets were used. When DiscussionTools was originally launched existing accounts were not opted in to automatic topic subscriptions, so this change should primarily affect newer accounts and users who have deliberately changed their preferences since that time. [https://phabricator.wikimedia.org/T290778] * Scribunto modules can now be used to [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#SVG library|generate SVG images]]. This can be used to build charts, graphics and other visualizations dynamically through Lua, reducing the need to compose them externally and upload them as files. [https://phabricator.wikimedia.org/T405861] * Wikimedia sites now provide all anonymous users with the option to enable a dark mode color scheme, featuring light-colored text on a dark background. This enhancement aims to deliver a more enjoyable reading experience, especially in dimly lit environments. [https://phabricator.wikimedia.org/T395628] * Users with large watchlists have long faced timeouts when editing [[Special:EditWatchlist|Special:EditWatchlist]]. The page now loads entries in smaller sections instead of all at once due to a paging update, allowing everyone to edit their watchlists smoothly. As part of the database update, sorting by expiry has been removed because it was over 100× slower than sorting by title. A [https://meta.wikimedia.org/wiki/Community_Wishlist/W454 community wish] has been created to explore alternative ways to restore sort-by-expiry. If this feature is important to you, please support the wish! [https://phabricator.wikimedia.org/T41510] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:31}} community-submitted {{PLURAL:31|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the fixing of the persisting highlighting when using VisualEditor find and replace during a query. [https://phabricator.wikimedia.org/T407318] '''Updates for technical contributors''' * Since 2019 the [[m:Special:MyLanguage/Wikimedia URL Shortener|Wikimedia URL Shortener]] at https://w.wiki is available for all Wikimedia wikis to create short links to articles, permalinks, diffs, etc. It is available in the sidebar as "Get shortened URL". There are 30 wikis that also install an older "ShortUrl" extension. The old extension will soon be removed. This means <code>/s/</code> URLs will not be advertised under article titles via HTML <code dir=ltr>class="title-shortlink"</code>. The <code>/s/</code> URLs will keep working. [https://phabricator.wikimedia.org/T107188] * On Thursday, October 30, the [[:mw:Special:MyLanguage/MediaWiki Interfaces Team|MediaWiki Interfaces]] and [[:mw:Special:MyLanguage/Wikimedia Site Reliability Engineering|SRE Service Operations]] teams began rerouting Action API traffic through a common API gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to the [https://phabricator.wikimedia.org/tag/serviceops/ Service Ops team] board. * MediaWiki Train deployments will pause for the final two weeks of 2025: 22 December and 29 December. Backport windows will also pause between Monday, 22 December 2025 and Thursday, 2 January 2026. A backport window is a scheduled time to add things like bug fixes and configuration changes. There are seven deployment trains remaining for 2025. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/SMWTEAES4SDLDUSK4HMWNBSKNCXZAWYN/] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.45/wmf.26|MediaWiki]] '''In depth''' * In 2025, the Wikimedia Foundation reported that AI systems and search engines increasingly use Wikipedia content without driving users to the site, contributing to an 8% drop in human pageviews compared to 2024. After detecting bots disguised as humans, Wikimedia updated its traffic data to reflect this shift. Read more about current user trends on Wikipedia in [[diffblog:2025/10/17/new-user-trends-on-wikipedia/|a Diff blog post]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/45|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W45"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:35, 3 November 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29552512 --> == Wikipedia translation of the week: 2025-46 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Marine coastal ecosystem]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Vegetation and fauna processes controlling benthic biogeochemical fluxes.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> A '''marine coastal ecosystem''' is a marine ecosystem which occurs where the land meets the ocean. Worldwide there is about 620,000 kilometres (390,000 mi) of coastline. Coastal habitats extend to the margins of the continental shelves, occupying about 7 percent of the ocean surface area. Marine coastal ecosystems include many very different types of marine habitats, each with their own characteristics and species composition. They are characterized by high levels of biodiversity and productivity. For example, estuaries are areas where freshwater rivers meet the saltwater of the ocean, creating an environment that is home to a wide variety of species, including fish, shellfish, and birds. Salt marshes are coastal wetlands which thrive on low-energy shorelines in temperate and high-latitude areas, populated with salt-tolerant plants such as cordgrass and marsh elder that provide important nursery areas for many species of fish and shellfish. Mangrove forests survive in the intertidal zones of tropical or subtropical coasts, populated by salt-tolerant trees that protect habitat for many marine species, including crabs, shrimp, and fish. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:54, 10 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29584005 --> == Tech News: 2025-46 == <section begin="technews-2025-W46"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/46|Translations]] are available. '''Updates for editors''' [[File:Talk pages default look (April 2023).jpg|thumb|alt=Screenshot of the visual improvements made on talk pages|Example of a talk page with the new design, in French.]] * Starting November 12, users will see a change in the [[m:Special:MyLanguage/Talk pages project/Feature summary#Usability improvements|appearance of talk pages]] on [[Phab:T379264|some Wikipedias]]. Almost [[phab:T392121|all wikis]] have received this design change; [[phab:T409297|English Wikipedia]] will get these changes later. You can read more [[diffblog:2024/05/02/making-talk-pages-better-for-everyone/|on ''Diff'']]. Users can opt out of these changes [[Special:Preferences#mw-prefsection-editing|in their user preferences]] in "{{int:discussiontools-preference-visualenhancements}}". [https://phabricator.wikimedia.org/T379264] * MediaWiki can now display a [[mw:Special:MyLanguage/Help:Protection indicators|page indicator]] automatically while a page is protected. This feature is disabled by default. It can be enabled by [[m:Special:MyLanguage/Requesting wiki configuration changes|community request]]. [https://phabricator.wikimedia.org/T12347] * Using the "{{int:showpreview}}" or "{{int:showdiff}}" buttons in the wikitext editor will now carry over certain URL parameters like '[[mw:Special:MyLanguage/Manual:Parameters to index.php#useskin|useskin]]', '[[mw:Special:MyLanguage/Manual:Parameters to index.php#uselang|uselang]]' and '[[mw:Special:MyLanguage/Help:Section#Editing sections|section]]'. This update also fixes an issue where, if the browser crashed while previewing an edit to a single section, saving this edit could overwrite the entire page with just that section’s content. [https://phabricator.wikimedia.org/T62744][https://phabricator.wikimedia.org/T24029][https://phabricator.wikimedia.org/T155097] * Wikivoyage wikis can use [[mw:Special:MyLanguage/Help:Extension:Kartographer#Markers and counters|colored map markers in the article text]]. The text of these markers will now be shown in contrasting black or white color, instead of always being white. Local workarounds for the problem can be removed. [https://phabricator.wikimedia.org/T369454] * The Activity tab in the Wikipedia Android app is now available for all users. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging. [https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/Activity_Tab_Experiment] * The Reader Growth team is launching an experiment called "Image browsing" to test how to make it easier for readers to browse and discover images on Wikipedia articles. This experiment, a mobile-only A/B test, will go live on English Wikipedia in the week of November 17 and will run for four weeks, affecting 0.05% of users on English wiki. The test launched on November 3 on Arabic, Chinese, French, Indonesian, and Vietnamese wikis, affecting up to 10% of users on those wikis. [https://www.mediawiki.org/wiki/Readers/Reader_Growth/WE3.1.3_Image_Browsing] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example the inability to lock accounts on mobile sites has been fixed. [https://phabricator.wikimedia.org/T256185] '''Updates for technical contributors''' * [[wikitech:Help talk:Toolforge/Toolforge standards committee#November 2025 committee nominations|Nominations are open on Wikitech]] for new [[wikitech:Help:Toolforge/Toolforge standards committee|Toolforge standards committee]] members. The committee oversees the Toolforge [[wikitech:Help:Toolforge/Right to fork policy|Right to fork policy]] and [[wikitech:Help:Toolforge/Abandoned tool policy|Abandoned tool policy]] among other duties. Nominations will remain open through 2025-11-28. * The [[w:JSON Web Token#Standard fields|JWT issuer field]] in [[mw:Special:MyLanguage/OAuth/For Developers#OAuth 2|OAuth 2 access tokens]] for [[m:Special:MyLanguage/Help:Unified login|SUL wikis]] has been changed to <code><nowiki>https://meta.wikimedia.org</nowiki></code>. Old access tokens will still work. [https://phabricator.wikimedia.org/T399199] * The [[w:JSON Web Token#Standard fields|JWT subject field]] in [[mw:Special:MyLanguage/OAuth/For Developers#OAuth 2|OAuth 2 access tokens]] will soon change from <code><user id></code> to <code dir=ltr style="white-space:nowrap">mw:<identity type>:<user id></code>, where <code><identity type></code> is typically <code dir=ltr>CentralAuth:</code><!-- not a typo --> (for [[m:Special:MyLanguage/Help:Unified login|SUL wikis]]) or <code dir=ltr style="white-space:nowrap">local:<wiki id></code> (for other wikis). This is to avoid conflicts between different user ID types, and to make OAuth 2 access tokens and the <code>sessionJwt</code> cookie more similar. Old access tokens will still work. [https://phabricator.wikimedia.org/T399199] * MediaWiki's block messages ([[MediaWiki:Blockedtext|blockedtext]], [[MediaWiki:Blockedtext-partial|blockedtext-partial]], [[MediaWiki:Autoblockedtext|autoblockedtext]], [[MediaWiki:Systemblockedtext|systemblockedtext]], [[MediaWiki:Blockedtext-tempuser|blockedtext-tempuser]], [[MediaWiki:Autoblockedtext-tempuser|autoblockedtext-tempuser]]) now support additional parameters indicating whether the user is blocked from editing their own user talk page <code><nowiki>$9</nowiki></code> or emailing other users <code><nowiki>$</nowiki><nowiki>10</nowiki></code>. [https://phabricator.wikimedia.org/T285612] * A <code>REL1_45</code> branch for MediaWiki core and each of the extensions and skins in Wikimedia git has been created. This is the first step in the release process for MediaWiki 1.45.0, scheduled for late November 2025. If you are working on a critical bug fix or working on a new feature, you may need to take note of this change. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/ZUY7TY3Z6XPZWZVAZV63OPO5OW52Q6GE/] * The process for generating CirrusSearch dumps has been updated due to slowing performance. If you encounter any issues migrating to the replacement dumps, please contact the Search Platform Team for support. [https://phabricator.wikimedia.org/T366248][https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/3KQPOR6ACVN6OVLMLZPIBXQSWQKW4E3K/] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.2|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/46|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W46"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:38, 10 November 2025 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29606150 --> == Wikipedia translation of the week: 2025-47 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Elephant communication]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Three elephant's curly kisses.jpg|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Elephants communicate''' via touching, visual displays, vocalisations, seismic vibrations, and semiochemicals. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:24, 17 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29627457 --> == Tech News: 2025-47 == <section begin="technews-2025-W47"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/47|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Readers/Reader Experience|Reader Experience team]] is experimenting with [[mw:Special:MyLanguage/Readers/Reader Experience/WE3.3.4_Reading lists|reading lists on mobile web]], allowing logged-in readers with no edits to save private lists of articles for later. The experiment is running on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias since the week of 10 November, and will begin on English Wikipedia the week of 17 November. * Users who can’t receive their email verification code during login can now get help by submitting a form on a new special page. This update is part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] initiative. If your account has an email address, please make sure you still have access to it. When logging in from a new device or location without 2FA, you may be asked to enter a 6-digit code sent by email to finish logging in. [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security#Why are you requiring me to enter a code from my email to log in? Can I opt out of this?|Learn more]]. * One new wiki has been created: a {{int:project-localized-name-group-wikisource}} in [[d:Q13324|Minangkabau]] ([[s:min:|<code>s:min:</code>]]) [https://phabricator.wikimedia.org/T408317] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * As part of the [[mw:Special:MyLanguage/Parsoid/Parser Unification|Parser Unification]] project, the Content Transform Team rolled out Parsoid as the default parser to many low-traffic Wikipedias and is preparing the next step to high traffic ones. This message is an invitation for you to opt-in to Parsoid, as described in the [[mw:Special:MyLanguage/Help:Extension:ParserMigration|Extension:ParserMigration]] documentation, and identify any issues you might encounter with your own workflow using bots, gadgets, or user scripts. Please, let us know through the ''"Report Visual Bug"'' link in the Tools sidebar or create a phab ticket and tag the [[phab:project/view/5846|Content Transform Team in Phabricator]]. * Unsupported Tools: Several issues with [[:c:Special:MyLanguage/Commons:Video2commons|Video2Commons]] have been fixed, including filename-related upload failures, black-video imports, and retry handling. AV1 support has also been added. Ongoing work focuses on backend stability, ffmpeg errors, subtitle imports, metadata handling, and playlist uploads. To track specific tasks, check the [[phab:tag/video2commons/|Phabricator board]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.3|MediaWiki]] '''Meetings and events''' * Save the date for the next Wikimedia Hackathon happening in Milan, Italy from May 1–3, 2026. Registration will open in January 2026. [https://pretix.eu/wikimedia/Hackathon-2026/ Scholarship applications are currently open], and will close on November 28, 2025. If you have any questions, please email <bdi lang="en" dir="ltr">hackathon@wikimedia.org</bdi>. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/47|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W47"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:27, 17 November 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29627455 --> == Wikipedia translation of the week: 2025-48 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Animal-made art]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Painting Queen 1024x768.png|center|300px|]] <div style="text-align:left; padding: .4em;"> '''Animal-made art''' consists of works by non-human animals, that have been considered by humans to be artistic, including visual works, music, photography, and videography. Some of these are created naturally by animals, often as courtship displays, while others are created with human involvement. There have been debates about the copyright status of these works, with the United States Copyright Office stating in 2014 that works that lack human authorship cannot have their copyright registered at the US Copyright Office. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:13, 24 November 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29627457 --> == Tech News: 2025-48 == <section begin="technews-2025-W48"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/48|Translations]] are available. '''Updates for editors''' * Last week, the [[mw:Special:MyLanguage/Wikimedia Search Platform|Wikimedia Search Team]] recreated the "DWIM" (Do What I Mean) gadget functionality server-side, for Russian and Hebrew Wikipedias. This feature adds cross-keyboard suggestions to the standard search-box suggestions. For example, searching for ''<span lang="und" dir="ltr">cxfcnmt</span>'' on Russian Wikipedia will now add suggestions for ''<span lang="ru" dir="ltr">счастье</span>'' ("happiness") that the user probably intended. They plan to enable this feature for other Russian and Hebrew wikis this week. [https://phabricator.wikimedia.org/T408734] * Later this week, users of the "{{int:codemirror-beta-feature-title}}" [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] will have syntax highlighting available in [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]]. This requires that the "{{int:discussiontools-preference-sourcemodetoolbar}}" preference be set. [https://phabricator.wikimedia.org/T407918] * [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|Campaign events extension]] – the set of tools for coordinating events and other on-wiki collaborations has now been deployed to all Wikimedia wikis. A new feature known as [[m:Special:MyLanguage/CampaignEvents/Collaborative contributions|Collaborative contribution]] to help organizers and participants see the impact of activities has also been added. Join the upcoming [[m:Special:MyLanguage/Event:Connection learning session 3|learning session]] to see the new feature in action and share your feedback. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:24}} community-submitted {{PLURAL:24|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the bug which stopped CodeReviewBot from working, has now been fixed. [https://phabricator.wikimedia.org/T410417] '''Updates for technical contributors''' * Users of Wikimedia API can join a usability study to help validate the new design of Wikimedia REST API sandboxes. Interested participants should fill the [https://wikimediafoundation.limesurvey.net/487662 recruitment survey]. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/IREJRRWTZTGCYWQHDMSNJFTQAEPOOAE3/] * The MediaWiki Interfaces team is deprecating XSLT stylesheets within the Action API. Support for <code dir=ltr>format=xml'''&xlst={stylesheet}'''</code> will be removed from Wikimedia projects by the end of November, 2025. In addition, it will soon be disabled by default in MediaWiki release versions: v1.43 (LTS), v1.44, and v1.45. Support for XSLT stylesheets will be fully removed from MediaWiki v1.46 (expected to release between April and May 2026). [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/5AX7UWAVVUNUSBOIRHMNOKWOZ5EZI3JX/] * The WDQS legacy endpoint ([https://query-legacy-full.wikidata.org/ query-legacy-full.wikidata.org]) will be decommissioned at the end of December 2025, and finally closed down on 7th January 2026. After this date, users should expect requests to query.wikidata.org that require the full graph to fail or return invalid results if they are not rewritten to use SPARQL federation. The team encourages users to ensure that tools and workflows use the supported WDQS endpoints (<span dir=ltr><nowiki>https://query.wikidata.org/</nowiki></span> - Main graph or <span dir=ltr><nowiki>https://query-scholarly.wikidata.org/</nowiki></span> - Scholarly graph). For support with migrating use cases, please review the [[d:Special:MyLanguage/Wikidata:Data_access|Data Access]] and [[d:Wikidata:Request_a_query|Request a Query]] pages for details and assistance on alternative access methods. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.4|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/48|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W48"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:57, 24 November 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29702226 --> == Wikipedia translation of the week: 2025-49 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Halachic state]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The term "'''halachic state'''" (Hebrew: מְדִינַת הֲלָכָה‎ Medīnat Hălāḵā) refers to a sovereign state that endorses Judaism in an official capacity and governs by Jewish religious law. It has been a subject of discussion among Orthodox Jews, particularly with regard to modern Israel, which, although a Jewish state, is not classified as a theocracy. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 08:01, 1 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29719355 --> == Tech News: 2025-49 == <section begin="technews-2025-W49"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/49|Translations]] are available. '''Updates for editors''' * The Wikipedia Year in Review 2025 will be available on December 2 for users of iOS and Android Wikipedia apps, featuring new personalized insights, updated reading highlights, and refreshed designs. Learn more on the review's [[mw:Special:MyLanguage/Wikimedia Apps/Team/Wikipedia Year in Review/Updates|project page]]. * The Growth team is working on improving the text and presentation of the Verification Email sent to new users to make them more welcoming, useful and informative. Some new text have been drafted for A/B testing and you can help by translating them. See [[phab:T396155|Phabricator]]. * [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]] will now be deployed at Japanese, Urdu and Chinese Wikipedias on December 2. Add a link is based on a prediction model that suggests links to be added to articles. While this feature has already been available on most Wikipedias, the prediction model could not support certain languages. A new model has now been developed to handle these languages, and it will be gradually rolled out to other Wikipedias over time. If you would like to know more, please contact [[mw:user:Trizek (WMF)|Trizek (WMF)]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:34}} community-submitted {{PLURAL:34|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where search boxes on some Commons pages showed no results due to switch from SpecialSearch to MediaSearch, has now been fixed. [https://phabricator.wikimedia.org/T399476] * Two new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q36846|Toki Pona]] ([[w:tok:|<code>w:tok:</code>]]) [https://phabricator.wikimedia.org/T404457] ** a {{int:project-localized-name-group-wikiquote}} in [[d:Q33655|Nigerian Pidgin]] ([[q:pcm:|<code>q:pcm:</code>]]) [https://phabricator.wikimedia.org/T408318] '''Updates for technical contributors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.5|MediaWiki]] '''In depth''' * The Wikimedia Foundation is in the early stages of exploring approaches to '''Article guidance'''. The initiative aims to identify interventions that could help new editors easily understand and apply existing Wikipedia practices and policies when creating an article. The project is in the exploration and early experimental design phase. All community members are encouraged to [[mw:Special:MyLanguage/Article guidance|learn more]] about the project, and share their thoughts on [[mw:Special:MyLanguage/Talk:Article guidance|the talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/49|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W49"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:58, 1 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29732328 --> == Wikipedia translation of the week: 2025-50 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:ru:Сто лошадей]]'''<br /> <small>''([[:en:One Hundred Horses]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:A_Hundred_Steeds.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''One Hundred Horses''''' (Chinese: 百駿圖) is a Qing dynasty silk and ink painting by Giuseppe Castiglione. It was painted in 1728 for the Yongzheng emperor. The painting depicts a hundred horses in a variety of poses and activities, combining Western realism with traditional Chinese composition and brushwork. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:29, 8 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29719355 --> == Tech News: 2025-50 == <section begin="technews-2025-W50"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/50|Translations]] are available. '''Weekly highlight''' * Anybody who wishes to secure their user account can now use [[m:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]] (2FA). This is available to all registered users of all Wikimedia projects. This is part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] initiative. Later, 2FA will be required for all users who can take security- or privacy-sensitive actions. '''Updates for editors''' * Following last week's deployments, the [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]] feature, which allows editors to add suggested links during editing, will be available to an additional [[Phab:T410469|33 Wikipedias]] starting on 9 December. This expansion is possible thanks to the new prediction model that now supports all languages, including those that were previously not covered. While the feature has been available on most Wikipedias for some time, this rollout brings us closer to using the improved model everywhere. If you have any questions or would like more details please contact [[mw:user:Trizek (WMF)|Trizek (WMF)]]. * Last week, the [[mw:Special:MyLanguage/Wikimedia Search Platform|Search Platform team]] added [[w:en:Transliteration|transliterated]] as-you-type search suggestions to Georgian wikis. If there are only a few regular search suggestions, then queries in Latin or Cyrillic script [[phab:T127003|are now rewritten into Georgian script]] to look for more matches. For example, searching for either <bdi lang="ka-Latn" dir="ltr">''bedniereba''</bdi> or <bdi lang="ka-Cyrl" dir="ltr">''бедниереба''</bdi> will now suggest the existing article about <bdi lang="ka" dir="ltr">ბედნიერება</bdi> ("happiness"). You can recommend other languages where transliterated suggestions would be useful [[phab:T375215|on Phabricator]] for future development. * Later this week, a controlled experiment will begin for editors on the 100 largest Wikipedias who are editing a section in the mobile web visual editor. 50% of these editors will notice a new "Edit full page" button that will enable them to expand their editing session to the whole page. This feature is intended to make it easier for people on mobile web to edit any article section, regardless of which section-edit icon they tapped to begin. The experiment will last ~4 weeks. You can find [[phab:T409112|more details]] about the project. * Later this week, the [[mw:Special:MyLanguage/Readers/Reader Growth|Reader Growth team]] will launch a [[mw:Special:MyLanguage/Readers/Reader Growth/WE3.1.14 Expanded Mobile Sections|mobile web experiment]] to expand all article sections by default (currently they are collapsed by default) and pin the section header the user is currently reading to the top of the page. The experiment will affect 10% of users on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias. [https://phabricator.wikimedia.org/T409485] * The [[mw:Special:MyLanguage/Wikimedia Apps/Team/Wikipedia Year in Review/2025 Year in Review|Wikipedia Year in Review 2025]], a feature in the Wikipedia mobile apps (iOS and Android) that provides users with a personalised summary of their engagement with Wikipedia over the year, is now available on the iOS and Android apps. This edition includes expanded personalised insights, improved reading highlights, new donor messaging, and updated designs. Open the app to view your Year in Review and explore your reading journey from 2025. * A recent software bug caused edits made with VisualEditor to make unintended changes to wikitext, including removing whitespace and replacing spaces with underscores in wikilinks inside citations. This was partially fixed last week, and further fixes are in progress. Editors who used VisualEditor between November 28 and December 2 should review their edits for unexpected modifications. [https://phabricator.wikimedia.org/T411238] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the incorrect handling of URLs copied from the address bar of Microsoft Edge users, has been resolved. [https://phabricator.wikimedia.org/T341281] '''Updates for technical contributors''' * Starting this week, users of the "{{int:codemirror-beta-feature-title}}" [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] will have [[mw:Special:MyLanguage/Help:Extension:CodeMirror|CodeMirror]] as the editor for Lua, JavaScript, CSS, JSON and Vue content models, instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]]. With this, the [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Linting|linters]] will be upgraded. This is part of a larger effort to eventually replace CodeEditor and provide a consistent code editing experience. [https://phabricator.wikimedia.org/T373711] * Developers are encouraged to take the [https://wikimediafoundation.limesurvey.net/552643 2025 Developer Satisfaction Survey], which remains open until 5 January 2026. If you build software for the Wikimedia ecosystem and would like to share your experiences or feedback, your participation is greatly appreciated. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/W4WBKO6Q55UWWCCSFWQATKEXBEHP3QNR/] * There is no new MediaWiki version this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/50|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W50"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:46, 8 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29738112 --> == Wikipedia translation of the week: 2025-51 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:First Universal Races Congress]]'''<br /> <small>''([[:fr:Premier Congrès universel des races]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Universal Races Congress seated outside the entrance to the Imperial Institute, London, 1911.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''First Universal Races Congress''' met in 1911 for four days at the University of London as an early effort at anti-racism. Speakers from a number of countries discussed race relations and how to improve them. The congress, with 2,100 attendees, was organised by prominent humanists of that era. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:56, 15 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29779168 --> == Tech News: 2025-51 == <section begin="technews-2025-W51"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/51|Translations]] are available. '''Updates for editors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:18}} community-submitted {{PLURAL:18|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, one of the fixes addressed an issue for temporary accounts adding an external URL, which triggered an hCaptcha request in more cases than intended, and did not display the required popup on the first attempt to publish the edit. [https://phabricator.wikimedia.org/T411927] '''Updates for technical contributors''' * To improve database and site performance, external links to Wikimedia projects will no longer be stored in the database. This means they will not be searchable in [[{{#special:LinkSearch}}]], will not be checked by the Spam Blacklist or AbuseFilter as new links, and will not be in the <code dir=ltr>externallinks</code> table on database replicas. In the future this may be extended to other highly-linked trusted websites on a per-wiki basis, such as Creative Commons links on Wikimedia Commons. [https://phabricator.wikimedia.org/T405005] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.7|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/51|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W51"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:03, 15 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29796010 --> == Wikipedia translation of the week: 2025-52 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pin Malakul]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Pin Malakul, January 1922.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Pin Malakul''' (24 October 1903 – 5 October 1995) was a Thai professor, educator and writer. His contributions to education in Thailand include the establishment of various institutions of higher education, the introduction of fixed class schedules, and the implementation of teacher-training programmes. In his career he served as Director-General of the Department of General Education, later becoming Permanent Secretary, and Minister, of Education. He was also a member of the executive board of UNESCO. His writings earned him the title of National Artist in 1987, and the 100th anniversary of his birth was celebrated by the UNESCO in 2003 as recognition of his contribution to the advancement of education in Thailand and Southeast Asia. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> -[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:26, 22 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29802495 --> == Tech News: 2025-52 == <section begin="technews-2025-W52"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2025/52|Translations]] are available. '''Updates for editors''' * From January, edit filters [[mw:Special:MyLanguage/Extension:AbuseFilter/Access flags|can be set]] to automatically suppress their details such as rules and list of attempted edits and actions. This will help oversighters use edit filters to prevent doxxing or other suppressible material. [https://phabricator.wikimedia.org/T290324] * The next issue of Tech News will be sent out on 12 January 2026 because of the end of year holidays. Thank you to all of the translators, and people who submitted content or feedback, this year. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:16}} community-submitted {{PLURAL:16|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the crash that occurred when tapping "First Steps" in the Wikipedia Android Year in Review has now been fixed, and the feature opens as expected. [https://phabricator.wikimedia.org/T411546] '''Updates for technical contributors''' * Interface elements such as diffs and categories generated by MediaWiki used to have the attribute <code dir=ltr>data-mw="interface"</code> to distinguish from wiki content. The attribute has been replaced with <code dir=ltr>data-mw-interface=""</code>, to avoid potential conflicts with other <code dir=ltr>data-mw</code> attributes, which are generated by Parsoid. [https://phabricator.wikimedia.org/T409187] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] There is no new MediaWiki version this week or next week. '''Meetings and events''' * The [[mw:Wikimedia Hackathon Northwestern Europe 2026|Wikimedia Hackathon Northwestern Europe 2026]] will take place on 13-14 March 2026 in Arnhem, the Netherlands. Applications just opened mid-December and will close in mid-January or earlier if capacity is reached. With space for approximately 100 participants, early application is encouraged. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2025/52|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2025-W52"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:46, 22 December 2025 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29831856 --> == Wikipedia translation of the week: 2026-01 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:The Morning of the Magicians]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Le Matin des magiciens, couverture.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''The Morning of the Magicians: Introduction to Fantastic Realism''''' (French: Le Matin des magiciens: Introduction au réalisme fantastique) is a 1960 book by the journalists Louis Pauwels and Jacques Bergier. It covers topics like cryptohistory, ufology, occultism in Nazism, alchemy, spiritual philosophy. The second half of the book is entirely dedicated to the Nazi-Occult connections; the book is widely credited with the proliferation of numerous myths related to occultism in Nazism. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:20, 29 December 2025 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29802495 --> == Wikipedia translation of the week: 2026-02 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Somaliland War of Independence]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Somaliland, fighters of the Somali National Movement (SNM), 1980s.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Somaliland War of Independence''' was a rebellion waged by the Somali National Movement (SNM) against the ruling military junta in Somalia led by General Siad Barre lasting from its founding on 6 April 1981 and ended on 18 May 1991 when the SNM declared what was then northern Somalia independent as the Republic of Somaliland. The conflict served as the main theater of the larger Somali Rebellion that started in 1978. The conflict was in response to the harsh policies enacted by the Barre regime against the main clan family in Somaliland, the Isaaq, including a declaration of economic warfare on the clan-family. These harsh policies were put into effect shortly after the conclusion of the disastrous Ogaden War in 1978. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:00, 5 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29871911 --> == Wikipedia translation of the week: 2026-03 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Pietro Lauro]]'''<br /> <small>''([[:en:Pietro Lauro]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Master I.A.V.F., Pietro Lauro, born 1508, Modenese Poet and Scholar (obverse), 1555, NGA 45072.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Pietro Lauro''', conosciuto anche come Pietro Lauro Modonese o Pietro Lauro da Modona (Modena o dintorni, 1510 circa – Venezia, 1568 circa) è stato un traduttore, scrittore e divulgatore scientifico italiano. Nonostante non si conosca gran parte della sua biografia, fu uno dei poligrafi italiani più conosciuti del Cinquecento. La sua produzione raccoglie traduzioni dal latino, dal greco e dallo spagnolo e riguardano opere di autori classici, stranieri e protestanti. Lauro si dimostrò abile nel trattare testi con temi molto diversi, come la filosofia, l'architettura, la medicina, il giardinaggio, l'agronomia, le scienze biologiche, la storia, la teologia e l'astronomia. Si cimentò anche nella scrittura di un poema cavalleresco sullo stile di quelli spagnoli, il Polendo, sua magnum opus in questo senso. Aderente alla Riforma protestante, sebbene le sue trasposizioni siano state oggetto di critiche già degli autori a lui contemporanei, che le giudicarono troppo letterali, rozze e imparziali, a Lauro si deve il merito di aver ultimato la traduzione in lingua volgare di numerosi testi sia classici, sia scientifici, sia epistolari. I suoi lavori ebbero una notevole diffusione, non solo tra i letterati veneziani della sua epoca, ma in tutta Italia, tanto che alcune sue traduzioni vengono ancora oggi ristampate in nuove edizioni. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:45, 12 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29894468 --> == Tech News: 2026-03 == <section begin="technews-2026-W03"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/03|Translations]] are available. '''Weekly highlight''' * The Wikimedia Foundation has shared some guiding questions for the July 2026–June 2027 Annual Plan on [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2026-2027/Product & Technology OKRs|Meta]] and ''[[diffblog:2025/12/10/shaping-wikimedia-foundations-2026-2027-annual-goals-key-questions-for-the-wikimedia-movement/|Diff]]''. These focus on global trends, faster and healthier experimentation, better support for newcomers, strengthening editors and advanced users, improving collaboration across projects, and growing and retaining readership. Feedback and ideas are welcome on the [[m:Talk:Wikimedia Foundation Annual Plan/2026-2027|talk page]]. '''Updates for editors''' * As part of the current work of Community Tech team on the [[m:Special:MyLanguage/Community Wishlist/W372|Multiple watchlists]] project, the display of [[Special:EditWatchlist|EditWatchlist]] will be updated as a first step towards multiple watchlists. Additionally, the pagination on [[Special:Search|Search]] will be updated too, as a part of the work on the [[m:Special:MyLanguage/Community Wishlist/W186|Revamp pagination / page navigation]] wish. [https://phabricator.wikimedia.org/T411596] * [[m:Special:GlobalWatchlist|The Global Watchlist]] is a MediaWiki [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] that lets you see your watchlists from different wikis on the same page. It was recently updated to look more like the regular [[Special:Watchlist|Watchlist]], such as preparing it for temporary accounts in IP masking (including rerouting user links to contributions pages), making page titles bold, and opening links in edit summaries and tags in new browser tabs. [https://phabricator.wikimedia.org/T398361][https://phabricator.wikimedia.org/T298919][https://phabricator.wikimedia.org/T273526][https://phabricator.wikimedia.org/T286309] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:28}} community-submitted {{PLURAL:28|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where global blocks did not have the option to disable sending emails, has now been fixed, and will be available for use in the week of January 13. [https://phabricator.wikimedia.org/T401293] '''Updates for technical contributors''' * The [[mw:Special:MyLanguage/VisualEditor/Citation tool|VisualEditor citation tool]] and [[mw:Special:MyLanguage/Help:Reference Previews|Reference Previews]] now support "map" as a reference type. [https://phabricator.wikimedia.org/T411083] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.10|MediaWiki]]/[[mw:MediaWiki 1.46/wmf.11|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/03|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W03"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:34, 12 January 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29907192 --> == Wikipedia translation of the week: 2026-04 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Volto di Palazzo Vecchio]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Piazza della signoria angolo via della ninna, palazzo vecchio, cantonata con testa scolpita 02.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> Il '''volto di Palazzo Vecchio''' (conosciuto anche come L'importuno o L'inopportuno) è un incisione su pietraforte attibuita a Michelangelo Buonarroti, scolpita in una delle pietre di Palazzo Vecchio a Firenze. Secondo le varie leggende, il profilo sarebbe stato realizzato come graffito dall'artista toscano, con soggetto un suo importunatore, un debitore, un condannato a morte o se stesso. Nel 2020, gli studiosi hanno ipotizzato possa invece trattarsi di un ritratto di Francesco Granacci, pittore amico di Michelangelo. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:14, 19 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-04 == <section begin="technews-2026-W04"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/04|Translations]] are available. '''Updates for editors''' * The tray shown on [[Special:Diff|Special:Diff]] in mobile view has been redesigned. It is now collapsed by default, and incorporates a link to undo the edit being viewed, making it easier for mobile editors and reviewers to take action while keeping the interface uncluttered. [https://phabricator.wikimedia.org/T402297] * [[m:Special:GlobalWatchlist|The Global Watchlist]] lets you view your watchlists from multiple wikis on one page. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] continues to improve — it now automatically determines the text direction (ensuring correct display of sites with unusual domain names) and shows detailed descriptions for log actions. Later this week, a new permanent link for page creations and CSS classes for each entry element will be added. [https://phabricator.wikimedia.org/T412505][https://phabricator.wikimedia.org/T287929][https://phabricator.wikimedia.org/T262768][https://phabricator.wikimedia.org/T414135] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the previously observed issue in Vector 2022, where anchor link targets were obscured by the sticky header, has now been addressed. [https://phabricator.wikimedia.org/T406114] '''Updates for technical contributors''' * As mentioned in the [[m:Special:MyLanguage/Tech/News/2025/44|October 2025 deprecation announcement]], MediaWiki Interfaces team will begin sunsetting all transform endpoints containing a trailing slash from the MediaWiki REST API the week of January 26. Changes are expected to roll out to all wikis on or before January 30th. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found, compared, and tested using the [https://test.wikipedia.org/wiki/Special:RestSandbox REST Sandbox]. If you have questions or encounter any problems, please file a ticket in Phabricator to the [https://phabricator.wikimedia.org/project/view/6931/ #MW-Interfaces-Team board]. * Interactive reference documentation for the [[mw:Special:MyLanguage/Wikimedia REST API|Wikimedia REST API]] has moved. Requests to API docs previously hosted through [[mw:Special:MyLanguage/RESTBase|RESTBase]] (e.g.: <code dir=ltr>https://en.wikipedia.org/api/rest_v1/</code>) are now redirected to the [[w:en:Special:RestSandbox|REST Sandbox]]. * The [[mw:Special:MyLanguage/Wikidata Platform|WMF Wikidata Platform team]] (WDP) has published its [[d:Special:MyLanguage/Wikidata:Wikidata Platform team/Newsletter|January 2026 newsletter]]. It includes updates on the legacy full-graph endpoint decommissioning, the User-Agent policy change, the monthly Blazegraph migration office hours, and efforts to reduce regressions caused by the legacy endpoint shutdown. As a reminder, you can [[m:Special:MyLanguage/Global message delivery/Targets/WDP team updates|subscribe to the WDP newsletter]]! * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.12|MediaWiki]] '''Meetings and events''' * The [[mw:Wikimedia Hackathon Northwestern Europe 2026|Wikimedia Hackathon Northwestern Europe 2026]] will take place on 13-14 March 2026 in Arnhem, the Netherlands. Applications opened mid-December and will close soon or when capacity is reached. It's a two-day, technically oriented hackathon bringing together Wikimedians from the region. Hope to see you there! '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/04|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W04"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:30, 19 January 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29943403 --> == Wikipedia translation of the week: 2026-05 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Raffaello Kobayashi]]'''<br /> <small>''([[:en:Raffaello Kobayashi]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Raffaello Kobayashi''', nato Raffaele Sanzio (Bari, 14 gennaio 1917 – Yokohama, 1 aprile 2011), è stato un militare italiano naturalizzato giapponese. Sommergibilista durante la Seconda guerra mondiale, prestò servizio per tutte e tre le principali Potenze dell'Asse: Regno d'Italia, Germania nazista e Impero giapponese. Alla fine della guerra si nascose in Giappone per evitare di subire l'internamento in un campo di prigionia, divenendo poi cittadino nipponico e cambiando il proprio nome. Prese parte all'affondamento della HMS Calypso nel 1940, primo successo italiano in campo navale nel corso del conflitto mondiale. Con l'abbattimento di un bombardiere statunitense il 22 agosto 1945, otto giorni dopo il discorso di resa del Giappone alle potenze alleate della seconda guerra mondiale, a bordo del Comandante Cappellini, sarebbe stata l'ultima persona in assoluto a mettere fuori combattimento un velivolo degli Alleati nella stessa guerra. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:05, 26 January 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-05 == <section begin="technews-2026-W05"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/05|Translations]] are available. '''Updates for editors''' * Wikimedia Foundation invites comments on [[m:Special:MyLanguage/Product and Technology Advisory Council/Year1 Reflections and Proposed Way Forward 2026 Update|proposed future]] of the [[:m:Special:MyLanguage/Product and Technology Advisory Council|Product and Technology Advisory Council]] until 28 February. * All users with registered accounts can now use passkeys for [[m:Special:MyLanguage/Help:Two-factor authentication|two-factor authentication]] (2FA). Passkeys are a simple way to log in without using a second device. They verify the user's identity using a fingerprint, face scan, or a PIN code. To set up a passkey, first set up a regular 2FA method. Currently, to log in with a passkey, users must also use a password. Later this quarter, passwordless login will allow users to log in with a single click and a passkey. Users with advanced rights will also be required to have 2FA enabled. This is part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] project. * Unregistered contributors on blocked IPs or blocked IP ranges can now interact on-wiki to appeal a block by creating a temporary account to appeal a block on the user talk page, unless the "prevent this user from editing their own talk page" is enabled. This solves the problem of logged-out users unable to use the default unblock process via user talk page. [https://phabricator.wikimedia.org/T398673] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the Two-Factor Authentication (2FA) methods description on the management page has been updated. It is now clearer and easier for users to understand and make use of. [https://phabricator.wikimedia.org/T332385] '''Updates for technical contributors''' * A new AbuseFilter variable, <code>account_type</code>, has been added to provide a reliable way to determine the account type being created in the <code>createaccount</code> and <code>autocreateaccount</code> actions. As part of this change, the variable <code>accountname</code> has been renamed to <code>account_name</code>, and <code>accountname</code> is now deprecated. Edit filter managers should update any filters that use hardcoded account type checks or the deprecated variable. [https://phabricator.wikimedia.org/T414049] * Image thumbnails that are requested in non-standard sizes, and using non-standard methods such as direct requests to <code dir=ltr><nowiki>upload.wikimedia.org/…</nowiki></code> will stop working in the near future. This change is to prevent ongoing external abuse by web-scrapers and bots. Some users with custom CSS/JS, Interface Admins who can fix gadgets and local skins, and Tool-authors, will need to update their code to use standard thumbnail sizes. [[phab:T414805|Details, search-links, and examples of how to fix them, are available in the task]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.13|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/05|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W05"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:18, 26 January 2026 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=29969530 --> == Wikipedia translation of the week: 2026-06 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Censorship in the Czech Republic]]'''<br /> <small>''([[:cs:Cenzura v Česku]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Censorship in the Czech Republic''' had been highly active until 17 November 1989 and the fall of Communism in the former Czechoslovakia. Czech Republic was ranked as the 13th most free country in the World Press Freedom Index in 2014. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:32, 2 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-06 == <section begin="technews-2026-W06"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/06|Translations]] are available. '''Updates for editors''' * The "{{int:pageinfo-toolboxlink}}" feature, which gives validating information about a page ([{{fullurl:{{FULLPAGENAME}}|action=info}} example]), now automatically includes a table of contents. If there is a local [[{{ns:8}}:Pageinfo-header]] page created by individual users, it can now be removed. [https://phabricator.wikimedia.org/T363726] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, VisualEditor previously added bold or italic formatting inside link descriptions, making the wikicode complex. This has now been fixed. [https://phabricator.wikimedia.org/T409669] '''Updates for technical contributors''' * There was no XML dump on 20 January. Additionally, from now on, dumps will be generated once per month only. [https://phabricator.wikimedia.org/T414389] * The MediaWiki Interfaces team removed support for all transform endpoints containing a trailing slash from the [https://www.mediawiki.org/wiki/Special:MyLanguage/API:REST%20API MediaWiki REST API]. All API users currently calling those endpoints are encouraged to transition to the non-trailing slash versions. If you have questions or encounter any problems, please file a ticket in phabricator to the [https://phabricator.wikimedia.org/project/view/6931/ #MW-Interfaces-Team board]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.14|MediaWiki]] '''Weekly highlight''' * Users are reminded that the Wikimedia Foundation has shared some guiding questions for the July 2026–June 2027 Annual Plan on [[m:Special:MyLanguage/Wikimedia Foundation Annual Plan/2026-2027/Product & Technology OKRs|Meta]] and ''[[diffblog:2025/12/10/shaping-wikimedia-foundations-2026-2027-annual-goals-key-questions-for-the-wikimedia-movement/|Diff]]''. These focus on global trends, faster and healthier experimentation, better support for newcomers, strengthening editors and advanced users, improving collaboration across projects, and growing and retaining readership. Feedback and ideas are welcome on the [[m:Talk:Wikimedia Foundation Annual Plan/2026-2027|talk page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/06|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W06"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:44, 2 February 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30000986 --> == Wikipedia translation of the week: 2026-07 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Petites Heures of Jean de France, Duc de Berry]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Jacquemart de Hesdin 002.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Petites Heures of Jean de France, Duc de Berry''' is an illuminated book of hours commissioned by John, Duke of Berry between 1375 and 1385–90. It is known for its ornate miniature leaves and border decorations. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:59, 9 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-07 == <section begin="technews-2026-W07"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/07|Translations]] are available. '''Updates for editors''' * [[File:Maki-gift-15.svg|12px|link=|class=skin-invert|Wishlist item]] Logged-in contributors who manage large or complex watchlists can now organise and filter watched pages in ways that improve their workflows with the new [[mw:Special:MyLanguage/Help:Watchlist labels|Watchlist labels]] feature. By adding custom labels (for example: pages you created, pages being monitored for vandalism, or discussion pages) users can more quickly identify what needs attention, reduce cognitive load, and respond more efficiently. This improves watchlist usability, especially for highly active editors. * A new feature available on [[Special:Contributions|Special:Contributions]] shows [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts|temporary accounts]] that are likely operated by the same person, and so makes patrolling less time-consuming. Upon checking contributions of a temporary account, users with access to temporary account IP addresses can now see a view of contributions from the related temporary accounts. The feature looks up all the IPs associated with a given temporary account within the data retention period and shows all the contributions of all temporary accounts that have used these IPs. [[mw:Special:MyLanguage/Trust and Safety Product/Temporary Accounts#February 2026: Improvements to the patroller tooling|Learn more]]. [https://phabricator.wikimedia.org/T415674] * When editors preview a wikitext edit, the reminder box that they are only seeing a preview (which is shown at the top), now has a grey/neutral background instead of a yellow/warning background. This makes it easier to distinguish preview notes from actual warnings (for example, edit conflicts or problematic redirect targets), which will now be shown in separate warning or error boxes. [https://phabricator.wikimedia.org/T414742] * The [[m:Special:GlobalWatchlist|Global Watchlist]] lets you view your watchlists from multiple wikis on one page. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] continues to improve — it now properly supports more than one Wikibase site, for example both [[d:|Wikidata]] and [[testwikidata:|testwikidata]]. In addition, issues regarding text direction have been fixed for users who prefer Wikidata or other Wikibase sites in right-to-left (RTL) languages. [https://phabricator.wikimedia.org/T415440][https://phabricator.wikimedia.org/T415458] * The automatic "magic links" for ISBN, RFC, and PMID numbers have been [[mw:Special:MyLanguage/Help:Magic links|deprecated in wikitext since 2021]] due to inflexibility and difficulties with localization. Several wikis have successfully replaced RFC and PMID magic links with equivalent external links, but a template was often required to replace the functionality of the ISBN magic link. There is now a new [[mw:Special:MyLanguage/Help:Magic words#isbn|built-in parser function]] <code dir=ltr><nowiki>{{#isbn}}</nowiki></code> available to replace the basic functionality of the ISBN magic link. This makes it easier for wikis who wish to migrate off of the deprecated magic link functionality to do so. [https://phabricator.wikimedia.org/T145604] * Two new wikis have been created: ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q35401|Jju]] ([[w:kaj:|<code>w:kaj:</code>]]) [https://phabricator.wikimedia.org/T413283] ** a {{int:project-localized-name-group-wikipedia}} in [[d:Q1186896|Nawat]] ([[w:ppl:|<code>w:ppl:</code>]]) [https://phabricator.wikimedia.org/T413273] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * A new global user group has been created: [[{{int:grouppage-local-bot}}|{{int:group-local-bot}}]]. It will be used internally by the software to allow community bots to bypass rate limits that are applied to abusive [[w:en:Web scraping|web scrapers]]. Accounts that are approved as bots on at least one Wikimedia wiki will be automatically added to this group. It will not change what user permissions the bot has. [https://phabricator.wikimedia.org/T415588] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.15|MediaWiki]] '''Meetings and events''' * The [[mw:Special:MyLanguage/MediaWiki Users and Developers Conference Spring 2026|MediaWiki Users and Developers Conference, Spring 2026]] will be held March 25–27 in Salt Lake City, USA. This event is organized by and for the third-party MediaWiki community. You can propose sessions and register to attend. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/AZBWVI46SDEB65PGR5J6E4TYOQQEZXM7/] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/07|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W07"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 23:31, 9 February 2026 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30026671 --> == Wikipedia translation of the week: 2026-08 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Lysmata grabhami]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Lysmata grabhami1.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Lysmata grabhami''''' is a species of saltwater shrimp in the family Hippolytidae. It was first described by Gordon in 1935. It occurs in the tropical and subtropical Atlantic Ocean and is a cleaner shrimp, operating a cleaning station to which fish come to have parasites removed. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 13:45, 16 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=29945240 --> == Tech News: 2026-08 == <section begin="technews-2026-W08"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/08|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Wikimedia Site Reliability Engineering|SRE Team]] will be performing a cleanup of Wikimedia's [[m:Special:MyLanguage/Etherpad|Etherpad]] instance, the web-based editor for real-time collaborative document editing. All pads will be permanently deleted after 30 April, 2026 – if there are still migration projects in progress at that point the team can revisit the date on a case by case basis. Please create local backups of any content you wish to keep, as deleted data cannot be recovered. This cleanup helps reduce database size and minimize infrastructure footprint. Etherpad will continue to support real-time collaboration, but long-term storage should not be expected. Additional cleanups may occur in the future without prior notice. [https://phabricator.wikimedia.org/T415237] '''Updates for editors''' * The Information Retrieval team will be launching an [[mw:Special:MyLanguage/Readers/Information Retrieval/Phase 1|Android mobile app experiment]] that tests hybrid search capabilities which can handle both semantic and keyword queries. The improvement of on-platform search will enable readers to find what they’re looking for directly on Wikipedia more easily. The experiment will first be launched on Greek Wikipedia in late February, followed by English, French, and Portuguese in March. [https://diff.wikimedia.org/2026/01/08/semantic-search-making-it-easier-to-find-the-information-readers-want/ Read more] on Diff blog. [https://www.mediawiki.org/wiki/Readers/Information_Retrieval] * The Reader Growth team will run [[mw:Special:MyLanguage/Readers/Reader Growth/WE3.10.2 Mobile Table of Contents|an experiment]] for mobile web users, that adds a table of contents and automatically expands all article sections, to learn more about navigation issues they face. The test will be available on Arabic, Chinese, English, French, Indonesian, and Vietnamese Wikipedias. * Previously, site notices ([[{{ns:8}}:Sitenotice]] and [[{{ns:8}}:Anonnotice]]) would only render on the desktop site. Now, they will render on all platforms. Users on mobile web will now see these notices and be informed. Site administrators should be prepared to test and fix notices on mobile devices to avoid interference with articles. To opt out, interface admins can add <code dir="ltr">#siteNotice { display: none; }</code> to [[{{ns:8}}:Minerva.css]]. [https://phabricator.wikimedia.org/T138572][https://phabricator.wikimedia.org/T416644] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:19}} community-submitted {{PLURAL:19|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue on [[Special:RecentChanges|Special:RecentChanges]] has been fixed. Previously, clicking hide in the active filters caused the "view new changes since…" button to disappear, though it should have remained visible. The button now behaves as expected. [https://phabricator.wikimedia.org/T406339] '''Updates for technical contributors''' * New documentation is now available to help editors debug on-site search features. It supports troubleshooting when pages do not appear in results, when ranking seems unexpected, and when you need to inspect what content is being indexed, helping make search behavior easier to understand and analyze. [[mw:Help:CirrusSearch/Debug|Learn more]]. [https://phabricator.wikimedia.org/T411169] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.16|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/08|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W08"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:17, 16 February 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30086330 --> == Wikipedia translation of the week: 2026-09 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Elefante di Cremona]]'''<br /> <small>''([[:de:Elefant von Cremona]])&#32;([[:eo:Elefanto de Cremona]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Matthew Paris Elephant from Parker MS 16 fol 151v.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> L''''elefante di Cremona''' (Asia, prima del 1228 - Parma, gennaio 1248) fu un esemplare di elefante donato nel 1228 a Federico II di Svevia da parte del sultano ayyubide al-Malik al-Kamil durante gli incontri che porteranno alla Pace di Giaffa. Usato principalmente per le manifestazioni trionfali del sovrano, l'elefante è citato da numerosi cronachisti e testimoni dell'epoca ed è noto per aver trainato il Carroccio dopo la grande vittoria delle armate di Federico II nella battaglia di Cortenuova del 1237. Rimasto a lungo nell'immaginario popolare collettivo, l'animale venne ucciso durante alcuni scontri occorsi nelle settimane immediatamente precedenti alla battaglia di Parma. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 11:43, 23 February 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30097839 --> == Tech News: 2026-09 == <section begin="technews-2026-W09"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/09|Translations]] are available. '''Weekly highlight''' * [[mw:Special:MyLanguage/Edit check/Reference Check|Reference Check]] has been deployed to English Wikipedia, completing its rollout across all Wikipedias. The feature prompts newcomers to add a citation before publishing new content, helping reduce common citation-related reverts and improve verifiability. In A/B testing, the impact was substantial: newcomers shown Reference Check were approximately 2.2 times more likely to include a reference on desktop and about 17.5 times more likely on mobile web. [https://analytics.wikimedia.org/published/reports/editing/reference_check_ab_test_report_final_2025.html] '''Updates for editors''' * The [[mw:Special:MyLanguage/Extension:InterwikiSorting|InterwikiSorting extension]], which allowed for the [[m:Special:MyLanguage/Interwiki sorting order|sorting of interwiki links]], has been undeployed from Wikipedia. As a result, editors who had enabled interwiki link sorting in non-compact mode (full list format) will now see links reordered. The links moving forward will be listed in the alphabetical order of language code. [https://phabricator.wikimedia.org/T253764] * Later this week, people who are editing a page-section using the mobile visual editor, will notice a new "Edit full page" button. When tapped, you will be able to edit the entire article. This helps when the change you want to make is outside the section you initially opened. [https://phabricator.wikimedia.org/T387175][https://phabricator.wikimedia.org/T409112] * [[mw:Special:MyLanguage/Readers/Reader Experience|The Reader Experience team]] is inviting editors to assess whether dark mode should still be considered "beta" on their wiki, based on their experience of how well it functions on desktop and mobile. If the feature is deemed mature, editors can update the interface messages in <code dir=ltr>MediaWiki:skin-theme-description</code> and <code dir=ltr>MediaWiki:Vector-night-mode-beta-tag</code> to indicate that dark mode is ready and no longer considered beta. * The improved [[mw:Wikimedia_Apps/Team/iOS/Activity_Tab|Activity tab]] which displays user-insights is now available to all users of the Wikipedia iOS app (version 7.9.0 and later). Following earlier A/B testing that showed higher account creation among users with access to the feature, it has been rolled out to 100% of users along with some updates. The Activity tab now shows your edited articles in the timeline, offers editing impact insights like contribution counts and article view trends, and customization options to improve in-app experience for users. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, a bug that prevented [[mw:Special:MyLanguage/Extension:DiscussionTools|DiscussionTools]] from working on mobile has now been fixed, restoring full functionality. [https://phabricator.wikimedia.org/T415303] '''Updates for technical contributors''' * The [[m:Special:GlobalWatchlist|Global Watchlist]] lets you view your watchlists from multiple wikis on one page. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] that makes this possible continues to improve. The latest upgrade is the inclusion of a [[mw:Extension:GlobalWatchlist#hook|new hook]], <code dir=ltr>ext.globalwatchlist.rebuild</code>, which fires after each watchlist rebuild. This allows you to run gadgets and user scripts for the Special page. [https://phabricator.wikimedia.org/T275159] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.17|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/09|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W09"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:04, 23 February 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30119102 --> == Wikipedia translation of the week: 2026-10 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Treaty of the Danish West Indies]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:The Virgin islands of the United States of America; historical and descriptive, commercial and industrial facts, figures, and resources (1918) (14596880870).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Treaty of the Danish West Indies''' (Danish: Vestindiens traktat), officially the Convention between the United States and Denmark for cession of the Danish West Indies (Danish: Konventionen mellem USA og Danmark), was a 1916 treaty transferring sovereignty of the Danish West Indies from Denmark to the United States in exchange for a sum of US$25,000,000 in gold ($722 million in 2024) and a declaration from the United States that it would "not object to the Danish Government extending their political and economic interests to the whole of Greenland". It is one of the most recent permanent expansions of United States territory. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:43, 2 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30097839 --> == Tech News: 2026-10 == <section begin="technews-2026-W10"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/10|Translations]] are available. '''Weekly highlight''' * Wikipedia 25 [[m:Special:MyLanguage/Wikipedia 25/Easter egg experiments|Birthday mode]] is now live on Betawi, Breton, Chinese, Czech, Dutch, English, French, Gorontalo, Indonesian, Italian, Luxembourgish, Madurese, Sicilian, Spanish, Thai, and Vietnamese Wikipedias! This limited-time campaign feature celebrates 25 years of Wikipedia with a birthday mascot, Baby Globe. When turned on, Baby Globe is shown on [[m:Special:MyLanguage/Wikipedia 25/Easter egg experiments/article configuration|~2,500 articles]], waiting to be discovered by readers. Communities can choose to turn Birthday mode on by getting consensus from their community and asking an admin to enable the feature and customize it via [[m:Special:MyLanguage/Wikipedia 25/Easter egg experiments#Community Configuration Demo|community configuration]] on the local wiki. '''Updates for editors''' * [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]], a new feature to re-use references with different details has been released to Swedish Wikipedia, Polish Wikipedia and [[:phab:T418209|a couple of other wikis]]. You can [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#test|try the feature]] on these projects or on testwiki and [https://en.wikipedia.beta.wmcloud.org/wiki/Sub-referencing betawiki]. Learnings from the first pilot wiki German Wikipedia have been [[:m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing/Learnings|published in a report]]. Reach out to the Wikimedia Deutschland team if you are [[:m:Talk:WMDE Technical Wishes/Sub-referencing#Pilot wikis|interested in becoming a pilot wiki]]. * [[mw:Special:MyLanguage/Help:Edit check#Paste check|Paste Check]] will become available at all Wikipedias this week. The feature prompts newcomers who are pasting text they are not likely to have written into VisualEditor to consider whether doing so risks a copyright violation. Paste Check [[mw:Special:MyLanguage/Edit check/Tags|tags]] all edits where it is shown for potential review. Local administrators can configure various aspects of the feature via [[{{#special:EditChecks}}]]. [[mw:Special:MyLanguage/Edit check/Paste Check#A/B Experiment|Research]] across 22 wikis found that Paste Check resulted in an 18% decrease in relative reverted-edits compared to the control group. Translators can [https://translatewiki.net/w/i.php?title=Special%3ATranslate&group=ext-visualeditor-ve-mw-editcheck&filter=&optional=1&action=translate help to localize] this and related features. * The [[mw:Special:MyLanguage/Readers/Reader Experience|Reader Experience team]] will be standardizing the user menu in the top right for all mobile users so that it is closer to the desktop experience. Currently this user menu is only visible to users with Advanced Mobile Controls (AMC) turned on. The only change is that a couple buttons previously in the left-side menu will move to the top right for users who do not have AMC turned on. This change is expected to go out March 9 and seeks to improve the user interface. [https://phabricator.wikimedia.org/T413912] * Starting in the week of March 2, the emails sent out when an email address was added, removed, or changed for an account will switch to a substantially nicer and clearer HTML email from the prior plaintext one. [https://phabricator.wikimedia.org/T410807] * Notifications are currently limited to 2,000 historic entries per user, and extend back to 2013 when the feature was released. This is going to be changed to only store Notifications from the last 5 years, but up to 10,000 of them. This will help with long-term infrastructure health and help to prevent more recent notifications from disappearing too soon. [https://phabricator.wikimedia.org/T383948] * The [[m:Special:GlobalWatchlist|Global Watchlist]] which lets you view your watchlists from multiple wikis on a single page continues to see improvements. The latest update improves label usage experience. The [[mw:Special:MyLanguage/Extension:GlobalWatchlist|extension]] now allows activating the [[mw:Special:MyLanguage/Manual:Language#Fallback languages|language fallback system]] for Wikidata items without labels in the viewed language, and showing those labels in the user’s preferred Wikidata language if no <code dir=ltr>uselang=</code> URL parameter is provided. [https://phabricator.wikimedia.org/T373686][https://phabricator.wikimedia.org/T416111] * The Wikipedia Android team has started a beta test of [[mw:Special:MyLanguage/Readers/Information Retrieval/Phase 1|hybrid search]] on Greek Wikipedia. Hybrid search capabilities can handle both semantic and keyword queries enabling readers to find what they’re looking for directly on Wikipedia more easily. * For security reasons, members of certain user groups are [[m:Special:MyLanguage/Mandatory two-factor authentication for users with some extended rights|required to have two-factor authentication]] (2FA) enabled. Currently, 2FA is required to use the group, but not to be a member of it. Given that this model still has some vulnerabilities, the situation will [[phab:T418580|gradually change in March]]. Members of these groups will be unable to disable last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the second half of March, users without 2FA will be removed from these groups. This applies to: CentralNotice administrators, checkusers, interface administrators, suppressors, Wikidata staff, Wikifunctions staff, WMF Office IT and WMF Trust & Safety. Nothing will change for other users. See the linked task for deployment schedule. [https://phabricator.wikimedia.org/T418580] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue preventing users from creating an instance in [https://www.wikibase.cloud/ Wikibase.cloud] has now been fixed. [https://phabricator.wikimedia.org/T416807] '''Updates for technical contributors''' * To help ensure [[mw:Special:MyLanguage/MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]], over the next month the Wikimedia Foundation will implement global API rate limits across our APIs. In early March, stricter limits will be applied to unidentified requests from outside Toolforge/WMCS and API requests that are made from web browsers. In April, higher limits will be applied to identified traffic. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]]. * The Wikidata Query Service Linked Data Fragment (LDF) endpoint will be decommissioned in February. This endpoint served limited traffic, which was successfully migrated to other data access methods that were better suited to support existing use cases. The hardware used to support the LDF endpoint will be reallocated to support the ongoing backend migration efforts. [https://phabricator.wikimedia.org/T415696] * The new Parsoid parser [[mw:Special:MyLanguage/Parsoid/Parser Unification/Updates|continues to be deployed to additional wikis]], improving platform sustainability and making it easier to introduce new reading and editing features. Parsoid is now the default parser on 488 WMF wikis (268 Wikipedias), now covering more than 10% of all Wikipedia page views. * The process and criteria for [[Special:MyLanguage/Wikimedia Enterprise#Access|requesting exceptional access]] to the high volume feed of the ''Wikimedia Enterprise'' APIs (at no cost for mission-aligned usecases), [[m:Talk:Wikimedia Enterprise#Exceptional access criteria|have now been published]]. This is to provide more thorough and clearer documentation for users. * [https://techblog.wikimedia.org/ Tech Blog], the blog dedicated to the Wikimedia technical community [https://techblog.wikimedia.org/2026/02/24/a-tech-blog-diff/ will be migrating] to [[diffblog:|Diff]], the community news and event blog. The migration should be complete in April 2026, after which new posts will be accepted for publishing. Readers will be able to access posts – old and new – on the landing page at https://diff.wikimedia.org/techblog. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.18|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/10|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W10"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 17:52, 2 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30137798 --> == Wikipedia translation of the week: 2026-11 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Steens Mountain]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Steens Mountain near Andrews, Oregon.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Steens Mountain''' is a large fault-block mountain in the northwest United States, located in Harney County, Oregon. Stretching some fifty miles (80 km) north to south, on its east side it rises from the Alvord Desert at an elevation of about 4,200 feet (1,280 m) to 9,738 feet (2,968 m) at the summit. Steens Mountain is not part of a mountain range but is properly a single mountain, the largest of Oregon's fault-block mountains. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 07:30, 9 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30097839 --> == Tech News: 2026-11 == <section begin="technews-2026-W11"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/11|Translations]] are available. '''Weekly highlight''' * [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on Wednesday, 25 March 2026 at [https://zonestamp.toolforge.org/1774450800 15:00 UTC]. This is for the datacenter server switchover backup tests, [[wikitech:Deployments/Yearly calendar|which happen twice a year]]. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies. * Last week, all wikis had 2 hours of read-only time, and extended unavailability for user-scripts and gadgets. This was due to a security incident which has since been resolved. Work is ongoing to prevent re-occurrences. For current information please see the [[m:Steward's noticeboard#Statement on Meta about today's user script security incident|post on the Stewards' noticeboard]] ([[m:Special:MyLanguage/Wikimedia Foundation/Product and Technology/Product Safety and Integrity/March 2026 User Script Incident|translations]]). '''Updates for editors''' * Users facing multiple blocks on mobile will now see the reasons for each block separately, instead of a generic message. This helps them understand why they are blocked and what steps they can take to resolve the issue. For example, users affected for using common VPNs (such as [[Special:MyLanguage/Apple iCloud Private Relay|iCloud Private Relay]]) will receive clearer guidance on what they need to do to start editing again. [https://phabricator.wikimedia.org/T357118] * Later this week, [[mw:Special:MyLanguage/VisualEditor/Suggestion Mode|Suggestion Mode]] will become available as a beta feature within the visual editor at all Wikipedias. This feature proactively suggests various types of actions that people can consider taking to improve Wikipedia articles, and learn about related guidelines. The feature is locally configurable, and can also be locally expanded with custom Suggestions. Current settings can be seen at [[Special:EditChecks]] and there are [[mw:Special:MyLanguage/Help:Suggestion mode#For administrators %E2%80%93 local customization|instructions for how administrators can customize]] the links to point to local guidelines. The feature is connected to [[mw:Special:MyLanguage/Help:Edit check|Edit check]] which suggests improvements while someone is writing new content. In the future, the Editing team plans to evaluate the feature's impact with newcomers through a controlled experiment. [https://phabricator.wikimedia.org/T404600] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where the cursor became misaligned during the use of CodeMirror’s syntax highlighting, which makes wikitext and code easier to read, has now been fixed. This problem specifically affected users who defined a font rule in a custom stylesheet while creating a new topic with DiscussionTools. [https://phabricator.wikimedia.org/T418793] '''Updates for technical contributors''' * API rate limiting update: To help ensure [[mw:Special:MyLanguage/MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]], global API rate limits will be applied this week to requests without a compliant User-Agent that originate from outside Toolforge/WMCS and to unauthenticated requests made from web browsers. Higher limits will be applied to identified traffic in April. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]]. * The new GraphQL API has been released. The API was developed as a flexible alternative to select features of the Wikidata Query Service (WDQS), to improve developer experience and foster adaptability, and efficient data access. Try it out and [[d:Wikidata:Wikibase GraphQL#Feedback and development|give feedback]]. You can also [https://greatquestion.co/wikimediadeutschland/GraphQLAPI/apply sign up for usability tests]. * The [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group|PTAC Unsupported Tools Working Group]] continued improvements to [[commons:Special:MyLanguage/Commons:Video2commons#|Video2Commons]] in February, with fixes addressing authentication errors, large-file handling, task queue visibility, and clearer upload behavior. Work is still ongoing in some areas, including changes related to deprecated server-side uploads. Read [[m:Special:MyLanguage/Product and Technology Advisory Council/Unsupported Tools Working Group#February 2026|this update]] to learn more. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.19|MediaWiki]] '''In depth''' * The Article Guidance team invites experienced Wikipedia editors from selected [[mw:Special:MyLanguage/Article guidance/Pilot wikis and collaborators#Collaborators|pilot wikis]] and interested contributors from other Wikipedias to fill out this questionnaire which is available in [https://docs.google.com/forms/d/e/1FAIpQLSfmLeVWnxmsCbPoI_UF2jyRcn73WRGWCVPHzerXb4Cz97X_Ag/viewform English], [https://docs.google.com/forms/d/e/1FAIpQLSd6rzr4XXQw8r4024fE3geTPFe13M_6w7Mitj-YJi0sOlWTAw/viewform?usp=header Arabic], [https://docs.google.com/forms/d/e/1FAIpQLSdok3-RfB18lcugYTUMGkpwmqG_8p760Wv4dCXitOXOszjUDw/viewform?usp=header Bengali], [https://docs.google.com/forms/d/e/1FAIpQLSfjTfYp4jEo0akA4B1e-Nfg3QZPCudUjhJzHzzDi6AHyAaMGA/viewform?usp=header Japanese], [https://docs.google.com/forms/d/e/1FAIpQLScteVoI29Aue4xc72dekk-6RYtvmMgQxzMI900UOawrFrSTWg/viewform?usp=header Portuguese], [https://docs.google.com/forms/d/e/1FAIpQLSetdxnYwL3ub2vqA7awCg5hJZPMIYcDPaiTe12rY9h0GYnVlw/viewform?usp=header Persian], and [https://docs.google.com/forms/d/e/1FAIpQLScNvfJF-Ot-4pzA4qAN771_0QDJ4Li19YcUsaTgSKW8Nc7U_Q/viewform?usp=header Turkish]. Your answers will help the team customize guidance for less experienced editors and help them learn community policies and practices while creating an article. Learn more [[mw:Special:MyLanguage/Article guidance|on the project page]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/11|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W11"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:53, 9 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30213008 --> == Wikipedia translation of the week: 2026-12 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Casque (anatomy)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Great hornbill (Buceros bicornis) Photograph by Shantanu Kuveskar.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''casque''' is an anatomical feature found in some species of birds, reptiles, and amphibians. In birds, it is an enlargement of the bones of the upper mandible or the skull, either on the front of the face, the top of the head, or both. The casque has been hypothesized to serve as a visual cue to a bird's sex, state of maturity, or social status; as reinforcement to the beak's structure; or as a resonance chamber, enhancing calls. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:43, 16 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30245038 --> == Tech News: 2026-12 == <section begin="technews-2026-W12"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/12|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]] beta feature, also known as [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror 6]], has been used for wikitext syntax highlighting since November 2024. It will be promoted out of beta by May 2026 in order to bring improvements and new [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Features|features]] to all editors who use the standard syntax highlighter. If you have any questions or concerns about promoting the feature out of beta, [[mw:Special:MyLanguage/Help talk:Extension:CodeMirror|please share]]. [https://phabricator.wikimedia.org/T259059] * Some changes to local user groups are performed by stewards on Meta-Wiki and logged there only. Now, interwiki rights changes will be logged both on Meta-Wiki and the wiki of the target user to make it easier to access a full record of user's rights changes on a local wiki. Past log entries for such changes will be backfilled in the coming weeks. [https://phabricator.wikimedia.org/T6055] * On wikis using [[m:Special:MyLanguage/Flagged Revisions|Flagged Revisions]], the number of pending changes shown on [[{{#Special:PendingChanges}}]] previously counted pages which were no longer pending review, because they have been removed from the system without being reviewed, e.g. due to being deleted, moved to a different namespace, or due to wiki configuration changes. The count will be correct now. On some wikis the number shown will be much smaller than before. There should be no change to the list of pages itself. [https://phabricator.wikimedia.org/T413016] * Wikifunctions composition language has been rewritten, resulting in a new version of the language. This change aims to increase service stability by reducing the orchestrator's memory consumption. This rewrite also enables substantial latency reduction, code simplification, and better abstractions, which will open the door to later feature additions. Read more about [[f:Special:MyLanguage/Wikifunctions:Status updates/2026-03-11|the changes]]. * Users can now sort search results alphabetically by page title. The update gives an additional option to finding pages more easily and quickly. Previously, results could be sorted by Edit date, Creation date, or Relevance. To use the new option, open 'Advanced Search' on the search results page and select 'Alphabetically' under 'Sorting Order'. [https://phabricator.wikimedia.org/T403775] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:28}} community-submitted {{PLURAL:28|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the bug that prevented UploadWizard on Wikimedia Commons from importing files from Flickr has now been fixed. [https://phabricator.wikimedia.org/T419263] '''Updates for technical contributors''' * A new special page, [[{{#special:LintTemplateErrors}}]], has been created to list transcluded pages that are flagged as containing lint errors to help users discover them easily. The list is sorted by the number of transclusions with errors. For example: [[{{#special:LintTemplateErrors}}/night-mode-unaware-background-color]]. [https://phabricator.wikimedia.org/T170874] * Users of the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]] beta feature have been using [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]] for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages, for some time now. Along with promoting CodeMirror 6 out of beta, the plan is to replace CodeEditor as the standard editor for these content models by May 2026. [[mw:Special:MyLanguage/Help talk:Extension:CodeMirror|Feedback or concerns are welcome]]. [https://phabricator.wikimedia.org/T419332] * The [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] JavaScript modules will soon be upgraded to CodeMirror 6. Leading up to the upgrade, loading the <code dir=ltr>ext.CodeMirror</code> or <code dir=ltr>ext.CodeMirror.lib</code> modules from gadgets and user scripts was deprecated in July 2025. The use of the <code dir=ltr>ext.CodeMirror.switch</code> hook was also deprecated in March 2025. Contributors can now make their scripts or gadgets compatible with CodeMirror 6. See the [[mw:Special:MyLanguage/Extension:CodeMirror#Gadgets and user scripts|migration guide]] for more information. [https://phabricator.wikimedia.org/T373720] * The MediaWiki Interfaces team is expanding coverage of REST API module definitions to include [[mw:Special:MyLanguage/API:REST API/Extensions|extension APIs]]. REST API modules are groups of related endpoints that can be independently managed and versioned. Modules now exist for [https://phabricator.wikimedia.org/T414470 GrowthExperiments] and [https://phabricator.wikimedia.org/T419053 Wikifunctions] APIs. As we migrate extension APIs to this structure, documentation will move out of the main MediaWiki OpenAPI spec and REST Sandbox view, and will instead be accessible via module-specific options in the dropdown on the [https://test.wikipedia.org/wiki/Special:RestSandbox REST Sandbox] (i.e., [[{{#Special:RestSandbox}}]], available on all wiki projects). * The [[mw:Special:MyLanguage/Extension:Scribunto|Scribunto]] extension provides different pieces of information about the wiki where the module is being used via the [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual|mw.site]] library. Starting last week, the library also provides a [[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#mw.site.wikiId|way]] of accessing the [[mw:Special:MyLanguage/Manual:Wiki ID|wiki ID]] that can be used to facilitate cross-wiki module maintenance. [https://phabricator.wikimedia.org/T146616] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.20|MediaWiki]] '''In depth''' * The [[m:Special:MyLanguage/Coolest Tool Award|2026 Coolest Tool Award]] celebrating outstanding community tools, is now open for nominations! Nominate your favorite tool using the [https://wikimediafoundation.limesurvey.net/435684?lang=en nomination survey] form by 23 March 2026. For more information on privacy and data handling, please see the [[foundation:Special:MyLanguage/Legal:Coolest_Tool_Award_2026_Survey_Privacy_Statement|survey privacy statement]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/12|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W12"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:36, 16 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30260505 --> == Wikipedia translation of the week: 2026-13 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Etruscan sculpture]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Frontone A del grande tempio di luni con concilio degli dei, 175-150 ac. ca. 01.JPG|300px|center]] <div style="text-align:left; padding: .4em;"> '''Etruscan sculpture''' was one of the most important artistic expressions of the Etruscan people, who inhabited the regions of Northern Italy and Central Italy between about the 9th century BC and the 1st century BC. Etruscan art was largely a derivation of Greek art, although developed with many characteristics of its own. Given the almost total lack of Etruscan written documents, a problem compounded by the paucity of information on their language—still largely undeciphered—it is in their art that the keys to the reconstruction of their history are to be found, although Greek and Roman chronicles are also of great help. Like its culture in general, Etruscan sculpture has many obscure aspects for scholars, being the subject of controversy and forcing them to propose their interpretations always tentatively, but the consensus is that it was part of the most important and original legacy of Italian art and even contributed significantly to the initial formation of the artistic traditions of ancient Rome. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:07, 23 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30245038 --> == Tech News: 2026-13 == <section begin="technews-2026-W13"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/13|Translations]] are available. '''Weekly highlight''' * Wikimedia site users can now log in without a password using passkeys. This is a secure method supported by fingerprint, facial recognition, or PIN. With this change, all users who opt for passwordless login will find it easier, faster, and more secure to log in to their accounts using any device. The new passkey login option currently appears as an autofill suggestion in the username field. An additional [[phab:T417120|"Log in with passkey" button]] will soon be available for users who have already registered a passkey. This update will improve security and user experience. The [[c:File:Passwordless_login_screencast.webm|screen recording]] demonstrates the passwordless login process step by step. * [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on Wednesday, 25 March 2026 at [https://zonestamp.toolforge.org/1774450800 15:00 UTC]. This is for the datacenter server switchover backup tests, [[wikitech:Deployments/Yearly calendar|which happen twice a year]]. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies. '''Updates for editors''' * Wikimedia site users can now export their notifications older than 5 years using a [[toolforge:echo-chamber|new Toolforge tool]]. This will ensure that users retain their important notifications and avoid them being lost based on the planned change to delete notifications older than 5 years, as previously announced. [https://phabricator.wikimedia.org/T383948] * Wikipedia editors in Indonesian, Thai, Turkish, and Simple English now have access to Special:PersonalDashboard. This is an [[mw:Special:MyLanguage/Moderator Tools/Dashboard|early version of an experience]] that introduces newer editors to patrolling workflows, making it easier for them to move from making edits to participating in more advanced moderation work on their project. [https://phabricator.wikimedia.org/T402647] * The [[Special:Block]] now has two minor interface changes. Administrators can now easily perform indefinite blocks through a dedicated radio button in the expiry section. Also, choosing an indefinite expiry provides a different set of common reasons to select from, which can be changed at: [[MediaWiki:Ipbreason-indef-dropdown]]. [https://phabricator.wikimedia.org/T401823] * Mobile editors [[mw:Special:MyLanguage/Contributors/Account Creation Experiments#Logged-out|at several wikis]] can now see an improved logged-out edit warning, thanks to the recent updates from the Growth team. These changes released last week are part of ongoing efforts and tests to enhance [[mw:Special:MyLanguage/Contributors/Account Creation Experiments|account creation experience on mobile]] and then increase participation. [https://phabricator.wikimedia.org/T408484] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:36}} community-submitted {{PLURAL:36|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the bug that prevented mobile web users from seeing the block information when affected by multiple blocks has been fixed. They can now see messages of all the blocks currently affecting them when they access Wikipedia. '''Updates for technical contributors''' * Images built using Toolforge will soon get the upgraded buildpacks version, bringing support for newer language versions and other upstream improvements and fixes. If you use Toolforge Build Service, review the recent [https://lists.wikimedia.org/hyperkitty/list/cloud-announce@lists.wikimedia.org/thread/EMYTA32EV2V5SQ2JIEOD2CL66YFIZEKV/ cloud-announce email] and update your build configuration as necessary to ensure your tools are compatible. [https://wikitech.wikimedia.org/w/index.php?title=Help:Toolforge/Building_container_images&oldid=2392097#Buildpack_environment_upgrade_process][https://phabricator.wikimedia.org/T380127] * The [https://api.wikimedia.org/wiki/Main_Page API Portal] documentation wiki will shut down in June 2026. API keys created on the API Portal will continue to work normally. api.wikimedia.org endpoints will be deprecated gradually starting in July 2026. Documentation on the API Portal is moving to [[mw:Wikimedia APIs|mediawiki.org]]. Learn more on the [[wikitech:API Portal/Deprecation|project page]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.21|MediaWiki]] '''In depth''' * [[m:Special:MyLanguage/WMDE Technical Wishes|WMDE Technical Wishes]] is considering improvements to [[m:WMDE Technical Wishes/References/VisualEditor automatic reference names|automatically generated reference names in VisualEditor]]. Please check out the [[m:WMDE Technical Wishes/References/VisualEditor automatic reference names#Proposed solutions|proposed solutions]] and participate in the [[m:Talk:WMDE Technical Wishes/References/VisualEditor automatic reference names#Request for comment|request for comment]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/13|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W13"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:51, 23 March 2026 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30268305 --> == Wikipedia translation of the week: 2026-14 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Pulse (nightclub)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Orlando FL Pulse Nightclub01.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Pulse''' was a gay bar, dance club, and nightclub in Orlando, Florida, founded in 2004 by Barbara Poma and Ron Legler. On June 12, 2016, the club was the scene of the second-deadliest mass shooting by a single gunman in U.S. history, and the second-deadliest terrorist attack on U.S. soil since the September 11 attacks. Forty-nine people were killed and 58 other people were injured. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:37, 30 March 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30306870 --> == Tech News: 2026-14 == <section begin="technews-2026-W14"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/14|Translations]] are available. '''Weekly highlight''' * The Beta version of [[abstract:|Abstract Wikipedia]] a new Wikimedia project which is language-independent, was launched last week. The project allows communities to build Wikipedia articles in their native language, which can be readily accessed by other users in their own languages. The wiki is powered by instructions from Wikifunctions and also based on structured content from Wikidata. [[:f:Special:MyLanguage/Wikifunctions:Status updates/2026-03-26|Read more]]. '''Updates for editors''' * The Growth team is running an A/B test to evaluate a clearer, more user-friendly message that promotes account creation on wikis. Currently when logged-out mobile users begin editing, they see a jarring warning message that can feel abrupt and discouraging. This also presents temporary account editing as the default rather than encouraging account creation. The test is running on ten Wikipedias, including Arabic, French, Spanish and German. [[mw:Special:MyLanguage/Contributors/Account Creation Experiments#2. Improve logged-out warning message (T415160)|Read more]]. * The Wikimedia Apps team is inviting feedback on [[mw:Special:MyLanguage/Wikimedia Apps/Team/Future of Editing on the Mobile Apps|how editing should work on the Wikipedia mobile apps]]. The discussion focuses on improving how users access editing tools when they tap "Edit". This is part of a broader effort to convert readers who develop an interest in editing, to access a more user-friendly pathway to start contributing. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:45}} community-submitted {{PLURAL:45|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where citation fetching from the large newspaper archive [https://www.newspapers.com Newspapers.com] was no longer working, due to a block in [[mw:Special:MyLanguage/Citoid|Citoid]] requests, has now been fixed. [https://phabricator.wikimedia.org/T419903] '''Updates for technical contributors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.22|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/14|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W14"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:26, 30 March 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30329462 --> == Wikipedia translation of the week: 2026-15 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Tofana di Rozes]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Tofana di Rozes 04.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Tofana di Rozes''' (3,225 metres (10,581 ft)) is a mountain of the Dolomites in the Province of Belluno, Veneto, Italy. Located west of the resort of Cortina d'Ampezzo, the mountain's giant three-edged pyramid shape and its vertical south face, above the Falzarego Pass, makes it the most popular peak in the Tofane group, and one of the most popular in the Dolomites. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:27, 6 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30306870 --> == Tech News: 2026-15 == <section begin="technews-2026-W15"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/15|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents|CampaignEvents extension]] now includes a new group goal-setting feature, enabling organizers to set and track event goals such as the number of articles created and participating contributors in real time. Similarly, participants can work toward shared targets and see their collective impact as the event unfolds. The feature is now available on all Wikimedia wikis. Learn more in [[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Registration/Collaborative contributions#Goal setting|the documentation]]. * [[File:Maki-gift-15.svg|12px|link=|class=skin-invert|Wishlist item]] The new [[mw:Special:MyLanguage/Help:Watchlist labels|watchlist labels]] feature (announced in [[m:Special:MyLanguage/Tech/News/2026/07|Tech News 2026-07]]) is now available via VisualEditor, the source editor, and the 'watchstar' (or watch link, for skins that don't have a star icon). Previously it was only possible to assign labels via [[Special:EditWatchlist|EditWatchlist]]. In all three places it is a new field following the expiry field. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where talk pages on mobile with Parsoid are unusable after empty section headers, has now been fixed. [https://phabricator.wikimedia.org/T419171] '''Updates for technical contributors''' * The [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|sub-referencing feature]], which lets editors add details to an existing reference without duplicating it, will be gradually rolled out to [[phab:T414094|more wikis]] later this year. Wikis using the [[mw:Special:MyLanguage/Reference Tooltips|Reference Tooltips]] gadget are encouraged to update their version (typically at [[m:MediaWiki:Gadget-ReferenceTooltips.js|MediaWiki:Gadget-ReferenceTooltips.js]] as shown [https://en.wikipedia.org/w/index.php?diff=1344408362 here]) to ensure compatibility. Other reference-related gadgets may also be affected. [https://phabricator.wikimedia.org/T416304] * All Wikinews editions will be closed and switched to read-only mode on 4 May 2026. Content will remain accessible, but no new edits or articles can be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions. [[m:Wikimedia Foundation Board noticeboard#Board of Trustees Approves Closure of Wikinews|Read more]]. * The [[:mw:Special:MyLanguage/API:Action API|Action API]] has had several formats for requested output. One of them, <bdi lang="zxx" dir="ltr"><code><nowiki>format=php</nowiki></code></bdi>, is being removed soon. Please ensure your scripts or bots use the [[mw:Special:MyLanguage/API:Data formats#Output|JSON format]]. This removal should affect very few scripts and bots. [https://phabricator.wikimedia.org/T118538] * The [[Special:NamespaceInfo|Special:NamespaceInfo]] page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia. [https://phabricator.wikimedia.org/T381455] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.23|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/15|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W15"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:19, 6 April 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30362761 --> == Wikipedia translation of the week: 2026-16 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Very-low-calorie diet]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Green smoothie (8222465502).jpg|300px|center]] <div style="text-align:left; padding: .4em;"> A '''very-low-calorie diet''' (VLCD), also known as semistarvation diet and crash diet, is a type of diet with very or extremely low daily food energy consumption. VLCDs are defined as a diet of 800 kilocalories (3,300 kJ) per day or less. Modern medically supervised VLCDs use total meal replacements, with regulated formulations in Europe and Canada which contain the recommended daily requirements for vitamins, minerals, trace elements, fatty acids, protein and electrolyte balance. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:56, 13 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30306870 --> == Tech News: 2026-16 == <section begin="technews-2026-W16"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/16|Translations]] are available. '''Weekly highlight''' * Experienced editors are invited to [https://b24e11a4f1.catalyst.wmcloud.org/wiki/Main_Page test] the [[mw:Special:MyLanguage/Article guidance|Article guidance]] feature, designed to help less-experienced editors create well-structured, policy-compliant Wikipedia articles. Testing instructions are [[mw:Special:MyLanguage/Article guidance/Test feature guide|available]]. Also, after reviewing [https://b24e11a4f1.catalyst.wmcloud.org/wiki/Category:Pages_using_article_guidance the outlines], please provide feedback on the [[mw:Talk:Article guidance|project talk page]]. Based on your input, the feature will be refined and transferred to the pilot Wikipedias to translate and adapt. Check out [[c:File:Article Guidance workflow demo - April 2026.webm|the video]] explaining the feature. '''Updates for editors''' * On most wikis, all autoconfirmed users can now use [[Special:ChangeContentModel|Special:ChangeContentModel]] page to [[mw:Special:MyLanguage/Help:ChangeContentModel|create new pages with custom content models]], such as mass message lists, making custom page formats more accessible. Check [[Special:ListGroupRights|Special:ListGroupRights]] for the status of your wiki. [https://phabricator.wikimedia.org/T248294] * The Growth team has launched an [[mw:Special:MyLanguage/Contributors/Account_Creation_Experiments|account creation experiment]] to evaluate whether adding an account creation button to the mobile web header increases new account registrations and encourages more mobile users to contribute to the wikis. The experiment is currently live on Hindi, Indonesian, Bengali, Thai, and Hebrew Wikipedia, and targets 10% of logged-out mobile web users. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where VisualEditor could get stuck loading on Windows devices with animations turned off, has now been fixed. [https://phabricator.wikimedia.org/T382856] '''Updates for technical contributors''' * Starting later this week, {{int:group-abusefilter}} who have the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]] beta feature enabled will have [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]] as the editor at [[Special:AbuseFilter|Special:AbuseFilter]]. This is part of the broader effort to make the user experience more consistent across all editors. [https://phabricator.wikimedia.org/T399673][https://phabricator.wikimedia.org/T419332] * Tools and bots that access the [[mw:Special:MyLanguage/Notifications/API|Notifications API]] (<bdi lang="zxx" dir="ltr"><code><nowiki>action=query&meta=notifications</nowiki></code></bdi>) will need to update their OAuth or BotPassword grants to also include access to private notifications. [https://phabricator.wikimedia.org/T421991] * Due to a library upgrade, listings on category pages may be displayed out of order starting on Monday, 20th April. A migration script will be run to correct this, and will take hours to days depending on the size of the wiki (up to a week for English Wikipedia). [https://phabricator.wikimedia.org/T422544] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.24|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/16|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W16"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:19, 13 April 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30380527 --> == Wikipedia translation of the week: 2026-17 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Chromodoris willani]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Babosa de mar (Chromodoris willani), Anilao, Filipinas, 2023-08-24, DD 34.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''''Chromodoris willani''''', commonly known as Willan's chromodoris, is a species of sea slug, a dorid nudibranch, a shell-less marine gastropod mollusk in the family Chromodorididae. The species is named for the renowned nudibranch taxonomist Dr. Richard C. Willan. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:34, 20 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30430366 --> == Tech News: 2026-17 == <section begin="technews-2026-W17"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/17|Translations]] are available. '''Weekly highlight''' * After two years of development, [[mw:Special:MyLanguage/Help:Extension:CodeMirror|{{int:codemirror-beta-feature-title}}]], also known as [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror 6]], is to be promoted out of beta on Tuesday, April 21. It brings better code and wikitext readability, reduction in typing errors, and other [[mw:Special:MyLanguage/Help:Extension:CodeMirror|benefits]] to all users of the standard syntax highlighter. A huge thank you to volunteer [https://phabricator.wikimedia.org/p/Bhsd/ Bhsd] who developed many of the new features, including [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Code folding|code folding]], [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Autocompletion|autocompletion]], and [[mw:Special:MyLanguage/Help:Extension:CodeMirror#Linting|linting]]. [https://phabricator.wikimedia.org/T259059] * A major update to the Wikipedia app for iOS is now rolling out, redesigning the interface to align with Apple's latest "Liquid Glass" visual design. [https://apps.apple.com/us/app/wikipedia/id324715238 Download the latest version] and explore the update. '''Updates for editors''' * [[mw:Special:MyLanguage/Readers/Reader Experience/WE3.3.4 Reading lists|Reading lists]] is a feature which allows readers to save articles to a list for reading later. This feature is now in beta on Arabic, French, Indonesian, Vietnamese, and Chinese Wikipedias and by default for all new accounts on all Wikipedias. * An experiment which explores extending [[mw:Special:MyLanguage/Readers/Reader Growth/Mobile page previews|Page Previews to mobile web]] will be launched in the week of April 20 on Arabic, English, French, Italian, Polish, and Vietnamese Wikipedias. Page Previews are pop-ups that display a thumbnail, lead paragraph, and a link to open the full article of a blue link, thereby improving content discovery. The feature is already available on desktop and in the apps. [[m:Special:MyLanguage/List of experiments in Product and Technology#Template|Read more about this experiment and others]]. * On several wikis, logged-in editors who haven't [[mw:Special:MyLanguage/Help:Email confirmation|confirmed their email addresses]] can now see a banner encouraging them to do so. Having the email address confirmed allows a user to restore access to the account if they lose it. [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security#Encouraging users to confirm their email addresses|Learn more]]. [https://phabricator.wikimedia.org/T421366] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:15}} community-submitted {{PLURAL:15|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where editing very large wiki pages in the 2017 wikitext editor caused slow loading, preview and scrolling lag, and performance issues when selecting, cutting, or pasting content, has now been fixed. [https://phabricator.wikimedia.org/T184857] '''Updates for technical contributors''' * As part of the promotion of [[mw:Special:MyLanguage/Help:Extension:CodeMirror|CodeMirror]] from a beta feature, all users will use [[mw:Special:MyLanguage/Extension:CodeMirror|CodeMirror]] instead of [[mw:Special:MyLanguage/Extension:CodeEditor|CodeEditor]] for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages. [https://phabricator.wikimedia.org/T419332] * The <code>mirrors.wikimedia.org</code> service for Debian and Ubuntu users will sunset and stop working on May 15. The resources for the service will be replaced with new and better options. Some users may need to switch to a different server which should take about a minute. [https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/LJYRIS4WB66HIRCAO4GIDTXCMDVZRBMA/ You can read more]. [https://phabricator.wikimedia.org/T416707] * The <bdi lang="zxx" dir="ltr"><code><nowiki>image</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>oldimage</nowiki></code></bdi> table will be removed from [[wikitech:Help:Wiki Replicas|wikireplicas]]. If your tools or queries access <bdi lang="zxx" dir="ltr"><code><nowiki>image</nowiki></code></bdi> or <bdi lang="zxx" dir="ltr"><code><nowiki>oldimage</nowiki></code></bdi> directly, please update them to use the <bdi lang="zxx" dir="ltr"><code><nowiki>file</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>filerevision</nowiki></code></bdi> table before 28 May. [https://phabricator.wikimedia.org/T28741] * Following the recent implementation of global API rate limits on unidentified traffic, the Wikimedia Foundation will continue efforts to ensure [[mw:Special:MyLanguage/MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]] by applying global limits to identified API traffic beginning the last week of April. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]] and [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits/FAQ|Frequently Asked Questions]]. * The [[mw:Special:MyLanguage/Attribution API|Attribution API]] is now available as a [[mw:Special:MyLanguage/Wikimedia APIs/Stability policy|beta]]. The API fetches information for crediting Wikimedia articles and media files wherever they are used. Reference documentation is available through the REST Sandbox special page available on all Wikimedia wikis (such as the [https://en.wikipedia.org/w/index.php?api=attribution.v0-beta&title=Special%3ARestSandbox REST sandbox on English Wikipedia]). Share your feedback on the [[mw:Talk:Attribution API|project talk page]]. * There is no new MediaWiki version this week. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/17|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W17"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:01, 20 April 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30432763 --> == Wikipedia translation of the week: 2026-18 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Platypus venom]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Platypus spur.JPG|300px|center]] <div style="text-align:left; padding: .4em;"> The platypus is one of the few living mammals to produce venom. The venom is made in venom glands that are connected to hollow spurs on their hind legs; it is primarily made during the mating season.[1] While the venom's effects are described as extremely painful, it is not lethal to humans. Many archaic mammal groups possess similar tarsal spurs, so it is thought that, rather than having developed this characteristic uniquely, the platypus simply inherited this characteristic from its ancestors. Rather than being a unique outlier, the platypus is the last demonstration of what was once a common mammalian characteristic, and it can be used as a model for non-therian mammals and their venom delivery and properties. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:04, 27 April 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30449041 --> == Tech News: 2026-18 == <section begin="technews-2026-W18"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/18|Translations]] are available. '''Updates for editors''' * There is a change in how new users are autoconfirmed that will improve anti-vandalism protection. Currently, users who have had an account for a few days and made a few edits are automatically added to the [[{{int:grouppage-autoconfirmed/{{CONTENTLANGUAGE}}}}|{{int:group-autoconfirmed}}]] group. This configuration tends to be exploited by some vandals, who create accounts and start to use them only after some time. To mitigate this, the configuration will be updated next week so that – for the purpose of becoming autoconfirmed – the account age will be counted from their first edit, instead of registration date. The numeric value of the age threshold will remain the same. This change will be deployed only to wikis which require at least one edit as part of the autoconfirmation conditions. [https://phabricator.wikimedia.org/T418484] * All Wikipedia users with new accounts and those who activated the "automatically enable most beta features" option in their preference can now use the [[mw:Special:MyLanguage/Readers/Reader Experience/WE3.3.4 Reading lists|reading lists]] beta feature to save articles for later reading. This helps organize reading interests in one place for convenient access. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where infobox images have huge padding in Firefox, has been fixed. [https://phabricator.wikimedia.org/T423676] '''Updates for technical contributors''' * As a reminder, the global API rate limits will be applied this week to identified API traffic. This is to help ensure [[mw:MediaWiki Product Insights/Responsible Reuse|fair use of infrastructure]]. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, including the actual rate limits, see [[mw:Wikimedia APIs/Rate limits|Wikimedia APIs/Rate limits]] and [[mw:Wikimedia APIs/Rate limits/FAQ|Frequently Asked Questions]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.26|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/18|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W18"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:06, 27 April 2026 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30458046 --> == Wikipedia translation of the week: 2026-19 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Kuwait National Assembly Building]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Kuwait City Arabian Gulf Street 10.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Kuwait National Assembly Building''' is the building that housed the National Assembly of Kuwait. Designed by Danish architect Jørn Utzon in 1972, it was completed in 1982 under the direction of his son Jan. The structural design was by Max Walt. The building was seriously damaged in February 1991 when retreating Iraqi troops set it on fire but has since been restored. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:16, 4 May 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30464799 --> == Tech News: 2026-19 == <section begin="technews-2026-W19"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/19|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Article guidance|Article guidance]] team invites experienced editors of [[mw:Special:MyLanguage/Article guidance/Pilot wikis and collaborators|pilot Wikipedias]]—Arabic, Bangla, Japanese, Portuguese, Persian, Turkish, Simple English, Spanish, and French—to help translate and adapt [https://b24e11a4f1.catalyst.wmcloud.org/wiki/Category:Pages_using_article_guidance sample outlines]. These outlines will guide editors in creating clear, well-structured, and policy-compliant articles when using [https://b24e11a4f1.catalyst.wmcloud.org/wiki/Special:NewArticle the feature] once it is launched in May 2026. [[mw:Special:MyLanguage/Article guidance#Adapting a sample outline in a Wikipedia|Simple instructions]] on how to translate and adapt the outlines are available. '''Updates for editors''' * The [[:m:Special:MyLanguage/Product and Technology Advisory Council|Product and Technology Advisory Council]] has published [[:m:Special:MyLanguage/Product and Technology Advisory Council/May 2026 draft PTAC recommendation for feedback|draft recommendations]] on a model that affiliates can follow when contributing to the technical space. Community members are invited to provide feedback on the recommendation until May 8th [[:m:Talk:Product and Technology Advisory Council/May 2026 draft PTAC recommendation for feedback|on the talk page]]. * The number of available thumbnail size preferences in MediaWiki is being reduced to three standardized options—Small (180px), Regular (250px), and Large (400px), as part of ongoing efforts to improve performance and reduce strain on thumbnail services. As a result, existing preferences will be mapped to the nearest new size (for example, smaller selections like 120px or 150px will render at 180px, while larger ones like 300px or 360px will render at 400px). The preferences interface will soon be updated to reflect these changes, and users who wish to opt out or provide feedback can do so. [https://phabricator.wikimedia.org/T424909] * From now on, even when a permission expires automatically, users will receive an Echo notification similar to the standard notification for permission changes. There is a difference between this and [[m:Special:MyLanguage/Global reminder bot|Global reminder bot]] in that the latter reminds users a week ''before'' the rights are due to expire, so that they can renew the rights. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the problem where the ULS language selector in [[m:Special:Translate|Special:Translate]] would scroll vertically when it shouldn't, has been resolved. Previously, when users opened the "Translate to English" dropdown and typed certain inputs, the dialog would scroll vertically by a few pixels even when there was enough space to display all results. The dropdown no longer shifts unnecessarily when filtering languages. [https://phabricator.wikimedia.org/T358864] * The [[m:Special:GlobalWatchlist|Global Watchlist]], which lets you view your watchlists from multiple wikis on a single page, continues to improve. For example, watchlists for Wikibase sites such as [[:d:|Wikidata]] now support [[mw:Special:MyLanguage/Extension:EntitySchema|EntitySchema]] elements for better tracking. The Live Updates mode now refreshes the special page every 60 seconds to comply with the updated [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|global API rate limits]] for improved real-time responsiveness. Additionally, a directionality bug that displayed links as "changes 3" instead of "3 changes" in mixed-direction lists has been fixed. [https://phabricator.wikimedia.org/T415450][https://phabricator.wikimedia.org/T424422][https://phabricator.wikimedia.org/T418091] '''Updates for technical contributors''' * The second phase of [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits|global API rate limits]] has been rolled out to reduce the [[diffblog:2026/03/26/quo-vadis-crawlers-progress-and-whats-next-on-safeguarding-our-infrastructure/|impact of AI crawlers]] and ensure fair, sustainable access to Wikimedia resources, prioritising human and mission-aligned traffic. [[mw:Special:MyLanguage/Wikimedia APIs/Rate limits#Limits|Limits]] have been shifted from per-hour to per-minute, producing smoother traffic patterns and more predictable API load. Community users are not expected to be affected, and no action is required. Early indications show some User-Agent-based requestors are adjusting behaviour, and around 64% of automated API traffic has been identified. Monitoring continues, and Wikimedia Enterprise remains available for commercial support. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.46/wmf.27|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/19|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W19"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:44, 4 May 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30498077 --> == Wikipedia translation of the week: 2026-20 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Macau National Security Law]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Lei relative à defesa da segurança do Estado projecto.JPG|center|300px]] <div style="text-align:left; padding: .4em;"> The '''Macau National Security Law''' is a law in Macau which prohibits and punishes acts of treason, secession, and subversion against the Central government, as well as preparative acts leading to any of the three acts. Taken into effect on 3 March 2009, the purpose of the law is to fulfil Article 23 of the Macau Basic Law, the de facto constitution of the Macau Special Administration Region. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:53, 11 May 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30513945 --> == Tech News: 2026-20 == <section begin="technews-2026-W20"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/20|Translations]] are available. '''Weekly highlight''' * Community Tech has published [[m:Special:MyLanguage/Community Wishlist/How to write a good wish|new guidance]] explaining how wishes on Community Wishlist are triaged and prioritized. The documentation is intended to help contributors write stronger proposals by clarifying the factors that influence prioritization decisions. Beyond vote counts, the guidance highlights considerations such as potential impact on the community when determining which wishes move forward. '''Updates for editors''' * The Reader Growth team is launching an experiment to test a new [[mw:Special:MyLanguage/Readers/Reader_Growth/Share_Card|Share Card feature]] that allows readers to create visually engaging cards from Wikipedia articles or selected article sections and share them online, with each card linking back to the original article to help expand readership and article discovery. The mobile-only A/B test will be available to a portion of readers on Arabic, Chinese, French, Vietnamese, and English Wikipedia to better understand reading and sharing habits, and is scheduled to begin the week of May 18 and run for four weeks. * The Android and iOS Wikipedia apps recently released the [[mw:Special:MyLanguage/Wikimedia_Apps/Team/25th_Birthday_Reading_Challenge|25-day reading challenge]] into Beta, as part of efforts to drive reader engagement by encouraging users to complete reading milestones. To track their reading streak during the challenge, App users can add a widget featuring Baby Globe to their home screen. The challenge officially begins May 11. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:17}} community-submitted {{PLURAL:17|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where the global preference for enabling syntax highlighting in wikitext could unexpectedly disable itself after being turned on, has now been fixed. [https://phabricator.wikimedia.org/T425286] '''Updates for technical contributors''' * [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The ResourceLoader module <bdi lang="zxx" dir="ltr"><code><nowiki>mediawiki.ui.input</nowiki></code></bdi>, deprecated since [[m:Special:MyLanguage/Tech/News/2023/39|September 2023]], will be removed this week. There is a [[mw:Special:MyLanguage/Codex/Migrating_from_MediaWiki_UI|guide for migrating from MediaWiki UI to Codex]] for any tools that use it. [https://phabricator.wikimedia.org/T420125] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.2|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/20|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W20"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:21, 11 May 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30524429 --> == Tech News: 2026-21 == <section begin="technews-2026-W21"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/21|Translations]] are available. '''Weekly highlight''' * The Abstract Wikipedia team has identified five potential pilot wikis to assess their interest in adopting abstract articles on their wikis. The pilots are Malayalam, Bengali, Dagbani, Arabic, and Indonesian Wikipedia. The feedback period will be open until May 22. If your community is interested in becoming a pilot, [[m:Talk:Abstract Wikipedia|let us know on Meta]]. '''Updates for editors''' * An experiment to show [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|Reading Lists]] to logged-out readers on mobile web will launch on May 18 across German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu Wikipedias, and will run for one month. The effort supports broader goals of helping readers save and organize articles for later reading, while encouraging habits that could lead to future Wikipedia contributions. * To support a bookmark button in the Reading List beta feature, the "Tools > Action" menu has been updated to display icons, including the watch star indicator that helps editors identify temporarily watched articles. The icons now also match those used on mobile, improving consistency across platforms. The change is currently limited to the actions menu and mainly affects editors with privileged user rights. [https://phabricator.wikimedia.org/T426008] * [[mw:Special:MyLanguage/VisualEditor/Suggestion Mode|Suggestion Mode]] was released as an [[w:en:A/B test|A/B test]] for newcomer editors on the mobile website at [[phab:T421189|~15 Wikipedias]]. The experiment will measure the impact that Suggestion Mode has on the proportion of newcomer mobile web edit sessions that result in constructive (un-reverted) article edits. The experiment will also evaluate the feature's impact on editor retention, and monitor changes in revert and block rates. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue in the Wikipedia Android app where images could sometimes fail to load after opening a recommended reading list notification, has now been fixed. [https://phabricator.wikimedia.org/T418231] '''Updates for technical contributors''' * The [[mw:Special:MyLanguage/Wikidata Platform|Wikidata Platform team]] has published its [[d:Special:MyLanguage/Wikidata:SPARQL query service/WDQS backend update/Backend Replacement|backend replacement recommendation]] and accompanying [[wikitech:Wikidata Query Service/WDQS Architecture re-design|technical architecture]] for the migration of the Wikidata Query Service (WDQS) away from Blazegraph. Feedback is invited until May 25th 2026, especially on potential gaps and impacts on advanced use cases. Wikidata community members and WDQS users are also encouraged to help identify high-impact tools and workflows that may need attention on [[d:Wikidata:SPARQL query service/WDQS backend update/High-Impact Use Cases|this page]]. Feedback can be shared on the [[d:Wikidata talk:SPARQL query service/WDQS backend update|Migration talk page]] or during the [[d:Special:MyLanguage/Wikidata:Blazegraph Migration Office Hours|next office hour]]. See the [[d:Special:MyLanguage/Wikidata:Wikidata Platform team/Newsletter|WDP team newsletter]] for more details. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.3|MediaWiki]] '''In depth''' * On English, French, Japanese, and a few other Wikipedias, there was a [[diffblog:2025/09/02/better-detecting-bots-and-replacing-our-captcha/|trial of hCaptcha]], a third-party bot detection service. The trial showed that hCaptcha effectively detects and deters some bad-faith automated activity, on its own and by giving [[w:en:Wikipedia:Village pump (technical)/Archive 225#Introducing SuggestedInvestigations|checkusers and stewards]] signals to look into. Because the results were positive, hCaptcha will be rolled out across all wikis over the next few weeks. [[mw:Special:MyLanguage/Product Safety and Integrity/Anti-abuse signals/hCaptcha|See the hCaptcha project page]] for technical information about the implementation and privacy protections. [[diffblog:2026/05/04/better-detecting-bots-and-replacing-our-captcha-part-2/|Learn more]]. * The latest Community Tech update is now available, with progress across several Community Wishlist initiatives, including Reading Lists expansion from the mobile app to the website, new language support for "Who Wrote That" and the Personal Dashboard, improvements to 3D rendering and Charts, and upcoming work on talk page sorting, audio playback, and editing workflows. The update also shares current priorities, wishlist status trends, and opportunities for community feedback on future focus areas and the Wikimedia Foundation’s 2026–2027 Annual Plan. [[m:Special:MyLanguage/Community Wishlist/Updates#May 13, 2026: Latest updates from the Community Tech team|Read the full newsletter for details]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/21|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W21"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:22, 18 May 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30539262 --> == Wikipedia translation of the week: 2026-21 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Stela of the cactus bearer]]'''<br /> <small>''([[:es:Estela del portador del cactus]])&#32;([[:ca:Estela del portador del cactus]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Estela Wachumero en Chavin.jpg|center|300px]] <div style="text-align:left; padding: .4em;"> The '''stela of the cactus bearer''' is a monolith or stele of a single piece of granite, belonging to the Chavín culture of ancient Peru, which remains in its original location on the northwest side of the circular plaza at the archaeological site known as the ceremonial center of Chavín de Huántar in the Ancash region of Peru. It was discovered during the 1972 excavation season by Peruvian archaeologist Luis Guillermo Lumbreras. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 04:05, 21 May 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30529698 --> == Wikipedia translation of the week: 2026-22 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Griffith Hughes]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The Reverend '''Griffith Hughes''' (1707 – c.1758), FRS, was a Welsh naturalist, clergyman, and author. Hughes wrote The Natural History of Barbados, which included the first description of the grapefruit (also known as "The Forbidden Fruit"). His work was praised by Linnaeus, but it has also been considered a "scientific fraud". <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:32, 25 May 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30529698 --> == Tech News: 2026-22 == <section begin="technews-2026-W22"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/22|Translations]] are available. '''Weekly highlight''' * Following a [[mw:Special:MyLanguage/Contributors/Account Creation Experiments#LOWM|successful account creation experiment]], an improved logged-out edit warning message will be deployed to all Wikimedia wikis in the first week of June. The change will only affect logged-out users on mobile web who open an editing session. The updated experience is designed to encourage account creation more clearly, while still allowing users to edit with temporary accounts. Results from the experiment showed a significant increase in account creation, with a 27% relative lift among users shown the updated message. As expected, as more people funnel into account creation, temporary accounts decreased by a relative 16%. The experiment did not show any significant changes in constructive edit rates or other monitored contributor metrics. [https://phabricator.wikimedia.org/T424595] '''Updates for editors''' * For security reasons, members of certain user groups are [[m:Special:MyLanguage/Mandatory two-factor authentication for users with some extended rights|required to have two-factor authentication]] (2FA) enabled. Members of these groups will be unable to disable the last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the next few weeks, users without 2FA will be removed from these groups. Notably, this applies to bureaucrats. See the linked tasks for deployment schedules. [https://phabricator.wikimedia.org/T423119][https://phabricator.wikimedia.org/T423120] * [[m:Special:MyLanguage/WMDE Technical Wishes|WMDE Technical Wishes]] will run an [[w:en:A/B testing|A/B test]] on [[:phab:T415904|10 wikis]], testing [[m:WMDE Technical Wishes/References/Reference Previews|potential improvements for Reference Previews]]. The experiment will run for ~2 weeks at the end of May / beginning of June and will affect 10% of desktop readers on the participating wikis. * After two successful experiments, the Reader Growth team is rolling out an [[mw:Special:MyLanguage/Readers/Reader Growth/Image Browsing|Image Browsing]] beta feature for all Wikipedias on mobile on May 25. This means that anyone who has all beta features on by default will start to see this feature, and others can check the box to turn it on in their preferences. The beta feature will include a carousel of all an article's images at the top of the article, with controls for editors to [[mw:Readers/Reader_Growth/Image_Browsing#Phase_2.1_beta_feature|exclude images from the article's carousel or to exclude an article from the feature entirely]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, three dimensional STL files were being rendered incorrectly by the media viewer 3D extension which is now fixed. [https://phabricator.wikimedia.org/T416723] '''Updates for technical contributors''' * The legacy CSS classes <bdi lang="zxx" dir="ltr"><code><nowiki>tleft</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>tright</nowiki></code></bdi> have been replaced with <bdi lang="zxx" dir="ltr"><code><nowiki>floatleft</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>floatright</nowiki></code></bdi> as the former do not work consistently across all MediaWiki platforms, notably mobile web and mobile apps. Projects relying on these classes are encouraged to review related usage and plan for migration. Please note that <bdi lang="zxx" dir="ltr"><code><nowiki>floatleft</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>floatright</nowiki></code></bdi> may also be deprecated in future, although there are currently no plans to do so. [[phab:T426452|Read more]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.4|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/22|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W22"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:52, 25 May 2026 (UTC) <!-- Message sent by User:Quiddity (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30584502 --> == Wikipedia translation of the week: 2026-23 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Umuganda]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Umuganda"Rwandan community work".jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Umuganda''' is a national holiday in Rwanda taking place on the last Saturday of every month for mandatory nationwide community service from 08:00 to 11:00. Participation in Umuganda is required by law; failure to participate can result in a fine. The program was most recently re-established under President Paul Kagame in 2009, having resulted in a notable improvement in the cleanliness of Rwanda. Also, there are other informal Umuganda day activities that occur in the middle of the month. These activities are initiated by either society or the government. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:55, 1 June 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30529698 --> == Tech News: 2026-23 == <section begin="technews-2026-W23"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/23|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Readers/Reader Experience|Reader Experience team]] is conducting an experiment to show the [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|reading lists]] feature, which is still in development, to logged-out mobile readers to test whether it encourages account creation at a higher rate compared to the watchstar button. The [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists#Experiment timeline|experiment]] was launched on May 18th on German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu wikis, and it will run for a month. * The Wikimedia Apps team released [[mw:Special:MyLanguage/Wikimedia Apps/Team/Explore Feed Refresh/Phase 1|Phase 1]] of the redesigned Home Feed to the Android Beta app. The new Home Feed includes a refreshed "Community" tab and a personalized "For You" tab featuring daily updated reading recommendations. The redesign is part of a broader effort to improve content discovery and create more engaging learning experiences in the Wikipedia apps. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:18}} community-submitted {{PLURAL:18|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where images could fail to load for some suggested edits on [[w:Special:Homepage|Special:Homepage]], leaving the thumbnail stuck in a loading state, has now been fixed. [https://phabricator.wikimedia.org/T424048] '''Updates for technical contributors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.5|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/23|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W23"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:09, 1 June 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30613639 --> == Wikipedia translation of the week: 2026-24 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Juryeonggu]]'''<br /> <small>''([[:kr:주령구]])&#32;([[:ja:酒令具]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:주령구의 발굴 당시 사진.png|300px|center]] <div style="text-align:left; padding: .4em;"> Il '''Juryeonggu''' (주령구?, 酒令具?, JuryeongguLR, ChuryŏngguMR) è un dado a 14 facce, risalente al periodo del Silla unificato (668-935 d.C.), ritrovato nel 1975 dopo alcuni scavi occorsi presso il Donggung e lo stagno Wolji di Gyeongju, in Corea del Sud. Le facce del dado mostravano inscrizioni recanti varie penalità o sfide, legate ad un gioco di bevute, dimostrando l'importanza dell'alcool e la raffinatezza con cui la sua assunzione veniva celebrata. L'artefatto originale è andato perduto, incendiato in un maldestro tentativo di preservazione: oggi ne esistono delle repliche, disponibili anche commercialmente. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:20, 8 June 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30622359 --> == Tech News: 2026-24 == <section begin="technews-2026-W24"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/24|Translations]] are available. '''Weekly highlight''' * Wikimedia Enterprise has increased the free usage limits for its API offerings. The monthly request limit for the On-demand API has increased from 5,000 to 50,000 requests, while the Snapshot API limit has increased from 15 to 30 requests per month. In addition, Structured Contents snapshots are now available for free accounts. These changes expand access to Wikimedia Enterprise data for developers, researchers, and organizations using Wikimedia content. [https://enterprise.wikimedia.com/blog/enhanced-free-api] '''Updates for editors''' * The [[mw:Special:MyLanguage/Wikimedia_Apps/Team/Explore Feed Refresh/Phase 1|refreshed Explore Feed]], now called the Home Feed, is rolling out to 50% of users of the Wikipedia Android app. The Home Feed helps readers discover relevant content through two new tabs: ''Community'' and ''For You''. The Community tab provides a scrollable feed of curated content and updates from the broader Wikimedia community and movement, while the ''For You'' tab offers a full-screen, swipeable experience that shows content tailored to a user's interests. The redesign is part of a broader effort to improve discovery and enhance the learning experience in the Wikipedia app. * The [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/"Which came first?" Game|Which came first?]] daily trivia game is now available in the beta version of the Wikipedia iOS app in English, German, French, Portuguese, Russian, Spanish, Arabic, Chinese, and Turkish. The game uses historical events from Wikipedia's "On This Day" content and challenges readers to guess which of two events happened first. The game was previously released on Android. Communities interested in making the game available in their languages can [[mw:Special:MyLanguage/Wikimedia_Apps/Team/Games#Game availability by language|read the instructions and requirements]]. * [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]], a new MediaWiki feature that allows editors to reuse references with different details, will begin rolling out to Wikimedia wikis following a successful pilot phase. Deployment will start on 8 June for most [[wikitech:Deployments/Train#Wednesday|Group 1 wikis]] and French Wikipedia, with additional Wikipedia language editions receiving the feature over the coming months. Communities are encouraged to prepare by checking for [https://translatewiki.net/w/i.php?title=Special%3ATranslate&group=ext-cite&language=en&action_source=search&filter=%21translated&optional=1&action=translate untranslated Cite extension messages] in their language and reviewing any use of [[mw:Special:MyLanguage/Reference Tooltips|Reference Tooltips]], which may require [[:phab:T416304#11668731|updates]] to support the new functionality. Wikis using [[mw:Special:MyLanguage/Help:Reference Previews|Reference Previews]] do not need to take any action. Communities may also wish to create the ''cite-tracking-category-ref-details'' [[Special:TrackingCategories|tracking category]] as a hidden category using <code><nowiki>__HIDDENCAT__</nowiki></code> (or a dedicated template), and connect it to the corresponding Wikidata item [[d:Q129764848]]. [https://phabricator.wikimedia.org/T425662] * The [[mw:Special:MyLanguage/Readers/Reader Growth/Mobile page previews#Experimentation|Page Previews experiment]] on mobile web has concluded. The team decided not to roll out the feature after the results showed no statistically significant impact on reader retention, as the primary success metric was retention improvement. Page Previews, which are already available on desktop and in the apps, display a thumbnail, lead paragraph, and link to the full article when readers tap a blue link. The experiment tested this experience on mobile web across six Wikipedias. * The [[mw:Special:MyLanguage/Codex/Design/Icons|user interface icon library]] will be [[phab:T399175|updated later this week or next week]]. Most of the ~300 icons have been slightly refined and ~30 new icons have been added. These changes improve the icons to make them more consistent and comprehensible, and provide more visual balance when they are used in groups. * The [[mw:Special:MyLanguage/Universal Language Selector|Universal Language Selector]] (ULS) interface in MediaWiki, which helps users select content in other languages, has been updated. The new version improves speed and accessibility, and users of Wikimedia projects can now pin languages for quicker language switching. The deployment to Wikimedia sites will happen gradually in the coming weeks. You can test it now as a beta feature by selecting [[Special:Preferences#mw-prefsection-betafeatures|beta features]] in your profile preferences and share your feedback on [[mw:Special:MyLanguage/Universal Language Selector/New ULS|the project page]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:21}} community-submitted {{PLURAL:21|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where the Pageviews Analysis dashboard on pageviews.wmcloud.org stopped updating graph data in May 2026, affecting all users, has been fixed. [https://phabricator.wikimedia.org/T427171] '''Updates for technical contributors''' * The function signature for <bdi lang="zxx" dir="ltr"><code><nowiki>mw.util.addPortletLink()</nowiki></code></bdi> has been simplified. Developers can now pass a configuration object instead of a list of positional parameters when creating portlet links. The previous function signature remains supported for backwards compatibility. For example, instead of: <bdi lang="zxx" dir="ltr"><code><nowiki>mw.util.addPortletLink('p-cactions', '#', 'Stub', 'ca-stubtag', 'Add a stub tag to this page');</nowiki></code></bdi> use <bdi lang="zxx" dir="ltr"><code><nowiki>mw.util.addPortletLink('p-cactions', { href: '#', text: 'Stub', id: 'ca-stubtag', tooltip: 'Add a stub tag to this page' });</nowiki></code></bdi>. Script maintainers are encouraged to review existing uses of <bdi lang="zxx" dir="ltr"><code><nowiki>addPortletLink()</nowiki></code></bdi> and update them where appropriate. This change will be available on all wikis from 11 June. Thanks to community volunteer Gerges for contributing this improvement. [https://phabricator.wikimedia.org/T427945] * '''Community Wishlist discussion''': Product & Technology [[m:Special:MyLanguage/Community Wishlist/Updates#May 20, 2026: Community Tech becomes a program|introduced changes]] meant to increase the number and complexity of wishes fulfilled, including the disbanding of the Community Tech team. They are [[m:Special:MyLanguage/Community Wishlist/Updates|engaging in discussions]] about a [[m:Talk:Community Wishlist#Proposed direction for Wishlist|proposed direction for the wishlist]] from community members. Includes ways to structure annual voting, better tracking of wishes, removing focus areas, and [[m:Special:MyLanguage/Community Wishlist/Updates|staffing updates]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.6|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/24|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W24"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:30, 8 June 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30650573 --> == Wikipedia translation of the week: 2026-25 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Cape Fiolent]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Beach of Cape Fiolent, Crimea.jpg|300px|center]] <div style="text-align:left; padding: .4em;"> '''Cape Fiolent''' (Crimean Tatar: Felenk Burun; Ukrainian: Фіолент; Russian: Фиолент; Latin: Parthenium), also historically called Cape Fiolente, is a cape and nature reserve (zakaznik) located in southern Sevastopol, a city within Crimea that is internationally recognised as part of Ukraine but currently occupied by Russia since 2014. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:24, 15 June 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30662919 --> == Tech News: 2026-25 == <section begin="technews-2026-W25"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/25|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Readers/Reader Growth|Reader Growth team]] has launched an [[mw:Special:MyLanguage/Readers/Reader Growth/Image Browsing|Image Browsing]] beta feature on the mobile web version of all Wikipedias. The feature shows an image carousel at the top of articles with 3 or more images. Editors can configure this feature with the following controls: to hide a specific image from a page, either use <code>class=notpageimage</code> excluding it from thumbnail previews, or <code>class=noviewer</code> excluding it from MediaViewer. The carousel can also be disabled from a page entirely, with the magic word <code><nowiki>__NOMEDIAVIEWERCAROUSEL__</nowiki></code>. To submit feedback or flag bugs, please visit the [[mw:Talk:Readers/Reader Growth/Image Browsing|project page]]. * [[mw:Special:MyLanguage/Help:Tables#class="wikitable"|Wikitables]] can now be [[mw:Special:MyLanguage/Help:Sortable tables#Forcing the initial sort direction|sorted in descending order]] on the first click by adding <code dir=ltr>data-sort-order="desc"</code> to the header cell. Previously, by default, clicking a column header for the first time sorts it in ascending order. This addition to a Wikitable gives it more control and flexibility, while the default behavior for subsequent clicks remains unchanged. [https://phabricator.wikimedia.org/T398416] '''Updates for editors''' * The [[mw:Special:MyLanguage/Article guidance|Article guidance]] feature is currently being tested with some editors creating new articles on the Simple English, French, and Turkish Wikipedias. The experiment will soon begin on the Arabic and Bangla Wikipedias as well. [[w:simple:Special:NewArticle|This feature]] gives editors community-curated guidance to help them create articles that follow community standards. Experienced editors can continue creating or adapting outlines for specific article types that are commonly created by less experienced contributors. The outlines guide less experienced editors in creating high-quality articles. A quick guide to markups used in outlines can be found on [[mw:Special:MyLanguage/Article guidance/Test feature guide#Markups in outlines|this page]]. [[w:simple:Wikipedia:Article Guidance|Example outlines]] that can be adapted and instructions for how to adapt them are on [[mw:Special:MyLanguage/Article guidance#Adapting a sample outline in a Wikipedia|this section]] of the project page. * Wikis that wish to replace the "indefinitely" button in Special:Block for temporary accounts (for example, wikis that block temporary users only until account expiration) will be able to do so by creating [[MediaWiki:ipb-indefinite-expiry-temporary-account]] with the block duration they want. [https://phabricator.wikimedia.org/T427125] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:41}} community-submitted {{PLURAL:41|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * By the end of June, a valid user-agent string will be required for automated dumps downloads from the dumps.wikimedia.org website. Automated requests that provide a generic or empty user-agent will be blocked. This [[phab:T400119|extends enforcement]] of the long standing [[foundation:Special:MyLanguage/Policy:Wikimedia Foundation User-Agent Policy|user-agent policy]]. Access to dumps through Wikimedia Cloud Services will not change. * The roll out of global [[mw:Wikimedia APIs/Rate limits|API rate limits]] is now complete, with limits enforced across all APIs and at the documented levels for all groups. Bots running in Toolforge/WMCS or with the bot user right on any wiki remain exempt. All bots should continue to follow the documented best practices to avoid being rate limited. * The [https://api.wikimedia.org/wiki/Main_Page API Portal wiki] will be read only starting this week (June 15-18). The following week (June 22-25), all API Portal wiki URLs will redirect to [[mw:Wikimedia APIs|Wikimedia APIs on mediawiki.org]]. Learn more on the [[wikitech:API Portal/Deprecation|project page]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.7|MediaWiki]] '''Meetings and events''' * On June 17th at 6pm UTC the WMF will be holding Discord call focused on a code review. We've heard through the [[mw:Special:MyLanguage/Developer Satisfaction Survey/2026|Developer Satisfaction Survey]] that volunteers are struggling with code review and we'd like to discuss these experiences with the goal of surfacing workable solutions. You can join the call [https://discord.gg/wikipedia?event=1514727511102062664 via the Wikimedia Community Discord server]. * The [[m:Special:MyLanguage/Conferencia Wikimedia de América Latina 2026|Latin American Wikimedia Conference]] will host a regional hackathon that will bring together the Wikimedia movement’s technical community including developers, system administrators, data scientists, and users with extended rights. Interested technical contributors can [https://docs.google.com/forms/d/e/1FAIpQLSf4osJzTHBJjQbYJk7TMVEJjTEQv7IgtsUDfP-o-qTgeRQQxw/viewform apply for a scholarship] to participate until June 21 at midnight (Bolivia time, UTC-4). * Sign up for Wikimania Team Challenges to join this special event. The Team challenges will take place online and in person from July 21 to 22, before Wikimania conference. Everyone is welcome, regardless of skills or Wikimania registration. Teams will work on 10 important challenges supporting the Wikimedia community. For details, visit [[wmania:Special:MyLanguage/2026:Team challenges|the Team Challenges page]] and [https://wikimedia.eventyay.com/wm/teamchallenges/ register there]. Registration closes on June 20th at 11pm UTC. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/25|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W25"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:49, 15 June 2026 (UTC) <!-- Message sent by User:UOzurumba (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30689604 --> == Wikipedia translation of the week: 2026-26 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Renovating Action Party]]'''<br /> <small>''([[:es:Partido de Acción Renovadora]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:Flag of the Renovating Action Party.svg|300px|center]] <div style="text-align:left; padding: .4em;"> The '''Renovating Action Party''' was a left-wing Salvadoran political party that existed from 1944 to 1967. The party had three distinct phases of its existence under the leaderships of Colonel José Asencio Menéndez (1944–1950), the old line (1950–1964), and the new line (1964–1967). <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:52, 22 June 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30717601 --> == Tech News: 2026-26 == <section begin="technews-2026-W26"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/26|Translations]] are available. '''Weekly highlight''' * [[mw:Special:MyLanguage/Growth/Feature summary|Growth features]] are [[phab:T418115|now available at Wikidata]]. This update enables access to Mentorship ([[mw:Special:MyLanguage/Help:Growth/Mentorship|if configured]]), Impact module, the Help Panel, and a simplified Newcomer Homepage (without Suggested Edits). Wikidata administrators are still configuring the features through Community Configuration. '''Updates for editors''' * The special page [[{{#special:RangeCalculator}}]] has been created. It allows users to find an IP range without needing to rely on external tools. Until now, this tool was only available to CheckUsers. [https://phabricator.wikimedia.org/T268429] * [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]] is a new MediaWiki feature that allows editors to reuse references with different details. It will be deployed to most small and medium-sized Wikipedia language versions on June 23. The [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#deployment|FAQ]] lists possible actions to take on your wiki to support the deployment. Check the [[:phab:T414094|rollout plan]] for the next deployment steps. [https://phabricator.wikimedia.org/T428902] * Starting next week, users will get a notification when they are blocked or unblocked from editing, or if this block changes. [https://phabricator.wikimedia.org/T100974] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:32}} community-submitted {{PLURAL:32|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * Starting next week, abuse filters that are set to "require CAPTCHA verification" will begin to also affect users with the <code>skipcaptcha</code> right, which includes most autoconfirmed users. Bots are exempted. This change only affects edits that trigger an abuse filter. The <code>skipcaptcha</code> right will continue to exempt users from having to solve CAPTCHAs in the ordinary course of using the wikis. [https://phabricator.wikimedia.org/T402595] * Reference documentation for the [[wikitech:Machine_Learning/LiftWing/API|Lift Wing API]] has moved from the API Portal to the interactive [https://wikitech.wikimedia.org/w/index.php?api=lift-wing&title=Special%3ARestSandbox REST Sandbox]. * The API Portal wiki is now closed. For API documentation, see [[mw:Special:MyLanguage/Wikimedia_APIs|Wikimedia APIs on mediawiki.org]]. All API Portal wiki URLs (https://api.wikimedia.org/wiki/) will redirect to the mediawiki.org page starting June 22. [https://phabricator.wikimedia.org/T427537] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.8|MediaWiki]] '''Meetings and events''' * Join an online call on 25 June at 2:30pm UTC to meet the current Wikimedia interns for [[mw:Google_Summer_of_Code/2026|Google Summer of Code]] and [[mw:Outreachy/Round_32|Outreachy]]. Interns will provide an overview of their projects and a brief demo of their work so far. Attendees are encouraged to [[mw:event:Google_Summer_of_Code/Summer_2026_June_Internship_open_session|share ideas and connections in their community]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/26|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W26"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 13:05, 23 June 2026 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30722494 --> == Wikipedia translation of the week: 2026-27 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Facial age estimation]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Facial age estimation''' is the use of artificial intelligence to estimate the age of a person based on their facial features. Computer vision techniques are used to analyse the facial features in the images of millions of people whose age is known and then deep learning is used to create an algorithm that tries to predict the age of an unknown person. The key use of the technology is to prevent access to age-restricted goods and services. Examples include restricting children from accessing internet pornography, checking that they meet a mandatory minimum age when registering for an account on social media, or preventing adults from accessing websites, online chat or games designed only for use by children. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div>--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:44, 29 June 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30717601 --> == Tech News: 2026-27 == <section begin="technews-2026-W27"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/27|Translations]] are available. '''Updates for editors''' * As part of the [[mw:Special:MyLanguage/Contributors/Account Creation Experiments|Account Creation Experiments]], the Growth team tested adding a user account icon in the mobile web header for logged-out users, providing direct access to "Create account" and "Log in" actions. The experiment increased account creation by about 20% without negatively affecting edit quality or constructive edit rates. The feature will now be rolled out to all Wikimedia Foundation wikis on mobile web in the first week of July. [https://phabricator.wikimedia.org/T428220] * After a [[phab:T426248|successful experiment]], logged-in users who did not [[mw:Special:MyLanguage/Help:Email_confirmation|confirm their email address]] when their account was created see a new banner asking them to complete that process. This helps reduce the risk that users get locked out of their account, and makes account email addresses overall more reliable. This is part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] project. [https://phabricator.wikimedia.org/T428292] * An update to [[Special:Search|Search]] is refining how the <bdi lang="zxx" dir="ltr"><code><nowiki>-prefix:</nowiki></code></bdi> behaves when used to exclude results. Previously, using <bdi lang="zxx" dir="ltr"><code><nowiki>-prefix:</nowiki></code></bdi> with negation could unintentionally broaden search results by adding the namespaces included in the search scope, leading to confusing behavior for users expecting a straightforward exclusion filter. With the update, <bdi lang="zxx" dir="ltr"><code><nowiki>-prefix:</nowiki></code></bdi> will now strictly exclude matching page titles as intended and may display a warning if the relevant namespace has not been explicitly selected. The behavior of <bdi lang="zxx" dir="ltr"><code><nowiki>prefix:</nowiki></code></bdi> without negation however remains unchanged. [https://phabricator.wikimedia.org/T427443] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:33}} community-submitted {{PLURAL:33|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where reviewers using the Page Curation toolbar were not automatically subscribed to talk page discussions they started has now been fixed. Reviewers will now receive notifications when someone replies to those discussions. [https://phabricator.wikimedia.org/T329346] '''Updates for technical contributors''' * Starting June 29th, automated downloads from the dumps.wikimedia.org website will be subject to the [[Foundation:Special:MyLanguage/Policy:Wikimedia Foundation User-Agent Policy|user-agent policy]]. Automated requests that provide a generic or empty user-agent will be blocked. Access to dumps through Wikimedia Cloud Services remains unaffected. This is a follow up to the announcement made in the [[m:Special:MyLanguage/Tech/News/2026/25|2026/25 issue of Tech News]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.9|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/27|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W27"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 11:48, 29 June 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30744833 --> == Wikipedia translation of the week: 2026-28 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Paulo César Vinha State Park]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Capim dourado.jpg|300px|center|]] <div style="text-align:left; padding: .4em;"> The '''Paulo César Vinha State Park''' (Portuguese: Parque Estadual Paulo César Vinha) is a state park in the state of Espírito Santo, Brazil. It protects an area of dunes, lagoons and marshes along the Atlantic shore. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:35, 6 July 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30717601 --> == Tech News: 2026-28 == <section begin="technews-2026-W28"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/28|Translations]] are available. '''Updates for editors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:34}} community-submitted {{PLURAL:34|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where the search bar results on Wikidata, showed English results instead of using the correct language fallback for users of language variants, has now been fixed. Search suggestions will now follow the expected language fallback chain. [https://phabricator.wikimedia.org/T429769] '''Updates for technical contributors''' * In preparation for [[m:Special:MyLanguage/Event:Celebrate Women|Celebrate Women campaign]] planned for March 2027, the Wikimedia Foundation’s [[m:Special:MyLanguage/Wikimedia Foundation/Advancement/Community Growth/Content Enablement|Content Enablement team]] has launched a 22-question survey to better understand technical contributions by women+ (anyone who identifies as a woman) across Wikimedia projects. The survey takes approximately 15–20 minutes to complete and will remain open until 20 July 2026. The [[m:Special:MyLanguage/Celebrate Women/Technical contributions survey|questions]] are also available on-wiki for review in advance. * The [[mw:Special:MyLanguage/Extension:Score|Score extension]] now supports rendering music scores as SVG images in addition to PNG, addressing a long-standing [[:phab:T49578|feature request]] and resolving historical image quality issues. Both formats are now provided to clients, with PNG in the <bdi lang="zxx" dir="ltr"><code><nowiki>src</nowiki></code></bdi> attribute and SVG in the <bdi lang="zxx" dir="ltr"><code><nowiki>srcset</nowiki></code></bdi> attribute. * The new [[wikitech:Parsoid|Parsoid]] parser [[mw:Special:MyLanguage/Parsoid/Parser_Unification/Updates|continues to be deployed to additional wikis]], making it easier to introduce new reading and editing features. It was enabled on French Wikipedia, bringing total progress to covering 78.9% of Wikipedia page views. Rollout to English Wikipedia desktop will progress through this week. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.10|MediaWiki]] '''In depth''' * The Wikimedia Hackathon 2026 [[diffblog:2026/06/29/wikimedia-hackathon-2026-building-collaborating-and-shaping-the-future-together/|recap blog post]] is now live. It highlights the projects, sessions, and social activities from this year’s event, and shares initial plans for the 2027 Wikimedia Hackathon. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/28|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W28"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 13:57, 6 July 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30773578 --> == Wikipedia translation of the week: 2026-29 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Caledonian MacBrayne]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Cal-Mac HQ2005.jpg|300px|center|]] <div style="text-align:left; padding: .4em;"> '''Caledonian MacBrayne''', in short form CalMac, is the trade name of CalMac Ferries Ltd, the major operator of passenger and vehicle ferries to the west coast of Scotland, serving ports on the mainland and 22 of the major islands. It is a subsidiary of holding company David MacBrayne, which is owned by the Scottish Government. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> -[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:20, 13 July 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30717601 --> == Tech News: 2026-29 == <section begin="technews-2026-W29"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/29|Translations]] are available. '''Updates for editors''' * [[mw:Special:MyLanguage/Growth/Revise_Tone|Revise Tone]] helps newcomers identify passages in Wikipedia articles that may contain non-encyclopedic language and encourages them to consider revising the tone. The feature was [[w:en:A/B_testing|A/B tested]] on the Arabic, English, French, and Portuguese Wikipedias, where newcomer task completion rates [[mw:Special:MyLanguage/Growth/Revise_Tone#Experiment_Results|increased by 38.7%]] compared to the default Copyedit task, with no decrease in edit quality. The test ended on July 9, and the feature is now available for everyone on these wikis, configurable via Community Configuration. [[phab:T426364|The plan]] is to release Revise Tone to more wikis. * The community configuration that allows [[mw:Special:MyLanguage/Help:Growth/Mentorship#Automated mentor list cleanup|automatic removal of inactive mentors]] based on configurable criteria will be enabled on Thursday 16, [[mw:Special:MyLanguage/Growth/Deployment|on some wikis]] to keep mentor lists up to date. Mentors are experienced contributors who opt in to help new users on-wiki through the [[mw:Special:MyLanguage/Growth/Feature summary|Growth Features]]. Administrators can now prepare the settings via [[w:Special:CommunityConfiguration/Mentorship|Special:CommunityConfiguration/Mentorship]]; they will take effect starting Thursday. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:38}} community-submitted {{PLURAL:38|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where some users of the Wikipedia Android app were logged out immediately after signing in, preventing them from staying logged in and editing pages, has now been fixed. [https://phabricator.wikimedia.org/T316916] '''Updates for technical contributors''' * Editing a page via user scripts or gadgets was causing watchlist labels that the user had assigned to that page to reset. This has now been fixed. [https://phabricator.wikimedia.org/T423778] * To work around a Safari bug (see [[phab:T425211]]), on Parsoid-enabled wikis, wikilink hrefs now use absolute urls instead of protocol-relative urls. REST API output remains unchanged and continue to use protocol-relative urls. Gadgets, user scripts, bots, and CSS might need to be adapted if they relied on the presence of protocol-relative urls in wikilink hrefs. [https://phabricator.wikimedia.org/T431358] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.11|MediaWiki]] '''In depth''' * The Wikimedia Foundation’s Experiment Platform Team has published a blog post reflecting on its first year of structured experimentation. It highlights successful experiments such as Paste Check, Reference Check, and Tone Check, which improved editing outcomes and have been rolled out to more users, as well as experiments that did not lead to product changes. [[diffblog:2026/07/07/moving-the-needle-how-we-test-new-ideas-across-wikimedia-projects|Read more]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/29|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W29"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 16:12, 13 July 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30804401 --> == Wikipedia translation of the week: 2026-30 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Immigration to Switzerland]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> In 2023, resident foreigners made up 26.3% of Switzerland's population. Most of these (83%) were from European countries. Italy provided the largest single group of foreigners, accounting for 14.7% of total foreign population, followed closely by Germany (14.0%), Portugal (11.7%), France (6.6%), Kosovo (5.1%), Spain (3.9%), Turkey (3.1%), North Macedonia (3.1%), Serbia (2.8%), Austria (2.0%), United Kingdom (1.9%), Bosnia and Herzegovina (1.3%) and Croatia (1.3%). Immigrants from Sri Lanka (1.3%), most of them former Tamil refugees, were the largest group of Asian origin (7.9%). <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 20 July 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30717601 --> == Tech News: 2026-30 == <section begin="technews-2026-W30"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/30|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Reader/Reader Experience|Reader Experience team]] has incorporated community feedback around the placement of watchstar and watchlist buttons for the [[mw:Special:MyLanguage/Readers/Reader Experience/WE3.3.4 Reading lists|Reading Lists beta feature]], which would allow for saving articles for later reading – a [[m:Special:MyLanguage/Community Wishlist/W102|wishlist item]] to bring the functionality to web. Editors are invited to enable the beta feature to test it out and [[phab:T426453|share their thoughts]]. * [[mw:Special:MyLanguage/VisualEditor/Suggestion Mode|Suggestion Mode]] offers edit suggestions within the VisualEditor for improving Wikipedia articles. [[Special:EditChecks|All suggestions]] are [[mw:Special:MyLanguage/Help:Suggestion mode#For administrators – local customization|community-configurable]]. The [[mw:Special:MyLanguage/Edit check/TextMatch|TextMatch]] feature is a way for volunteers to create custom local suggestions. The feature searches in articles for strings of text, and now includes support for regular expressions. This gives volunteers greater precision and flexibility over the kinds of local suggestions they can create. Note: Suggestions [[mw:Special:MyLanguage/Edit check/Configuration#:~:text=maximumEditcount|can be targeted]] based on the edit count of the person editing as well as other aspects of the page. You can [[mw:Special:MyLanguage/Help:Suggestion mode#Create custom local types of Suggestions|find examples from other communities]] for inspiration, including TextMatches that detect: typos, grammar-errors, potential advertisements, clichés, incorrect dash or hyphen usage, non-specific time keywords, outdated names, and more. Any [[mw:Special:MyLanguage/Talk:VisualEditor/Suggestion Mode|feedback]] is appreciated. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:27}} community-submitted {{PLURAL:27|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where the SVG Translate tool could use an outdated version of a file, causing existing translations to be overwritten when new ones were uploaded, has now [[phab:T430577|been fixed]]. Overall, in the last quarter from April – June 2026 about 337 community tasks were resolved by the Wikimedia Foundation. '''Updates for technical contributors''' * On Parsoid-enabled wikis, Parsoid now renders a maximum of 1,250 images per page. A new tracking category, "media-limit-reached", will be soon made available to identify pages where this limit is reached, making it easier to find content whose media output may have been restricted during rendering. See [[phab:T430854]] for more information and to provide feedback. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.12|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/30|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W30"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 05:47, 21 July 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30836091 --> == Wikipedia translation of the week: 2026-31 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:fr:Study of Man's Impact on Climate]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> La '''Study of Man's Impact on Climate''' (traduisible en français par « Étude de l'impact de l'homme sur le climat ») est une conférence scientifique internationale consacrée à l'influence humaine sur le climat qui s'est tenue à Stockholm, en Suède, du 28 juin au 16 juillet 1971. Elle aborde diverses hypothèses parmi lesquelles la destruction de la couche d'ozone et le réchauffement (ou refroidissement) climatique, établit l'état du savoir à leur sujet et, soulignant les nombreuses inconnues qui demeurent, appelle à consacrer davantage de fonds à la recherche scientifique sur le climat. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:00, 27 July 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30849684 --> == Tech News: 2026-31 == <section begin="technews-2026-W31"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/31|Translations]] are available. '''Updates for editors''' * [[File:Maki-gift-15.svg|12px|link=|class=skin-invert|Wishlist item]] [[mw:Special:MyLanguage/ContentTranslation|Content Translation]] now supports dark mode, fulfilling a [[m:Community Wishlist/W544|Community Wishlist request]]. This brings the tool in line with the accessibility features available in the Vector 2022 and Minerva skins, helping reduce visual fatigue for users translating content. [https://phabricator.wikimedia.org/T367077] * DiscussionTools' source mode and the 2017 wikitext editor will now offer autocomplete for links (<bdi lang="zxx" dir="ltr"><code><nowiki>[[</nowiki></code></bdi>), templates (<bdi lang="zxx" dir="ltr"><code><nowiki>{{</nowiki></code></bdi>), HTML and parser tags (<bdi lang="zxx" dir="ltr"><code><nowiki><</nowiki></code></bdi>), and magic words (<bdi lang="zxx" dir="ltr"><code><nowiki>__</nowiki></code></bdi>), making it quicker and easier to insert links, templates, and other wiki markup while editing. [https://phabricator.wikimedia.org/T432400] * The [[mw:Special:MyLanguage/Readers/Reader Growth/Mobile page previews|Readers Growth team]] has concluded its experiment with mobile page previews and will not roll out the feature. Page Previews are a pop-up bottom sheet that appears when readers tap a blue link, showing a thumbnail, lead paragraph, and an option to open the article. The experiment showed flat retention and negative indicator metrics, suggesting that mobile web readers preferred navigating directly to linked articles rather than using page previews. * The Reader Experience team has seen encouraging early results from the [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|Reading Lists feature]], with 93% of participating users reporting that it was useful. Reading Lists help active readers save articles for future reading and support their learning goals on Wikimedia projects. The team plans further improvements before expanding the feature to more users. * The [[mw:Special:MyLanguage/Wikimedia Apps/Team/Explore Feed Refresh|Explore Feed Refresh]] initiative was tested with new and casual Wikipedia app readers. The refreshed feed helps readers discover new and relevant content. After a 10.5% increase in engagement with the feed, Wikimedia Apps team has decided to scale the Home Feed redesign to iOS with the learnings from the Android release applied. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:23}} community-submitted {{PLURAL:23|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where subject names in the Article Guidance feature were displayed with incorrect capitalization on French Wikipedia, has now been fixed. Subject names will now follow the correct capitalization rules for the language. [https://phabricator.wikimedia.org/T427201] '''Updates for technical contributors''' * After running several [[mw:Special:MyLanguage/Contributors/Account Creation Experiments|Account Creation Experiments]] to improve registration completion rates, a new version of the username field on [[Special:CreateAccount|Create Account]] has been rolled out. It includes [[:c:File:Create account - July 2026 updates.png|a popover summarizing the username policy]] to provide clearer guidance during account creation. As part of this change, the messages <bdi lang="zxx" dir="ltr"><code><nowiki>createacct-helpusername</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>createacct-username-help</nowiki></code></bdi> that several communities have configured will no longer be used. If communities want to customize the guidance shown in the new popover, they can instead edit the following messages: <bdi lang="zxx" dir="ltr"><code><nowiki>createacct-username-policy-popover-bullet1</nowiki></code></bdi>, <bdi lang="zxx" dir="ltr"><code><nowiki>createacct-username-policy-popover-bullet2</nowiki></code></bdi>, and <bdi lang="zxx" dir="ltr"><code><nowiki>createacct-username-policy-popover-bullet3</nowiki></code></bdi>. [https://phabricator.wikimedia.org/T430604] * Later this week, the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|CodeMirror syntax highlighter]] will offer [[w:en:Theme (computing)|themes]]. The themes can be picked from a dropdown menu in the full [[mw:Special:MyLanguage/Help:Extension:CodeMirror#CodeMirror preferences|CodeMirror preferences]] dialog. For wikitext, available themes are default, colorblind-friendly (previously the colorblind preference option on [[Special:Preferences#mw-prefsection-editing]]) and no-highlighting. For code languages (i.e., CSS/JavaScript/JSON/Vue/Lua), there are several themes available. These same themes will eventually be available for wikitext, too. [https://phabricator.wikimedia.org/T163533] * From now on, wikis can restrict editing in the "User" namespace to only the page owner and certain user groups. [[mw:Special:MyLanguage/Manual:$wgRestrictUserPageEditing|Read the configuration documentation]] to learn more. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.14|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/31|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W31"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:50, 27 July 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30856308 --> == Wikipedia translation of the week: 2026-32 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Plot of Prats de Molló]]'''<br /> <small>''([[:ca:Fets de Prats de Molló]])&#32;([[:es:Complot de Prats de Molló]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''plot of Prats de Molló''' was an attempted military invasion of Catalonia carried out from France to achieve its independence planned by Francesc Macià and the leadership of the Estat Català party, discovered and aborted in 1926. The plan consisted of the penetration of two columns (one from Saint-Laurent-de-Cerdans, the other from Coll d'Ares), which were to occupy Olot and proclaim the Catalan Republic. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:11, 3 August 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30879613 --> == Tech News: 2026-32 == <section begin="technews-2026-W32"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/32|Translations]] are available. '''Updates for editors''' * The [[mw:Special:MyLanguage/Readers/Reader Experience|Reader Experience team]] has developed a [https://82db7c8d4b.catalyst.wmcloud.org/w/index.php?title=Regent%27s_Park&uselang=de patch demo] that wraps the page toolbar onto two lines when there is not enough horizontal space for all the buttons. This aims to reduce crowding in the Vector 2022 toolbar, which can occur on some language Wikipedias at certain screen widths. [https://phabricator.wikimedia.org/T429518] * The Reader Experience team is planning to launch [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|Reading Lists]], a [[m:Special:MyLanguage/Community Wishlist Survey 2021/Mobile and apps/Have Apps reading lists available on Destop/Mobile|Community Wishlist item]], which is currently available to try in beta, as a full feature in September. Before then, volunteer translator help is needed for [https://translatewiki.net/w/i.php?title=Special%3ATranslate&group=ext-readinglists&filter=&action=translate string translations] into a number of languages. The feature supports reading and learning goals on Wikipedia. * Next week, the table of contents on Wikimedia Commons file pages will be improved by consolidating the file page table of contents with the page table of contents. This will make it easier to understand a file page’s structure, navigate to specific sections, and share links to individual sections. [https://phabricator.wikimedia.org/T332644] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:24}} community-submitted {{PLURAL:24|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where some [[w:TIFF|TIFF]] images failed to load after clicking their thumbnail, causing a broken image to be displayed instead of the full-size image, has now been fixed. [https://phabricator.wikimedia.org/T429326] '''Updates for technical contributors''' * The variable and function selector in AbuseFilter has been updated to support search and autocomplete. It will allow filter maintainers to find the desired variable or function more quickly. [https://phabricator.wikimedia.org/T323698] * The MJPEG and VP8 formats are removed from the video player. The MP4 format (MPEG-4 Part 2) is added instead, which provides higher quality videos to older iPhone devices. It may take a few weeks to retroactively update all existing videos. The default format for modern devices stays the same (VP9/WebM). [https://phabricator.wikimedia.org/T358266] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.15|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/32|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W32"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 19:47, 3 August 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30872536 --> == Wikipedia translation of the week: 2026-33 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Composizione VII]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Composition VII - Wassily Kandinsky, GAC.jpg|300px|center|]] <div style="text-align:left; padding: .4em;"> '''Composizione VII''' (Композиция VII o Zu Komposition 7) è un olio su tela del 1913, realizzato dal pittore russo Vasilij Vasil'evič Kandinskij e conservato nella Galleria Tret'jakov di Mosca. Prodotto centrale del pittore russo nel periodo 1910-1915, essa è considerata l'opera che certificò la raggiunta maturità creativa da parte di Kandinskij, rappresentando anche l'apice della sua energia creativa. È considerato il più rappresentativo tra i lavori completati durante l'anno del successo internazionale dell'artista, simboleggiando il punto di emancipazione definitivo dell'Astrattismo. Opera più grande mai realizzata dall'artista per dimensione, facente parte della serie denominata Composizioni, rappresenta un'allegoria dell'Apocalisse, di cui riprende il tema e lo propone in una versione astratta, trasfigurata dalla realtà in una forma composta da sole linee e colori. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:24, 10 August 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30889664 --> == Tech News: 2026-33 == <section begin="technews-2026-W33"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/33|Translations]] are available. '''Updates for editors''' * [[File:Maki-gift-15.svg|12px|link=|class=skin-invert|Wishlist item]] A new ChartWizard is [[c:Special:ChartWizard/Data:Example.Pie.chart|now available on Wikimedia Commons]] for users interested in creating charts from their own data. The wizard makes the [[mw:Special:MyLanguage/Extension:Chart|Chart extension]] more beginner-friendly by allowing editors to create charts, such as bar and pie charts, without needing to use JSON. Users can still switch to the JSON editor if they prefer. Feedback on the new tool is welcome on the [[m:Talk:Community Wishlist/W414|wish talk page]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:19}} community-submitted {{PLURAL:19|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where the Wikipedia iOS app’s Picture of the Day widget displayed the same image every day instead of updating daily, has now been fixed. [https://phabricator.wikimedia.org/T430692] '''Updates for technical contributors''' * [[mw:Special:MyLanguage/Extension:Math|Math formula]] SVG images will soon be generated in the browser instead of on the server. MathML continues to be generated on the server and renders in the browser without JavaScript. Wikibooks will see this change on 12 August, Wikisource on 19 August and Wikipedia from 20-27 August. You can try this by selecting "{{int:Mw-math-mathjax}}" in your preferences. This change is part of [[mw:Special:MyLanguage/RESTBase/deprecation|deprecating RESTBase]] and [[phab:T431372|deprecating Mathoid]]. [https://phabricator.wikimedia.org/T271001] * Category pages will soon support sorting entries by the time they are added to a category. This will make it easier to find recently or long-standing categorized pages. It will also improve workflows for maintenance categories such as deletion backlogs and other time-based review tasks. You can use <bdi lang="zxx" dir="ltr"><code><nowiki>cldsort=timestamp</nowiki></code></bdi> URL argument in category view to sort the entries. [https://phabricator.wikimedia.org/T433768] * [[mw:Special:MyLanguage/Extension:Gadgets|Gadgets]] and user scripts on Wikimedia wikis may now use [[phab:T395347|ES2018 features]] and [[phab:T419142|ES2019 features]] in JavaScript code. Previously, the platform only allowed up to ES2017. MediaWiki validates the source code to protect functionality from syntax errors and to ensure scripts are valid in all [[mw:Special:MyLanguage/Compatibility#Browser_support_matrix|supported browsers]]. [https://phabricator.wikimedia.org/T419142] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.16|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/33|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W33"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:46, 10 August 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30901051 --> == Wikipedia translation of the week: 2026-34 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Divorce in Poland]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''Divorce in Poland''' occurs at a rate slightly below that of the average for Europe. In the Polish legal system, divorce proceedings fall within the exclusive jurisdiction of the civil court; there is no legal basis for resolving a marriage through the agreement of the spouses or through administrative procedures. Divorce requests are assessed by the court, in accordance with the positive and negative prerequisites set in the relevant law. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:59, 17 August 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30927700 --> == Tech News: 2026-34 == <section begin="technews-2026-W34"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/34|Translations]] are available. '''Weekly highlight''' * The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Registration/Worklist|Worklist feature]] for the Event Registration tool is now live on all Wikimedia wikis. With Worklist, event organizers can add the articles their event will focus on directly to the event page. The Worklist also powers [[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Registration/Worklist#How Event Pathways uses the worklist|Event Pathways]] which notifies other editors of the upcoming or ongoing event when they edit an article featured in the event's Worklist. This is the minimum viable version (MVP), and feedback is welcome. Organizers are encouraged to try the feature. A hands-on [[m:Special:MyLanguage/Event:Worklist Setup Workshop: Get Your Event Ready|Worklist Setup Workshop]] will take place on 18 August at 16:00 UTC and 19 August at 11:00 UTC. '''Updates for editors''' * [[Special:ShortPages]] displays short pages by their size, but in many cases it gets filled with disambiguations and soft redirects, making it harder to find the short articles themselves. Starting this weekend, you will be able to choose not to include an article in the special page by adding the magic word <bdi lang="zxx" dir="ltr"><code><nowiki>__EXPECTSHORTPAGE__</nowiki></code></bdi>. [https://phabricator.wikimedia.org/T433203] * One new wiki has been created: a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q3436680|Bole]] ([[w:bol:|<bdi lang="zxx" dir="ltr"><code><nowiki>w:bol:</nowiki></code></bdi>]]) [https://phabricator.wikimedia.org/T429921] * Starting the week of August 17, the page toolbar will wrap onto two lines when there is not enough horizontal space for all the buttons. This is a [[phab:T429518|fully merged patch from the Reader Experience team]] which aims to reduce crowding in the Vector 2022 toolbar, that may occur on some language Wikipedias at certain screen widths. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:16}} community-submitted {{PLURAL:16|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, uploading large files to Wikimedia Commons has become more stable and less prone to failure following some fixes related to the “Could not acquire lock” upload error. [https://phabricator.wikimedia.org/T386640] '''Updates for technical contributors''' * Debian Bullseye will reach the end of its Long Term Support on 31 August 2026. [[phab:T434103|Some Cloud VPS projects]] still have instances running Debian Bullseye. Maintainers of those projects are encouraged to migrate to Debian Bookworm or Debian Trixie. A [[wikitech:Help:Cloud VPS instance operating system migration|migration guide]] is available to help with the process, and users may also want to consider whether their workload is better suited to Toolforge. If you need help or cannot complete the migration by 31 August, please contact the Cloud VPS admins as soon as possible. [[listarchive:list/cloud-announce@lists.wikimedia.org/thread/RVIPQSYLKMSL5M46JP6NEJVGVE6I2RXQ/|Read more]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.16|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/34|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W34"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 21:04, 17 August 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30922806 --> == Wikipedia translation of the week: 2026-35 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Day of the Macedonian Revolutionary Struggle]]'''<br /> <small>''([[:mk:Ден на македонската револуционерна борба]])''</small> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''Day of the Macedonian Revolutionary Struggle''' (Macedonian: Ден на македонската револуционерна борба),[1] also known as Day of VMRO, is a national holiday which is celebrated on October 23 in North Macedonia. In 2007, the holiday was voted into law as a new national holiday. It is a non-working day. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:15, 24 August 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30927700 --> == Tech News: 2026-35 == <section begin="technews-2026-W35"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/35|Translations]] are available. '''Updates for editors''' * The [[Special:CreateAccount|Special:CreateAccount]] page has been simplified as part of ongoing work to modernize the account creation experience. The panel showing project statistics no longer appears next to the form on desktop and mobile web. Multiple account creation experiments show that a simpler form helps newcomers complete registration. [https://phabricator.wikimedia.org/T433783] * In order to improve page performance, images now load when they are viewed. This means images lower down an article will not load if a reader never scrolls to that part of the page, which may affect some image-related metrics. [https://phabricator.wikimedia.org/T148047] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:42}} community-submitted {{PLURAL:42|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where image thumbnails in Abstract Wikipedia could fail to display after the corresponding file was moved on Wikimedia Commons, has now been fixed. Thumbnails will now update correctly when files are moved. [https://phabricator.wikimedia.org/T433448] '''Updates for technical contributors''' * User Info card is a feature that helps patrollers see information about user accounts. So far, it has been available only in places such as page history, logs and recent changes. Now, it's possible to [[mw:Special:MyLanguage/Help:Extension:CheckUser#User_Info_card_in_page_content|place it in the page content]] as well, using the <bdi lang="zxx" dir="ltr"><code><nowiki>{{#uic:}}</nowiki></code></bdi> parser function. It can be particularly useful in templates like [[:en:Template:Userlinks|<bdi lang="zxx" dir="ltr"><code><nowiki>{{Userlinks}}</nowiki></code></bdi>]] (or their specialized variants), as it will make it easier to see the context about a user on various noticeboard pages. The card will be displayed only to users who have it enabled in their [[Special:Preferences#mw-input-wpcheckuser-userinfocard-enable|preferences]]. [https://phabricator.wikimedia.org/T424466] * Due to user security and privacy risks, we have disabled access to <bdi lang="zxx" dir="ltr"><code><nowiki>Special:MyPage</nowiki></code></bdi> URLs when specifically using <bdi lang="zxx" dir="ltr"><code><nowiki>action=raw</nowiki></code></bdi>. If you are impacted by this, consider whether you can use an alternative approach. <bdi lang="zxx" dir="ltr"><code><nowiki>Special:MyPage</nowiki></code></bdi> URLs can still be accessed and used without <bdi lang="zxx" dir="ltr"><code><nowiki>action=raw</nowiki></code></bdi>. Specified user page URLs (e.g. <bdi lang="zxx" dir="ltr"><code><nowiki>User:Myusername</nowiki></code></bdi>) can still be used with <bdi lang="zxx" dir="ltr"><code><nowiki>action=raw</nowiki></code></bdi>. [https://phabricator.wikimedia.org/T120386] * Due to an update, the thumbnailing software has been improved. This includes upgrading <bdi lang="zxx" dir="ltr"><code><nowiki>librsvg</nowiki></code></bdi> to 2.60 and <bdi lang="zxx" dir="ltr"><code><nowiki>ImageMagick</nowiki></code></bdi> to 7, as well as resolving a number of long-standing thumbnailing bugs like rendering errors. [https://phabricator.wikimedia.org/T419815#12222841] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.17|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/35|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W35"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:46, 24 August 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30961208 --> == Wikipedia translation of the week: 2026-36 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Wimmen's Comix]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''''Wimmen's Comix''''', later retitled (respelled) as Wimmin's Comix, is an influential all-female underground comics anthology published from 1972 to 1992. Though it covered a wide range of genres and subject matters, Wimmen's Comix focused more than other anthologies of the time on feminist concerns, homosexuality, sex and politics in general, and autobiographical comics. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:54, 31 August 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30988228 --> == Tech News: 2026-36 == <section begin="technews-2026-W36"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/36|Translations]] are available. '''Weekly highlight''' * A new format for the Community Wishlist is open for feedback. You can [[m:Special:MyLanguage/Community Wishlist/Community Wishlist 2027|read the proposed ideas on Meta]]. This new process plans to improve how wishes are triaged, voted on, and prioritized in a way that is transparent and balanced across project families and language editions. This consultation is open for two weeks. '''Updates for editors''' * The latest release of the Wikipedia Android app includes updates to the Saved feature, bringing the app’s saving experience closer to iOS and Web. The update redesigns the Saved tab with an “All articles” view, removes the default “Saved” reading list, renames reading lists to “Collections,” and modernizes the article-saving experience. [https://phabricator.wikimedia.org/T420788] * The [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|Reading Lists]] feature was enabled for all logged-in users on Bengali, Chinese, Czech and Vietnamese Wikipedias on August 25, after several months as a beta feature. Reading Lists will be available to all logged-in users on Arabic, French and Indonesian Wikipedias on September 1, followed by English Wikipedia on September 14, and all other Wikipedia wikis on September 28. * At the end of the month, some logged-out readers on Bengali, Czech, Persian, English, and Polish Wikipedias using the Minerva skin on mobile will see an [[mw:Special:MyLanguage/Readers/Reader_Growth/Minimal_Minerva|updated navigation bar]] in an [[w:A/B test|A/B test]]. The test will compare the current navigation bar with a new version designed to make it easier to find information more quickly. The goal is to determine whether these changes encourage readers to return more often. This experiment will not change the experience for logged-in readers and/or editors. * Editors who maintain redirects, templates, and categories used on redirect pages now have improved ways for finding and curating redirects. Previously, redirects pages could not be searched. Two new search keywords, <bdi lang="zxx" dir="ltr"><code><nowiki>onlyredirects:</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>withredirects:</nowiki></code></bdi>, now allow redirects to be searched directly and can be combined with existing keywords such as <bdi lang="zxx" dir="ltr"><code><nowiki>incategory:</nowiki></code></bdi>, <bdi lang="zxx" dir="ltr"><code><nowiki>intitle:</nowiki></code></bdi>, and <bdi lang="zxx" dir="ltr"><code><nowiki>insource:</nowiki></code></bdi>. [https://phabricator.wikimedia.org/T204089] * The ISBN lookup tools for generating citations were recently not working because of external service problems. Developers are working on solutions. [https://phabricator.wikimedia.org/T435179] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:30}} community-submitted {{PLURAL:30|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where searching for pages by category using <bdi lang="zxx" dir="ltr"><code><nowiki>deepcat</nowiki></code></bdi> could return no results or unrelated results has now been fixed. [https://phabricator.wikimedia.org/T414859] '''Updates for technical contributors''' * The domain of URLs for thumbnails is changing from upload.wikimedia.org to thumb.wikimedia.org. The old URLs will continue to work for the foreseeable future but MediaWiki will advertise the new domain instead. URLs to other types of media such as original files, videos and transcodes will still be served from upload.wikimedia.org. [https://phabricator.wikimedia.org/T427465] * The Wikimedia [https://www.mediawiki.org/w/index.php?api=wmf-math%2Fv1&title=Special%3ARestSandbox Math API] is now deprecated. These endpoints will be fully sunset by the end of September 2026. Developers who call these endpoints should transition to alternative math rendering solutions, such as the native [https://developer.mozilla.org/en-US/docs/Web/MathML MathML] or [https://www.mathjax.org/ MathJax]. Third-party MediaWiki installations that utilize the Math extension for formula rendering are required to upgrade to v1.43+ to avoid disruption of service. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.18|MediaWiki]] '''In depth''' * Read more about [[mw:Special:MyLanguage/Edit_check/TextMatch|TextMatch]] in a Diff post titled, [[diffblog:2026/08/28/custom-edit-suggestions-for-every-wiki-how-communities-are-shaping-suggestion-mode-with-textmatch/|Custom edit suggestions for every wiki: How communities are shaping Suggestion Mode with TextMatch]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/36|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W36"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 20:54, 31 August 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=30990659 --> == Wikipedia translation of the week: 2026-37 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Paulet affair]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> The '''Paulet affair''', also known as British Hawaii, was the insubordinate five-month occupation of the Hawaiian Kingdom in 1843 by British naval officer Captain Lord George Paulet, of HMS Carysfort. It was ended by the arrival of American warships sent to defend Hawaii's independence. The British government in London did not authorise the move and it had no official status. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:59, 7 September 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=30993988 --> == Tech News: 2026-37 == <section begin="technews-2026-W37"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/37|Translations]] are available. '''Updates for editors''' * [[mw:Special:MyLanguage/Help:Growth/Tools/Add_a_link|Add a Link]] has been upgraded for English Wikipedia users with improved detection of links that have different capitalization. This will help reduce ambiguous suggestions caused by differences in capitalization in article titles, including articles about cultural goods. A second phase of improvements is planned, which will also prepare the feature for release in other languages. [https://phabricator.wikimedia.org/T435526#12240876] [https://phabricator.wikimedia.org/T434259] * The [[mw:Special:MyLanguage/Article_guidance|Article guidance]] feature will be enabled by default for junior editors on Simple English and Turkish Wikipedia starting 10 September 2026 following [[mw:Special:MyLanguage/Article_guidance/Updates#Summary_of_experiment_result|an experiment]]. Junior editors with 0 to 99 edits will automatically see the feature when they click a red link or use the "[[tr:Vikipedi:Madde_sihirbazı|Madde oluşturto]]" option on Turkish Wikipedia to create a new article. The change is intended to help junior editors create higher-quality articles that meet each Wikipedia’s standards. [[phab:maniphest/query/z3tcTjmLMxk5/#R|Additional improvements]] will continue based on the experiment results and community feedback. * The [https://pageviews.wmcloud.org Pageviews Analysis] tool which allows users to compare pageviews across multiple pages, turns 10 years old this year and several new features have been added. They include [[toolforge:wikinav|WikiNav]] which provides insights into how readers of Wikipedia explore the content, editing stats in [https://pageviews.wmcloud.org/siteviews?range=latest-30&sites=en.wikipedia.org Siteviews], the ability to [https://pageviews.wmcloud.org/massviews?source=wikiproject&project=en.wikipedia.org lookup articles belonging to a WikiProject], and support for dark mode. [https://phabricator.wikimedia.org/T378549] * A [[mw:Special:MyLanguage/Readers/Reader_Growth/Minimal_Minerva|visually simplified Minerva]] navigation bar is being tested for logged-out readers using mobile web on the Bengali, Czech, English, Farsi, and Polish Wikipedias. The experiment aims to determine whether simplifying the navigation improves reader retention. The test will run from August 31 to September 28, and no action is required from users. * [[m:Special:MyLanguage/WMDE Technical Wishes|WMDE Technical Wishes]] is working on improving [[en:Wikipedia:VisualEditor/Named references|auto-generated reference names in VisualEditor]]. Editors will only notice a slight change starting this week. When adding automatic reference names the numbering will start at <bdi lang="zxx" dir="ltr"><code><nowiki>:1</nowiki></code></bdi> instead of <bdi lang="zxx" dir="ltr"><code><nowiki>:0</nowiki></code></bdi>. Read more on the [[m:WMDE Technical Wishes/References/VisualEditor automatic reference names|project page]]. [https://gerrit.wikimedia.org/r/c/VisualEditor/VisualEditor/+/1332704] * All wikis will be [[m:Special:MyLanguage/Tech/Server switch|read-only for a few minutes]] on September 23. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [https://phabricator.wikimedia.org/T433363] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:25}} community-submitted {{PLURAL:25|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where [[mw:Special:MyLanguage/Parsoid|Parsoid]] could mishandle nested nowiki tags, causing content to be lost and displaying unwanted text has now been fixed. [https://phabricator.wikimedia.org/T435116] '''Updates for technical contributors''' * Interface administrators can configure gadgets from [[MediaWiki:Gadgets-definition]]. The definition format has been updated and no longer requires the <bdi lang="zxx" dir="ltr"><code><nowiki>ResourceLoader</nowiki></code></bdi> option, as gadgets are always loaded through <bdi lang="zxx" dir="ltr"><code><nowiki>ResourceLoader</nowiki></code></bdi>. This simplifies gadget configuration by removing an option that is no longer necessary, making gadget definitions easier for administrators. [https://phabricator.wikimedia.org/T298199] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.19|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/37|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W37"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:45, 7 September 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=31008437 --> == Wikipedia translation of the week: 2026-38 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:No-AI label]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:No AI Sign.svg|300px|center|]] <div style="text-align:left; padding: .4em;"> A '''no-AI label''' is a label used on a product to signify that it was not made using generative AI. Phrases on the labels include but are not limited to "human-made", "proudly human" and "AI-free". Some organisations that provide the labels allow product creators to download and use their no-AI labels for free, while others charge creators for analysing the content and allowing the use of the labels if the organisation believes that no AI was used. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:43, 14 September 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=31028050 --> == Tech News: 2026-38 == <section begin="technews-2026-W38"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/38|Translations]] are available. '''Weekly highlight''' * The Future Audiences team has started a [[en:Special:MyLanguage/Wikipedia:Village pump (proposals)#New proposed experiment to let readers know about “Google preferred sources”|discussion on English Wikipedia]] about a proposed new experiment to show a temporary notice about the new [https://blog.google/products-and-platforms/products/search/original-high-quality-content-search/ Google Preferred Sources] feature to Wikipedia readers coming from Google. The experiment is to test whether this notice makes visitors come back to Wikipedia more often. Preferred Sources feature lets users choose websites they trust so Google can highlight content from those sources more prominently in Search and AI experiences. We are interested in testing this on other languages that Google supports and would welcome assistance with starting conversations on other wikis. If interested, please reach out to Future Audiences on the [[m:Special:MyLanguage/Future Audiences/Preferred sources|talk page]]. '''Updates for editors''' * The chat platform Discord is releasing a new self-service framework that websites can use to specify how their links should look when shared on Discord. The Future Audiences team is planning to start using this new framework to improve how Wikipedia links look when shared on Discord, giving better attribution and credit to contributors. The link appearance and behavior won't change in the first phase of this project as we want to first collect some baseline data to assess the impact of future changes. However, if community members who are active on Discord spot any issues, they can reach out on [[phab:tag/future-audiences/|Phabricator]] or [[m:Special:MyLanguage/Future Audiences|Metawiki]]. * The Reader Growth team will be running an experiment to test whether [[mw:Special:MyLanguage/Readers/Reader_Growth/Compact Lead|compacting article lead sections on mobiles]] with the addition of a "read more" button improves reader retention. The test will begin on September 17 on Arabic, Spanish, French, Indonesian, Italian, Japanese, Portuguese, Vietnamese, and Chinese Wikipedias and will run for four weeks. * All wikis will be [[m:Special:MyLanguage/Tech/Server switch|read-only for a few minutes]] on September 23. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming week. [https://phabricator.wikimedia.org/T433363] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:28}} community-submitted {{PLURAL:28|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where [https://wikistats.wmcloud.org/ Wikistats] for Wikipedias was returning an HTTP 500 error and could not be reached, has now been fixed. [https://phabricator.wikimedia.org/T435959] '''Updates for technical contributors''' * Developers who maintain a tool that queries the Wikimedia Commons links tables need to update their code to connect to the new x4 database cluster. The links tables have been moved from the s4 cluster to x4, and will no longer receive updates on s4. The page and redirect tables remain available on both clusters. A wiki replica for the x4 cluster will be set up afterwards. The change is being made because the s4 cluster has grown too large to operate efficiently. You can [[wikitech:Special:MyLanguage/News/2026 Commons links tables database split|read more]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.20|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/38|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W38"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 15:31, 14 September 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=31039826 --> == Wikipedia translation of the week: 2026-39 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Scotty (dinosaur)]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Scotty Tyrannosaurus.jpg|300px|center|]] <div style="text-align:left; padding: .4em;"> '''Scotty''' is the nickname for the Tyrannosaurus rex fossil, catalogued as RSM P2523.8, that was discovered in Saskatchewan, Canada in 1991.[3] The fossilised remains were painstakingly removed, almost completely by hand, over two decades from the rock in which they were embedded. When the preparation was complete in 2011, an around 65% complete T. rex skeleton was revealed. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:02, 21 September 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=31045260 --> == Tech News: 2026-39 == <section begin="technews-2026-W39"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/39|Translations]] are available. '''Weekly highlight''' * [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on Wednesday, 23 September 2026 at [https://zonestamp.toolforge.org/1790172000 14:00 UTC]. This is for the datacenter server switchover backup tests, [[wikitech:Special:MyLanguage/Deployments/Yearly calendar|which happen twice a year]]. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies. [https://phabricator.wikimedia.org/T433363] '''Updates for editors''' * The Growth team tested a new post-edit notice designed to [[mw:Special:MyLanguage/Contributors/Account Creation Experiments#4. Encourage Temporary Accounts to Register|encourage Temporary Account holders to register for a permanent account]]. The new notice replaced multiple dialogs and a simultaneous welcome notification with a single message highlighting the benefits of creating an account. The experiment increased permanent account creation from 1.94% to 3.66%, an 87% relative increase. The change will now be released to all wikis. [https://phabricator.wikimedia.org/T433551] * For Wikipedia editors using the [[Special:Preferences#mw-prefsection-betafeatures|"Suggestion mode" Beta Feature]], there is a [[Special:Preferences#mw-input-wpvisualeditor-editcheck-experimental|new opt-in user preference]] for showing "experimental" edit checks and suggestions. These types are listed at [[Special:EditChecks#experimental-checks|Special:EditChecks]], and are intended for early developer-testing and for gathering feedback from experienced users. Administrators can change the [[mw:Special:MyLanguage/Edit check/Configuration|configuration details]] for each suggestion as usual. Administrators can also [[mw:Special:MyLanguage/Help:Suggestion mode#Experimental Suggestions|use this feature]] to help test their community's ideas for locally created checks and suggestions. Experimental types will have a more distinct visual style later this week. [[mw:Talk:VisualEditor/Suggestion Mode|Feedback is welcome]]. * The [[m:CEE Technical Village Pump|CEE Technical Village Pump]] has been launched as a space for technical discussions and collaboration among Wikimedia communities in Central and Eastern Europe. * A new tool, [[mw:Special:MyLanguage/Language Onboarding and Development/Starter kit|Starter Kit]], is now available for new and small language Wikipedia communities. It brings together guided tasks, tools, and resources to help communities get started, monitor their progress, and collaborate with the broader Wikimedia community. Starter Kit is hosted on Wikimedia Toolforge and is designed for Wikipedias with fewer than 50,000 articles. Learn more about how Starter Kit works and how communities have been using it in [[diffblog:2026/09/18/introducing-starter-kit-for-new-and-small-language-wikipedias/|this Diff blog post]]. * The Reader Growth team is launching a retest of the [[mw:Special:MyLanguage/Readers/Reader Growth/Image Browsing|image carousel experiment]]. The retest will use three new versions of the design, updated based on community feedback. The team will assess results and determine with communities whether or not to proceed with the feature. The experiment will begin the week of September 28 and will run on Arabic, Bengali, Chinese, Czech, English, Farsi, French, German, Indonesian, Japanese, Polish, Portuguese, Spanish, Swedish, and Vietnamese Wikipedias. * After successful rollouts to Arabic, Bengali, Chinese, Czech, English, French, Indonesian, and Vietnamese Wikipedias, the [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|Reading Lists feature]] from the Reader Experience team will be available to all logged-in users on all Wikipedia wikis starting September 28. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:28}} community-submitted {{PLURAL:28|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where the mentor status script repeatedly updated mentors’ status even when nothing had changed, creating unnecessary Recent Changes entries, has now been fixed. [https://phabricator.wikimedia.org/T436659] '''Updates for technical contributors''' * The <bdi lang="zxx" dir="ltr"><code><nowiki>abusefilters</nowiki></code></bdi> list query API, used to retrieve specific details about active or historical abuse filters configured on a wiki, has been updated to support the <bdi lang="zxx" dir="ltr"><code><nowiki>formatversion=2</nowiki></code></bdi> configuration parameter, thereby leading to breaking changes to the API response. All users who maintain user-scripts or other code need to check if they use the <bdi lang="zxx" dir="ltr"><code><nowiki>abusefilters</nowiki></code></bdi> list query API, and respond to any breaking changes. [https://phabricator.wikimedia.org/T435828] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.21|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/39|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W39"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 11:56, 27 September 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=31085309 --> == Wikipedia translation of the week: 2026-40 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Descartes Highlands]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Apollo 16 landingsite.jpg|300px|center|]] <div style="text-align:left; padding: .4em;"> The '''Descartes Highlands''' is an area of lunar highlands located on the near side that served as the landing site of the American Apollo 16 mission in early 1972. The Descartes Highlands is located in the area surrounding Descartes crater, after which the feature received its name <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:27, 28 September 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=31087748 --> == Tech News: 2026-40 == <section begin="technews-2026-W40"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/40|Translations]] are available. '''Updates for editors''' * Users of default skins on desktop and mobile web (Vector 2022 and Minerva respectively) will now be informed if the search suggestions displayed as they type into Search come from page redirects. Previously, users could get confused when the top search suggestions did not match exactly what they had typed. The new redirect notice clarifies that these suggestions are not random, but related to the search. The suggested pages may be redirects to the most relevant destination articles being searched for. [https://phabricator.wikimedia.org/T303013] * Logged-out Wikipedia users on mobile web will begin to see a bookmark button for saving articles to their [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|reading lists]] instead of the current Watchstar button. When clicked, the bookmark button prompts users to log in or create an account to save an article for later. An earlier experiment found that the bookmark icon was four times more likely than the Watchstar button to encourage logged-out users to create an account. This change is part of efforts to encourage more readers to become account holders and use features that help them save and return to content. [https://phabricator.wikimedia.org/T438769] * An experiment will begin on September 29 on Spanish, Arabic, English, and French Wikipedias to simplify the experience users encounter immediately after account creation. The test will explore whether removing friction from the current Welcome Survey helps new users understand what to do next more easily. The experiment will run through the end of October. [https://phabricator.wikimedia.org/T430058] * The [[m:Special:MyLanguage/Product and Technology Advisory Council|Product and Technology Advisory Council]] has put out a call for the community to suggest topics that it should consider and discuss with the Wikimedia Foundation. Editors and technical contributors are invited to add topics to [[m:Talk:Product and Technology Advisory Council|the council's talk page]]. * Later this week, it will be possible for communities to configure [[mw:Special:MyLanguage/Help:Edit check|Edit Checks and Suggestions]] so that they are [[mw:Special:MyLanguage/Edit check/Configuration#extraNamespaces|shown within additional namespaces]], such as a <bdi lang="zxx" dir="ltr"><code><nowiki>Draft:</nowiki></code></bdi> namespace. [[mw:Talk:VisualEditor/Suggestion Mode|Feedback is welcome]]. * A bug in the [[m:Special:GlobalWatchlist|Global Watchlist]] is causing the page to fail to load for users that have unseen changes on Wikimedia Commons. Developers are working on a fix. Until then, affected users can follow the workarounds described in the [[mw:Special:MyLanguage/Extension:GlobalWatchlist#GlobalWatchlist temporarily broken for users with Wikimedia Commons|relevant]] help section. * New magic words <bdi lang="zxx" dir="ltr"><code><nowiki>{{CATEGORYSORT:TIMESTAMP}}</nowiki></code></bdi> and <bdi lang="zxx" dir="ltr"><code><nowiki>{{CATEGORYSORT:RTIMESTAMP}}</nowiki></code></bdi> are now available for use. They are able to change the default sorting of categories to be based on timestamp of categorization. [https://phabricator.wikimedia.org/T433768] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:20}} community-submitted {{PLURAL:20|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where [https://wikistats.wmcloud.org/ Wikistats] for Wikipedias was not reachable has now been fixed. [https://phabricator.wikimedia.org/T435959] '''Updates for technical contributors''' * The datacenter switchover, scheduled on September 23, has been postponed. [[diffblog:2025/03/12/hear-that-the-wikis-go-silent-twice-a-year/|The equinox exercise]] revealed capacity issues, preventing the switch of all services to the other datacenter. The process has been paused, prioritizing investigating that issue, to ensure that we continue to be able to serve our users reliably. A new exercise will be scheduled. Meanwhile, all traffic and edits continue to work as usual. * On September 23, a power loss briefly affected all wikis, creating intermittent issues on both reading and editing modes. This also affected Gerrit. This is unrelated to the datacenter switchover postponement. [https://www.wikimediastatus.net/incidents/9fm19t8qykk8] * [[mw:Special:MyLanguage/Help:Extension:Produnto|Produnto]] has been deployed to mediawiki.org and [[phab:T421436|some Indic language wikis]]. We want to hear your feedback on this experimental product. Produnto allows users to use Lua modules hosted in [[gitlab:repos/lua|Wikimedia's GitLab]]. It simplifies the sharing of Lua code between wikis. Instead of copying each individual Lua module from one wiki to another, users will be able to easily share packages across all wikis. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.22|MediaWiki]] '''Meetings and events''' * A [[m:Event:Cross-wiki Code Collaboration Workshop|Cross-wiki code collaboration workshop]] will be held online on October 2 at 12:30 UTC, bringing together South Asian technical contributors to learn about Produnto and begin piloting it on Hindi, Punjabi, Odia, Telugu, and Malayalam Wikipedias. Produnto is a package manager for deploying Lua modules hosted on GitLab to Wikimedia wikis, and was recently deployed on some pilot wikis. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/40|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W40"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 10:49, 28 September 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=31092225 --> == Wikipedia translation of the week: 2026-41 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:it:Battaglia del pastificio]]'''<br /> <small>''([[:en:Battle of Checkpoint Pasta]])''</small> </div> Please be bold and help translate this article! </div> ---- [[File:OTO Melara Somalia 1993.jpg|300px|center|]] <div style="text-align:left; padding: .4em;"> La '''battaglia del pastificio''', talvolta chiamata anche battaglia del checkpoint Pasta, fu uno scontro a fuoco verificatosi a Mogadiscio tra le truppe italiane e le milizie Mooryaan somale del generale Aidid ed è ricordata per essere stata la prima battaglia che vide impiegati i militari dell'Esercito Italiano dalla fine della seconda guerra mondiale. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:39, 5 October 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=31108366 --> == Tech News: 2026-41 == <section begin="technews-2026-W41"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/41|Translations]] are available. '''Weekly highlight''' * The process for this year’s Community Wishlist [[m:Special:MyLanguage/Community Wishlist/Community Wishlist 2027#Updated Community Wishlist Process 2027/2028|has been published]], incorporating community feedback. The wish submission process will [[m:Special:MyLanguage/Community Wishlist/FAQ#What is the deadline for submitting wishes?|end on November 8]]. This year, [[m:Special:MyLanguage/Community Wishlist/Community Wishlist 2027/Working group|a working group (open for volunteering)]] that includes community members familiar with the technical aspect of our wikis alongside Wikimedia Foundation staff, will take care of the [[m:Special:MyLanguage/Community Wishlist/FAQ#What is triage?|triage process]]. The triage is expected to be completed by late November. Votes for wishes will start in January. '''Updates for editors''' * Editors using the [[mw:Special:MyLanguage/VisualEditor|visual editor]] will now see a warning when they paste text that is likely to have initially been copied from one of five external generative AI chatbots into Wikipedia. This feature is known as [[mw:Special:MyLanguage/Edit check/LLM Paste Check|LLM Paste Check]]. It is a type of [[mw:Special:MyLanguage/Edit check|Edit Check]] that is community configurable. The check looks for markers in the copied HTML and is not using content watermark detection. Edits will also [[mw:Special:MyLanguage/Edit check/LLM Paste Check#Edit tags|be tagged]] so that patrollers can review them more closely. The feature helps newcomers add content that respects Wikipedia’s policies and makes it easier for experienced editors to identify problematic edits. Communities with local policies about LLM usage can [[mw:Special:MyLanguage/Edit check/LLM Paste Check#Configuration|adjust the wording and policy that is linked]]. The team [[listarchive:list/translators-l@lists.wikimedia.org/message/EVHKWJ4IERZELMPIWNH3XUVUSQV5KOO4/|apologizes]] that this was rolled out without a delay for translations. * Editors can now easily [[mw:Special:MyLanguage/Wikimedia Apps/Team/Future of Editing on the Mobile Apps|access the web visual editor directly from the iOS and Android apps]]. When opening the editor, users will be given a choice between visual editing and source editing. If they choose visual editing, they will be sent to a mobile web window in their phone's browser. After completing their edit, a banner will give them the option to return to the app. This enables readers to make quick contributions while casually reading. * Users of the Wikipedia Android and iOS apps will now see a one-time account creation prompt after they have used the app for two consecutive weeks. This prompt explains the benefits of having an account. It is intended to help more casual readers become logged-in users who return to the apps regularly. [https://phabricator.wikimedia.org/T434847] * Editors on [[wmnoc:conf/dblists/group1.dblist|group1 wikis]], including Wikiquote, Wikibooks, Wikiversity, Wikivoyage, and Wikisource, will no longer see notifications on [[mw:Special:MyLanguage/Help:Recent changes|Recent Changes]] and [[mw:Special:MyLanguage/Help: Watching pages|Watchlist]] when a link to another language version of a page is added, removed, or changed in its Wikidata item. This change will begin on October 5 at 07:00 UTC as a two-week trial to reduce high-volume, low-value notifications and make important changes easier to identify. Editors who rely on these notifications can read more on the [[m:Wikidata For Wikimedia Projects/Clearer Wikidata Edit Summaries/Hide Language Link edits|project page]] and share feedback or concerns on the [[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|talk page]]. [https://phabricator.wikimedia.org/T439415] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:36}} community-submitted {{PLURAL:36|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where mentors who removed themselves from the mentorship program could still have mentees assigned to them and receive questions, has now been fixed. Mentees will now be reassigned when a mentor leaves the program. [https://phabricator.wikimedia.org/T418194] '''Updates for technical contributors''' * Wikimedia Brasil has published its [[m:Special:MyLanguage/Wikimedia Brasil/Arcabouço de Boas Práticas de Desenvolvimento|Development Best Practices Framework]] (ABPD). It is a guide for staff, contractors and volunteers building technical tools and projects. It covers the project lifecycle, security, accessibility, personal data protection and responsible AI use, and explains how movement-wide guidelines were adapted to a local context. They encourage other affiliates to reuse it and adapt it. Read more in the [[wmfblog:2026/09/26/wikimedia-brasils-development-best-practices-framework-technical-sustainability-as-an-organizational-responsibility|Diff post]]. * A new, canonical base URL for Wikimedia APIs will soon be introduced. The new canonical route follows a <bdi lang="zxx" dir="ltr"><code><nowiki>{projectName}/api/</nowiki></code></bdi> pattern and will act as an alternative path for current REST APIs (for example: <bdi lang="zxx" dir="ltr"><code><nowiki>{projectName}/w/rest.php/</nowiki></code></bdi>). Both versions will be callable for all existing APIs, but the new structure will be the preferred path for newly created API modules. This change will be non-breaking for most users. The existing pathways will remain available for all existing endpoint requests. However, some endpoints may return URLs following the new pattern in response bodies. Changes will be available on test wiki first, with the rollout expected to cover all wikis by the end of October. [https://phabricator.wikimedia.org/T433535] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.23|MediaWiki]]. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/41|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W41"/> 18:52, 5 October 2026 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=31098825 --> == Wikipedia translation of the week: 2026-42 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:The Trolleybus Museum at Sandtoft]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Lineup.5.JPG|300px|center|]] <div style="text-align:left; padding: .4em;"> '''The Trolleybus Museum at Sandtoft''' is a transport museum which specialises in the preservation of trolleybuses. It is located by the village of Sandtoft, near Belton on the Isle of Axholme in the English county of Lincolnshire. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:09, 12 October 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=31131525 --> == Tech News: 2026-42 == <section begin="technews-2026-W42"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/42|Translations]] are available. '''Weekly highlight''' * Starting October 13, wikis can change the default pattern for [[:en:Wikipedia:VisualEditor/Named references|auto-generated reference names in VisualEditor]] (currently <syntaxhighlight lang="wikitext" inline><ref name=":1" /></syntaxhighlight>). They will be able to use human-readable, content-based reference names that are more helpful to contributors using the source editor (e.g. <syntaxhighlight lang="wikitext" inline><ref name="Miller2026-1" /></syntaxhighlight>). VisualEditor reference name patterns can be defined using MediaWiki system messages, JSON, templates and modules ([[:mw:Special:MyLanguage/Help:Cite/VisualEditor reference names|more information]]). Admins can enable these changes via [[Special:CommunityConfiguration/Cite-VisualEditor-Autonames|community configuration]]. This is a [[:m:Special:MyLanguage/Community_Wishlist/W17|community wish]] implemented by [[:m:Special:MyLanguage/WMDE Technical Wishes|WMDE Technical Wishes]]. [https://phabricator.wikimedia.org/T436255] * [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]] is a new MediaWiki feature that allows editors to reuse references with different details. It will be deployed to English Wikipedia on October 14 and to remaining Wikimedia Foundation wikis by end of October (likely October 21). The [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#deployment|FAQ]] lists possible actions to take on your wiki to support the deployment. This is a [[:m:WMDE Technical Wishes/Sub-referencing/History|long-standing community wish]] implemented by [[:m:Special:MyLanguage/WMDE Technical Wishes|WMDE Technical Wishes]]. [https://phabricator.wikimedia.org/T440243][https://phabricator.wikimedia.org/T440304] '''Updates for editors''' * [[mw:Special:MyLanguage/Moderator Tools|Moderator Tools]] will be removing the list view of the Watchlist and defaulting everyone to the changelog view. Previously, there were two versions of how the Watchlist is shown to mobile web users: the list view, where editors could see watched articles in a list format, and the changelog view, where editors could see changes to watched articles in a log format, controlled by a user's Advanced Mobile Control settings. This has created issues for code-base maintenance: two different displays means two sets of code to manage. By defaulting to the changelog view, we are simplifying the codebase and avoiding the likelihood of missing bugs. * The Wikipedia Android app is testing a way to listen to article introductions in the “For you” feed. A text-to-speech model reads the existing article text aloud without rewriting it or adding any content. The 30-day experiment will begin in the Wikipedia Beta app during the third week of September, then move to the regular Wikipedia Android app in October for a limited group of eligible users. A small portion of app users (those with English feeds and at least one topic interest) will have access to the feature. This experiment is part of broader efforts to give app readers options in how they consume content in order to deepen engagement and user retention. [[mw:Special:MyLanguage/Readers/Listening to Wikipedia/Phase 1|Learn more]] and [[mw:Talk:Readers/Listening to Wikipedia|share feedback]]. * [[mw:Special:MyLanguage/Help:Extension:CodeMirror|CodeMirror syntax highlighting]] was [[phab:T288161|enabled]] by default for all logged out and newly registered users on the English Wikipedia on September 14. With no signs of adverse effects, the same change is being proposed to be made globally across all wikis in a few weeks. If you have concerns or feedback, or if your wiki would like to opt out, [[mw:Special:MyLanguage/Help talk:Extension:CodeMirror#Enabling CodeMirror by default on all WMF wikis for newbies|please see the help page]]. [https://phabricator.wikimedia.org/T440077] * [[d:Wikidata:Usability_and_usefulness/Item_editing_experience/Mobile_editing_of_statements|Wikidata mobile statement editing]] of all datatypes will be officially launched on October 13, when it will be removed from Wikidata [[d:Special:Preferences#mw-prefsection-betafeatures|beta features]] and become available to all editors. Users can [[d:Wikidata_talk:Usability_and_usefulness/Item_editing_experience/Mobile_editing_of_statements|report bugs and share feedback]]. * Last week, language link changes were removed from [[Special:RecentChanges|Recent Changes]] and [[Special:Watchlist|Watchlist]] feeds on Wikivoyage, Wikisource, Wikiversity, Wikiquote and Wiktionary. As no adverse effects have been observed, the [[m:Wikidata_For_Wikimedia_Projects|Wikidata For Wikimedia Projects]] plans to roll out this change globally to all Wikipedias. This is scheduled for October 13 at 07:00 UTC, after which editors will no longer see when a link to ''another'' language version of a page is added, removed, or changed in its Wikidata item. Editors who rely on these notifications can read more on the [[m:Wikidata For Wikimedia Projects/Clearer Wikidata Edit Summaries/Hide Language Link edits|project page]] and share feedback or ask to opt out their wiki on the [[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|talk page]]. [https://phabricator.wikimedia.org/T440698] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:28}} community-submitted {{PLURAL:28|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where accidentally touching the graph while scrolling on the Pageviews tool on mobile could unintentionally zoom in has now been fixed. Click-and-drag zoom is now disabled on touch devices. [https://phabricator.wikimedia.org/T440075] '''Updates for technical contributors''' * There are three major changes coming to dumps: the legacy content dumps [https://lists.wikimedia.org/hyperkitty/list/xmldatadumps-l@lists.wikimedia.org/thread/E6D5EU4PMSTSOI2J7A46HJ3YW2W554CS/ deprecated in January 2026] will now be sunset, the replacement [https://wikitech.wikimedia.org/wiki/MediaWiki_Content_File_Exports MediaWiki Content File Exports] will be delayed to implement a “safety buffer”, and they are now also available as 7zip-compressed files. Users will need to switch the URL they download their dump from. For more information, timeline and migration instructions, see [https://wikitech.wikimedia.org/wiki/Legacy_content_dumps_sunset Legacy content dumps sunset]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.24|MediaWiki]] '''In depth''' * The Wikimedia Foundation discovered unauthorized activity by OpenAI agents on Wikimedia projects, including edits to wikis, attempts to exploit a public note-taking tool, and heavy automated traffic. [[diffblog:2026/10/05/openai-rogue-agent-activities-found-on-wikimedia-projects/|Read the blog post on Diff]] for more details about the activity and the Foundation’s response. '''Meetings and events''' * Save the date for the next Wikimedia Hackathon! We’ll be meeting in lovely Tirana, Albania for the [https://www.mediawiki.org/wiki/Wikimedia%20Hackathon%202027 2027 Wikimedia Hackathon] from April 9–11, 2027. Scholarship and staff sponsorship applications are currently being [https://pretix.eu/wikimedia/Hackathon-2027/ accepted through Pretix] and will close on October 30, 2026. General registration will open in January 2027. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/42|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W42"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 07:40, 13 October 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=31142468 --> == Wikipedia translation of the week: 2026-43 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:Jalapeño popper]]'''<br /> </div> Please be bold and help translate this article! </div> ---- [[File:Cooking-food-stuffed-jalapenos-peppers.jpg|300px|center|]] <div style="text-align:left; padding: .4em;"> '''Jalapeño poppers''', or jalapeño bites, are jalapeño peppers that have been hollowed out, stuffed with a mixture of cheese, spices, and sometimes ground meat, and breaded and deep-fried or wrapped with bacon and baked. They are a common dish on appetizer menus in chain restaurants in the United States. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 07:15, 19 October 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=31131525 --> == Tech News: 2026-43 == <section begin="technews-2026-W43"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/43|Translations]] are available. '''Updates for editors''' * To measure the impact of incorporating some [[mw:Special:MyLanguage/Readers/Reader_Growth/Image_Browsing#November 2025: Ideas and feedback|community-requested features]] on logged-out reader retention, a test for [[mw:Special:MyLanguage/Readers/Reader_Growth/Image_Browsing|Image Carousel]] will be pushed to logged-out readers. With the Image Carousel feature, readers browse community-uploaded images, selected by editors as relevant to specific articles. The test starts on November 20. * An experimental notice will be pushed to 0.5% of logged-out mobile readers who come to English Wikipedia from Google, asking them to add Wikipedia as a [https://blog.google/products-and-platforms/products/search/preferred-sources/ Google Preferred Source]. The test is to see if this notice increases reader retention and encourages people who use Google Search to visit Wikipedia more often. It will run from October 15–29 and will be assessed for its impact on retention and referrals. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:26}} community-submitted {{PLURAL:26|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where [[quarry:|Quarry]] returned an “Access denied” error when users tried to run SQL queries, preventing queries from running normally, has now been fixed. [https://phabricator.wikimedia.org/T440966] '''Updates for technical contributors''' * [[File:Cog-icon-grey.svg|12px|link=|class=skin-invert|Advanced item]] Due to a long-standing bug, applications that use the [[mw:Special:MyLanguage/OAuth/For_Developers|OAuth 2]] client credentials flow to act on their owners’ behalf are treated as if they are logged out. This will be fixed for new applications registered on or after Monday, October 19. Some affected applications need to re-register. [https://phabricator.wikimedia.org/T420297] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.48/wmf.1|MediaWiki]] '''Meetings and events''' * A proposal to hold the Wikimedia Hackathon every three years, with regional hackathons in between, [[mw:Wikimedia Hackathon/Community Proposal 2026|has been shared]]. It explores making the event more accessible to technical communities in different regions. Share your feedback on the proposal’s [[mw:Talk:Wikimedia Hackathon/Community Proposal 2026|talk page]] before November 6. '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/43|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W43"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 14:38, 19 October 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=31178499 --> == Wikipedia translation of the week: 2026-44 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:National Day of Bhutan]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''National Day of Bhutan''' (Dzongkha: རྒྱལ་ཡོངས་དུས་ཆེན་; Wylie: rgyal yongs dus chen) known as Gyalyong Düchen is a major national event celebrated annually on 17 December in the Kingdom of Bhutan <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:05, 26 October 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=31131525 --> == Tech News: 2026-44 == <section begin="technews-2026-W44"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/44|Translations]] are available. '''Weekly highlight''' * An experiment launched on September 29 is testing [[mw:Special:MyLanguage/Readers/Reader_Experience/Reading_recommendations|article recommendations]] for new account holders who also identify as readers. By suggesting articles to read, similar to recommendations in the Wikipedia app for logged-in readers, the experiment aims to encourage new account holders to read and return to the website regularly, with the goal of increasing internal referrals by 1%. See the related [[m:Community Wishlist/W505|Community Wishlist]] proposal. * Several Wikimedia services were taken offline last week because of a [https://www.php.net/archive/2026.php#2026-10-20-1 security vulnerability in PHP]. This is because they need to be updated before they are safe to put back online. This is not a problem just for the Wikimedia movement but affects a lot of websites. You can follow updates on [[wikitech:Incidents/2026-10-21 PHP security update/Community|Wikitech]]. Cloud VPS and Toolforge will take longer to bring back online. This is to make sure that applications which run on Cloud VPS or Toolforge are not affected. Tool developers can see updates and more information on the [https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.org/ Cloud-announce mailing list]. [https://diff.wikimedia.org/2026/10/21/impact-of-php-vulnerabilities-on-wikimedia-tools-and-services/][https://diff.wikimedia.org/2026/10/21/impact-of-php-vulnerabilities-on-wikimedia-cloud-services/] * [[m:Special:MyLanguage/Tech/News/2026/43|Last week we shared]] that to measure the impact of incorporating some community-requested features on logged-out reader retention, a test for the [[mw:Special:MyLanguage/Readers/Reader Growth/Image Browsing|Image Carousel]] feature would be pushed to logged-out readers. Due to an issue, we will be restarting the test, but it will be live on October 26, not November 20 as initially announced. '''Updates for editors''' * A new [[wikitech:KAPOW|bot detection system]] to better identify automated traffic that disguises itself as human visitors, is coming to the Wikimedia wikis. This might cause sudden changes to visitor statistics starting from 26 October, going back to 20 June 2026. * The [[mw:Special:MyLanguage/Extension:Score|Score extension]] which renders musical notation inside wiki pages, has been temporarily disabled on all wikis due to a security issue. Affected pages will display a notice instead of musical scores, but the underlying code remains intact. No action is needed from editors, and a fix is in progress. A separate announcement will follow when the extension is re-enabled. Read more on [[phab:T441579|Phabricator]]. * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:18}} community-submitted {{PLURAL:18|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, the issue where CodeMirror syntax highlighter appears to have been enabled in error for existing editors has been fixed. [https://phabricator.wikimedia.org/T441308] '''Updates for technical contributors''' * [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on Wednesday, October 28 2026 at [https://zonestamp.toolforge.org/1793199600 15:00 UTC]. This is for the datacenter server switchover backup tests, [[wikitech:Deployments/Yearly calendar|which happen twice a year]]. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies. [https://phabricator.wikimedia.org/T439703] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.48/wmf.2|MediaWiki]] '''Meetings and events''' * Scholarship and sponsorship applications for the [https://www.mediawiki.org/wiki/Wikimedia%20Hackathon%202027 2027 Wikimedia Hackathon] will close on Friday, October 30th. Submit your application [https://pretix.eu/wikimedia/Hackathon-2027/ through Pretix] before the deadline! '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/44|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W44"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 18:57, 26 October 2026 (UTC) <!-- Message sent by User:STei (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=31199592 --> == Wikipedia translation of the week: 2026-45 == <div lang="en" dir="ltr" style="width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;"> <div style="text-align:center;">The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is <div style="font-size:140%;">'''[[:en:AI washing]]'''<br /> </div> Please be bold and help translate this article! </div> ---- <div style="text-align:left; padding: .4em;"> '''AI washing''' is a deceptive marketing tactic that consists of promoting a product or a service by overstating the role of artificial intelligence (AI) and the integration of it. Companies often involve in the practice to mislead customers to boost their offerings, and to secure funding from investors. The practice raises concerns regarding transparency, and legal issues. <small>(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)</small> ---- [[File:TOTW.svg|24px|]] ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]'' </div> </div> --[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 2 November 2026 (UTC) <!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&oldid=31131525 --> == Tech News: 2026-45 == <section begin="technews-2026-W45"/><div class="plainlinks"> Latest '''[[m:Special:MyLanguage/Tech/News|tech news]]''' from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. [[m:Special:MyLanguage/Tech/News/2026/45|Translations]] are available. '''Weekly highlight''' * Many Wikimedia tools were taken offline last week because of a [[:w:PHP2Shell|security vulnerability in PHP]]. This affected many websites worldwide. [[m:Special:MyLanguage/Toolforge|Toolforge]] and [[m:Special:MyLanguage/Wikimedia Cloud Services|Cloud VPS]] have been back up since October 22. Many important tools have been gradually restored. Some tools need the respective volunteer maintainers to restart them. Others still need to upgrade to a patched PHP version. Some tools were using older versions of PHP which are not supported by the recent security patches. They will require maintainers to upgrade to a more recent version. This might require additional effort. You can follow the work [[:wikitech:Talk:Incidents/2026-10-21 PHP security update/Community#Exceptions|on Wikitech]]. '''Updates for editors''' * A new optional search experiment is running in the Wikipedia Android and iOS apps for Arabic, French, and Japanese Wikipedias. Participating readers can search inside articles and open quoted passages directly in their source articles, no answers or summaries are generated. This is the first of four experiments in [[mw:Special:MyLanguage/Readers/Information%20Retrieval/Phase%202|Phase 2 of Semantic Search]]. It began on October 22 and runs for 20 days. Feedback is welcome on the project’s [[mw:Special:MyLanguage/Talk:Readers/Information%20Retrieval/Phase%202|discussion page]]. * The [[m:Special:MyLanguage/Future_Audiences|Future Audiences]] team is planning to bring [[m:Special:MyLanguage/Future_Audiences/Share_card|Share Cards]] to Wikipedia on mobile. This feature gives users the option to share a visually appealing card with friends, based on the article they are reading. The card contains the article’s title, image, opening text, and related attribution, and links back to the article for full reading. Editors are invited to try out this feature by adding <code dir="ltr">?useformat=mobile&sharecard=1</code> to any article URL from October 29 to November 8. Share any thoughts on the [[m:Talk:Future_Audiences/Share_card| project talk page]] and report any bugs on [[phab:T439161|Phabricator]]. * The default renderer for math formulas will change on November 2. After the change, the server sends the formula as MathML, and your browser uses MathJax to show it. This is the last step towards the Mathoid/RESTBase deprecation process, for sustainability and security reasons. You can [[w:en:Wikipedia:WikiProject Mathematics/MathFormattingBugs|ask questions or report problems]]. [https://phabricator.wikimedia.org/T375238] * Do you have an idea for a new feature, or a bug that needs fixing? [[m:Special:MyLanguage/Community Wishlist|Submit your suggestion for the community wish list by November 8!]] * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:41}} community-submitted {{PLURAL:41|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. '''Updates for technical contributors''' * [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.48/wmf.3|MediaWiki]] '''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&nbsp;• [[m:Special:MyLanguage/Tech/News/2026/45|Translate]]&nbsp;• [[m:Tech|Get help]]&nbsp;• [[m:Talk:Tech/News|Give feedback]]&nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].'' </div><section end="technews-2026-W45"/> <bdi lang="en" dir="ltr">[[User:MediaWiki message delivery|MediaWiki message delivery]]</bdi> 14:23, 3 November 2026 (UTC) <!-- Message sent by User:Trizek (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Global_message_delivery/Targets/Tech_ambassadors&oldid=31236748 --> 45si1xzcnsqkp5h0ax6cc86otoehdpi Wikibooks:Sandbox 4 464822 4679904 4679676 2026-11-04T07:19:32Z NARAKASURA985 3626636 4679904 wikitext text/x-wiki == <big>ESP32 Microcontroller and Its Features</big> == The ESP32 is a low-cost, low-power microcontroller developed by Espressif Systems. It is widely used in embedded systems, Internet of Things (IoT) applications, robotics, and automation projects. The ESP32 features a 32-bit processor with dual-core architecture in the original ESP32 variant, operating at frequencies up to 240 MHz's One of its major advantages is built-in Wi-Fi and Bluetooth connectivity, enabling wireless communication with smartphones, computers, and other devices. It provides multiple GPIO pins for interfacing with sensors, LEDs, displays, and motors. It also supports ADC, DAC, PWM, UART, SPI, and I2C communication interfaces. The ESP32 supports programming through Arduino IDE and Micro-Python, making it suitable for beginners and advanced developers. Its low-power modes, compact design, and versatile peripherals make it an excellent choice for smart homes, wearable devices, industrial automation, and IoT-based applications. l8y53yjn1yhw30lirmpfvplk725updf User talk:Codename Noreste 3 466307 4679928 4679699 2026-11-04T08:10:56Z ArchiverBot 1227662 Bot: Archiving 1 thread (older than 14 days) to [[User talk:Codename Noreste/Archive 1]] 4679928 wikitext text/x-wiki {{talk header}} {{User:MiszaBot/config |archive = User talk:Codename Noreste/Archive %(counter)d |algo = old(14d) |counter = 1 |maxarchivesize = 100K |archiveheader = {{Automatic archive navigator}} |minthreadstoarchive = 1 |minthreadsleft = 1 }} == Information about Wikibooks Magazine on Mediawiki Sitenotice == Hello Codename Noreste, If it is alright, could you perhaps add the suggestion that I have made on the MediaWiki Sitenotice? Many thanks. --[[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 04:31, 3 November 2026 (UTC) ftg4uarrydhadjf9djuv3lflo4swfmi User talk:Codename Noreste/Archive 1 3 477022 4679927 4676478 2026-11-04T08:10:46Z ArchiverBot 1227662 Bot: Archiving 1 thread from [[User talk:Codename Noreste]] 4679927 wikitext text/x-wiki {{Automatic archive navigator}} == Question == Hi @[[User:Codename Noreste|Codename Noreste]]! Is there a reason you created [[Cuisine of Mexico]] as a redirect? Nothing links there, and all redirects in the cookbook should begin with the Cookbook: prefix. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:39, 8 May 2025 (UTC) : Hi. Say for example there is a redirect, [[Cuisine of Armenia]] (it does exist), and it redirects to the cookbook itself. I thought it would be OK to create the redirect per that example I posted here, but otherwise you can let me know what mistakes I have done and how I can learn from them. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:50, 8 May 2025 (UTC) ::Very understandable! I took a look at it, and [[Cuisine of Armenia]] should be deleted for the same reasons as [[Cuisine of Mexico]]. If you want some more information on Cookbook redirects, please feel free to take a look at [[Cookbook:Policy]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:17, 8 May 2025 (UTC) ::: All right, thank you for the information. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:23, 8 May 2025 (UTC) == Pending edit == Hey, sorry to be messaging you directly here, but I seem to not have permission to edit the requests pages and IRC seems to be inactive as well. Could you approve my proposed change to [[Chess Opening Theory/1. e4/1...e5/2. f4/2...exf4]]? [[User:Dayshade|Dayshade]] ([[User talk:Dayshade|discuss]] • [[Special:Contributions/Dayshade|contribs]]) 15:16, 25 July 2025 (UTC) : Hello, [[User:Dayshade|Dayshade]]. I just marked your edit to the Chess Opening Theory page as reviewed. Thank you for the clarification. <span style="font-family:Verdana">[[User:Codename Noreste|<span style="color:#0024FF">'''''Codename Noreste'''''</span>]] ([[User talk:Codename Noreste|<span style="color:#A1000E">talk</span>]])</span> 15:44, 25 July 2025 (UTC) == correctly? == Did I [https://en.wikibooks.org/wiki/Wikibooks:Requests_for_permissions nominate] myself correctly? [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 19:42, 9 October 2025 (UTC) :Leaderboard granted you the importer permission indefinitely, as you have imported pages before using your temporary administrator status. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|d]] • [[Special:Contributions/Codename Noreste|c]]) 17:25, 12 October 2025 (UTC) ::That's great to know! [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 03:16, 16 October 2025 (UTC) :::No problem. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:35, 16 October 2025 (UTC) == ~2025 accounts == I'm seeing several accounts that start with "~2025" over here and on Simple English Wikipedia, and there's probably other places too. What are these accounts, bots? [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 03:16, 16 October 2025 (UTC) :[[User:2005-Fan|2005-Fan]], please read [[:mw:Help:Temporary accounts|Help:Temporary accounts]] on MediaWiki. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:35, 16 October 2025 (UTC) == Please no more LTA == Please let me edit Unicode again since I didn't add LTA stuff. [[Special:Contributions/&#126;2025-29764-49|&#126;2025-29764-49]] ([[User talk:&#126;2025-29764-49|talk]]) 23:52, 22 October 2025 (UTC) : You can talk to Kittycataclysm about this. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:25, 23 October 2025 (UTC) == [[:Template:PD-self]] == line 3, remove leading <nowiki>''</nowiki>? I can't do this directly. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 11:11, 28 October 2025 (UTC) Also appreciated if you could look through: https://en.wikibooks.org/wiki/Special:LintErrors/missing-end-tag?wpNamespaceRestrictions=&titlecategorysearch=&exactmatch=1&tag=all&template=with Thanks :). [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 11:11, 28 October 2025 (UTC) : Also [[:Template:PD-user]] [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 11:12, 28 October 2025 (UTC) :: [[User:ShakespeareFan00|ShakespeareFan00]], I've removed those leading symbols. Given that you are dealing with those lint errors and some of them are in fully protected pages, I would suggest you should run for (either temporary or permanent) adminship with your stated reasoning (including for cleaning up these lint errors) on [[Wikibooks:Requests for permissions]]. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 12:40, 28 October 2025 (UTC) :::Will consider it, At least some of the remainder are 'interface' (e.g. [[MediaWiki:Explainconflict&action=edit&lintid=984488]]) and I wouldn't be granted interface admin to edit those. <!-- Template:Unsigned --><small class="autosigned">—&nbsp;Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00#top|talk]] • [[Special:Contributions/ShakespeareFan00|contribs]]) </small> 12:58, 28 October 2025 (UTC) : @[[User:ShakespeareFan00|ShakespeareFan00]]: [[MediaWiki:Explainconflict]] can only be edited by administrators and global interface editors (they have <code>editinterface</code>), and I don't see any non-admin interface administrators on this project. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 12:57, 28 October 2025 (UTC) : [[Template:File link]] Module in template space? [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 13:40, 28 October 2025 (UTC) :: There was already a module, [[Module:File link]], so I've replaced the content of that template. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 13:57, 28 October 2025 (UTC) == [[:Wikibooks:AutoWikiBrowser/CheckPageJSON]] == This should be admin only, and I would like to request AWB access for future lint fixes which can be semi automated. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 14:59, 28 October 2025 (UTC) : [[User:ShakespeareFan00|ShakespeareFan00]], I've added you to the list, but I am hesitant to fully protect the check page at the moment. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:08, 28 October 2025 (UTC) == [[:Template:Effective_protection_level]] == Module in template namespace? (Aside: Do we have {{tl|edit protected}}[[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 16:42, 28 October 2025 (UTC) : I've deleted that template, and yes we have the edit protected template. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 17:56, 28 October 2025 (UTC) == [[Chess_Opening_Theory/1._e4/1...d5/2._Nf3/2...dxe4]] == What broke? The template {{tlx|chess/not|only}} throws a lint, and just REFUSES to format properly where it's used here. Suggestions? [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 00:31, 29 October 2025 (UTC) == [[:User talk:Adrignola/2009/06]] == The lint is a simple unclosed <nowiki><tt></nowiki>. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 09:24, 29 October 2025 (UTC) Should be easily found with somwthing like the linthint script. I am starting to hit the limits of what I can usefully repair. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 09:24, 29 October 2025 (UTC) : You should apply for adminship. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 14:06, 29 October 2025 (UTC) == [[:MediaWiki:Common.js/w/Wikibooks:Dialog]] == This is a misdetection by the Linter, The file type is clearly javascript, but a linter for wikitext is being applied? Also: * [[:MediaWiki:Common.js/w/Wikibooks:Dialog/diagnostic panel]] * [[:MediaWiki:Common.js/w/Wikibooks:Dialog/do]] * [[MediaWiki:Common.js/w/Wikibooks:Dialog/echo]] * [[MediaWiki:Dialog/receive]] [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 11:07, 29 October 2025 (UTC) : Now {{done|converted}} to JavaScript. '''[[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 14:04, 29 October 2025 (UTC) == Thank you! == Just wanted to stop by and say thank you for all the work you've been putting into the edit filter lately! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:27, 11 November 2025 (UTC) : I appreciate your response. Wikibooks needed an administrator who has solid expertise in edit filters and regex, so I have decided to lend a helping hand in that field. I have also been overhauling and updating the modules and templates. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 14:58, 11 November 2025 (UTC) == Removed user right == I received a notification that I'm no longer a member of autoreviewed users. Would you explain why? I have gaps in my editing here, but when I do edit, it tends to be significant things on one Wikibook: [[OpenSCAD User Manual]] (see my contribution history). If it matters, I am also an administrator on the English Wikipedia. [[User:Anachronist|Anachronist]] ([[User talk:Anachronist|discuss]] • [[Special:Contributions/Anachronist|contribs]]) 03:31, 13 November 2025 (UTC) : [[User:Anachronist|Anachronist]], the autoreviewed user permission is a subset of reviewer permissions, and per [[Wikibooks:Reviewers]], the autoreviewed user permission can be removed from a user when they also have reviewer permissions. I am also doing this per [[User talk:Kittycataclysm#Administrator and reviewer user right combinations are not needed anymore]]. Thank you. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:34, 13 November 2025 (UTC) ::Thanks, I appreciate the explanation. [[User:Anachronist|Anachronist]] ([[User talk:Anachronist|discuss]] • [[Special:Contributions/Anachronist|contribs]]) 04:32, 13 November 2025 (UTC) == Thank you == for having taken the time to report [[phab:T409743]]. It is greatly appreciated :) &zwj;—&zwj;[[user:a smart kitten|a&nbsp;smart kitten]] ([[user talk:a smart kitten|discuss]] • [[special:contribs/a smart kitten|contribs]]) 06:01, 13 November 2025 (UTC) : No problemo. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:32, 13 November 2025 (UTC) == Notice of expiration of your interface-admin right == <div dir="ltr">Hi, as part of [[:m:Special:MyLanguage/Global reminder bot|Global reminder bot]], this is an automated reminder to let you know that your permission "interface-admin" (Interface administrators) will expire on 2026-01-05 23:59:00. Please renew this right if you would like to continue using it. <i>In other languages: [[:m:Special:MyLanguage/Global reminder bot/Messages/default|click here]]</i> [[User:Leaderbot|Leaderbot]] ([[User talk:Leaderbot|discuss]] • [[Special:Contributions/Leaderbot|contribs]]) 19:41, 30 December 2025 (UTC)</div> == Notice of expiration of your sysop right == <div dir="ltr">Hi, as part of [[:m:Special:MyLanguage/Global reminder bot|Global reminder bot]], this is an automated reminder to let you know that your permission "sysop" (Administrators) will expire on 2026-01-05 23:59:00. Please renew this right if you would like to continue using it. <i>In other languages: [[:m:Special:MyLanguage/Global reminder bot/Messages/default|click here]]</i> [[User:Leaderbot|Leaderbot]] ([[User talk:Leaderbot|discuss]] • [[Special:Contributions/Leaderbot|contribs]]) 19:41, 30 December 2025 (UTC)</div> == Regarding your mass deletions == Firstly, I have reversed all your deletions of [[Chess Opening Theory]] redirects. Whenever you see a broken redirect, ''please always open the page it targeted''. Here, when you moved a bunch of pages en masse after a request at [[WB:AA]], you left behind a bunch of broken redirects. I saw these redirects in [[:CAT:CSD]] earlier, and left them alone since I figured you'd connect those redirects to that request, and thus discover [[Special:GoToComment/c-Atiedebee-20251231082700-Codename_Noreste-20251229012000|this comment]], after which you would move the pages again and retarget. However, you deleted them. I have undeleted them. Secondly, I'd like to ask why exactly you deleted all those subpages of [[Australian Curriculum Mathematics]], which have existed for over a decade in many instances? I feel like this should have been taken to RfD instead. I have no problems with your other deletions. Thank you for your time. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 22:30, 31 December 2025 (UTC) : I was handling the speedy deletion backlog when unfortunately, I did not realize the chess redirects were supposed to be corrected. Second, @[[User:Kittycataclysm|Kittycataclysm]] marked the Australian Curriculum Mathematics subpages for speedy deletion, because the subpages were considered abandoned material (but I agree that this should have been taken to RFD). However, we should probably wait for their opinion regarding the ACM subpages. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 22:51, 31 December 2025 (UTC) ::@[[User:JJPMaster|JJPMaster]] @[[User:Codename Noreste|Codename Noreste]] Chiming in here! I nominated the [[Australian Curriculum Mathematics|ACM]] pages for speedy deletion because it looked to me like they met the [[WB:SPEEDY]] criteria of "pages with no meaningful content" and the instruction to "delete stubs that are too narrowly defined or do not have a decent definition of what they are about" (see, for example, [[Australian Curriculum Mathematics/Grade 10A/Chance]]). I flagged them for another admin to delete because I sometimes like to get a second pair of eyes on a page I think should be speedily deleted, but I didn't think they were sufficiently developed to bring to RFD. Does this clarify things? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:50, 1 January 2026 (UTC) == Font wrapping links? == Do you know any bot writers? The update pattern is reasonably straightforward (check my contributions), and it would seem sensible for this to be done as a bulk effort. This would free up time to work on items that need a more human nuance... There are automated repair bots on Wikipedia that could do this. :) [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 20:21, 17 March 2026 (UTC) :Forwarding this matter to @[[User:JJPMaster|JJPMaster]]. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 13:51, 18 March 2026 (UTC) == Unclosed table == [[Control Systems/Print version]] However none of the input pages seem to show up as a having a missing table? Suggestions? It's not really feasible to build the print version up from scratch in a sandbox as I do not know how it gets built.. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 20:00, 28 March 2026 (UTC) : I think many of the chapters are transcluded on that printable page, so you might need to find out which chapter has lint errors. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:04, 11 April 2026 (UTC) == Future of game coverage on Wikimedia wikis == Hi, what's the future of video game coverage on Wikimedia wikis? I'm a major proponent of in-depth gaming coverage, even though I'm aware places like the English Wikipedia don't easy allow for its inclusion. I've also opened a question if Simple English Wikipedia can [https://simple.wikipedia.org/wiki/Wikipedia_talk:Notability#Scope loosen its scope], partly to help with the accessibility of niche topics that people who may not understand English well can read that may not be presentable as such elsewhere. Or is Wikibooks the only true Wikimedia project for in-depth game coverage, just through a textbook or instruction manual lens? [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 00:20, 17 April 2026 (UTC) : I'm afraid that I may not able to answer that, apart that you comply with Wikibooks' scope. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:02, 27 April 2026 (UTC) == Deletion of Subpage == Hello Codename Noreste You have recently deleted a subpage in "my" Wikibook for Publications: https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia This was a page for a variety of publications which were deleted summarily about 6 months ago at a time when personal matters intervened and I was unable to respond adequately. Would you please undelete this subpage as I will shortly be seeking to have most of the publications restored (they are in the public domain). Thanks Sam Dellit [[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 22:46, 26 April 2026 (UTC) : Hi, which subpage would you want to be restored? Some context: @[[User:ShakespeareFan00|ShakespeareFan00]] tagged these as copyright violations which I couldn’t tell if they are, and they said they were. I deleted them, until you notified me here. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 22:51, 26 April 2026 (UTC) ::Hello Codename Noreste ::The primary page is here: ::https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Publications ::If you could undelete the subpages also, that would be great (sorry, I have no record of what they were). ::Then I could start including proof of public domain for as many as possible (I am now again active on Wikibooks). ::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 22:57, 26 April 2026 (UTC) ::: @[[User:Samuel.dellit|Samuel.dellit]] They are now undeleted, so you can make the necessary changes. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:02, 27 April 2026 (UTC) ::::Thank you, I can now see: ::::https://en.wikibooks.org/w/index.php?title=History_of_wireless_telegraphy_and_broadcasting_in_Australia/Topical/Publications ::::But I still can't see any of the subpages ::::[[User:Samuel.dellit|Samuel.dellit]] ([[User talk:Samuel.dellit|discuss]] • [[Special:Contributions/Samuel.dellit|contribs]]) 03:03, 27 April 2026 (UTC) ::::: Try restoring [[Special:Permalink/4019477|this version]], thank you. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:10, 27 April 2026 (UTC) :{{ping|Samuel.dellit}} Reverted the tags, you should see the articles, I suggest you look into the authors of articles of transcribed articles and confirm they ALL died before 1946 ( Australia at the date of the Issues concerned was 50 pma, making it (disapointinhly that anything still in copyright in Australia in 1996, got a full US term due to URAA, NOT a 28 year and renewal as might be expected.). If you don't provide further biographical detail for the authors, these publication transcriptions will be considered copyvio, and retagged. [[User:ShakespeareFan00|ShakespeareFan00]] ([[User talk:ShakespeareFan00|discuss]] • [[Special:Contributions/ShakespeareFan00|contribs]]) 11:01, 27 April 2026 (UTC) == You may be an eligible candidate for the U4C election == <div lang="en" dir="ltr" class="mw-content-ltr"> Greetings, The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years. This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required. The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run. In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) </div> <!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&oldid=30471751 --> == Markdown == Can you clarify why you deleted [[Markdown]]? The deletion summary says "Mass deletion of abandoned/orphaned/out of scope pages with minimal or no content. (sysop action)". It did not seem to fail a RFD and from what I remeber, it was a short instructional page I made on Markdown. The page is in [https://web.archive.org/web/20250427011600/https://en.wikibooks.org/wiki/Markdown Wayback Machine]. Actually, can you please undelete the page, send it to RFD if you are still convinced it should be deleted, and ping me? I think it is a neat little page providing minimum useful artifact and can be expanded later. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 08:53, 5 May 2026 (UTC) : Looking at the deleted edits from that page, [[User:Kittycataclysm|Kittycataclysm]] (whom I pinged for second opinion) marked it for speedy deletion as it was considered {{tq|abandoned with little to no meaningful content}}, but you may file a request at [[Wikibooks:Requests for undeletion]] citing your reasons why that page should be undeleted and kept when you plan to update it. [[User:Codename Noreste|<span style="color:#0024FF">Codename Noreste</span>]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 14:55, 5 May 2026 (UTC) :: I opened [[Wikibooks:Requests for undeletion#Markdown]]. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 15:38, 5 May 2026 (UTC) == [[Wikibooks:Requests for deletion/Character Encodings]] == Note that some subpages are still around at [[:Category:Book:Character Encodings]]. However, I would also disagree with the deletion since the code pages provide useful information that is not found elsewhere. [[User:1234qwer1234qwer4|𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰]] ([[User talk:1234qwer1234qwer4|𝗍𝗮𝘭𝙠]]) 22:08, 24 September 2026 (UTC) : I want to apologize for being super busy with this, because of my real life commitments. I will get to undeleting the remaining pages (including the main one). [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 14:31, 2 October 2026 (UTC) == Removal of rights of inactive patrollers == Hi, I started the script to remove the rights, sorry it took me a bit. I had to deal with an urgent issue. it's running as bot so it's not flooding RC. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 21:41, 15 October 2026 (UTC) : Thanks. Once you are done, you can request a steward to remove your ''temporary'' administrator and bot rights. : While not related, one option is that you can request system administrator rights–after you add the request to SRGP explaining your use case, and then send a detailed use case to Wikimedia T&S by email. : Once again, thank you for operating the behind the scenes on removing FlaggedRevs for good, as you had me on charge with the necessary patches. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 21:50, 15 October 2026 (UTC) ::yeah I know how to get rid of it, this is not my first time :D A couple months ago I needed similar rights on cywiki. I do this kind of thing once every couple of months. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 22:09, 15 October 2026 (UTC) ::: Wait, something weird happened: [[Special:Redirect/logid/5414075]]. No former autoreviewed user became autopatrolled. :( [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 23:38, 15 October 2026 (UTC) ::::(please ping me). I ran this: " mwscript-k8s --follow -- migrateUserGroup --wiki=enwikibooks autoreview autopatrol". Maybe the name was not correct? Can you double check. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 15:40, 16 October 2026 (UTC) ::::: @[[User:Ladsgroup|Ladsgroup]] it removed autopatrol (not patroller), but we would have to find out users with the autopatrol user group (formerly autoreviewed user) and migrate them to the autopatroller user group. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 21:01, 16 October 2026 (UTC) : Pinging once again to [[User:Ladsgroup|Ladsgroup]]: <span class="plainlinks">[https://en.wikibooks.org/wiki/Special:ListUsers?username=&group=autopatrol&wpsubmit=&wpFormIdentifier=mw-listusers-form&limit=50 This list of users who were previously autoreviewed]</span> should be migrated to the autopatroller user group. Thank you. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 13:40, 17 October 2026 (UTC) :: Also, the removal of that permission after being inactive for more than 2 years (as we discussed on IRC) also applies (in addition to former reviewer). [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 13:49, 17 October 2026 (UTC) ::I'm sick and can't sit behind pc. Give me a day or two [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 17:21, 17 October 2026 (UTC) ::: No worries, there is no rush here. :) [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 18:35, 17 October 2026 (UTC) ::::So the problem was that they are migrated to "autopatrol" group while the name of the group is "autopatrollED" (also "autopatroller" that you mentioned is wrong). I run the script to migrate members of "autopatrol" to "autopatrolled" [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 10:31, 19 October 2026 (UTC) :::::okay, now they have been migrated. I can take a look at the list of inactive users later today. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 11:07, 19 October 2026 (UTC) ::::::This is the list of users who haven't made an edit or log action since 2024: [[phab:P96896]]. Feel free to massive revoke the rights. 60 should be easy. [[User:Ladsgroup|Ladsgroup]] ([[User talk:Ladsgroup|discuss]] • [[Special:Contributions/Ladsgroup|contribs]]) 16:31, 20 October 2026 (UTC) almskr8qnqq059odqqv8s12q311vcmr General Literary Chinese from Scratch 0 481710 4679909 4677637 2026-11-04T07:25:03Z Shira the Mogul 3560559 /* Unit 1: Basic Skills */ 4679909 wikitext text/x-wiki __notoc__ Welcome to the Wikibook for Literary Chinese (Known as 漢文 "Han Language" in East Asia or 文言 "Literary Language" in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. However, as Zhou-Qin era texts served as the main body from which individuals learned, they are employed here as and when they are considered necessary or otherwise useful. It does so through a "buffet" approach, showering you, the reader, with an ocean of texts of myriad genre. ==Table of Contents== === Front matter === * [[/Introduction/]] * [[/Appendices/]] === Useful resources === These are quick grab-bags that can be useful for vocabulary-building. * [[/Antonym List/]] <!--- 文/武,大/小,厚/薄,橫/縱...---> * [[/Collocation Groups/]] <!--- e.g. 四象,三靈…… ---> * [[/Colour Correspondence Table/]] <!--- Colour characters with hex colorations in cells ---> * [[/Pronoun Table/]] * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] <!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---> * [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms] <!--- this will be translated eventually, but right now it's bad to just leave this here. ---> * [https://docs.google.com/document/d/1A0hl5nDb653yS42i5xRBoIBEF8bc7jfR_UQcCE121-o/edit?usp=sharing General Reading List] === Useful primers === Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. * [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. * 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. ** 三字經(太平天國版)- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. * 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. * 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. * 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece. ===Unit 0: The Han script=== This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. By the end of this unit, students will: * Recognise around 50 characters. * Understand how characters are composed and how this gives them meaning. * Have a basic idea of how to handwrite and/or type characters using the Cangjie Input Method. * Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of "is", 有...) Lessons: # [[/An Introduction to the Han Script/]] # [[/People, Big and Small/]] # [[/How do we write Chinese?/]] # [[/What are Chinese characters, anyway?/]] # [[/The Sun, the Moon, and the Five Elements/]] # [[/Getting Familiar with Body Parts/]] # [[/Using Numbers and Using Weapons/]] <!--- 竹戈十大中一弓廿卜---> # [[/Tilling the Fields with 有/]] <!--- 山田 ---> # [[/How Characters are Made/|How Characters are Made with Kiyohara no Sanemoto]] # [[/Cangjie Created Characters/]] <!--- Get people to use Cangjie ---> # [[/The Kangxi Radical System/]] <!--- Introduce some monoradical texts to train recognition. ---> ===Unit 1: Basic Skills=== This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. Before starting this unit, students should: * Recognise around ~30 characters. * Can use Cangjie input. * Have given Unit 0 a cursory glance. <br> By the end of this unit, students will: * Recognise around ~100 characters. * Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date. * Intuit the basic topic -> comment idea behind Literary Chinese. "This, it is..." * Understand basic function words such as 也, 而, 有, and 謂. * Have developed some proficiency with dictionary apps such as Pleco and Yomitan to be able to look up terms without relying on glosses. Lessons: # [[/The All-Purpose 也/]] # [[/An Introduction to Chinese Numbers/]] # [[/One, Two, Left, and Right with Gongsun Long/]] # [[/The Heavenly Stems/]] # [[/Tell the Time with Earthly Branches/]] # [[/How Much Time, Exactly?/]] # [[/Lunar Dates with the Spring and Autumn Annals/]] # [[/Scanning for Major Events in Historical Annals/]] # [[/Dinner with the Daimyo/]] # [[/In Discourse with Jibong/]] # [[/How do we Write Height and Weight?/]] # [[/Eating like a Zhou Aristocrat/]] <!--- Some cool stuff I saw someone studying from https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98# https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98 Could be used for period focus ---> ===Unit 2: Myths and Legends of East Asia=== In this unit, you will be studying some of the ancient myths and legends of East Asia, along with one of your first literary genres: Zhiguai 志怪. These texts happen to be quite easy to read and utilise skills you have already learned. By the end of this Unit, students will: * Recognise around 120 more characters. * Be able to use function words such as 在, 無, 不, 焉, and 于/於. * Understand 里 as a measure of distance. * Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage. * (Chinese speakers) Be able to differentiate 于 and 於, and understand the "interest(ed) in" meaning of 好 in most circumstances. <!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---> # [[/Exploring the World of Mountains and Seas/]]<!-- Structure: 出焉 --> # [[/Oh, the Qilin!/]] # [[/The Poison of Zhen/]] <!--- referenced a lot in histories 《説文解字》鴆:毒鳥也。从鳥冘聲。一名運日。 《山海經·中山經》 又東六十里,曰瑤碧之山,其木多梓柟,其陰多青䨼,其陽多白金。有鳥焉,其狀如雉,恒食蜚,名曰鴆。 史記 魯 662 三十二莊公弟叔牙鴆死。慶父弒子般。季友奔陳,立湣公。 《後漢書·紀·孝順孝沖孝質帝紀》 閏月甲申,大將軍梁冀潛行鴆弒,帝崩于玉堂前殿,年九歲。 ---> # [[/Ultimate Justice with Xiezhi/]] <!--- the yellow emperor met one, gao yao also used one ---> # [[/The Virtue of the Fenghuang/]] <!--- The Shanhaijing has a great line which we can link with the Daimyo exercise and promote scanning with 《山海經·南山經》又東五百里,曰丹穴之山,其上多金玉。丹水出焉,而南流注于渤海。有鳥焉,其狀如雞,五采而文,名曰鳳皇,首文曰德,翼文曰義,背文曰禮,膺文曰仁,腹文曰信。是鳥也,飲食自然,自歌自舞,見則天下安寧。 ---> # [[/The Entrapment of Hua Po/]] # [[/Nüwa Created the World/]] ===Unit 3: Confucianism and the World=== This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states! Lessons: # [[/A Brief Overview of Confucianism/]] # [[/Teaching the Annals in Qi/]] <!-- Gongyang Gao's commentary --> # [[/Is a White Horse a Horse?/]]<!-- Teach negation with 非 in 公孙龍子 and compare with 不 --> # [[/The Three Character Classic/]] # [[/Expressing Filial Conduct with Confucius and Hara Saihin/]] <!-- 次韻杏坪先生 父執有君孤不孤 相依遍接搢紳徒 区区自抱地方寸 杳杳重遊天一隅 羇雁飛鳴迷汝國 家人思夢入江都 如教志業青年遂 世上寧無逐臭夫 --> # [[/Confucianism and the Environment with Sai On/]]<!-- 木假山記 --> # [[/In Debate with Mencius/]] ===Unit 4: Women's Writing=== In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here! # [[/An Unmarried Life with Heo Nansŏrhŏn/]] <!--- 貧女吟 豈是乏容色。工鍼復工織。 少小長寒門。良媒不相識。 夜久織未休。戛戛鳴寒機。 機中一匹練。終作阿誰衣。 手把金翦刀。夜寒十指直。 爲人作嫁衣。年年還獨宿。 ---> # [[/Responding to Lord Trần with Hồ Xuân Hương/]] <!--- Responding to 陳光靜 Trần Quang Tĩnh 《和陳侯》 愧無才調使人驚,十載風塵貫耳鈴。 已是臨枰知敵手,莫須敲月苦殫精。 為輪為彈隨遭遇,誰鳳誰鶯任賦生。 造物於人何苟惜,明珠休向暗中呈。 莫須 is an important structure to teach here. ---> # [[/Gaze into the Autumn Night with Taisei Shōan/]] <!--- 秋夜偶成·大成聖安 長天浮爽気,月色興無窮 群犬吠山径,百蟲啼野風 悲秋秋夜永,感古古今同 自是孤窓下,凄然万慮空 ---> # [[/Visiting a Temple with Yu Xuanji/]] <!--- 遊崇真觀南樓覩新及第題名處 雲峰滿目放春晴,歷歷銀鈎指下生。 自恨羅衣掩詩句,擧頭空羨榜中名。 ---> # [[/Remonstrance with Dasese/]] <!--- https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C 諷諫歌·大瑟瑟 勿嗟塞上兮暗紅塵。 勿傷多難兮畏夷人。 不如塞奸邪之路兮選取賢臣。 直須臥薪嚐膽兮激壯士之捐身。 可以朝清漠北兮夕枕燕雲。 Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. ---> # [[/The Love Songs of the Odes/]] <!--- 褰裳 子惠思我,褰裳涉溱。子不我思,豈無他人?狂童之狂也且! 子惠思我,褰裳涉洧。子不我思,豈無他士?狂童之狂也且! 柏舟 彼柏舟,在彼中河,髧彼兩髦,實維我儀,之死矢靡它,母也天只,不諒人只。 汎彼柏舟,在彼河側,髧彼兩髦,實維我特,之死矢靡慝,母也天只,不諒人只。 行露 厭浥行露,豈不夙夜,謂行多露。 誰謂雀無角?何以穿我屋?誰謂女無家?何以速我獄?雖速我獄,室家不足。 誰謂鼠無牙?何以穿我墉?誰謂女無家?何以速我訟?雖速我訟,亦不女從。 ---> # [[/Rules for Women with Ban Zhao/]] <!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---> # [[/The Tragedy of Cai Wenji/]] <!--- 悲憤詩 〔兩漢〕蔡文姬 漢季失權柄,董卓亂天常。 志欲圖篡弒,先害諸賢良。 逼迫遷舊邦,擁主以自強。 海內興義師,欲共討不祥。 卓眾來東下,金甲耀日光。 平土人脆弱,來兵皆胡羌。 獵野圍城邑,所向悉破亡。 斬截無孑遺,屍骸相撐拒。 馬邊懸男頭,馬後載婦女。 長驅西入關,迥路險且阻。 還顧邈冥冥,肝脾為爛腐。 所略有萬計,不得令屯聚。 或有骨肉俱,欲言不敢語。 失意幾微間,輒言斃降虜。 要當以亭刃,我曹不活汝。 豈復惜性命,不堪其詈罵。 或便加棰杖,毒痛參並下。 旦則號泣行,夜則悲吟坐。 欲死不能得,欲生無一可。 彼蒼者何辜,乃遭此厄禍。 邊荒與華異,人俗少義理。 處所多霜雪,胡風春夏起。 翩翩吹我衣,肅肅入我耳。 感時念父母,哀嘆無窮已。 有客從外來,聞之常歡喜。 迎問其消息,輒復非鄉里。 邂逅徼時願,骨肉來迎己。 己得自解免,當復棄兒子。 天屬綴人心,念別無會期。 存亡永乖隔,不忍與之辭。 兒前抱我頸,問母欲何之。 人言母當去,豈復有還時。 阿母常仁惻,今何更不慈。 我尚未成人,奈何不顧思。 見此崩五內,恍惚生狂痴。 號泣手撫摩,當發復回疑。 兼有同時輩,相送告離別。 慕我獨得歸,哀叫聲摧裂。 馬為立踟躕,車為不轉轍。 觀者皆噓唏,行路亦嗚咽。 去去割情戀,遄征日遐邁。 悠悠三千里,何時復交會。 念我出腹子,匈臆為摧敗。 既至家人盡,又復無中外。 城廓為山林,庭宇生荊艾。 白骨不知誰,縱橫莫覆蓋。 出門無人聲,豺狼號且吠。 煢煢對孤景,怛吒糜肝肺。 登高遠眺望,魂神忽飛逝。 奄若壽命盡,旁人相寬大。 為復強視息,雖生何聊賴。 託命於新人,竭心自勖勵。 流離成鄙賤,常恐復捐廢。 人生幾何時,懷憂終年歲。 ---> ===Unit 5: Food from Across the Ages=== # [[/A Simple, Rich Fry/]] <!--- 《禮記 內則》淳熬:煎醢,加于陸稻上,沃之以膏曰淳熬。淳毋煎醢,加于黍食上,沃之以膏曰淳毋。---> # [[/Song Cuisine with Chen Dasou and Lin Hong/]] <!--- 陳達叟 本心齋疏食譜 https://zh.wikisource.org/zh-hant/%E6%9C%AC%E5%BF%83%E6%96%8B%E7%96%8F%E9%A3%9F%E8%B0%B1 ---> <!--- 山家清供 https://zh.wikisource.org/wiki/%E5%B1%B1%E5%AE%B6%E6%B8%85%E4%BE%9B ---> # [[/Yuan Cuisine with Ni Zan/]] <!--- https://ctext.org/wiki.pl?chapter=318337&if=en 《雲林堂飲食制度集》倪瓚 one of the Four Masters, also a painter ---> # [[/A Feast with Yuan Mei/]] <!--- 袁枚 隨園食單 https://ctext.org/wiki.pl?if=gb&res=344157 ---> # [[/Remembering the Food of Joseon with Hŏ Kyun/]] <!--- https://rmda.kulib.kyoto-u.ac.jp/item/rb00023424?page=3p 許筠 屠門大嚼 ---> ===Unit 6: An Overview of Sinitic Poetry=== This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole! <!--- Summary of the above part about 于 and 於 for other editors: 于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their "merging" through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000); * 于 - This can mean "to go" or "to/at". 黃鳥于飛 "The yellow birds go flying". Must be post-verbal. It can also appear in 至于. * 於 - This is an all-purpose locative preposition - from "on/at/in" to "from" or even "than" (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏). ---> Lessons: # [[/Across the Rivers with Emperor Puliuru Guang/]] <!--- Illustrate ping-ze ---> # [[/To Study the Odes/]] # [[/A Detour into Orthodox Ping-Ze/]] <!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄,歉仄,逼仄 as it's often difficult to immediately use ---> # [[/The Restraint of Du Fu/]] # [[/The Longing of Li Bai/]] # [[/The Environment with Bukha Timur/]] # [[/Pillow Talk with Guan Yunshi/]] <!--- 紅繡鞋·貫雲石 挨著靠著雲窗同坐,偎著抱著月枕雙歌,聽著數著愁著怕著早四更過。四更過情未足,情未足夜如梭。天哪,更閏一更兒妨甚么! Uyghur author! ---> # [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]] <!-- 元火·吳真流 木中元有火,元火復還生。 若為木無火,鉆燧何有萌。--> <!-- 杜鵑·大成聖安 夢覚孤床静 杜鵑帯雨飛 一声来近枕 何者不沾衣 --> # [[/Odes with Mō Taiei and Zheng Chengxun/]] <!-- 詠松·毛泰永 植體宜千仞,垂陰動百尋。 李膺真烈烈,和嶠自森森。 桃李何堪較,雪霜安得侵。 萬年身不老,種子又成林。 AKA Inoha Seiki 伊野波 盛紀 --> <!-- 詠班蘭·鄭成勛 南國多芳草,班蘭最有名。 深根將綠茁,長葉亦叢生。 取味迎賓合,入厨任水烹。 可憐經一用,擲棄不留情。 鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --> # [[/A Golden Cup and the Fall of a Dynasty with Yan Fu/]] # [[/On a Journey with Sadula/]] <!--- No lesson entry: 朝中措·襄陽古道灞陵橋 襄陽古道灞陵橋,詩興與秋高。 千古風流人物,一時多少雄豪。 霜清玉塞,雲飛隴首,風落江皋。 夢到鳳凰台上,山圍故國周遭。 北郊晚步 陂水荷凋晚,茅檐燕去涼。 遠林明落景,平麓淡秋光。 群牧歸村巷,孤禽立野航。 自諳閑散樂,園圃意尤長。 Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later. ---> ===Unit 7: Nation Focus - Japan=== # [[/An Introduction to Kanbun Kundoku/]] # [[/The Inariyama Sword/]] <!--- short and sweet! ---> # [[/Entering Japan with Takeda Shingen/]] # [[/The Oldest Inscription in Japan/]] <!--- 宇治橋断碑 ---> # [[/The End of a Rebellion/]] # [[/The Diary of Fujiwara no Teika/]] <!--- 明月記 ---> # [[/Reading the History of Japan with Prince Toneri/]] <!--- 日本書記, etc. ---> # [[/A Biographical Painting of Toyotomi Hideyoshi/]] <!--- This is on Fanya Hanwen Corpus ---> <!--- # [[/Occupying Taiwan/]] ---> <!--- I have some colonial literature on me that can be used here. ---> ===Unit 8: Shinto, the Nature Religion=== # [[/Shinto, Questions and Answers/]] <!--- https://wikisource.org/wiki/%E7%9C%9E%E9%81%93%E5%95%8F%E5%B0%8D 眞道問對 本田親徳 really good way of operationalising 乎 and much of the early grammar. 問 天帝無始無終乎。 對 天帝無始無終也。 旣以無始無終之力 與無始無終之體 造無始無終之萬物。 其功亦無始無終也。 問 天地大原在道乎。 對 天地大原實在道。 鬼神依道而立。 人民依道而活。 萬物依道而息。 This is great! ---> # [[/The Way of Shinto with Honda Chikaatsu/]] <!--- https://wikisource.org/wiki/%E9%81%93%E4%B9%8B%E5%A4%A7%E5%8E%9F 本田親徳 道之大原 ---> <!--- 滄海窓問答 鎮魂帰神の極意 新論 by 会沢正志斎 https://dl.ndl.go.jp/pid/2610897 大和神学 神道大意 三社託宣 神道五部書 古語拾遺 日本書紀 ---> ===Unit 9: Nation Focus - Korea=== # [[/Feigned Surrender with Ŭlchi Mundŏk/]] <!--- 乙支文德漢詩 ---> # [[/A fu with Yi Kyubo/]] # [[/An Elegy to the Empress with Choe Ja/]] <!--- Choe Ja 元德大后輓詞·崔滋(최자) 乾極曾客配,坤儀正體元。 枕前朝聖主,帳底見曾孫。 陰慘俄沉月,屋悲便沒軒。 三韓千古淚,七十九年恩。 ---> # [[/Language Reform with Sejong the Great/]] <!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---> # [[/Fall Off Your Horse!/]] <!--- a famous record from 朝鮮王朝實錄 ---> # [[/The Diary of Yi Sun-Sin/]] <!--- 亂中日記 ---> # [[/Tales from Mount Kumo/]] <!--- 金鰲新話 ---> # [[/Pak Chiwŏn Tours the Qing/]] <!--- 熱河日記 ---> # [[/Korea's Three Kingdoms/]] <!--- 三國史記 for sure! ---> # [[/Hwang Yun-seok's Essays/]] <!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---> ===Unit 10: Christian Literature=== # [[/A Different Three Character Classic with Hong Xiuquan/]] # [[/Friar Juan Cobo's Veritable Record/]] <!--- One of few texts from the Philippines that I have ever found! https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 ---> # [[/The Delegate's Edition/]] # [[/Nestorian Steles during the Tang/]] <!--- 大秦景教宣元至本經經幢 and 景教碑 ---> # [[/Hong Xiuquan's Bible/]] <!--- https://bible.fhl.net/ob/nob.html?book=407 ---> <!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---> ===Unit 11: An Introduction to Daoism=== <!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---> # [[/Laozi Explains the Dao/]] # [[/Qingtan with Xie Daoyun/]] # [[/The Doubting Neighbour/]] # [[/Kuafu Chases the Sun/]] # [[/The Frog in a Well/]] # [[/Wu wei with King Hui of Liang/]] # [[/The Old Man that Moves the Mountains/]] # [[/Master Zhuang Dreams of Butterflies/]] # [[/Master Incapable and the Poisonous Bird/]] # [[/Transmitting the Dao with Yelü Chucai/]] <!---耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with. https://zh.wikisource.org/wiki/%E7%8E%84%E9%A2%A8%E6%85%B6%E6%9C%83%E9%8C%84 ---> # [[/The Indifferent Taoist/]] <!--- northern song https://zh.wikisource.org/wiki/%E7%8E%89%E6%AD%B7%E5%AF%B6%E9%88%94 ---> <!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---> ===Unit 12: Nation Focus - Ryukyu Kingdom=== # [[/Historical Annals with Sai On/]] <!--- Kyuko is an easy cop ---> # [[/The Enthronement of Shō Tei/]] # [[/The Twilight of Ryukyu with Shō Ten/]] # [[/A Trip to Ryukyu with Luo Sen/]] <!--- Pre-Capstone ---> <!--- 遐邇貫珍 1854-11 - 日本日記 羅森 https://archive.org/details/HEKC185411/page/n5/mode/1up A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者 不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 ---> <!--- 中山世鑑 and so on. Lots of poetry too. ---> ===Unit 13: Nation Focus - Singapore=== <!--- National Library of Singapore has a poetry series that's super good! ---> # [[/Three Nights in Penang with Gao Chao/]] ===Unit 14: Literary Chinese in Medicine=== <!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---> # [[/The Books of the Yellow Emperor/]] <!-- 黃帝内徑 ---> # [[/Deviant Qi with Zhang Congzheng/]] <!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---> # [[/Anatomy with Sugita Genpaku/]] <!--- 解体新書 ---> # [[/A Lost Wu Medical Text analysed in Japan/]] <!--- 難經古義 ---> ===Unit 15: People Focus - Zhuang peoples=== <!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&knowledgeId=84745463&_from_=&_fromV2_=&rtag= 《峤西诗钞》 is also a really good shout. Found here: https://ctext.org/wiki.pl?if=gb&res=215640&remap=gb ---> <!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---> # [[/Zhuang poetry with Li Bi/]] # [[/The Beauty of Wuyuan with Fang Ju/]] # [[/Disaster and Society with Wei Fenghua/]] # [[/Who Deserves a Biography?/]] <!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm 一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮(hé)《大塘谣》(《峤西诗钞》卷二)云: 去了休。去到大塘红蓼洲。红蓼生花,不结子。绿朴生花,毬见毬。 诗中所说“绿朴”,是壮族对柚子的惯称。“柚子”,壮语发音为“bug”。根据《古壮字字典》,其对应的古壮字为“朴(㭪)”。诗人将古壮字运用到汉文诗歌创作中,刻下了明清壮汉文化交相辉映的注脚。 This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---> ===Unit 16: People Focus - Tangut peoples=== <!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---> ===Unit 17: Literary Chinese in the Military=== <!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---> # [[/Fū! Rin! Ka! Zan!/]] # [[/A Bilingual Stele of the Khitans/]] # [[/Going to war with Boyan/]] <!--- Boyan's Poem from the 元史   伯顏,蒙古巴林部人。至元十一年拜中書左丞相,總兵伐宋。官至開府儀同三司,薨贈太師,封淮安王,諡忠武。   《玉堂嘉話》:初,宋未下時,江南謠云:「江南若破,白雁來過。」當時莫喻其意。及宋亡,蓋知指丞相巴延也。   過梅嶺岡留題 馬首經從庾嶺回 【 庾嶺回 七修類稿(乾隆刊本)卷四十六作「嶺島歸」。】 ,王師到處悉平夷。擔頭不帶江南物,只插梅花一兩枝。   《七修類藳》:伯顏下江南,過金陵梅嶺岡詩云云。所以著名,亦有是善。 ---> # [[/An Edict from the Xianbei/]] # [[/The Suppression of the Kingdom of Dongning/]] <!--- 台灣鄭氏始末 https://ctext.org/wiki.pl?if=en&chapter=139938 Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. ---> # [[/The Shunzhi Emperor vs Li Zicheng/]] # [[/The Art of War/]] ===Unit 18: Nation Focus - Vietnam=== # [[/Đỗ Pháp Thuận and the Southern Skies/]] # [[/Ancestor Veneration with the Descendants of Zhu Xi/]] <!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean somewhere in here ---> # [[/Resolving a Succession Crisis with Emperor Trần Minh Tông/]] <!-- 南翁夢錄·黎澄 --> # [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] <!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---> # [[/Academia in Literary Chinese between East and West/]] <!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---> ===Unit 19: Historical Annals and Encyclopediae=== <!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---> # [[/An Introduction to Biographical Paintings/]] <!-- Many older paintings include biographies at the top in Literary Chinese. Students need to learn these. https://commons.wikimedia.org/wiki/File:%E6%AD%B7%E4%BB%A3%E8%81%96%E8%B3%A2%E5%8D%8A%E8%BA%AB%E5%83%8F_%E5%86%8A_%E8%AB%B8%E8%91%9B%E4%BA%AE_(Zhuge_Liang).png - Famous figure, also part of a very notable series. https://commons.wikimedia.org/wiki/File:Otomo-Sorin-2.jpg - Contains the Japanese repetition character 々 https://commons.wikimedia.org/wiki/File:Toyotomi_hideyoshi4.jpg - simply has aura --> # [[/The History of Liao, Jin, and Song with Toqto'a/]] <!--- 脱脱 ---> # [[/Two Years in the Forbidden City with Yu Deling/]] <!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---> # [[/Selected Records of the History of the Da Shun/]] <!--- Fair Use of a 2010 book written in Literary Chinese about the Da Shun dynasty. Limit to 500 characters, if that. Use to encourage recognition of Simplified variants and modern Wenyanwen. ---> # [[/Documenting the World with Terajima/]] <!--- 和漢三才図会 寺島良安, built off 三才圖會 ---> ===Unit 20: Buddhist Literature=== <!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---> <!--- Place focus on practical stuff first. Stuff you can and WILL see in Buddhist temples. Stuff Buddhists can take away immediately. Skills-based approach feels strongest here. ---> <!--- Look at Northern Liang and Later Qin literature, as there is a ton of work by translators from India during the 16 kingdoms period, particularly those two. ---> <!--- Stuff by Bodhidharma 達摩 could be fun too https://zh.wikisource.org/wiki/Author:%E9%81%94%E6%91%A9 ---> # [[/Dipping your feet in with Wenyan Shu/]] <!--- 華亭 世尊遺法本忘言,教外別傳意已圓。 只履攜將蔥嶺去,不妨來上月明船。 ---> # [[/Buddhism in Battle Standards/]] # [[/The Seven Tathagatas/]] <!--- 南無寶勝如來 南無多寶如來 南無妙色身如來 南無廣博身如來 南無離怖畏如來 南無甘露王如來 南無阿彌陀佛 Use to introduce some core vocabulary in repetitive manner. Useful phrases from my trip to Jing'an Temple 南無本師釋迦牟尼佛 - Pay homage to the root teacher 南無大悲觀世音菩薩 - Pay homage to the goddess of mercy 廣種福田 - widely plant a meritorious field ---> # [[/Two Buddhist Temples in Shanghai/]] <!--- 留雲禪寺 雲留雲翔領畧幾許禪機此地有雲散天開真如界。 塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。 歲次壬午冬月吉旦。 覺醒敬撰。 楊胡生沐手恭書。 善信印利明敬獻。 ---> <!--- 福慧宝鼎 慧明大和尚 - introduce the Buddhist timekeeping system with 佛歷 around this point. 赤烏古剎 建寺一千七百六十周年紀念 古剎三國建 滬瀆有重玄 石佛音淨現 聖跡顯重元 唐時稱永泰 宋敕名靜安 聖祖留佛闡 仲師移伽藍 元收八景偈 明鑄鐘聲梵 清樹化羅漢 選賢十方讚 佛日普光明 福慧共修善 鼎運昌隆際 轉正法輪緣 歲次丁亥住持慧明監製 ---> # [[/Foreseeing Monkhood with Yi Xing/]] <!--- 看命一掌金 ---> # [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]] <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> <!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---> # [[/Jizang's Three Discourses/]] <!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---> <!--- I saw these texts being quoted and thus should consider them in some capacity. 《般若波羅蜜多心經》 《金剛般若波羅蜜經》 《一切智光明仙人慈心因緣不食肉經》 《妙法蓮華經》 《大般涅槃經》 《大方等大集經》 《大毘盧舍那成佛神變加持經蓮華胎藏悲生曼荼羅廣大成就儀軌供養方便會》/ 胎藏曼荼羅 《佛說救拔焰口餓鬼陀羅尼經》 《雜阿含經》 Look at Japan's 五山文学 ---> ===Unit 21: People Focus - Manchu peoples=== # [[/Qing dynasty Poetry with Nara Singde/]] <!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---> # [[/Amassing Words with the Kangxi Emperor/]] # [[/Amassing Literature with the Qianlong Emperor/]] <!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---> <!--- Yongzheng Emperor's Poetry https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D 《和碩怡賢親王祭文》 Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B ---> # [[/Paintings and Beauty with Puru Aisin-Gioro/]] <!--- Saw these in Shanghai Museum with some writing, seemed really cool. Teaches another skill. ---> ===Unit 22: Qing-RoC Literature=== <!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---> # [[/Jewish Refugees in Shanghai/]] <!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---> # [[/A Literary Chinese Abstract/]] <!--- Abstracts from siku quanshu, probably want others ---> # [[/Lament with Lu Ruoteng/]] <!--- 《疑猜》盧若騰,東寧國 盟誓變為交質子,春秋戰國風如此;末世上下相疑猜, 更質妻子防逃徙。 此法只可羈庸奴,若遇梟雄術窮矣;妻可再娶子再育, 安能長坐針氈裏。 我贈一法君記存;推心置腹人知恩;眾人畜之眾人報, 幾個國士在君門。 盧若騰撰,陳漢光編輯,《島噫詩》,臺灣文獻叢刊第二四五種(臺北:臺灣銀行經濟研究室,1968年)21頁。 ---> # [[/Common Linguistics Knowledge in the RoC/]] <!--- 音韻常識 ---> ==References used for this page== * Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9 * Priestley, K. E., & Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books. {{BookCat}} 2to55tkfcyjosmeyngbzarv92q3yu67 User:Duskhasfallen 2 482997 4679852 4633363 2026-11-03T22:51:44Z Mfield 753190 Mfield moved page [[User:TrulyFlawed]] to [[User:Duskhasfallen]]: Automatically moved page while renaming the user "[[Special:CentralAuth/TrulyFlawed|TrulyFlawed]]" to "[[Special:CentralAuth/Duskhasfallen|Duskhasfallen]]" 4633363 wikitext text/x-wiki Hiya, I'm TrulyFlawed (she/her). I'm editing Wikibooks since I saw that the books could use a bit of a quality boost; hopefully my contributions are considered valuable. Please scrutinize my edits to ensure they're in line with policy! I can be quite bold if I am confident I know the material. 45cxbjkfe8q055un2pgxw61k5bwqjbi User talk:Duskhasfallen 3 483056 4679854 4633533 2026-11-03T22:51:44Z Mfield 753190 Mfield moved page [[User talk:TrulyFlawed]] to [[User talk:Duskhasfallen]]: Automatically moved page while renaming the user "[[Special:CentralAuth/TrulyFlawed|TrulyFlawed]]" to "[[Special:CentralAuth/Duskhasfallen|Duskhasfallen]]" 4633533 wikitext text/x-wiki <div style="text-align:center; font-size:110%; font-weight:bold;">[[Wikibooks:Welcome|Welcome]] to Wikibooks, TrulyFlawed!</div> <!-- FIRST COLUMN --> <div style="width:49.5%; float:left; margin:0em; padding:0em;"> <div style="margin:0.2em; border:1px solid #15304f; background-color:#f4eed7;"> <div style="border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;">[[File:Crystal Clear app kedit.png|20px|link=|alt=]] '''First steps tutorial'''</div> <div style="padding:0.4em 1em 0.3em 1em;"> '''Wikibooks is for [[WB:AGF|collaborative]] development of free&nbsp;[[WB:WIW|textbooks]].''' You do not need technical skills to [[Using Wikibooks|contribute]]. You can [[WB:BOLD|easily change most books]]. Please [[WB:CHAT|introduce yourself]], and let us know what [[WB:PROJECTS|interests you]]. If you already contribute at other Wikimedia projects, our [[Wikibooks:Wikibooks for Wikimedians|Wikimedia Orientation]] should quickly get you started. </div> </div> <div class="collapsible" style="margin:0.2em; border:1px solid #15304f; background-color:#f4eed7; text-align:left;"> <div class="title" style="border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;">[[File:Icon apps query.svg|20px|link=|alt=]] '''Getting help'''</div> <div class="NavContent" style="padding:0.4em 1em 0.3em 1em;"> * Read the [[Using Wikibooks]] book for a friendly introduction to the project, or our [[Help:Contents|help pages]] for more information. * You can get friendly help from the community in the [[WB:HELP|user assistance room]] or our [[irc:wikibooks|IRC channel]]. * Upload freely licensed files to [[commons:Wikimedia Commons|Wikimedia Commons]]. You may [[WB:RFP|request permission]] to upload [[w:fair use|fair use]] files locally. Please include author and source {{tl|information}} and a {{nowrap|{{tl|non-free use rationale}}}} for [[WB:FU|non-free]] files. </div> </div> </div> <!-- SECOND COLUMN --> <div style="width:49.5%; float:left; margin:0em; padding:0em;"> <div class="collapsible" style="margin:0.2em; border:1px solid #14304f; background-color:#f4eed7; text-align:left;"> <div class="title" style="border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;">[[File:Nuvola filesystems trashcan full.png|20px|link=|alt=]] '''Made a mistake?'''</div> <div class="NavContent" style="padding:0.4em 1em 0.3em 1em;"> * You can [[WB:REVERT|restore]] a previously saved version. * Pages should follow the [[WB:NP|<code>'''Book Title/Chapter Title'''</code>]] naming convention. * Need to rename a page? Use the ''move'' tab (is available once your account is 4 days old - until then, ask for [[WB:HELP|help]]). * To request a page be deleted, add {{tlx|delete|''your reason''}} to the top of the page. * Was a page you made deleted? Please read the [[WB:DP|deletion policy]], and check the [[Special:Log/delete|deletion log]] to find out why. Also check the [[WB:RFD|RFD]] archives if applicable. You can request undeletion at [[WB:RFU]], or ask the administrator who deleted the page. </div> </div> <div class="collapsible selected" style="margin:0.2em; border:1px solid #15304f; background-color:#f4eed7; text-align:left;"> <div class="title" style="border-bottom:1px solid #15304f; background-color:#89b5e7; padding:0.2em 0.5em; font-size:110%; font-weight:bold;">[[File:Transmission icon.png|20px|link=|alt=]] '''Goodies, tips and tricks'''</div> <div class="NavContent" style="padding:0.4em 1em 0.3em 1em;"> * Please fill in [[WB:ES|the edit summary]] and [[WB:PREVIEW|preview]] your edits before saving. * Sign your name on [[WB:TALK|discussion pages]] by typing &#126;&#126;&#126;&#126; * User scripts can make many tasks easier. Look at the ''Gadgets'' tab of [[Special:Preferences|''my preferences'']]; check off the boxes for the scripts you want, and hit ''save''! </div> </div> </div> <div style="clear:both; padding-right:1em; text-align:right; font-size:smaller">(Would you like to provide [[Template talk:Bigwelcome|feedback]] on this message?)</div> <div style="clear:both;"> </div> —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:18, 2 May 2026 (UTC) h787qt4tx7yiuwhzbu5vqofdug6fr06 Wikijunior:Animal Alphabet 2/T 110 483496 4679778 4637982 2026-11-03T13:16:49Z ~2026-58523-79 3630299 4679778 wikitext text/x-wiki <div style="text-align: center; font-size: 400%;">'''T''' is for '''T'''igerPG13 成人题材 [[File:Panthera tigris tigris.jpg|500px|center]] {{ {{BOOKTEMPLATE}} }} n9w95r57ssfjc10rexywfevvzwfauaq 4679780 4679778 2026-11-03T13:17:58Z NDG 3510220 [[WB:REVERT|Reverted]] edit by [[Special:Contributions/~2026-58523-79|~2026-58523-79]] ([[User talk:~2026-58523-79|talk]]) to last version by ~2026-32105-54 4637982 wikitext text/x-wiki <div style="text-align: center; font-size: 400%;">'''T''' is for '''T'''iger</div> [[File:Panthera tigris tigris.jpg|500px|center]] {{ {{BOOKTEMPLATE}} }} 717ixcsck18m42ykwo38s5bwn70gx2h Vehicle Identification Numbers (VIN codes)/Audi/VIN Codes 0 483747 4679910 4650399 2026-11-04T07:31:47Z JustTheFacts33 3434282 /* Position 11, Production Plant: */ 4679910 wikitext text/x-wiki {{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}} ===Positions 1–3, World Manufacturer Identifier:=== * WAU - Audi (Audi AG) passenger car * WA1 - Audi (Audi AG) SUV * WUA - Audi passenger car - quattro GmbH/Audi Sport GmbH (RS3, RS4, RS5, RS6, RS7, TT RS ['18-'22], R8,<br> S4 Cabriolet ['04-'09], S4 25quattro Special Edition sedan ['06], S8 plus ['16-'18], Non-North American Mkt. RS Q3, Q7 V12 TDI) * WU1 - Audi SUV - Audi Sport GmbH (RS Q8) * TRU - Audi Hungary (Audi Hungaria Motor Kft.) passenger car (only used for TT/TTS & '12-'13 TT RS) * 3U5 - Audi Mexico SUV ===Position 5, Engine Type: === {| class="wikitable" |+Position 5 |- ! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications |- | A || 1.7L || I4 || Gas || SOHC,<br /> 8 valve || MPI. VW EA827 engine.<br> Audi 4000 4E/4000S 4E ('81-'83) |- | A || 1.8L || I4 || Gas || SOHC,<br /> 8 valve || MPI. VW EA827 engine.<br> Audi 4000S ('84) |- | A || 2.1L || I5 || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi Coupe GT ('84) |- | A || 2.0L || I4 || Gas || SOHC,<br /> 8 valve || MPI. VW EA827 engine.<br> Audi 80 ('90) |- | A || 2.2L || I5 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || MPI. Audi EA828 I5 engine. <br> Audi S6 ('95 & '96-'97 in Canada) |- | A || 2.8L || 90° V6 || Gas || SOHC,<br /> 12 valve || MPI. Audi EA835 engine - Gen 1. Iron Block. <br> Audi 90 ('95), Cabriolet ('95-'98), A4 2.8 ('96-'97), A6 sedan ('95-'97), A6 wagon ('95-'98) |- | A || 2.8L || 90° V6 || Gas || DOHC,<br /> 30 valve || MPI. Audi EA835 engine - Gen 2. Iron Block.<br> Audi A6 sedan 2.8 ('98-'99), A6 Avant 2.8 ('99) |- | A || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || Direct injection. Audi-Bentley EA824 engine. 3993cc. 560 hp.<br> Audi RS7 ('17-'18) |- | A || 5.2L || 90° V10 || Gas || DOHC,<br /> 40 valve || Direct injection. Dry sump lubrication. Audi EA824 V10 engine. 532 hp.<br> Audi R8 V10 Quattro ('17-'18), R8 V10 RWS ('18), R8 Rwd ('21) |- | A || 3.0L || 90° V6 supercharged [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || Direct injection. Audi EA837 engine.<br> Audi Q7 3.0T ('17-'19) |- | A || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || 12v Mild Hybrid. Direct injection. Exhaust AVS. Audi EA888 Evo4 engine - ULEV. TSI. Timing chain. 261 hp. <br> Audi A4 45 TFSI ('21-'25), A4 Allroad 45 TFSI ('21-'25),<br> A5 Coupe/Cabriolet 45 TFSI ('21-'24), A5 Sportback 45 TFSI ('21-'25),<br> Q5 45 TFSI [FY] ('21-'25), Q5 Sportback 45 TFSI [FY] ('21-'25) |- | A || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Exhaust AVS. Audi EA888 Evo4 engine - SULEV. TSI. Timing chain. 268 hp. <br> Audi Q5 [GU] (Mid '25-'26), Q5 Sportback [GU] (Mid '25-'26), A5 [B10] ('26) |- | B || 2.1L || I5 || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi 4000 ('81), Coupe ('81-'83), 5000/5000S ('81-'84) |- | B || 1.8L || I4 || Gas || SOHC,<br /> 8 valve || MPI. VW EA827 engine.<br> Audi 4000S ('85-'87) [Pos. 7-8 of VIN is 81] |- | B || 2.2L || I5 || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi 4000S Quattro ('84-'85), 4000CS Quattro ('86-'87) [Pos. 7-8 of VIN is 85],<br> 5000S ('85-'86) |- | B || 2.0L || I4 || Gas || SOHC,<br /> 8 valve || MPI. VW EA827 engine.<br> Audi 80 ('88-'89), 90 ('88) |- | B || 2.3L || I5 || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi 100 ('89), 100 Quattro ('89) |- | B || 2.0L || I4 || Gas || SOHC,<br /> 8 valve || MPI. VW EA827 engine.<br> Audi 80 ('90) |- | B || 1.8L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || MPI. Audi EA827/EA113 engine. <br> Audi A4 1.8T ('97-'99) |- | B || 5.2L || 90° V10 || Gas || DOHC,<br /> 40 valve || Direct injection. Dry sump lubrication. Audi EA824 V10 engine. 602 hp.<br> Audi R8 V10 Plus Quattro ('17-'18), R8 V10 Performance Quattro ('20-'23), R8 GT Rwd ('23) |- | B || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || 12v Mild Hybrid. Direct injection. Miller Cycle (B-Cycle). Intake AVS. Audi EA888 Gen3B engine - ULEV. TSI. Timing chain. Detuned version: 201 hp.<br> Audi A4 40 TFSI ('21-'25), A5 Sportback 40 TFSI ('21-'25), Q5 40 TFSI [FY] ('22-'25) |- | B || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Exhaust AVS. Audi EA888 Evo4 engine - ULEV. TSI. Timing chain. 268 hp. <br> Audi A5 [B10] (Mid '25) |- | B || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Exhaust AVS. Audi EA888 Evo4 engine - SULEV. TSI. Timing chain. 255 hp. <br> Audi Q3 ('26) |- | C || 2.1L || I5 Turbo || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi 5000 Turbo ('81-'83) |- | C || 2.1L || I5 Turbo [[w:Intercooler|IC]] || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi Quattro Coupe ('82‡ & '83-'85), 5000S Turbo ('84-'85) |- | C || 2.3L || I5 || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi 80 ('91-'92), 80 Quattro ('88-'92), 90 ('88-'91), 90 Quattro ('88-'89),<br> 5000S ('87-'88), 5000S Quattro ('88), 100 ('90-'91), 100 Quattro ('90-'91) |- | C || 2.2L || I5 Turbo [[w:Intercooler|IC]] || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi 200 Turbo ('89), 200 Turbo Quattro ('89) |- | C || 2.8L || 90° V6 || Gas || SOHC,<br /> 12 valve || MPI. Audi EA835 engine - Gen 1. Iron Block. CA-type emissions. <br> Audi A6 sedan ('95-'97), A6 wagon ('96-'98) |- | C || 1.8L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || MPI. Audi EA827/EA113 engine. <br> Audi A4 sedan/Avant 1.8T ('00-Mid '05), A4 Cabriolet 1.8T ('03-'06), TT [180 hp] ('00-'06) |- | C || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric Hybrid || DOHC,<br /> 16 valve || Direct injection. Audi EA888 engine + electric motor. Lithium-ion Battery Pack.<br> Audi Q5 Hybrid (Early '14) |- | C || 1.8L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine - PZEV. TSI. Timing chain.<br> Audi A3 Fwd 1.8T ('15) |- | C || 3.0L || 90° V6 supercharged [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || Direct injection. Audi EA837 engine.<br> Audi SQ5 ('16-'17) |- | C || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 engine - ULEV. TSI. Timing chain. <br> Audi Q3 ('17-'18) |- | C || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || 48v Mild Hybrid. Direct injection. Porsche-Audi EA825 engine. 3996cc. 591 hp.<br> Audi RS6 Avant ('21-'23), RS7 ('21-'23) |- | C || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || 12v Mild Hybrid. Direct injection. Exhaust AVS. Audi EA888 Evo4 engine - ULEV. TSI. Timing chain. 261 hp. <br> Audi Q7 45 TFSI ('23-'26) |- | D || 2.1L || I5 || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi Coupe GT ('84) |- | D || 2.2L || I5 || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi Coupe GT ('85-'87) |- | D || 2.3L || I5 || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi 80 ('91), 80 Quattro ('90-'91), 90 ('90) |- | D || 2.3L || I5 || Gas || DOHC,<br /> 20 valve || MPI. Audi EA828 I5 engine. <br> Audi Coupe Quattro 20V ('90) |- | D || 2.2L || I5 Turbo [[w:Intercooler|IC]] || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi 5000CS Turbo ('86-'88), 200 Turbo ('90-'91), 200 Turbo Quattro ('90) |- | D || 2.8L || 90° V6 || Gas || DOHC,<br /> 30 valve || MPI. Audi EA835 engine - Gen 2. Iron Block.<br> Audi A4 2.8 ('98-'99) |- | D || 2.7L || 90° V6 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 30 valve || MPI. Audi EA835 engine - Gen 2. Iron Block.<br> Audi S4 ('00-'02), A6 2.7T ('00-'04), Allroad Quattro 2.7T ('02-'05) |- | D || 3.2L || 15° VR6 || Gas || DOHC,<br /> 24 valve || MPI. VW EA390 engine.<br> Audi A3 3.2 ('06-'09), TT 3.2 ('05-'06, '08-'09) |- | D || 3.0L || 90° V6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || 48v Mild Hybrid. Direct injection. Audi-Porsche EA839 engine.<br> Audi A8 3.0T/55 TFSI ('19-'26) |- | D || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || 48v Mild Hybrid. Direct injection. Porsche-Audi EA825 engine. 3996cc. 621 hp.<br> Audi RS6 Avant performance ('24-'26), RS7 performance ('24-'26) |- | E || 2.3L || I5 || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi Coupe GT 2.3 "Special Build" (Late '87) |- | E || 2.2L || I5 Turbo [[w:Intercooler|IC]] || Gas || SOHC,<br /> 10 valve || MPI. Audi EA828 I5 engine. <br> Audi 5000CS Turbo Quattro ('86-'88) |- | E || 2.3L || I5 || Gas || DOHC,<br /> 20 valve || MPI. Audi EA828 I5 engine. <br> Audi 90 Quattro 20V ('90-'91), Coupe Quattro 20V ('90-'91) |- | E || 2.2L || I5 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || MPI. Audi EA828 I5 engine. <br> Audi 200 Turbo Quattro 20V ('91) |- | E || 3.6L || 90° V8 || Gas || DOHC,<br /> 32 valve || MPI. Audi V8 engine. Timing belt. Audi V8 Quattro ('90-'91) |- | E || 2.8L || 90° V6 || Gas || SOHC,<br /> 12 valve || MPI. Audi EA835 engine - Gen 1. Iron Block. <br> Audi 90 ('95) |- | E || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 engine - PZEV. TSI. Timing chain.<br> Audi A3 Fwd 2.0T ('08-'13) |- | E || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Exhaust AVS. Audi EA888 Gen3 engine - SULEV. TSI. Timing chain.<br> Audi A3 2.0T Quattro ('18-'20), TT ('19-'23), Q3 2.0T/45 TFSI ('19-'20), Q3 S Line 45 TFSI ('21-'25) |- | E || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || 48v Mild Hybrid. Direct injection. Porsche-Audi EA825 engine. 3996cc. 453 hp.<br> Audi A8 4.0T ('19-'21) |- | E || 5.2L || 90° V10 || Gas || DOHC,<br /> 40 valve || Direct injection. Dry sump lubrication. Audi EA824 V10 engine. 562 hp.<br> Audi R8 V10 Quattro ('20), R8 V10 Performance Rwd ('22-'23) |- | F || 2.3L || I5 || Gas || DOHC,<br /> 20 valve || MPI. Audi EA828 I5 engine. <br> Audi 90 Quattro 20V ('90-'91), Coupe Quattro 20V ('91) |- | F || 3.7L || 90° V8 || Gas || DOHC,<br /> 32 valve || MPI. Audi V8 engine. Timing belt. Audi A8 3.7 ('97-'99) |- | F || 3.2L || 15° VR6 || Gas || DOHC,<br /> 24 valve || MPI. VW EA390 engine.<br> Audi TT 3.2 ('04-'05) |- | F || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA113 engine. FSI. Timing belt. <br> Audi A3 2.0T ('06-'08), A4 sedan 2.0T (Mid '05-'08), A4 Avant 2.0T (Mid '05-'08),<br> A4 Cabriolet 2.0T ('07-'09), TT ('08-'09), TTS ('09) |- | F || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 engine - ULEV. TSI. Timing chain.<br> Audi A3 2.0T ('08-'11), A3 2.0T Quattro ('12-'13), A4 sedan 2.0T ('09-'12), A4 sedan 2.0T Fwd ('13-'16), A4 sedan 2.0T Quattro w/man. trans. ('13-'16), A4 sedan 2.0T Quattro w/auto. trans. (Early '13),<br> A4 Avant 2.0T ('09-'12), Allroad 2.0T (Early '13), A5 2.0T ('10-'12),<br> A5 Coupe 2.0T Quattro w/man. trans. ('13-'15), A5 Cabriolet 2.0T Fwd ('13-'14),<br> A5 2.0T Quattro w/auto. trans. (Early '13), A6 2.0T ('12-'16), TT ('09-'15), Q3 ('15-'16),<br> Q5 2.0T ('11-Early '13) |- | F || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 engine - PZEV. TSI. Timing chain.<br> Audi A3 Fwd 2.0T (Early prod. '12) |- | F || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas/E85 || DOHC,<br /> 16 valve || Flex Fuel. Direct injection. Audi EA888 engine - ULEV. TSI. Timing chain.<br> Audi A4 sedan 2.0T Quattro w/auto. trans. ('13-'16), Allroad 2.0T ('13-'16),<br> A5 2.0T Quattro w/auto. trans. ('13-'15), Q5 2.0T ('13-'15) |- | F || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine - PZEV. TSI. Timing chain.<br> Audi A3 2.0T Quattro ('15) |- | F || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine - ULEV. TSI. Timing chain. High Output: 288 hp.<br> Audi S3 Quattro ('15) |- | F || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || Direct injection. Audi-Bentley EA824 engine. 3993cc. 450 hp.<br> Audi S6 ('17-'18), S7 ('17-'18) |- | F || 2.9L || 90° V6 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || 48v Mild Hybrid. Direct injection. Audi-Porsche EA839 engine.<br> Audi S6 ('20-'25), S7 ('20-'25) |- | G || 1.6L || I4 || Diesel || SOHC,<br /> 8 valve || Indirect injection. VW EA827 engine. Audi 4000 Diesel ('82) |- | G || 2.0L || I5 || Diesel || SOHC,<br /> 10 valve || Indirect injection. Audi 5000 Diesel ('81) |- | G || 4.2L || 90° V8 || Gas || DOHC,<br /> 32 valve || MPI. Audi V8 engine. 4172cc. Timing belt.<br> Audi A8 4.2 ('97-'99) |- | G || "3.2L" || 90° V6 || Gas || DOHC,<br /> 24 valve || Direct injection. Audi EA837 engine. 3.1L=3123cc.<br> Audi A4 sedan/Avant 3.2 (Mid '05-'06), A6 3.2 ('05-'06) |- | G || 3.0L || 90° V6 supercharged [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || Direct injection. Audi EA837 engine.<br> Audi S4 ('10-'16), S5 Cabriolet ('10-'15, Early '16), S5 coupe ('13-'15), A6 3.0T ('09-'16),<br> A7 3.0T ('12-'16), A8 3.0T ('13-'15), Q5 3.0T ('13-'15), SQ5 ('14-'15), Q7 3.0T ('11-'15) |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 engine - ULEV. TSI. Timing chain.<br> Audi A5 2.0T w/man. trans. ('16-'17) |- | G || 6.3L || 72° W12 || Gas || DOHC,<br /> 48 valve || Direct injection. VW W12 engine. Audi A8 W12 ('16) |- | G || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric Hybrid || DOHC,<br /> 16 valve || Direct injection. Audi EA888 engine + electric motor. Lithium-ion Battery Pack.<br> Audi Q5 Hybrid ('16) |- | H || 1.6L || I4 Turbo || Diesel || SOHC,<br /> 8 valve || Indirect injection. VW EA827 engine. Audi 4000 Turbo Diesel ('83) |- | H || 2.0L || I5 || Diesel || SOHC,<br /> 10 valve || Indirect injection. Audi 5000 Diesel ('82) |- | H || 2.0L || I5 Turbo || Diesel || SOHC,<br /> 10 valve || Indirect injection. Audi 5000 Turbo Diesel ('83) |- | H || 2.8L || 90° V6 || Gas || DOHC,<br /> 30 valve || MPI. Audi EA835 engine - Gen 2. Iron Block.<br> Audi A4 2.8 ('00-'01), A6 2.8 ('00-'01) |- | H || "3.2L" || 90° V6 || Gas || DOHC,<br /> 24 valve || Direct injection. Audi EA837 engine. 3.1L=3123cc.<br> Audi A4 sedan/Avant 3.2 ('06-'08), A4 Cabriolet 3.2 ('07-'09), A6 3.2 ('06-'09) |- | H || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine - ULEV. TSI. Timing chain. <br> Audi Q7 2.0T ('17-'19) |- | H || 3.0L || 90° V6 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 24 valve || Direct injection. Audi-Porsche EA839 engine + electric motor. Lithium-ion Battery Pack.<br> Audi A8 60 TFSI e ('20-'21) |- | J || 2.8L || 90° V6 || Gas || SOHC,<br /> 12 valve || MPI. Audi EA835 engine - Gen 1. Iron Block. <br> Audi 90 ('93-'94), 100 ('92-'94) |- | J || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,<br /> 16 valve || Common-Rail Direct injection. VW EA189 engine.<br> Audi A3 TDI ('10-'13) |- | J || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,<br /> 16 valve || Common-Rail Direct injection. SCR. VW EA288 engine.<br> Audi A3 TDI ('15) |- | J || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine - ULEV. TSI. Timing chain. 248 hp. <br> Audi Q7 45 TFSI ('20-'22) |- | K || 2.8L || 90° V6 || Gas || SOHC,<br /> 12 valve || MPI. Audi EA835 engine - Gen 1. Iron Block. <br> Audi 90 ('93-'95), 100 ('92-'94) |- | K || 3.2L || 90° V6 || Gas || DOHC,<br /> 24 valve || Direct injection. Audi EA837 engine. 3197cc. <br> Audi A4 sedan 3.2 ('09), A5 3.2 ('08-'10), A6 3.2 ('10-'11), Q5 3.2 ('09-'12) |- | L || 2.8L || 90° V6 || Gas || SOHC,<br /> 12 valve || MPI. Audi EA835 engine - Gen 1. Iron Block. <br> Audi Cabriolet ('94-'95) |- | L || 4.2L || 90° V8 || Gas || DOHC,<br /> 40 valve || MPI. Audi V8 engine. 4172cc. Timing belt.<br> Audi A6 4.2 ('00-'04), A8 4.2 ('00-'06) |- | L || 4.2L || 90° V8 || Gas || DOHC,<br /> 40 valve || MPI. Audi EA824 engine. 4163cc. Timing chain.<br> Audi S4 sedan/Avant ('04-'08), S4 Cabriolet ('04-'09),<br> A6 4.2 ('05-'06), Allroad Quattro 4.2 ('04-'05) |- | M || 3.0L || 90° V6 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,<br /> 24 valve || Direct injection. Audi EA897 engine.<br> Audi A6 TDI ('14-'16), A7 TDI ('14-'16), A8 TDI ('14-'15), Q5 TDI ('14-'15), Q7 TDI ('09-'15) |- | M || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Miller Cycle (B-Cycle). Intake AVS. Audi EA888 Gen3B engine - ULEV. TSI. Timing chain. Detuned version: 188 hp.<br> Audi A4 Ultra 2.0T Fwd ('17-'18), A4 2.0T Fwd ('19-'20) |- | N || 5.2L || 90° V10 || Gas || DOHC,<br /> 40 valve || Direct injection. Audi EA824 V10 engine.<br> Audi S6 ('07-'11), S8 ('07-'09) |- | N || 5.2L || 90° V10 || Gas || DOHC,<br /> 40 valve || Direct injection. Dry sump lubrication. Audi EA824 V10 engine.<br> Audi R8 ('10-'12, '14-'15) |- | N || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Exhaust AVS. Audi EA888 Gen3 engine - ULEV. TSI. Timing chain. <br> Audi A4 2.0T Fwd/Quattro ('17-'18), A4 2.0T Quattro ('19-'20), A4 Allroad Quattro ('17-'20),<br> A5 Coupe/Cabriolet 2.0T Quattro ('18-'20), A5 Sportback 2.0T Quattro ('18-'20),<br> Q5 2.0T Quattro ('18-'20) |- | P || 2.2L || I5 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || MPI. Audi EA828 I5 engine. <br> Audi S4 [C4 (4A)] ('92-'93) |- | P || 2.7L || 90° V6 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 30 valve || MPI. Audi EA835 engine - Gen 2. Iron Block.<br> Audi Allroad Quattro 2.7T ('01) |- | P || 1.4L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 16 valve || Direct injection. VW EA211 engine + electric motor. Lithium-ion Battery Pack. Timing belt.<br> Audi A3 Sportback e-tron ('16-'18) |- | P || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine + electric motor. Lithium-ion Battery Pack. TSI. Timing chain.<br> SULEV.<br> Audi A7 55 TFSI e ('21-'22) |- | R || 2.2L || I5 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || MPI. Audi EA828 I5 engine. <br> Audi S4 [C4 (4A)] ('93-'94) |- | R || 6.0L || 72° W12 || Gas || DOHC,<br /> 48 valve || MPI. VW W12 engine. Audi A8 W12 ('05-'09) |- | R || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || Direct injection. Audi-Bentley EA824 engine. 3993cc. 605 hp.<br> Audi RS7 performance ('16-'18) |- | R || 3.0L || 90° V6 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,<br /> 24 valve || Direct injection. Audi EA897 engine. Audi A8 TDI ('16) |- | R || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || 48v Mild Hybrid. Direct injection. Porsche-Audi EA825 engine. 3996cc. 591 hp.<br> Audi RS Q8 ('20-'24) |- | R || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || 48v Mild Hybrid. Direct injection. Porsche-Audi EA825 engine. 3996cc. 631 hp.<br> Audi RS Q8 performance ('25-'26) |- | S || 1.8L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || MPI. Audi EA827/EA113 engine. 180 hp. <br> Audi TT (Early '00) |- | S || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || Direct injection. Audi-Bentley EA824 engine. 3993cc.<br> Audi S8 ('16) |- | S || 2.5L || I5 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || Direct/Port injection. Audi EA855 Evo engine.<br> Audi TT RS ('18-'22) |- | S || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || 48v Mild Hybrid. Direct injection. Porsche-Audi EA825 engine. 3996cc. 563 hp.<br> Audi S8 ('20-'26) |- | T || 1.8L || I4 Turbo Twin [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || MPI. Audi EA827/EA113 engine. High Output - 225 hp. Single Turbo, Twin Intercoolers. <br> Audi TT ('01-'06) |- | T || 3.0L || 90° V6 || Gas || DOHC,<br /> 30 valve || MPI. Audi EA835 engine - Gen 3. Aluminum block.<br> Audi A4 sedan/Avant 3.0 ('02-Mid '05), A4 Cabriolet 3.0 ('03-'06), A6 3.0 ('02-'04) |- | T || "3.2L" || 90° V6 || Gas || DOHC,<br /> 24 valve || Direct injection. Audi EA837 engine. 3.1L=3123cc.<br> Audi A6 3.2 ('05) |- | U || 4.2L || 90° V8 || Gas || DOHC,<br /> 40 valve || MPI. Audi V8 engine. 4172cc. Timing belt.<br> Audi S6 Avant ('02-'03), S8 ('01-'03) |- | U || 4.2L || 90° V8 || Gas || DOHC,<br /> 32 valve || Direct injection. Audi EA824 engine. 4163cc. Timing chain.<br> Audi RS4 sedan ('07-'08), RS4 Cabriolet ('08) |- | U || 4.2L || 90° V8 || Gas || DOHC,<br /> 32 valve || Direct injection. Dry sump lubrication. Audi EA824 engine. 4163cc. Timing chain.<br> Audi R8 ('08-'12, '14-'15) |- | U || 5.2L || 90° V10 || Gas || DOHC,<br /> 40 valve || Direct injection. Dry sump lubrication. Audi EA824 V10 engine.<br> Audi R8 V10 coupe w/man. trans. (Early '14) [when U in 5th pos. of VIN follows G in 4th pos. of VIN] |- | U || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Miller Cycle (B-Cycle). Intake AVS. Audi EA888 Gen3B engine - PZEV. TSI. Timing chain. Detuned version: 184 hp.<br> Audi A3 2.0T Fwd ('17) |- | U || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Miller Cycle (B-Cycle). Intake AVS. Audi EA888 Gen3B engine - SULEV. TSI. Timing chain. Detuned version: 184 hp.<br> Audi A3 2.0T Fwd ('18-'20), Q3 40 TFSI ('21-'22) |- | U || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Miller Cycle (B-Cycle). Intake AVS. Audi EA888 Gen3B engine - ULEV. TSI. Timing chain. Detuned version: 184 hp.<br> Audi Q3 40 TFSI ('23-'24 & '25 in Canada) |- | U || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || 48v Mild Hybrid. Direct injection. Miller Cycle (B-Cycle). Intake AVS. Audi EA888 Gen3B engine - SULEV.<br> TSI. Timing chain. 201 hp.<br> Audi A3 40 TFSI ('22-'26) |- | V || 4.2L || 90° V8 || Gas || DOHC,<br /> 32 valve || MPI. Audi V8 engine. 4172cc. Timing belt. Audi V8 Quattro ('92-'93) |- | V || 4.2L || 90° V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 40 valve || MPI. Audi V8 engine. 4172cc. Timing belt.<br> Audi RS6 (US: '03, Canada: '04) |- | V || 4.2L || 90° V8 || Gas || DOHC,<br /> 32 valve || Direct injection. Audi EA824 engine. 4163cc. Timing chain.<br> Audi S5 coupe ('08-'12), A6 4.2 ('07-'11), A8 4.2 ('07-'12), Q7 4.2 ('07-'10) |- | V || 3.0L || 90° V6 Turbo [[w:Intercooler|IC]] || Diesel || DOHC,<br /> 24 valve || Direct injection. Audi EA897 engine. Audi Q5 TDI ('16) |- | V || 3.0L || 90° V6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || 48v Mild Hybrid. Direct injection. Audi-Porsche EA839 engine.<br> Audi Q8 3.0T/55 TFSI ('19-'26), Q7 55 TFSI ('25-'26) |- | W || 4.2L || 90° V8 || Gas || DOHC,<br /> 32 valve || MPI. Audi V8 engine. 4172cc. Timing belt. Audi V8 Quattro ('92-'94) |- | W || 2.5L || I5 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || Direct/Port injection. Audi EA855 Evo engine.<br> Audi RS3 ('17-'20) |- | W || 2.9L || 90° V6 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || Direct injection. Audi-Porsche EA839 engine.<br> Audi RS5 coupe ('18-'19, '21-'24), RS5 Sportback ('19, '21-'25) |- | W || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || 48v Mild Hybrid. Direct injection. Porsche-Audi EA825 engine. 3996cc. 500 hp.<br> Audi SQ7 ('20-'26), SQ8 ('20-'26) |- | W || 2.5L || I5 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || Direct/Port injection. Audi EA855 Evo engine. 394 hp.<br> Audi RS3 ('25-'26) |- | X || 1.8L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || MPI. Audi EA827/EA113 engine. 180 hp. <br> Audi TT ('01-'02) |- | X || 3.0L || 90° V6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || 48v Mild Hybrid. Direct injection. Audi-Porsche EA839 engine.<br> Audi Q7 55 TFSI ('20-'24) |- | Y || 3.6L || 10.6° VR6 || Gas || DOHC,<br /> 24 valve || Direct injection. VW EA390 engine.<br> Audi Q7 3.6 ('07-'10) |- | 1 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA113 engine - ULEV. FSI. Timing belt.<br> Audi TTS ('10-'15) |- | 1 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine - ULEV. TSI. Timing chain. High Output: 288 hp.<br> Audi S3 Quattro ('16-'20), TTS ('16-'23) |- | 2 || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || Direct injection. Audi-Bentley EA824 engine. 3993cc.<br> Audi S6 ('13-'16), S7 ('13-'16), RS7 ('14-'16), A8 4.0T ('13-'15), S8 ('13-'15) |- | 2 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas/E85 || DOHC,<br /> 16 valve || Flex Fuel. Direct injection. Audi EA888 engine - ULEV. TSI. Timing chain.<br> Audi A5 2.0T w/auto. trans. ('16-'17), Q5 2.0T ('16-'17) |- | 2 || 3.0L || 90° V6 supercharged [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || Direct injection. Audi EA837 engine.<br> Audi A6 3.0T ('17), A7 3.0T ('17) |- | 2 || 3.0L || 90° V6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || 48v Mild Hybrid. Direct injection. Audi-Porsche EA839 engine.<br> Audi A6 3.0T/55 TFSI ('19-'25), A6 Allroad ('20-'26), A7 3.0T/55 TFSI ('19-'25) |- | 2 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric [[w:Plug-in hybrid|PHEV]] || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine + electric motor. Lithium-ion Battery Pack. TSI. Timing chain.<br> Audi Q5 55 TFSI e [FY] ('20-'25) |- | 3 || 2.5L || I5 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || Direct injection. Audi EA855 engine.<br> Audi TT RS ('12-'13) |- | 3 || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || Direct injection. Audi-Bentley EA824 engine. 3993cc.<br> Audi A8 4.0T ('16-'18) |- | 3 || 3.0L || 90° V6 supercharged [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || Direct injection. Audi EA837 engine. Higher Output: 340 hp.<br> Audi A6 3.0T Competition ('17), A6 3.0T ('18), A7 3.0T Competition ('17), A7 3.0T ('18) |- | 3 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || 12v Mild Hybrid. Direct injection. Audi EA888 Gen3 engine - ULEV. TSI. Timing chain. 261 hp.<br> Audi A6 Sport 45 TFSI ('21), A6 45 TFSI ('22-'25) |- | 3 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Evo4 engine - ULEV. TSI. Timing chain. High Output: 306 hp.<br> Audi S3 Quattro ('22-'24) |- | 4 || 6.3L || 72° W12 || Gas || DOHC,<br /> 48 valve || Direct injection. VW W12 engine. Audi A8 W12 ('12-'15) |- | 4 || 3.0L || 90° V6 supercharged [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || Direct injection. Audi EA837 engine.<br> Audi S5 coupe ('16-'17), S5 Cabriolet ('16-'17), A8 3.0T ('16-'18) |- | 4 || 3.0L || 90° V6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || Direct injection. Audi-Porsche EA839 engine.<br> Audi S4 ('18-'25), S5 coupe/cabriolet ('18-'24), S5 Sportback ('18-'25), SQ5 [FY] ('18-'25),<br> SQ5 Sportback [FY] ('21-'25) |- | 4 || 2.5L || I5 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 20 valve || Direct/Port injection. Audi EA855 Evo engine. 401 hp.<br> Audi RS3 ('22-'24) |- | 5 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Exhaust AVS. Audi EA888 Gen3 engine - PZEV. TSI. Timing chain.<br> Audi TT ('16-'17) |- | 5 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Exhaust AVS. Audi EA888 Gen3 engine - SULEV. TSI. Timing chain.<br> Audi TT ('18) |- | 5 || 4.0L || V8 Twin Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 32 valve || Direct injection. Audi-Bentley EA824 engine. 3993cc. 605 hp.<br> Audi S8 plus ('16-'18) |- | 5 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Evo4 engine - ULEV. TSI. Timing chain. High Output: 328 hp.<br> Audi S3 Quattro ('25-'26) |- | 5 || 3.0L || 90° V6 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || Direct injection. Audi-Porsche EA839 engine.<br> Audi S5 [B10] (Mid '25-'26), SQ5 [GU] (Mid '25-'26), SQ5 Sportback [GU] (Mid '25-'26), A6 [C9] ('26) |- | 6 || 4.2L || 90° V8 || Gas || DOHC,<br /> 32 valve || Direct injection. Audi EA824 engine. 4163cc. Timing chain.<br> Audi RS5 ('13-'15) |- | 7 || 1.8L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine - PZEV. TSI. Timing chain.<br> Audi A3 Fwd 1.8T ('16) |- | 7 || 3.0L || 90° V6 supercharged [[w:Intercooler|IC]] || Gas || DOHC,<br /> 24 valve || Direct injection. Audi EA837 engine.<br> Audi Q5 3.0T ('16-'17) |- | 8 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas-Electric Hybrid || DOHC,<br /> 16 valve || Direct injection. Audi EA888 engine + electric motor. Lithium-ion Battery Pack.<br> Audi Q5 Hybrid ('13-'15) |- | 8 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine - PZEV. TSI. Timing chain.<br> Audi A3 2.0T Quattro ('16-'17) |- | 8 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine - SULEV. TSI. Timing chain.<br> Audi A3 2.0T Quattro ('18) |- | 8 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || Direct injection. Audi EA888 Gen3 engine - ULEV. TSI. Timing chain.<br> Audi A6 2.0T ('17-'18) |- | 8 || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,<br /> 16 valve || 12v Mild Hybrid. Direct injection. Audi EA888 Gen3 engine - ULEV. TSI. Timing chain. 248 hp.<br> Audi A6 2.0T/45 TFSI ('19-'21) |} ‡1982 Audi Quattro: 3-4 cars were imported to the US for marketing purposes and as press cars. They remained in the US after those uses ended and transitioned into private ownership. These cars carry US-style VINs rather than European-style VINs. 3 VINs have been found. Their serial numbers (last 6 digits of VIN) are 900565, 900586, and 900648. The Audi Quattro was officially sold in the US for the 1983-1985 model years. ====Motor codes for Electric Vehicles==== {| class="wikitable" |+Position 5 |- ! VIN !! Motor Designation !! Fuel !! Drive Wheels !! Battery Size !! Application/Notes |- | A ||APA250 (Front) / AKA320 (Rear)|| Electricity || All ||95 Kwh (gross) / 83.6 Kwh (net) || Audi e-tron quattro ('19), e-tron Sportback quattro ('20) |- | A ||APA250 (Front) / AKA320 (Rear)|| Electricity || All ||95 Kwh (gross) / 86.5 Kwh (net) || Audi e-tron quattro ('21-'23), e-tron Sportback quattro ('21-'23) |- | A ||APA250 (Front) / AKA320 (Rear)|| Electricity || All ||114 Kwh (gross) / 106 Kwh (net) || Audi Q8 e-tron quattro ('24), Q8 e-tron Sportback quattro ('24) |- | C ||APA320 (1 Front) / ATA250 (2 Rear)|| Electricity || All ||95 Kwh (gross) / 86.5 Kwh (net) || Audi e-tron S quattro ('22-'23), e-tron S Sportback quattro ('22-'23) |- | C ||APA320 (1 Front) / ATA250 (2 Rear)|| Electricity || All ||114 Kwh (gross) / 106 Kwh (net) || Audi SQ8 e-tron quattro ('24), SQ8 e-tron Sportback quattro ('24) |- | C ||APP310 (Rear) || Electricity || Rear ||82 Kwh (gross) / 77 Kwh (net) || Audi Q4 e-tron 40 ('23-Mid '24) |- | C ||APP580 (Rear)|| Electricity || Rear ||100 Kwh (gross) / 94.4 Kwh (net) || Audi A6 e-tron Sportback ('25) |- | D ||APA275 (Front) / APP580 (Rear)|| Electricity || All ||100 Kwh (gross) / 94.4 Kwh (net) || Audi A6 e-tron Sportback quattro ('25) |- | E ||APA275 (Front) / APP580 (Rear)|| Electricity || All ||100 Kwh (gross) / 94.4 Kwh (net) || Audi S6 e-tron Sportback quattro ('25) |- | H ||V662 (Front) Code EBGA / V663 (Rear) (Higher output-Code EBEA)|| Electricity || All ||93.4 Kwh (gross) / 83.7 Kwh (net) || Audi RS e-tron GT quattro ('22-'24) |- | J ||V662 (Front) Code EBGA / V663 (Rear) Code EBFA|| Electricity || All ||93.4 Kwh (gross) / 83.7 Kwh (net) || Audi e-tron GT quattro ('22-'24) |- | U ||HASCO Magna asynchronous motor (Front) / APP550 (Rear) || Electricity || All ||82 Kwh (gross) / 77 Kwh (net) || Audi Q4 e-tron 55 quattro (Mid '24-'26), Q4 e-tron Sportback 55 quattro (Mid '24-'26) |- | 2 ||HASCO Magna asynchronous motor (Front) / APP310 (Rear) || Electricity || All ||82 Kwh (gross) / 77 Kwh (net) || Audi Q4 e-tron 50 quattro ('22-Mid '24), Q4 e-tron Sportback 50 quattro ('22-Mid '24) |- | 2 ||APP580 (Rear)|| Electricity || Rear ||100 Kwh (gross) / 94.4 Kwh (net) || Audi Q6 e-tron ('25) |- | 4 ||APA275 (Front) / APP580 (Rear)|| Electricity || All ||100 Kwh (gross) / 94.4 Kwh (net) || Audi Q6 e-tron quattro ('25), Q6 e-tron Sportback quattro ('25) |- | 5 ||APP550 (Rear) || Electricity || Rear ||82 Kwh (gross) / 77 Kwh (net) || Audi Q4 e-tron 45 ('25-'26) |- | 5 ||APA275 (Front) / APP580 (Rear)|| Electricity || All ||100 Kwh (gross) / 94.4 Kwh (net) || Audi SQ6 e-tron quattro ('25), SQ6 e-tron Sportback quattro ('25) |- | 8 || (Front) / (Rear) || Electricity || All ||105 Kwh (gross) / 97 Kwh (net) || Audi RS e-tron GT performance quattro ('25-'26) |- | 9 || (Front) / (Rear) || Electricity || All ||105 Kwh (gross) / 97 Kwh (net) || Audi S e-tron GT quattro ('25-'26) |} HASCO Magna=HASCO Magna Electric Drive Systems Co., Ltd. ===Position 6, Restraint Systems:=== *0 = Active (Manual) 3-point Seat Belts only *5 = Driver-side Airbag, Driver and Passenger Active (Manual) 3-point Seat Belts *8 = Driver and Passenger Front Airbags *2 = Active (Manual) belts plus Driver and Passenger Front Airbags & Front Side Airbags ('00-'06 TT) *4 = Active (Manual) belts plus Driver and Passenger Front Airbags & Front and Rear Side Airbags & Sideguard Side Curtain Airbags ('04-'07 A8) *5 = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front and Rear Side Airbags & Sideguard Side Curtain Airbags (A3, A4, A6, Allroad) *6 = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front Side Airbags & Sideguard Side Curtain Airbags ('06-'09 A3, A4, A6, Allroad) *3 = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front Side Airbags & Front Knee Airbags ('08-'09 TT, R8, '09 TTS) *4 = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front Side Airbags ('03-'09 A4 Cabriolet, '04-'09 S4 Cabriolet, '08 RS4 Cabriolet) *7 = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front Side Airbags & Sideguard Side Curtain Airbags *9 = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front and Rear Side Airbags & Sideguard Side Curtain Airbags (Except '08-'09 A8/S8) *9 = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front and Rear Side Airbags & Sideguard Side Curtain Airbags & Front Knee Airbags ('08-'09 A8/S8) *A = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front Side Airbags & Front Knee Airbags ('10- A5/S5 Cabriolet, '10- TT/TTS, '12-'13 TT RS, '10- R8) *A = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front Side Airbags & Sideguard Side Curtain Airbags ('10- A3, '10- A4/S4, '10-'11 A5/S5 Coupe, '10- A6/S6, '12- A7, '10- Q5, '10- Q7) *B = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front and Rear Side Airbags & Sideguard Side Curtain Airbags ('10- A3, '10- A4/S4, '10- A6/S6, '12- A7, '10- Q5, '10- Q7) *A = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front Side Airbags & Sideguard Side Curtain Airbags & Front Knee Airbags ('12- A5/S5 Coupe) *A = Active (Manual) belts plus Driver and Passenger Front Advanced Airbags & Front and Rear Side Airbags & Sideguard Side Curtain Airbags & Front Knee Airbags ('10-' A8) ===Position 7-8, Model Line:=== 1981-2009: *8P = A3 ('06-'09) *81 = 4000 Fwd ('81-'87) *85 = 4000 Quattro ('84-'87), Coupe ('81-'83), Coupe GT ('84-'87), Quattro ('82‡ & '83-'85) *89 = 80/90 ('88-'89) *8A = 80 ('90-'92), 90 ('90-'91) *8C = 90 ('93-'95) *8B = Coupe Quattro ('90-'91) *8G = Cabriolet ('94-'98) *8D = A4 ('96-'01), S4 ('00-'02) *8E = A4 ('02-'08), S4 ('04-'08), RS4 ('07-'08) *8H = A4 Cabriolet ('03-'09), S4 Cabriolet ('04-'09), RS4 Cabriolet ('08) *8K = A4 ('09) *8T = A5 coupe ('08-'09), S5 coupe ('08-'09) *43 = 5000 ('81-'83) *44 = 5000 ('84-'88), 100/200 ('89-'91) *4A = 100/S4 ('92-'94), A6 sedan ('95-'97), A6 wagon ('95-'98), S6 ('95 & '96-'97 in Canada) *4B = A6 sedan ('98-'04), A6 Avant wagon ('99-'04), Allroad ('01-'05), S6 ('02-'03), RS6 (US: '03, Canada: '04) *4F = A6 ('05-'09), S6 ('07-'09) *44 = V8 Quattro ('90) *4A = V8 Quattro ('91-'94) *4D = A8 ('97-'03), S8 ('01-'03) *4E = A8 ('04-'09), S8 ('07-'09) *8N = TT ('00-'06) *8J = TT ('08-'09), TTS ('09) *42 = R8 ('08-'09) *8R = Q5 ('09) *4L = Q7 ('07-'09) 2010-: *FM (Type 8P) = A3 ('10-'13) *FF (Type 8V) = A3 ('15-'20), S3 ('15-'20), RS3 ('17-'20), A3 Sportback e-tron [PHEV] '16-'18 *GY (Type 8Y) = A3/S3/RS3 ('22-) *FL (Type 8K) = A4 ('10-'16), Allroad ('13-'16), S4 ('10-'16) *F4 (Type 8W) = A4 ('17-'25), A4 Allroad ('17-'25), S4 ('18-'25) *FR (Type 8T) = A5 Coupe ('10-'17), S5 Coupe ('10-'17), RS5 Coupe ('13-'15) *FH (Type 8F) = A5 Cabriolet ('10-'17), S5 Cabriolet ('10-'17), RS5 Cabriolet ('13-'15) *F5 = A5 ('18-'25), S5 ('18-'25), RS5 ('18-'19, '21-'25) [Coupe/Cabriolet: '18-'24, Sportback: '18-'25] *FU = A5/S5 ('25-) *FB (Type 4F) = A6 ('10-'11), S6 ('10-'11) *FC (Type 4G) = A6 ('12-'18), S6 ('13-'18) *FC (Type 4G) = A7 ('12-'18), S7 ('13-'18), RS7 ('14-'18) *F2 (Type 4A) = A6 ('19-'25), S6 ('20-'25), RS6 Avant ('21-'26), A6 Allroad ('20-'26) *F2 (Type 4K) = A7 ('19-'25), S7 ('20-'25), RS7 ('21-'26) *FN = A6 ('26-) *GH = A6 e-tron, S6 e-tron ('25, '27) *FA (Type 4E) = A8 ('10) *FD (Type 4H) = A8 ('11-'18), S8 ('13-'16), S8 plus ('16-'18) *F8 (Type 4N) = A8 ('19-'26), S8 ('20-'26) *FW (Type F8) = e-tron GT ('22-'24), RS e-tron GT ('22-'24), S e-tron GT ('25-), RS e-tron GT performance ('25-) *FK (Type 8J) = TT ('10-'15), TTS ('10-'15), TT RS ('12-'13) *FV (Type FV or 8S) = TT ('16-'23), TTS ('16-'23), TT RS ('18-'22) *FG (Type 42) = R8 ('10-'12, '14-'15) *FX (Type 4S) = R8 ('17-'18, '20-'23) *FS (Type 8U) = Q3 ('15-'18) *F3 = Q3 ('19-'25) *FJ = Q3 ('26-) *FZ (Type F4) = Q4 e-tron, Q4 e-tron Sportback ('22-) *FP (Type 8R) = Q5 ('10-'17), SQ5 ('14-'17) *FY = Q5 ('18-'25), SQ5 ('18-'25), Q5 Sportback ('21-'25), SQ5 Sportback ('21-'25) *GU = Q5 ('25-'26), SQ5 ('25-'26), Q5 Sportback ('25-'26), SQ5 Sportback ('25-'26) *GF = Q6 e-tron, SQ6 e-tron, Q6 e-tron Sportback, SQ6 e-tron Sportback ('25, '27) *FE (Type 4L) = Q7 ('10-'15) *F7 (Type 4M) = Q7 ('17-), SQ7 ('20-) *F1 (Type 4M) = Q8 ('19-), SQ8 ('20-), RS Q8 ('20-) *GE = e-tron ('19, '21-'23), e-tron S ('22-'23), e-tron Sportback ('20-'23), e-tron S Sportback ('22-'23),<br> Q8 e-tron ('24), SQ8 e-tron ('24), Q8 e-tron Sportback ('24), SQ8 e-tron Sportback ('24) ===Position 9, Check Digit=== [[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]] Check Digit in 9th position of VIN was always used in US & Canada. In Europe, Check Digit in 9th position of VIN was adopted for 2002 model year. Prior to the 2002 model year, a letter Z was used in the 9th position of the VIN in Europe. ===Position 10, Model Year: === [[Vehicle Identification Numbers (VIN codes)/Model year|Model year]] ===Position 11, Production Plant:=== * A: Ingolstadt, Germany * B: Brussels, Belgium * D: Bratislava, Slovakia (VW Slovakia a.s. plant) * E: Emden, Germany (VW plant) * K: Rheine, Germany (Karmann plant: Cabriolet ['98], A4 Cabriolet ['03-'09], S4 Cabriolet ['04-'09], RS4 Cabriolet ['08] * N: Neckarsulm, Germany * P: Zwickau, Germany (VW plant) * R: Martorell, Spain (SEAT plant) * 1: Gyor, Hungary * 2: San Jose Chiapa, Puebla state, Mexico * 7: Heilbronn, Germany Other plant codes for non-North American models: * G: Graz, Austria (Steyr-Daimler-Puch plant: V8L) * U: Uitenhage, South Africa * X: Poznan, Poland * Z: Zuffenhausen, Germany (Porsche plant: RS2 Avant) * 3: Changchun, China (FAW-VW plant) * 4: Sao Jose dos Pinhais, Parana state, Brazil (Curitiba plant) * 9: Sarajevo, Bosnia and Herzegovina (Volkswagen Sarajevo d.o.o. plant) '''Positions 12–17, Serial Number''' {{BookCat}} m0inxbs10mpkxgrlj67q6vch5tjr2sl Cookbook:Ofada stew 102 483804 4679861 4679666 2026-11-04T00:51:17Z Kittycataclysm 3371989 flag 4679861 wikitext text/x-wiki {{Incomplete recipe|reason=missing links, missing categories, headers need to match template, procedure needs to match template}}{{Recipe summary | Name = Ofada stew | Cuisine = Nigerian cuisine | Origin = Southwestern Nigeria | Yield = 6plates | Servings = 4-6 people | Time = 2 hours | Difficulty = 3 | Image = [[File:Ofada Stew.jpg|300px]] }} {{recipe}} '''Ofada stew''' is a local dish which originated from the southern part of Nigeria. Ofada stew is otherwise known as ata dindin. It is a spicy, rich, and oily stew made from blended green peppers and bleached palm oil. It is common in southwestern Nigeria, especially among the Yoruba people, and is often served at parties and special occasions.<ref>{{Cite web |title=How to cook Ofada Stew (Ayamase) |url=https://www.allnigerianrecipes.com/stews/ofada-stew/ |access-date=2026-06-05 |website=All Nigerian Recipes |language=en-US}}</ref><ref>{{Cite web |last=Jemimah |first=Sisi |date=2015-12-08 |title=Obe Ata Dindin - Ofada Sauce |url=https://sisijemimah.com/2015/12/08/obe-ata-dindin-ofada-stew/ |access-date=2026-06-05 |website=Sisi Jemimah |language=en-GB}}</ref><ref>{{Cite web |last=O |first=Lois |date=2018-05-23 |title=How to Make Ofada Stew (Nigerian Ofada Sauce Recipe) |url=https://www.yummymedley.com/ofada-stew/ |access-date=2026-06-05 |website=Yummy Medley |language=en-US}}</ref> == Ingredients == === Pepper base === * 10–15 green bell [[Cookbook:Pepper|peppers]] (tatashe or mixed green peppers) * 3–5 scotch bonnet peppers (ata rodo) * 2 medium onions, chopped. === Protein === * Assorted [[Cookbook:Meat|meat]] ([[Cookbook:Beef|beef]], shaki, goat meat, ponmo) * [[Cookbook:Fish|Smoked fish (]]<nowiki/>optional) === Other ingredients === * 1/2 cup [[Cookbook:Palm Oil|palm oil]] (bleached) * 2 tablespoons [[Cookbook:Locust Bean|locust beans]] (iru) * 1–2 tablespoons ground [[Cookbook:Crawfish|crayfish]] (optional) * [[Cookbook:Salt|Salt]] to taste * 2–3 seasoning cubes == Preparation == === Step 1: Blend the peppers<ref>{{Cite web |last=Osinkolu |first=Lola |date=2025-04-07 |title=How to pepare Ayamase stew (ofada stew) |url=https://cheflolaskitchen.com/ayamase-stew-ofada-stew/ |access-date=2026-06-05 |website=Chef Lola's Kitchen |language=en-US}}</ref><ref>{{Cite web |last=Uguru |first=Chichi |date=2019-06-06 |title=The Real Ofada Stew Recipe |url=https://www.mydiasporakitchen.com/real-ofada-stew-recipe/ |access-date=2026-06-05 |website=My Diaspora Kitchen |language=en-US}}</ref> === *Wash and [[Cookbook:Blend|blend]] the green bell peppers, scotch bonnet, and one onion. The blend should not be too smooth; a slightly coarse texture is preferred. === Step 2: Prepare the meat === *Wash and season the assorted [[Cookbook:Meat|meat]] with [[Cookbook:Salt|salt]], [[Cookbook:Onion|onions]], and seasoning cubes. Boil until tender. *You may fry or grill the meat for extra flavor. === Step 3: Bleach the palm oil === *Heat the palm oil in a pot until it becomes lighter in color. Be careful not to overheat it. *Allow it to cool slightly before use. === Step 4: Cook the stew base === *Add chopped onions to the bleached oil. *Stir in locust beans and fry for a few minutes. *Add the blended pepper mix and cook until the water reduces and the oil begins to separate (about 20–30 minutes). === Step 5: Add meat and seasoning === *Add the cooked meat and smoked [[Cookbook:Fish|fish]]. *Season with salt, seasoning cubes, and [[Cookbook:Crawfish|crayfish]]. *Stir well and allow to simmer for 10–15 minutes. == Serving == Serve hot with: * [[Cookbook:Ofada rice|Ofada rice]] * White [[Cookbook:Rice|rice]] * [[Cookbook:Yam|Boiled yam]] or [[Cookbook:Plantain|plantain]] == Tips == * Locust beans (iru) is essential for authentic flavor. * Proper bleaching of palm oil gives the traditional Ofada taste. * The stew tastes even better the next day after the flavors have mixed well. == References == {{reflist}} [[Category:Nigerian recipes]] [[Category:Yoruba recipes]] [[Category:African recipes]] [[Category:recipes]] 6yaqh0u0a94224a8lisf472o1i9d3tt 4679878 4679861 2026-11-04T04:43:06Z MathsScienceNerd1 3626296 Undid revision [[Special:Diff/4679861|4679861]] by [[Special:Contributions/Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]]) // don't add incomplete template without prior information, this can be considered disruptive 4679878 wikitext text/x-wiki {{Recipe summary | Name = Ofada stew | Cuisine = Nigerian cuisine | Origin = Southwestern Nigeria | Yield = 6plates | Servings = 4-6 people | Time = 2 hours | Difficulty = 3 | Image = [[File:Ofada Stew.jpg|300px]] }} {{recipe}} '''Ofada stew''' is a local dish which originated from the southern part of Nigeria. Ofada stew is otherwise known as ata dindin. It is a spicy, rich, and oily stew made from blended green peppers and bleached palm oil. It is common in southwestern Nigeria, especially among the Yoruba people, and is often served at parties and special occasions.<ref>{{Cite web |title=How to cook Ofada Stew (Ayamase) |url=https://www.allnigerianrecipes.com/stews/ofada-stew/ |access-date=2026-06-05 |website=All Nigerian Recipes |language=en-US}}</ref><ref>{{Cite web |last=Jemimah |first=Sisi |date=2015-12-08 |title=Obe Ata Dindin - Ofada Sauce |url=https://sisijemimah.com/2015/12/08/obe-ata-dindin-ofada-stew/ |access-date=2026-06-05 |website=Sisi Jemimah |language=en-GB}}</ref><ref>{{Cite web |last=O |first=Lois |date=2018-05-23 |title=How to Make Ofada Stew (Nigerian Ofada Sauce Recipe) |url=https://www.yummymedley.com/ofada-stew/ |access-date=2026-06-05 |website=Yummy Medley |language=en-US}}</ref> == Ingredients == === Pepper base === * 10–15 green bell [[Cookbook:Pepper|peppers]] (tatashe or mixed green peppers) * 3–5 scotch bonnet peppers (ata rodo) * 2 medium onions, chopped. === Protein === * Assorted [[Cookbook:Meat|meat]] ([[Cookbook:Beef|beef]], shaki, goat meat, ponmo) * [[Cookbook:Fish|Smoked fish (]]<nowiki/>optional) === Other ingredients === * 1/2 cup [[Cookbook:Palm Oil|palm oil]] (bleached) * 2 tablespoons [[Cookbook:Locust Bean|locust beans]] (iru) * 1–2 tablespoons ground [[Cookbook:Crawfish|crayfish]] (optional) * [[Cookbook:Salt|Salt]] to taste * 2–3 seasoning cubes == Preparation == === Step 1: Blend the peppers<ref>{{Cite web |last=Osinkolu |first=Lola |date=2025-04-07 |title=How to pepare Ayamase stew (ofada stew) |url=https://cheflolaskitchen.com/ayamase-stew-ofada-stew/ |access-date=2026-06-05 |website=Chef Lola's Kitchen |language=en-US}}</ref><ref>{{Cite web |last=Uguru |first=Chichi |date=2019-06-06 |title=The Real Ofada Stew Recipe |url=https://www.mydiasporakitchen.com/real-ofada-stew-recipe/ |access-date=2026-06-05 |website=My Diaspora Kitchen |language=en-US}}</ref> === *Wash and [[Cookbook:Blend|blend]] the green bell peppers, scotch bonnet, and one onion. The blend should not be too smooth; a slightly coarse texture is preferred. === Step 2: Prepare the meat === *Wash and season the assorted [[Cookbook:Meat|meat]] with [[Cookbook:Salt|salt]], [[Cookbook:Onion|onions]], and seasoning cubes. Boil until tender. *You may fry or grill the meat for extra flavor. === Step 3: Bleach the palm oil === *Heat the palm oil in a pot until it becomes lighter in color. Be careful not to overheat it. *Allow it to cool slightly before use. === Step 4: Cook the stew base === *Add chopped onions to the bleached oil. *Stir in locust beans and fry for a few minutes. *Add the blended pepper mix and cook until the water reduces and the oil begins to separate (about 20–30 minutes). === Step 5: Add meat and seasoning === *Add the cooked meat and smoked [[Cookbook:Fish|fish]]. *Season with salt, seasoning cubes, and [[Cookbook:Crawfish|crayfish]]. *Stir well and allow to simmer for 10–15 minutes. == Serving == Serve hot with: * [[Cookbook:Ofada rice|Ofada rice]] * White [[Cookbook:Rice|rice]] * [[Cookbook:Yam|Boiled yam]] or [[Cookbook:Plantain|plantain]] == Tips == * Locust beans (iru) is essential for authentic flavor. * Proper bleaching of palm oil gives the traditional Ofada taste. * The stew tastes even better the next day after the flavors have mixed well. == References == {{reflist}} [[Category:Nigerian recipes]] [[Category:Yoruba recipes]] [[Category:African recipes]] [[Category:recipes]] e38q0gkwvz6gkdl163lkdphm4ppwtgs Cookbook:Scottish Porridge 102 484816 4679847 4654622 2026-11-03T20:42:35Z Kittycataclysm 3371989 style, format, language, links 4679847 wikitext text/x-wiki {{recipesummary | category = Breakfast recipes | Cuisine = Scottish | Origin = Scotland | servings = 1 | time = 25 minutes + 7–8 hours soaking | difficulty = 3 | image = }} __NOTOC__ {{recipe}} | [[Cookbook:Vegetarian cuisine|Vegetarian]] | [[Cookbook:Breakfast|Breakfast]] '''Scottish Porridge''' is a beloved traditional breakfast dish from Scotland. Traditionally, it doesn't use dairy and only consists of three ingredients: oats, salt, and water. This recipe follows the golden ratio of one parts oats to three parts water and uses an overnight pre-soaking method for steel-cut oats. The soaking helps reduce cooking time, and the oats are later simmered slowly. The end result is a creamy, satisfying porridge with a pleasant chewy texture. A variety of toppings can be added according to personal preferences, including berries, sliced banana, seeds, nuts, cinnamon, and a dollop of Greek yogurt.<ref>{{Cite news |last=Lam |first=Yvonne C. |date=2023-06-06 |title=No milk, no rolled oats and always add salt: how to make porridge like a champion |language=en-GB |work=The Guardian |url=https://www.theguardian.com/food/2023/jun/06/how-to-make-porridge-like-a-champion-toby-wilson-australian-chef-world-porridge-making-championship |access-date=2026-07-15 |issn=0261-3077}}</ref><ref>{{Cite web |last=Conte |first=Christina |date=2025-06-14 |title=Porridge Recipe (by a Porridge World Champion) |url=https://www.christinascucina.com/porridge/ |access-date=2026-07-15 |website=Authentic Italian & Scottish Recipes & Travel - Christina's Cucina |language=en-US}}</ref> ==Ingredients== * ½ [[Cookbook:Cup|cup]] (80 [[Cookbook:gram|g]]) steel-cut [[Cookbook:Oats|oats]], also called Irish oats * 1 teaspoon of [[Cookbook:Buckwheat|buckwheat]] flour (for reducing phytates) * 1½ cup (375 [[Cookbook:Milliliter|ml]]) warm water * 1 [[Cookbook:Teaspoon|teaspoon]] [[Cookbook:Lemon|lemon]] juice or apple cider [[Cookbook:Vinegar|vinegar]] * ⅛ teaspoon fine sea salt ==Procedure== #Mix the oats with the buckwheat flour in a bowl. #Add the water and lemon juice. Cover and allow to soak overnight or at least 7–8 hours. #Place the oat mixture into a small saucepan along with the salt, and gently bring it to a small [[Cookbook:Boiling|boil]], stirring occasionally until the porridge starts to thicken. #Once the thickening has begun, lower the heat to low to avoid burning the porridge and allow it to [[Cookbook:Simmering|simmer]] for approximately 15–20 minutes (or less if the oats are tender and have reached your preferred consistency). #Remove from the heat and let it stand for 1–2 minutes before serving. #Serve with your choice of toppings, such as chia seeds, walnuts, tablespoon of peanut butter, berries, cinnamon, or a dollop of Greek yogurt. ==Notes, tips, and variations== * Traditionalists uses whole-oat groats and mill them to make Scottish porridge. However store bought steel-cut oats are a reliable substitute for those who do not possess a mill. If you possess a mill and desire the authentic Scottish taste, you can swap steel-cut oats and use milled whole-oat groats instead. * Pre-soaking is essential to achieve a soft, velvety texture as it helps break down starches in oats and soften its hearty outer hull. * To reduce phytates in oats, you should add both an acidic medium and a phytase-rich ingredient to your soaking liquid, This can be achieved by adding a teaspoon of buckwheat flour and a teaspoon of apple cider vinegar. * Ideally you should start your soak with warm water (but not boiling as that kills enzymes) and leave it out to soak at room temperature for 16 to 24 hours. However, a shorter 8 to 12 hours can still significantly reduce anti-nutrients and make your breakfast much easier on your stomach. *After soaking, rinsing reduces starch, apple cider vinegar or lemon juice, and any available pesticide residue. If you are using organic oats and want maximum nutrition and creaminess, you can skip the rinse. * Always cover the bowl with cling wrap when soaking oats. This is to both to keep out potential contaminants (brought in by outside flies, dusts, bad bacteria, etc), as well as keeping the oats from drying out by preventing the evaporation of the top layer of water. If top oats are exposed to air and are dried out, they will be unable to benefit from buckwheat enzymes. * Salt is essential to a good Scottish porridge as it brings out the earthy flavor of the oats. There is however a difference in opinion on when it is best to add in the salt. Some argue that it's better to add a pinch halfway through cooking whilst others believe it's best added at the very beginning of the cooking process. Feel free to experiment and choose the one that you prefer though it is just a myth that oats cannot cook properly if you add salt in very early. * When serving, try to opt for shallow bowls as they help quickly cool down the porridge evenly whereas deeper bowls tend to keep the centre of the porridge dangerously hot. * Opt to start with cold water for cooking. Avoid cooking with milk as milk sugars tend to both mask the clean grain taste and it scorches easily. ==References== [[Category:Scottish recipes|Scottish porridge]] [[Category:Breakfast recipes]] [[Category:Vegetarian recipes]] [[Category:Recipes using oat]] [[Category:Boiled recipes]] [[Category:Recipes with metric units]] <references /> [[Category:Recipes using buckwheat]] [[Category:Recipes using lemon juice]] [[Category:Recipes using vinegar]] [[Category:Recipes using salt]] o0sqlak5y8gbcgbkv4hkx4r66j2prb1 General Literary Chinese from Scratch/Oh, the Qilin! 0 485046 4679903 4670717 2026-11-04T07:18:49Z Shira the Mogul 3560559 4679903 wikitext text/x-wiki [[File:Chinese - Dragon - Walters 492425 - Profile.jpg|thumb|200px|麒麟]] In this lesson, you will learn your first ode from the ''Classic of Poetry'' 詩經,a foundational text for much of East Asian culture. It is among the earliest sources of Classical Chinese and is also the most quoted. We will go over the genres and exact details in a later unit. ==Pre-Reading== This poem focuses on the Qilin 麒麟, a mythical creature you may have heard about. Let's consult Shuowen Jiezi about it. <blockquote> 麒:仁獸也。麋身牛尾,一角。从鹿其聲。<br> 麟:大牝鹿也。从鹿粦聲。 </blockquote> Think you can follow it? Use Yomitan for words you aren't sure about! What do you know about the Qilin? Have you seen it in any video games or other media? How about the ''Kirin'' in, say, ''Monster Hunter''? Yep, that is the same animal! ==Text== ===國風·周南·麟之趾=== <poem> 麟之趾,振振公子,吁嗟麟兮。{{efn|于 is how 吁 was originally written, but I have replaced it for clarity. 吁 is what the word ''is'' and how it is pronounced.}} 麟之定,振振公姓,吁嗟麟兮。 麟之角,振振公族,吁嗟麟兮。 </poem> Do you remember how 之 works here? ===Gloss=== * 振振 - Benevolent and generous; * 吁嗟 - Purely phonetic; like "Oh, the Qilin~!" * 兮 - Likewise. * 趾 - Feet * 定 - Head * 角 - Horn * 公 - Duke * 姓 - Descendant * 族 - Kin-group, families ==Commments== Poems in the ''Classic of Poetry'' rhymed in a very old form of Chinese, during a time before the tones it is known for today existed. This has led to it becoming a massive part of study on how the spoken language of the time, "Old Chinese," sounded. It was, and is, extremely helpful. ==Exercise== Reflect on the verse. # How do you think it comes across to you? # What do you think it is trying to say? # Think of animals you have learned about in the previous lessons. Can you write something similar about them, with the structures seen in this poem? ==Notes== {{notelist}} ==References== * 《毛詩》 * 《毛詩故訓傳定本》 * Deng, Q. (2013). 诗经 [Classic of Poetry] (Q. Kong, Ed.; 2nd ed, Vols 1–2). 东南大学出版社 [Southeast University Press]. * Pulleyblank, E. G. (2014). Middle Chinese: A Study in Historical Phonology. UBC Press. * Pulleyblank, E. G. (2000). Outline of classical Chinese grammar (Repr). UBC Press. {{BookCat}} pgoavd2xkqchfbaa6cnjo0z2igb9irv 4679905 4679903 2026-11-04T07:20:02Z Shira the Mogul 3560559 4679905 wikitext text/x-wiki [[File:Chinese - Dragon - Walters 492425 - Profile.jpg|thumb|200px|麒麟]] [[Statue of Qilin, Tielu Temple 2023030501.jpg|thumb|200px|麒麟]] In this lesson, you will learn your first ode from the ''Classic of Poetry'' 詩經,a foundational text for much of East Asian culture. It is among the earliest sources of Classical Chinese and is also the most quoted. We will go over the genres and exact details in a later unit. ==Pre-Reading== This poem focuses on the Qilin 麒麟, a mythical creature you may have heard about. Let's consult Shuowen Jiezi about it. <blockquote> 麒:仁獸也。麋身牛尾,一角。从鹿其聲。<br> 麟:大牝鹿也。从鹿粦聲。 </blockquote> Think you can follow it? Use Yomitan for words you aren't sure about! What do you know about the Qilin? Have you seen it in any video games or other media? How about the ''Kirin'' in, say, ''Monster Hunter''? Yep, that is the same animal! ==Text== ===國風·周南·麟之趾=== <poem> 麟之趾,振振公子,吁嗟麟兮。{{efn|于 is how 吁 was originally written, but I have replaced it for clarity. 吁 is what the word ''is'' and how it is pronounced.}} 麟之定,振振公姓,吁嗟麟兮。 麟之角,振振公族,吁嗟麟兮。 </poem> Do you remember how 之 works here? ===Gloss=== * 振振 - Benevolent and generous; * 吁嗟 - Purely phonetic; like "Oh, the Qilin~!" * 兮 - Likewise. * 趾 - Feet * 定 - Head * 角 - Horn * 公 - Duke * 姓 - Descendant * 族 - Kin-group, families ==Commments== Poems in the ''Classic of Poetry'' rhymed in a very old form of Chinese, during a time before the tones it is known for today existed. This has led to it becoming a massive part of study on how the spoken language of the time, "Old Chinese," sounded. It was, and is, extremely helpful. ==Exercise== Reflect on the verse. # How do you think it comes across to you? # What do you think it is trying to say? # Think of animals you have learned about in the previous lessons. Can you write something similar about them, with the structures seen in this poem? ==Notes== {{notelist}} ==References== * 《毛詩》 * 《毛詩故訓傳定本》 * Deng, Q. (2013). 诗经 [Classic of Poetry] (Q. Kong, Ed.; 2nd ed, Vols 1–2). 东南大学出版社 [Southeast University Press]. * Pulleyblank, E. G. (2014). Middle Chinese: A Study in Historical Phonology. UBC Press. * Pulleyblank, E. G. (2000). Outline of classical Chinese grammar (Repr). UBC Press. {{BookCat}} 64e68qjgsl9x9jait2iv0ievimnoiz1 4679906 4679905 2026-11-04T07:20:10Z Shira the Mogul 3560559 4679906 wikitext text/x-wiki [[File:Chinese - Dragon - Walters 492425 - Profile.jpg|thumb|200px|麒麟]] [[File:Statue of Qilin, Tielu Temple 2023030501.jpg|thumb|200px|麒麟]] In this lesson, you will learn your first ode from the ''Classic of Poetry'' 詩經,a foundational text for much of East Asian culture. It is among the earliest sources of Classical Chinese and is also the most quoted. We will go over the genres and exact details in a later unit. ==Pre-Reading== This poem focuses on the Qilin 麒麟, a mythical creature you may have heard about. Let's consult Shuowen Jiezi about it. <blockquote> 麒:仁獸也。麋身牛尾,一角。从鹿其聲。<br> 麟:大牝鹿也。从鹿粦聲。 </blockquote> Think you can follow it? Use Yomitan for words you aren't sure about! What do you know about the Qilin? Have you seen it in any video games or other media? How about the ''Kirin'' in, say, ''Monster Hunter''? Yep, that is the same animal! ==Text== ===國風·周南·麟之趾=== <poem> 麟之趾,振振公子,吁嗟麟兮。{{efn|于 is how 吁 was originally written, but I have replaced it for clarity. 吁 is what the word ''is'' and how it is pronounced.}} 麟之定,振振公姓,吁嗟麟兮。 麟之角,振振公族,吁嗟麟兮。 </poem> Do you remember how 之 works here? ===Gloss=== * 振振 - Benevolent and generous; * 吁嗟 - Purely phonetic; like "Oh, the Qilin~!" * 兮 - Likewise. * 趾 - Feet * 定 - Head * 角 - Horn * 公 - Duke * 姓 - Descendant * 族 - Kin-group, families ==Commments== Poems in the ''Classic of Poetry'' rhymed in a very old form of Chinese, during a time before the tones it is known for today existed. This has led to it becoming a massive part of study on how the spoken language of the time, "Old Chinese," sounded. It was, and is, extremely helpful. ==Exercise== Reflect on the verse. # How do you think it comes across to you? # What do you think it is trying to say? # Think of animals you have learned about in the previous lessons. Can you write something similar about them, with the structures seen in this poem? ==Notes== {{notelist}} ==References== * 《毛詩》 * 《毛詩故訓傳定本》 * Deng, Q. (2013). 诗经 [Classic of Poetry] (Q. Kong, Ed.; 2nd ed, Vols 1–2). 东南大学出版社 [Southeast University Press]. * Pulleyblank, E. G. (2014). Middle Chinese: A Study in Historical Phonology. UBC Press. * Pulleyblank, E. G. (2000). Outline of classical Chinese grammar (Repr). UBC Press. {{BookCat}} bok5d6r6uk6l7zsifg898nimnlt0lg0 4679907 4679906 2026-11-04T07:20:47Z Shira the Mogul 3560559 /* Exercise */ 4679907 wikitext text/x-wiki [[File:Chinese - Dragon - Walters 492425 - Profile.jpg|thumb|200px|麒麟]] [[File:Statue of Qilin, Tielu Temple 2023030501.jpg|thumb|200px|麒麟]] In this lesson, you will learn your first ode from the ''Classic of Poetry'' 詩經,a foundational text for much of East Asian culture. It is among the earliest sources of Classical Chinese and is also the most quoted. We will go over the genres and exact details in a later unit. ==Pre-Reading== This poem focuses on the Qilin 麒麟, a mythical creature you may have heard about. Let's consult Shuowen Jiezi about it. <blockquote> 麒:仁獸也。麋身牛尾,一角。从鹿其聲。<br> 麟:大牝鹿也。从鹿粦聲。 </blockquote> Think you can follow it? Use Yomitan for words you aren't sure about! What do you know about the Qilin? Have you seen it in any video games or other media? How about the ''Kirin'' in, say, ''Monster Hunter''? Yep, that is the same animal! ==Text== ===國風·周南·麟之趾=== <poem> 麟之趾,振振公子,吁嗟麟兮。{{efn|于 is how 吁 was originally written, but I have replaced it for clarity. 吁 is what the word ''is'' and how it is pronounced.}} 麟之定,振振公姓,吁嗟麟兮。 麟之角,振振公族,吁嗟麟兮。 </poem> Do you remember how 之 works here? ===Gloss=== * 振振 - Benevolent and generous; * 吁嗟 - Purely phonetic; like "Oh, the Qilin~!" * 兮 - Likewise. * 趾 - Feet * 定 - Head * 角 - Horn * 公 - Duke * 姓 - Descendant * 族 - Kin-group, families ==Commments== Poems in the ''Classic of Poetry'' rhymed in a very old form of Chinese, during a time before the tones it is known for today existed. This has led to it becoming a massive part of study on how the spoken language of the time, "Old Chinese," sounded. It was, and is, extremely helpful. ==Exercise== Reflect on the verse. # How do you think it comes across to you? # What do you think it is trying to say? * It talks about a 角, but the statue on the right doesn't have one, does it? Why do you think that is? # Think of animals you have learned about in the previous lessons. Can you write something similar about them, with the structures seen in this poem? ==Notes== {{notelist}} ==References== * 《毛詩》 * 《毛詩故訓傳定本》 * Deng, Q. (2013). 诗经 [Classic of Poetry] (Q. Kong, Ed.; 2nd ed, Vols 1–2). 东南大学出版社 [Southeast University Press]. * Pulleyblank, E. G. (2014). Middle Chinese: A Study in Historical Phonology. UBC Press. * Pulleyblank, E. G. (2000). Outline of classical Chinese grammar (Repr). UBC Press. {{BookCat}} 5nw5vtymf3zxqehbccyv6otx5aqilga 4679908 4679907 2026-11-04T07:20:56Z Shira the Mogul 3560559 /* Exercise */ 4679908 wikitext text/x-wiki [[File:Chinese - Dragon - Walters 492425 - Profile.jpg|thumb|200px|麒麟]] [[File:Statue of Qilin, Tielu Temple 2023030501.jpg|thumb|200px|麒麟]] In this lesson, you will learn your first ode from the ''Classic of Poetry'' 詩經,a foundational text for much of East Asian culture. It is among the earliest sources of Classical Chinese and is also the most quoted. We will go over the genres and exact details in a later unit. ==Pre-Reading== This poem focuses on the Qilin 麒麟, a mythical creature you may have heard about. Let's consult Shuowen Jiezi about it. <blockquote> 麒:仁獸也。麋身牛尾,一角。从鹿其聲。<br> 麟:大牝鹿也。从鹿粦聲。 </blockquote> Think you can follow it? Use Yomitan for words you aren't sure about! What do you know about the Qilin? Have you seen it in any video games or other media? How about the ''Kirin'' in, say, ''Monster Hunter''? Yep, that is the same animal! ==Text== ===國風·周南·麟之趾=== <poem> 麟之趾,振振公子,吁嗟麟兮。{{efn|于 is how 吁 was originally written, but I have replaced it for clarity. 吁 is what the word ''is'' and how it is pronounced.}} 麟之定,振振公姓,吁嗟麟兮。 麟之角,振振公族,吁嗟麟兮。 </poem> Do you remember how 之 works here? ===Gloss=== * 振振 - Benevolent and generous; * 吁嗟 - Purely phonetic; like "Oh, the Qilin~!" * 兮 - Likewise. * 趾 - Feet * 定 - Head * 角 - Horn * 公 - Duke * 姓 - Descendant * 族 - Kin-group, families ==Commments== Poems in the ''Classic of Poetry'' rhymed in a very old form of Chinese, during a time before the tones it is known for today existed. This has led to it becoming a massive part of study on how the spoken language of the time, "Old Chinese," sounded. It was, and is, extremely helpful. ==Exercise== Reflect on the verse. # How do you think it comes across to you? # What do you think it is trying to say? # It talks about a 角, but the statue on the right doesn't have one, does it? Why do you think that is? # Think of animals you have learned about in the previous lessons. Can you write something similar about them, with the structures seen in this poem? ==Notes== {{notelist}} ==References== * 《毛詩》 * 《毛詩故訓傳定本》 * Deng, Q. (2013). 诗经 [Classic of Poetry] (Q. Kong, Ed.; 2nd ed, Vols 1–2). 东南大学出版社 [Southeast University Press]. * Pulleyblank, E. G. (2014). Middle Chinese: A Study in Historical Phonology. UBC Press. * Pulleyblank, E. G. (2000). Outline of classical Chinese grammar (Repr). UBC Press. {{BookCat}} l1x41nrzpgbw0n757n6zkq4hdsjlqlp Electric Tractor 0 485500 4679845 4677368 2026-11-03T20:35:07Z Kittycataclysm 3371989 +template 4679845 wikitext text/x-wiki {{New book}} '''This page is for the BCS 201 Electric Rototiller made for Farmship Growers Cooperative/Haliburton Community Organic Farm.''' The design of the tiller system was inspired by Reid Allaway of Tournesol cooperative, Reid runs the DIY electric farmer facebook group, that is a good place to find out about electric tractors. The system is based around the following information The motor, the motor is permanent magnet synchronous machine motor ME1509 from Motoenergy, an american company. PMSM are highly efficient when run at the correct RPM and torque, the diagram for the me1509 is not available though this one form the me1507 shows the idea https://www.thunderstruck-ev.com/images/companies/1/ME1507dyno.pdf?1518651550248 the me1507 when run at 5000 rpm would be 100% efficient meaning that electrical power inputed would be fully applied as output power at the shaft. The BCS 201 has a reduction gear box, 12:75 or ~ 7:1 reduction. The output RPM for a tiller should be about 540 rpm so with a 7:1 gear ratio 3780. I.e. the motor used should have high efficiency at 3780 RPM the motenergy 1509 is efficient in the range of 2500-3500 rpm so an ideal motor. The power of the motor is determined by how much heat it can disappate as well as the input power. In theory since the windings of a motor are low resistance you can put as much energy into the motor as you would like, but it shouldn't overheat and melt the windings. So the motor power is essentially power in keeping in mind the rate at which the motor dissapates energy. So when making garden beds, check that the motor is not above ~70 C. It should feel warm but not feel like it is burning. It is possible to put a cycleanalyst display on the motor that can read the motor temperature as their is a sensor in the motor. The battery for the electric tractor should output sufficent power to provide the necessary torque for doing the job at the tines. The gas motors on rototillers are typically 5-10 hp, a 5000 watt motor will output approximately 5.6 hp so in the correct range. At 3600 rpm the torque of 5000 watts motor (torque = power/RPM) is 13Nm, with the 7:1 reduction gear and an efficiency factor of .8 72.8Nm so in theory the 5kw motor will deliver the torque required. Reid Allaway designed a similar tiller and found that the motor was adequate to do the job with a kelly motor controller that delivers peak amps of 200. So a 48 volt battery (potential) with 100 ah (capacity) that can run at 2C (rate) will deliver 4000-8000 watts of power to the motor drive shaft (efficiency factor of .8 included) The motor controller used in this project is a Cheetah motor controller. It is sinuoisdal brushless DC motor controller meaning it works from a computerized programming detecting the magnetic fields of the motor and not using commutator brushes. The control circuit is relatively simple as outlined [https://media.kellycontroller.com/new/Kelly-Cheetah-series-KLS-SUserManual.pdf Kelly Cheetah Motor Controller Guide] you can see on page 13 of the manual the circuit for connecting the motor controller to the motor Important elements are a 200 amp fuse on the positive line of the controller that prevents overcurrent. The next element is a contactor that is has a coil that closes the circuit to the battery this is then connected to the battery pack and on the negative side of the pack to the low voltage.. The positive of the battery pack is also connected to a key witch then when closed powers the controller as well as the contactor coil. There's also the hall sensor connections to the motor which are the power, the three sensor signals and the ground. Their is a directional switch which is determines the direction of the motor and a throttle and diode on the contactor coil which prevents current flow in reverse direction on the power input of the controller In practice the circuit that runs the motor had two important glitches, first was proper electrical crimps, the kelly contoller connects are automotive connectors '''they should be crimped by having the wire at the first set of tongs and the bare wire at the second, the covered wire secures the crimp in place and the bare wire connects. One of the connectors is currently partially loose and should be plug and secured tightly to start up the tractor. This will need to be repeated all connections are secure.''' The motor itself is connected to the gearbox by an adaptor plate, the motor driveshaft should be centered on the bearing exactly, this is tricky if you try as I did to line up the holes with measurement of the bolt holes, what worked was to machine the motor coupler to fit between the bearing and the motor shaft thus perfectly centering the plate. The motor is bolted to the plate by machining a square hole in the plate with the milling machine sufficiently wide to accommodate the motor shaft bolting the motor to the plate, the alignment occurs by aligning the plate to the gearbox pretty much at any angle but square is sastifying. '''Because the electronics are currently too close to the ground a new adaptor plate will need to be machined with the plate to the side. Motor connections need to contained with a sock that is sewed.\''' '''Battery Frame''' The frame was built in a bit of slipshod manner by bolting together. A key idea is to have battery swap allowing for extended work times by swapping batteries. The current situation is a 15 amp charger that can charge the 100 ah battery in ~ 7 hours a level '''a 32 amp level 2 charger could be installed on farmships current electrical system''', this would allow for full charge in just over three hours, a system like this could also charge 4 batteries on an overnight charge that would allow for 4 hours of working time during the day. It would be possible to carry '''two batteries''' on the tractor at once. '''The comment was the center of mass of the tractor was too high. Rotating the battery 90 degrees would help or two batteries on either side of the tractor would also be possible''' '''Motor drive shaft''' You can look at the drawings from the tractor manufacturer to see inside the gearbox. In the case of the BCS 201 their was a large reduction gear that connects to the motor driveshaft. Gear The first thing to do is to calculate the module of the gear. Module is the ratio of the diameter of the gear to the number of teeth. (m=d/z) (d in millimetres) If you think about the relationship circumference = pi*d this gives you the idea that the module is essentially the inverse of the number of teeth per millimeter of circumference divided by pi. this is confusing to me as well, but what I am trying to say is that for two gears to mesh they should have the same module. I initially 3d printed a gear that I designed in cad, problem with this is that it sheared apart immediately after applying the motor torque. Theirs also the pressure angle of the gear, which is the angle between the circumference tangent and the gear tooth profile, essentially the sharpness of the gear. It should again match as close as possible. In the end I purchased a gear from aliexpress that was module 2 twelve teeth with pressure angle 20 that is standard. I'll come back to the gear Shaft The shaft is the simplest part, to extend the motor driveshaft you need a piece of keyed motor stock that is the same diameter of your motor axle, it can be to length to fit inside the gearbox, thiniking of it now I realize the original motor shaft was resting on a bearing to increase strength, something that I didn't achieve by shortening the shaft, '''probably should lengthen the drive shaft to rest on the bearing on the far side of gearbox.''' Coupler Coupler, the standard way of attaching a coupler is with a set screw from the side, pressumably into the keyed shaft. I'll get to this soon but basically we machined the coupler to fit in the bearing of the gearbox so tight that it didn't slip, put a key in the motor shaft and axle and then spot welded motor shaft to the coupler, not pretty but hey it worked. {{shelves}} 7yf0fx0ssyadx2vwra312zpl5gpbn5m General Literary Chinese from Scratch/Eating like a Zhou Aristocrat 0 485502 4679900 4669550 2026-11-04T07:01:19Z Shira the Mogul 3560559 4679900 wikitext text/x-wiki Have you ever tried Asian food? Ramen 拉麵? Hotpot 火鍋? Rice 米? Of course you have! Well, Literary Chinese has plenty of recipe books in it. This time, I want you to get up and try making something nice and simple that the Zhou literati would make. Get out your frying pan! ==Recipe== This recipe is from the ''Record of Social Conduct'' 禮記, a Zhou-Han text that records the culture of the Zhou dynasty. <blockquote> 糝:取牛羊豕之肉,三如一小切之,與稻米;稻米二肉一,合以為餌煎之。 </blockquote> <!--- highlight 三如一小切 and 稻米二肉一 specifically ---> Here, you will see two uses for 之, a swiss-army knife in Literary Chinese: * Linking adjectives to nouns: 牛羊豕之肉; the meat '''of''' three animals you saw last lesson! * An all-purpose "it", used after a verb. 煎之 - fry it! Let's look at the key verbs here: # 取 - Take # 切 - Cut # 與 - With; in-context, mix... # 合 - Combine # 煎 - Fry We see 三如一 here too, where 如 is "equal to." This is a useful function word. Here, then, it would be "take 3 as 1". That said, I daresay you may be able to follow this recipe. There are no quantities or anything: Just go with your gut! They sure did! ==Comments== It seems that in this recipe, the rice is used as a sort of batter, to ensure that the game meat the Zhou hunted would not dry out during cooking. Unlike the domestic animals we have today, animals back then were mostly muscle, with little fat, so there was no barrier to protect what is under the fat from heat. The Zhou people would hunt aurochs, birds, rams, boar, short-horned water buffalo (白兕), and more! Many recipes in the ''Record of Social Conduct'' contain pickling, with words like 醢 and 醯 describing it. You can preserve meat for a very long time this way, without the need for freezing and other preservatives. Perhaps try doing it yourself, or even trying to get inspiration for other recipes from there! You truly won't find many recipes there anywhere else. ==Examples of recipe books== If you are interested in finding more recipes to follow, I must recommend these texts: * 山家清供(南宋) * 雲林堂飲食制度集(元) * 本心齋食譜(明) * 屠門大嚼(朝鮮) ==Cangjie codes== * 糝: 火木戈戈竹 (FDIIH) * 取: 尸十水 (SJE) * 牛: 竹手 (HQ) * 羊: 廿手 (TQ) * 豕: 一尸竹人 (MSHO) * 之: 戈弓人 (INO) * 肉: 人月人 (OBO) * 三: 一一一 (MMM) * 如: 女口 (VR) * 小: 弓金 (NC) * 切: 心尸竹 (PSH) * 與: 竹難卜金 (HXYC) * 稻: 竹木月竹難 (HDBHX) * 米: 火木 (FD) * 二: 一一 (MM) * 合: 人一口 (OMR) * 以: 女戈人 (VIO) * 為: 戈大弓火 (IKNF) * 餌: 人戈尸十 (OISJ) * 煎: 廿月弓火 (TBNF) * 禮: 戈火廿田廿 (IFTWT) * 記: 卜口尸山 (YRSU) * 內: 人月 (OB) * 則: 月金中弓 (BCLN) ==References== * 《禮記·內則》 {{BookCat}} 2gy7jwhncsdc2ti3elqrmfs0206k1n0 A-level Computing AQA Paper 1 Skeleton program 2027 0 485519 4679788 4679735 2026-11-03T13:35:08Z Fware404 3630157 Accredited Python Solutions/Fixes 4679788 wikitext text/x-wiki {{soft redirect|v:en:A-level Computer Science AQA Paper 1 Skeleton program 2027}} == Section C Mark distribution comparison == Mark distribution for this year: The 2027 paper 1 will contain The 2026 paper 1 contained 5 questions worth 3, 2, 5, 2 and 1 mark(s) (13 total). The 2025 paper contained 4 questions worth 2 marks each (8 total). The 2024 paper contained 3 questions worth 11 marks in total (3+2+6=11). The 2023 paper contained 6 questions worth 13 marks The 2022 paper contained 5 questions worth 17 marks. The 2021 paper contained 4 questions worth 13 marks. == Section C Predictions == '''Predictions:''' == Section D Mark distribution comparison == Mark distribution for this year: * The 2027 paper 1 contains These marks include the screen capture(s), so the marks for the coding will be 1-2 marks lower. * The 2026 paper 1 contains 4 questions: a 5 mark, an 8 mark and two 12 mark questions. * The 2025 paper 1 contained 4 questions: a 5 mark, a 6 mark and two 14 mark questions. * The 2024 paper 1 contained 4 questions: a 5 mark, a 6 mark and two 14 mark questions. * The 2023 paper 1 contained 4 questions: a 5 mark, a 9 mark, a 10 mark and one 13 mark question. * The 2022 paper 1 contained 4 questions: a 5 mark, a 9 mark, a 11 mark and one 13 mark question. * The 2021 paper 1 contained 4 questions: a 6 mark, an 8 mark, a 9 mark and one 14 mark question. * The 2020 paper 1 contained 4 questions: a 6 mark, an 8 mark, a 11 mark and one 12 mark question. * The 2019 paper 1 contained 4 questions: a 5 mark, an 8 mark, a 9 mark and one 13 mark question. * The 2018 paper 1 contained 5 questions: a 2 mark, a 5 mark, two 9 mark and one 12 mark question. * The 2017 paper 1 contained 5 questions: a 5 mark, three 6 mark and one 12 mark question. == Section D Predictions == === '''Q1: Write code to utilize Bonus when a player clears a pile, or use TurnsSinceMatch to trigger a board reshuffle when players get stuck.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q2: Modify board creation or grid coordinate calculations to validate that board sizes loaded from external files form valid square dimensions.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q3: Refactor Pile.GetSymbolOfTopTile() to return a fallback character (e.g., ' ' or '?') or throw a defensive guard check if the pile is empty.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q4: Modify TilesCS.Main() so that when setting up a default game, the user is prompted to enter a custom target score (MaxScore) rather than using the hardcoded value of 10.'''=== {{CPTAnswerTab|C#}} GK - Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> if (UseDataFromFile == false) { Players.Add(new Player("Player 1", 0)); Players.Add(new Player("Player 2", 0)); for (int Count = 1; Count <= 36; Count++) { Pile P = new Pile(3, 0); P.Add(new Tile('A', 1)); P.Add(new Tile('B', 2)); P.Add(new Tile('A', 1)); Board.Add(P); } //start change Console.WriteLine("Enter a target score"); MaxScore = int.Parse(Console.ReadLine()); //end change } </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> if UseDataFromFile == False: Players.append(Player("Player 1", 0)) Players.append(Player("Player 2", 0)) for Count in range(1, 37): P = Pile(3, 0) P.Add(Tile("A", 1)) P.Add(Tile("B", 2)) P.Add(Tile("A", 1)) Board.append(P) # -- Start Changes -- MaxScoreInput=input("Enter a max score: ") if type(MaxScoreInput)==int: MaxScore=MaxScoreInput else: print("Using default max score (10)") # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q5: Update the DisplayScores() method in Game so that in addition to printing player scores, it prints which player is currently winning or states that the game is currently a tie.'''=== {{CPTAnswerTab|C#}} GK - Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> private void DisplayScores() { Console.WriteLine(); foreach (Player P in Players) { Console.WriteLine($"{P.GetName()}: has a score of {P.GetScore()}"); } //start change if (Players[1].GetScore() > Players[0].GetScore()) { Console.WriteLine($"{Players[1].GetName()} is winning"); } else if (Players[1].GetScore() < Players[0].GetScore()) { Console.WriteLine($"{Players[0].GetName()} is winning"); } else if (Players[1].GetScore() == Players[0].GetScore()) { Console.WriteLine("The game is currently a tie."); } //end change Console.WriteLine(); } </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def __DisplayScores(self): print() for P in self.__Players: print(f"{P.GetName()}: has a score of {P.GetScore()}") print() # -- Start Changes -- if self.__Players[0]._Score>self.__Players[1]._Score: print(f"{self.__Players[0].GetName} Is winning") elif self.__Players[0]._Score<self.__Players[1]._Score: print(f"{self.__Players[1].GetName} Is winning") else: print("Both players are tied") # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q6: Add a method CountTotalTiles() to the Game class that counts and returns the total number of tiles remaining across all piles on the board. Display this total when the board is displayed ('B'). '''=== {{CPTAnswerTab|C#}} GK - Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> //total number of tiles //start change private int CountTotalTiles() { int total = 0; for (int i = 0; i < Board.Count; i++) { total += Board[i].GetNumberOfTiles(); } return total; } //end change DisplayMenu(); Choice = GetChoice(); if (Choice == "B") { DisplayBoard(); //start change Console.WriteLine($"Total number of tiles {CountTotalTiles()}"); //end change } </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q7: Modify ChoosePile() in the Game class to validate that both user-entered X and Y coordinates fall within valid grid boundaries (1 \le x {GridSize} and 1 \le y \le{GridSize}) before calculating the index.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q8: The Pile class contains an unused Bonus field. Add a method GetAndClearBonus() to Pile that returns the bonus value and resets it to 0. Update PlayGame() in Game so that when a matching pair is found, any bonus points from the two chosen piles are added to the player's score.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q9: Extend the Player class to keep track of how many successful matching pairs each player has made during the game. Display this count in DisplayScores().'''=== {{CPTAnswerTab|C#}} JO: Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> JO // START CHANGE class Player protected int SuccessMatches = 0; public virtual void NumberOfSuccessfulMatches() { SuccessMatches++; } public virtual int ReturnMatches() { return SuccessMatches; } //END CHANGE //START CHANGE DisplayScores Console.WriteLine($"{Players[0].GetName()} has {Players[0].ReturnMatches()} successful matches"); Console.WriteLine($"{Players[1].GetName()} has {Players[1].ReturnMatches()} successful matches"); // END CHANGE </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): # Code Omitted ScoreIncrease += Tile1.GetPoints() + Tile2.GetPoints() self.__Players[self.__WhoseTurn].ChangeScore(ScoreIncrease) # -- Start Changes : PlayGame -- self.__Players[self.__WhoseTurn].match() # -- End Changes -- def __DisplayScores(self): print() for P in self.__Players: # -- Start Changes : __DisplayScores -- print(f"{P.GetName()}: has a score of {P.GetScore()} with {P.GetSuccessfulPairs()} Successful Pair(s)") # -- End Changes -- print() # -- Start Changes : Player -- def GetSuccessfulPairs(self): return self._SuccessfulPairs def match(self): self._SuccessfulPairs+=1 # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q10: Add a new menu option 'P' ("Peek at Pile") to Game. When selected, prompt the user for coordinates and display all tile symbols contained within that specific pile from top to bottom without removing any tiles.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q11: In Game.PlayGame(), if 5 consecutive turns occur without a single successful match (TurnsSinceMatch >= 5), automatically discard the top tile of every non-empty pile on the board to refresh the grid state, and reset '''=== {{CPTAnswerTab|C#}} JB: Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> TurnsSinceMatch = 0. // ANNOTATION: Player taking a turn selects two piles int Pile1 = ChoosePile(); int Pile2; do { Pile2 = ChoosePile(); } while (Pile1 == Pile2); // Ensure they don't pick the exact same pile twice TurnsSinceMatch++; int resetGame = 0; // ANNOTATION: Check if both chosen piles actually have tiles in them if (Board[Pile1].Empty() == false && Board[Pile2].Empty() == false) { // ANNOTATION: Match Check! Compare the top tile symbols if (Board[Pile1].GetSymbolOfTopTile() == Board[Pile2].GetSymbolOfTopTile()) { TurnsSinceMatch = 0; // Reset counter // Remove top tiles from the board Tile Tile1 = Board[Pile1].Remove(); Tile Tile2 = Board[Pile2].Remove(); // Add them to discard Discard.Add(Tile1); Discard.Add(Tile2); // Calculate score (sum of both tile point values) int ScoreIncrease = 0; ScoreIncrease += Tile1.GetPoints() + Tile2.GetPoints(); Players[WhoseTurn].ChangeScore(ScoreIncrease); Console.WriteLine($"{Players[WhoseTurn].GetName()}, you had two matching {Tile1.GetSymbol()} tiles; your score has increased by {ScoreIncrease}"); resetGame = 0; } else { Console.WriteLine("You did not find a matching pair."); Console.WriteLine($"The first pile you chose had a {Board[Pile1].GetSymbolOfTopTile()}"); Console.WriteLine($"The second pile you chose had a {Board[Pile2].GetSymbolOfTopTile()}"); resetGame += 1; Console.WriteLine(resetGame); if (resetGame == 5) { TurnsSinceMatch = 0; for (int i = 0; i < Board.Count - 1; i++) { Tile Tilei = Board[Pile1].Remove(); } } } </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q12: Add a static method SaveGame(...) to TilesCS that saves the current state of the game (Board, Players, Discard, MaxScore, WhoseTurn, TurnsSinceMatch) to a text file using the exact structure expected by LoadGame().'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q13: Create a subclass SpecialTile inheriting from Tile. It includes a boolean attribute IsDoublePoints. Override GetPoints() so that if IsDoublePoints is true, the method returns twice the standard base points.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q14: Create a subclass WildcardTile inheriting from Tile with symbol '*'. Modify PlayGame() in Game so that if either selected top tile is a WildcardTile ('*'), the selection automatically counts as a match with any other symbol'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): # Code Omitted if self.__Board[Pile1].Empty() == False and self.__Board[Pile2].Empty() == False: # -- Start Changes -- if self.__Board[Pile1].GetSymbolOfTopTile() == self.__Board[Pile2].GetSymbolOfTopTile() or self.__Board[Pile1].GetSymbolOfTopTile()=="*" or self.__Board[Pile2].GetSymbolOfTopTile()=="*": self.__TurnsSinceMatch = 0 Tile1 = self.__Board[Pile1].Remove() Tile2 = self.__Board[Pile2].Remove() self.__Discard.append(Tile1) self.__Discard.append(Tile2) ScoreIncrease = 0 if Tile1.GetSymbol()=="*": ScoreIncrease=Tile2.GetPoints*2 elif Tile2.GetSymbol()=="*": ScoreIncrease=Tile1.GetPoints*2 else: ScoreIncrease += Tile1.GetPoints() + Tile2.GetPoints() # -- End Changes -- # -- Start Changes -- class WildTile(Tile): def __init__(self): super().__init__("*",3) # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q15: Create a derived class AIPlayer inheriting from Player. Add a method SelectPiles(List<Pile> Board) that scans the board for two non-empty piles sharing identical top tiles and returns their indices. If no match is visible, return the first two available non-empty pile indices.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q16: Add an Undo feature to Game. If a player makes a successful match, store the removed tiles, pile indices, and score awarded. Add menu option 'U' to undo the last move, returning the tiles from Discard back into their respective piles and deducting the awarded score from the player.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q17: Allow each player a maximum of 1 "Peek" ability per game. Add option 'V' to the menu. When used, the current player selects a pile and previews the symbol of the second tile down in that pile without removing it. Subtract 1 from their available peeks.'''=== {{CPTAnswerTab|C#}} JO: Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> // start change in Player Class protected int PeekAbility = 1; public virtual bool Peek() { if (PeekAbility == 1) { PeekAbility--; return true; } else { return false; } } // end change while (GameOver == false) { string Choice = ""; while (Choice != "T") { DisplayMenu(); Choice = GetChoice(); if (Choice == "B") { DisplayBoard(); } else if (Choice == "D") { DisplayDiscard(); } else if (Choice == "S") { DisplayScores(); } // start change else if (Choice == "V") { DisplaySecondTile(); } // end change } // start change in Class Game private void DisplaySecondTile() { if (Players[WhoseTurn].Peek() == true) { int PilePeek = ChoosePile(); char TopTile = Board[PilePeek].GetSymbolOfTopTile(); Board[PilePeek].Remove(); Console.WriteLine(Board[PilePeek].GetSymbolOfTopTile()); Board[PilePeek].Add(new Tile(TopTile, 0)); } else { Console.WriteLine("Peek has already been used!"); } } // end change private void DisplayMenu() { Console.WriteLine(); Console.WriteLine(); Console.WriteLine("MENU"); Console.WriteLine("B. Display the board"); Console.WriteLine("D. Display the discard"); Console.WriteLine("T. Take turn"); Console.WriteLine("S. Display scores"); //start change Console.WriteLine("V. Peek at pile"); //end change Console.WriteLine(); } </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q18: Create a derived class TrapPile inheriting from Pile. If a matching pair of tiles is removed where either selected pile is a TrapPile, convert the score gain into a penalty (subtract points instead of adding).'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q19:Modify Game to support non-square grids (e.g., Width \times Height = 20 piles total). Replace GridSize with GridWidth and GridHeight. Update GetIndex(x, y) and DisplayBoard() accordingly.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q20: Create a MoveLog class to track turn events. Record player name, chosen pile coordinates, matched symbols, and points earned. Add menu option 'H' to print a structured text table summarizing all completed turns in the current game session.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} == Section D: Issues with the Code and Fixes : == === '''Issue 1: When entering a choice, the way the program detects what choice the player has inputted is case sensitive. Entering ‘b’ rather than ‘B’ will prompt the user to enter their choice again.'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> // Start change Choice = Console.ReadLine().ToUpper(); // end change </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> # Start change Choice = input(f"{self.__Players[self.__WhoseTurn].GetName()}, enter your choice: ").upper() # End change </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 2: The program allows the user to enter x and y coordinates out of the 1-6 range'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> // Start change while (x>6 || x<1 || y>6 || y<1) { Console.WriteLine("Please enter within the range of 1-6"); Console.Write("Enter x coordinate: "); x = Convert.ToInt32(Console.ReadLine()); Console.Write("Enter y coordinate: "); y = Convert.ToInt32(Console.ReadLine()); } return GetIndex(x, y); // end change </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def __ChoosePile(self): x = 0 y = 0 # -- Start Changes -- while x<1 or x>6 or y<1 or y>6: print() print("For each coordinate enter a number between 1 and 6") x = int(input("Enter x coordinate: ")) y = int(input("Enter y coordinate: ")) print() # -- End Changes -- return self.__GetIndex(x, y) </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 3: If player 1 and player 2 get the same score, the game ends and a tie isn't declared.'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> // Start change else if (Players[1].GetScore() == Players[0].GetScore()) { Console.WriteLine("The game is a tie."); } // end change </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): #Code Omitted if self.__Players[0].GetScore() > self.__Players[1].GetScore(): print(f"{self.__Players[0].GetName()} has won!") elif self.__Players[1].GetScore() > self.__Players[0].GetScore(): print(f"{self.__Players[1].GetName()} has won!") # -- Start Changes -- else: print("The game ends in a tie.") # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 4: The program doesn’t display any error messages to the user when they choose the same pile.'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> int Pile1 = ChoosePile(); // START CHANGE int Pile2 = ChoosePile(); while (Pile1 == Pile2) { Console.WriteLine("Please input a different tile"); Pile2 = ChoosePile(); } // END CHANGE </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): #Code Omitted Pile1 = self.__ChoosePile() Pile2 = self.__ChoosePile() while Pile1 == Pile2: # -- Start Changes -- print("Pile 2 must be different to Pile 1") # -- End Changes Pile2 = self.__ChoosePile() </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 5: If a letter which is not on the display menu is entered, there is no error message or a message to prompt the user to enter a valid letter'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> while (Choice.ToUpper() != "T") { DisplayMenu(); Choice = GetChoice(); if (Choice.ToUpper() == "B") { DisplayBoard(); } else if (Choice.ToUpper() == "D") { DisplayDiscard(); } else if (Choice.ToUpper() == "S") { DisplayScores(); } // CHANGE else if (Choice.ToUpper() != "T") { Console.WriteLine("That is not a valid menu option."); } // END CHANGE } </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): while self.__GameOver == False: Choice = "" while Choice != "T": self.__DisplayMenu() Choice = self.__GetChoice() if Choice == "B": self.__DisplayBoard() elif Choice == "D": self.__DisplayDiscard() elif Choice == "S": self.__DisplayScores() # -- Start Changes -- elif Choice != "T": print("Please enter a valid option") # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 6: Before the tiles are matched, the code should check if the pile is empty or the players turn is wasted'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> int Pile1 = ChoosePile(); // START Change while (Board[Pile1].Empty() == true) { Console.WriteLine("Empty tile"); Pile1 = ChoosePile(); } int Pile2 = ChoosePile(); while (Board[Pile2].Empty() == true) { Console.WriteLine("Empty Tile"); Pile2 = ChoosePile(); } // end change else { Console.WriteLine("You chose an empty pile"); //player is given another turn if pile is empty //start change PlayGame(); //end change } </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): #Code Omitted Pile1 = self.__ChoosePile() # -- Start Changes -- while Pile1.Empty(): print("Please pick a pile that isn't empty") Pile1=self.__ChoosePile Pile2 = self.__ChoosePile() while Pile2.Empty(): print("Please pick a pile that isn't empty") Pile2=self.__ChoosePile() # -- End Changes -- while Pile1 == Pile2: Pile2 = self.__ChoosePile() </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 7: When invalid input is entered code crashes'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> int x = 0, y = 0; // CHANGE try { Console.Write("Enter x coordinate: "); x = Convert.ToInt32(Console.ReadLine()); Console.Write("Enter y coordinate: "); y = Convert.ToInt32(Console.ReadLine()); return GetIndex(x, y); } catch (Exception) { Console.WriteLine("Invalid input"); ChoosePile(); } // END CHANGE </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 8: When the game finishes, it does not display the scores of both users'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> //start change if (Players[0].GetScore() > Players[1].GetScore()) { Console.WriteLine($"{Players[0].GetName()} has won! Score:" + Players[0].GetScore()); } else if (Players[1].GetScore() > Players[0].GetScore()) { Console.WriteLine($"{Players[1].GetName()} has won! Score:" + Players[1].GetScore()); } //end change </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): #Code Omitted if self.__Players[0].GetScore() > self.__Players[1].GetScore(): print(f"{self.__Players[0].GetName()} has won!") # -- Start Changes -- self.__DisplayScores() # -- End Changes -- elif self.__Players[1].GetScore() > self.__Players[0].GetScore(): print(f"{self.__Players[1].GetName()} has won!") # -- Start Changes -- self.__DisplayScores() # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 9: The x coordinates can go above the boundary of 1-6'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> // CHANGE try { do { Console.Write("Enter x coordinate: "); x = Convert.ToInt32(Console.ReadLine()); if (x > GridSize || x < 1) { Console.WriteLine("Out of bounds. Enter a value within the range of the grid."); } } while (x > GridSize || x < 1); do { Console.Write("Enter y coordinate: "); y = Convert.ToInt32(Console.ReadLine()); if (y > GridSize || y < 1) { Console.WriteLine("Out of bounds. Enter a value within the range of the grid."); } return GetIndex(x, y); } while (y > GridSize || y < 1); } catch (Exception) { Console.WriteLine("Invalid input"); ChoosePile(); } return 0; // END CHANGE </syntaxhighlight> {{CPTAnswerTabEnd}} c1l8szbyykulia64hqdpdwvhp8p0yr4 4679789 4679788 2026-11-03T13:48:00Z Fware404 3630157 Added Python section to each Question / Issue 4679789 wikitext text/x-wiki {{soft redirect|v:en:A-level Computer Science AQA Paper 1 Skeleton program 2027}} == Section C Mark distribution comparison == Mark distribution for this year: The 2027 paper 1 will contain The 2026 paper 1 contained 5 questions worth 3, 2, 5, 2 and 1 mark(s) (13 total). The 2025 paper contained 4 questions worth 2 marks each (8 total). The 2024 paper contained 3 questions worth 11 marks in total (3+2+6=11). The 2023 paper contained 6 questions worth 13 marks The 2022 paper contained 5 questions worth 17 marks. The 2021 paper contained 4 questions worth 13 marks. == Section C Predictions == '''Predictions:''' == Section D Mark distribution comparison == Mark distribution for this year: * The 2027 paper 1 contains These marks include the screen capture(s), so the marks for the coding will be 1-2 marks lower. * The 2026 paper 1 contains 4 questions: a 5 mark, an 8 mark and two 12 mark questions. * The 2025 paper 1 contained 4 questions: a 5 mark, a 6 mark and two 14 mark questions. * The 2024 paper 1 contained 4 questions: a 5 mark, a 6 mark and two 14 mark questions. * The 2023 paper 1 contained 4 questions: a 5 mark, a 9 mark, a 10 mark and one 13 mark question. * The 2022 paper 1 contained 4 questions: a 5 mark, a 9 mark, a 11 mark and one 13 mark question. * The 2021 paper 1 contained 4 questions: a 6 mark, an 8 mark, a 9 mark and one 14 mark question. * The 2020 paper 1 contained 4 questions: a 6 mark, an 8 mark, a 11 mark and one 12 mark question. * The 2019 paper 1 contained 4 questions: a 5 mark, an 8 mark, a 9 mark and one 13 mark question. * The 2018 paper 1 contained 5 questions: a 2 mark, a 5 mark, two 9 mark and one 12 mark question. * The 2017 paper 1 contained 5 questions: a 5 mark, three 6 mark and one 12 mark question. == Section D Predictions == === '''Q1: Write code to utilize Bonus when a player clears a pile, or use TurnsSinceMatch to trigger a board reshuffle when players get stuck.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q2: Modify board creation or grid coordinate calculations to validate that board sizes loaded from external files form valid square dimensions.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q3: Refactor Pile.GetSymbolOfTopTile() to return a fallback character (e.g., ' ' or '?') or throw a defensive guard check if the pile is empty.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q4: Modify TilesCS.Main() so that when setting up a default game, the user is prompted to enter a custom target score (MaxScore) rather than using the hardcoded value of 10.'''=== {{CPTAnswerTab|C#}} GK - Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> if (UseDataFromFile == false) { Players.Add(new Player("Player 1", 0)); Players.Add(new Player("Player 2", 0)); for (int Count = 1; Count <= 36; Count++) { Pile P = new Pile(3, 0); P.Add(new Tile('A', 1)); P.Add(new Tile('B', 2)); P.Add(new Tile('A', 1)); Board.Add(P); } //start change Console.WriteLine("Enter a target score"); MaxScore = int.Parse(Console.ReadLine()); //end change } </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> if UseDataFromFile == False: Players.append(Player("Player 1", 0)) Players.append(Player("Player 2", 0)) for Count in range(1, 37): P = Pile(3, 0) P.Add(Tile("A", 1)) P.Add(Tile("B", 2)) P.Add(Tile("A", 1)) Board.append(P) # -- Start Changes -- MaxScoreInput=input("Enter a max score: ") if type(MaxScoreInput)==int: MaxScore=MaxScoreInput else: print("Using default max score (10)") # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q5: Update the DisplayScores() method in Game so that in addition to printing player scores, it prints which player is currently winning or states that the game is currently a tie.'''=== {{CPTAnswerTab|C#}} GK - Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> private void DisplayScores() { Console.WriteLine(); foreach (Player P in Players) { Console.WriteLine($"{P.GetName()}: has a score of {P.GetScore()}"); } //start change if (Players[1].GetScore() > Players[0].GetScore()) { Console.WriteLine($"{Players[1].GetName()} is winning"); } else if (Players[1].GetScore() < Players[0].GetScore()) { Console.WriteLine($"{Players[0].GetName()} is winning"); } else if (Players[1].GetScore() == Players[0].GetScore()) { Console.WriteLine("The game is currently a tie."); } //end change Console.WriteLine(); } </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def __DisplayScores(self): print() for P in self.__Players: print(f"{P.GetName()}: has a score of {P.GetScore()}") print() # -- Start Changes -- if self.__Players[0]._Score>self.__Players[1]._Score: print(f"{self.__Players[0].GetName} Is winning") elif self.__Players[0]._Score<self.__Players[1]._Score: print(f"{self.__Players[1].GetName} Is winning") else: print("Both players are tied") # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q6: Add a method CountTotalTiles() to the Game class that counts and returns the total number of tiles remaining across all piles on the board. Display this total when the board is displayed ('B'). '''=== {{CPTAnswerTab|C#}} GK - Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> //total number of tiles //start change private int CountTotalTiles() { int total = 0; for (int i = 0; i < Board.Count; i++) { total += Board[i].GetNumberOfTiles(); } return total; } //end change DisplayMenu(); Choice = GetChoice(); if (Choice == "B") { DisplayBoard(); //start change Console.WriteLine($"Total number of tiles {CountTotalTiles()}"); //end change } </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q7: Modify ChoosePile() in the Game class to validate that both user-entered X and Y coordinates fall within valid grid boundaries (1 \le x {GridSize} and 1 \le y \le{GridSize}) before calculating the index.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q8: The Pile class contains an unused Bonus field. Add a method GetAndClearBonus() to Pile that returns the bonus value and resets it to 0. Update PlayGame() in Game so that when a matching pair is found, any bonus points from the two chosen piles are added to the player's score.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q9: Extend the Player class to keep track of how many successful matching pairs each player has made during the game. Display this count in DisplayScores().'''=== {{CPTAnswerTab|C#}} JO: Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> JO // START CHANGE class Player protected int SuccessMatches = 0; public virtual void NumberOfSuccessfulMatches() { SuccessMatches++; } public virtual int ReturnMatches() { return SuccessMatches; } //END CHANGE //START CHANGE DisplayScores Console.WriteLine($"{Players[0].GetName()} has {Players[0].ReturnMatches()} successful matches"); Console.WriteLine($"{Players[1].GetName()} has {Players[1].ReturnMatches()} successful matches"); // END CHANGE </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): # Code Omitted ScoreIncrease += Tile1.GetPoints() + Tile2.GetPoints() self.__Players[self.__WhoseTurn].ChangeScore(ScoreIncrease) # -- Start Changes : PlayGame -- self.__Players[self.__WhoseTurn].match() # -- End Changes -- def __DisplayScores(self): print() for P in self.__Players: # -- Start Changes : __DisplayScores -- print(f"{P.GetName()}: has a score of {P.GetScore()} with {P.GetSuccessfulPairs()} Successful Pair(s)") # -- End Changes -- print() # -- Start Changes : Player -- def GetSuccessfulPairs(self): return self._SuccessfulPairs def match(self): self._SuccessfulPairs+=1 # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q10: Add a new menu option 'P' ("Peek at Pile") to Game. When selected, prompt the user for coordinates and display all tile symbols contained within that specific pile from top to bottom without removing any tiles.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q11: In Game.PlayGame(), if 5 consecutive turns occur without a single successful match (TurnsSinceMatch >= 5), automatically discard the top tile of every non-empty pile on the board to refresh the grid state, and reset '''=== {{CPTAnswerTab|C#}} JB: Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> TurnsSinceMatch = 0. // ANNOTATION: Player taking a turn selects two piles int Pile1 = ChoosePile(); int Pile2; do { Pile2 = ChoosePile(); } while (Pile1 == Pile2); // Ensure they don't pick the exact same pile twice TurnsSinceMatch++; int resetGame = 0; // ANNOTATION: Check if both chosen piles actually have tiles in them if (Board[Pile1].Empty() == false && Board[Pile2].Empty() == false) { // ANNOTATION: Match Check! Compare the top tile symbols if (Board[Pile1].GetSymbolOfTopTile() == Board[Pile2].GetSymbolOfTopTile()) { TurnsSinceMatch = 0; // Reset counter // Remove top tiles from the board Tile Tile1 = Board[Pile1].Remove(); Tile Tile2 = Board[Pile2].Remove(); // Add them to discard Discard.Add(Tile1); Discard.Add(Tile2); // Calculate score (sum of both tile point values) int ScoreIncrease = 0; ScoreIncrease += Tile1.GetPoints() + Tile2.GetPoints(); Players[WhoseTurn].ChangeScore(ScoreIncrease); Console.WriteLine($"{Players[WhoseTurn].GetName()}, you had two matching {Tile1.GetSymbol()} tiles; your score has increased by {ScoreIncrease}"); resetGame = 0; } else { Console.WriteLine("You did not find a matching pair."); Console.WriteLine($"The first pile you chose had a {Board[Pile1].GetSymbolOfTopTile()}"); Console.WriteLine($"The second pile you chose had a {Board[Pile2].GetSymbolOfTopTile()}"); resetGame += 1; Console.WriteLine(resetGame); if (resetGame == 5) { TurnsSinceMatch = 0; for (int i = 0; i < Board.Count - 1; i++) { Tile Tilei = Board[Pile1].Remove(); } } } </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q12: Add a static method SaveGame(...) to TilesCS that saves the current state of the game (Board, Players, Discard, MaxScore, WhoseTurn, TurnsSinceMatch) to a text file using the exact structure expected by LoadGame().'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q13: Create a subclass SpecialTile inheriting from Tile. It includes a boolean attribute IsDoublePoints. Override GetPoints() so that if IsDoublePoints is true, the method returns twice the standard base points.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q14: Create a subclass WildcardTile inheriting from Tile with symbol '*'. Modify PlayGame() in Game so that if either selected top tile is a WildcardTile ('*'), the selection automatically counts as a match with any other symbol'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): # Code Omitted if self.__Board[Pile1].Empty() == False and self.__Board[Pile2].Empty() == False: # -- Start Changes -- if self.__Board[Pile1].GetSymbolOfTopTile() == self.__Board[Pile2].GetSymbolOfTopTile() or self.__Board[Pile1].GetSymbolOfTopTile()=="*" or self.__Board[Pile2].GetSymbolOfTopTile()=="*": self.__TurnsSinceMatch = 0 Tile1 = self.__Board[Pile1].Remove() Tile2 = self.__Board[Pile2].Remove() self.__Discard.append(Tile1) self.__Discard.append(Tile2) ScoreIncrease = 0 if Tile1.GetSymbol()=="*": ScoreIncrease=Tile2.GetPoints*2 elif Tile2.GetSymbol()=="*": ScoreIncrease=Tile1.GetPoints*2 else: ScoreIncrease += Tile1.GetPoints() + Tile2.GetPoints() # -- End Changes -- # -- Start Changes -- class WildTile(Tile): def __init__(self): super().__init__("*",3) # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q15: Create a derived class AIPlayer inheriting from Player. Add a method SelectPiles(List<Pile> Board) that scans the board for two non-empty piles sharing identical top tiles and returns their indices. If no match is visible, return the first two available non-empty pile indices.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q16: Add an Undo feature to Game. If a player makes a successful match, store the removed tiles, pile indices, and score awarded. Add menu option 'U' to undo the last move, returning the tiles from Discard back into their respective piles and deducting the awarded score from the player.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q17: Allow each player a maximum of 1 "Peek" ability per game. Add option 'V' to the menu. When used, the current player selects a pile and previews the symbol of the second tile down in that pile without removing it. Subtract 1 from their available peeks.'''=== {{CPTAnswerTab|C#}} JO: Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> // start change in Player Class protected int PeekAbility = 1; public virtual bool Peek() { if (PeekAbility == 1) { PeekAbility--; return true; } else { return false; } } // end change while (GameOver == false) { string Choice = ""; while (Choice != "T") { DisplayMenu(); Choice = GetChoice(); if (Choice == "B") { DisplayBoard(); } else if (Choice == "D") { DisplayDiscard(); } else if (Choice == "S") { DisplayScores(); } // start change else if (Choice == "V") { DisplaySecondTile(); } // end change } // start change in Class Game private void DisplaySecondTile() { if (Players[WhoseTurn].Peek() == true) { int PilePeek = ChoosePile(); char TopTile = Board[PilePeek].GetSymbolOfTopTile(); Board[PilePeek].Remove(); Console.WriteLine(Board[PilePeek].GetSymbolOfTopTile()); Board[PilePeek].Add(new Tile(TopTile, 0)); } else { Console.WriteLine("Peek has already been used!"); } } // end change private void DisplayMenu() { Console.WriteLine(); Console.WriteLine(); Console.WriteLine("MENU"); Console.WriteLine("B. Display the board"); Console.WriteLine("D. Display the discard"); Console.WriteLine("T. Take turn"); Console.WriteLine("S. Display scores"); //start change Console.WriteLine("V. Peek at pile"); //end change Console.WriteLine(); } </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q18: Create a derived class TrapPile inheriting from Pile. If a matching pair of tiles is removed where either selected pile is a TrapPile, convert the score gain into a penalty (subtract points instead of adding).'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q19:Modify Game to support non-square grids (e.g., Width \times Height = 20 piles total). Replace GridSize with GridWidth and GridHeight. Update GetIndex(x, y) and DisplayBoard() accordingly.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Q20: Create a MoveLog class to track turn events. Record player name, chosen pile coordinates, matched symbols, and points earned. Add menu option 'H' to print a structured text table summarizing all completed turns in the current game session.'''=== {{CPTAnswerTab|C#}} <syntaxhighlight lang="C#" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} == Section D: Issues with the Code and Fixes : == === '''Issue 1: When entering a choice, the way the program detects what choice the player has inputted is case sensitive. Entering ‘b’ rather than ‘B’ will prompt the user to enter their choice again.'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> // Start change Choice = Console.ReadLine().ToUpper(); // end change </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> # Start change Choice = input(f"{self.__Players[self.__WhoseTurn].GetName()}, enter your choice: ").upper() # End change </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 2: The program allows the user to enter x and y coordinates out of the 1-6 range'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> // Start change while (x>6 || x<1 || y>6 || y<1) { Console.WriteLine("Please enter within the range of 1-6"); Console.Write("Enter x coordinate: "); x = Convert.ToInt32(Console.ReadLine()); Console.Write("Enter y coordinate: "); y = Convert.ToInt32(Console.ReadLine()); } return GetIndex(x, y); // end change </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def __ChoosePile(self): x = 0 y = 0 # -- Start Changes -- while x<1 or x>6 or y<1 or y>6: print() print("For each coordinate enter a number between 1 and 6") x = int(input("Enter x coordinate: ")) y = int(input("Enter y coordinate: ")) print() # -- End Changes -- return self.__GetIndex(x, y) </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 3: If player 1 and player 2 get the same score, the game ends and a tie isn't declared.'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> // Start change else if (Players[1].GetScore() == Players[0].GetScore()) { Console.WriteLine("The game is a tie."); } // end change </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): #Code Omitted if self.__Players[0].GetScore() > self.__Players[1].GetScore(): print(f"{self.__Players[0].GetName()} has won!") elif self.__Players[1].GetScore() > self.__Players[0].GetScore(): print(f"{self.__Players[1].GetName()} has won!") # -- Start Changes -- else: print("The game ends in a tie.") # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 4: The program doesn’t display any error messages to the user when they choose the same pile.'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> int Pile1 = ChoosePile(); // START CHANGE int Pile2 = ChoosePile(); while (Pile1 == Pile2) { Console.WriteLine("Please input a different tile"); Pile2 = ChoosePile(); } // END CHANGE </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): #Code Omitted Pile1 = self.__ChoosePile() Pile2 = self.__ChoosePile() while Pile1 == Pile2: # -- Start Changes -- print("Pile 2 must be different to Pile 1") # -- End Changes Pile2 = self.__ChoosePile() </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 5: If a letter which is not on the display menu is entered, there is no error message or a message to prompt the user to enter a valid letter'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> while (Choice.ToUpper() != "T") { DisplayMenu(); Choice = GetChoice(); if (Choice.ToUpper() == "B") { DisplayBoard(); } else if (Choice.ToUpper() == "D") { DisplayDiscard(); } else if (Choice.ToUpper() == "S") { DisplayScores(); } // CHANGE else if (Choice.ToUpper() != "T") { Console.WriteLine("That is not a valid menu option."); } // END CHANGE } </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): while self.__GameOver == False: Choice = "" while Choice != "T": self.__DisplayMenu() Choice = self.__GetChoice() if Choice == "B": self.__DisplayBoard() elif Choice == "D": self.__DisplayDiscard() elif Choice == "S": self.__DisplayScores() # -- Start Changes -- elif Choice != "T": print("Please enter a valid option") # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 6: Before the tiles are matched, the code should check if the pile is empty or the players turn is wasted'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> int Pile1 = ChoosePile(); // START Change while (Board[Pile1].Empty() == true) { Console.WriteLine("Empty tile"); Pile1 = ChoosePile(); } int Pile2 = ChoosePile(); while (Board[Pile2].Empty() == true) { Console.WriteLine("Empty Tile"); Pile2 = ChoosePile(); } // end change else { Console.WriteLine("You chose an empty pile"); //player is given another turn if pile is empty //start change PlayGame(); //end change } </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): #Code Omitted Pile1 = self.__ChoosePile() # -- Start Changes -- while Pile1.Empty(): print("Please pick a pile that isn't empty") Pile1=self.__ChoosePile Pile2 = self.__ChoosePile() while Pile2.Empty(): print("Please pick a pile that isn't empty") Pile2=self.__ChoosePile() # -- End Changes -- while Pile1 == Pile2: Pile2 = self.__ChoosePile() </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 7: When invalid input is entered code crashes'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> int x = 0, y = 0; // CHANGE try { Console.Write("Enter x coordinate: "); x = Convert.ToInt32(Console.ReadLine()); Console.Write("Enter y coordinate: "); y = Convert.ToInt32(Console.ReadLine()); return GetIndex(x, y); } catch (Exception) { Console.WriteLine("Invalid input"); ChoosePile(); } // END CHANGE </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 8: When the game finishes, it does not display the scores of both users'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> //start change if (Players[0].GetScore() > Players[1].GetScore()) { Console.WriteLine($"{Players[0].GetName()} has won! Score:" + Players[0].GetScore()); } else if (Players[1].GetScore() > Players[0].GetScore()) { Console.WriteLine($"{Players[1].GetName()} has won! Score:" + Players[1].GetScore()); } //end change </syntaxhighlight> {{CPTAnswerTabEnd}} {{CPTAnswerTab|Python}} Caistor Grammar School - Lincolnshire <syntaxhighlight lang="Python" line="1" start="1"> def PlayGame(self): #Code Omitted if self.__Players[0].GetScore() > self.__Players[1].GetScore(): print(f"{self.__Players[0].GetName()} has won!") # -- Start Changes -- self.__DisplayScores() # -- End Changes -- elif self.__Players[1].GetScore() > self.__Players[0].GetScore(): print(f"{self.__Players[1].GetName()} has won!") # -- Start Changes -- self.__DisplayScores() # -- End Changes -- </syntaxhighlight> {{CPTAnswerTabEnd}} === '''Issue 9: The x coordinates can go above the boundary of 1-6'''=== {{CPTAnswerTab|C#}} Coombe Wood School - South Croydon <syntaxhighlight lang="C#" line="1" start="1"> // CHANGE try { do { Console.Write("Enter x coordinate: "); x = Convert.ToInt32(Console.ReadLine()); if (x > GridSize || x < 1) { Console.WriteLine("Out of bounds. Enter a value within the range of the grid."); } } while (x > GridSize || x < 1); do { Console.Write("Enter y coordinate: "); y = Convert.ToInt32(Console.ReadLine()); if (y > GridSize || y < 1) { Console.WriteLine("Out of bounds. Enter a value within the range of the grid."); } return GetIndex(x, y); } while (y > GridSize || y < 1); } catch (Exception) { Console.WriteLine("Invalid input"); ChoosePile(); } return 0; // END CHANGE </syntaxhighlight> {{CPTAnswerTabEnd}}{{CPTAnswerTab|Python}} <syntaxhighlight lang="Python" line="1" start="1"> </syntaxhighlight> {{CPTAnswerTabEnd}} a4wmx7gkvtz505czrqzzerqa1uhq8q7 Cookbook:Family Pizza 102 485811 4679843 4672261 2026-11-03T20:33:49Z Kittycataclysm 3371989 adjustments per discussion page 4679843 wikitext text/x-wiki __NOTOC__ {{recipe summary | servings = 4 | time = | difficulty = 3 | image = [[File:Préparation d'une pizza maison, mars 2020 (025).jpg|300px]] | energy = <!-- Should if provided contain the number of calories and cal (can include kJ)--> | note = }}{{recipe}} '''Pizza''' is a traditional Italian dish, and this one combines ham with two varieties of cheese. == Ingredients == ===Dough=== * 180 [[Cookbook:Milliliter|ml]] warm water * 1 tsp [[Cookbook:Sugar|granulated sugar]] * ⅔ sachet (~4.5 g) active dry [[Cookbook:Yeast|yeast]] * 1 [[Cookbook:Teaspoon|tsp]] [[Cookbook:Salt|salt]] * 330 [[Cookbook:Gram|g]] [[Cookbook:All-purpose flour|flour]] * 1 [[Cookbook:Tablespoon|tbsp]] [[Cookbook:Olive Oil|olive oil]] ===Topping=== * 5 generous tbsp tomato sauce * 6 slices prosciutto cotto (cooked Italian [[Cookbook:Ham|ham]], or equivalent) * 1 ball buffalo [[Cookbook:Mozzarella Cheese|mozzarella]], [[Cookbook:Dice|diced]] * 40 g [[Cookbook:Emmental Cheese|Emmental]], grated == Procedure == # Combine the warm water, sugar, yeast, and salt in a jug, mixing well to ensure the yeast is distributed. Allow the mixture to rest for 3–4 minutes to activate the yeast. # Pour the flour in a bowl or a salad bowl, then stir in the yeast mixture. Mix, then [[Cookbook:Knead|knead]] well until you get a smooth dough that doesn't stick to your hands. If the dough is too sticky after a few minutes of kneading, try kneading in a little more flour. # Add the olive oil, and knead again until smooth. # Cover the dough with a damp cloth, and let the dough rest for around 20 min. # Briefly knead again, then [[Cookbook:Dough#Rolling|roll]] the dough out with a [[Cookbook:Rolling Pin|rolling pin]] until thin. Transfer to a [[Cookbook:Baking Sheet|baking sheet]]. # Spread the tomato sauce over the dough, then top with the ham slices, arranging them closely together. # Scatter the mozzarella then the Emmental cheese over the ham. # [[Cookbook:Baking|Bake]] at 180°C (356°F) for 15 minutes. ==Gallery== <gallery mode="packed" heights="180"> File:Préparation d'une pizza maison, mars 2020 (004).jpg|Yeast mixture File:Préparation d'une pizza maison, mars 2020 (005).jpg| Combining the yeast mixture with the flour. File:Préparation d'une pizza maison, mars 2020 (006).jpg| Smooth dough after kneading File:Préparation d'une pizza maison, mars 2020 (009).jpg| Dough resting under a cloth File:Préparation d'une pizza maison, mars 2020 (015).jpg|Dough base on a baking sheet File:Préparation d'une pizza maison, mars 2020 (018).jpg| Adding the tomato sauce File:Préparation d'une pizza maison, mars 2020 (019).jpg| Topping with ham File:Préparation d'une pizza maison, mars 2020 (024).jpg| Topping with cheeses </gallery> [[Category:Recipes for pizza]] [[Category:Recipes using emmental]] [[Category:Recipes using mozzarella]] [[Category:Recipes using yeast]] [[Category:Recipes using flour]] [[fr:Livre de cuisine/Pizza familiale]] [[Category:Recipes using salt]] [[Category:Recipes using sugar]] [[Category:Recipes using olive oil]] [[Category:Recipes using ham]] blg237ohm61g3jbcrr8ixi2j5zk9cgv Infrastructure Policy Casebook 0 485833 4679844 4672310 2026-11-03T20:34:13Z Kittycataclysm 3371989 +template 4679844 wikitext text/x-wiki {{New book}} This casebook contains case studies developed by students in the '''Infrastructure Policy''' course at [https://www.gmu.edu/ George Mason University]. The course is offered through the [https://schar.gmu.edu/ Schar School of Policy and Government] in collaboration with the [https://civil.gmu.edu/ Sid and Reva Dewberry Department of Civil, Environmental, and Infrastructure Engineering]. == Fall 2026 Cases == * [[Infrastructure Policy Casebook/Colorado River|Colorado River]] * [[Infrastructure Policy Casebook/NYC Subway Accessibility|New York City Subway Accessibility]] * [[Infrastructure Policy Casebook/Steel River Energy Center|Steel River Energy Center]] * [[Infrastructure Policy Casebook/HS2|HS2 – Britain's High-Speed Rail]] {{BookCat}} h7mw5kz6gpmei8oulps8zwcxttkn9g8 Cookbook:Pasta with Budget Bolognese Sauce 102 485848 4679831 4679662 2026-11-03T19:37:45Z Kittycataclysm 3371989 style, format, language, links, categories 4679831 wikitext text/x-wiki {{recipe summary | servings = 3 | time = 20 minutes | difficulty = 2 | image = | energy = | note = }} {{recipe}} '''Pasta with budget bolognese''' is a pasta dish with bolognese sauce for people on a tight budget. ==Ingredients== *300 g frozen cooked hamburgers, thawed *[[Cookbook:Olive Oil|Olive oil]] *2 [[Cookbook:Onion|onions]], finely [[Cookbook:Chopping|chopped]] *1 [[Cookbook:Garlic|garlic]] clove, finely chopped *1 tin (400 g) peeled [[Cookbook:Tomato|tomatoes]], chopped or puréed in a food processor *2 fresh tomatoes, chopped *[[Cookbook:Salt|Salt]] *Ground [[Cookbook:Pepper|pepper]] (preferably black) * [[Cookbook:Italian Seasoning|Italian seasoning]] * 360 g [[Cookbook:Pasta|pasta]] (preferably [[Cookbook:Spaghetti|spaghetti]]) == Equipment == * [[Cookbook:Saucepan|Saucepan]], to cook the pasta * [[Cookbook:Frying Pan|Frying pan]], to make the sauce * [[Cookbook:Food Processor|Food processor]] ==Procedure== #Cut the thawed hamburgers into pieces, and grind the pieces in the food processor until minced. #Heat a dash of oil in a frying pan over medium to medium-high heat. Add the onion and garlic, and [[Cookbook:Sautéing|sauté]], being careful not to let the garlic burn. #Add the minced hamburgers, and fry for a minute, stirring constantly. #Add the tinned tomatoes, and carefully heat the sauce for a few minutes. #Stir in the chopped fresh tomato, and cook until everything is heated through. #Season the sauce to taste with salt, pepper, and the Italian mixed herbs. #Keep the sauce warm while you cook the pasta according to the package instructions. #Spread the sauce over the pasta and serve. [[Category:Recipes using pasta and noodles]] [[Category:Recipes using mixed herbs]] [[Category:Recipes using beef]] [[Category:Recipes using tomato]] [[Category:Recipes using onion]] [[Category:Recipes using garlic]] [[Category:Recipes using salt]] [[Category:Recipes using olive oil]] [[Category:Recipes using pepper]] 15ypytgy4iwl95vt5lon44zsyvvwenv 4679877 4679831 2026-11-04T04:39:46Z MathsScienceNerd1 3626296 /* Procedure */ Typos fixed 4679877 wikitext text/x-wiki {{recipe summary | servings = 3 | time = 20 minutes | difficulty = 2 | image = | energy = | note = }} {{recipe}} '''Pasta with budget bolognese''' is a pasta dish with bolognese sauce for people on a tight budget. ==Ingredients== *300 g frozen cooked hamburgers, thawed *[[Cookbook:Olive Oil|Olive oil]] *2 [[Cookbook:Onion|onions]], finely [[Cookbook:Chopping|chopped]] *1 [[Cookbook:Garlic|garlic]] clove, finely chopped *1 tin (400 g) peeled [[Cookbook:Tomato|tomatoes]], chopped or puréed in a food processor *2 fresh tomatoes, chopped *[[Cookbook:Salt|Salt]] *Ground [[Cookbook:Pepper|pepper]] (preferably black) * [[Cookbook:Italian Seasoning|Italian seasoning]] * 360 g [[Cookbook:Pasta|pasta]] (preferably [[Cookbook:Spaghetti|spaghetti]]) == Equipment == * [[Cookbook:Saucepan|Saucepan]], to cook the pasta * [[Cookbook:Frying Pan|Frying pan]], to make the sauce * [[Cookbook:Food Processor|Food processor]] ==Procedure== #Cut the thawed hamburgers into pieces, and grind the pieces in the food processor until minced. #Heat a dash of oil in a frying pan over medium to medium-high heat. Add the onion and garlic, and [[Cookbook:Sautéing|sauté]], being careful not to let the garlic burn. #Add the minced hamburgers, and fry for a minute, stirring constantly. #Add the tinned tomatoes, and carefully heat the sauce for a few minutes. #Stir in the chopped fresh tomatoes, and cook until everything is heated through. #Season the sauce to taste with salt, pepper, and the Italian mixed herbs. #Keep the sauce warm while you cook the pasta according to the package instructions. #Spread the sauce over the pasta and serve. [[Category:Recipes using pasta and noodles]] [[Category:Recipes using mixed herbs]] [[Category:Recipes using beef]] [[Category:Recipes using tomato]] [[Category:Recipes using onion]] [[Category:Recipes using garlic]] [[Category:Recipes using salt]] [[Category:Recipes using olive oil]] [[Category:Recipes using pepper]] f1zbhxv5ipl2hgf7fwcnsbkiihyhbmm Cookbook:Four Cheese Pizza 102 486467 4679842 4677995 2026-11-03T20:30:16Z Kittycataclysm 3371989 style, format, language, links, categories, instructions to match original 4679842 wikitext text/x-wiki __NOTOC__ {{recipe summary | servings = 1 | time = | difficulty = 2 | image = [[File:Pizza quatre fromages.jpg|300px]] | energy = <!-- Should if provided contain the number of calories and cal (can include kJ)--> | note = }} {{recipe}} '''Pizza''' is a hot dish widely adapted from its Italian origins, and this simple version combines crushed tomatoes with four different types of cheese. == Ingredients == * 1 portion store-bought pizza dough * 400g [[Cookbook:Tomato|crushed tomatoes]] *100g low-moisture [[Cookbook:Mozzarella|mozzarella]], [[Cookbook:Dice|diced]] *100g [[Cookbook:Gorgonzola Cheese|gorgonzola]], diced *100g [[Cookbook:Cheddar Cheese|cheddar]], diced * 50g comté cheese, [[Cookbook:Grating|grated]] == Procedure == # Roll or stretch the pizza dough into a round base, and place on a [[Cookbook:Baking Sheet|baking sheet]]. Alternatively, fit it into a round [[Cookbook:Baking Pan|baking pan]] or [[Cookbook:Baking Dish|dish]] if needed. # Spread the crushed tomatoes over the pizza base. #Arrange the mozzarella, gorgonzola, and cheddar, over the dough in a cross pattern (as shown in the image). #Sprinkle the grated comté over the rest of the cheeses.[[File:Pizza aux quatre fromages.jpg|thumb|Pattern for arranging the cheeses]] #[[Cookbook:Baking|Bake]] the pizza for 15 minutes at 210°C (410°F), or until the crust is golden brown and the cheese is fully melted. [[Category:Recipes using mozzarella]] [[Category:Recipes using cheddar]] [[Category:Recipes using gorgonzola]] [[Category:Recipes for pizza]] se8f7flrrms2yuhxilxwpkpx4ee99vi WhatsApp Group Administration 0 486547 4679839 4678178 2026-11-03T20:03:17Z Kittycataclysm 3371989 +template 4679839 wikitext text/x-wiki {{New book}} '''WhatsApp Group Administration''' is a short practical manual for people who create and run groups and Communities on WhatsApp. It describes the platform's built-in settings as of October 2026, and the safety problems that group admins most often face. It is independent of WhatsApp and Meta and does not cover third-party software. == Contents == # [[/Introduction/]] # [[/Groups and Communities/]] # [[/Permissions/]] # [[/Membership/]] # [[/Content moderation/]] # [[/Scams and spam/]] # [[/Securing admin accounts/]] # [[/Checklist/]] Menu names vary slightly between Android, iPhone, Web and desktop, and features roll out gradually. {{Shelves|Computer software}} {{Alphabetical|W}} {{status|50%}} pk2yqmklxj8z46vsn3rioq33iqud0lo Wikibooks talk:Magazine/1 5 486595 4679816 4679097 2026-11-03T15:55:24Z Codename Noreste 3441010 /* Mass message */ new topic ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]]) 4679816 wikitext text/x-wiki Are there any ideas for the next Wikibooks Magazine? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 08:00, 28 October 2026 (UTC) :*Discontinuation of FlaggedRevs. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 08:03, 28 October 2026 (UTC) :Snapshot of featured content (best case scenario, this changes from issue to issue). ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:46, 28 October 2026 (UTC) :Admins lost/gained. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:47, 28 October 2026 (UTC) :Interviews, overviews of projects (WikiJunior, Cookbook). ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:47, 28 October 2026 (UTC) :Spotlight on featured content. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:47, 28 October 2026 (UTC) : Maybe we can encourage active, highly trusted patrollers to become administrators? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 23:26, 28 October 2026 (UTC) ::That could be added! Are you willing to write a piece about it? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 11:44, 29 October 2026 (UTC) ::: Probably, but I would write it in an neutral, albeit encouraging tone. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:26, 29 October 2026 (UTC) :If there's ever enough information about it, any technical changes to the site. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 22:20, 30 October 2026 (UTC) :: I can write such technical changes to the magazine. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 23:36, 30 October 2026 (UTC) == Mass message == Should we create a mass message list for interested users ([[Wikibooks:Magazine/Delivery list]]), or would that become a magazine published in the reading room? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 15:55, 3 November 2026 (UTC) 5rp6tjla253h8nxx3ch64yemrqk9w2a 4679870 4679816 2026-11-04T01:42:01Z MathsScienceNerd1 3626296 /* Mass message */ Reply 4679870 wikitext text/x-wiki Are there any ideas for the next Wikibooks Magazine? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 08:00, 28 October 2026 (UTC) :*Discontinuation of FlaggedRevs. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 08:03, 28 October 2026 (UTC) :Snapshot of featured content (best case scenario, this changes from issue to issue). ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:46, 28 October 2026 (UTC) :Admins lost/gained. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:47, 28 October 2026 (UTC) :Interviews, overviews of projects (WikiJunior, Cookbook). ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:47, 28 October 2026 (UTC) :Spotlight on featured content. ―[[User:Koavf|Justin (<span style="color:grey">ko'''a'''<span style="color:black">v</span>f</span>)]]<span style="color:red">❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯</span> 16:47, 28 October 2026 (UTC) : Maybe we can encourage active, highly trusted patrollers to become administrators? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 23:26, 28 October 2026 (UTC) ::That could be added! Are you willing to write a piece about it? [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 11:44, 29 October 2026 (UTC) ::: Probably, but I would write it in an neutral, albeit encouraging tone. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 17:26, 29 October 2026 (UTC) :If there's ever enough information about it, any technical changes to the site. [[User:JJPMaster|JJP]]<sub>[[User talk:JJPMaster|Mas]]<sub>[[Special:Contributions/JJPMaster|ter]]</sub></sub> ([[wikt:she|she]]/[[wikt:they|they]]) 22:20, 30 October 2026 (UTC) :: I can write such technical changes to the magazine. [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 23:36, 30 October 2026 (UTC) == Mass message == Should we create a mass message list for interested users ([[Wikibooks:Magazine/Delivery list]]), or would that become a magazine published in the reading room? [[User:Codename Noreste|<span style="color: blue">Codename Noreste</span>]] /// [[User talk:Codename Noreste|⭐️✨]] 15:55, 3 November 2026 (UTC) :Yes, that would be a good idea. That way, users can get more information regarding the magazine. Is that perhaps possible? --[[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 01:42, 4 November 2026 (UTC) 2qr3desyaosqjywy8w1wq4hc3b3jv36 User:Bojja Mahesh Yadav/sandbox 2 486634 4679885 4679762 2026-11-04T05:57:42Z Bojja Mahesh Yadav 3629813 /* Indian Cell Tower Radiation Norms */ 4679885 wikitext text/x-wiki = Indian Cell Tower Radiation Norms = Mobile communication is an integral part of today's society. Communication signals are sent and received by mobile towers, also known as mobile base stations. A variety of communication services can be provided, such as voice calling and internet browsing using radio frequency (RF) electromagnetic waves.<ref name="WHO1">World Health Organization (WHO), [https://www.who.int/news-room/questions-and-answers/item/radiation-electromagnetic-fields Radiation: Electromagnetic Fields].</ref> Emission from Mobile Towers comes in the form of electromagnetic fields generated by the antenna located on mobile towers. This emission falls under the non-ionizing section of the electromagnetic spectrum. The amount of exposure depends on many factors such as transmission output, antenna properties, distance from antenna and environmental factors.<ref name="WHO2">World Health Organization (WHO), [https://www.who.int/teams/environment-climate-change-and-health/radiation-and-health/non-ionizing/wireless Base Stations and Wireless Networks].</ref> In India, the standards for EMF exposure are set by the Department of Telecommunications (DoT) under the Ministry of Communications. The standards set out limits for exposure to electromagnetic fields for the public from mobile base stations. The limits prescribed for the public exposure to electromagnetic fields from mobile base stations in India are ten times lower than those of ICNIRP, according to DoT publications.<ref name="DOT1">Department of Telecommunications, Government of India, [https://www.dot.gov.in/static/uploads/2025/08/f5e00b30612004ac3a993a6f93d68d95.pdf Report and decisions regarding Electromagnetic Field (EMF) Radiation, 27 February 2014].</ref> The book contains information regarding radiation standards in India. Scientific explanation of RF radiation will be mentioned along with the government regulations. Exposure levels, measuring methods and monitoring systems will also be covered in this book. The role of the DoT, Tarang Sanchar portal and raising public awareness will also be discussed. The main objective of this book is to make the student aware about the regulations regarding mobile tower radiation in India and monitoring and controlling of exposure to RF electromagnetic fields by the authorities. == Table of Contents == === 1. Introduction === [[User:Bojja_Mahesh_Yadav/sandbox/1.1 Introduction to Mobile Communication|1.1 Introduction to Mobile Communication]] [[User:Bojja_Mahesh_Yadav/sandbox/1.2 Introduction to Cell Tower Radiation|1.2 Introduction to Cell Tower Radiation]] [[User:Bojja_Mahesh_Yadav/sandbox/1.3 Need for Radiation Standards in India|1.3 Need for Radiation Standards in India]] [[User:Bojja_Mahesh_Yadav/sandbox/1.4 Objectives of the Study|1.4 Objectives of the Study]] === 2. Basics of Cell Tower Radiation === * [[User:Bojja_Mahesh_Yadav/sandbox/2.1 Electromagnetic Waves|2.1 Electromagnetic Waves]] * [[User:Bojja_Mahesh_Yadav/sandbox/2.2 Radio Frequency Radiation|2.2 Radio Frequency Radiation]] * [[User:Bojja_Mahesh_Yadav/sandbox/2.3 Non-Ionizing Radiation|2.3 Non-Ionizing Radiation]] * [[User:Bojja_Mahesh_Yadav/sandbox/2.4 Working Principle of Mobile Towers|2.4 Working Principle of Mobile Towers]] === 3. Indian Radiation Standards === * [[User:Bojja_Mahesh_Yadav/sandbox/3.1 Department of Telecommunications|3.1 Department of Telecommunications]] * [[User:Bojja_Mahesh_Yadav/sandbox/3.2 Indian Government Regulations|3.2 Indian Government Regulations]] * [[User:Bojja_Mahesh_Yadav/sandbox/3.3 EMF Exposure Limits|3.3 EMF Exposure Limits]] * [[User:Bojja_Mahesh_Yadav/sandbox/3.4 Comparison with International Standards|3.4 Comparison with International Standards]] === 4. Radiation Measurement and Monitoring === * [[User:Bojja_Mahesh_Yadav/sandbox/4.1 Measurement Units|4.1 Measurement Units]] * [[User:Bojja_Mahesh_Yadav/sandbox/4.2 Measurement Equipment|4.2 Measurement Equipment]] * [[User:Bojja_Mahesh_Yadav/sandbox/4.3 Measurement Procedures|4.3 Measurement Procedures]] * [[User:Bojja_Mahesh_Yadav/sandbox/4.4 Tarang Sanchar Portal|4.4 Tarang Sanchar Portal]] === 5. Health and Safety === * [[User:Bojja_Mahesh_Yadav/sandbox/5.1 Human Exposure to RF Radiation|5.1 Human Exposure to RF Radiation]] * [[User:Bojja_Mahesh_Yadav/sandbox/5.2 Scientific Research|5.2 Scientific Research]] * [[User:Bojja_Mahesh_Yadav/sandbox/5.3 Public Safety Guidelines|5.3 Public Safety Guidelines]] * [[User:Bojja_Mahesh_Yadav/sandbox/5.4 Myths and Facts|5.4 Myths and Facts]] === 6. Regulatory Compliance in India === * [[User:Bojja_Mahesh_Yadav/sandbox/6.1 EMF Compliance Requirements|6.1 EMF Compliance Requirements]] * [[User:Bojja_Mahesh_Yadav/sandbox/6.2 Self-Certification|6.2 Self-Certification]] * [[User:Bojja_Mahesh_Yadav/sandbox/6.3 Government Monitoring|6.3 Government Monitoring]] * [[User:Bojja_Mahesh_Yadav/sandbox/6.4 Penalties for Non-Compliance|6.4 Penalties for Non-Compliance]] === 7. Conclusion === === 8. References === hqty7nyop9msriqc2m7onjqaw98hw2a User:Ritwik2418/sandbox 2 486652 4679901 4679542 2026-11-04T07:01:23Z Jcb 90773 4679901 wikitext text/x-wiki = 4-DOF Robotic Arm Using Inverse Kinematics = A '''4-DOF (degrees of freedom) robotic arm''' has four joints, each driven by a servo or stepper motor. It is a popular project for beginners because it can reach a point in 3D space and also control the tilt of the gripper, while still being cheap and simple to build with an Arduino or ESP 32. == What is Inverse Kinematics? == * '''Forward kinematics (FK)''': given the joint angles, calculate where the end of the arm (the gripper) is. * '''Inverse kinematics (IK)''': given the position where you want the gripper to be, calculate the joint angles needed to get there. When you tell a robotic arm to "pick up the object at (x, y, z)", you are asking an IK question. The controller must convert that position into angles for each servo.<ref name="craig">Craig, John J. (2005). ''Introduction to Robotics: Mechanics and Control'' (3rd ed.). Pearson Prentice Hall. {{ISBN|0-201-54361-3}}.</ref> == Structure of a 4-DOF Arm == A common layout is: {| class="wikitable" !Joint !Angle !Motion !Purpose |- |1. Base |θ<sub>1</sub> |Rotation around the vertical axis |Points the arm toward the target |- |2. Shoulder |θ<sub>2</sub> |Up/down pitch |Moves the first link |- |3. Elbow |θ<sub>3</sub> |Up/down pitch |Moves the second link |- |4. Wrist |θ<sub>4</sub> |Up/down pitch |Sets the gripper tilt |} Link lengths: '''L<sub>1</sub>''' (shoulder to elbow), '''L<sub>2</sub>''' (elbow to wrist), '''L<sub>3</sub>''' (wrist to gripper tip). Joints 2, 3 and 4 all move in the same vertical plane, so the problem can be reduced to a 2D problem once the base angle is known. == Formulas Involved == Inverse kinematics for a 4-DOF arm uses a few key formulas. Here, (x, y, z) is the target position, L<sub>1</sub> and L<sub>2</sub> are the link lengths, and r<sub>w</sub> and z<sub>w</sub> are the horizontal and vertical distances from the shoulder to the wrist. '''1. Base angle''' (which direction the arm turns) <code><nowiki><math>\theta_1 = \operatorname{atan2}(y, x)</math></nowiki></code> This turns the base so the arm faces the target at (x, y). '''2. Elbow angle''' (from the law of cosines) <code><nowiki><math>D = \frac{r_w^2 + z_w^2 - L_1^2 - L_2^2}{2 L_1 L_2}</math></nowiki> <nowiki><math>\theta_3 = \operatorname{atan2}\left(\pm\sqrt{1 - D^2},\, D\right)</math></nowiki></code> Here r<nowiki><sub>w</sub></nowiki> and z<nowiki><sub>w</sub></nowiki> are the horizontal and vertical distances from the shoulder to the wrist, and L<nowiki><sub>1</sub></nowiki>, L<nowiki><sub>2</sub></nowiki> are the two link lengths. The ± gives the elbow-up or elbow-down solution. If |D| is greater than 1, the target is out of reach. '''3. Shoulder angle''' <code><nowiki><math>\theta_2 = \operatorname{atan2}(z_w, r_w) - \operatorname{atan2}(L_2 \sin\theta_3,\; L_1 + L_2 \cos\theta_3)</math></nowiki></code> == Applications == * Pick-and-place demonstrations * Education and robotics competitions * Sorting objects by color with a camera * Low-cost desktop automation == References == Craig, John J. (2005). ‘’Introduction to Robotics: Mechanics and Control’’ (3rd ed.). Pearson Prentice Hall. Spong, Mark W.; Hutchinson, Seth; Vidyasagar, M. (2006). ‘’Robot Modeling and Control’’. Wiley. Siciliano, Bruno; Sciavicco, Lorenzo; Villani, Luigi; Oriolo, Giuseppe (2009). ‘’Robotics: Modelling, Planning and Control’’. Springer. md0cusfomrzw5wjw9hed9ux7ra6a7kl User:Ashu935/sandbox 2 486658 4679793 4679187 2026-11-03T14:26:46Z Ashu935 3629901 4679793 wikitext text/x-wiki = Chopper = Chopper is power controller which converts fixed magnitude of DC into variable magnitude of DC. Chopper can increase as well as decrease the supply voltage. So, in D.C circuit, it is equivalent to a transformer. In chopper circuit, any power semiconductor devices i.e., SCR, GTO, MOSFET, BJT, IGBT etc. are represented as switch only. [[File:Chopper_sym.png|thumb|This is the image of chopper]] == Types Of Choppers == There are several types of Choppers which includes the following: # Step Down Chopper # Step Up Chopper # Step Up/Down Chopper === Step Down Chopper : === Step down chopper is a chopper in which average output voltage is less than the supply voltage. ( Vo < Vs ) <u>Types of Step Down Chopper On the Basis of type of load :</u> # R Load [[File:Step_down_chopper_R_load.png|thumb|Step Down Chopper (R Load)]] * Average output voltage : <math>Vo = Vs * \alpha</math> where Vo is output voltage, Vs is supply voltage, α is duty cycle(Ton/T) and is always greater then 0 and less than 1. * Average output Current : <math>Io = (Vs * \alpha) / R</math> where Io is output current, Vs is source voltage , α is duty cycle and R is resistance. * Average Supply Current : <math>Is = (Vs * \alpha) / R</math> where Is is supply current, Vs is source voltage , α is duty cycle and R is resistance. * Effective input resistance : Rin = Vs / Is = Vs x R / αVs = R / α * RMS output voltage: <math>Vor =\surd\alpha Vs </math> where Vor is RMS output voltage. * RMS output Current: <math>Ior =Vor / R = \surd\alpha Vs / R </math> where Ior is RMS output current. 6j3jeauzvsvaryug2xuewfpp7w1vopt 4679797 4679793 2026-11-03T14:39:11Z Ashu935 3629901 4679797 wikitext text/x-wiki = Chopper = Chopper is power controller which converts fixed magnitude of DC into variable magnitude of DC. Chopper can increase as well as decrease the supply voltage. So, in D.C circuit, it is equivalent to a transformer. In chopper circuit, any power semiconductor devices i.e., SCR, GTO, MOSFET, BJT, IGBT etc. are represented as switch only. [[File:Chopper_sym.png|thumb|This is the image of chopper]] == Types Of Choppers == There are several types of Choppers which includes the following: # Step Down Chopper # Step Up Chopper # Step Up/Down Chopper === Step Down Chopper : === Step down chopper is a chopper in which average output voltage is less than the supply voltage. ( Vo < Vs ) <u>Types of Step Down Chopper On the Basis of type of load :</u> # R Load [[File:Step_down_chopper_R_load.png|thumb|Step Down Chopper (R Load)]] *Average output voltage : <math>Vo = Vs * \alpha</math> where Vo is output voltage, Vs is supply voltage, α is duty cycle(Ton/T) and is always greater then 0 and less than 1. *Average output Current : <math>Io = (Vs * \alpha) / R</math> where Io is output current, Vs is source voltage , α is duty cycle and R is resistance. *Average Supply Current : <math>Is = (Vs * \alpha) / R</math> where Is is supply current, Vs is source voltage , α is duty cycle and R is resistance. * Effective input resistance : Rin = Vs / Is = Vs x R / αVs = R / α *RMS output voltage: <math>Vor =\surd\alpha Vs </math> where Vor is RMS output voltage. *RMS output Current: <math>Ior =Vor / R = \surd\alpha Vs / R </math> where Ior is RMS output current. WAVEFORMS: https://commons.wikimedia.org/wiki/File:Chopper_with_R_load_waveform.png fmzs5mo6xsxfsul5j64k2dxen32s9n5 4679798 4679797 2026-11-03T14:40:42Z Ashu935 3629901 4679798 wikitext text/x-wiki = Chopper = Chopper is power controller which converts fixed magnitude of DC into variable magnitude of DC. Chopper can increase as well as decrease the supply voltage. So, in D.C circuit, it is equivalent to a transformer. In chopper circuit, any power semiconductor devices i.e., SCR, GTO, MOSFET, BJT, IGBT etc. are represented as switch only. [[File:Chopper_sym.png|thumb|This is the image of chopper]] == Types Of Choppers == There are several types of Choppers which includes the following: # Step Down Chopper # Step Up Chopper # Step Up/Down Chopper === Step Down Chopper : === Step down chopper is a chopper in which average output voltage is less than the supply voltage. ( Vo < Vs ) <u>Types of Step Down Chopper On the Basis of type of load :</u> # R Load [[File:Step_down_chopper_R_load.png|thumb|Step Down Chopper (R Load)]] *Average output voltage : <math>Vo = Vs * \alpha</math> where Vo is output voltage, Vs is supply voltage, α is duty cycle(Ton/T) and is always greater then 0 and less than 1. *Average output Current : <math>Io = (Vs * \alpha) / R</math> where Io is output current, Vs is source voltage , α is duty cycle and R is resistance. *Average Supply Current : [[File:Chopper_with_R_load_waveform.png|thumb|295x295px|Waveform]] <math>Is = (Vs * \alpha) / R</math> where Is is supply current, Vs is source voltage , α is duty cycle and R is resistance. * Effective input resistance : Rin = Vs / Is = Vs x R / αVs = R / α *RMS output voltage: <math>Vor =\surd\alpha Vs </math> where Vor is RMS output voltage. *RMS output Current: <math>Ior =Vor / R = \surd\alpha Vs / R </math> where Ior is RMS output current. 373uh6kusg65pnv8n3vaqskkb1zorpg 4679800 4679798 2026-11-03T14:41:50Z Ashu935 3629901 4679800 wikitext text/x-wiki = Chopper = Chopper is power controller which converts fixed magnitude of DC into variable magnitude of DC. Chopper can increase as well as decrease the supply voltage. So, in D.C circuit, it is equivalent to a transformer. In chopper circuit, any power semiconductor devices i.e., SCR, GTO, MOSFET, BJT, IGBT etc. are represented as switch only. [[File:Chopper_sym.png|thumb|This is the image of chopper]] == Types Of Choppers == There are several types of Choppers which includes the following: # Step Down Chopper # Step Up Chopper # Step Up/Down Chopper === Step Down Chopper : === Step down chopper is a chopper in which average output voltage is less than the supply voltage. ( Vo < Vs ) Types of Step Down Chopper On the Basis of type of load : === R Load === [[File:Step_down_chopper_R_load.png|thumb|Step Down Chopper (R Load)]] *'''Average output voltage :''' <math>Vo = Vs * \alpha</math> where Vo is output voltage, Vs is supply voltage, α is duty cycle(Ton/T) and is always greater then 0 and less than 1. *'''Average output Current :''' <math>Io = (Vs * \alpha) / R</math> where Io is output current, Vs is source voltage , α is duty cycle and R is resistance. *'''Average Supply Current :''' [[File:Chopper_with_R_load_waveform.png|thumb|295x295px|Waveform]] <math>Is = (Vs * \alpha) / R</math> where Is is supply current, Vs is source voltage , α is duty cycle and R is resistance. * '''Effective input resistance :''' Rin = Vs / Is = Vs x R / αVs = R / α *'''RMS output voltage:''' <math>Vor =\surd\alpha Vs </math> where Vor is RMS output voltage. *'''RMS output Current:''' <math>Ior =Vor / R = \surd\alpha Vs / R </math> where Ior is RMS output current. 0ymdatuaxadhm7bstp4uo7cydf4knbr User:Chandrakiran66/sandbox 2 486660 4679899 4679168 2026-11-04T07:01:14Z Jcb 90773 4679899 wikitext text/x-wiki {{BookCat}} == Learning Objectives == After studying this chapter, students of Electronics & Communication Engineering (ECE) should be able to: * Define the architectural framework of an IoT-enabled Smart City. * Understand the selection of sensor and actuator technologies for urban sensing. * Compare and analyze wireless communication protocols (LoRaWAN, NB-IoT, Zigbee, 5G NR) for smart city telemetry. * Understand the role of Edge vs. Cloud computing paradigms in latency-sensitive urban infrastructure. * Analyze critical engineering challenges including power harvesting, RF interference, data security, and interoperability. --- == 1. Introduction == [[File:Components_of_Smart_City.png|right|thumb|340x340px|Key structural components and interconnected domains within an IoT-enabled Smart City ecosystem.]] Rapid urbanization has placed immense pressure on civil infrastructure, transportation, utilities, and ecological sustainability. A '''Smart City''' leverages Information and Communication Technologies (ICT) and the '''Internet of Things (IoT)''' to optimize city functions, enhance operational efficiency, minimize resource wastage, and improve the quality of life for its citizens.<ref name="zanella2014">Zanella, A., Bui, N., Castellani, A., Vangelista, L., & Zorzi, M. (2014). "Internet of Things for Smart Cities." ''IEEE Internet of Things Journal'', 1(1), 22–32. doi:10.1109/JIOT.2014.2306328.</ref> From an ECE perspective, a smart city represents a large-scale, heterogeneous, distributed cyber-physical system (CPS) comprising billions of embedded devices, transceivers, network gateways, processing units, and actuator controllers operating continuously in dynamic urban environments.<ref name="alfuqaha2015">Al-Fuqaha, A., Guizani, M., Mohammadi, M., Aledhari, M., & Ayyash, M. (2015). "Internet of Things: A survey on enabling technologies, protocols, and applications." ''IEEE Communications Surveys & Tutorials'', 17(4), 2347–2376.</ref> === 1.1 Conceptual Framework === The deployment of IoT in municipal infrastructure transforms traditional, open-loop management into closed-loop, data-driven automated systems: # '''Physical State Perception''': Micro-electro-mechanical systems (MEMS) sensors collect physical variables (flow rate, gas concentration, vibrational stress, vehicle speed). # '''Data Transmission''': Low-Power Wide-Area Networks (LPWAN) and cellular infrastructures route the telemetry over standardized communication channels. # '''Analytical Synthesis''': Edge microservers and central cloud platforms run signal processing, machine learning (ML), and analytics to generate operational insights. # '''Closed-Loop Actuation''': Commands are transmitted back to actuators (e.g., adjusting traffic signal phases, dynamic street lighting intensity, pressure valve control). --- == 2. IoT Architecture for Smart Cities == [[File:Internet_of_Things.svg|left|thumb|271x271px|Evolution and structural convergence across physical sensing, connectivity, and analytical layers in IoT.]] Smart City IoT architectures generally follow an extended layered model tailored for high scalability, real-time response, and cross-domain data integration.<ref name="ray2018">Ray, P. P. (2018). "A survey on Internet of Things architectures." ''Journal of King Saud University - Computer and Information Sciences'', 30(3), 291–319.</ref> {| class="wikitable" style="width: 100%;" !Layer !Key Hardware / Technologies !Primary Function in Smart Cities |- |'''Application Layer''' |Citizen portals, SCADA control consoles, emergency response dispatch systems. |Domain-specific services (Smart Mobility, Smart Grid, Automated Waste Logistics). |- |'''Middleware & Analytics Layer''' |Cloud servers, distributed databases, Big Data analytics, AI/ML inference engines. |Aggregation, semantic mediation, data storage, predictive modeling, decision logic. |- |'''Edge / Fog Computing Layer''' |Industrial IoT gateways, micro-edge nodes (ARM Cortex-A / RISC-V SBCs), roadside units (RSUs). |Local protocol translation, time-critical event detection, data compression, bandwidth optimization. |- |'''Network & Transport Layer''' |IPv6/6LoWPAN, LoRaWAN, NB-IoT, 4G/5G NR, Wi-SUN, Optical Fiber backbones. |Long-range and short-range wireless telemetry, packet routing, Quality of Service (QoS). |- |'''Perception / Sensing Layer''' |Transducers, MEMS sensors, smart meters, RFID tags, CMOS cameras, microcontrollers (MCU). |Analog-to-digital signal acquisition, physical parameter sampling, local pre-filtering. |} --- == 3. Communication Technologies and Protocols == [[File:LoRaWAN-Architecture.svg|right|thumb|360x360px|End-to-end LoRaWAN network architecture showing star-of-stars topology from End Nodes through Gateways to Network and Application Servers.]] Urban deployments require a heterogeneous mix of short-range wireless, wide-area LPWAN, and high-throughput cellular infrastructure.<ref name="centenaro2016">Centenaro, M., Vangelista, L., Zanella, A., & Zorzi, M. (2016). "Long-range communications in unlicensed bands: the rising stars in the IoT and smart city scenarios." ''IEEE Wireless Communications'', 23(5), 60–67.</ref> === 3.1 Protocol Comparison === {| class="wikitable" style="width: 100%; text-align: center;" !Technology !Operating Band !Typical Range !Data Rate !Power Consumption !Primary Urban Use Case |- |'''Zigbee (IEEE 802.15.4)''' |2.4 GHz ISM |10 – 100 m |Up to 250 kbps |Very Low |Indoor building automation, home energy management. |- |'''LoRaWAN''' |Sub-GHz (868/915 MHz) |2 – 5 km (Urban), 15 km (LOS) |0.3 – 50 kbps |Ultra-Low (multi-year battery) |Smart water meters, trash bin monitoring, soil monitoring. |- |'''NB-IoT (3GPP Rel 13+)''' |Licensed Cellular (LTE in-band/guard) |1 – 10 km |~20 – 250 kbps |Low (PSM / eDRX enabled) |Smart utility metering, municipal street lighting. |- |'''Wi-SUN''' |Sub-GHz (868/915 MHz mesh) |Up to 1 km/hop (Mesh) |50 – 300 kbps |Low to Medium |Smart electrical distribution networks, AMI. |- |'''5G NR (eMBB / URLLC)''' |Sub-6 GHz & mmWave |100 m – 2 km |Up to 10 Gbps |High |Autonomous vehicles (C-V2X), real-time CCTV analytics. |} === 3.2 Application Layer Messaging Protocols === * '''MQTT (Message Queuing Telemetry Transport)''': ** Lightweight Publish/Subscribe model designed for low-bandwidth, high-latency, or unreliable networks.<ref name="oasis_mqtt">OASIS Standard (2019). "MQTT Version 5.0." OASIS Open Standard.</ref> ** Runs over TCP/IP (typically port 1883 or 8883 with TLS). ** Features three Quality of Service (QoS) levels: QoS 0 (At most once), QoS 1 (At least once), QoS 2 (Exactly once). * '''CoAP (Constrained Application Protocol)''': ** Designed specifically for constrained 8-bit and 16-bit nodes (RFC 7252).<ref name="rfc7252">Shelby, Z., Hartke, K., & Bormann, C. (2014). "The Constrained Application Protocol (CoAP)." IETF RFC 7252.</ref> ** Operates over UDP to reduce connection overhead; uses a RESTful Request/Response model. ** Includes built-in support for resource discovery, multicast, and asynchronous subscriptions. --- == 4. Core Subsystems and Engineering Implementations == === 4.1 Intelligent Transportation Systems (ITS) === [[File:Types_V2X_.png|left|thumb|340x340px|Communication modes in Cellular V2X (C-V2X): Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), and Vehicle-to-Pedestrian (V2P).]] * '''Adaptive Traffic Control System (ATCS)''': ** Embedded inductive loops, radar sensors, and thermal imaging cameras monitor queue length and vehicle flow. ** Microcontroller units (e.g., STM32 / NXP i.MX) process local occupancy rates and dynamically modulate green-signal timing via actuated controllers, minimizing vehicle wait times and carbon emissions. * '''Connected Vehicles & Cellular V2X (C-V2X)''': ** Operates in the 5.9 GHz ITS band utilizing direct PC5 sidelink communication.<ref name="3gpp_v2x">3GPP TS 22.185: "Service requirements for V2X services; Stage 1 (Release 16)".</ref> ** Facilitates Vehicle-to-Vehicle (V2V) and Vehicle-to-Infrastructure (V2I) low-latency messaging for collision mitigation and pedestrian safety. * '''Smart Parking Systems''': ** Magnetoresistive and ultrasonic sensors embedded into parking slots detect vehicle presence via magnetic flux distortion. ** Data is pushed over LoraWAN or NB-IoT to municipal navigation dashboards. === 4.2 Smart Grid and Utility Automation === [[File:Smart_grid.png|right|thumb|360x360px|Bidirectional electrical flow and telemetric data communications in an Advanced Metering Infrastructure (AMI) and smart distribution grid.]] * '''Advanced Metering Infrastructure (AMI)''': ** Replaces mechanical analog meters with bidirectional electronic smart meters equipped with high-precision ADCs (e.g., ADE7758/ADE7953) for active/reactive power measurement.<ref name="fang2012">Fang, X., Misra, S., Xue, G., & Yang, D. (2012). "Smart Grid — The New and Improved Power Grid: A Survey." ''IEEE Communications Surveys & Tutorials'', 14(4), 944–980.</ref> ** Communicates interval consumption data to the utility via cellular or RF mesh networks, enabling Time-of-Use (ToU) dynamic tariffs. * '''Automated Fault Detection, Isolation, and Service Restoration (FDIR)''': ** Phasor Measurement Units (PMUs) synchronize voltage and current waveforms using GPS timestamps, enabling real-time detection of distribution grid anomalies. === 4.3 Environmental Monitoring and Waste Logistics === * '''Air Quality & Noise Pollution Monitoring''': ** Electrochemical and optical particulate matter sensors (PM2.5 / PM10 using laser light scattering) interface via I2C/SPI with wireless transceiver nodes. ** Nodes transmit spatial dispersion data to identify industrial pollutant plumes. * '''Solid Waste Optimization''': ** Ultrasonic distance sensors mounted on container lids measure fill levels. ** Tilt sensors detect bin emptying events. ** Dynamic routing algorithms calculate optimized collection paths for municipal fleets, reducing fuel consumption by up to 30%. --- == 5. Hardware and Communication Engineering Challenges == Implementing city-wide IoT networks presents unique challenges for electronic and communication systems engineers: === 5.1 Energy Constraints and Power Harvesting === * Many field nodes cannot connect to mains power and must function for 5 to 10 years on lithium-thionyl chloride ($Li-SOCl_2$) batteries. * '''Mitigation Techniques''': ** Deep-sleep operational cycling ($< 5\ \mu\text{A}$ standby currents). ** Implementation of ambient micro-energy harvesting: photovoltaic micro-cells, piezoelectric vibrational harvesters, and thermoelectric generators (TEG).<ref name="sudevalayam2011">Sudevalayam, S., & Kulkarni, P. (2011). "Energy Harvesting Sensor Nodes: Survey and Implications." ''IEEE Communications Surveys & Tutorials'', 13(3), 443–461.</ref> === 5.2 RF Propagation and Urban Path Loss === * High-density urban environments introduce severe multi-path fading, shadow fading, and Non-Line-of-Sight (NLOS) conditions. * '''Path Loss Modeling''': Empirical models such as the '''Okumura-Hata''' and '''COST 231''' models are applied to characterize Sub-GHz and 2 GHz propagation: : <math>PL(dB) = 69.55 + 26.16 \log_{10}(f) - 13.82 \log_{10}(h_b) - a(h_m) + (44.9 - 6.55 \log_{10}(h_b)) \log_{10}(d)</math> * '''Co-Channel Interference''': The uncoordinated use of unlicensed Sub-GHz (868/915 MHz) and 2.4 GHz ISM bands causes packet collisions, necessitating Adaptive Data Rate (ADR) and Listen-Before-Talk (LBT) mechanisms. === 5.3 System Interoperability and Standardization === * Proprietary hardware silos impede horizontal data flow between municipal departments. * Standardized semantic data models (such as oneM2M and OMA SpecWorks Lightweight M2M / LwM2M) are crucial for unifying heterogeneous sensors under common RESTful APIs.<ref name="onem2m">oneM2M Technical Specification: "TS-0001: Functional Architecture," Release 4.</ref> --- == 6. Security, Privacy, and Cyber-Physical Resilience == Because smart cities control critical civil infrastructure, security vulnerabilities can directly threaten public safety.<ref name="kumar2019">Kumar, P., Lin, Y., Bai, G., Paik, H. Y., & Chen, J. (2019). "Smart Grid Security: Threats, Vulnerabilities, and Solutions." ''ACM Computing Surveys'', 52(4), 1–36.</ref> * '''Attack Surfaces''': ** ''Perception Layer'': Hardware tampering, side-channel attacks, RF jamming, rogue node injection. ** ''Network Layer'': Man-in-the-Middle (MitM) attacks, Distributed Denial of Service (DDoS) against gateways, routing loop attacks (RPL attacks in 6LoWPAN). ** ''Application Layer'': Unauthorized access to citizen location data, SCADA command spoofing. * '''ECE Engineering Solutions''': ** '''Hardware Security Modules (HSMs) & Secure Elements (SE)''': Integration of cryptographic coprocessors (e.g., ATECC608A) for hardware-isolated root-of-trust, secure boot, and zero-knowledge private key storage. ** '''Lightweight Cryptography (LWC)''': Implementation of NIST-standardized lightweight ciphers (e.g., ASCON) to provide authenticated encryption on resource-constrained 8/16/32-bit MCUs with minimal latency and power penalty.<ref name="nist_lwc">NIST SP 800-226: "Guidelines for Evaluating Lightweight Cryptographic Systems".</ref> --- == 7. Summary == * The Internet of Things is the foundational nervous system of modern Smart Cities, translating physical urban dynamics into actionable digital intelligence. * A robust smart city relies on a tiered architecture: Perception, Network, Edge, and Application layers. * Wireless protocol selection is dictated by trade-offs between data rate, link range, operating spectrum, and battery longevity. LPWAN (LoRaWAN, NB-IoT) dominates static low-throughput sensing, while 5G caters to mission-critical, low-latency applications. * Hardware-level security, edge-computing paradigms, and efficient RF power management form the backbone of resilient urban deployments. --- == 8. Review and Numerical Questions == # Explain the 4-layer IoT architecture with specific reference to an automated flood monitoring and drainage system in an urban context. # A smart water meter node powered by a 3.6 V, 2400 mAh battery transmits data once every hour using LoRaWAN. #* During active transmission (duration = 2 seconds), it draws 40 mA. #* During sleep mode, it draws <math>5\ \mu\text{A}</math>. #* Calculate the theoretical battery life of the node in years (assume negligible self-discharge). # Compare and contrast LoRaWAN and NB-IoT with respect to spectrum usage, modulation schemes, deployment costs, and latency. # What are the distinct security vulnerabilities at the perception layer of an IoT network? How does a hardware Secure Element (SE) mitigate private key extraction? # Discuss why Edge Computing is preferred over centralized Cloud Computing for Cellular V2X (C-V2X) and real-time collision avoidance. --- == 9. References == {{reflist}} === Further Reading & Textbook Standards === * Stallings, W. (2018). ''Foundations of Modern Networking: SDN, NFV, QoE, IoT, and Cloud''. Addison-Wesley. {{ISBN|978-0134291079}}. * Kurose, J. F., & Ross, K. W. (2021). ''Computer Networking: A Top-Down Approach'' (8th ed.). Pearson. * 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description". * LoRa Alliance Technical Committee: "LoRaWAN® 1.0.4 Regional Parameters Specification". pqva1n221wwckzjnbauf3v99r4awcjl User:PushpenderSingh369/sandbox 2 486663 4679774 4679176 2026-11-03T12:30:39Z PushpenderSingh369 3629895 Replaced content with " == My Sandbox Pages == * [[User:PushpenderSingh369/sandbox/ArUco_Markers|ArUco Markers]]" 4679774 wikitext text/x-wiki == My Sandbox Pages == * [[User:PushpenderSingh369/sandbox/ArUco_Markers|ArUco Markers]] 4mzjv1cjalh0p08kh5mrw19sptuobqz Chess Opening Theory/1. e4/1...c6/2. d4/2...d5/3. Bd3/3...dxe4/4. Bxe4/4...Nf6/5. Bf3/5...Bf5/6. g4 0 486695 4679791 4679338 2026-11-03T14:18:03Z ~2026-58490-24 3630307 4679791 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Caro–Kann Defence: Mieses Attack, Hibbins-Khan Variation |eco=[[Chess/ECOB|B12]] |parent=[[../|5...Bf5]] }} == 6. g4 == It is a move ==References== {{Chess Opening Theory/Footer}} {{ChessStub}} 2180bsbn2jlqsxet1zjey16ngs2de1z 4679819 4679791 2026-11-03T16:11:46Z Codename Noreste 3441010 [[WB:REVERT|Reverted]] edit by [[Special:Contributions/~2026-58490-24|~2026-58490-24]] ([[User talk:~2026-58490-24|talk]]) to last version by Ggquazar 4679338 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Caro–Kann Defence: Mieses Attack, Hibbins-Khan Variation |eco=[[Chess/ECOB|B12]] |parent=[[../|5...Bf5]] }} == 6. g4 · Hibbins-Khan Variation == '''6. g4''' is the critical answer to 5...Bf5 and the most ambitious way of handling the Mieses Attack. The pawn hits the undefended bishop and claims space on the kingside. The bishop usually retreats with '''6...Bg6'''. White then plays h4, intending to chase the bishop again, with Ne2 and Nf4 as a further idea. A typical continuation is 7. h4 h5 8. g5 Nd5 9. e2 e6, with white keeping the initiative on the kingside.<ref>[https://lichess.org/J1qwsG6O Ditrealman v StrapoChi02M, Lichess 2026]</ref> ==References== {{reflist}} {{Chess Opening Theory/Footer}} {{ChessStub}} 90t3trk17ukhsucy4xu1ya2dnl00vpn Overview of Theology/Glossary 0 486719 4679859 4679529 2026-11-04T00:14:31Z Omphalographer 3427146 delete 4679859 wikitext text/x-wiki {{delete|Out of scope. This nonsense is clearly not a glossary.}} Terminology | Translating 'Plotinus' : Enneads...anonymous. Nite: Enneads ¥ || translated by his best friend, Porphyr. The transcription of Plotinus' mentations and verbal verses were written and recorded as testaments and treatises, serving to provide an Ancient Greek philosopher the historic recorded measurement of a "rule book" depicting the nature of existentialism of the here and n of w.. 'A man of his times', devoting his life's work to the issuance of advice on how to achieve enlightenment, knowledge and a concrete understanding of aegis; the world we live in and accept as the reality for the inhabitants of that intersection in that time and space continuum, an era 207 years after the birth of Jesus, the Son of GOD (refer to 'Hesiod'. His name reads as though it is transcribing hieroglyphics. 'H' ('historically') - 'ES ('is') - 'IOD' ('the word of God(s)+..) ."Hesiod is the word of the world in accordance with religious intonations and mutual admiration in believing all men are created equally and deserve respect and dignity to believe in what they want to." Ancient Greek philosophers did a very factual and detailed comprehensive body of work that covers any and every aspect to being a self or "soul". Words really DO wound the heart. This monumental testate to humanity reads like velvet frosting. Each page wrapped with intellect and transcendental ideologies without ever leaving the mythical tale of deities brought to life, yet always proving to be a read of pure delight and witticism preserved so beautifully for all to witness and absorb viscerally as well as neurologically. The following terms and phrases are a depiction of one individual's sentiments with hopes that this writer's muse will always spill the secrets of Plotinus. His thinking did bring about Neoplatonism, a field of study in philosophy that is another map to reality. z€£+ {{BookCat}} 6lrn9z0xjfeaxnn6sgu68x8d3cbn6p5 User:Badepalli praveen kumar reddy/sandbox 2 486729 4679790 4679547 2026-11-03T13:53:40Z Badepalli praveen kumar reddy 3630117 4679790 wikitext text/x-wiki = Understanding I2C and SPI Communication in Embedded Systems = '''1. Introduction to Serial Communication''' Serial communication transfers data sequentially, one bit at a time, over one or more signal lines. It is commonly used in embedded systems to connect a central processing device, such as a microcontroller, to peripheral components. Compared with using a separate group of parallel data wires, serial interfaces can reduce pin count and simplify circuit connections. A synchronous serial interface uses a clock signal to coordinate when bits are transmitted and sampled. I2C and SPI are both synchronous protocols, but they organize the bus differently. '''Abstract''' '''Serial communication is fundamental to embedded systems because it enables a microcontroller to exchange information with sensors, displays, memory devices and other peripherals. This chapter introduces two common synchronous serial protocols: Inter-Integrated Circuit (I2C) and Serial Peripheral Interface (SPI). It explains their signals, bus organization, communication sequences, strengths, limitations and practical applications. A comparison is provided to help readers select an appropriate protocol for an embedded-system design.''' '''Learning Objectives''' '''.Understand the purpose of serial communication in embedded systems.''' '''.Identify the signal lines used by I2C and SPI.''' '''.Describe the basic communication sequence of each protocol.''' '''.Compare I2C and SPI in terms of wiring, speed, addressing and duplex operation.''' '''.Recognize common applications and practical design considerations.2. I2C Communication Protocol''' '''2.1 Definition''' I2C (Inter-Integrated Circuit) is a synchronous, two-wire serial bus originally developed by Philips Semiconductors, now NXP Semiconductors. It allows multiple compatible devices to communicate over the same bus using a shared data line and a shared clock line. Devices are selected by address. '''2.2 I2C Signal Lines''' {| class="wikitable" |'''Signal''' |'''Full name''' |'''Purpose''' |- |SDA |Serial Data |Carries address, control and data bits. |- |SCL |Serial Clock |Provides timing for data transfer. |} SDA and SCL are normally implemented as open-drain or open-collector signals and require pull-up resistors. This arrangement allows devices to share the bus and supports acknowledgement and clock-stretching features. '''2.3 I2C Bus Diagram''' ''Figure 1. Multiple I2C targets share the SDA and SCL bus lines.'' '''2.4 Working Principle''' .A typical I2C transaction follows this general sequence: .START condition: the controller signals the beginning of a transaction. In the standard definition, SDA falls while SCL is high. .Address and direction: the controller sends the target address followed by a read/write direction bit. .Acknowledgement: the receiver indicates whether it accepted the address by pulling SDA low during the acknowledgement clock pulse. .Data transfer: data is sent in groups of eight bits. Each byte is followed by an acknowledgement bit. .STOP condition: the controller signals the end of the transaction. SDA rises while SCL is high. ''.Figure 2. Simplified illustrative I2C transaction. Exact timing depends on the selected I2C mode.'' '''2.5 I2C Addressing and Modes''' Many I2C devices use 7-bit addressing; 10-bit addressing is also defined. The address identifies the target on the shared bus. Common I2C speed grades include Standard-mode (100 kbit/s), Fast-mode (400 kbit/s), Fast-mode Plus (1 Mbit/s) and High-speed mode (3.4 Mbit/s). Some newer implementations support additional modes, so the device datasheet should always be checked. '''2.6 Advantages of I2C''' .Only two signal lines are required, regardless of the number of targets within bus limits. .Multiple devices can share the same bus. .Addressing avoids needing a separate chip-select line for every target. .Acknowledgement helps the controller detect whether a byte was accepted. '''2.7 Limitations of I2C''' .Usually offers lower throughput than SPI at comparable system conditions. .Pull-up resistor values and total bus capacitance affect signal rise time. .All devices share the bus, so only one controller normally transfers data at a time. .Address conflicts and bus faults must be considered during system design. '''2.8 Applications of I2C''' .Temperature, humidity and pressure sensors. .Real-time clock (RTC) modules. .EEPROMs and other low-to-moderate-speed memory devices. .OLED displays and small peripheral controllers. .Battery monitoring and power-management ICs. '''3. SPI Communication Protocol''' '''3.1 Definition''' SPI (Serial Peripheral Interface) is a synchronous serial communication interface widely used to connect microcontrollers to peripheral devices. It is commonly associated with Motorola's interface design. A conventional SPI connection uses separate data paths for transmission and reception, a clock line, and one or more chip-select lines. '''3.2 SPI Signal Lines''' {| class="wikitable" |'''Signal''' |'''Full name''' |'''Purpose''' |- |MOSI |Controller Out / Peripheral In |Carries data from controller to peripheral. |- |MISO |Controller In / Peripheral Out |Carries data from peripheral to controller. |- |SCLK |Serial Clock |Provides the timing reference. |- |CS/SS |Chip Select / Slave Select |Enables the selected peripheral. |} Terminology varies between manufacturers. Newer documentation may use controller/peripheral instead of master/slave, but MOSI, MISO, SCLK and CS remain common signal names. '''3.3 SPI Bus Diagram''' ''Figure 3. SPI data and clock lines are shared; each peripheral has a selection signal.'' '''3.4 Working Principle''' .The controller activates the chip-select line for the intended peripheral. .The controller generates clock pulses on SCLK. .Bits are shifted from the controller to the peripheral on MOSI. .At the same time, the peripheral can shift bits back to the controller on MISO. .When the transfer is complete, the controller deactivates the chip-select line. ''.Figure 4. Simplified illustrative SPI transfer showing simultaneous MOSI and MISO data paths.'' '''3.5 Clock Polarity and Phase''' SPI devices use clock polarity (CPOL) and clock phase (CPHA) settings to define the idle clock level and the clock edge on which data is sampled or changed. The four common combinations are called SPI modes 0, 1, 2 and 3. The controller and peripheral must use compatible settings; consult the peripheral datasheet. {| class="wikitable" |'''SPI mode''' |'''CPOL''' |'''CPHA''' |- |Mode 0 |0 |0 |- |Mode 1 |0 |1 |- |Mode 2 |1 |0 |- |Mode 3 |1 |1 |} '''3.6 Advantages of SPI''' .Often supports higher data rates than I2C. .Separate transmit and receive lines allow full-duplex transfers. .The protocol is relatively simple and has low framing overhead. .It is widely supported by displays, memory devices and converters. '''3.7 Limitations of SPI''' .Requires more signal connections than I2C. .A separate chip-select signal is commonly required for each peripheral. .There is no universal device-addressing or acknowledgement mechanism in basic SPI. .Clock mode, bit order and transfer length may differ between devices. '''3.8 Applications of SPI''' .SD and microSD card interfaces. .TFT and other graphical displays. .Serial flash memory. .Analog-to-digital and digital-to-analog converters. .High-speed sensors and radio-frequency transceiver modules. '''4. Comparison Between I2C and SPI''' {| class="wikitable" |'''Feature''' |'''I2C''' |'''SPI''' |- |Typical signal lines |2: SDA and SCL |4 main signals: MOSI, MISO, SCLK, CS |- |Bus organization |Shared two-wire bus |Shared clock/data lines plus target select |- |Device selection |Address |Chip-select signal |- |Data paths |One bidirectional data line |Separate transmit and receive lines |- |Duplex |Typically half-duplex |Can be full-duplex |- |Acknowledgement |ACK/NACK defined |No standard ACK in basic SPI |- |Pull-up resistors |Normally required |Not normally required for standard push-pull signals |- |Speed |Common modes from 100 kbit/s to 3.4 Mbit/s |Depends on devices; often higher |- |Best suited for |Many low/medium-speed peripherals |Higher-throughput peripheral transfers |} The listed speeds are representative, not guaranteed limits for every component. Actual performance depends on the controller, peripheral, wiring, electrical loading and configuration. '''5. Practical Example: A Mixed I2C and SPI System''' Consider a microcontroller-based monitoring device containing a temperature sensor, an OLED display and an SD card. The temperature sensor and OLED display may communicate over I2C, while the SD card may use SPI. The microcontroller reads the sensor, displays the measured value and stores records on the memory card. This example demonstrates that I2C and SPI are complementary interfaces. A single embedded system can use both protocols when the selected peripherals support them. '''6. Design Considerations''' .Check the logic-voltage levels of every device. A 5 V controller must not be connected directly to a 3.3 V-only input unless the device is 5 V tolerant or suitable level shifting is provided. .For I2C, select pull-up resistors according to bus voltage, capacitance, speed and device sink-current limits. .For SPI, verify CPOL, CPHA, bit order, maximum clock frequency and chip-select timing. .Keep signal wiring appropriate for the selected speed and electrical environment. .Use the device datasheet and the relevant protocol specification when designing the interface. '''7. Importance in Robotics and IoT''' In robotics, I2C is commonly used to connect motion sensors, environmental sensors and small displays. SPI is often used for memory, graphical displays and peripherals that need higher data throughput. In IoT devices, these interfaces allow a microcontroller to collect measurements, process data, show status and store information. The choice depends on the required speed, number of peripherals, wiring complexity and hardware support. '''8. Conclusion''' I2C and SPI are two important synchronous serial communication protocols in embedded systems. I2C reduces the number of signal wires and supports multiple addressed devices on a shared bus. SPI uses separate transmit and receive lines and can provide high-speed, full-duplex communication. Neither protocol is universally better: the correct choice depends on the application, peripheral requirements, electrical design and available microcontroller resources. '''9. References and Further Reading''' NXP Semiconductors, “UM10204: I2C-bus Specification and User Manual.” <nowiki>https://www.nxp.com/docs/en/user-guide/UM10204.pdf</nowiki> Analog Devices, “Introduction to SPI Interface.” <nowiki>https://www.analog.com/en/resources/analog-dialogue/articles/introduction-to-spi-interface.html</nowiki> Arduino Documentation. <nowiki>https://docs.arduino.cc/</nowiki> STMicroelectronics – Microcontroller and peripheral documentation. <nowiki>https://www.st.com/</nowiki> jvwc8olpzwtjw5xza6fus17p6kxy06t User:Anandu SN/sandbox 2 486736 4679898 4679558 2026-11-04T07:01:00Z Jcb 90773 4679898 wikitext text/x-wiki == Embedded Systems: The Brain Behind Smart Devices == [[File:Arduino Uno - R3.jpg|thumb|right|300px|An Arduino Uno, a popular microcontroller board used in embedded projects.]] === Introduction === An '''embedded system''' is a small computer built into a larger device to perform one specific task. Unlike a laptop or phone, which can run many different programs, an embedded system is designed to do one job reliably, often in real time. Washing machines, microwave ovens, cars, medical devices, drones and smart watches all rely on embedded systems. === Main Components === * '''Microcontroller (MCU):''' The "brain" that contains the processor, memory and input/output pins on a single chip. * '''Sensors:''' Collect information from the environment, such as temperature, light, distance or motion. * '''Actuators:''' Carry out actions, such as turning a motor, switching a relay or lighting an LED. * '''Firmware:''' The software stored in the device that tells the hardware what to do. * '''Communication interfaces:''' Protocols such as UART, I2C, SPI, Wi-Fi and Bluetooth let components and devices exchange data. === How It Works === An embedded system typically follows a simple loop: # Read data from sensors. # Process the data using the firmware. # Make a decision. # Control an actuator or send data to another device. For example, in a smart thermostat, a temperature sensor measures the room, the microcontroller compares it with the target value, and a relay switches the heater or cooler on or off. === Embedded Systems in Robotics and IoT === In '''robotics''', embedded systems control motors, read sensors and make real-time decisions, such as a line-following robot steering along a path. In the '''Internet of Things (IoT)''', embedded systems are connected to the internet so that devices can send data to the cloud and be monitored or controlled remotely, as in smart lights, wearable fitness trackers and smart agriculture sensors. === Applications === {| class="wikitable" ! Field !! Example |- | Home || Smart TVs, washing machines, smart speakers |- | Automotive || Airbags, ABS brakes, engine control units |- | Healthcare || Pacemakers, glucose monitors |- | Industry || Robotic arms, PLCs, automated production lines |- | Agriculture || Soil moisture sensors, automatic irrigation |} === Advantages and Challenges === '''Advantages:''' low cost, low power consumption, small size, high reliability. '''Challenges:''' limited memory and processing power, strict real-time requirements, security risks in connected devices. === Conclusion === Embedded systems quietly run much of the technology we use every day. As robotics and IoT grow, understanding how these small "brains" work is an important skill for future engineers and makers. === References === <references /> <ref>Wolf, Marilyn (2012). ''Computers as Components: Principles of Embedded Computing System Design'' (3rd ed.). Morgan Kaufmann. {{ISBN|978-0-12-388436-7}}.</ref> [[Category:Embedded systems]] 9qbfqu9e885r7tnj3k7q7ilzk1xgd5y User:D542006P/sandbox/Time Division Multiplexing 2 486752 4679804 4679618 2026-11-03T14:58:10Z D542006P 3629126 4679804 wikitext text/x-wiki == '''Time Division Multiplexing (TDM) : Synchronous and Asynchronous''' == === Introduction: === The sampled PAM waveform is off for most of the time and during the off period, the channel can be used to transmit samples of other waveforms and the whole concept of interleaving samples from several signals into a single waveform is called Time Division Multiplexing skhuza55xqs1rn3cijpwu7d5m6m8xhi 4679806 4679804 2026-11-03T15:13:32Z D542006P 3629126 4679806 wikitext text/x-wiki == '''Time Division Multiplexing (TDM) : Synchronous and Asynchronous''' == === Introduction: === The sampled PAM waveform is off for most of the time and during the off period, the channel can be used to transmit samples of other waveforms and the whole concept of interleaving samples from several signals into a single waveform is called Time Division Multiplexing [[File:Time division multiplexing.PNG|thumb|435x435px]] 0partczfkeqwgvhhb4ctqazh3ri4lsp 4679809 4679806 2026-11-03T15:40:37Z D542006P 3629126 4679809 wikitext text/x-wiki == '''Time Division Multiplexing (TDM) : Synchronous and Asynchronous''' == === Introduction: === [[File:Time division multiplexing.PNG|thumb|400x400px]]The sampled PAM waveform is off for most of the time and during the off period, the channel can be used to transmit samples of other waveforms and the whole concept of interleaving samples from several signals into a single waveform is called Time Division Multiplexing '''<big>Types of Time Division Multiplexing:</big>''' Time Division Multiplexing is mainly classified into two categories: Synchronous Time Division Multiplexing. Asynchronous Time Division Multiplexing (Statistical TDM). '''<big>Synchronous Time Division Multiplexing:</big>''' Synchronous Time Division Multiplexing is a technique in which each input source is assigned a fixed time slot in every transmission frame, irrespective of whether that source has information to transmit [[File:Multiplex-Synchron-en.svg|thumb|509x509px]] the multiplexer follows a predefined sequence to collect data from the input channels. Every source gets its turn at a regular interval. If an input source has no data available during its assigned time slot, that slot may remain unused. The receiver uses the same timing sequence to identify the data belonging to each input source. '''<big>Advantage:</big>''' * The transmission arrangement is simple and predictable. * Each input channel receives a guaranteed transmission opportunity. * Data separation at the receiver is straightforward. * It is suitable for applications that require regular and continuous data transmission. '''<big>Limitations:</big>''' * Unused time slots can waste transmission capacity. * The system may provide less flexibility when data traffic varies. * A fixed allocation may not efficiently support sources with different transmission requirements. '''<big>Applications</big><big>:</big>''' * Traditional digital telephone systems. * Time-slot-based digital communication networks. * Constant-rate data transmission systems. * Certain digital audio and video transmission systems. 17aj6u21r8zvyl6csopcdyv7sh2xarg 4679813 4679809 2026-11-03T15:49:05Z D542006P 3629126 4679813 wikitext text/x-wiki == '''Time Division Multiplexing (TDM) : Synchronous and Asynchronous''' == === Introduction: === [[File:Time division multiplexing.PNG|thumb|400x400px]]The sampled PAM waveform is off for most of the time and during the off period, the channel can be used to transmit samples of other waveforms and the whole concept of interleaving samples from several signals into a single waveform is called Time Division Multiplexing ====== Types of Time Division Multiplexing: ====== Time Division Multiplexing is mainly classified into two categories: Synchronous Time Division Multiplexing. Asynchronous Time Division Multiplexing (Statistical TDM). ====== <big>Synchronous Time Division Multiplexing:</big> ====== Synchronous Time Division Multiplexing is a technique in which each input source is assigned a fixed time slot in every transmission frame, irrespective of whether that source has information to transmit [[File:Multiplex-Synchron-en.svg|thumb|509x509px]] the multiplexer follows a predefined sequence to collect data from the input channels. Every source gets its turn at a regular interval. If an input source has no data available during its assigned time slot, that slot may remain unused. The receiver uses the same timing sequence to identify the data belonging to each input source. ====== Advantage: ====== * The transmission arrangement is simple and predictable. * Each input channel receives a guaranteed transmission opportunity. * Data separation at the receiver is straightforward. * It is suitable for applications that require regular and continuous data transmission. ====== Limitations: ====== * Unused time slots can waste transmission capacity. * The system may provide less flexibility when data traffic varies. * A fixed allocation may not efficiently support sources with different transmission requirements. ====== Applications: ====== * Traditional digital telephone systems. * Time-slot-based digital communication networks. * Constant-rate data transmission systems. * Certain digital audio and video transmission systems. fux0a4rk5cci3g1sr9w5sms5r0r5l3s Māori 0 486757 4679833 4679645 2026-11-03T19:41:50Z Kittycataclysm 3371989 +Template 4679833 wikitext text/x-wiki {{New book}} {{displaytitle|title=Te reo Māori - Māori language}} {{Stub}} {{Category 2}} '''Māori''', also known as '''te reo Māori''', is an Eastern Polynesian language and the language of the Māori people, the indigenous population of mainland New Zealand. The southernmost member of the Austronesian language family, it is related to Cook Islands Māori, Moriori, Tuamotuan, and Tahitian. =Preliminaries= The examples of Māori words, phrases, clauses and sentences used in this book are generally presented simultaneously in two written forms: one using the Māori alphabet, and an English translation. A phonemic transcription using the [[:w:International_Phonetic_Alphabet|IPA]], as well as recorded audio samples, is also used. bpapp91e5mmt1hd28gzd7ses6pk4bqp Cookbook talk:Pasta with Budget Bolognese Sauce 103 486758 4679832 4679665 2026-11-03T19:38:23Z Kittycataclysm 3371989 /* Recipe questions */ Reply 4679832 wikitext text/x-wiki == Recipe questions == @[[User:MathsScienceNerd1|MathsScienceNerd1]] what do you mean by "frozen hamburgers"? Do you mean pre-cooked and frozen hamburgers? Or, do you mean frozen raw ground beef? Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:06, 2 November 2026 (UTC) :Frozen hamburgers, as in hamburgers from the store. This is already pretty obvious, as I specifically mentioned it, and not minced beef. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 22:16, 2 November 2026 (UTC) ::Keep in mind, that if you look in the edit summary, it mentions the original Dutch version. I don't think I need to specify more in the recipe, this is already specific enough, the hamburgers would then be blended enough. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 22:19, 2 November 2026 (UTC) :::Thank you for the response! I ask only because "frozen hamburger" is a somewhat ambiguous term—some people use the term "hamburger" to mean raw ground/minced beef. Given the regional differences, I went ahead and noted "cooked" in the ingredients to avoid ambiguity. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:38, 3 November 2026 (UTC) nuii5w0cn3f9db7gkzxlzuf5p3hr20q Create Vampires/Precursors To Modern Vampires 0 486759 4679848 4679658 2026-11-03T21:15:06Z 3MMPEYTON 3393808 4679848 wikitext text/x-wiki == Precursors To Modern Vampires == The modern vampire took thousands of years to develop, emerging from early mythology, folklore, and the creative imagination of many writers and poets. <br> <br> To many, vampires have always been a part of the human story. Traces of the evolving vampire archetype can be found in Aztec, Ancient Greek, Hebrew and Mesopotamian mythology. <br> <br> '''Aztec Mythology:''' <br> In Aztec mythology, the ''cihuateteo'' were the spirits of women who had died during childbirth. These spirits became deified. <br> The ''cihuateteo'' were worshiped and feared. It was believed that they hunted during the night. They were believed to attack children, leaving them disabled or diseased. The ''cihuateteo'' could be killed by sunlight. [1] <br> <br> '''Ancient Greek Mythology:''' <br> Greece is one of the earliest sources to have contributed to the vampire legend. Ancient texts record tales of the ''lamiai'', ''keres'', ''empusai'', and the ''mormolykiai''. <br> <br> The ''lamiai'' were named after a Libyan queen, Lamia. She was loved by Zeus, the head of the Greek gods. Unfortunately, Hera, Zeus' jealous wife, found out about the secret affair and took away the children she had with Zeus. Unable to retaliate, Lamia retreated to a cave, where she dwelled and took her anger out on human children, by draining them of their blood. Her actions transformed her into a monster. Her image became a model for hideous beings with deformed, serpent-like lower bodies. <br> <br> The ''lamiai'' were known as demonic beings who suck the blood out of children, although the demonic beings could appear as beautiful women capable of seducing young men. <br> <br> The ''keres'' were the daughters of Nyx, the goddess of the night. They are spirit-like beings associated with the Fates, the divinities that control the life, destiny, and death of every human. It was believed that the ''keres'' sought out souls destined to die in a violent or bloody manner, yet they could only feed from the people the Fates allowed. [2] The ''keres'' were described as women with dark skin, leathery black wings, clawlike nails and white fangs. They hunted on battlefields, sucking the life and blood from fallen soldiers with terrifying shrieks. [2] <br> <br> According to Hollyhock in ''Vampires: A Handbook Of History & Lore Of The Undead'', the ''empusas'' were vampiric-beings that were similar to demons. They were believed to be the handmaidens to Hecate, the Greek goddess of magic and witchcraft. [2] The ''empusas'' were either beautiful women, or illusions of beautiful people. They sought out young men prone to their illusions, offering them wealth or fame in order to keep them under their control while they drained them of their energy or blood. [2] <br> <br> The ''mormolykiai'' were similar to the ''lamiai''. They were named after Mormo, a woman who consumed her own children. Mormo or Moromolyce have been described as a female specter, phantom, or ghost by modern commentators. For centuries, Mormo has been used as a word to frighten small children into behaving. [3] <br> <br> The ''vrykolakas'' were a group of revenants (reanimated corpses) who developed into classic vampires. Recorded in ancient Greek Literature, they were beings who returned to life, to join the living in order to carry out unfinished business. As they developed over time, they gained a thirst for blood and a vicious nature. <br> <br> ==== Reference: ==== 1. Melton, Gordon J. Phd. The Vampire Book: The Encyclopedia Of The Undead [Third Edition]. Visible Ink Press, 2014. <br> <br> 2. Hollyhock, Agnes. Vampires: A Handbook Of History & Lore Of The Undead. Wellfleet Press, 2024. <br> <br> 3. "Mormo." Wikipedia. Wikimedia Foundation, June 8, 2026. https://en.wikipedia.org/wiki/Mormo <br> <br> <br> <noinclude>{{Chapter navigation with TOC||Literary Construction|TOC mini}}</noinclude> <br> {{bookcat}} a3eg5o5rcdz4hfc7bt7zvb7w8syohp9 4679849 4679848 2026-11-03T21:42:59Z 3MMPEYTON 3393808 4679849 wikitext text/x-wiki == Precursors To Modern Vampires == The modern vampire took thousands of years to develop, emerging from early mythology, folklore, and the creative imagination of many writers and poets. <br> <br> To many, vampires have always been a part of the human story. Traces of the evolving vampire archetype can be found in Aztec, Ancient Greek, Hebrew and Mesopotamian mythology. <br> <br> '''Aztec Mythology:''' <br> In Aztec mythology, the ''cihuateteo'' were the spirits of women who had died during childbirth. These spirits became deified. <br> The ''cihuateteo'' were worshiped and feared. It was believed that they hunted during the night. They were believed to attack children, leaving them disabled or diseased. The ''cihuateteo'' could be killed by sunlight. [1] <br> <br> '''Ancient Greek Mythology:''' <br> Greece is one of the earliest sources to have contributed to the vampire legend. Ancient texts record tales of the ''lamiai'', ''keres'', ''empusai'', and the ''mormolykiai''. <br> <br> The ''lamiai'' were named after a Libyan queen, Lamia. She was loved by Zeus, the head of the Greek gods. Unfortunately, Hera, Zeus' jealous wife, found out about the secret affair and took away the children she had with Zeus. Unable to retaliate, Lamia retreated to a cave, where she dwelled and took her anger out on human children, by draining them of their blood. Her actions transformed her into a monster. Her image became a model for hideous beings with deformed, serpent-like lower bodies. <br> <br> The ''lamiai'' were known as demonic beings who suck the blood out of children, although the demonic beings could appear as beautiful women capable of seducing young men. <br> <br> The ''keres'' were the daughters of Nyx, the goddess of the night. They are spirit-like beings associated with the Fates, the divinities that control the life, destiny, and death of every human. It was believed that the ''keres'' sought out souls destined to die in a violent or bloody manner, yet they could only feed from the people the Fates allowed. [2] The ''keres'' were described as women with dark skin, leathery black wings, clawlike nails and white fangs. They hunted on battlefields, sucking the life and blood from fallen soldiers with terrifying shrieks. [2] <br> <br> According to Hollyhock in ''Vampires: A Handbook Of History & Lore Of The Undead'', the ''empusas'' were vampiric-beings that were similar to demons. They were believed to be the handmaidens to Hecate, the Greek goddess of magic and witchcraft. [2] The ''empusas'' were either beautiful women, or illusions of beautiful people. They sought out young men prone to their illusions, offering them wealth or fame in order to keep them under their control while they drained them of their energy or blood. [2] <br> <br> The ''mormolykiai'' were similar to the ''lamiai''. They were named after Mormo, a woman who consumed her own children. Mormo or Moromolyce have been described as a female specter, phantom, or ghost by modern commentators. For centuries, Mormo has been used as a word to frighten small children into behaving. [3] <br> <br> The ''vrykolakas'' were a group of revenants (reanimated corpses) who developed into classic vampires. Recorded in ancient Greek Literature, they were beings who returned to life, to join the living in order to carry out unfinished business. As they developed over time, they gained a thirst for blood and a vicious nature. <br> <br> '''Hebrew And Mesopotamian Mythology:''' <br> Lilith is a popular figure in Hebrew folklore. Stories of Lilith have spread far and wide. Her mythology continues, emerging into popular culture. <br> <br> Lilith originated as a storm demon. She was a part of a group, the Sumerian vampire demons, that included Irdu Lili, Ardat Lili, and Lillu. She can be found in the ''Gilgamesh Epic'' (2000 B.C.E), the ancient Babylonian story, where she is described as a vampire harlot incapable of having children, with breast that were dry. [1] Lilith appeared in the Talmud, where she was recorded as being married to Adam before he married Eve. According to the tale, Lilith and Adam fought, with Lilith using her magical ability to fly away to the Red Sea, a home of demons. There she took many lovers and had many children called the lilim. [1] <br> <br> Lilith is considered a malicious and bloodthirsty demon that ate babies and drank human blood. To many people, she is the mother of monsters, including vampires. [2] <br> <br> <br> ==== Reference: ==== 1. Melton, Gordon J. Phd. The Vampire Book: The Encyclopedia Of The Undead [Third Edition]. Visible Ink Press, 2014. <br> <br> 2. Hollyhock, Agnes. Vampires: A Handbook Of History & Lore Of The Undead. Wellfleet Press, 2024. <br> <br> 3. "Mormo." Wikipedia. Wikimedia Foundation, June 8, 2026. https://en.wikipedia.org/wiki/Mormo <br> <br> <br> <noinclude>{{Chapter navigation with TOC||Literary Construction|TOC mini}}</noinclude> <br> {{bookcat}} abcxbtpxzvipsg57jz9zcah9mxdyth8 4679850 4679849 2026-11-03T21:46:54Z 3MMPEYTON 3393808 4679850 wikitext text/x-wiki == Precursors To Modern Vampires == The modern vampire took thousands of years to develop, emerging from early mythology, folklore, and the creative imagination of many writers and poets. <br> <br> To many, vampires have always been a part of the human story. Traces of the evolving vampire archetype can be found in Aztec, Ancient Greek, Hebrew and Mesopotamian mythology. <br> <br> '''Aztec Mythology:''' <br> In Aztec mythology, the ''cihuateteo'' were the spirits of women who had died during childbirth. These spirits became deified. <br> The ''cihuateteo'' were worshiped and feared. It was believed that they hunted during the night. They were believed to attack children, leaving them disabled or diseased. The ''cihuateteo'' could be killed by sunlight. [1] <br> <br> '''Ancient Greek Mythology:''' <br> Greece is one of the earliest sources to have contributed to the vampire legend. Ancient texts record tales of the ''lamiai'', ''keres'', ''empusai'', and the ''mormolykiai''. <br> <br> The ''lamiai'' were named after a Libyan queen, Lamia. She was loved by Zeus, the head of the Greek gods. Unfortunately, Hera, Zeus' jealous wife, found out about the secret affair and took away the children she had with Zeus. Unable to retaliate, Lamia retreated to a cave, where she dwelled and took her anger out on human children, by draining them of their blood. Her actions transformed her into a monster. Her image became a model for hideous beings with deformed, serpent-like lower bodies. <br> <br> The ''lamiai'' were known as demonic beings who suck the blood out of children, although the demonic beings could appear as beautiful women capable of seducing young men. <br> <br> The ''keres'' were the daughters of Nyx, the goddess of the night. They are spirit-like beings associated with the Fates, the divinities that control the life, destiny, and death of every human. It was believed that the ''keres'' sought out souls destined to die in a violent or bloody manner, yet they could only feed from the people the Fates allowed. [2] The ''keres'' were described as women with dark skin, leathery black wings, clawlike nails and white fangs. They hunted on battlefields, sucking the life and blood from fallen soldiers with terrifying shrieks. [2] <br> <br> According to Hollyhock in ''Vampires: A Handbook Of History & Lore Of The Undead'', the ''empusas'' were vampiric-beings that were similar to demons. They were believed to be the handmaidens to Hecate, the Greek goddess of magic and witchcraft. [2] The ''empusas'' were either beautiful women, or illusions of beautiful people. They sought out young men prone to their illusions, offering them wealth or fame in order to keep them under their control while they drained them of their energy or blood. [2] <br> <br> The ''mormolykiai'' were similar to the ''lamiai''. They were named after Mormo, a woman who consumed her own children. Mormo or Moromolyce has been described as a female specter, phantom, or ghost by modern commentators. For centuries, Mormo has been used as a word to frighten small children into behaving. [3] <br> <br> The ''vrykolakas'' were a group of revenants (reanimated corpses) who developed into classic vampires. Recorded in ancient Greek Literature, they were beings who returned to life, to join the living in order to carry out unfinished business. As they developed over time, they gained a thirst for blood and a vicious nature. <br> <br> '''Hebrew And Mesopotamian Mythology:''' <br> Lilith is a popular figure in Hebrew folklore. Stories of Lilith have spread far and wide. Her mythology continues, emerging into popular culture. <br> <br> Lilith originated as a storm demon. She was a part of a group, the Sumerian vampire demons, that included Irdu Lili, Ardat Lili, and Lillu. She can be found in the ''Gilgamesh Epic'' (2000 B.C.E), the ancient Babylonian story, where she is described as a vampire harlot incapable of having children, with breast that were dry. [1] Lilith appeared in the Talmud, where she was recorded as being married to Adam before he married Eve. According to the tale, Lilith and Adam fought, with Lilith using her magical ability to fly away to the Red Sea, a home of demons. There she took many lovers and had many children called the lilim. [1] <br> <br> Lilith is considered a malicious and bloodthirsty demon that ate babies and drank human blood. To many people, she is the mother of monsters, including vampires. [2] <br> <br> <br> ==== Reference: ==== 1. Melton, Gordon J. Phd. The Vampire Book: The Encyclopedia Of The Undead [Third Edition]. Visible Ink Press, 2014. <br> <br> 2. Hollyhock, Agnes. Vampires: A Handbook Of History & Lore Of The Undead. Wellfleet Press, 2024. <br> <br> 3. "Mormo." Wikipedia. Wikimedia Foundation, June 8, 2026. https://en.wikipedia.org/wiki/Mormo <br> <br> <br> <noinclude>{{Chapter navigation with TOC||Literary Construction|TOC mini}}</noinclude> <br> {{bookcat}} 9rwgto1dnmfu1fd3bolt2zzq219oeda User:PushpenderSingh369/sandbox/ArUco Markers 2 486778 4679772 4679755 2026-11-03T12:18:20Z PushpenderSingh369 3629895 Created introduction section 4679772 wikitext text/x-wiki == ArUco Marker == An ArUco marker is a type of square fiducial marker used in computer vision applications for identification, camera pose estimation and spatial localization. It consists of black and white binary pattern enclosed within a square border. ArUco markers are commonly used in [[robotics]] and augmented reality, where they provide identifiable visual references for determining the position and orientation of cameras or objects. djtvosb1puyf8evt09k3l301031u4pw User:Bojja Mahesh Yadav/sandbox/1.1 Introduction to Mobile Communication 2 486783 4679886 4679763 2026-11-04T06:04:43Z Bojja Mahesh Yadav 3629813 /* 1. Meaning of Mobile Communication */ 4679886 wikitext text/x-wiki = 1.1 Introduction to Mobile Communication = == 1. Meaning of Mobile Communication == Mobile communications is a wireless communication technology that allows users to communicate with each other using mobile devices. RF electromagnetic waves are used to send and receive voice, text, images and data between devices and communication networks. Mobile communication lets people talk while they travel from one place to another without needing a cable. <ref>International Telecommunication Union (ITU), [https://www.itu.int/net4/mob/ituemf/en/emfguide_m.html ITU EMF Guide].</ref> == 2. Basic Components of Mobile Communication == A mobile communication system consists of several important components. # Mobile Phone: A device used to make calls, send messages and access the internet. # Base Station: Equipment that communicates wirelessly with mobile phones in a particular coverage area. # Antenna: A device that transmits and receives radiofrequency signals. # Base Station Controller: In traditional GSM networks, it controls and manages multiple base stations. # Core Network: The central part of the network that manages connections and routes communication to the destination. [[File:Cellular mobile Antenna and Dipole Antenna 2018 v1.jpg|thumb|center|250px|Mobile communication antenna. Photograph by Goodtiming8871, Wikimedia Commons, CC BY-SA 4.0.]] == 3. How Mobile Communication Works == Mobile communication works through the transmission and reception of radiofrequency signals. The basic process is: # A user makes a call or sends data using a mobile phone. # The mobile phone transmits radiofrequency signals to a nearby base station. # The base station receives the signals and forwards them to the network. # The core network processes the communication and routes it to the destination. # The receiving mobile device receives the information through its serving base station. <ref>International Telecommunication Union (ITU), [https://www.itu.int/net4/mob/ituemf/en/emfguide_m.html ITU EMF Guide].</ref> == 4. Generations of Mobile Communication == Mobile communication technology has developed through different generations. # 1G: First-generation technology provided basic analogue voice communication. # 2G: Second-generation technology introduced digital voice communication and SMS. # 3G: Third-generation technology improved mobile internet access and multimedia services. # 4G: Fourth-generation technology provided high-speed mobile broadband and better data services. # 5G: Fifth-generation technology supports higher data rates, lower latency and communication between a large number of connected devices. Each generation introduced improvements in network capacity, speed and communication services. <ref>International Telecommunication Union (ITU), [https://www.itu.int/net4/mob/ituemf/en/emfguide_m.html ITU EMF Guide].</ref> == 5. Role of Mobile Towers == Mobile towers support wireless communication by holding antennas and other network equipment at suitable heights. These antennas transmit and receive radiofrequency signals between mobile devices and the communication network. Mobile towers help to: * Provide network coverage in different areas. * Support voice calls and mobile data services. * Connect mobile devices to the network. * Improve communication capacity in areas with many users. [[File:A mobile communication tower in Kakinada.jpg|thumb|center|400px|Mobile communication tower in Kakinada, India. Photograph by Adityamadhav83, Wikimedia Commons, CC BY-SA 4.0.]] <ref>Telecom Regulatory Authority of India (TRAI), [https://www.trai.gov.in/sites/default/files/2024-10/EMF_Information_Paper_30.07.2014.pdf Radiation from Mobile BTS, Information Paper].</ref> == 6. Importance of Mobile Communication == Mobile communication plays an important role in everyday life. * Personal Communication: Helps people communicate through calls and messages. * Education: Supports online learning and access to educational resources. * Business: Helps organizations communicate with customers and employees. * Emergency Services: Supports communication during emergencies and disasters. * Internet Access: Provides access to online services, information and digital applications. == 7. Mobile Communication and Tower Radiation == Mobile Communication systems make use of Radio Frequency (RF) Electromagnetic waves to communicate information between mobile devices and base station antennae. These RF waves are a form of non-ionising electromagnetic radiation. During normal operation of the mobile network the mobile towers will emit radio frequency signals. Depending on the power levels of the antennae, direction of the antenna, distance and surrounding factors will have an impact on the exposure levels. Within India, the Department of Telecommunications (DoT) sets and enforces the exposure limits of electromagnetic fields (EMF’s) around mobile base stations. This is discussed in further detail within the following chapters. <ref>World Health Organization (WHO), [https://www.who.int/teams/environment-climate-change-and-health/radiation-and-health/non-ionizing/wireless Base stations and wireless technologies].</ref> == 8. Summary == Mobile communication is a vital wireless technology that is responsible for providing voice, messaging and internet services. It involves using mobile devices, antennas, base stations and core networks to send information. Mobile towers are very important when it comes to mobile communication. Knowing how mobile communication works will help you understand radio frequency radiation, exposure levels and mobile towers in India. == References == <references /> oneghri694j06nvr09zb0x30dusyaej User:Bojja Mahesh Yadav/sandbox/1.2 Introduction to Cell Tower Radiation 2 486784 4679888 4679764 2026-11-04T06:14:34Z Bojja Mahesh Yadav 3629813 /* 1. Introduction */ 4679888 wikitext text/x-wiki = Introduction to Cell Tower Radiation = == 1. Introduction == A mobile communication system is an essential part of our lives. Mobile phones can be used for communication using wireless signals. They allow us to make voice calls, send text messages and access the internet. This is done via antennas installed on mobile communication towers. Cell tower radiation is a form of ‘Radio Frequency’ (RF) electromagnetic radiation produced by the antennas used in mobile communication networks. Understanding this is important when looking at exposure levels, measuring radiation and standards in India. <ref>World Health Organization (WHO), [https://www.who.int/teams/environment-climate-change-and-health/radiation-and-health/non-ionizing/wireless Base stations and wireless technologies].</ref> [[File:Cell-Tower.jpg|thumb|center|300px|A cellular base station tower. Photograph by Justin Smith, Wikimedia Commons, CC BY-SA 2.5.]] == 2. Meaning of Cell Tower Radiation == Cell tower radiation refers to radio frequency electromagnetic radiation created by transmission antenna towers. Mobile phone signal is transmitted via radio wave signals sent from antennas on the mobile tower. This communicates with the mobile phone and other network devices, carrying information such as voice, messaging and internet data. Important terms: * Radiofrequency (RF):A range of electromagnetic frequencies used in wireless communication. * Electromagnetic waves:Waves that carry energy through space. * Non-ionizing radiation:Radiation that does not have enough energy per photon to remove electrons from atoms or molecules. * EMF: Electromagnetic field associated with electric and magnetic forces. <ref>World Health Organization (WHO), [https://www.who.int/news-room/questions-and-answers/item/radiation-electromagnetic-fields Radiation: Electromagnetic fields].</ref> == 3. Sources of Radiation from Mobile Towers == The main sources of radiofrequency emissions from a mobile communication site include: # Panel Antennas:These antennas transmit and receive radiofrequency signals to provide coverage in a particular direction. # Microwave Antennas:These are used for wireless communication links between network locations. # Radio Transmitter Equipment:This equipment generates radiofrequency signals that are supplied to the antennas. # Base Transceiver Station (BTS):The BTS contains communication equipment that connects mobile devices with the mobile network. [[File:Cellular Mobile UHF Antenna Tower.jpg|thumb|center|300px|A cellular mobile antenna tower with multiple antennas. Photograph by Goodtiming8871, Wikimedia Commons, CC BY-SA 4.0.]] == 4. Characteristics of Cell Tower Radiation == Cell tower radiation has the following characteristics: # Non-Ionizing Nature: Radiofrequency radiation is classified as non-ionizing radiation. # Frequency: Mobile communication systems operate in different frequency bands depending on the technology and service. # Power Density: Power density describes the amount of electromagnetic power passing through a unit area. It is commonly expressed in watts per square metre (W/m²). # Directional Transmission:Mobile tower antennas are designed to transmit signals in specific directions to provide network coverage. # Exposure Variation: Exposure levels depend on antenna power, direction, distance and surrounding environmental conditions. == 5. Factors Affecting Radiation Exposure == The level of radiofrequency exposure near a mobile tower depends on several factors: * Distance from the antenna: Exposure generally decreases as distance from an antenna increases under comparable conditions. * Transmitting power:The power supplied to an antenna affects the emitted signal. * Antenna direction: Antenna orientation and tilt influence the distribution of radiofrequency energy. * Frequency: Different operating frequencies have different propagation characteristics. * Surrounding environment: Buildings, trees and other structures can affect signal propagation through reflection, absorption and obstruction. * Network activity: The amount of radiofrequency transmission varies with network operation and traffic. Actual exposure should be assessed through suitable measurement procedures. Distance alone does not establish whether a location meets the applicable exposure limit. == 6. Possible Health Effects and Scientific Assessment == International scientific and public health bodies have looked into this. Radio frequency energy can cause tissue heating at sufficiently high levels of exposure. Limits have been set to help ensure that people are protected from known harmful effects. The World Health Organisation (WHO) provides a review of the scientific evidence on radio frequency electromagnetic fields. The organisation explains that exposure from base stations in areas that are open to the general public is generally well below the international guidelines. It is important to look at how the science is assessing the concern around radiation from mobile towers. <ref>World Health Organization (WHO), [https://www.who.int/teams/environment-climate-change-and-health/radiation-and-health/non-ionizing/wireless Base stations and wireless technologies].</ref> == 7. Importance of Studying Cell Tower Radiation == Studying cell tower radiation is important for the following reasons: * To understand the working of mobile communication antennas. * To identify the sources of radiofrequency emissions. * To understand the factors affecting human exposure. * To study radiation measurement methods and equipment. * To learn about Indian and international exposure standards. * To understand the role of government authorities in monitoring compliance. * To improve public awareness through reliable scientific information. == 8. Summary == Cell tower radiation refers to radio-frequency electromagnetic radiation that is emitted from antennas of mobile communication networks. This type of radiation falls under the category of non-ionizing radiation, and the amount depends on various factors like the antenna power, direction, frequency etc. Understanding about Cell tower radiation will provide you the basics of understanding Indian radiation standards, EMF measurement processes, health and safety standards and regulations. == References == <references /> 1lmnwptwx4lqurlv6oa79wxiyw2679w User:Bojja Mahesh Yadav/sandbox/1.3 Need for Radiation Standards in India 2 486785 4679889 4679765 2026-11-04T06:18:15Z Bojja Mahesh Yadav 3629813 /* 1. Introduction */ 4679889 wikitext text/x-wiki = 1.3 Need for Radiation Standards in India = == 1. Introduction == The mobile communication sector is now an integral part of our lives. Mobile towers help connect users to wireless networks that can make voice calls, send text messages and access the internet. It is important to control the electromagnetic field (EMF) emissions from mobile communication towers, as mobile networks are expanding in India. Radiation standards set exposure limits for radio frequency (RF) electromagnetic fields. The Department of Telecommunications (DoT) under the Ministry of Communications is responsible for defining and monitoring EMF exposure requirements for mobile base stations in India.<ref>Department of Telecommunications, Government of India, [https://www.dot.gov.in/static/uploads/2025/08/f5e00b30612004ac3a993a6f93d68d95.pdf Office Memorandum on EMF Radiation, 27 February 2014].</ref>[[File:Mobile tower in fields in Punjab.jpg|thumb|center|400px|Mobile communication tower in Punjab, India. Photograph from Wikimedia Commons, CC BY-SA 4.0.]] == 2. Need for Radiation Standards == Radiation standards are required for the following reasons: # Public protection: Exposure limits are designed to protect people against established adverse effects associated with excessive RF exposure. # Uniform regulations: Standards provide common technical requirements for telecom service providers across India. # Monitoring and compliance: They help government authorities assess whether mobile towers follow prescribed exposure limits. # Public awareness: Radiation standards provide reliable information to address public concerns about mobile tower emissions. # Scientific assessment: Standards are developed with reference to scientific research and recommendations from recognized organizations. # Regulatory control: They provide a basis for inspections, compliance checks and action against violations. == 3. Department of Telecommunications (DoT) == The Department of Telecommunications is part of the Ministry of Communications, Government of India. It plays an important role in regulating EMF emissions from mobile communication towers. The main responsibilities of DoT include: * Prescribing EMF exposure limits for mobile base stations. * Issuing technical guidelines for telecom service providers. * Requiring service providers to submit EMF compliance certificates. * Conducting inspections and audits through its field units. * Providing information about mobile tower emissions to the public. * Taking action when a site does not comply with prescribed requirements. DoT has prescribed public exposure limits for mobile base stations at one-tenth of the corresponding ICNIRP limits.<ref>Department of Telecommunications, Government of India, [https://www.dot.gov.in/static/uploads/2025/08/f5e00b30612004ac3a993a6f93d68d95.pdf Office Memorandum on EMF Radiation, 27 February 2014].</ref> [[File:A mobile communication tower in Kakinada.jpg|thumb|center|400px|Mobile communication tower in Kakinada, India. Photograph by Adityamadhav83, Wikimedia Commons, CC BY-SA 4.0.]] == 4. Indian Government Regulations == The Government of India has introduced regulations and guidelines to control EMF emissions from mobile communication towers. Important regulatory measures include: # Adoption of ICNIRP guidelines: India adopted internationally recognized exposure guidelines as a basis for regulating RF emissions. # Stricter exposure limits: The Government prescribed public exposure limits at one-tenth of the corresponding ICNIRP limits. # Compliance requirements: Telecom service providers are required to follow DoT instructions and submit compliance information. # Monitoring procedures: DoT uses technical assessment, inspections and monitoring to check compliance. # Public information: The Tarang Sanchar portal provides information about mobile towers and available EMF compliance details. These measures support the regulation and monitoring of radiofrequency emissions from mobile base stations.<ref>Department of Telecommunications, Government of India, [https://www.dot.gov.in/static/uploads/2025/08/453dc8cbd95d0e40b867611ef5a55284.pdf Advisory Guidelines for State Governments for Issue of Clearance for Installation of Mobile Towers].</ref> == 5. EMF Exposure Limits in India == EMF limits are used to limit the level of EMF exposure. The Department of Telecommunications has defined EMF limits based on Electric Field Strength, Magnetic Field Strength and Power Density. The following table gives an example of the power density limits for some frequency bands used in mobile communications. {| class="wikitable" |+ Indian public exposure limits for selected mobile communication frequencies ! Frequency ! Power density limit |- | 900 MHz | 0.45 W/m² |- | 1800 MHz | 0.90 W/m² |- | 2100 MHz and above | 1.00 W/m² |} <ref>Department of Telecommunications, Government of India, [https://www.dot.gov.in/static/uploads/2025/08/453dc8cbd95d0e40b867611ef5a55284.pdf Advisory Guidelines for State Governments for Issue of Clearance for Installation of Mobile Towers].</ref> Power density is measured in watts per square metre (W/m²). The applicable exposure limit depends on the frequency band and the current DoT requirements. == 6. Comparison with International Standards == International guidelines have been developed for restricting public exposure to radiofrequency electromagnetic fields. Scientific guidelines have been developed by the International Commission on Non-Ionizing Radiation Protection (ICNIRP) to reduce exposures to non-ionizing radiation. The World Health Organization (WHO) provides scientific information and guidance on electromagnetic fields and public health. These guidelines have been adopted by India and public exposure limits were set to a tenth of those specified by ICNIRP for emissions from mobile base stations.<ref>Department of Telecommunications, Government of India, [https://www.dot.gov.in/static/uploads/2025/08/f5e00b30612004ac3a993a6f93d68d95.pdf Office Memorandum on EMF Radiation, 27 February 2014].</ref> == 7. EMF Compliance and Government Monitoring == Telecom service providers must ensure that their mobile base stations comply with the prescribed EMF exposure limits. The compliance process includes: * Submission of self-certification by telecom service providers. * Compliance checks when a base station is installed or upgraded. * Submission of compliance information. * Inspection and testing by authorized DoT field units. * Action against sites found to be non-compliant. DoT has established procedures for submitting EMF compliance information. The Tarang Sanchar portal provides information about mobile towers and EMF compliance. Website: [https://tarangsanchar.gov.in/ Tarang Sanchar Portal] [[File:Base Transceiver Station.jpg|thumb|center|350px|Base transceiver station equipment in India. Photograph by abhiriksh, Wikimedia Commons, CC BY-SA 3.0.]] <ref>Department of Telecommunications, Government of India, [https://www.dot.gov.in/ Department of Telecommunications official website].</ref> == 8. Importance of Public Awareness == Public awareness is important because people often have questions about mobile tower radiation and its possible effects. Awareness programmes should explain: * The meaning of radiofrequency radiation. * The purpose of EMF exposure limits. * The role of the Department of Telecommunications. * How mobile tower emissions are measured. * How to check available tower compliance information. * The importance of scientific evidence and government regulations. Citizens can use the Tarang Sanchar portal to access available information about mobile towers and EMF compliance. == 9. Summary == Radiation standards help control electromagnetic emissions from mobile communication towers in India. They include guidelines for exposure levels set by the Department of Telecommunications and monitored by telecom service providers. Public exposure levels are a tenth of the ICNIRP levels in India. Guidelines, self certification, inspections and public information portals are used to monitor. Understanding radiation standards can help students and the public understand more about radiation emitted from mobile towers and how they are controlled by exposure limits. == References == <references /> hx96j8czc9oxriqy56nxlw8suv7qul9 User:Wikilalithbook/sandbox 2 486789 4679771 2026-11-03T12:16:19Z Wikilalithbook 3629892 added images 4679771 wikitext text/x-wiki __TOC__ == Learning Objectives == After studying this chapter, students of Electronics & Communication Engineering (ECE) should be able to: * Contrast the 3-layer, 5-layer, and IEEE P2413 / ITU-T standard IoT reference architectural models. * Understand the hardware interfacing of analog and digital transducers via I2C, SPI, UART, and precision ADCs. * Analyze the low-power wireless networking stack, including IEEE 802.15.4, 6LoWPAN adaptation, and the RPL routing algorithm. * Differentiate between application-layer protocols (MQTT, CoAP, HTTP/REST, AMQP) based on transport overhead, latency, and reliability. * Evaluate Edge, Fog, and Cloud computing paradigms for bandwidth optimization and real-time inference. * Design end-to-end IoT solutions across core applications: Precision Agriculture, Internet of Medical Things (IoMT), Smart Grid, and Industrial Telemetry. --- == 1. Introduction and Architectural Evolution == [[File:Internet of Things.svg|thumb|right|340px|Evolution and structural convergence across physical sensing, connectivity, and analytical layers in the IoT ecosystem.]] The '''Internet of Things (IoT)''' is an expansive paradigm wherein physical objects ("things") embedded with transducers, microcontrollers, and transceivers seamlessly communicate over IP-based networks to exchange telemetry and receive operational commands without human intervention.<ref name="gubbi2013">Gubbi, J., Buyya, R., Marusic, S., & Palaniswami, M. (2013). "Internet of Things (IoT): A vision, architectural elements, and future directions." ''Future Generation Computer Systems'', 29(7), 1645–1660. doi:10.1016/j.future.2013.01.010.</ref> Unlike traditional localized embedded systems, IoT devices are globally addressable and integrate into larger data-processing pipelines, transforming raw environmental phenomena into actionable business and engineering intelligence. == 2. IoT Reference Architectures == To manage the heterogeneity of hardware platforms and communication standards, IoT is organized into formal layered architectural models.<ref name="al-fuqaha2015">Al-Fuqaha, A., Guizani, M., Mohammadi, M., Aledhari, M., & Ayyash, M. (2015). "Internet of Things: A survey on enabling technologies, protocols, and applications." ''IEEE Communications Surveys & Tutorials'', 17(4), 2347–2376.</ref> === 2.1 The 3-Layer and 5-Layer Architectures === [[File:Iot apps.png|thumb|left|320px|Hierarchical classification of IoT systems connecting smart physical objects to diverse domain applications.]] * '''3-Layer Classical Model''': #* '''Perception Layer''': Transducers, RFID tags, sensors, and actuators that sense physical variables and convert them into electrical signals. #* '''Network Layer''': Transmission media (Wi-Fi, Cellular, LPWAN, Ethernet) that route packets to data-processing servers. #* '''Application Layer''': End-user interfaces, dashboards, and domain-specific services. * '''5-Layer Extended Model''' (Standardized for Enterprise IoT): {| class="wikitable" style="width: 100%;" ! Layer !! Key Hardware / Technologies !! Core Engineering Function |- | '''Business Layer''' | System dashboards, ERP, decision support models, billing. | High-level governance, business logic, economic monetization, KPI tracking. |- | '''Application Layer''' | Mobile apps, cloud APIs, SCADA consoles, smart health/home portals. | Domain-specific user interactions and service presentation. |- | '''Processing (Middleware) Layer''' | Cloud servers, distributed time-series databases, stream analytics. | Data ingestion, semantic mediation, machine learning inference, persistent storage. |- | '''Transport (Network) Layer''' | IPv6/6LoWPAN, 4G/5G NR, LoRaWAN, Wi-Fi (802.11ax), BLE Mesh. | Packetization, routing, addressing, Quality of Service (QoS) management. |- | '''Perception Layer''' | MEMS sensors, thermocouples, load cells, ADCs, microcontrollers. | Physical parameter acquisition, analog-to-digital conversion, edge pre-filtering. |} == 3. Perception Layer: Sensor Interfacing & Signal Conditioning == The perception layer converts physical environmental phenomena into digitized binary representations suitable for embedded microcontrollers. === 3.1 Digital Serial Bus Interfaces === {| class="wikitable" style="width: 100%; text-align: center;" ! Protocol !! Bus Lines !! Mode !! Maximum Clock Rate !! Addressing !! Typical Range |- | '''I2C''' (Inter-Integrated Circuit) || 2 (SDA, SCL) || Half-Duplex || 100 kbps (Standard), 400 kbps (Fast), 3.4 Mbps (High-Speed) || 7-bit or 10-bit addressing || On-board (< 30 cm) |- | '''SPI''' (Serial Peripheral Interface) || 4 (MOSI, MISO, SCK, CS) || Full-Duplex || 10 – 50+ Mbps || Dedicated Chip Select line per slave || On-board (< 20 cm) |- | '''UART''' (Universal Asynchronous Receiver-Transmitter) || 2 (TX, RX) || Full-Duplex || Standard baud rates up to 921.6 kbps || Point-to-Point (No address) || Up to 15 m (RS-232) |- | '''1-Wire''' (Dallas) || 1 (Data + Parasitic Power) || Half-Duplex || 16.3 kbps || Unique 64-bit ROM code || Up to 100 m |} === 3.2 Analog Conditioning and ADC Quantization === Real-world analog transducers (e.g., strain gauges, thermocouples, photodetectors) require signal conditioning prior to ADC sampling: * '''Instrumentation Amplifiers (INA)''': High Common-Mode Rejection Ratio (CMRR > 100 dB) to eliminate ground loop noise. * '''Anti-Aliasing Filter (AAF)''': Analog low-pass filter satisfying the Nyquist criteria (<math>f_{\text{cutoff}} \le \frac{f_s}{2}</math>). * '''Quantization Resolution''': :<math>V_{\text{LSB}} = \frac{V_{\text{ref}}}{2^N}</math> where <math>N</math> is the ADC bit resolution (e.g., for <math>N = 12\text{ bits}</math> and <math>V_{\text{ref}} = 3.3\text{ V}</math>, <math>V_{\text{LSB}} = 0.805\text{ mV}</math>). == 4. Connectivity and Protocol Stack == [[File:Data Networks classification by spatial scope.svg|thumb|right|340px|Classification of network topologies by spatial reach: from Body Area Networks (BAN) and PAN to WAN and LPWAN.]] IoT demands lightweight protocols capable of operating over constrained links characterized by high packet error rates and duty-cycle limitations. === 4.1 6LoWPAN (IPv6 over Low-Power Wireless Personal Area Networks) === Standard IPv6 packets require a Minimum Transmission Unit (MTU) of 1280 bytes, whereas the IEEE 802.15.4 physical payload is capped at 127 bytes. '''6LoWPAN''' (RFC 4944 / RFC 6282) provides an intermediate adaptation layer that enables IPv6 over constrained radios:<ref name="rfc6282">Hui, J., & Thubert, P. (2011). "Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks." IETF RFC 6282.</ref> * '''Header Compression''': Compresses 40-byte IPv6 headers down to 2 bytes by eliding redundant prefix and MAC address data. * '''Fragmentation and Reassembly''': Splits oversized IPv6 datagrams across multiple 802.15.4 frames. * '''Stateless Autoconfiguration''': Maps 64-bit IEEE EUI-64 addresses directly to IPv6 link-local addresses. === 4.2 Application Layer Messaging Comparison === {| class="wikitable" style="width: 100%; text-align: center;" ! Protocol !! Transport !! Architecture !! Overhead !! Reliability (QoS) !! Best Suited For |- | '''MQTT''' || TCP (Port 1883/8883) || Publish / Subscribe (Broker-centric) || Low (2-byte header) || QoS 0, 1, 2 || Telemetry streaming, remote actuator control. |- | '''CoAP''' || UDP (Port 5683/5684) || Request / Response + PubSub (RESTful) || Ultra-Low (4-byte header) || Confirmable (CON) / Non-confirmable (NON) || Resource-constrained microcontrollers, sleep cycles. |- | '''HTTP/REST''' || TCP (Port 80/443) || Client / Server || High (ASCII text headers) || Relies on TCP ACK || Enterprise integrations, cloud webhooks. |- | '''AMQP''' || TCP (Port 5672) || Message Queue Broker || Moderate to High || Configurable delivery guarantees || Financial systems, enterprise B2B messaging. |} == 5. Cross-Domain IoT Applications == === 5.1 Smart Agriculture and Precision Farming === [[File:Applications of integrated IoT and smart sensors for precision farming.jpg|thumb|right|340px|Integrated precision agriculture setup with multispectral drone imaging, soil moisture probes, and automated drip irrigation valves.]] * '''Soil Moisture & Salinity Sensing''': Time-Domain Reflectometry (TDR) and Frequency-Domain Reflectometry (FDR) capacitive probes measure dielectric permittivity to infer soil volumetric water content (VWC). * '''Automated Closed-Loop Irrigation''': Sensor nodes transmit moisture data over LoRaWAN to an irrigation controller that drives solenoid valves based on evapotranspiration (ET) models, achieving water savings of up to 45%.<ref name="ojha2015">Ojha, T., Misra, S., & Raghuwanshi, N. S. (2015). "Wireless sensor networks for agriculture: The state-of-the-art in practice and future challenges." ''Computers and Electronics in Agriculture'', 118, 66–84.</ref> * '''Microclimate Telemetry''': Atmospheric pressure, relative humidity, and canopy temperature monitoring predict fungal disease outbreaks. === 5.2 Internet of Medical Things (IoMT) & Wearable Health === [[File:Body Area Network.jpg|thumb|left|320px|Wireless Body Area Network (WBAN / IEEE 802.15.6) connecting medical physiological sensors to an edge smartphone gateway.]] * '''Wireless Body Area Networks (WBAN - IEEE 802.15.6)''': Standardized for ultra-low-power biomedical sensor nodes placed on or implanted inside the human body.<ref name="movassaghi2014">Movassaghi, S., Abolhasan, M., Lipman, J., Smith, D., & Jamalipour, A. (2014). "Wireless body area networks: A survey." ''IEEE Communications Surveys & Tutorials'', 16(3), 1658–1686.</ref> * '''Physiological Signal Interfacing''': ** ''Electrocardiography (ECG)'': Differential biopotential amplifiers capture millivolt-level cardiac polarization waveforms. ** ''Photoplethysmography (PPG)'': Red (660 nm) and Infrared (940 nm) LEDs evaluate differential optical absorption in arterial blood to determine Oxygen Saturation ($SpO_2$): :<math>R = \frac{(AC / DC)_{660\text{ nm}}}{(AC / DC)_{940\text{ nm}}}</math> * '''Real-Time Arrhythmia Detection''': Edge DSP microcontrollers compute Heart Rate Variability (HRV) and trigger automated emergency SMS alerts in cases of ventricular tachycardia or sudden falls. === 5.3 Smart Grid and Energy Automation === * '''Advanced Metering Infrastructure (AMI)''': Bidirectional solid-state smart meters report real-time consumption every 15 minutes, enabling dynamic Time-of-Use (ToU) tariffs and demand-response shedding. * '''Phasor Measurement Units (PMU)''': Wide-Area Monitoring Systems (WAMS) sample voltage and current phasors synchronized to GPS clocks at 50/60 samples/sec to maintain grid frequency stability. --- == 6. Practical Implementation & Code Examples == === 6.1 Embedded C (ESP32 / Arduino): Interfacing I2C Sensor and Publishing JSON over Secure MQTT === This practical firmware initializes an I2C environmental sensor, constructs a standard JSON telemetry payload, and publishes it to a cloud broker over MQTT with TLS encryption: <syntaxhighlight lang="c"> #include <WiFi.h> #include <PubSubClient.h> #include <Wire.h> #include <ArduinoJson.h> // Network Credentials const char* WIFI_SSID = "University_IoT_Lab"; const char* WIFI_PASSWORD = "LabSecurePassword2026"; const char* MQTT_BROKER = "broker.hivemq.com"; const int MQTT_PORT = 1883; const char* MQTT_TOPIC = "dept/ece/iot/telemetry"; WiFiClient espClient; PubSubClient client(espClient); // I2C Sensor Simulation: Reads ambient temperature and humidity float read_ambient_temperature() { // In production: Read registers from I2C device (e.g. BME280 at address 0x76) return 24.5 + (random(-50, 50) / 100.0); } float read_relative_humidity() { return 55.0 + (random(-100, 100) / 100.0); } void connect_wifi() { Serial.print("Connecting to Wi-Fi"); WiFi.begin(WIFI_SSID, WIFI_PASSWORD); while (WiFi.status() != WL_CONNECTED) { delay(500); Serial.print("."); } Serial.println("\n[WiFi] Connected! IP: " + WiFi.localIP().toString()); } void reconnect_mqtt() { while (!client.connected()) { Serial.print("[MQTT] Connecting to broker..."); String clientId = "ESP32_ECE_Node_" + String(random(0xffff), HEX); if (client.connect(clientId.c_str())) { Serial.println(" Connected successfully."); } else { Serial.print(" Failed, rc="); Serial.print(client.state()); Serial.println(" Retrying in 3 seconds..."); delay(3000); } } } void setup() { Serial.begin(115200); Wire.begin(21, 22); // SDA=GPIO21, SCL=GPIO22 connect_wifi(); client.setServer(MQTT_BROKER, MQTT_PORT); } void loop() { if (!client.connected()) { reconnect_mqtt(); } client.loop(); // 1. Read environmental data from sensor float temp_val = read_ambient_temperature(); float hum_val = read_relative_humidity(); // 2. Build structured JSON payload StaticJsonDocument<200> doc; doc["node_id"] = "ECE_LAB_ESP32_01"; doc["temp_c"] = temp_val; doc["humidity_pct"]= hum_val; doc["rssi_dbm"] = WiFi.RSSI(); char payloadBuffer[256]; serializeJson(doc, payloadBuffer); // 3. Publish to MQTT broker with QoS 1 if (client.publish(MQTT_TOPIC, payloadBuffer)) { Serial.print("[MQTT Telemetry Published]: "); Serial.println(payloadBuffer); } else { Serial.println("[MQTT Error] Telemetry publication failed."); } delay(5000); // Sample interval: 5 seconds } </syntaxhighlight> === 6.2 Python: Edge Gateway Subscriber with Anomaly Filtering === The following script represents an Edge Gateway or Fog Node running on an industrial SBC. It subscribes to incoming node telemetry, applies an Exponential Moving Average (EMA) filter, and detects abnormal parameter deviations: <syntaxhighlight lang="python"> #!/usr/bin/env python3 """ IoT Edge Gateway Telemetry Ingest & Anomaly Detection Subscribes to sensor MQTT topic, computes moving statistics, and flags anomalies. """ import json import paho.mqtt.client as mqtt BROKER_ADDRESS = "broker.hivemq.com" PORT = 1883 TOPIC = "dept/ece/iot/telemetry" ALPHA = 0.2 # EMA smoothing factor ema_temperature = None TEMP_ALERT_THRESHOLD = 35.0 # Celsius def on_connect(client, userdata, flags, rc): if rc == 0: print(f"[Gateway] Connected to MQTT Broker. Subscribing to '{TOPIC}'...") client.subscribe(TOPIC) else: print(f"[Gateway] Connection failed with result code: {rc}") def on_message(client, userdata, msg): global ema_temperature try: payload = json.loads(msg.payload.decode('utf-8')) raw_temp = payload.get("temp_c") node_id = payload.get("node_id") if raw_temp is not None: # Initialize or update Exponential Moving Average (EMA) if ema_temperature is None: ema_temperature = raw_temp else: ema_temperature = (ALPHA * raw_temp) + ((1 - ALPHA) * ema_temperature) print(f"[{node_id}] Raw: {raw_temp:.2f}°C | Smoothed EMA: {ema_temperature:.2f}°C") # Edge Rule: Immediate Alert Trigger if raw_temp > TEMP_ALERT_THRESHOLD: print(f" >>> [CRITICAL ALARM] Over-temperature event detected on {node_id}!") # Insert edge actuation trigger here (e.g., trip relay / sound buzzer) except Exception as e: print(f"[Error] Failed to parse message: {e}") def main(): client = mqtt.Client() client.on_connect = on_connect client.on_message = on_message client.connect(BROKER_ADDRESS, PORT, keepalive=60) print("[Gateway] Edge Processing Service Running. Press Ctrl+C to stop.") try: client.loop_forever() except KeyboardInterrupt: print("\n[Gateway] Shutting down cleanly.") client.disconnect() if __name__ == "__main__": main() </syntaxhighlight> --- == 7. Security, Privacy, and Scalability Constraints == IoT security requires a defense-in-depth model that addresses physical, network, and firmware attack surfaces: * '''Resource Constraints''': Standard enterprise cryptosystems (e.g., RSA-2048) are infeasible on low-power 8-bit or 16-bit microcontrollers due to RAM exhaustion and battery drain. * '''Lightweight Cryptography (LWC)''': Adoption of NIST-standardized authenticated ciphers such as '''ASCON''' and stream ciphers like '''ChaCha20-Poly1305''' provides AEAD (Authenticated Encryption with Associated Data) with minimal hardware footprint.<ref name="nist_ascon">NIST (2023). "Lightweight Cryptography Standardization Process: ASCON Announcement".</ref> * '''Secure Boot & Zero Trust''': Verification of cryptographically signed firmware images using on-chip Hardware Secure Elements (e.g., ATECC608A) prevents malicious rogue firmware injection. --- == 8. Summary == * The Internet of Things is a multi-tier cyber-physical framework encompassing perception, network/transport, middleware/fog, and enterprise application layers. * Transducer interfacing mandates careful consideration of bus bandwidth (I2C vs. SPI vs. UART), ADC bit resolution, and noise filtering. * At the network layer, 6LoWPAN compresses IPv6 headers to make IP routing feasible over IEEE 802.15.4 constrained mesh links. * MQTT and CoAP represent the predominant application-layer telemetry protocols, trading off TCP connection statefulness against UDP packet agility. * Real-world implementations across agriculture, medical body area networks (IoMT), and smart power grids depend on edge preprocessing to minimize cloud bandwidth overhead and ensure low-latency actuation. == 9. Review and Numerical Questions == # Explain the role of the 6LoWPAN adaptation layer. How does it compress the 40-byte IPv6 header into 2 bytes? # A 12-bit successive approximation register (SAR) ADC operates with an internal reference voltage <math>V_{\text{ref}} = 3.3\text{ V}</math>. #* Calculate the resolution (voltage weight of 1 LSB) in millivolts. #* If a linear temperature transducer yields an output voltage of <math>1.85\text{ V}</math>, compute the digitized integer output code. # Differentiate between MQTT and CoAP across the following parameters: underlying transport layer, messaging paradigm, packet header overhead, and caching support. # In a Wireless Body Area Network (WBAN), a wearable photoplethysmography (PPG) optical sensor samples arterial pulse signals. #* If the heart rate can reach up to 210 beats per minute (BPM), calculate the fundamental frequency <math>f_0</math> in Hz. #* Determine the minimum Nyquist sampling frequency required to capture up to the 10th harmonic of the cardiac waveform. # Discuss the security trade-offs between symmetric-key lightweight cryptography (e.g., ASCON) and public-key cryptography (e.g., ECC / RSA) in battery-powered field nodes. == 10. References == {{reflist}} === Recommended Textbooks & Standards === * Bahga, A., & Madisetti, V. (2014). ''Internet of Things: A Hands-On Approach''. VPT Publishers. ISBN 978-0996025515. * Hersent, O., Boswarthick, D., & Elloumi, O. (2012). ''The Internet of Things: Key Applications and Protocols''. Wiley. * IEEE P2413: "Standard for an Architectural Framework for the Internet of Things (IoT)". * IETF RFC 7252: "The Constrained Application Protocol (CoAP)". * OASIS Standard: "MQTT Version 5.0 Specification". m5h4g1lstsgg7tvnciasud8l1va0b4y 4679902 4679771 2026-11-04T07:01:35Z Jcb 90773 4679902 wikitext text/x-wiki __TOC__ == Learning Objectives == After studying this chapter, students of Electronics & Communication Engineering (ECE) should be able to: * Contrast the 3-layer, 5-layer, and IEEE P2413 / ITU-T standard IoT reference architectural models. * Understand the hardware interfacing of analog and digital transducers via I2C, SPI, UART, and precision ADCs. * Analyze the low-power wireless networking stack, including IEEE 802.15.4, 6LoWPAN adaptation, and the RPL routing algorithm. * Differentiate between application-layer protocols (MQTT, CoAP, HTTP/REST, AMQP) based on transport overhead, latency, and reliability. * Evaluate Edge, Fog, and Cloud computing paradigms for bandwidth optimization and real-time inference. * Design end-to-end IoT solutions across core applications: Precision Agriculture, Internet of Medical Things (IoMT), Smart Grid, and Industrial Telemetry. --- == 1. Introduction and Architectural Evolution == [[File:Internet of Things.svg|thumb|right|340px|Evolution and structural convergence across physical sensing, connectivity, and analytical layers in the IoT ecosystem.]] The '''Internet of Things (IoT)''' is an expansive paradigm wherein physical objects ("things") embedded with transducers, microcontrollers, and transceivers seamlessly communicate over IP-based networks to exchange telemetry and receive operational commands without human intervention.<ref name="gubbi2013">Gubbi, J., Buyya, R., Marusic, S., & Palaniswami, M. (2013). "Internet of Things (IoT): A vision, architectural elements, and future directions." ''Future Generation Computer Systems'', 29(7), 1645–1660. doi:10.1016/j.future.2013.01.010.</ref> Unlike traditional localized embedded systems, IoT devices are globally addressable and integrate into larger data-processing pipelines, transforming raw environmental phenomena into actionable business and engineering intelligence. == 2. IoT Reference Architectures == To manage the heterogeneity of hardware platforms and communication standards, IoT is organized into formal layered architectural models.<ref name="al-fuqaha2015">Al-Fuqaha, A., Guizani, M., Mohammadi, M., Aledhari, M., & Ayyash, M. (2015). "Internet of Things: A survey on enabling technologies, protocols, and applications." ''IEEE Communications Surveys & Tutorials'', 17(4), 2347–2376.</ref> === 2.1 The 3-Layer and 5-Layer Architectures === [[File:Iot apps.png|thumb|left|320px|Hierarchical classification of IoT systems connecting smart physical objects to diverse domain applications.]] * '''3-Layer Classical Model''': #* '''Perception Layer''': Transducers, RFID tags, sensors, and actuators that sense physical variables and convert them into electrical signals. #* '''Network Layer''': Transmission media (Wi-Fi, Cellular, LPWAN, Ethernet) that route packets to data-processing servers. #* '''Application Layer''': End-user interfaces, dashboards, and domain-specific services. * '''5-Layer Extended Model''' (Standardized for Enterprise IoT): {| class="wikitable" style="width: 100%;" ! Layer !! Key Hardware / Technologies !! Core Engineering Function |- | '''Business Layer''' | System dashboards, ERP, decision support models, billing. | High-level governance, business logic, economic monetization, KPI tracking. |- | '''Application Layer''' | Mobile apps, cloud APIs, SCADA consoles, smart health/home portals. | Domain-specific user interactions and service presentation. |- | '''Processing (Middleware) Layer''' | Cloud servers, distributed time-series databases, stream analytics. | Data ingestion, semantic mediation, machine learning inference, persistent storage. |- | '''Transport (Network) Layer''' | IPv6/6LoWPAN, 4G/5G NR, LoRaWAN, Wi-Fi (802.11ax), BLE Mesh. | Packetization, routing, addressing, Quality of Service (QoS) management. |- | '''Perception Layer''' | MEMS sensors, thermocouples, load cells, ADCs, microcontrollers. | Physical parameter acquisition, analog-to-digital conversion, edge pre-filtering. |} == 3. Perception Layer: Sensor Interfacing & Signal Conditioning == The perception layer converts physical environmental phenomena into digitized binary representations suitable for embedded microcontrollers. === 3.1 Digital Serial Bus Interfaces === {| class="wikitable" style="width: 100%; text-align: center;" ! Protocol !! Bus Lines !! Mode !! Maximum Clock Rate !! Addressing !! Typical Range |- | '''I2C''' (Inter-Integrated Circuit) || 2 (SDA, SCL) || Half-Duplex || 100 kbps (Standard), 400 kbps (Fast), 3.4 Mbps (High-Speed) || 7-bit or 10-bit addressing || On-board (< 30 cm) |- | '''SPI''' (Serial Peripheral Interface) || 4 (MOSI, MISO, SCK, CS) || Full-Duplex || 10 – 50+ Mbps || Dedicated Chip Select line per slave || On-board (< 20 cm) |- | '''UART''' (Universal Asynchronous Receiver-Transmitter) || 2 (TX, RX) || Full-Duplex || Standard baud rates up to 921.6 kbps || Point-to-Point (No address) || Up to 15 m (RS-232) |- | '''1-Wire''' (Dallas) || 1 (Data + Parasitic Power) || Half-Duplex || 16.3 kbps || Unique 64-bit ROM code || Up to 100 m |} === 3.2 Analog Conditioning and ADC Quantization === Real-world analog transducers (e.g., strain gauges, thermocouples, photodetectors) require signal conditioning prior to ADC sampling: * '''Instrumentation Amplifiers (INA)''': High Common-Mode Rejection Ratio (CMRR > 100 dB) to eliminate ground loop noise. * '''Anti-Aliasing Filter (AAF)''': Analog low-pass filter satisfying the Nyquist criteria (<math>f_{\text{cutoff}} \le \frac{f_s}{2}</math>). * '''Quantization Resolution''': :<math>V_{\text{LSB}} = \frac{V_{\text{ref}}}{2^N}</math> where <math>N</math> is the ADC bit resolution (e.g., for <math>N = 12\text{ bits}</math> and <math>V_{\text{ref}} = 3.3\text{ V}</math>, <math>V_{\text{LSB}} = 0.805\text{ mV}</math>). == 4. Connectivity and Protocol Stack == [[File:Data Networks classification by spatial scope.svg|thumb|right|340px|Classification of network topologies by spatial reach: from Body Area Networks (BAN) and PAN to WAN and LPWAN.]] IoT demands lightweight protocols capable of operating over constrained links characterized by high packet error rates and duty-cycle limitations. === 4.1 6LoWPAN (IPv6 over Low-Power Wireless Personal Area Networks) === Standard IPv6 packets require a Minimum Transmission Unit (MTU) of 1280 bytes, whereas the IEEE 802.15.4 physical payload is capped at 127 bytes. '''6LoWPAN''' (RFC 4944 / RFC 6282) provides an intermediate adaptation layer that enables IPv6 over constrained radios:<ref name="rfc6282">Hui, J., & Thubert, P. (2011). "Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks." IETF RFC 6282.</ref> * '''Header Compression''': Compresses 40-byte IPv6 headers down to 2 bytes by eliding redundant prefix and MAC address data. * '''Fragmentation and Reassembly''': Splits oversized IPv6 datagrams across multiple 802.15.4 frames. * '''Stateless Autoconfiguration''': Maps 64-bit IEEE EUI-64 addresses directly to IPv6 link-local addresses. === 4.2 Application Layer Messaging Comparison === {| class="wikitable" style="width: 100%; text-align: center;" ! Protocol !! Transport !! Architecture !! Overhead !! Reliability (QoS) !! Best Suited For |- | '''MQTT''' || TCP (Port 1883/8883) || Publish / Subscribe (Broker-centric) || Low (2-byte header) || QoS 0, 1, 2 || Telemetry streaming, remote actuator control. |- | '''CoAP''' || UDP (Port 5683/5684) || Request / Response + PubSub (RESTful) || Ultra-Low (4-byte header) || Confirmable (CON) / Non-confirmable (NON) || Resource-constrained microcontrollers, sleep cycles. |- | '''HTTP/REST''' || TCP (Port 80/443) || Client / Server || High (ASCII text headers) || Relies on TCP ACK || Enterprise integrations, cloud webhooks. |- | '''AMQP''' || TCP (Port 5672) || Message Queue Broker || Moderate to High || Configurable delivery guarantees || Financial systems, enterprise B2B messaging. |} == 5. Cross-Domain IoT Applications == === 5.1 Smart Agriculture and Precision Farming === [[File:Applications of integrated IoT and smart sensors for precision farming.jpg|thumb|right|340px|Integrated precision agriculture setup with multispectral drone imaging, soil moisture probes, and automated drip irrigation valves.]] * '''Soil Moisture & Salinity Sensing''': Time-Domain Reflectometry (TDR) and Frequency-Domain Reflectometry (FDR) capacitive probes measure dielectric permittivity to infer soil volumetric water content (VWC). * '''Automated Closed-Loop Irrigation''': Sensor nodes transmit moisture data over LoRaWAN to an irrigation controller that drives solenoid valves based on evapotranspiration (ET) models, achieving water savings of up to 45%.<ref name="ojha2015">Ojha, T., Misra, S., & Raghuwanshi, N. S. (2015). "Wireless sensor networks for agriculture: The state-of-the-art in practice and future challenges." ''Computers and Electronics in Agriculture'', 118, 66–84.</ref> * '''Microclimate Telemetry''': Atmospheric pressure, relative humidity, and canopy temperature monitoring predict fungal disease outbreaks. === 5.2 Internet of Medical Things (IoMT) & Wearable Health === [[File:Body Area Network.jpg|thumb|left|320px|Wireless Body Area Network (WBAN / IEEE 802.15.6) connecting medical physiological sensors to an edge smartphone gateway.]] * '''Wireless Body Area Networks (WBAN - IEEE 802.15.6)''': Standardized for ultra-low-power biomedical sensor nodes placed on or implanted inside the human body.<ref name="movassaghi2014">Movassaghi, S., Abolhasan, M., Lipman, J., Smith, D., & Jamalipour, A. (2014). "Wireless body area networks: A survey." ''IEEE Communications Surveys & Tutorials'', 16(3), 1658–1686.</ref> * '''Physiological Signal Interfacing''': ** ''Electrocardiography (ECG)'': Differential biopotential amplifiers capture millivolt-level cardiac polarization waveforms. ** ''Photoplethysmography (PPG)'': Red (660 nm) and Infrared (940 nm) LEDs evaluate differential optical absorption in arterial blood to determine Oxygen Saturation ($SpO_2$): :<math>R = \frac{(AC / DC)_{660\text{ nm}}}{(AC / DC)_{940\text{ nm}}}</math> * '''Real-Time Arrhythmia Detection''': Edge DSP microcontrollers compute Heart Rate Variability (HRV) and trigger automated emergency SMS alerts in cases of ventricular tachycardia or sudden falls. === 5.3 Smart Grid and Energy Automation === * '''Advanced Metering Infrastructure (AMI)''': Bidirectional solid-state smart meters report real-time consumption every 15 minutes, enabling dynamic Time-of-Use (ToU) tariffs and demand-response shedding. * '''Phasor Measurement Units (PMU)''': Wide-Area Monitoring Systems (WAMS) sample voltage and current phasors synchronized to GPS clocks at 50/60 samples/sec to maintain grid frequency stability. --- == 6. Practical Implementation & Code Examples == === 6.1 Embedded C (ESP32 / Arduino): Interfacing I2C Sensor and Publishing JSON over Secure MQTT === This practical firmware initializes an I2C environmental sensor, constructs a standard JSON telemetry payload, and publishes it to a cloud broker over MQTT with TLS encryption: <syntaxhighlight lang="c"> #include <WiFi.h> #include <PubSubClient.h> #include <Wire.h> #include <ArduinoJson.h> // Network Credentials const char* WIFI_SSID = "University_IoT_Lab"; const char* WIFI_PASSWORD = "LabSecurePassword2026"; const char* MQTT_BROKER = "broker.hivemq.com"; const int MQTT_PORT = 1883; const char* MQTT_TOPIC = "dept/ece/iot/telemetry"; WiFiClient espClient; PubSubClient client(espClient); // I2C Sensor Simulation: Reads ambient temperature and humidity float read_ambient_temperature() { // In production: Read registers from I2C device (e.g. BME280 at address 0x76) return 24.5 + (random(-50, 50) / 100.0); } float read_relative_humidity() { return 55.0 + (random(-100, 100) / 100.0); } void connect_wifi() { Serial.print("Connecting to Wi-Fi"); WiFi.begin(WIFI_SSID, WIFI_PASSWORD); while (WiFi.status() != WL_CONNECTED) { delay(500); Serial.print("."); } Serial.println("\n[WiFi] Connected! IP: " + WiFi.localIP().toString()); } void reconnect_mqtt() { while (!client.connected()) { Serial.print("[MQTT] Connecting to broker..."); String clientId = "ESP32_ECE_Node_" + String(random(0xffff), HEX); if (client.connect(clientId.c_str())) { Serial.println(" Connected successfully."); } else { Serial.print(" Failed, rc="); Serial.print(client.state()); Serial.println(" Retrying in 3 seconds..."); delay(3000); } } } void setup() { Serial.begin(115200); Wire.begin(21, 22); // SDA=GPIO21, SCL=GPIO22 connect_wifi(); client.setServer(MQTT_BROKER, MQTT_PORT); } void loop() { if (!client.connected()) { reconnect_mqtt(); } client.loop(); // 1. Read environmental data from sensor float temp_val = read_ambient_temperature(); float hum_val = read_relative_humidity(); // 2. Build structured JSON payload StaticJsonDocument<200> doc; doc["node_id"] = "ECE_LAB_ESP32_01"; doc["temp_c"] = temp_val; doc["humidity_pct"]= hum_val; doc["rssi_dbm"] = WiFi.RSSI(); char payloadBuffer[256]; serializeJson(doc, payloadBuffer); // 3. Publish to MQTT broker with QoS 1 if (client.publish(MQTT_TOPIC, payloadBuffer)) { Serial.print("[MQTT Telemetry Published]: "); Serial.println(payloadBuffer); } else { Serial.println("[MQTT Error] Telemetry publication failed."); } delay(5000); // Sample interval: 5 seconds } </syntaxhighlight> === 6.2 Python: Edge Gateway Subscriber with Anomaly Filtering === The following script represents an Edge Gateway or Fog Node running on an industrial SBC. It subscribes to incoming node telemetry, applies an Exponential Moving Average (EMA) filter, and detects abnormal parameter deviations: <syntaxhighlight lang="python"> #!/usr/bin/env python3 """ IoT Edge Gateway Telemetry Ingest & Anomaly Detection Subscribes to sensor MQTT topic, computes moving statistics, and flags anomalies. """ import json import paho.mqtt.client as mqtt BROKER_ADDRESS = "broker.hivemq.com" PORT = 1883 TOPIC = "dept/ece/iot/telemetry" ALPHA = 0.2 # EMA smoothing factor ema_temperature = None TEMP_ALERT_THRESHOLD = 35.0 # Celsius def on_connect(client, userdata, flags, rc): if rc == 0: print(f"[Gateway] Connected to MQTT Broker. Subscribing to '{TOPIC}'...") client.subscribe(TOPIC) else: print(f"[Gateway] Connection failed with result code: {rc}") def on_message(client, userdata, msg): global ema_temperature try: payload = json.loads(msg.payload.decode('utf-8')) raw_temp = payload.get("temp_c") node_id = payload.get("node_id") if raw_temp is not None: # Initialize or update Exponential Moving Average (EMA) if ema_temperature is None: ema_temperature = raw_temp else: ema_temperature = (ALPHA * raw_temp) + ((1 - ALPHA) * ema_temperature) print(f"[{node_id}] Raw: {raw_temp:.2f}°C | Smoothed EMA: {ema_temperature:.2f}°C") # Edge Rule: Immediate Alert Trigger if raw_temp > TEMP_ALERT_THRESHOLD: print(f" >>> [CRITICAL ALARM] Over-temperature event detected on {node_id}!") # Insert edge actuation trigger here (e.g., trip relay / sound buzzer) except Exception as e: print(f"[Error] Failed to parse message: {e}") def main(): client = mqtt.Client() client.on_connect = on_connect client.on_message = on_message client.connect(BROKER_ADDRESS, PORT, keepalive=60) print("[Gateway] Edge Processing Service Running. Press Ctrl+C to stop.") try: client.loop_forever() except KeyboardInterrupt: print("\n[Gateway] Shutting down cleanly.") client.disconnect() if __name__ == "__main__": main() </syntaxhighlight> --- == 7. Security, Privacy, and Scalability Constraints == IoT security requires a defense-in-depth model that addresses physical, network, and firmware attack surfaces: * '''Resource Constraints''': Standard enterprise cryptosystems (e.g., RSA-2048) are infeasible on low-power 8-bit or 16-bit microcontrollers due to RAM exhaustion and battery drain. * '''Lightweight Cryptography (LWC)''': Adoption of NIST-standardized authenticated ciphers such as '''ASCON''' and stream ciphers like '''ChaCha20-Poly1305''' provides AEAD (Authenticated Encryption with Associated Data) with minimal hardware footprint.<ref name="nist_ascon">NIST (2023). "Lightweight Cryptography Standardization Process: ASCON Announcement".</ref> * '''Secure Boot & Zero Trust''': Verification of cryptographically signed firmware images using on-chip Hardware Secure Elements (e.g., ATECC608A) prevents malicious rogue firmware injection. --- == 8. Summary == * The Internet of Things is a multi-tier cyber-physical framework encompassing perception, network/transport, middleware/fog, and enterprise application layers. * Transducer interfacing mandates careful consideration of bus bandwidth (I2C vs. SPI vs. UART), ADC bit resolution, and noise filtering. * At the network layer, 6LoWPAN compresses IPv6 headers to make IP routing feasible over IEEE 802.15.4 constrained mesh links. * MQTT and CoAP represent the predominant application-layer telemetry protocols, trading off TCP connection statefulness against UDP packet agility. * Real-world implementations across agriculture, medical body area networks (IoMT), and smart power grids depend on edge preprocessing to minimize cloud bandwidth overhead and ensure low-latency actuation. == 9. Review and Numerical Questions == # Explain the role of the 6LoWPAN adaptation layer. How does it compress the 40-byte IPv6 header into 2 bytes? # A 12-bit successive approximation register (SAR) ADC operates with an internal reference voltage <math>V_{\text{ref}} = 3.3\text{ V}</math>. #* Calculate the resolution (voltage weight of 1 LSB) in millivolts. #* If a linear temperature transducer yields an output voltage of <math>1.85\text{ V}</math>, compute the digitized integer output code. # Differentiate between MQTT and CoAP across the following parameters: underlying transport layer, messaging paradigm, packet header overhead, and caching support. # In a Wireless Body Area Network (WBAN), a wearable photoplethysmography (PPG) optical sensor samples arterial pulse signals. #* If the heart rate can reach up to 210 beats per minute (BPM), calculate the fundamental frequency <math>f_0</math> in Hz. #* Determine the minimum Nyquist sampling frequency required to capture up to the 10th harmonic of the cardiac waveform. # Discuss the security trade-offs between symmetric-key lightweight cryptography (e.g., ASCON) and public-key cryptography (e.g., ECC / RSA) in battery-powered field nodes. == 10. References == {{reflist}} === Recommended Textbooks & Standards === * Bahga, A., & Madisetti, V. (2014). ''Internet of Things: A Hands-On Approach''. VPT Publishers. {{ISBN|978-0996025515}}. * Hersent, O., Boswarthick, D., & Elloumi, O. (2012). ''The Internet of Things: Key Applications and Protocols''. Wiley. * IEEE P2413: "Standard for an Architectural Framework for the Internet of Things (IoT)". * IETF RFC 7252: "The Constrained Application Protocol (CoAP)". * OASIS Standard: "MQTT Version 5.0 Specification". kd5wihsx4fp1krpglexsk3aqjtr9duv Chess Opening Theory/1. d4/1...d5/2. c4/2...c6/3. cxd5/3...cxd5/4. Nc3/4...Nf6/5. f3 0 486790 4679773 2026-11-03T12:30:10Z Greenman 7490 start 4679773 wikitext text/x-wiki {{Chess Opening Theory/Position |name=Slav Defence: Boor Attack |eco=[[Chess/ECOD|D10]] |parent=[[../|Exchange variation]] }} == 5. f3 == f3 is a rare sideline that can lead the unprepared Black player into trouble. White, at the cost of weakening f2, aims to build a strong centre with an e4 push. Black has a number of responses. 6...Nc6 and 6...e6 are most common at amateur level, but the best response is the rarely-played 6...Qb6, targeting the weakness on f2. ==Theory table== {{ChessTable}} {{Chess/theory table |line1=5...Nc6 |eval1= |line2=5...e6 |eval2= |line3=5...Qb6 |eval3= }} {{ChessMid}} ==References== {{reflist}} {{BCO2}} {{Chess Opening Theory/Footer}} agayumvaxk77l7e621t8qjqqiu1ayih User:Adarsh1204/sandbox 2 486791 4679775 2026-11-03T12:36:08Z Adarsh1204 3629896 Created page with "== My Sandbox Pages == * [[User:Adarsh1204/Gate-All-Around_Transistor_Technology]]" 4679775 wikitext text/x-wiki == My Sandbox Pages == * [[User:Adarsh1204/Gate-All-Around_Transistor_Technology]] feiq881idgd3q3eje18njac07lkvj60 Chess Opening Theory/1. e4/1...e5/2. Nf3/2...Nc6/3. Bc4/3...Nf6/4. Ng5/4...d5/5. exd5/5...Nxd5/6. Nxf7/6...Kxf7/7. Qf3/7...Ke6/8. Nc3/8...Nb4/9.0-0!! 0 486792 4679795 2026-11-03T14:29:51Z ~2026-47231-00 3624794 9. 0-0!! 4679795 wikitext text/x-wiki '''9. 0-0!!''' White sacrifices c-pawn and the rook. After '''9... c6''' ('''9... Nxc2?? 10. Bxd5+-''') white plays '''10. d4!''' and white has a excellent attack!. If Black moves '''10... Nxc2?? 11. exd4!! Nxa1 12. Rd1!+-''' White have a great winning position. The best move for black is '''10... Qf6!? 11.Qd1+=''' and black has a slightly worse position. oyrhk228q7c5uf2v9anr8vk1mgfmxeb User:Aditya31Raj/sandbox 2 486793 4679796 2026-11-03T14:37:14Z Aditya31Raj 3630248 Explained the working and demonstrate the mathematical expression for Single-Phase Half Wave Fully Controlled Rectifier. 4679796 wikitext text/x-wiki == '''<big>Analysis of a Single Phase Half-Wave Controlled Rectifier at Various Firing Angles</big>''' == === 1. <u>Introduction</u> === Power electronics plays an important role in controlling and converting electrical energy. An important circuit used within power electronics is a controlled rectifier which will convert an alternating current (AC) supply to a controlled direct current (DC) supply. A single phase half-wave controlled rectifier is a basic conversion circuit that uses an SCR as the main switching component. Unlike an uncontrolled rectifier where diodes will be used to obtain a fixed output, the controlled rectifier has a variable output voltage. This enables control of the output voltage by varying the firing angle. The firing angle is a parameter that defines when the gate pulse is applied to the SCR during the positive half of the AC supply. Varying the firing angle will change the amount of time the SCR conducts. In this experiment, a single phase half-wave controlled rectifier will be analysed at various firing angles. A digital oscilloscope will be used to view the various output waveforms. === 2. <u>Aim</u> === To understand how a single phase half-wave controlled rectifier works. To understand how an SCR acts as a controlled switching device. To view the effect various firing angles will have on the output waveform. To analyse how the firing angle affects the average DC output voltage. To understand how a controlled rectifier behaves practically by viewing the waveforms on an oscilloscope. === 3. <u>Circuit Setup</u> === A single phase half-wave controlled rectifier consists of: An AC supply. An SCR. A load. A gate triggering circuit. The AC supply will provide the sinusoidal input. The SCR will control the current flow through the load. The triggering circuit will determine when the SCR will turn ‘ON’. The main components are: AC Supply - Provide the single phase AC input. Silicon Controlled Rectifier (SCR) - Acts as a controlled switching device. Allows current to flow through it when forward biased with the correct gate pulse. Load - Where the rectified voltage will be applied. The characteristics of the load will affect the amount of current flowing through and the amount of time the SCR conducts. Gate Triggering Circuit - Provides trigger pulses at various firing angles. Digital Oscilloscope - To view various voltage waveforms. === 4. <u>Operation</u> === There are two main sections to the operation of a single phase half-wave controlled rectifier. ==== ''Positive Half'' ==== During the positive half of the AC supply, the SCR will become forward biased. However, it will not conduct straight away as the SCR needs a gate pulse to turn ‘ON’. Once the gate pulse is applied at the firing angle α, the SCR will begin to conduct. Current will then flow through the load. The SCR will continue to conduct until the current drops below its holding current. This is normally when the end of the positive half is reached for a purely resistive load. ===== ''Negative Half'' ===== During the negative half of the AC supply, the SCR will become reverse biased. It will stop conducting. No current will flow through the load so the output voltage will be approximately 0 volts for an ideal half-wave rectifier with a resistive load. This will repeat throughout the input waveform producing a controlled pulsating DC output. === 5. <u>Understanding the Firing Angle (α)</u> === The firing angle is an important parameter in controlled rectifiers. It defines how far into the positive half cycle of the AC supply the gate pulse will be applied to the SCR. It is measured in electrical degrees. If the firing angle is small, the SCR will turn ‘ON’ sooner. If the firing angle is large, the SCR will turn ‘ON’ later. Therefore, increasing the firing angle will decrease the amount of time the SCR conducts for a resistive load. This will cause the average output voltage to decrease. The relation between firing angle and conduction time for a resistive load is: Conduction Angle = 180° - α If the firing angle was 30°, the SCR would conduct for approximately 150°. === 6. <u>Effects of Various Firing Angles on Output Waveform</u> === The most important part of this experiment is observing how the output waveform changes depending on the firing angle. Small Firing Angle A small firing angle will mean the gate pulse will be applied to the SCR soon after the positive half of the supply starts. This means the SCR will conduct for a long time. A large amount of the positive half of the input waveform will be applied across the load. This will give a relatively high average DC voltage. Medium Firing Angle Increasing the firing angle will mean the gate pulse will be applied later during the positive half. This means the SCR will start to conduct after a greater delay. This will cause the SCR to conduct for less time. Less of the positive half of the input waveform will appear across the load. This will cause a lower average DC output voltage. Large Firing Angle The gate pulse will be applied to the SCR much later during the positive half of the supply. The SCR will conduct for a much shorter amount of time. This means a small amount of the input waveform will appear across the load. This will cause the average output voltage to decrease. Very Large Firing Angle When the firing angle gets close to 180°, the gate pulse will be applied to the SCR near the end of the positive half. There will be very little time for the SCR to conduct. This will produce a very small output voltage. From this you can see the output voltage from a controlled rectifier can be controlled by controlling when the SCR conducts. '''7. <u>Mathematical Analysis</u>''' For an ideal single phase half-wave controlled rectifier with a purely resistive load. The average output voltage can be calculated by: Vdc = (Vm / 2π)(1 + cos α) [[File:Minimum_firing_angle.jpg|thumb|The waveform of rectifier at minimum firing angle - 36.196.]] Where, Vdc = Average DC Output Voltage Vm = Maximum AC Input Voltage α = Firing Angle (Electrical Degrees) π = Constant [[File:3rd_firing_angle.jpg|thumb|The waveform at firing angle - 129.56.]] The RMS Output Voltage can be calculated using: Vrms = Vm x sqrt( (1 / 2π)(π - α + (sin 2α)/2 ) ) This shows that increasing the firing angle will decrease the average output voltage. [[File:2nd_firing_angle.jpg|thumb|The waveform at firing angle 86.27 .]] Theoretical Relation Firing Angle (α) Conduction Angle Average Output Voltage 0° 180° Maximum [[File:Maximum_firing_angle.jpg|thumb|The waveform at maximum firing angle - 177.43 .]] 30° 150° Decreases 60° 120° Further Decrease 90° 90° 50% of Max 120° 60° Low 150° 30° Very Low 180° 0° 0 This table represents how the circuit will theoretically behave for an ideal circuit with a resistive load. === 8. <u>Observing Waveform using Digital Oscilloscope</u> === A digital oscilloscope will be used to view the output waveform. Throughout the experiment, the firing angle will be changed and the output waveform will be viewed. The oscilloscope will give a visual representation of how the rectifier behaves. Various observations can be made such as: The start of the output waveform will change depending on the firing angle. The SCR will conduct for a longer time when the firing angle is small. The SCR will conduct for a shorter time when the firing angle is large. Average output voltage will change depending on the amount of time the SCR conducts. During the SCR not conducting, the output will be 0. The waveform can be seen to change depending on the firing angle. The images show how the waveform will change practically. The waveform may not be exactly the same as the theoretical waveform due to losses in the circuit, triggering, load and measuring. === 9. <u>Applications of Single Phase Controlled Rectifiers</u> === Single phase controlled rectifiers can be found in various power electronics applications such as: Speed control of a DC motor. Battery charger. Controlled DC power supplies. Industrial heating. Controlling DC voltages in a laboratory. Small scale industrial power conversion. They can be used anywhere where the average DC output voltage needs to be controlled. === 10. <u>Conclusion</u> === This experiment has shown how a single phase half-wave controlled rectifier works. It highlighted how important it is to control the firing angle in power electronics. By changing the firing angle of the SCR, control can be implemented to control the amount of time the SCR conducts. This will affect the average output voltage supplied to the load. If the firing angle was small, the SCR will conduct for a longer amount of time causing the average output voltage to increase. If the firing angle is increased, the SCR will conduct for a shorter amount of time reducing the average output voltage. The oscilloscope has shown how the rectifier will behave practically. This helps to get a clear understanding of how controlled rectifiers work. Overall this gives a good base knowledge to look at more complex power electronics converters, for example full wave controlled rectifiers, semi-converters and fully-controlled bridge converters. 544lpu0nvdoyvddcej462jx7jfemh41 User:Parmindersingh0830/sandbox 2 486794 4679802 2026-11-03T14:54:04Z Parmindersingh0830 3630254 Added title and introduction 4679802 wikitext text/x-wiki == How Servo Motors Control Motion in Robotic Systems == This page covers the working and applications of servo motors. It explains how sensors are used to sense the exact position, and where robots use servo motors, for example in robot arms. omy7b4gd4umue96tq9x7tv2hvylt9g0 User:Deepakdasari09/sandbox 2 486795 4679805 2026-11-03T15:03:34Z Deepakdasari09 3630298 NEW ARTICLE 4679805 wikitext text/x-wiki == '''Embedded Systems and Microcontrollers: Architecture, Hardware Subsystems and Edge Computing Paradigms''' == == Abstract == An embedded system is a specialized computing platform engineered to perform dedicated control functions within a larger mechanical or electrical system, frequently operating under deterministic real-time constraints, stringent power envelops, and constrained memory budgets. At the core of modern embedded systems lies the '''Microcontroller Unit (MCU)''', a monolithic integrated circuit incorporating a processor core, volatile and non-volatile memory, and reconfigurable hardware peripherals on a single silicon die. This paper presents an architectural, functional and empirical analysis of embedded systems and microcontrollers. This paper provides a concise architectural overview of embedded systems, covering core processor models (Non Neumann vs. Harvard; RISC vs. CISC), memory organization, contemporary trends such as edge AI(Tiny-ML). == 1.Introduction == Unlike general-purpose computers, embedded systems are engineered for specialized, deterministic tasks. * '''Microprocessor(MPU):''' Optimized for intensive computing. Relies on external RAM, storage, and peripheral controllers. * '''Microcontroller(MCU):''' An all-in-one system-on-chip (SoC) integrating CPU, SRAM, Flash memory and I/O ports, Optimized for low power, low latency and real time operations. == 2.Microcontroller Architecture == '''2.1 Von Neumann vs Harvard Architecture''' * '''Von Neumann Architecture:''' Uses a single shared bus and memory space for both<gallery mode="packed-hover"> File:Von Neumann architecture in Italian.svg|Von Neumann Architecture. </gallery>program instructions and data. it is simpler to design but introduces the von Neumann bottleneck, as code fetch and data read / write cannot simultaneously. * '''Harvard Architecture:''' Uses separate buses and physical memory spaces for instructions and data, allowing simultaneous instruction execution and data access.<gallery mode="packed-hover"> File:Harvard architecture-es.svg|Harvard architecture. </gallery> '''2.2 RISC Principles''' Most modern microcontrollers use Reduced Instruction set computer (RISC) architectures: * Fixed-length, uniform instruction sets. * Load/store design: Only specialized load/store instructions access data memory; arithmetic and logic occur strictly in registers. * Pipelining: Multiple instruction stages (Fetch, Decode, Execute) are handled concurrently. == 3.Memory Hierarchy & Hardware Peripherals == '''3.1 On-Chip Memory''' * '''SRAM(static RAM):''' Fast, volatile memory used for the call stack, global variables, and dynamic allocations. * '''Flash(NOR Flash):''' Non-volatile storage holding the compiled program binary and interrupt vector table. * '''EEPROM:''' Byte-erasable non-volatile memory for saving device settings, calibration data and keys. '''3.2 Core Periperals''' * '''GPIO:''' Digital pins configured as input (high-impedance/pull-up/pull-down) or output (push-pull/open-drain). * '''Interrupts(ISR):''' Hardware signals that pause the main program loop, save CPU registers and jump to an interrupt service Routine (ISR) via a vector table, ensuring low-latency responses. * '''Timers/Counters & PWM:''' Clock-driven digital used for event timing, input frequency capture and pulse width modulation (PWM) for motor control and power regulation. * '''ADC/DAC:''' Analog-to-digital converters (typically Successive Approximation Register / SAR) translate real-world analog sensor voltages into digital values. == 4. Serial Communication Protocols == Microcontrollers interface with external sensors, displays and actuators using serial protocols: * '''UART:''' Point-to-point, asynchronous communication requiring matching baud rates across two data lines (TX and RX). * '''SPI:''' High-speed, synchronous, full-duplex 4-wire bus (SCLK,MOSI,MISO,SS). Highly efficient for fast sensors and displays over short distances. * '''I2C(Inter-Integrated Circuit):''' Synchronous, half-duplex 2-wire bus (SDA, SCL) using bus.<gallery mode="packed-hover"> File:UART block diagram.svg|UART </gallery> == 5. Firmware Architectures == '''5.1 Bare-Metal (Super loop)''' A simple, non-preemptive design where the program executes sequentially inside an infinite loop, accompanied by interrupt service routines:<!-- int main(void) { system_Init(); while (1) { if (event_ready) { Process_Event(); event_ready = 0; } } } --> Ideal for simple, low-power applications, but difficult to scale as system complexity grows. '''5.2 Real-Time Operating Systems (RTOS)''' For complex applications, an RTOS (e.g., FreeRTOS, Zephyr) introduces: * '''Preemptive Priority Scheduling:''' The scheduler guarantees that the highest-priority ready task executes immediately. * '''Synchronization Primitives:''' Semaphores, mutexes (with priority inheritance to avoid priority inversion) and message queues. == 6. Comparative Analysis of Popular Microcontrollers == '''Overview of Common MCU Platforms''' {| class="wikitable" |+ !Platform !Architecture !clock speed !memory(flash/SRAM) !Key Use Case |- |'''ATmega328P''' |8-bit AVR RISC |16MHz |32 KB/2 KB |Education, simple automation (Arduino Uno) |- |'''STM32F401''' |32-bit ARM Cortex- M4F |84MHz |256KB / 96KB |Industrial control, DSP, robotics |- |'''ESP32''' |32-bit Xtensa Dual- core |Up to 240 MHz |4MB / 520KB |Connected IoT(integrated Wi-Fi & BLE) |- |'''RP2040''' |32-bit ARM Cortex- M0+ |133MHz |External Flash/ 264KB |Custom I/O protocol state machines (PIO) |} == 7. Emerging Trends == * '''Edge AI(Tiny-ML):''' Running quantized machine learning models (e.g., TensorFlow Lite for Microcontrollers) directly on MCUs under milliwatt power budgets for vibration analysis, gesture recognition and voice triggers. * '''Hardware Security:''' Integration of hardware cryptographic accelerators (AES, SHA),immutable secure Boot chains and isolated execution partitions (such as ARM Tust-Zone0. == 8. Conclusion == Microcontrollers from the bridge between digital logic and the physical world. While core constraints real-time determinism, energy efficiency and low bill-of-materials remain constant modern microcontrollers continue to expand into advanced domains through higher clock speeds, 32-bit architectures, integrated wireless radios and on-chip neural network inference. == 9. References == # Wolf,M.(2012). Computers as components: Principles of Embedded Computing System Design. Morgan Kaufmann. # Yiu, J.(2013). The Definitive Guide to ARM Cortex-M3 and Cortex-M4 processors.Newnes. # Ganssle, J.(2008). The art of designing Embedded Systems. Newnes. # Cooling, J.(2017). Real-time Operating systems: Book 1 - The Theory. 7fevdgvq0z7r49f6kgn0g2nxpowtc1x User:Chand2006/sandbox 2 486796 4679807 2026-11-03T15:19:55Z Chand2006 3630247 Created page with "== '''<big>inverter</big>''' == An '''inverter is a power electronic device that converts DC (Direct Current) into AC (Alternating Current).''' == Based on Output Waveform == * '''Square Wave Inverter:''' Produces square-shaped AC output. * '''Modified Sine Wave Inverter:''' Produces an approximate sine-wave output. * '''Pure Sine Wave Inverter:''' Produces smooth sinusoidal AC output. == Based on Input Source == # '''Voltage Source Inverter (VSI):''' Supplied by a..." 4679807 wikitext text/x-wiki == '''<big>inverter</big>''' == An '''inverter is a power electronic device that converts DC (Direct Current) into AC (Alternating Current).''' == Based on Output Waveform == * '''Square Wave Inverter:''' Produces square-shaped AC output. * '''Modified Sine Wave Inverter:''' Produces an approximate sine-wave output. * '''Pure Sine Wave Inverter:''' Produces smooth sinusoidal AC output. == Based on Input Source == # '''Voltage Source Inverter (VSI):''' Supplied by a constant DC voltage source. # '''Current Source Inverter (CSI):''' Supplied by a constant DC current source. == Based on Phase == # '''Single-Phase Inverter:''' Produces single-phase AC output. # '''Three-Phase Inverter:''' Produces three-phase AC output. == Based on Circuit Configuration == # '''Half-Bridge Inverter:''' Uses two controlled switches and a split DC supply. # '''Full-Bridge Inverter:''' Uses four controlled switches arranged in an H-bridge configuration. == Based on Commutation Technique == # '''Line-Commutated Inverter:''' Uses the AC supply to turn OFF thyristors. # '''Forced-Commutated Inverter:''' Uses an external commutation circuit to turn OFF thyristors. == Square Wave Inverter == '''Definition:''' A square wave inverter is a type of inverter that converts DC power into AC power and produces a square-shaped output voltage waveform. '''Working:''' * Semiconductor switches (MOSFETs or IGBTs) turn ON and OFF alternately. * This switching produces a square-shaped AC voltage. * The output voltage changes suddenly between positive and negative values. '''Characteristics:''' * Simple circuit design. * Low manufacturing cost. * High harmonic content. * Not suitable for all sensitive electronic devices. == Modified Sine Wave Inverter == '''Definition:''' A modified sine wave inverter is a type of inverter that converts DC power into AC power and produces a stepped waveform that approximately resembles a sine wave. '''Working:''' * Semiconductor switches operate in a controlled sequence. * The output contains positive, zero and negative voltage levels. * These voltage levels create a stepped AC waveform. '''Characteristics:''' * Moderate circuit complexity. * More economical than pure sine wave inverters. * Lower harmonic distortion than a typical square wave output. * Suitable for many basic electrical appliances, but may cause noise or heating in some devices == Pure Sine Wave Inverter == '''Definition:''' A pure sine wave inverter is a type of inverter that converts DC power into AC power and produces a smooth sinusoidal output waveform similar to the AC supply provided by electricity distribution systems. '''Working:''' * Power electronic switches operate using PWM (Pulse Width Modulation). * The switching pulses are controlled to produce a sinusoidal output. * An LC filter removes high-frequency switching components to obtain a smooth sine wave. '''Characteristics:''' * High-quality AC output. * Low harmonic distortion. * Suitable for sensitive electronic equipment. * Smooth operation of AC motors. * Generally more expensive than other types. == Voltage Source Inverter (VSI) == '''Definition:''' A Voltage Source Inverter (VSI) is a power electronic converter that converts a constant DC voltage into AC voltage at the output. === Working Principle === # A DC voltage source, such as a battery or rectifier, provides input voltage. # A large capacitor is connected across the DC input to maintain nearly constant DC voltage. # Semiconductor switches (MOSFETs, IGBTs or thyristors) turn ON and OFF in a controlled sequence. # Switching action converts DC voltage into AC voltage. # AC output is supplied to the load. === Characteristics of VSI === * Input: Constant DC voltage. * Output: AC voltage. * A large capacitor is generally connected across the DC supply. * Output current depends on the load. * Voltage can be controlled using PWM techniques. * Commonly used in solar systems and electric vehicles. === Applications === # Solar inverters. # Electric vehicles (EVs). # UPS systems. # Variable-frequency motor drives. # Industrial applications. ---- == 2. Current Source Inverter (CSI) == '''Definition:''' A Current Source Inverter (CSI) is a power electronic converter that converts a constant DC current into AC current at the output. === Working Principle === # A DC current source provides input current. # A large inductor is connected in series with the DC supply to maintain nearly constant current. # Semiconductor switches turn ON and OFF in a controlled sequence. # Switching action converts DC current into AC current. # AC current is supplied to the load. === Characteristics of CSI === * Input: Constant DC current. * Output: AC current. * A large inductor is connected in series with the DC supply. * Output voltage depends on the load. * Current can be controlled by the switching sequence. * Suitable for certain high-power industrial motor drives. === Applications === # High-power industrial motor drives. # Large synchronous motor drives. # Some renewable energy conversion systems. # Industrial power conversion systems. = Based on Phase = Based on the number of AC output phases, inverters are classified into two types. === A. Single-Phase Inverter === '''Definition:''' A single-phase inverter is a power electronic device that converts DC power into single-phase AC power. '''Working:''' # DC supply is given to the inverter. # Semiconductor switches (MOSFETs or IGBTs) operate in a controlled sequence. # Switching produces an alternating voltage. # Single-phase AC power is supplied to the load. '''Characteristics:''' * Produces single-phase AC output. * Generally used for low and medium-power applications. * Circuit configuration can be half-bridge or full-bridge. '''Applications:''' * Domestic UPS. * Home solar systems. * Small electrical appliances. * Single-phase motor drives. === B. Three-Phase Inverter === '''Definition:''' A three-phase inverter is a power electronic device that converts DC power into three-phase AC power consisting of three alternating voltages having the same frequency and magnitude, with a phase difference of 120° electrical between them. '''Working:''' # DC supply is provided to the inverter. # It generally uses six semiconductor switches. # The switches operate in a controlled sequence. # Three AC output voltages are generated. # These voltages are supplied to a three-phase load. '''Characteristics:''' * Produces three-phase AC output. * Three output phases are separated by 120°. * Suitable for high-power applications. * Commonly uses six IGBTs or MOSFETs. '''Applications:''' * Industrial motor drives. * Electric vehicles. * Solar power plants. * Industrial pumps and compressors. '''Working Principle:''' *# The DC supply is divided into two equal halves using two capacitors. *# When switch S1 is ON, the load receives positive voltage (+Vdc/2). *# When switch S2 is ON, the load receives negative voltage (-Vdc/2). *# The switches operate alternately to generate AC output. '''Advantages:''' * Simple circuit. * Requires fewer switches. * Lower cost. '''Disadvantages:''' * Requires a split DC supply. * Output voltage is half of the DC-link voltage. === B. Full-Bridge Inverter === '''Definition:''' A full-bridge inverter is a single-phase inverter that uses four controlled semiconductor switches arranged in an H-bridge configuration to convert DC power into AC power. '''Working Principle:''' # When switches S1 and S4 are ON, positive voltage (+Vdc) is applied across the load. # When switches S2 and S3 are ON, negative voltage (-Vdc) is applied across the load. # These switching combinations generate alternating voltage across the load. # PWM can be used to control the output waveform. '''Advantages:''' #* Higher output voltage than a half-bridge inverter for the same DC-link voltage. #* Better utilization of DC supply. #* Suitable for higher-power applications. '''Disadvantages:''' #* Requires four controlled switches. #* More complex control circuit. === Line-Commutated Inverter === '''Definition:''' A line-commutated inverter is an inverter in which the AC supply voltage provides the necessary reverse voltage to turn OFF the conducting thyristors. '''Working Principle:''' # The inverter uses thyristors (SCRs) as switching devices. # The AC system provides the commutating voltage. # When the AC voltage reverses, the conducting SCR experiences reverse voltage. # The SCR turns OFF, and another SCR can start conducting. # This process continues to produce AC power flow from the DC side to the AC side. '''Characteristics:''' * Requires an existing AC supply or grid. * Uses natural or line commutation. * Commonly associated with grid-connected thyristor converters. * Cannot independently establish an AC voltage and frequency. '''Applications:''' * HVDC transmission systems (line-commutated converter systems). * Grid-connected power conversion. * Some large industrial power systems. === B. Forced-Commutated Inverter === '''Definition:''' A forced-commutated inverter is an inverter in which an external commutation circuit or an appropriate switching arrangement is used to turn OFF the conducting thyristors. '''Working Principle:''' # DC supply is provided to the inverter. # A thyristor starts conducting when triggered. # An external commutation circuit applies reverse voltage or current to turn OFF the conducting thyristor. # Another thyristor is triggered to conduct. # The process repeats to produce AC output. '''Characteristics:''' * Does not depend on AC supply voltage for commutation. * Uses an external commutation arrangement when thyristors are employed. * Can operate with an independent AC output. * Modern self-commutated inverters commonly use IGBTs or MOSFETs. '''Applications:''' * UPS systems. * Solar inverters. * Battery energy storage systems. * Variable-frequency motor drives. c7a5up77c1q9xhfo1rslj82pi5pu47t User:Ronak0830/sandbox 2 486797 4679817 2026-11-03T15:58:18Z Ronak0830 3630311 Created page with "== '''Digital Twin Technology in Robotics and Automation''' ==" 4679817 wikitext text/x-wiki == '''Digital Twin Technology in Robotics and Automation''' == 8x7u75q1d0rlrtli7t2pnphv3yewd6l User:Sonupandit2580/sandbox 2 486798 4679818 2026-11-03T16:08:35Z Sonupandit2580 3626133 . 4679818 wikitext text/x-wiki = Battery System Packaging and Thermal Management = 5d88ixhsr1kvva443tq8jqqsfz8efox User:Noxveil29/Kishankumar/RaspberryPi 2 486799 4679820 2026-11-03T16:12:17Z Noxveil 29 3630280 Created page with "genius raspberry pi" 4679820 wikitext text/x-wiki genius raspberry pi gd07ev5z5mr7id5pev6lza2ly6coa2a User:Abhaypal2005/sandbox 2 486800 4679821 2026-11-03T16:37:45Z Abhaypal2005 3626134 Created page with "== AC Voltage Controllers ==" 4679821 wikitext text/x-wiki == AC Voltage Controllers == 691f2xu5e0wovc6wet1j2uecvucyl3s User:Thanuj1212/Power Electronics in Electric Vehicles 2 486801 4679825 2026-11-03T17:16:58Z Thanuj1212 3629947 Created page with " == Power Electronics in Electric Vehicles == The transition to electric vehicles (EVs) has seen a major change thanks to their widespread use. Power electronics form the basis of EV technology and are essential for efficient energy conversion and management. This paper gives a thorough review of the role, developments, and challenges associated with power electronics in electric vehicles. It looks at how power electronics improve performance, increase range, and help ma..." 4679825 wikitext text/x-wiki == Power Electronics in Electric Vehicles == The transition to electric vehicles (EVs) has seen a major change thanks to their widespread use. Power electronics form the basis of EV technology and are essential for efficient energy conversion and management. This paper gives a thorough review of the role, developments, and challenges associated with power electronics in electric vehicles. It looks at how power electronics improve performance, increase range, and help make electric mobility more sustainable, from the powertrain right through to the charging infrastructure. The abstract examines key technologies, including inverters, converters, and energy management systems, in the context of EVs. It also looks at emerging trends, standards, and future developments that are influencing the field of power electronics in the quickly changing area of electric vehicles. 9vscoxq02kqsjlfhvbspe4quluwnzdk User:Chalky282 2 486802 4679826 2026-11-03T17:29:23Z Chalky282 3630310 I added a Wikibooks page for myself 4679826 wikitext text/x-wiki Hi! I'm Chalky282. I joined Wikipedia on 10/28/2026 on 8:52 pm EDT. I've used Wikibooks before but I'm new to editing Wikibooks. I am the same person as: [https://en.wikipedia.org/wiki/User:Chalky282 Chalky 282] du5htqnk8l5934qn1pe2b2jrzzsnj56 4679827 4679826 2026-11-03T17:30:12Z Chalky282 3630310 little touch up 4679827 wikitext text/x-wiki Hi! I'm Chalky282. I joined Wikibooks on 11/2/2026 on morning EDT. I've used Wikibooks before but I am new to editing Wikibooks. I am the same person as: [https://en.wikipedia.org/wiki/User:Chalky282 Chalky 282] ekixvnjy4gp3l5pqr2sco4dezi2c4gh User:Tej-09/sandbox 2 486803 4679828 2026-11-03T17:51:20Z Tej-09 3629922 Title 4679828 wikitext text/x-wiki = Embedded Systems = alr61io7lbu8gxl16xc9q65w3bk32rj User talk:James3141592/sandbox 3 486804 4679829 2026-11-03T17:59:53Z James3141592 3217245 test signature 4679829 wikitext text/x-wiki <span style="background-color: purple">[[User:James3141592|<span style="color: white">'''James3141592'''</span>]] [[User talk:James3141592|<span style="color: white">'''talk'''</span>]]</span> 17:59, 3 November 2026 (UTC) pqbzlfk0l1qcnsq5b5ov8vpvhwaoo44 4679830 4679829 2026-11-03T18:00:35Z James3141592 3217245 rm signature 4679830 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 Category:Wikibooks Magazine 14 486805 4679851 2026-11-03T22:42:34Z Arlo Barnes 381814 subcategorise 4679851 wikitext text/x-wiki [[category:Wikibooks|Magazine]] qiuxaxai97mydw8qfcfxgdwweeau8pk User:TrulyFlawed 2 486806 4679853 2026-11-03T22:51:44Z Mfield 753190 Mfield moved page [[User:TrulyFlawed]] to [[User:Duskhasfallen]]: Automatically moved page while renaming the user "[[Special:CentralAuth/TrulyFlawed|TrulyFlawed]]" to "[[Special:CentralAuth/Duskhasfallen|Duskhasfallen]]" 4679853 wikitext text/x-wiki #REDIRECT [[User:Duskhasfallen]] c5v3x7g6241412d32ikmiolg6v46jn8 User talk:TrulyFlawed 3 486807 4679855 2026-11-03T22:51:44Z Mfield 753190 Mfield moved page [[User talk:TrulyFlawed]] to [[User talk:Duskhasfallen]]: Automatically moved page while renaming the user "[[Special:CentralAuth/TrulyFlawed|TrulyFlawed]]" to "[[Special:CentralAuth/Duskhasfallen|Duskhasfallen]]" 4679855 wikitext text/x-wiki #REDIRECT [[User talk:Duskhasfallen]] gn662tprk32u2gvxe7by3lodnaqa8qj User:Jay D. Rattle 2 486808 4679856 2026-11-03T22:55:13Z Jay D. Rattle 3629560 created a user page 4679856 wikitext text/x-wiki Hello, I'm new here I guess. I'm mostly here to edit the world war two wikijunior book I guess. th0wo9g999n2dtvmur9z0cf8mn0erov 4679857 4679856 2026-11-03T23:33:46Z Jay D. Rattle 3629560 4679857 wikitext text/x-wiki Hello, I'm new here. I'm mostly here to edit the world war two wikijunior book I guess. t7pc6hq0iabgh5hoeguk0sa5zli95ph User:Jay D. Rattle/sandbox 2 486809 4679858 2026-11-03T23:40:00Z Jay D. Rattle 3629560 Created page with "The Nazi's persecution of Jews began even before they took power in 1933." 4679858 wikitext text/x-wiki The Nazi's persecution of Jews began even before they took power in 1933. 5esaido5cd4elrvwsb1fxaqomlwmzwm On 2D Inverse Problems/Eta 0 486810 4679865 2026-11-04T01:12:11Z DVD206 724793 geometric progression eigenvalues 4679865 wikitext text/x-wiki The binomial matrix, central to the study is upper triangular in the Vandermonde basis providing a bridge between linear algebra eigenvalues and set theory continuum hypothesis: <math>\begin{pmatrix}1&6&1&0\\0&4&4&0\\0&1&6&1\\0&0&4&4\end{pmatrix}= V^{-1}(x)\begin{pmatrix}8& & & \\0&4&*&\\0&0&2&\\0&0&0&1\end{pmatrix}V(x), </math> <math>V(x)=\begin{pmatrix}1&x&x^2&x^3\\1&(1+x)&(1+x)^2&(1+x)^3\\1&(2+x)&(2+x)^2&(2+x)^3\\1&(3+x)&(3+x)^2&(3+x)^3\end{pmatrix}, </math> <math> V(0)=\begin{pmatrix}1&0&0&0\\1&1&1&1\\1&2&4&8\\1&3&9&27\end{pmatrix}</math> The eigenvalues therefor form geometric progression as for the shift matrix with complex parameter and are described by <math>\ln(2)=\eta(1)</math>, the alternating series. {{BookCat}} oekzqz35oi6u7arrg7zclx5xy4rdm3c On 2D Inverse Problems/Complex 0 486811 4679866 2026-11-04T01:17:00Z DVD206 724793 complex, real and imaginary 4679866 wikitext text/x-wiki The points of complex plane or 2D numbers can be written in two ways: <math></math> 4mpsq1a4mhk6nhiauk2tm9wsiuwobls 4679867 4679866 2026-11-04T01:26:37Z DVD206 724793 symbolic complex variable 4679867 wikitext text/x-wiki The points of complex plane or 2D numbers can be written in two ways: <math> z=x+iy=re^{i\theta},\bar{z}=x-iy. </math> <math> |z|^2=z\bar{z} </math> and <math> \Lambda_1^2=\partial_\theta \partial_\theta^*=-\partial{\theta\theta} </math> is the square of the response of the circle and disc. The linear fractional transformation, <math>\tau(z)=\frac{1-z}{1+z}</math> maps unit disc into half-plane and <math>\tau\dot\tau=identity.</math> 8za13g64pnegmj9ttwyybx71tzkkw0q 4679868 4679867 2026-11-04T01:28:21Z DVD206 724793 4679868 wikitext text/x-wiki The points of complex plane or 2D numbers can be written in two ways: <math> z=x+iy=re^{i\theta},\bar{z}=x-iy. </math> <math> |z|^2=z\bar{z} </math> and <math> \Lambda_1^2=\partial_\theta \partial_\theta^*=-\partial_{\theta\theta} </math> is the square of the response of the circle and disc. The linear fractional transformation, <math>\tau(z)=\frac{1-z}{1+z}</math> maps unit disc into half-plane and <math>\tau\circ\tau=identity.</math> 83zvhhhlkgftockfjebyfw3c1ysy1y5 Professionalism/Air India Flight 171 0 486812 4679873 2026-11-04T02:26:47Z Yqj3km 3579825 created initial page 4679873 wikitext text/x-wiki '''CLASS PROJECT IN PROGRESS: DO NOT DELETE''' l2len1rdixfgshqx0mqvvxwub825ug4 4679874 4679873 2026-11-04T02:27:26Z Yqj3km 3579825 4679874 wikitext text/x-wiki '''CLASS PROJECT IN PROGRESS: DO NOT DELETE''' {{BookCat}} oo5hhq6yva0t9cjbhyegcdhfqvfz9pd 4679876 4679874 2026-11-04T02:31:21Z Yqj3km 3579825 4679876 wikitext text/x-wiki '''CLASS PROJECT IN PROGRESS: DO NOT DELETE''' == Background == == Investigation and Timeline == == Institutional Responses == === Air India === === Federal Aviation Administration (FAA) === === Aircraft Accident Investigation Bureau (AAIB) === === UK Government === == Professionalism and Deflection of Responsibility == == Conclusion == == References == <references /> {{BookCat}} {{BookCat}} oheuanp3kezxmq4lbafczovjyqqk610 User talk:Booksby 3 486814 4679882 2026-11-04T05:20:14Z MathsScienceNerd1 3626296 Notifying author of speedy deletion nomination 4679882 wikitext text/x-wiki == I have added a tag to a page you created == Hi! I'm MathsScienceNerd1, and I recently reviewed your page, [[:The Speech]]. I have added a tag to the page, because it <strong>may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].</strong> This means that it can be deleted at any time. If you believe that your page should not be deleted, please post a message on [[Talk:The Speech|the page's talk page]] explaining why. <strong>If your reasoning is convincing, your page may be saved.</strong> If you have any questions or concerns, please [[User talk:MathsScienceNerd1|let me know]]. Thank you! <!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --> [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 05:20, 4 November 2026 (UTC) qsap8kzqhiyzplfeyk1zlcs8atfhfht User:Ninja100R/sandbox 2 486815 4679887 2026-11-04T06:11:52Z Ninja100R 3629842 Created page with "===Working Principle of Mobile Communication Engineering===" 4679887 wikitext text/x-wiki ===Working Principle of Mobile Communication Engineering=== 5v9d8xh5d293v761xgqkcvo0w8uw6he User:Bojja Mahesh Yadav/sandbox/2.1 Electromagnetic Waves 2 486816 4679890 2026-11-04T06:30:25Z Bojja Mahesh Yadav 3629813 Added images and references to Section 2.1 on Electromagnetic Waves, with minor grammar and formatting corrections. 4679890 wikitext text/x-wiki == 2.1 Electromagnetic Waves == Electromagnetic waves are a type of energy that can be transmitted through space. This occurs through oscillating electric and magnetic fields. The electric and magnetic fields are at right angles to each other and to the direction of travel. Electromagnetic waves do not require any medium to travel through. They can travel at the speed of light, which is approximately <math>3 \times 10^8</math> m/s through a vacuum.<ref name="NASA">{{cite web |title=Electromagnetic Waves |url=https://science.nasa.gov/ |publisher=NASA |access-date=4 November 2026}}</ref> Electromagnetic waves are created by accelerated electric charges. They transfer energy from one place to another. They are important in many areas, such as natural processes, scientific research, communication and modern technology. [[File:Electromagnetic wave EN.svg|thumb|center|450px|Diagram showing the electric and magnetic fields of an electromagnetic wave.]] === 2.1.1 Key Properties of Electromagnetic Waves === There are several key properties associated with electromagnetic waves. ;Frequency :The number of complete waves that pass through a certain point in one second. It is measured in Hertz (Hz). Higher frequency means more waves pass each second. ;Wavelength :The distance between two points that are in phase, such as two consecutive peaks. It is measured in metres. ;Amplitude :The maximum strength of the electric or magnetic field. ;Velocity :Electromagnetic waves travel at approximately <math>3 \times 10^8</math> m/s in a vacuum. They travel more slowly in certain materials, such as glass and water. ;Energy :Energy is carried by electromagnetic radiation. The energy of each photon depends on its frequency. The relationship between frequency, wavelength and velocity is: :<math>c=f\lambda</math> Where: * Speed of light = <math>c</math> (m/s) * Frequency = <math>f</math> (Hz) * Wavelength = <math>\lambda</math> (m) This shows that frequency and wavelength are inversely proportional when the wave velocity remains constant.<ref name="NASA"/> === 2.1.2 Electromagnetic Spectrum === The electromagnetic spectrum is the entire range of electromagnetic radiation. The electromagnetic spectrum is divided into several categories. The main categories are: * Radio waves * Microwaves * Infrared * Visible light * Ultraviolet * X-rays * Gamma rays Radio waves and microwaves are very important in wireless communication. [[File:Electromagnetic-Spectrum.svg|thumb|center|450px|The electromagnetic spectrum showing the different categories of electromagnetic radiation.]] === 2.1.3 Radio Frequency Electromagnetic Waves === Radio Frequency (RF) electromagnetic waves are used in wireless communications. They operate in a frequency range of approximately 3 kHz to 300 GHz.<ref name="ICNIRP">{{cite web |title=Guidelines for Limiting Exposure to Electromagnetic Fields (100 kHz to 300 GHz) |url=https://www.icnirp.org/en/publications/article/rf-guidelines-2020.html |publisher=International Commission on Non-Ionizing Radiation Protection |year=2020 |access-date=4 November 2026}}</ref> RF electromagnetic waves are frequently used in: * Mobile communication networks. * Radio and television. * Wi-Fi and Bluetooth. * Satellite communications. * Radar. * Wireless sensor networks. Mobile towers send RF signals through antennas. These signals carry information between the user's mobile phone and the cellular network. There are several generations of mobile communication that operate on different frequencies. For example, 4G and 5G operate on various frequencies depending on the country, provider and network. === 2.1.4 Electromagnetic Waves in Mobile Communication === Mobile communication uses electromagnetic waves to allow wireless communication. A basic cellular communication system includes: ;Mobile Device Phones have antennas that send and receive RF signals. When a user makes a call or accesses the internet, the device converts information into RF signals. ;Base Transceiver Station (BTS) This is an important part of the cellular network. The BTS has antennas and electronic equipment to send and receive signals in a certain area. ;Mobile Network Core This manages communication between base stations and allows users to connect to other networks, including telephone and internet networks. The communication works as follows: # The mobile device creates an RF signal. # The RF signal travels through the air to a nearby base station. # The base station receives and processes the signal. # The network sends the information to its intended destination. # The receiving device receives the information through RF signals. This allows mobile users to communicate without wired connections.<ref name="WHO">{{cite web |title=Radiation: Electromagnetic Fields |url=https://www.who.int/news-room/questions-and-answers/item/radiation-electromagnetic-fields |publisher=World Health Organization |access-date=4 November 2026}}</ref> [[File:Mobile telephone antennas tower.jpg|thumb|center|400px|Antennas installed on a mobile communication tower.]] === 2.1.5 Ionising and Non-Ionising Radiation === Electromagnetic radiation can be divided into two categories. ;Ionising Radiation Radiation that has enough energy to remove electrons from atoms or molecules, causing them to become electrically charged particles known as ions. Examples of ionising radiation: * X-rays. * Gamma rays. * Some high-energy ultraviolet radiation. Exposure to ionising radiation at sufficient levels can cause damage to biological tissue and DNA. ;Non-Ionising Radiation Radiation that does not have enough photon energy to directly ionise atoms or molecules. Examples of non-ionising radiation: * Radio waves. * Microwaves. * Infrared. * Visible light. Mobile towers operate using RF electromagnetic waves, which are non-ionising. However, just because radiation is non-ionising does not mean it is safe at every exposure level. High levels of RF fields can cause heating in biological tissues. The level of exposure is measured and compared with established safety guidelines.<ref name="WHO"/><ref name="ICNIRP"/> === 2.1.6 Interaction of Electromagnetic Waves with the Surrounding Area === As electromagnetic waves travel through the environment, they interact with buildings, trees, vehicles, soil and other objects. These interactions affect the strength and quality of wireless signals. The main interactions are: ;Reflection :Waves are reflected off surfaces such as buildings and metal structures. ;Refraction :Waves change direction as they pass through a material with different electromagnetic properties. ;Diffraction :Waves bend around objects or pass through gaps. This allows signals to reach areas that are not in the direct line of sight of the antenna. ;Scattering :Waves spread out in different directions when they encounter rough surfaces or small objects. ;Absorption :Some electromagnetic energy is absorbed by materials and converted into different forms of energy, including heat. These interactions affect mobile network coverage, signal strength and quality. === 2.1.7 Measuring Electromagnetic Fields === The electromagnetic fields produced by communication systems can be measured using the following quantities: * Electric Field Strength (E): Measured in volts per metre (V/m). * Magnetic Field Strength (H): Measured in amperes per metre (A/m). * Power Density (S): Measured in watts per square metre (W/m²). * Frequency (f): Measured in Hertz (Hz). Power density is useful because it measures the amount of electromagnetic power passing through a unit area. RF exposure can be measured using appropriate RF field meters and spectrum analysers.<ref name="ICNIRP"/> === 2.1.8 Electromagnetic Waves and Cell Tower Radiation === Cellular base stations use RF electromagnetic waves to provide wireless communication in a certain area. The antennas mounted on communication towers send signals using pre-assigned frequency bands. As the signals travel through the environment, they interact with nearby objects. The strength of the electromagnetic field depends on: * Power of the signal transmitted from the base station. * Antenna gain. * Distance from the antenna. * Height and orientation of the antenna. * Frequency. * Environmental conditions. The antenna has a radiation pattern. This shows how electromagnetic energy is distributed in different directions. Cellular antennas are usually designed to cover certain geographical sectors. Understanding these properties is important when studying electromagnetic field exposure.<ref name="WHO"/><ref name="ICNIRP"/> === 2.1.9 Why Study Electromagnetic Waves? === Studying electromagnetic waves provides an understanding of how modern wireless communication systems work and how they interact with the environment. It helps us understand how mobile communication signals travel. This knowledge can help us analyse RF signal propagation, design efficient antennas and communication networks, understand electromagnetic field exposure, identify factors affecting signal strength and coverage, and compare measured RF exposure levels with safety guidelines. Overall, electromagnetic waves are fundamental to understanding cell tower radiation. == References == <references /> gbhjfvr4lkmusguzxj40rp528b84ygc General Literary Chinese from Scratch/How do we Write Height and Weight? 0 486817 4679891 2026-11-04T06:40:50Z Shira the Mogul 3560559 Created page with "Having learned numbers, you must be wondering how to handle traditional Chinese measurements. Having no true standard for a significant period of time, you will not find a clean conversion for all time periods. However, it is useful to get an idea of the sizes, so you can visualise it. By this point in the course, I trust that you have figured out your favourite dictionary and use it in Yomitan, Pleco, or similar software. If you still need to figure this out, go to ..." 4679891 wikitext text/x-wiki Having learned numbers, you must be wondering how to handle traditional Chinese measurements. Having no true standard for a significant period of time, you will not find a clean conversion for all time periods. However, it is useful to get an idea of the sizes, so you can visualise it. By this point in the course, I trust that you have figured out your favourite dictionary and use it in Yomitan, Pleco, or similar software. If you still need to figure this out, go to [[General_Literary_Chinese_from_Scratch/Introduction|the introduction]] and get yourself set up. This is ''essential'' for a fluid experience in and out of the course. ==Text== [[File:Phénix à neuf têtes.png|thumb|200px|九鳳像]] This is a text from the ''Classic of Mountains and Seas'' 山海經, which we will be covering more in the next Unit. It is known for talking about strange things; weird plants, odd animals, and where to find the best metals and jade. It was one of the first atlases ever written. You will see many structures in this text that you recognise from previous lessons, and I want you to write those down for me now. <blockquote> 又東五十里,曰宣山。淪水出焉,東南流注于視水,其中多蛟。其上有桑焉,大五十尺,其枝四衢,其葉大尺餘,赤理黃華青柎,名曰帝女之桑。 </blockquote> Right! Now, you have identified what you ''can'' grasp right now. You have likely identified: * It has named something, a mountain? * There is some sort of water (What kind? A body of water?) * There are numbers, followed by something. * Something is named at the end. Let's identify what these numbers are next to: * 里 - Chinese mile, around 500 metres, or 0.33 miles. * 尺 - Chinese foot, around 0.33 metres. I now want you to use your dictionary to look at the words you don't understand and write them down. Consult 説文解字 or 康熙字典, or perhaps use Yomitan. Find what works for you. ==Grammar== <blockquote> 又東五十里 </blockquote> 東 is a compass direction: East. In Chinese, the four directions 四方 are typically ordered East 東 South 南, West 西, and North 北. Don't worry your head about 又, but think of it as "anyway" or "on another note" here. So you get: "Anyway, 50 'miles' east...". The next part of the text is important, as you learn some very expressive terms here: <blockquote> 其上有桑焉,大五十尺,其枝四衢,其葉大尺餘 </blockquote> 其 is like "it/he/she" here, referring to the mountain from before. Therefore, 其上 is "its surface" or "on it" if taken idiomatically. There is also a very important structure: <blockquote> 有甲焉 </blockquote> This literally translates to "have X here," and comes up a lot, especially in older texts like this one. You can use this to describe things that appear in places and then go further thereafter. You will also see 大 here: What do you think it means here, if followed by 尺? The equivalent for this in weight is 重, which appears less often compared to size. I must highlight 餘 here: It can come across as "surplus" or even "extra," and you will find yourself wanting to use this a lot. Here, it is like "or more," so "over x measurement." It is very broad, very flexible, and very useful. So now you know: * Directions go before the measurement of distance. * The word for measuring usually goes after the number. * How to describe things in given places. The majority of the 山海經 is written this way. Now that you know the basic structures, I strongly recommend [https://ctext.org/shan-hai-jing using it as a starter text]. ==Correspondence Table== This is a conversion table for length and weight as promulgated in 營造尺庫平制 during the Qing dynasty, in 1908. This is not quite equivalent to what you see prior, but it is a decent enough approximation for your purposes. {| class="wikitable" |+ Length ! Measure !! Qing standard !! Metric !! Imperial |- ! scope="row" | 丈 | 10 尺 || 3.2 m || 10.499 ft |- ! scope="row" | 尺 | 10 寸 || 32 cm || 12.598 in |- ! scope="row" | 寸 | 10 分 || 3.2 cm || 1.260 in |- ! scope="row" | 分 | — || 3.2 mm || 0.126 in |} {| class="wikitable" |+ Weight ! Measure !! Qing standard !! Metric !! Imperial |- ! scope="row" | 斤 | 16 兩 || 596.816 g || 1.316 lb |- ! scope="row" | 兩 | 10 錢 || 37.301 g || 1.316 oz |- ! scope="row" | 錢 | 10 分 || 3.7301 g || 0.132 oz |} ==Exercise== [[File:Stamp of Indonesia - 2008 - Colnect 385155 - Holy Days - Celebrations Chinese New Year.jpeg|thumb|200px|<u>印度尼西亞</u>之蓋印有鼠焉]] I have some animals next to emoji here. Think of their size and weight, and write it down. * 🐀 鼠 * 🐂 牛 * 🐅 虎 * 🐇 兔 * 🐉 龍 * 🐍 蛇 * 🐎 馬 * 🐐 羊 * 🐒 猴 * 🐓 雞 * 🐕 犬 * 🐖 豕 How about writing it like this? <blockquote> 豕重幾何?曰:重百斤。 </blockquote> I think you can do it! How about you try writing about that field with grains we thought of before, now knowing how to express distance and how to describe something being somewhere? Do you recognise this order? What do you think they are? ==References== * 《營造尺庫平制》 * 《山海經》 * 《清稗類鈔》 * 《蘭室秘藏》 * 《聊齋》 * Pulleyblank, E. G. (2000). Outline of classical Chinese grammar (Repr). UBC Press. cbts81r3wvaqktbqxnbl12a30jcmgqa 4679892 4679891 2026-11-04T06:41:12Z Shira the Mogul 3560559 4679892 wikitext text/x-wiki {{BookCat}} Having learned numbers, you must be wondering how to handle traditional Chinese measurements. Having no true standard for a significant period of time, you will not find a clean conversion for all time periods. However, it is useful to get an idea of the sizes, so you can visualise it. By this point in the course, I trust that you have figured out your favourite dictionary and use it in Yomitan, Pleco, or similar software. If you still need to figure this out, go to [[General_Literary_Chinese_from_Scratch/Introduction|the introduction]] and get yourself set up. This is ''essential'' for a fluid experience in and out of the course. ==Text== [[File:Phénix à neuf têtes.png|thumb|200px|九鳳像]] This is a text from the ''Classic of Mountains and Seas'' 山海經, which we will be covering more in the next Unit. It is known for talking about strange things; weird plants, odd animals, and where to find the best metals and jade. It was one of the first atlases ever written. You will see many structures in this text that you recognise from previous lessons, and I want you to write those down for me now. <blockquote> 又東五十里,曰宣山。淪水出焉,東南流注于視水,其中多蛟。其上有桑焉,大五十尺,其枝四衢,其葉大尺餘,赤理黃華青柎,名曰帝女之桑。 </blockquote> Right! Now, you have identified what you ''can'' grasp right now. You have likely identified: * It has named something, a mountain? * There is some sort of water (What kind? A body of water?) * There are numbers, followed by something. * Something is named at the end. Let's identify what these numbers are next to: * 里 - Chinese mile, around 500 metres, or 0.33 miles. * 尺 - Chinese foot, around 0.33 metres. I now want you to use your dictionary to look at the words you don't understand and write them down. Consult 説文解字 or 康熙字典, or perhaps use Yomitan. Find what works for you. ==Grammar== <blockquote> 又東五十里 </blockquote> 東 is a compass direction: East. In Chinese, the four directions 四方 are typically ordered East 東 South 南, West 西, and North 北. Don't worry your head about 又, but think of it as "anyway" or "on another note" here. So you get: "Anyway, 50 'miles' east...". The next part of the text is important, as you learn some very expressive terms here: <blockquote> 其上有桑焉,大五十尺,其枝四衢,其葉大尺餘 </blockquote> 其 is like "it/he/she" here, referring to the mountain from before. Therefore, 其上 is "its surface" or "on it" if taken idiomatically. There is also a very important structure: <blockquote> 有甲焉 </blockquote> This literally translates to "have X here," and comes up a lot, especially in older texts like this one. You can use this to describe things that appear in places and then go further thereafter. You will also see 大 here: What do you think it means here, if followed by 尺? The equivalent for this in weight is 重, which appears less often compared to size. I must highlight 餘 here: It can come across as "surplus" or even "extra," and you will find yourself wanting to use this a lot. Here, it is like "or more," so "over x measurement." It is very broad, very flexible, and very useful. So now you know: * Directions go before the measurement of distance. * The word for measuring usually goes after the number. * How to describe things in given places. The majority of the 山海經 is written this way. Now that you know the basic structures, I strongly recommend [https://ctext.org/shan-hai-jing using it as a starter text]. ==Correspondence Table== This is a conversion table for length and weight as promulgated in 營造尺庫平制 during the Qing dynasty, in 1908. This is not quite equivalent to what you see prior, but it is a decent enough approximation for your purposes. {| class="wikitable" |+ Length ! Measure !! Qing standard !! Metric !! Imperial |- ! scope="row" | 丈 | 10 尺 || 3.2 m || 10.499 ft |- ! scope="row" | 尺 | 10 寸 || 32 cm || 12.598 in |- ! scope="row" | 寸 | 10 分 || 3.2 cm || 1.260 in |- ! scope="row" | 分 | — || 3.2 mm || 0.126 in |} {| class="wikitable" |+ Weight ! Measure !! Qing standard !! Metric !! Imperial |- ! scope="row" | 斤 | 16 兩 || 596.816 g || 1.316 lb |- ! scope="row" | 兩 | 10 錢 || 37.301 g || 1.316 oz |- ! scope="row" | 錢 | 10 分 || 3.7301 g || 0.132 oz |} ==Exercise== [[File:Stamp of Indonesia - 2008 - Colnect 385155 - Holy Days - Celebrations Chinese New Year.jpeg|thumb|200px|<u>印度尼西亞</u>之蓋印有鼠焉]] I have some animals next to emoji here. Think of their size and weight, and write it down. * 🐀 鼠 * 🐂 牛 * 🐅 虎 * 🐇 兔 * 🐉 龍 * 🐍 蛇 * 🐎 馬 * 🐐 羊 * 🐒 猴 * 🐓 雞 * 🐕 犬 * 🐖 豕 How about writing it like this? <blockquote> 豕重幾何?曰:重百斤。 </blockquote> I think you can do it! How about you try writing about that field with grains we thought of before, now knowing how to express distance and how to describe something being somewhere? Do you recognise this order? What do you think they are? ==References== * 《營造尺庫平制》 * 《山海經》 * 《清稗類鈔》 * 《蘭室秘藏》 * 《聊齋》 * Pulleyblank, E. G. (2000). Outline of classical Chinese grammar (Repr). UBC Press. no92ynl4kkg3snmrif07e6gs3ntpb5l 4679894 4679892 2026-11-04T06:42:00Z Shira the Mogul 3560559 4679894 wikitext text/x-wiki {{BookCat}} Having learned numbers, you must be wondering how to handle traditional Chinese measurements. Having no true standard for a significant period of time, you will not find a clean conversion for all time periods. However, it is useful to get an idea of the sizes, so you can visualise it. By this point in the course, I trust that you have figured out your favourite dictionary and use it in Yomitan, Pleco, or similar software. If you still need to figure this out, go to [[General_Literary_Chinese_from_Scratch/Introduction|the introduction]] and get yourself set up. This is ''essential'' for a fluid experience in and out of the course. ==Text== [[File:Phénix à neuf têtes.png|thumb|200px|九鳳像]] This is a text from the ''Classic of Mountains and Seas'' 山海經, which we will be covering more in the next Unit. It is known for talking about strange things; weird plants, odd animals, and where to find the best metals and jade. It was one of the first atlases ever written. You will see many structures in this text that you recognise from previous lessons, and I want you to write those down for me now. '''Skim''' it. Do not try to understand everything. Do not comb through it with Yomitan. <blockquote> 又東五十里,曰宣山。淪水出焉,東南流注于視水,其中多蛟。其上有桑焉,大五十尺,其枝四衢,其葉大尺餘,赤理黃華青柎,名曰帝女之桑。 </blockquote> Right! Now, you have identified what you ''can'' grasp right now. You have likely identified: * It has named something, a mountain? * There is some sort of water (What kind? A body of water?) * There are numbers, followed by something. * Something is named at the end. Let's identify what these numbers are next to: * 里 - Chinese mile, around 500 metres, or 0.33 miles. * 尺 - Chinese foot, around 0.33 metres. I now want you to use your dictionary to look at the words you don't understand and write them down. Consult 説文解字 or 康熙字典, or perhaps use Yomitan. Find what works for you. ==Grammar== <blockquote> 又東五十里 </blockquote> 東 is a compass direction: East. In Chinese, the four directions 四方 are typically ordered East 東 South 南, West 西, and North 北. Don't worry your head about 又, but think of it as "anyway" or "on another note" here. So you get: "Anyway, 50 'miles' east...". The next part of the text is important, as you learn some very expressive terms here: <blockquote> 其上有桑焉,大五十尺,其枝四衢,其葉大尺餘 </blockquote> 其 is like "it/he/she" here, referring to the mountain from before. Therefore, 其上 is "its surface" or "on it" if taken idiomatically. There is also a very important structure: <blockquote> 有甲焉 </blockquote> This literally translates to "have X here," and comes up a lot, especially in older texts like this one. You can use this to describe things that appear in places and then go further thereafter. You will also see 大 here: What do you think it means here, if followed by 尺? The equivalent for this in weight is 重, which appears less often compared to size. I must highlight 餘 here: It can come across as "surplus" or even "extra," and you will find yourself wanting to use this a lot. Here, it is like "or more," so "over x measurement." It is very broad, very flexible, and very useful. So now you know: * Directions go before the measurement of distance. * The word for measuring usually goes after the number. * How to describe things in given places. The majority of the 山海經 is written this way. Now that you know the basic structures, I strongly recommend [https://ctext.org/shan-hai-jing using it as a starter text]. ==Correspondence Table== This is a conversion table for length and weight as promulgated in 營造尺庫平制 during the Qing dynasty, in 1908. This is not quite equivalent to what you see prior, but it is a decent enough approximation for your purposes. {| class="wikitable" |+ Length ! Measure !! Qing standard !! Metric !! Imperial |- ! scope="row" | 丈 | 10 尺 || 3.2 m || 10.499 ft |- ! scope="row" | 尺 | 10 寸 || 32 cm || 12.598 in |- ! scope="row" | 寸 | 10 分 || 3.2 cm || 1.260 in |- ! scope="row" | 分 | — || 3.2 mm || 0.126 in |} {| class="wikitable" |+ Weight ! Measure !! Qing standard !! Metric !! Imperial |- ! scope="row" | 斤 | 16 兩 || 596.816 g || 1.316 lb |- ! scope="row" | 兩 | 10 錢 || 37.301 g || 1.316 oz |- ! scope="row" | 錢 | 10 分 || 3.7301 g || 0.132 oz |} ==Exercise== [[File:Stamp of Indonesia - 2008 - Colnect 385155 - Holy Days - Celebrations Chinese New Year.jpeg|thumb|200px|<u>印度尼西亞</u>之蓋印有鼠焉]] I have some animals next to emoji here. Think of their size and weight, and write it down. * 🐀 鼠 * 🐂 牛 * 🐅 虎 * 🐇 兔 * 🐉 龍 * 🐍 蛇 * 🐎 馬 * 🐐 羊 * 🐒 猴 * 🐓 雞 * 🐕 犬 * 🐖 豕 How about writing it like this? <blockquote> 豕重幾何?曰:重百斤。 </blockquote> I think you can do it! How about you try writing about that field with grains we thought of before, now knowing how to express distance and how to describe something being somewhere? Do you recognise this order? What do you think they are? ==References== * 《營造尺庫平制》 * 《山海經》 * 《清稗類鈔》 * 《蘭室秘藏》 * 《聊齋》 * Pulleyblank, E. G. (2000). Outline of classical Chinese grammar (Repr). UBC Press. 4uej7c123drdmhejx1kwkivn74yzqgj 4679895 4679894 2026-11-04T06:45:51Z Shira the Mogul 3560559 4679895 wikitext text/x-wiki {{BookCat}} Having learned numbers, you must be wondering how to handle traditional Chinese measurements. Having no true standard for a significant period of time, you will not find a clean conversion for all time periods. However, it is useful to get an idea of the sizes, so you can visualise it. By this point in the course, I trust that you have figured out your favourite dictionary and use it in Yomitan, Pleco, or similar software. If you still need to figure this out, go to [[General_Literary_Chinese_from_Scratch/Introduction|the introduction]] and get yourself set up. This is ''essential'' for a fluid experience in and out of the course. ==Text== [[File:Phénix à neuf têtes.png|thumb|200px|九鳳像]] This is a text from the ''Classic of Mountains and Seas'' 山海經, which we will be covering more in the next Unit. It is known for talking about strange things; weird plants, odd animals, and where to find the best metals and jade. It was one of the first atlases ever written. You will see many structures in this text that you recognise from previous lessons, and I want you to write those down for me now. '''Skim''' it. Do not try to understand everything. Do not comb through it with Yomitan. <blockquote> 又東五十里,曰宣山。淪水出焉,東南流注于視水,其中多蛟。其上有桑焉,大五十尺,其枝四衢,其葉大尺餘,赤理黃華青柎,名曰帝女之桑。 </blockquote> Right! Now, you have identified what you ''can'' grasp right now. You have likely identified: * It has named something, a mountain? * There is some sort of water (What kind? A body of water?) * There are numbers, followed by something. * Something is named at the end. Let's identify what these numbers are next to: * 里 - Chinese mile, around 500 metres, or 0.33 miles. * 尺 - Chinese foot, around 0.33 metres. I now want you to use your dictionary to look at the words you don't understand and write them down. Consult 説文解字 or 康熙字典, or perhaps use Yomitan. Find what works for you. ==Grammar== <blockquote> 又東五十里 </blockquote> 東 is a compass direction: East. In Chinese, the four directions 四方 are typically ordered East 東 South 南, West 西, and North 北. Don't worry your head about 又, but think of it as "anyway" or "on another note" here. So you get: "Anyway, 50 'miles' east...". The next part of the text is important, as you learn some very expressive terms here: <blockquote> 其上有桑焉,大五十尺,其枝四衢,其葉大尺餘 </blockquote> 其 is like "it/he/she" here, referring to the mountain from before. Therefore, 其上 is "its surface" or "on it" if taken idiomatically. There is also a very important structure: <blockquote> 有甲焉 </blockquote> This literally translates to "have X here," and comes up a lot, especially in older texts like this one. You can use this to describe things that appear in places and then go further thereafter. You will also see 大 here: What do you think it means here, if followed by 尺? The equivalent for this in weight is 重, which appears less often compared to size. You may also see 高 for height in later Literary Chinese. I must highlight 餘 here: It can come across as "surplus" or even "extra," and you will find yourself wanting to use this a lot. Here, it is like "or more," so "over x measurement." It is very broad, very flexible, and very useful. So now you know: * Directions go before the measurement of distance. * The word for measuring usually goes after the number. * How to describe things in given places. The majority of the 山海經 is written this way. Now that you know the basic structures, I strongly recommend [https://ctext.org/shan-hai-jing using it as a starter text]. ==Correspondence Table== This is a conversion table for length and weight as promulgated in 營造尺庫平制 during the Qing dynasty, in 1908. This is not quite equivalent to what you see prior, but it is a decent enough approximation for your purposes. {| class="wikitable" |+ Length ! Measure !! Qing standard !! Metric !! Imperial |- ! scope="row" | 丈 | 10 尺 || 3.2 m || 10.499 ft |- ! scope="row" | 尺 | 10 寸 || 32 cm || 12.598 in |- ! scope="row" | 寸 | 10 分 || 3.2 cm || 1.260 in |- ! scope="row" | 分 | — || 3.2 mm || 0.126 in |} {| class="wikitable" |+ Weight ! Measure !! Qing standard !! Metric !! Imperial |- ! scope="row" | 斤 | 16 兩 || 596.816 g || 1.316 lb |- ! scope="row" | 兩 | 10 錢 || 37.301 g || 1.316 oz |- ! scope="row" | 錢 | 10 分 || 3.7301 g || 0.132 oz |} ==Exercise== [[File:Stamp of Indonesia - 2008 - Colnect 385155 - Holy Days - Celebrations Chinese New Year.jpeg|thumb|200px|<u>印度尼西亞</u>之蓋印有鼠焉]] I have some animals next to emoji here. Think of their size and weight, and write it down. * 🐀 鼠 * 🐂 牛 * 🐅 虎 * 🐇 兔 * 🐉 龍 * 🐍 蛇 * 🐎 馬 * 🐐 羊 * 🐒 猴 * 🐓 雞 * 🐕 犬 * 🐖 豕 How about writing it like this? <blockquote> 豕重幾何?曰:重百斤。 </blockquote> I think you can do it! How about you try writing about that field with grains we thought of before, now knowing how to express distance and how to describe something being somewhere? Do you recognise this order? What do you think they are? ==References== * 《營造尺庫平制》 * 《山海經》 * 《清稗類鈔》 * 《蘭室秘藏》 * 《聊齋》 * Pulleyblank, E. G. (2000). Outline of classical Chinese grammar (Repr). UBC Press. 0htxl8u3sptd1deaonbohdw2xbe6c5l User:Surajshinde2005/Semiconductor Devices and Their Applications 2 486818 4679896 2026-11-04T06:51:42Z Raghav3434 3629927 Created page with "tyty" 4679896 wikitext text/x-wiki tyty 2svnvmwii70i90nm8fi1mrkp2g4lnrq 4679897 4679896 2026-11-04T06:53:12Z NDG 3510220 Requesting deletion ([[:m:Special:MyLanguage/User:TenWhile6/XReport|XReport]] v3.1d) 4679897 wikitext text/x-wiki <noinclude>{{delete|1=Test page <small>[[:m:Special:MyLanguage/User:TenWhile6/XReport|XReport]]</small>}}</noinclude> tyty 7rl4tlctrxktkp453hrlllmp77iyyv7 User:Surajshinde2005/Semiconductor Devices and Their applications 2 486819 4679911 2026-11-04T07:34:24Z ~2026-58561-14 3630362 Created page with "Materials in nature generally fall into two categories regarding electricity: '''conductors''' (like copper and gold), which let electrons flow freely, and '''insulators''' (like glass and rubber), which block electron flow completely. Semiconductors, most notably '''Silicon''' and '''Germanium''', sit right in the middle. In their pure state, they are poor conductors. However, their true power is unlocked through a process called '''doping'''—intentionally introducin..." 4679911 wikitext text/x-wiki Materials in nature generally fall into two categories regarding electricity: '''conductors''' (like copper and gold), which let electrons flow freely, and '''insulators''' (like glass and rubber), which block electron flow completely. Semiconductors, most notably '''Silicon''' and '''Germanium''', sit right in the middle. In their pure state, they are poor conductors. However, their true power is unlocked through a process called '''doping'''—intentionally introducing specific impurities into the crystal lattice to alter their electrical properties: 1) '''N-type doping:''' Introduces extra electrons (negative charge carriers) '''2) P-type doping:''' Creates a deficit of electrons, known as "holes" (acting as positive charge carriers). rsjcjf38ldmcunpfntp46y9btnybyyc User:Anshugk 2 486820 4679912 2026-11-04T07:39:01Z Anshugk 3630363 /* */ 4679912 wikitext text/x-wiki = ESP32 Capacitive Touch Pins = [[File:ESP32 Espressif ESP-WROOM-32 Dev Board.jpg|thumb|right|300px|ESP32 development board. Image source: Wikimedia Commons, CC0.]] == 1. Introduction == The ESP32 is a low-cost, low-power microcontroller that provides several built-in features, including Wi-Fi, Bluetooth, GPIO, ADC, PWM, and capacitive touch sensing. One of the useful features of the ESP32 is its built-in capacitive touch sensor. It allows the microcontroller to detect human touch without requiring a traditional mechanical push button. A capacitive touch pin can detect when a finger touches or approaches a conductive surface connected to the pin. This feature is useful for developing touch-sensitive switches, control panels, interactive devices, and smart home applications. Unlike a mechanical button, a capacitive touch sensor does not require physical movement or pressing of electrical contacts. Instead, it detects changes in capacitance. == 2. What is a Capacitive Touch Sensor? == A capacitive touch sensor is an electronic sensing device that detects changes in capacitance when a conductive object, such as a human finger, comes near or touches a sensing surface. Capacitance is the ability of an object or system to store electrical charge. The human body naturally has electrical capacitance. When a finger touches a conductive pad connected to an ESP32 touch pin, the effective capacitance of the sensing system changes. The ESP32 detects this change and produces a corresponding sensor reading that can be processed by a program. For example: * When nobody touches the sensor pad, the ESP32 reads the normal capacitance value. * When a finger touches the pad, the capacitance changes. * The ESP32 detects this change. * The program identifies the touch and performs a predefined operation, such as turning ON an LED. == 3. Working Principle of ESP32 Capacitive Touch Pins == The ESP32 contains an internal capacitive touch sensing circuit. It measures changes in the electrical characteristics of a sensing pad connected to a touch-enabled GPIO. The working process is explained below: # A conductive touch pad is connected to an ESP32 capacitive touch pin. # The ESP32 continuously measures the electrical characteristics of the sensing pad. # When a finger approaches or touches the pad, the effective capacitance changes. # The internal touch sensing circuit detects this change. # The ESP32 produces a different sensor reading. # The program compares the sensor reading with a predefined threshold. # If the reading indicates a touch, the ESP32 performs the programmed action. === Capacitance Formula === The basic capacitance equation for a parallel-plate capacitor is: <math>C = \frac{\varepsilon A}{d}</math> Where: * C = Capacitance * ε = Permittivity of the dielectric material * A = Area of the plates * d = Distance between the plates A human finger changes the effective capacitance of the touch sensing system. The ESP32 detects this variation using its internal touch sensing peripheral. === Capacitive Touch Sensor Diagram === [[File:Capacitive sensor scheme.svg|thumb|center|400px|Basic capacitive sensor working principle. Source: Wikimedia Commons, public domain.]] == 4. Capacitive Touch Pins Available on ESP32 == The classic ESP32 microcontroller provides ten capacitive touch sensing channels, named T0 to T9. The following table shows their corresponding GPIO numbers. {| class="wikitable" |+ ESP32 Capacitive Touch Pins ! Touch Channel !! GPIO Number !! Description |- | T0 || GPIO 4 || Touch sensing pin |- | T1 || GPIO 0 || Touch sensing pin |- | T2 || GPIO 2 || Touch sensing pin |- | T3 || GPIO 15 || Touch sensing pin |- | T4 || GPIO 13 || Touch sensing pin |- | T5 || GPIO 12 || Touch sensing pin |- | T6 || GPIO 14 || Touch sensing pin |- | T7 || GPIO 27 || Touch sensing pin |- | T8 || GPIO 33 || Touch sensing pin |- | T9 || GPIO 32 || Touch sensing pin |} '''Important:''' These pin numbers apply to the original ESP32. Other ESP32 variants, such as ESP32-S2 and ESP32-S3, have different touch pin assignments. Always check the datasheet of the selected microcontroller. == 5. Internal Architecture of Capacitive Touch Sensing == The ESP32 has a dedicated touch sensing peripheral that measures capacitance changes without requiring an external touch sensor IC. The main functional blocks are: * '''Touch sensing GPIO:''' Provides the electrical connection to the external sensing pad. * '''Internal sensing circuit:''' Detects changes in capacitance. * '''Measurement circuit:''' Converts capacitance changes into measurable readings. * '''Controller:''' Processes touch measurements. * '''Software application:''' Compares measurements with a threshold and performs the required operation. === Block Diagram === <pre> Human Finger | v Conductive Touch Pad | v ESP32 Touch GPIO | v Capacitive Touch Circuit | v Measurement Unit | v ESP32 Controller | v Program / Threshold | v Output Action | +----+----+ | | v v LED Buzzer </pre> == 6. Hardware Requirements == The following components are required to perform a basic ESP32 capacitive touch experiment. {| class="wikitable" ! Component !! Quantity !! Purpose |- | ESP32 Development Board || 1 || Main microcontroller |- | LED || 1 || Indicates touch detection |- | Resistor (220–330 Ω) || 1 || Limits LED current |- | Jumper Wires || As required || Circuit connections |- | Breadboard || 1 || Circuit assembly |- | Conductive Touch Pad || 1 || Detects finger touch |- | USB Cable || 1 || Programming and power supply |} == 7. Circuit Connections == For this experiment, GPIO 4 is used as the capacitive touch input, and GPIO 2 is used to control an LED. {| class="wikitable" ! ESP32 Pin !! Component !! Connection |- | GPIO 4 || Touch Pad || Connected to conductive touch pad |- | GPIO 2 || LED || Connected through a current-limiting resistor |- | GND || LED || Connected to the LED ground terminal |} === Circuit Connection Diagram === <pre> ESP32 +-------------+ | | | GPIO 4 |------ Touch Pad | | | GPIO 2 |------ Resistor ------ LED | | | GND -----------------------------+ | | +-------------+ </pre> === Circuit Working === # Connect the touch pad to GPIO 4. # Connect the LED to GPIO 2 through a suitable current-limiting resistor. # Connect the other terminal of the LED to GND. # Connect the ESP32 to a computer using a USB cable. # Upload the MicroPython program. # Touch the sensing pad and observe the LED response. The LED turns ON when the program detects a touch and turns OFF when the touch is released. == 8. MicroPython Programming for ESP32 Capacitive Touch == MicroPython provides a built-in class called <code>TouchPad</code> in the <code>machine</code> module to access capacitive touch functionality on supported ESP32 boards. The following functions are commonly used: {| class="wikitable" ! Function !! Description |- | <code>TouchPad(Pin(x))</code> || Creates a touch sensor object for a supported GPIO. |- | <code>read()</code> || Reads the current touch sensor value. |- | <code>config(value)</code> || Configures the touch detection threshold on supported implementations. |} === Basic Syntax === <syntaxhighlight lang="python"> from machine import Pin, TouchPad touch = TouchPad(Pin(4)) value = touch.read() print(value) </syntaxhighlight> '''Note:''' On the classic ESP32, the touch reading generally decreases when a finger touches the sensing pad. The exact reading depends on the board and surrounding environment. == 9. Practical Experiment: Controlling an LED Using a Capacitive Touch Pin == '''Aim:''' To interface a capacitive touch sensor with ESP32 and control an LED using MicroPython. '''Objective:''' To understand how the ESP32 detects human touch and controls an output device based on the sensor reading. === Program === <syntaxhighlight lang="python"> from machine import Pin, TouchPad import time # Configure touch sensor touch = TouchPad(Pin(4)) # Configure LED led = Pin(2, Pin.OUT) # Read initial sensor value baseline = touch.read() # Set touch threshold threshold = baseline * 0.70 print("Baseline:", baseline) print("Threshold:", threshold) while True: value = touch.read() print("Touch Value:", value) if value < threshold: led.on() print("Touch Detected - LED ON") else: led.off() print("No Touch - LED OFF") time.sleep(0.1) </syntaxhighlight> === Program Explanation === {| class="wikitable" ! Code !! Explanation |- | <code>from machine import Pin, TouchPad</code> || Imports the required classes. |- | <code>import time</code> || Imports the time module. |- | <code>TouchPad(Pin(4))</code> || Initializes GPIO 4 as a touch sensor. |- | <code>Pin(2, Pin.OUT)</code> || Configures GPIO 2 as an output pin. |- | <code>baseline = touch.read()</code> || Reads the initial sensor value without touching the pad. |- | <code>threshold = baseline * 0.70</code> || Sets an example touch detection threshold. |- | <code>while True:</code> || Repeats the program continuously. |- | <code>touch.read()</code> || Reads the current touch sensor value. |- | <code>if value &lt; threshold:</code> || Checks whether the measured value indicates a touch. |- | <code>led.on()</code> || Turns ON the LED. |- | <code>led.off()</code> || Turns OFF the LED. |- | <code>time.sleep(0.1)</code> || Adds a short delay between readings. |} '''Important:''' The 70% threshold is an example, not a universal value. Actual readings depend on the touch pad, wiring, board, and environment. Observe the readings both with and without touching the pad and adjust the threshold accordingly. For reliable applications, averaging and filtering can be used to reduce false touch detections. == 10. Understanding Touch Sensor Readings == The ESP32 produces numerical readings that represent the measured capacitance characteristics of the touch pad. For the classic ESP32 using MicroPython, a lower reading generally indicates that the touch pad has been touched. An illustrative example is shown below. {| class="wikitable" ! Sensor Condition !! Example Reading !! Result |- | No touch || 800 || Normal condition |- | Finger approaching || 650 || Capacitance changing |- | Finger touching || 400 || Touch detected |- | Finger released || 800 || Normal condition restored |} '''Note:''' These are hypothetical values for understanding the concept. Actual readings can be significantly different. === Graphical Representation === <pre> Touch Sensor Reading 800 | No Touch No Touch | 650 | Approaching | 400 | Touch | +----------------------------> Time Higher value = No touch Lower value = Touch </pre> == 11. Difference Between Capacitive Touch Sensor and Mechanical Push Button == {| class="wikitable" ! Capacitive Touch Sensor !! Mechanical Push Button |- | Detects changes in capacitance. || Detects physical contact between electrical contacts. |- | No moving parts are required. || Contains mechanical moving parts. |- | Can detect touch without pressing. || Requires physical pressing. |- | Generally has less mechanical wear. || Mechanical contacts may wear over time. |- | Requires touch sensing circuitry. || Can be connected directly to a GPIO with suitable circuitry. |- | Can be designed with a smooth touch surface. || Usually requires a physical button. |} == 12. Applications of ESP32 Capacitive Touch Pins == Capacitive touch pins are useful in many embedded systems and IoT applications. === 12.1 Touch-Sensitive Switches === Capacitive touch sensors can replace conventional switches in electronic devices. A user can touch a conductive surface to turn an LED or an appliance control system ON and OFF. === 12.2 Smart Home Automation === Touch-sensitive control panels can be developed to control lights, fans, and other home automation devices. === 12.3 Touch-Based Doorbells === A touch pad connected to an ESP32 can detect a visitor's touch and activate a buzzer or notification system. === 12.4 Interactive Electronic Projects === Capacitive touch pins can be used in educational projects, interactive displays, and electronic control panels. === 12.5 Musical Instruments === Multiple touch pads can be programmed to produce different musical notes or sound effects when touched. === 12.6 Touch-Based Lighting Systems === A touch sensor can be used to switch lights ON or OFF without a mechanical switch. === Real-World Example === [[File:Capacitive touch buttons.jpg|thumb|center|400px|Capacitive touch buttons on a household appliance control panel. Source: Wikimedia Commons.]] == 13. Advantages of ESP32 Capacitive Touch Pins == * No mechanical button is required. * No moving parts are involved. * Simple hardware interfacing. * Supports touch-based user interaction. * Can be integrated directly with the ESP32. * Suitable for compact electronic designs. * Can detect changes caused by a finger approaching the sensing pad. * Supports multiple touch sensing channels on the classic ESP32. == 14. Limitations of Capacitive Touch Pins == * Sensor readings can change due to environmental conditions. * Moisture and humidity may affect touch detection. * Electrical noise can cause incorrect readings. * Proper threshold calibration is required. * Touch detection can be affected by pad size and wiring. * Some GPIO pins have additional boot configuration or peripheral functions. * Different ESP32 variants support different touch sensing features. '''Design consideration:''' Espressif documents limitations related to conducted susceptibility testing of the original ESP32 touch sensor. Applications requiring high reliability should be tested under their intended operating conditions. == 15. Important Precautions While Using ESP32 Touch Pins == # Always check whether the selected GPIO supports capacitive touch sensing. # Use the correct pin numbers for the ESP32 variant. # Avoid excessively long touch sensor wires because they can introduce unwanted capacitance and noise. # Calibrate the sensor before setting a threshold. # Keep the touch pad away from strong electrical noise sources. # Avoid using GPIO pins that may interfere with boot configuration unless their requirements are understood. # Use suitable filtering or averaging for stable touch detection. # Never apply voltages higher than the ESP32 GPIO operating limits. == 16. Conclusion == The ESP32 capacitive touch sensor is a useful built-in feature that allows touch-based interaction without using mechanical switches. It works by detecting changes in capacitance when a finger approaches or touches a conductive sensing pad. Using the MicroPython <code>TouchPad</code> class, developers can easily read touch sensor values and control output devices such as LEDs and buzzers. This feature makes ESP32 suitable for developing smart home systems, touch-sensitive switches, interactive control panels, and other IoT-based applications. == 17. Frequently Asked Questions (FAQs) == '''Q1. How many capacitive touch pins are available on the classic ESP32?''' The classic ESP32 provides 10 capacitive touch channels, from T0 to T9. '''Q2. Which MicroPython class is used to access touch pins?''' The <code>TouchPad</code> class from the <code>machine</code> module is used. '''Q3. Does a capacitive touch sensor require a mechanical button?''' No. It detects changes in capacitance and does not require mechanical movement. '''Q4. What happens to the sensor reading when a finger touches the classic ESP32 touch pad?''' The reading generally decreases when the touch pad is touched. '''Q5. Can an LED be controlled using a capacitive touch pin?''' Yes. A MicroPython program can detect touch and control an LED through a normal GPIO output pin. '''Q6. Why is threshold calibration required?''' Because sensor readings vary depending on the board, touch pad, wiring, and environmental conditions. '''Q7. Can ESP32 capacitive touch pins be used in home automation?''' Yes. They can be used to develop touch-sensitive switches and control panels for smart home applications. == 18. References and Further Reading == # [https://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf ESP32 Technical Datasheet - Espressif Systems]. Refer to the Touch Sensor section and capacitive-sensing GPIO table. # [https://www.espressif.com/sites/default/files/documentation/esp32_technical_reference_manual_en.pdf ESP32 Technical Reference Manual - Espressif Systems]. Refer to the on-chip sensors and analog signal processing chapter. # [https://docs.micropython.org/en/latest/esp32/quickref.html MicroPython ESP32 Quick Reference]. Refer to the Capacitive Touch section for the TouchPad class and programming examples. # [https://docs.micropython.org/en/latest/library/machine.TouchPad.html MicroPython TouchPad Documentation]. # [https://commons.wikimedia.org/wiki/File:ESP32_Espressif_ESP-WROOM-32_Dev_Board.jpg Wikimedia Commons - ESP32 Development Board]. # [https://commons.wikimedia.org/wiki/File:Capacitive_sensor_scheme.svg Wikimedia Commons - Capacitive Sensor Scheme]. # [https://commons.wikimedia.org/wiki/File:Capacitive_touch_buttons.jpg Wikimedia Commons - Capacitive Touch Buttons]. == End of Chapter == b5o9mp8c0097qgfm39kofarkt3y1eci General Literary Chinese from Scratch/Exploring the World of Mountains and Seas 0 486821 4679913 2026-11-04T07:47:03Z Shira the Mogul 3560559 Created page with "Near the end of Unit 1, I introduced you to the ''Classic of Mountains and Seas'' 山海經, an ancient atlas of sorts used by Chinese people to find jade, metal, animals, and other resources. Today, it is known for its fairly odd descriptions of the world, the people who used it no longer able to tell us what was being described. Reconstructing the terrain and what animals were described is very difficult, but it is a very fun read, especially when trying to draw and co..." 4679913 wikitext text/x-wiki Near the end of Unit 1, I introduced you to the ''Classic of Mountains and Seas'' 山海經, an ancient atlas of sorts used by Chinese people to find jade, metal, animals, and other resources. Today, it is known for its fairly odd descriptions of the world, the people who used it no longer able to tell us what was being described. Reconstructing the terrain and what animals were described is very difficult, but it is a very fun read, especially when trying to draw and comprehend what it contains. It is a very simple text with short, sweet sentences, making it perfect for your level! You can read the text online [https://ctext.org/shan-hai-jing here]. ==Text== Remember what you saw in Unit 1 and give this a look: <blockquote> 又東三百里,曰堂庭之山,多棪木,多白猿,多水玉,多黃金。 </blockquote> What do you think 多 must mean here? Additionally, when you see 曰堂庭之山, combine your understanding of 曰 and 之! You can likely read entries like these without much fear: <blockquote> 又東四百里,曰句餘之山,無草木,多金玉。<br> 又東五百里,曰咸陰之山,無草木,無水。 </blockquote> How about you try to draw them? Some items in this book are quite culturally important to ancient Chinese people. For example, the Ruo River 弱水 is a mythical river said to have existed on Mount Kunlun 昆侖: <blockquote> 北五十里,曰勞山,多茈草。弱水出焉,而西流注于洛。 </blockquote> You see the structure 出焉 here. Considering your understanding of 焉 from Unit 1, what do you think 出 must mean here? TBC - mythical creatures... ==Comments== While the book is commonly seen as a curiosity today, it is important to remember that this atlas was very valuable to many people back when it was still in use. ==References== {{BookCat}} 2les3xj5y7fmeebv1l06ramee5p7g15 4679914 4679913 2026-11-04T07:47:25Z Shira the Mogul 3560559 4679914 wikitext text/x-wiki Near the end of Unit 1, I introduced you to the ''Classic of Mountains and Seas'' 山海經, an ancient atlas of sorts used by Chinese people to find jade, metal, animals, and other resources. Today, it is known for its fairly odd descriptions of the world, the people who used it no longer able to tell us what was being described. Reconstructing the terrain and what animals were described is very difficult, but it is a very fun read, especially when trying to draw and comprehend what it contains. It is a very simple text with short, sweet sentences, making it perfect for your level! You can read the text online [https://ctext.org/shan-hai-jing here]. ==Text== Remember what you saw in Unit 1 and give this a look: <blockquote> 又東三百里,曰堂庭之山,多棪木,多白猿,多水玉,多黃金。 </blockquote> What do you think 多 must mean here? Additionally, when you see 曰堂庭之山, combine your understanding of 曰 and 之! You can likely read entries like these without much fear: <blockquote> 又東四百里,曰句餘之山,無草木,多金玉。<br> 又東五百里,曰咸陰之山,無草木,無水。 </blockquote> How about you try to draw them? Some items in this book are quite culturally important to ancient Chinese people. For example, the Ruo River 弱水 is a mythical river said to have existed on Mount Kunlun 昆侖: <blockquote> 北五十里,曰勞山,多茈草。弱水出焉,而西流注于洛。 </blockquote> You see the structure 出焉 here. Considering your understanding of 焉 from Unit 1, what do you think 出 must mean here? TBC - mythical creatures... ==Comments== While the book is commonly seen as a curiosity today, it is important to remember that this atlas was very valuable to many people back when it was still in use. ==References== * Zhongquan, M. (Ed.) (with Liu, X., & Liu, X.). (2018). 山海经 [Shānhǎijīng] (Simplified Chinese ed.). 万卷出版公司 [Wanjuan Publishing Company]. {{BookCat}} rkp4wxmg2x4w4rqafs5c91yyf1he23y User:Vision Robotics/sandbox/Event-Driven Robotic Vision 2 486822 4679920 2026-11-04T08:06:01Z Vision Robotics 3630109 Created page with "h" 4679920 wikitext text/x-wiki h 4ni88dkindqjjb63hk6ic0eltmdwlmd User:Yuvraj.444u/sandbox/The Living Machine 2 486823 4679922 2026-11-04T08:07:30Z Yuvraj.444u 3630369 Created blank page 4679922 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 User:Mohit Jakhar07/sandbox 2 486824 4679925 2026-11-04T08:10:04Z Mohit Jakhar07 3630385 added title 4679925 wikitext text/x-wiki <nowiki>''</nowiki>Ethical Challenges of Autonomous Robots: Safety, Accountability, Privacy and Legal Compliance.<nowiki>''</nowiki> 8838q1mjq956dv299dbiruw5ic6v753 User talk:Kaw57 3 486825 4679932 2026-11-04T09:03:11Z MathsScienceNerd1 3626296 Welcoming user with {{Welcome}} 4679932 wikitext text/x-wiki ==Welcome!== {| style="background:white; border:1px solid #abd5f5;; padding:0px; border-spacing:0px; color: #000000;" ! style="background:#d0e5f5; color: #000000;" | [[Wikibooks:Welcome|Getting started]] with Wikibooks |- | style="padding:5px;" | * Wikibooks is a collection of open-source textbooks. Find out [[WB:WIW|what this means]]. * To sign your name (on discussion pages), use four tildes, like this: &#126;&#126;&#126;&#126; * Learn how to [[Using Wikibooks|use Wikibooks]] and learn more about the community. * [[WB:CCO|Explore]], [[Wikibooks:Be bold|be bold]], and have fun! |} If you have any questions, you can ask in the [[Wikibooks:Reading room/Assistance|assistance reading room]] or possibly contact me personally. [[User:MathsScienceNerd1|MathsScienceNerd1]] ([[User talk:MathsScienceNerd1|discuss]] • [[Special:Contributions/MathsScienceNerd1|contribs]]) 09:03, 4 November 2026 (UTC) e3zd9hfux9jrbec03oz3dx117pnudjb