I am a contributor of theNorthern Min language and the current AI software is unable to recognize several of the diacritic letters of the pages, for example,THIS PAGE.
At present contributors of the Northern Min language are needing to manually type out this text and each page takes approximately thirty minutes to complete. This means it would take 19,500 minutes (325 hours) to type out the entire New Testament of this language (650 pages approx).
If the AI can be enhanced to correctly recognize those texts, then each page would only take 5 seconds to complete and therefore the entire New Testament could be completed in 3,250 seconds (54 minutes), thus a time saving of 99%.
The AI software only needs to recognize these additional Special Characters (the ones highlighted in Red are currently unrecognizable by the AI software):
Acute: á í ú é ó á̤ é̤ ó̤ ṳ́ Á Í Ú É Ó Á̤ É̤ Ó̤ Ṳ́
Circumflex: â î û ê ô â̤ ê̤ ô̤ ṳ̂ Â Î Û Ê Ô Â̤ Ê̤ Ô̤ Ṳ̂
I may be too ignorant here, but the software is optical character recognition (OCR), which I don't think uses AI. There are multiple OCR scanning solutions here at Wikisource. If you open up a page to edit (e.g.), then you should see a button that says "Transcribe text" which has a drop-down menu that allows you to use three different OCR tools, which will yield different results. Are all of them equally bad at transcribing Northern Min? One thing thatcould help is changing thepage's information so that the language ismnp (note that only admins can do this). Unfortunately,mnp is not on the list currently. So I think step one is to file a bug atphab: asking formnp to be added to the list of languages available here.Then change the page information on various pages tomnp and see if that helps with the OCR scans. If it does, then the solution is more language changes to make transcription more efficient. If it does not, then we may need to come up with another solution. —Justin (koavf)❤T☮C☺M☯11:17, 2 January 2025 (UTC)[reply]
I tried to transcribe using all three OCR Egnines (Google Cloud Vision OCR, Tesseract OCR, and Transkribus OCR). Of the three, Google Cloud Vision OCR is the most accurate and can transcribe macrons: ā ī ū ē ō Ā Ī Ū Ē Ō and also Breves: ă ĭ ŭ ĕ ŏ Ă Ĭ Ŭ Ĕ Ŏ.
However Double Macrons and diacritics with diaresis below, namely:
a̿ i̿ u̿ e̿ o̿ A̿ I̿ U̿ E̿ O̿
ā̤ ē̤ ō̤ ṳ̄ A̤̿ E̤̿ O̤̿ Ṳ̿
á̤ é̤ ó̤ ṳ́ Á̤ É̤ Ó̤ Ṳ́
ă̤ ĕ̤ ṳ̆ ŏ̤ Ă̤ Ĕ̤ Ṳ̆ Ŏ̤
à̤ è̤ ṳ̀ ò̤ À̤ È̤ Ṳ̀ Ò̤
â̤ ê̤ ô̤ ṳ̂ Â̤ Ê̤ Ô̤ Ṳ̂
a̤̿ e̤̿ o̤̿ ṳ̿ A̤̿ E̤̿ O̤̿ Ṳ̿
are still unable to be transcribed. The letters highlighted in red above are the letters that all three OCR's are currently unable to transcribe. --DaveZ123 (talk)01:57, 5 January 2025 (UTC)[reply]
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.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. Seethe SUL3 project page for more details and a timeline.
Updates for editors
On wikis withPageAssessments installed, you can nowfilter search results to pages in a given WikiProject by using theinproject: keyword. (These wikis: Arabic Wikipedia, English Wikipedia, English Wikivoyage, French Wikipedia, Hungarian Wikipedia, Nepali Wikipedia, Turkish Wikipedia, Chinese Wikipedia)[1]
One new wiki has been created: a Wikipedia inTigre (w:tig:)[2]
View all 35 community-submitted tasks that wereresolved last week. For example, there was a bug with updating a user's edit-count after making a rollback edit, which is now fixed.[3]
Updates for technical contributors
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 reroutingsome 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 theMediaWiki 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.Read more and share your thoughts about Toolforge UI.
For tool and library developers who use the OAuth system: The identity endpoint used forOAuth 1 andOAuth 2 returned a JSON object with an integer in itssub 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.[4]
Many wikis currently useCite CSS to render custom footnote markers in Parsoid output. Starting January 20 these rules will be disabled, but the developers ask you tonot clean up yourMediaWiki:Common.css 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.[5]
We’re happy to announce the launch ofWiki Loves Ramadan 2025, an annual international campaign dedicated to celebrating and preserving Islamic cultures and history through the power of Wikipedia. As an active contributor to the Local Wikipedia, you are specially invited to participate in the launch.
This year’s campaign will be launched for you to join us write, edit, and improve articles that showcase the richness and diversity of Islamic traditions, history, and culture.
To get started, visit thecampaign page for details, resources, and guidelines: Wiki Loves Ramadan 2025.
Addyour community here, and organized Wiki Loves Ramadan 2025 in your local language.
Whether you’re a first-time editor or an experienced Wikipedian, your contributions matter. Together, we can ensure Islamic cultures and traditions are well-represented and accessible to all.
Feel free to invite your community and friends too. Kindly reach out if you have any questions or need support as you prepare to participate.
Hi, I just ran into an abuse filter while trying to blank some user talk page vandalism[6][7]. Please either blank the talk page yourself or speedy delete it (no meaningful content). I didn't ask for speedy deletion right away, because many projects never delete user talk pages.
Going by the filter title, the action should just be "create" instead of "edit" (or you should change the title).
I recommend usinguser_rights instead ofuser_groups, that way you avoid false positives with crosswiki patrollers with global permissions.
If you want to keep the action "edit" instead of just page creations, I recommend adding namespace 2 and probably also 3 to the exempted name space, in order to avoid false positives like these[8][9]. Users should be allowed to blank their own user page or anything else in their own user space[10][11]
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
Administrators can mass-delete multiple pages created by a user or IP address usingExtension: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.[12]
Onwikis that use thePatrolled 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 usefilters on Recent Changes may need to update their filter settings.[13]
View all 31 community-submitted tasks that wereresolved 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 beenfixed.
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 byDiscussionTools, which is used on any regular talk page.The last group of wikis (Catalan Wikiquote, Wikimedia Finland, Goan Konkani Wikipedia, Kabyle Wikipedia, Portuguese Wikibooks, Wikimedia Sweden) will soon be contacted. If you have questions about this process, please pingTrizek (WMF) at your wiki.[14]
The latest quarterlyTechnical 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.
I am writing to you to let you know the annual review period for the Universal Code of Conduct and Enforcement Guidelines is open now. You can make suggestions for changes through 3 February 2025. This is the first step of several to be taken for the annual review.Read more information and find a conversation to join on the UCoC page on Meta.
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.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 and13 other questions to shape the technical direction for next year.
Updates for editors
iOS Wikipedia App users worldwide can now access apersonalized 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.
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 inSpecial:RecentChanges andSpecial:NewPages.[15]
Later this week, there will be a new warning for editors if they attempt to create a redirect that links to another redirect (adouble redirect). The feature will recommend that they link directly to the second redirect's target page. Thanks to the user SomeRandomDeveloper for this improvement.[16]
Wikimedia wikis allowWebAuthn-based second factor checks (such as hardware tokens) during login, but the feature isfragile and has very few users. The MediaWiki Platform team is temporarily disabling adding new WebAuthn keys, to avoid interfering with the rollout ofSUL3 (single user login version 3). Existing keys are unaffected.[17]
For developers that use theMediaWiki History dumps: The Data Platform Engineering team has added a couple of new fields to these dumps, to support theTemporary 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 themediawiki_user_history dump, theanonymous field will be renamed tois_anonymous. The changes will take effect with the next release of the dumps in February.[18]
This is a reminder that the first phase of the annual review period for the Universal Code of Conduct and Enforcement Guidelines will be closing soon. You can make suggestions for changes throughthe end of day, 3 February 2025. This is the first step of several to be taken for the annual review.Read more information and find a conversation to join on the UCoC page on Meta. After review of the feedback, proposals for updated text will be published on Meta in March for another round of community review.
Please share this information with other members in your community wherever else might be appropriate.
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.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.[19]
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.[20] You can now also insert<code> tags using a new toolbar button.[21] Thanks to user stjn for these improvements.
Help is needed to ensure thecitation generator works properly on each wiki.
(1) Administrators should update the local versions of the pageMediaWiki:Citoid-template-type-map.json to include entries forpreprint,standard, anddataset; Here are example diffs to replicatefor 'preprint' andfor 'standard' and 'dataset'.
(2.1) If the citoid map in the citation template used for these types of references is missing,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 updatesfor 'preprint' andfor 'standard' and 'dataset'. The new fields that may need to be supported arearchiveID,identifier,repository,organization,repositoryLocation,committee, andversionNumber.[22]
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Weekly highlight
The Product and Technology Advisory Council (PTAC) has publisheda draft of their recommendations for the Wikimedia Foundation's Product and Technology department. They have recommended focusing onmobile experiences, particularly contributions. They request communityfeedback 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 atT385346.[25]
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 outthe project page for more information.
View all 22 community-submitted tasks that wereresolved 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.[27]
Updates for technical contributors
Wikidatanow 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.[28]
The functiongetDescription 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.[29]
As part of the RESTBase deprecationeffort, the/page/related 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 "morelike" action API in MediaWiki, anda migration example is available. The MediaWiki Interfaces teamcan be contacted for any questions.[30]
In depth
The latest quarterlyLanguage 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 latestChart 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.
Hello everyone! Sometime ago I found theTemplate:New texts that was created years ago, but never used in this project. Would the community believe that it would be interesting to add this template in the main page? Inspired by @Koavf:, I've experimented a little at theSandbox, but I bet that someone here could create a more interesting visual for this template in the main page. Thanks,Erick Soares3 (talk)22:17, 11 February 2025 (UTC)[reply]
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Weekly highlight
Communities using growth tools can now showcase one event on theSpecial:Homepage 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 atSpecial:CommunityConfiguration. To learn more about this feature, please readthe Diff post, have a lookat the documentation, or contactthe Growth team.
Updates for editors
Highlighted talk pages improvements
Starting next week, talk pages at these wikis – Spanish Wikipedia, French Wikipedia, Italian Wikipedia, Japanese Wikipedia – will geta new design. This change was extensively tested as a Beta feature and is the last step oftalk pages improvements.[31]
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.[32]
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,an error message was displayed. As part of the work tomodernize 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 canhelp to update the localized versions. Thanks to user Msz2001 for these improvements.
A new filter has been added to theSpecial: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.[33]
Non-administrators can now check which pages are able to be deleted using theSpecial:Nuke tool. Thanks to user MolecularPilot for this and the previous improvements.[34]
View all 25 community-submitted tasks that wereresolved last week. For example, a bug was fixed in the configuration for the AV1 video file format, which enables these files to play again.[35]
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 theParsoid/Parser Unification project page.[36][37]
Developers of tools that run on-wiki should note thatmw.Uri is deprecated. Tools requiringmw.Uri must explicitly declaremediawiki.Uri as a ResourceLoader dependency, and should migrate to the browser nativeURL API soon.[38]
We’re excited to announce that the nextLanguage Community Meeting is happening soon,February 28th at 14:00 UTC! If you’d like to join, simply sign up on thewiki page.
This is a participant-driven meeting where we share updates on language-related projects, discuss technical challenges in language wikis, and collaborate on solutions. In our last meeting, we covered topics like developing language keyboards, creating the Moore Wikipedia, and updates from the language support track at Wiki Indaba.
Got a topic to share? Whether it’s a technical update from your project, a challenge you need help with, or a request for interpretation support, we’d love to hear from you! Feel free toreply to this message or add agenda items to the documenthere.
Also, we wanted to highlight that the sixth edition of the Language & Internationalization newsletter (January 2025) is available here:Wikimedia Language and Product Localization/Newsletter/2025/January. This newsletter provides updates from the October–December 2024 quarter on new feature development, improvements in various language-related technical projects and support efforts, details about community meetings, and ideas for contributing to projects. To stay updated, you can subscribe to the newsletter on its wiki page:Wikimedia Language and Product Localization/Newsletter.
We look forward to your ideas and participation at the language community meeting, see you there!
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
Administrators can now customize how theBabel feature creates categories usingSpecial:CommunityConfiguration/Babel. They can rename language categories, choose whether they should be auto-created, and adjust other settings.[39]
Thewikimedia.org 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 aswikibooks.org, now support dark mode when a reader is using that system setting.[40][41][42]
View all 30 community-submitted tasks that wereresolved 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.[44]
Meetings and events
The next Language Community Meeting is happening soon, February 28th at14: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, simplysign up on the wiki page.
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Updates for editors
All logged-in editors using the mobile view can now edit a full page. The "Edit full page" link is accessible from the "More" menu in the toolbar. This was previously only available to editors using theAdvanced mobile contributions setting.[45]
Interface administrators can now help to remove the deprecated Cite CSS code matching "mw-ref" from their localMediaWiki:Common.css. The list of wikis in need of cleanup, and the code to remove,can be found with this global search and inthis example, and you can learn more about how to help on theCSS migration project page. The Cite footnote markers ("[1]") are now rendered byParsoid, and the deprecated CSS is no longer needed. The CSS for backlinks ("mw:referencedBy") 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.[[File:MediaWiki.png]]) 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.[46] In contrast, transcluding a file description page (e.g.{{:File:MediaWiki.png}}) will now restrict edits to the page.[47]
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,[48] and respects cascading protection.[49]
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.[50]
Thepreviously 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 onGroup0 wikis this week. Seethe 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.[51]
View all 23 community-submitted tasks that wereresolved last week. For example, a bug was fixed with loading images in very old versions of the Firefox browser on mobile.[53]
@-jkb-,Ooswesthoesbes: This wiki may or may not need bureaucrats while not very big, so in order to keep them, please clear the backlogs and consider more nominations while I am open to this role with past experience onCommons. Or collective resignations of all bureaucrats? Either way, please act on.--Jusjih (talk)03:54, 8 March 2025 (UTC)[reply]
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.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 theSUL3 project which aims to improve how our unified login works, and to keep it compatible with ongoing changes to the web-browsers we use.[54][55]
The Wikipedia Apps Team is inviting interested users to help improve Wikipedia’s offline and limited internet use. After discussions inAfrika Baraza and the lastESEAP 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?Join the discussion or emailaramadan@wikimedia.org!
All wikis will be read-only for a few minutes on March 19. This is planned at14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks.
The latest quarterlyGrowth 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 canread more details about this change.
Hi there! Could someone with importer rights take inen:Index:Gille dubh ciar-dhubh.pdf and its pages throughSpecial:Import? Coming here because I believe there's no gaelic ws to host it. We're at some point in the near future going to delete that as out of scope (not in english), but we're waiting to see if first we can bring it where it belongs. (I'm an admin on enws.) Cheers, —Alien 3 3 312:58, 12 March 2025 (UTC)[reply]