This page is used for technical questions relating to the tools, gadgets, or other technical issues about Commons; it is distinguished from the main Village pump, which handles community-wide discussion of all kinds. The page may also be used to advertise significant discussions taking place elsewhere, such as on the talk page of a Commons policy. Recent sections with no replies for 30 days and sections tagged with {{Section resolved|1=--~~~~}} may be archived; for old discussions, see the archives; recent archives: /Archive/2024/11/Archive/2024/12.
I would also like to add that I feel demotivated and hopeless by the way the now archived thread linked above was handled. I asked for help and no one even bothered to answer "no, I won't help, do it yourself". The thread was left to die, without anyone giving a helping hand to bring the topic closer to some solution. I don't think that ignoring a problem makes it disappear. This was an unpleasant experience for me to collaborate this way. I hope someone reads this feedback and makes some use of it. Derbethtalk16:15, 18 November 2024 (UTC)[reply]
I'll flag it to the devs and see if they can do something about it. I'm sorry that @Derbeth had this unpleasant experience. I'll keep you posted about it, but please be aware that it might take some time. Sannita (WMF) (talk) 14:51, 19 November 2024 (UTC)[reply]
Thank you Sannita. I fully understand fixing bugs takes time. I just wish discussions here were more like "exchanging different opinions -> agreeing what to do -> doing", instead of "dissolving" without any conclusion, as I felt was the case with the topic I started in October. --Derbethtalk16:51, 19 November 2024 (UTC)[reply]
Yeah, I see. As I said, I'll try this time to get you a solution for it, instead of just disappearing. If you don't hear from me, you're free to ping me on my talk page about this bug. Sannita (WMF) (talk) 17:21, 19 November 2024 (UTC)[reply]
I wish that too. I think people did not engage exchanging different opinions -> because it's clear this needs to be fixed and people share the opinion that it needs to be fixed with it not being useful in regards to getting it fixed to write that. -> agreeing what to do for bugs people generally agree that it should be reported and fixed. Somebody should have asked to create a phab issue. -> doing this part is the key problem. Even major bugs like all interactive charts on Wikipedia being broken or Commons categories not showing on mobile are not getting fixed after timescales of 5 years to decades. I don't think complaining about this is enough anymore so I made concrete suggestions on how to fix this here. They could readily be discussed and implemented which would result in all technical issues being addressed more often and more quickly:
The commons category thing is not a case of insufficient resources. The graph thing is partially a resource problem, but that is hardly the only issue there and it would be a gross oversimplification to boil it down to just that. Some problems are resource problems, i would even say many problems on commons are resource problems, but not all problems are resource problems. Bawolff (talk) 21:09, 19 November 2024 (UTC)[reply]
Those were just examples. Meant to add a note that the hiding of categories on mobile doesn't even really require much resources but dropped it; this just makes it even worse. Add them already, what gives WMF the permission to just hide away this core useful data I wonder. It's not a simplification to say things are technical development capacity problems, it would be solved much faster with more thinking/development capacity or are we waiting for a new Internet protocol for it to be invented before it can be addressed? I was not describing "resource" problems, I was describing a lack of technical development...obviously increasing technical development would result in more technical issues getting fixed and faster. Prototyperspective (talk) 21:15, 19 November 2024 (UTC)[reply]
Sure, but i also think some of these problems are deciding what to do problems. No amount of technical resources will fix a problem if the underlying issue is we simply decided not to do it. Like the category thing in particular is pretty clearly not a case of WMF being too busy - its a trivial change. Its a product failure - there is a mismatch between what commons thinks is important and what that particular team thinks is important. If we want to fix that we need better communication not more people fixing bugs (there are other things where more people would be helpful). Bawolff (talk) 09:11, 20 November 2024 (UTC)[reply]
These were examples so ignore this example if it's a bad example. we simply decided not to do it we did not. its a trivial change which is one reason why I don't donate to WMF and think they're doing a bad job what that particular team thinks is important what team? we need better communication there have been Wishlist proposals and phabricator issues and it's the most-supported request in the technical needs survey. All WMF needs to do is listen a bit and/or engage in any of these venues. not more people fixing bugs I see a tiny fraction of usually quite useful proposals in meta:Category:Community Wishlist Survey results have been implemented so far and on phabricator it's an even more desolate situation. We need far more people fixing bugs. Prototyperspective (talk) 19:28, 20 November 2024 (UTC)[reply]
There are always going to be more tasks than people. Having more people does not mean they will neccesarily work on the things you want them to. Like if there is something everyone agrees needs to be worked, but is pushed for something higher priority - then yes, more people will help with that. If there is something nobody seems to intend to fix, more people won't help, because that is not going to change the intention. Bawolff (talk) 14:48, 25 November 2024 (UTC)[reply]
I wasn't saying anything to the contrary. Anyway, as a note the likelihood of particularly useful or needed issues/proposals getting implemented is higher with more developers working on issues and more development per dev. Moreover, if lots of issues like pesky bugs are worked on then there is more possibility for other devs to work on interesting features since the major bugs are already being taken care of. e.g. we can't innovate much if everyone is only busy fixing bugs. Prototyperspective (talk) 15:05, 25 November 2024 (UTC)[reply]
Dear fellow Wikimedians, here is one for the template experts, it regards the {{Licensed-FOP}} template. IMHO this edit has introduced two errors into the template by making it create unmatched/unbalanced {{...}} and <div>...</div>. I have tried to fix this in the two last edits ([1], [2]). Could you please check whether the template is now (more or less) correct again, or if I have overlooked or even introduced yet another error (in the latter case please take my apologies!)? Thank you very much for your help! Best, – Aristeas (talk) 20:34, 22 November 2024 (UTC)[reply]
Thank you for your input, JWilz12345! It’s the same with my own photos which use the template (example): the FoP is still displayed in a wrong way. The question is: Where is the problem in the code of the {{Licensed-FOP}} template? I think my two edits have fixed the syntax errors introduced by this edit. Maybe the current problems were not related to that, but to some other changes, e.g. to this one?
Thank you very much, Enhancing999! Now the template works perfectly again. The current (reverted) version is identical to the revision as of 21:16, 8 August 2024 by Jarekt. This confirms that the recent problems were introduced by this edit. In addition to the problems this edit introduced I also doubt whether the layout change made by that edit was really necessary – the additonal left margin may look nice in some contexts, but looks irritating in some other contexts. Therefore I would ask that everybody who wants to change the layout of such widespread templates should discuss this before with other users and then tests the changes first befor deploying them. Thank you – Aristeas (talk) 10:04, 26 November 2024 (UTC)[reply]
Hello everyone, first of all, sorry for the inconvenience. The reason for my contribution was that {{Licensed-FOP}} looks the same as {{Licensed-PD}}. Unfortunately, I could not use the solution there because it would cause problems with {{Self}}. I thought I had found the solution with the <div>-function. But apparently not. I have also reset {{Licensed-TOO}}. I have put the process on my to-do list and will be continue working on it in my user-namespace. --Labant (talk) 14:36, 27 November 2024 (UTC)[reply]
Especially when it comes to uploading larger files, the error "Could not acquire lock. Somebody else is doing smth. with that file." occurs. It is frustrating when there are many attempts needed to upload a larger file. The error occurs with the Upload Wizard and th chunked upload. It's been already around for several days.
Thank you! This solves it. I think there were also some templates that display image despite that the file is an audio but I can't find them anymore and think some of these change once structured data is added to the file which can take some time (but not all of them). So this may also be useful it various places. Prototyperspective (talk) 15:04, 2 December 2024 (UTC)[reply]
You can get the mime type via Lua reference manual - File metadata. But it doesn't seem that MediaWiki's internal concept of mediatype (image/video/application etc, that the search etc depend for categorising these) is exposed through that endpoint. Then again, this is a very internal definition and concept. —TheDJ (talk • contribs) 14:31, 5 December 2024 (UTC)[reply]
@YanikB: I took the comment as the file would not display. I added the sodipodi and inkscape namespace declarations, so the file now displays. The file should have had the namespace declarations, it used to display on Commons, but in April 2024 the Commons SVG renderer started rejecting noncompliant SVG files. There are probably thousands of such files on Commons. Glrx (talk) 02:29, 28 November 2024 (UTC)[reply]
Hi there, the original content producer of these videos has noticed a deterioration in the sound quality of the videos there, both old and new. I can hear a drop in the audio quality from the files uploaded.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
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 HTTPS Browser Recommendations page for more-detailed information. All modern operating systems and browsers are always able to reach Wikimedia projects. [3]
Starting December 16, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: arwiki, cawiki, frwiki, mediawikiwiki, orwiki, wawiki, wawiktionary, wikidatawiki, zhwiki. This is done as part of StructuredDiscussions deprecation work. If you need any assistance to archive your page in advance, please contact Trizek (WMF). [4]
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 on Testwiki and read the November project update for more details.
View all 23 community-submitted tasks that were resolved last week. For example, a bug with the "Download as PDF" system was fixed. [5]
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 this list. In addition, review the updated documentation to learn how to adjust the tools. Join the discussions on the project talk page or in the dedicated thread on the Wikimedia Community Discord server (in English) for support and to share feedback.
scale(<sx> [<sy>]), which specifies a scale operation by sx and sy. If <sy> is not provided, it is assumed to be equal to <sx>
Given that, the images are valid. Anyone has an authoritative SVG spec saying that different scaling factors for X and Y are invalid? Taylor 49 (talk) 23:31, 3 December 2024 (UTC)[reply]
The files are legitimate, so they should not need to be fixed. Fixing them is also problematic because the support for font-stretch="condensed" (the practical effect of the nonuniform scaling) is poor. Also, Commons does not support textLength.
There was an involved discussion about this problem a long time ago, but I could not find it. I also did not find something on Phabricator, so a Phabricator issue should be started. Someone can check whether this bug is already fixed in later versions of librsvg.
aufBuchen banner with the forest behind somewhat visible
When I upload and download a JPG file with the XMP.Attribution Name set to First Last <first.last@provider.tld>, Wikimedia Commons, for some reason, omits the space char between Last and < in the "When re-using this work, please credit" field in the Metadata section. This is the only name/email address combination that renders incorrectly in this section. So a bit odd really.
The given thumbnail provides an example. A small but not insignificant bug. I also searched the Village Pump archives but could not find any reference to this particular problem. Best, RobbieIanMorrison (talk) 21:22, 4 December 2024 (UTC)[reply]
I can confirm that this very minor bug exists. In the file in the field "author" there is ordinary space $20 followed by ordinary less-than-sign $3C. However in the field "please credit" there is ordinary space $20 folowed by a HTML-encoded less-than-sign. Taylor 49 (talk) 21:58, 4 December 2024 (UTC)[reply]
it's probably because it can be html, and it does some sort of normalisation on it. These parts of the MediaWiki code tend to be rather obscure. —TheDJ (talk • contribs) 14:13, 5 December 2024 (UTC)[reply]
Speaking as a programmer, it is usually worth fixing bugs. An artifact that is brushed aside as trivial may well indicate a more significant problem. And I would also argue that image metadata should be faithfully replicated in all cases. RobbieIanMorrison (talk) 07:33, 7 December 2024 (UTC)[reply]
I'm trying to help UN FAO upload some maps to Commons but I'm getting an error I've never seen before, the error happens when I try to upload the SVG files, does anyone know what the issue is and can someone suggest steps to fix them? I'm not very technical so a vague answer isn't really going to help a lot :)
The error message is maybe 20 pages long so I'll just copy the start of it in below.
A data URL allows arbitrary content. MediaWiki wants to limit that content, so it only accepts a limited number of data URL mimetypes. The mimetype is not specified in the data URL, so MediaWiki will reject the upload.
The element is probably trying to include a bitmap image. Inserting the appropriate mimetype between the colon and semicolon should fix the problem. Acceptable mimetypes are image/jpeg or /image/png.
Hi Glrx thanks very much for the technical explanation, unfortunately I'm far too much of a muggle to work out how to use it. Do you have a suggestion of which program to use and what buttons to press to resolve this? Thanks again, John Cummings (talk) 08:34, 6 December 2024 (UTC)[reply]
Use a text editor. Search for href="@data:. then add the appropriate mimetype after the colon and before the semicolon. Save the file. Then open the file in a browser to see that it displays correctly (Windows: locate file in the File explorer; then right click and open with Chrome/Edge/Firefox/whatever). If the file is good, then upload the file to Commons.
I'd like to sort audio files not by recency or relevance but by duration (maybe filesize would also work as a proxy for that). Is that possible somehow? I'd like to use it in a category of spoken Wikipedia audios for example to be able to choose between a very long or a shorter audio. It would probably be useful also for many other kinds of applications. Prototyperspective (talk) 16:39, 5 December 2024 (UTC)[reply]
Image duration is not an indexed field in the database I believe. It's only in the db's metadata structure of a file's record, which makes it difficult to query over a collection of files. —TheDJ (talk • contribs) 10:42, 6 December 2024 (UTC)[reply]
Thanks, that's helpful. However, that's just the filesize, not the duration and I'm looking for something that can be used in the UI (integrated into MediaSearch or SpecialSearch). Strange if it's not in the database since on the file page there is a field "Dimensions" which shows both the file-size and the duration (except for files with this bug). Prototyperspective (talk) 11:11, 6 December 2024 (UTC)[reply]
The file page is just one page, it can descend into the metadata relatively cheaply. Sorting is a 140+ million row operation and for that we need to pre-extract the information and put it into a separate column of the database and keep an index. We do this for width, height and file size, but not for duration. —TheDJ (talk • contribs) 15:54, 10 December 2024 (UTC)[reply]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. 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 Documentation hub on MediaWiki.org. This page links to: resources for writing and improving documentation, a new #wikimedia-techdocs 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 contact the Technical Documentation Team.
Updates for editors
Layout change for the Edit Check feature
Later this week, 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 new Checks that appear while they are typing. The 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 on Testwiki and read the November project update for more details.
Translators in wikis where the mobile experience of Content Translation is available, can now discover articles in Wikiproject campaigns of their interest from the "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 <page-collection> </page-collection> 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 the step-by-step guide. [6]
The Nuke feature, which enables administrators to mass delete pages, now has a 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 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. [7]
The Editing Team is working on making it easier to populate citations from archive.org using the Citoid tool, the auto-filled citation generator. They are asking communities to add two parameters preemptively, archiveUrl and archiveDate, within the TemplateData for each citation template using Citoid. You can see an example of a change in a template, and a list of all relevant templates. [8]
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. [10]
View all 19 community-submitted tasks that were resolved last week. For example, a bug in the Add Link feature has been fixed. Previously, the list of sections which are excluded from Add Link was partially ignored in certain cases. [11][12]
Updates for technical contributors
Codex, the design system for Wikimedia, now has an early-stage implementation in PHP. It is available for general use in MediaWiki extensions and Toolforge apps through Composer, with use in MediaWiki core coming soon. More information is available in the documentation. Thanks to Doğu for the inspiration and many contributions to the library. [13]
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 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 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 RESTBase system.
The 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 privacy statement.
I've slowly been requesting overwriting of various files from the IWM. They've been so gracious in correcting exposure on some of those (as I write this, I begin to wonder whether the modifications are enough to warrant copyright protection...), but there being multiple versions of a file seems to confuse Dezoomify, who only pulls the second version with lighting issues. With the help of ChatGPT, I could extract the exposure-corrected one, albeit at a reduced-resolution (1000x1300, compared to the 2400x3000 unedited) version of the edited image. Is there something I'm doing wrong in terms of extracting the edited image in all of its glorious pixels?
Hi. If Dezoomify does not yield the desired result, then we have other methods ... First, look at the code for the page. On the page mentioned in IWM, press Shift + Ctrl + i (works in Firefox) to see the code window. In the code window, you should use the "Network" tab. Then click on the desired picture (the one to the left?). You will see three lines of code, one with the "info.json" file that is used by Dezoomify, and two with jpg files that result in thumbs of the picture. If you click on the bottom jpg codeline, you will see this code: https://media.iwm.org.uk/cantaloupe/iiif/2/171%7C%7C950%7C%7Csuper_000000.jpg/full/251,/0/default.jpg
Now substitute "251" with "2400" and Voila! You get a picture in 2400 x 3111 (at least that is how it worked for me). You might try with larger values than "2400", but the system at IWM would block that option. Hope this helps. Cheers Rsteen (talk) 03:27, 11 December 2024 (UTC)[reply]
Great, I can do that going forward and many thanks! Often images that have been retouched aren't accessible beyond the 2400px, or so I've unreliably figured out after further digging in the source code. JayCubby (talk) 03:53, 11 December 2024 (UTC)[reply]
Interesting. I use the Dezoomify extension on Chrome, and I only get 1536 x 1990 pixels. Please note that this may not be in the public domain. They say "Press agency", not a government picture. Yann (talk) 09:59, 11 December 2024 (UTC)[reply]
Upload shown as "completed" in OpenRefine, but no upload has been made to Wikimedia Commons
Problem: I have prepared and reconciled all relevant metadata, filenames and filepath in OpenRefine for a test batch of 5 images, including schema preparation with "add media" to Wikimedia Commons. When I did a first technical trial run of the pipeline a month ago, my images successfully uploaded to Wikimedia Commons even though the metadata was far from perfect at the time. Now that I have worked on the data transformation, following the Wikimedia best practices as closely as I could, I have the same thing happening to me as this user here: https://forum.openrefine.org/t/no-errors-reported-and-the-percentage-completed-went-through-but-no-upload-done/899. I get a "100% percent completed" notification from OpenRefine but no uploads have been made (I checked under my user profile as well as searched for the file names).
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
Interested in improving event management on your home wiki? The 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 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 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 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 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 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.
View all 27 community-submitted tasks that were resolved last week. For example, a bug was 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. [15]
Validate offline and re upload. Or if they are valid and can be identified easily (by prefix for instance) it might be worth it to run a server side script, but this requires a Phabricator ticket. The cause might be that there is no XML DOCtype declared for these files. —TheDJ (talk • contribs) 12:21, 17 December 2024 (UTC)[reply]
Being more concrete with two example files.
File:Dam.svg (27 March 2015) does not have an XML processing instruction.
Rebecca Moore (en:Rebecca Moore (scientist)) is a friend of mine. When I told her what her picture was used in Wikipedia (because she never looked at her own page - haha), she was appreciative of the guy who uploaded it, but wished he had uploaded one she felt better represented her and her work. (Yes, the Rachel Carson Award was a great honor, but she thinks the work in Brazil with helping Chief Almir and the Surui tribe save their rainforest was more meaningful.) She gave me the original photo that they used in Time Magazine article April 15, 2016,(https://time.com/4295351/rebecca-moore-google-earth-outreach/) to replace it. I cropped the original 1600 x 1062 to be square, but then realized I couldn't upload it. Can someone please do that for me if I get you the photo? And how would I do that? My real email is martha.legare@gmail.com. Thanks much for your help, Martha MarleeRobertson (talk) 05:58, 19 December 2024 (UTC)[reply]
@MarleeRobertson: Hi, We need a written permission from the photographer, unless he/she uploads it her/himself. And it would be much better to have the original image first, it can always be cropped later. Please see COM:VRT for the procedure. Yann (talk) 09:41, 19 December 2024 (UTC)[reply]
Thanks. To make sure I'm clear: we (and thank you!) can replace the current photo as long as we get the Brazilian photographer's permission, not the guy who posted the current photo? The photo I have was taken for Google - I'm 99% sure they paid her for it. (I think the photographer was from Brazil - will check with Rebecca.) I appreciate your help. MarleeRobertson (talk) 04:09, 20 December 2024 (UTC)[reply]
This image, File:Papua New Guinea relief map.svg, is failing to load globally, and I don't see any indication as to why. The image hasn't been modified in a few years, and the image loads from the direct URL ([16]) and from the link on the description page, but doesn't load when it's placed inline. Is this some kind of database error? Ivanvector (talk) 13:55, 19 December 2024 (UTC)[reply]
I imported {{Q+}} and Template:Q+/doc from this project into Wikispecies, but the latter is behaving very oddly, and the former not working as expected, and I cannot figure out why. Wikispecies is a small project with few technical editors; can someone assist there, please? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits16:07, 19 December 2024 (UTC)[reply]
Hi! It seems that there is a problem during File-uploading here on commons. The page was created for my picture, all descriptions and categories can be seen, but the picture itself is missing. Instead I get following message: "Die Datei „mwstore://local-multiwrite/local-public/1/15/Bargischow_Kirche_lub_2024-07-27_img01.jpg“ befindet sich, innerhalb des internen Speicher-Backends, in einem inkonsistenten Zustand." Is this a known issue, is the issue being resolved, and is there a chance I can add my images to the page without having to go through all the work of describing and categorizing again? Thanks in advance Lukas Beck (talk) 20:03, 23 December 2024 (UTC)[reply]
Hi, I got an error while uploading a big video with Chunked Uploads, and many errors while deleting files. It seems there is some issue on the servers today. Yann (talk) 21:22, 23 December 2024 (UTC)[reply]
Never mind, apparently there was no file description page. As soon as I had created one with the content test, I could delete the file. --Rosenzweigτ00:26, 24 December 2024 (UTC)[reply]
When you look at Category:Amastra, you'll find categories of which the name has changed by a vandal, e.g.
Ancient Amastra should be Amastra antiqua
Amastra Abbey should be Amastra badia
Amastra Baldwiniana should be Amastra baldwiniana
Amastra horny should be Amastra cornea
Hulled Amastra should be Amastra decorticata
Amastra fossil should be Amastra fossilis
Fraternal Amastra should be Amastra fraterna
Amastra Grayana should be Amastra grayana
Amastra Johnsoni should be Amastra johnsoni
Amastra Lahaina should be Amastra lahainana
and many more. When I press F5 on my keyboard, the proper name appears for a second or two and then changes again into the vandalised names. I have tried to find a solution for this, but I'm at a loss. Can someone put this right ? JoJan (talk) 10:16, 24 December 2024 (UTC)[reply]
I show you a partial clipboard of what I see on my computer (the arrows are mine): Partial clipboard of the Category:Amastra. Perhaps this will help solving this problem. JoJan (talk) 14:15, 25 December 2024 (UTC)[reply]
@JoJan It looks like you have Google Translate attempting to translate these. Try clicking the icon (next to the bookmark star in the address bar), then select Italian (or whatever it detects the source language as). —Mdaniels5757 (talk • contribs) 16:46, 25 December 2024 (UTC)[reply]
Hi!
It is common to smooth edges in raster images to make them look more aesthetic to the eye. But sometimes, it is desired not to apply this anti aliasing (for example for small 8-bit graphics). Otherwise it looks blurred. Is there a way to change the display style?
A pixelated arrow looks blurred, which is undesired in this case.
Yeah, I thought about it, too, but I guess there are several (unexperienced) users, who may not take the SVG conversion into account (and batch converting may be complicated, too)... --PantheraLeo1359531 😺 (talk) 14:51, 26 December 2024 (UTC)[reply]
EXIF data rendering omits space chars in some contexts
A recent example of faulty metadata rendering, click thru to view and search on "LNG boom"
I raised a similar issue previously and was told the code involved is intricate and quite possibly quirky and that the problem I described is relatively minor — in short, creating a fix is not especially likely. That earlier example involved ␣< sequences in email addresses.
For context, I specify my JPG metadata using YAML — a language with its own idiosyncrasies — and write that information to file using Python and ExifTool.
My latest upload (see thumbnail) used single quotes preceded (or followed) by spaces in the EXIF::Image Description metadata field, namely ␣'. This sequence was rendered faithfully to my terminal by Python and reported correctly on upload and download by both ExifTool and the gThumb image viewer. So I assume that the metadata is stored correctly in the JPG file.
But Wikimedia omits the leading (or trailing) space char in that sequence in the Description field and in the Metadata table. I duly edited the Description field to correct the corrupted string. But the faulty Metadata table rendering cannot be so easily fixed by users.
This presumed bug might not seem important but I can imagine use‑cases where confusion could result. In any case, I am raising the matter in the hope that a fix might be given some increased priority. Best, RobbieIanMorrison (talk) 22:46, 25 December 2024 (UTC)[reply]
Done Thanks, added :) --PantheraLeo1359531 😺 (talk) 16:02, 26 November 2024 (UTC)
View all 19 community-submitted tasks that were resolved last week. For example, a bug in the Add Link feature has been fixed. Previously, the list of sections which are excluded from Add Link was partially ignored in certain cases. [11][12]
.jpg){kind=link}
_Pudong_Yanggao_W0K-114_沪A31192D_581_2024-12-08.jpg){kind=link}
![[16]](https://upload.wikimedia.org/wikipedia/commons/d/de/Papua_New_Guinea_relief_map.svg){kind=link}
.jpg&action=edit&redlink=1){kind=link}
A pixelated arrow looks blurred, which is undesired in this case.
