This specific page is the requests page for the Illustration Workshop. Anyone can make a request for an illustration to be created or improved. The standard format for making a request is shown below, along with general advice, and should be followed. Many charts and graphs on the web are in the public domain. See Template:PD-chart; no need to create another free chart here if it already exists on the web.
Make a request
Show manual procedures
Use the following template when making a new request, replacing the examples with your image(s) and request(s):
<gallery>
IMAGENAME.EXT|Description of image
IMAGE#TWO.EXT|2nd image (If there is one)
ETCETCETC.EXT|Don't request too many at once, though
</gallery>
;Request:
: Details of your request go here… --~~~~
;Graphist opinion(s):
SpBotarchives all sections tagged with {{Section resolved|1=~~~~}} after 7 days and sections whose most recent comment is older than 60 days. For the archive overview, see /Archive. The latest archive is located at /Archive/2026.
An illustration of a coat of arms based on the following heraldic blazon: Azure, on a bend argent three crosses pattée gules, between two swords erect or. Thank you! --~2026-35405-34 (talk) 15:12, 17 June 2026 (UTC)reply
@Ilzolende: Thank you! Yes, looks good. Actually, this version with standing crosses (1) seems more faithful to the original. Although your other version (2) with rotaded crosses could be kept as a separate alternative. Furthermore, would you be willing to make an third version (3) including the version 1 coat of arms (horizontal crosses), but with a full heraldic achievement, complete with a conventional heraldic helmet, crest, torse, and mantling? Crest: a plume of three ostrich feathers, the center gules, the outer ones argent. Mantling: gules, doubled argent. Thank you! ~2026-37470-92 (talk) 12:10, 30 June 2026 (UTC)reply
Regarding a full achievement: I'll think about it.
I can put the standing crosses back no problem. The rotated crosses will still be in the file history. Also, if you have any sources for the blazon, or the blazon in some other language, I'd be happy to include those.
Actually, you could “cite” any source, since it couldn’t be verified and might well be far from the truth, as well as close - who knows? -, this one can hardly be accepted, to which it might be added that this coat of arms is not registered in any official roll, which make it out of scope.
Moreover, the fact that the applicant takes the position of the crosses so lightly (“Actually, this version with standing crosses (1) seems more faithful to the original. Although your other version (2) with rotaded crosses could be kept as a separate alternative”) only serves to heighten the doubt, given that, from an heraldic point of view, this matter is perfectly defined and cannot be subject to any nuance or interpretation, nor considered as a “possible alternative”. i.e. if the charges are not bendwise, this cannot fail to be specified.
It might be valuable to create an account and upload this file onto commons, then it could be used as an additional illustration in the article and also justify the SVG version.
Still there is no reference for this coat of arms;
Also, incidentally, given the picture linked above, the fact that the crosses are ‘unequivocally straight’ is most likely a matter of circumstance, and the point here is that no precise heraldic description exists. --Kontributor 2K (talk) 09:36, 18 September 2026 (UTC)reply
An illustration of a coat of arms based on the following heraldic blazon: "An eagle reguardant with wings elevated and displayed standing on a triple mount issuing from the base, in the dexter claw a rose slipped and leaved, and in chief a sun in his splendour issuing from the top of the shield." Thank you! --~2026-35405-34 (talk) 15:16, 17 June 2026 (UTC)reply
Thank you for your answer. For your information, you may find the Swedish language version of the blazon in question in this PDF document: here. Feel free if you want to consider an improved English language of the original Swedish one. Thank you! ~2026-37470-92 (talk) 12:15, 30 June 2026 (UTC)reply
Thank you. It's not “for my information”, since every coat of arms must rely on an official reference, which should systematically be provided with every request. That said, I wouldn’t say that freepages.rootsweb.com is what might be called an official reference. --Kontributor 2K (talk) 09:04, 01 July 2026 (UTC)reply
Not done The fact that this source cannot be verified – even though it's related to far past events – means that it is difficult to use it in an article or to use it to support any claim. --Kontributor 2K (talk) 10:00, 03 July 2026 (UTC)reply
@Kontributor 2K: The original source is stated as "Matrikel Härnösands län (1646)". Admittedly, it seems a bit unclear exactly what this refers to, although it should be among these archive souces: here or here. If that would be credible enough regarding good faith about source? ~2026-40614-70 (talk) 15:54, 20 July 2026 (UTC)reply
There don't seem to be many details on the pages cited;
Globally, one is entering an area where it might be best to directly contact a user who is knowledgeable about Swedish heraldry; I mean this not just for a matter of language proficiency. --Kontributor 2K (talk) 06:30, 22 July 2026 (UTC)reply
Can you please correct the designs of Kayah and Tanintharyi? The designs of the flags were poorly drawn. As for Bago, please make a SVG version of this flag --SpinnerLaserzthe2nd (talk) 15:10, 25 June 2026 (UTC)reply
Finished Kayah and Bago, though I do plan on adding some extra details to the current Kayah flag to make it more accurate without breaking any copyright rules. Burjkh (talk) 16:41, 9 August 2026 (UTC)reply
Thanksǃ But the Tampere PO logo is really really small. Why? I'm also noticing that it's not quite identical to the original, especially the font is different and the spacing between the graphic lines varies. Silence of Järvenpää (talk) 16:06, 18 August 2026 (UTC)reply
In regards to the sinfonia lahti, the current svg version is used on it's page is just a recolor of the svg file available on their website. So it's good. The person who made it picked the color from the link you provided and recolored it.
However their official website uses a white logo, not red. The link you provided seems to be for the website where the font was developed and published by request of the orchestra, and not the orchestras website. Although I'm not sure which one is better to use. I uploaded the original from their website just in case TheNoob1337 (talk) 22:15, 18 August 2026 (UTC)reply
@TheNoob1337:
Unfortunately, I have to say that you did not take my comments about the logos you created into account.
I have uploaded another testing file where I show the problems I found.
The whole logo is drawn very inaccurately. I would describe it as sloppy.
You say that you have “identified” the font. But this is not really an identified font. It is only an approximate match. You can see this, for example, in the letter “R”.
Even the simpler graphic elements, the bars, are not correct. Their size, vertical alignment and spacing, as well as their horizontal spacing, do not match the original.
I told you that you should always first search for existing vector files directly from the original source, where they can be considered “official”. Did you do that?
I think a small margin around the logo would be useful.
When optimizing your SVGs, please do not remove formatting characters such as line breaks and indentation. Removing them makes the SVG code much harder to read.
I also asked you to clearly state your source on the file description page. Using {{Own}} may satisfy the system, but it does not provide useful information here.
If a Commons category exists for the article, you should also use that category for your logo.
To make this clear again: I appreciate your work and your motivation. Your contribution is important for Wikimedia.
However, logos are official trademarks. It is simply not okay to redraw them yourself as only an approximate match.
If you cannot find official vector files, you should only draw logos yourself if you have the necessary skills. At the moment, I do not think this is the case. I would therefore recommend, and ask, that you work on other SVGs for Wikimedia instead. --Mrmw (talk) 05:36, 17 August 2026 (UTC)reply
Thank you, Mrmw, for these improvements. I'll use the file you uploaded. Someone earlier did the logo for the Lahti SO ... is this one okay? Finally, would you be able to do the remaining two logos (Turku PO and Tampere PO)? Warmly, Silence of Järvenpää (talk) 21:50, 17 August 2026 (UTC)reply
@Mrmw Thank you for your help! I sincerely appreciate your comments, however I think you're taking it a little too close to heart. I'm always trying my best to continiously improve, and making mistakes in the process is natural. There's no need to mention everything you don't like in someone else's work. I also understand your concerns about logos, but they are merely a vectorized version of the official logo primarily meant for using on wikipedia pages. Hence I don't think there's any problems with making mistakes in trying to vectorize them. If you're so concerned with my work, please be supportive instead of judjemental, it would be much more helpful and uplifting! For now I'll continue improving my skills and helping people around while having fun along the way, if you don't mind. TheNoob1337 (talk) 02:41, 18 August 2026 (UTC)reply
Could you please vectorize the Military Physical Fitness Badge and create three versions: white-red (pictures 1–3), gold (picture 4),silver (picture 5) and bronze (pgnum.pl)? Thank you in advance --Bastruk (talk) 14:03, 15 August 2026 (UTC)reply
This section is resolved and can be archived. If you disagree, replace this template with your comment. 痛Designism (talk) 00:14, 30 September 2026 (UTC)
why not (I think a full horizontal text would appear overly small on the top left corner of the Wiki)
Make an SVG image based on two PNG images of a word mark. Here are the two PNG images
The letters should be vectorised to match the original as closely as possible. "XKCD" is higher-resolution, so in case there's doubt as to how a letter in "EXPLAIN" should be vectorised, you can double-check from "XKCD".
For example, the ending strokes of the letters in "EXPLAIN" might sometimes look perfectly rounded, but from "XKCD" you can see that they are all a little square-ish and are never perfectly round.
Do not reuse the "X" from "XKCD" in "EXPLAIN" or vice versa.
It is important that the letters be vectorised as closely as possible to the original:
The letters never "touch" each other, including in the initial "EX" sequence (there's a really small gap, but they should not collide in the results).
The letters should not be stretched or rotated and their position relative to the other letters in the same word should not be changed.
In theory, the thickness of the letters in the two PNG images is almost identical, but in case they're different, the letters of "EXPLAIN" can be made slightly thicker to match the thickness of the letters in "XKCD".
The result should contain the two words in a single SVG file.
In the result, the words should be distinguishable as two different words, with sufficient spacing between the two.
The two words should be vertically aligned and resized correctly, so that one word doesn't look bigger/smaller or lower/higher compared to the other.
No, it's actually the other way around. The plan is to change our old PNG logo, and then use it on the en:xkcd article in the paragraph mentioning explainxkcd.com. But, in order to change the existing logo, we first need a new logo! So: (1) create the new logo, then (2) adopt it as explainxkcd's official logo, and once that's done (3) use the logo on the Wikipedia article about the webcomic. Would that be acceptable? FaviFake (talk) 21:48, 26 September 2026 (UTC)reply
Of course, here it is! Note that the discussion is pretty long and disorganised, mostly because we linked it from the sitenotice and editors were more interested in proposing new taglines rather than logos. FaviFake (talk) 16:30, 27 September 2026 (UTC)reply
Thank you so much! I hadn't considered the possibility of stacking the texts, but that's actually super useful! We needed a full horizontal text because we're planning to switch the default skin to Vector 2022 and the old square-ish logo didn't fit, but we can use your stacked version for users who wish to keep using Vector 2010!I made a few changes which I described in detail in the edit summary for the overwrite, and I then cropped the leftover empty space around them.I've proposed it on the explain xkcd wiki, I'm sure they'll love it! The only thing preventing us from switching to v22 was the png logo :D FaviFake (talk) 18:02, 28 September 2026 (UTC)reply
Can someone please vectorize the logo of Kabinet Merah Putih, because when the user uploaded this image, it was not yet vectorized. Thank You. --~2026-43697-16 (talk) 23:57, 8 August 2026 (UTC)reply
This section is resolved and can be archived. If you disagree, replace this template with your comment. 痛Designism (talk) 00:15, 30 September 2026 (UTC)
@Anidaat: Being a JPEG, correction is not trivial. What is the advantage of this diagram over, say, File:Political_spectrum_horseshoe_model.svg? If it's colour, I'd caution that it's locale-dependent: for example, red is conventionally considered politically to the right of blue in the USA but vice versa in the UK, thus it might actually be better for it to be grey. cmɢʟee ⋅τaʟκ18:56, 20 August 2026 (UTC)reply
Good point with the colours - I saw it "european", left being red in all languages....
I liked this one more than others though for its shape with good radiusses and especially for it being rounded, not ending in a straight cut. Anidaat (talk) 15:25, 21 August 2026 (UTC)reply
Glancing at what those platforms are, they seem to be all decentralized FOSS platforms. While they are notable, they are not that popular. I don't even think I would've included PeerTube and Dribbble if it wasn't part of the original image. Gemdation (talk) 17:17, 23 August 2026 (UTC)reply
This section is resolved and can be archived. If you disagree, replace this template with your comment. 痛Designism (talk) 00:17, 30 September 2026 (UTC)
Please re-upload/overwrite this file with the updated Cricinfo logo (removing the obsolete "ESPN" branding). I have prepared the updated image file here: "https://postimg.cc/zyW5d9Dm". I am not the original uploader, so I cannot overwrite the file directly. Thank you! RavanaTALK04:55, 4 September 2026 (UTC)reply
Could someone please create the standard Wikimedia football kit pattern files for FC Zenit Saint Petersburg's 2025–26 home and away kits?
The Russian Wikipedia article currently uses the old 2023/24 patterns (`_zenit23h` and `_zenit23a`), although the club introduced completely new Jögel kits for the 2025–26 season.
The distinctive feature of both shirts is the architectural graphic across the lower part, depicting Saint Petersburg imagery, including Gazprom Arena and Lakhta Center. The home kit is light blue with a darker blue graphic and white trim; the away kit is white with a light-blue graphic and dark-blue trim.
Standard kit files are needed, preferably using the following names:
`Kit body zenit2526h.png`
`Kit left arm zenit2526h.png`
`Kit right arm zenit2526h.png`
`Kit shorts zenit2526h.png`
`Kit body zenit2526a.png`
`Kit left arm zenit2526a.png`
`Kit right arm zenit2526a.png`
`Kit shorts zenit2526a.png`
The patterns should work with the standard football kit system used in Wikipedia infoboxes (`pattern_b`, `pattern_la`, `pattern_ra`, `pattern_sh`).
There's a big mess exists in TP cable illustration variations, most of which (old) are falsely named/descripted etc, but have one unique feature absent on newest ones - they are texted. However, despite some of these files is marked with template:Translation possible (and it really have embedded text inside) it was used a bit primitive way as such "autotranslation" function still not working as decsribed at Switch SVG but multiple one-language derivations created instead (with only language text inside) so in fact text was never used there as dynamic.
However, to avoid "losing" (not literally, but in file history) the text content within them, I propose updating the aforementioned files by incorporating both pointers and dynamic text—or, even better, pre-integrated multilingual text that allows for automatic language switching across different language sections. This would enable a unified approach to file usage and eliminate the errors associated with repeatedly duplicating what are essentially the same files.
All words used (in multilanguage set for later autotranslation i.e. using a tool meant here) you can take from i.e. that english (or any other you prefer from what we have) file. Also, I guess, it would be good to not create new files but to update already existing ones. Any ideas about does it worth it or easy to be done?--~2026-48708-14 (talk) 13:35, 10 September 2026 (UTC)reply
I do not see a problem in the gallery above, but the "big mess" link goes to a template that lists multiple language versions of an illustration. For example, SUTP:
yes - that template what I mean as a place where I collected anything to show how much is the mess.
I.e. you have 5 SVGs and 3 PNGs for only UUTP cable schematics, 5+4 for UFTP (where 7 of it with ambiguous naming - as STP is old naming used earlier for what is called now as UFTP and FUTP), 4+3 for SUTP where one of claiming SUTP/(U)FTP/SFTP have the same schematics - that's not true), 4+1 for SFTP. What for? People quite often also miss the exact image to be used needed or to be updated because of mess we have.
Many wikis choose different languages (despite there's ~3 only translation for each of 4 only ever translated diagrams to choose from) that's no way still enough (which means duplicates will appear more and more, sometimes faulty). So why not to make most advanced imaged, but multilanguage-texted (similar to old diagrams, but only multilanguaged file exactly) and upload it? it's better to update/advance already most advanced one then to translate 13 years old one.
Got it: the side views don't have text but the cross-sections do.
What seems to be needed are two language flags: one for the label language, and another for the type of cable. If it's foreseen that the side views will eventually need labels, how about constructing them from two images, the way sports kits are?
one with the graphics (switchable by hacking switch) with leader lines running off the right:
the other being text labels (with switchable language)
A drawback is that if a reader views an image on Media Viewer, only half the figure is shown.
Another solution might be to write a (Python) script that generates a series of images, each being a type of cable with multiple translations. The translations could be stored as JSON or simple table on Commons, which the script reads to get the latest translations.
Instead of separate elevation and section diagrams, I decided to combine them in one image.
It supports English, German and Italian so far using switch. I'm unsure what to call "Fe" so tentatively used "cable foil". It's strange that the original diagram had "Fi" as "pair shield" and "Se" as "cable shield": "shield" sometimes means "screen" and sometimes "foil".
Please do not add more languages in the files, but instead update the table, rerun the script and upload the SVG output.
Wow! Looks just great! ;) Thanks! And multilanguage autoswitching works just fine. Still wondering does it need shielding type heading.
However using "Shield" is misleading.
It traces back before the distinction between "screen" (mesh) and "foil" (solid) existed - time when there was just concept of wires shielding to improve attenuation characteristics - no one much cared which type it was - each pair-level or overall external. For now it's just a sort of obsolete term used to define is it UTP (Unshielded) or some way shielded, effectively combining everything except the UTP having too wide meaning to be used for exact shielding type definition. As you clearly said - "shield" sometimes means "screen" and sometimes "foil" - which is inherent in the past - that's why exactly it can't be used now anywhere except "Unshielded" (such a full shielding name is not used on your diagrams for now), i.e. SF/UTP is "Screened Foiled / Unshielded Twisted Pair" where "/" is external/pair shielding level separator.
It's better to use "Foil" for both Fe and Fi and "Screen" - for Se. No need to differ "cable" foil from "pair" foil - what it relates to has already been visualized. I.e. SF/FTP - can have "Screen" - aligned to "cable shield" and "Foil" aligned to both cable foil and pair foil. Because what you have now at both SF/UTP and SF/FTP is misleading as equalize "shield" for pair and cable when there's "cable foil" name exists leads us to "pair shield" ostensibly have mesh (similar to cable screen that named "cable shield" there) and not foil - as it really is. ~2026-51070-19 (talk) 03:41, 22 September 2026 (UTC)reply
@Cmglee As an example how same "foil" word is used for both shielding levels you can see here:
Thanks, @~2026-51070-19: . I've updated the diagrams making the terminology and spacing consistent, and avoiding leader lines reaching across the right figure. I've used "pair foil", "cable screen" and "cable foil" for consistency (I think it's better to disambiguate "foil" instead of having the same label point at different elements).
@@Cmglee: Looks like I can't edit anything inside the user namespace, so I'll leave it here. Just copypaste it there - I guess it have to work (most problematic was to leave spaces until next column separator, but I still left same format as you had).
I changed part of the translation (you mistakenly took words from the same positions, but linked to another elements which caused mix up).
I can't say that everything is translated perfectly, but I tried my best. For he-af-uk-ru I partly used words from already existing pngs, rest was some kind of own initiative. If anyone will want to add something or to change something - I'll leave {{Translation possible}} on file pages in addition to linking the current discussion - for everyone to be free to choose option they like most to add/update the languages. However I think it will be enough to fill the basic use and exclude obsolete single-language diagrams from use as superceded.
Despite there's 49 language versions about twisted-pair (mostly about ethernet one) I can't effectively translate to all of the languages. It would be great for natives to do it further.
@Cmglee Sure, feel free to do whatever you need - I'll still be glad when it'll be done ;) As it looks so exciting!! ;))
Just fixed a couple of languages there as initially while trying to shorten the terms or using direct translation sometimes the result was quite unnatural with only word (or hieroglyph) and completely different meaning.
I.e. I removed what in parentheses in the next phrases:
(Cable) Sheath, but still had to add it in German and Afrikaans as Mantel itself, I guess, have usually an exclusively different meaning - the coat (as people clothing exactly).
(Twisted) Pair (of wires), but had to add it ("wire") back in Chinese as 对 doesn't look like can be translated as "pair" exactly.
Also I used "screen" (and not i.e. "braid") term exactly for cable (external braided) screen to not confuse the readers and to be clear with cable types standartized terms ("S" meaning there) at default language (english), however i.e. in Spanish first I used "Trenza" but later used synonymized "external braid" (Malla exterior) instead of using more natural "blindaje trenzado" or "malla metálica" which however doesn't contain any information about the shielding level, sometimes used also "cable braid" term to be translated, as most natural use of this term in affected languages, in French I initially used "Tresse" (Braid), but later, despite it naturally had to be "tresse métallique", it had same issue as spanish translation - no any shielding level information (probably because still noone made braided shielding on pairs level so by default noone use any shielding level clarification for braided term like decades ago noone cared about level of "shielded" meaning), so I used "(La) Tresse du câble" that still in use. Braid can be also nylon and in some languages "metallic" clarification is being used, but within the diagram such clarification looks excessive so I avoided to use it in any translation.
Anyway, if natives will be active enough - they always will be able to change whatever they want to, however @Cmglee if there's some sort of chars limit per one label exists - you better note it somewhere - who knows what kind of label essays one could come up with? ~2026-51193-56 (talk) 11:58, 23 September 2026 (UTC)reply
@~2026-51193-56: My pleasure. Thanks for clarifying the terminology in various languages, too.
There is no strict length limit: just run the script and see if the result is acceptable! ୯ ͡° ͜১͡° ੭
A section of the SVG e.g. text[systemLanguage="de" i] { font-size:90%; } globally scales all strings of the stated language so one could tweak the percentage for fit. It's sadly not trivial to support multi-line labels in SVG, and there's also insufficient space in the SF/FTP case.
To align columns as best I can, I reordered your table so that languages with fixed-width characters are on the left. I've had to separate Hebrew and Arabic, otherwise RTL rendering makes the columns appear swapped.
I also made the page a template, so it can be transcluded in your template, putting the source code in a scrollable div to not take up too much space and yet letting editors copy it easily. Let me know if it overly clutters up your template.
I've uploaded new versions of the images with your 13 translations. Would you mind checking if they're ok, please?
@Cmglee You read my mind! ;) While testing translations I found 1 overlapping the conductors and wanted to focus you on it meaning you still have ~12-15 (variable as font you use is not monospaced) chars limit to not spoil the picture, but missing the moment when you were online trying to substantiate the issue, I write now only when you already fixed it ;) Case is I was trying to make the descriptions in certain languages (including English) more detailed (longer), but I ran into an issue and didn't try again. Now I'm wondering whether to give it another shot, taking in view you already resolved it by scaling in place, or better focus on more translation languages, because some editors are not intended to join translation themselves, but rather prefer to just revert if something wrong with it.
Anyway - you made a great job ;) I didn't even expect it to be so much successful and you so much involved. I greatly appreciated.
What threw me off was the fact that - as a editor noted in the link above - S/STP-like variants (or rather, their non-Ethernet counterparts, - like LiYDY-CY TP 6x2x0,25mm2 having 3 pairs and using low-frequency signals only [both unlike ethernet], - I'm not much familiar with) actually exist; however, I wouldn't venture to ask for more diagrams, as the number of possibilities could be infinite, which isn't practical. For now, it is better to stick to the Ethernet diagrams only, as there is a finite number of them and examples are easy to find.
Also, I found some widely used images of the human body (turned into illustrations with captions), which have multiple international copies (at least 20), some of which have not yet been vectorized, which can be combined into one file using the same technology. Are you interested in this as the next task to be done or we'd better focus on translating even more of current one?
What I still count as soft issue (it's not for me but can be for someone else) is need of stretching the language table to the right instead of down when adding new ones. I guess it could be easier to edit it for someone with like adding the language line instead of row. As I also not sure why do you need same language captions equal chars alignment (I mean it's just design or technical requirement) as one as your additional requirements to leave non-fonetic languages rightmost - I don't know is it easy for you to make such a source table transposition, so... I'll just ask - is it easy to do it? I repeat - I don't need it - but I guess it will greatly ease for someone else out of topic to add/edit the language there. ~2026-51278-70 (talk) 15:21, 25 September 2026 (UTC)reply
Thanks. How do you get Arabic, Chinese and Japanese to appear as monospace in the source editor? Latin and Cyrillic text appears so when editing source but not the others, which I why put them at the end and padded with spaces so they look right in my browser.
I'd rather keep the labels short as we don't have multiline labels and to reduce clutter (but still distinguish pair foil from cable foil). If there's an exception from the general case, one could add an asterisk and elaborate in the caption.
Can you point me to your human body diagrams? I wouldn't want to redraw anatomy (much more complicated than cables) but can help create a script to read off a table as above.
If I had realised that there would be over 20 languages and only 7 labels, I'd have switched the rows and columns. Too late to do it for twisted pair but could rethink for anatomy diagrams. Of course, that depends on how many labels vs languages there will be.
The other problem is how to quickly update diagrams. With just 3 on/off features, there are 8 files to manually upload each time a change is made. n features will need 2n. Before starting this endeavour, please find out how several tens of files can be updated at once. cmɢʟee ⋅τaʟκ18:16, 26 September 2026 (UTC)reply
Good sleuthing. One needs to find a balance between number of languages and number of labels. It's also conceivable that editors add more and more strings, resulting in wide tables. Frankly, I thought we'd stick with maybe 6 or 7 existing languages in the PNGs and didn't think it'd grow to 20+. cmɢʟee ⋅τaʟκ14:53, 29 September 2026 (UTC)reply
P.S. Also whether the strings are roughly the same length in a given language: if they are not, the current labels as rows leads to much wasted whitespace, but at least succint languages can compensate for verbose ones.
@Cmglee As of languages number - I see. Probably i had to tell I mean number of languages meant can grow at least to number of articles it used in (i.e. one per exact language) initially. However.. Isn't it great it've been used so widely? Sad only is noone still added more languages except you and me. Btw did you succeed using tools?
As of spaces I use excel to generate appropriate number of spaces to add there based on difference between len() and max(chars) for each language row - my source editor same way doesn't mean to monospace arabic etc. However someone says you can use "Hasubi Mono" or "kawkab mono" fonts as one as edit Special:MyPage/global.css and add some css there like:
there (theoretically, I can't check it being as is).
As of human body diagrams I was trying to trace whole the connections there (community made about 100 (94 if to be exact number I counted) similar images, more then half of each are just some way, mostly multilanguaged, copies, based on 4 initial) and realized someone already did it anatomical here however with 7 languages and english as default only:
and no any information about how to add there more i.e. with {{Translate}}.
What is still good to be done there is to add more languages and make similar to TP template with description about how to add more languages for further use.
As of languages itself we can add there initially - there's partly (17 of) vectorized images translated already have place I found 23 more - I can list files if will be needed - diferent ones (af/ar/ca/cz/de/el/en/en/eo/es/fr/he/hi/Ja/ko/mdf/nd/pl/pt /ru/shi/tr/zh) we can extract labels' content from (By OCRing probably) and one numbered we can add content of to zxx language)
As addition - there's one more 2 languaged diagram exists:
with 7 more languaged (af/de/fr/Ja/pt/ru/zh-Hans) svgs I can list also.
similar separate already translalted svgs exists good to be merged to the same. However there's also a way to make it better as one language have also a back view that would be also great to add to the lables and enline it all using i.e. that image or that one (labels here can be hard to match) or squared and adding some sort of score there.
Initial images can be also taken from originals if you wish to make it from the scratch (there's 2 versions exist of male/female anteriors and 1 of posteriors as one as 1 version of anterior of another couple).
As further (later task) for same way translation there's also exists some using same male planes diagram that is nor widely used nor translated unlike another version of that both have copies and used widely not having appropriate translation.
Or that couple based organs diagram (fe/male) which however doesn't looks like widely used.
You better pick you most like of it - and I'll provide more images to process focused on your choice exactly.
I downloaded the original logo from the official White House website. Unfortunately, the vectorization of the White House is atrocious in that there are several redundant nodes and paths, resulting in a huge filesize. If this was just a regular file, it would rightly be tagged with {{TracedSVG}}; however, since this is the official logo (visual errors included, such as the overlapping stars on the American flag), I've been trying to find a way to simplify the paths without "perfecting" the visual appearance of the image. I used the original logo to create two vectorizations of The White House logo under Trump 2.0.jpg, a JPG file which is listed in Top 200 JPG images that should use vector graphics and Top 200 logo images that should use vector graphics, one with editable text (though the font required to render properly isn't installed on MediaWiki), and one with the text converted to glyphs to preserve the original appearance (the font is licensed under OFL). I am hesitant to mass-replace all these files though, considering that the original JPG is 295 KB while the vectorization without editable text is 1.47 MB. For all three requests, I am requesting that the image of the White House be edited to remove redundant nodes and paths while preserving noticeable visual errors. The White House vector is exactly the same between all three of them. Ideally, the final vector should be no greater than 295 KB (the size of the original JPG). --ForeverFlying (talk) 03:33, 14 September 2026 (UTC)reply
Graphist opinion(s)
Telkomsel logo with "Melayani Sepenuh hati" tagline
Illustration workshop
Nordlander coat of arms
Not done The fact that this source cannot be verified – even though it's related to far past events – means that it is difficult to use it in an article or to use it to support any claim. --Kontributor 2K (talk) 10:00, 03 July 2026 (UTC)
2000–2015 version of the seal, which could be used in the creation of the 1961–2000 version of the seal.
Flag of Mobile adopted in 2000, which could be used in the creation of the 1968–2000 version of the flag.
Flag of Kayah
Done.svg/120px-Flag_of_Kayah_State_(1974–2010).svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Former flag of Kayah
Flag of Tanintharyi
Flag of Bago
Flag of Bago Region (Vectorized)
.svg)
![Lahti Symphony Orchestra logo (Red)[OK]](https://thumb.wikimedia.org/wikipedia/commons/thumb/2/26/Logo_Lahti_Symphony_Orchestra.svg/120px-Logo_Lahti_Symphony_Orchestra.svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Lahti Symphony Orchestra logo (Red)
![Lahti Symphony Orchestra logo (White)[OK]](https://thumb.wikimedia.org/wikipedia/commons/thumb/d/dd/Sinfonia_Lahti_logo.svg/120px-Sinfonia_Lahti_logo.svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Lahti Symphony Orchestra logo (White)![Helsinki Philharmonic Orchestra[OK]](https://thumb.wikimedia.org/wikipedia/commons/thumb/2/27/Logo_Helsinki_Philharmonic_Orchestra.svg/120px-Logo_Helsinki_Philharmonic_Orchestra.svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Helsinki Philharmonic Orchestra![Turku Philharmonic Orchestra logo[OK]](https://thumb.wikimedia.org/wikipedia/commons/thumb/e/eb/TFO_logo.svg/120px-TFO_logo.svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Turku Philharmonic Orchestra logo![Tampere Philharmonic Orchestra logo[OK]](https://thumb.wikimedia.org/wikipedia/commons/thumb/7/78/Tampere_Philharmonic_Orchestra_logo.svg/120px-Tampere_Philharmonic_Orchestra_logo.svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Tampere Philharmonic Orchestra logo![Lahti Symphony Orchestra logo (Red)[OK]](https://commons.wikimedia.org/wiki/File:Logo_Lahti_Symphony_Orchestra.svg){kind=small}
![Lahti Symphony Orchestra logo (White)[OK]](https://commons.wikimedia.org/wiki/File:Sinfonia_Lahti_logo.svg){kind=logo}
![Helsinki Philharmonic Orchestra[OK]](https://commons.wikimedia.org/wiki/File:Logo_Helsinki_Philharmonic_Orchestra.svg)
![Turku Philharmonic Orchestra logo[OK]](https://commons.wikimedia.org/wiki/File:TFO_logo.svg){kind=logo}
![Tampere Philharmonic Orchestra logo[OK]](https://commons.wikimedia.org/wiki/File:Tampere_Philharmonic_Orchestra_logo.svg){kind=logo}
Request taken by TheNoob1337 (talk) 21:56, 16 August 2026 (UTC)
Military Physical Fitness Badge (.gov pdf source)
Military Physical Fitness Badge (.png transparent background)
Military Physical Fitness Badge (.gif)
Gold Military Physical Fitness Badge
Silver Military Physical Fitness Badge
This section is resolved and can be archived. If you disagree, replace this template with your comment. 痛Designism (talk) 00:14, 30 September 2026 (UTC) 
.svg/120px-Wordmark_of_explain_xkcd_(stacked).svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
why not (I think a full horizontal text would appear overly small on the top left corner of the Wiki)
.svg)
PNG
Main file.svg/120px-Flag_of_Egypt_(darker_shade_of_gold).svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Old location for dark emblem
.svg)
it should say far right on the bottom right side
Montage or collage of Jeddah
Logo![Icon of Teleclub SVG[OK]](https://thumb.wikimedia.org/wikipedia/commons/thumb/8/8b/TeleclubIcon.svg/120px-TeleclubIcon.svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Icon of Teleclub SVG![Logo of Teleclub SVG[OK]](https://thumb.wikimedia.org/wikipedia/commons/thumb/3/3b/TeleclubLogo.svg/120px-TeleclubLogo.svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Logo of Teleclub SVG
![Icon of Teleclub SVG[OK]](https://commons.wikimedia.org/wiki/File:TeleclubIcon.svg)
![Logo of Teleclub SVG[OK]](https://commons.wikimedia.org/wiki/File:TeleclubLogo.svg){kind=small}
Current logo on Commons.svg/120px-Cricinfo_logo_(2026).svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
.svg){kind=logo}
Logo of the former home improvement chain BAUSPAR
.svg/250px-Giro_di_Campania_logo_(vector).svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
.svg){kind=logo}
PNG
SVG
PNG (icon)
SVG (icon)
FFTP
FUTP
SFFTP
SFTP
SFUTP
SUTP
UFTP
UUTP
SUTP-Kabel.svg German
S-UTP-cable.svg English
S-UTP-cable-it.svg Italian
S-UTP-cable-en.png English
S-UTP-cable.png Hebrew
Cavo S-UTP.png Italian
~2026-51070-19 (talk) 18:43, 22 September 2026 (UTC)
JPG
Original logo (reference)
Vectorization of The White House logo under Trump 2.0.jpg (without editable text).svg/120px-The_White_House_logo_under_Trump_2.0_(embedded_text).svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Vectorization of The White House logo under Trump 2.0.jpg (with editable text).svg/120px-Telkomsel_(2021).svg.png?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Logo without tagline
Intermarché logo with the addition "by Mestdagh"
Logo of the former Belgian trading company Mestdagh S.A.
Logo of the former Belgian supermarket chain Super M
Logo
.svg){kind=logo}
.svg){kind=small}
.svg){kind=link}
.svg){kind=link}
.svg){kind=link}
.svg){kind=link}
.svg){kind=link}
.svg){kind=link}
.svg){kind=link}
.svg){kind=link}
.svg){kind=link}
.svg){kind=link}
