Template talk:Image generation/Archive 1

Test report

On OOjs UI icon unStar.svg I tested {{igen|A|+}}, and its "SVG genesis" triggered my DEnglish alert. How about "SVG creation" (or whatever a native speaker suggests)?

I tried to take a word that is somehow useable in all languages... now "development" is used in English, and I am working on a multilingual version. sarang♥사랑 08:09, 6 January 2015 (UTC)

At the moment I'm not sure when this template would be used without + and without -: Apparently it needs a + for other fields in {{Information}}, or a - outside of {{Information}}. Presumably (untested) no - adding Template:{{Image generation/Archive 1}} would also work to stop the floating. –Be..anyone (talk) 20:44, 12 December 2014 (UTC)

FYI, mentioned on Commons_talk:Quality_images_candidates/Archive_8#SVG. –Be..anyone (talk) 21:35, 15 December 2014 (UTC)

Because the template cannot recognize whether it is transcluded from inside the Information box or not, the usage of "+"/"-" is provided.

The "-" isn't needed when after the template no more text is displayed, or the following item has any <div ...> options (as boxes have), or when you add the Template:{{Image generation/Archive 1}}. Better use it if any doubt.

The "-" is necessary when e.g. the license header follows. Of course you can code everything (e.g. the function of "+" or "-") by yourself.

See also the explanation and examples at Parameter table in the documentation. sarang♥사랑 08:09, 6 January 2015 (UTC)

SimplSVG

To enable the use of {{SimplSVG}} which is completely otherwise parametrized, as a workaround it can be invoked

• within Infobox: |Other fields = {{Igen|9=+|10=S| all the parameters #1 to #8 }}
• outside of box: {{Igen|10=S| all the parameters #1 to #8 }} (no need of 9=-)

Because the template cannot determine whether it is used inside the Infobox or outside, the 9=+ is necessary.
See also the documentation for use of SimplSVG . sarang♥사랑 11:51, 17 March 2015 (UTC)

More tools

Example: |other fields={{ Igen | X | + | s = c | t2 = {{ Adobe | v | vo = n | topic = c }} }}

(as in the example e.g. Torgauer Wappen.svg)

You can see that it results in categorizing the file in two categories! — It can be avoided, with |cat=<nowiki/> one categorization (or all) can be suppressed. This example can be specified much easier with {{ Igen | X | + | & = A | s = c }}

with QGIS

When the second tool to specify is QGIS, just set the parameter "&" whose default is QGIS, e.g. |other fields={{ Igen | I | + | & | s = m }}

Bug reports

Fixed

{{igen|?|+}} to get only a "valid" doesn't work as I expected it to work, and {{igen|n=TBD|+}} assumes InkScape out of thin air. Background, I want to use {{Igen}} in "other fields" also for cases, where the tool is unclear, instead of {{ValidSVG}} or {{InvalidSVG}}. –Be..anyone (talk) 00:29, 16 December 2014 (UTC)

New {{igen|U|+}} feature tested on File:Motorway Sweden, Switzerland and Italy.svg maybe drop the "unknown" box, because the category "valid + other tool" is good enough. –Be..anyone (talk) 01:24, 22 December 2014 (UTC)

Template expansion: When a name is specified, Other tools is implied and parameter 1 can be omitted. See docu. 17:49, 6 January 2015 (UTC)

@Sarang: , 0 errors end up as "invalid" (category), tested/visible on File:Symbol delete vote (2).svg. –Be..anyone (talk) 13:40, 22 December 2014 (UTC)

 Done The template {{HandSVG}} needed an expansion for the err=0 option. @Be..anyone: Thank you for telling me; sorry that I didn't see it earlier..

BTW, |Other fields={{igen|T|v|+}} isn't necessary, |Other fields={{igen|T|+}} will be enough, because "v"="0" is defaulted.

See also the parameter table at the bottom of the docu. -- sarang♥사랑 08:09, 6 January 2015 (UTC)

Less typing is nice, but I'm happy with three parameters, the last always + for other fields. Unrelated, there's an old CFD Bitmap from Inkscape, maybe you can answer Perhelion's question. –Be..anyone (talk) 15:27, 7 January 2015 (UTC)

Open

{{igen|O|v|+|n=Batik}} works intuitively and far better than expected, but I'm not sure about the missing category:commonsOTM, create it? –Be..anyone (talk) 11:05, 21 January 2015 (UTC)

When an existing Created with ... template is used as an Other tool the transclusion is stored in that maintenance category. This is useful for maintaining transclusion where the missing template is created later. Because the template {{Created with Batik}} exists this happens there.

It takes me more than three seconds to figure out how {{Adobe-hand}} is supposed to work in the {{Igen}} framework, that is not acceptable. Please add a list of "well-known" names to the documentation, and count me as  Support for a deletion request of {{Adobe-hand}} if it does not fit into this framework for some obscure reason. For now I'll just use A for "anything Adobe", even if it's not AI. –Be..anyone (talk) 16:22, 30 January 2015 (UTC)

Update, other field= instead of other fields=, error on my side. But the "info" for {{Adobe-hand}} is a kind of "promotional essay with trivia", I stick to A, until somebody tells me why the difference might matter. –Be..anyone (talk) 16:33, 30 January 2015 (UTC)

Adobe-hand (and Inkscape-hand) had been designed for a stand-alone, they don't fit into the later unification of the Created with ... templates. With some expansions they are made fitting, more or less, if used with not too many special parameters. The templates HandSVG and SimplSVG are now also useable with {{Igen}} (more complicated uses of HandSVG can be done with SimplSVG).

About the boring other fields= (I hate to type it, often mistype it, and miss this text string at the edittools below) it is possible at COAInformation and Map to write instead simply Imgen= but my request to insert it into the Information failed. sarang♥사랑 11:51, 17 March 2015 (UTC)

Commonist

Recently I needed a "chunked upload" thingy, and couldn't use Rillke's script, because I'm not sure how it works for new files with a monobook skin. Looking at commonist I also wasn't sure if that's something for me, and tested VicuñaUploader, worked for me, just a double click on the JAR. In other words, what's the idea of supporting only commonist instead of nothing, when these three upload tools already manage correct "uploaded with" categories and wikilinks in the upload history? Quoting my talk page archive: Inzwischen kann es auch Eier legen und Kaffee kochen. –Be..anyone (talk) 10:54, 9 January 2015 (UTC)

Slashdot

There are three Gnuplot examples, one with a slash, the same without slash, and a third about something else. The output for with / and for no slash is identical, and apparently / is not documented, only mentioned as existing. –Be..anyone (talk) 05:15, 10 April 2015 (UTC)

I do not really understand, is there something wrong? Where are the three examples? May be it is about parameter #2 of the template - IMHO that is well documented. If it is something else, please show me what can be amended. sarang♥사랑 08:35, 18 October 2015 (UTC)

Protection, and template sandbox

As was requested at COM:AN/P, I protected this because it's used on over 15k file pages, and thus a vandalism target. I created a 'sandbox' for it, at Template:Image generation/sandbox that can be used for future work (it's currently initialized with a 'substed' copy of the template), and then just pushed live with a edit request here or at AN. Sorry for any extra hassle for people maintaining it, but we really don't want it to suddenly say 'poop', lol. Revent (talk) 08:45, 18 October 2015 (UTC)

To add

• SVG-edit as seen here: File:Pentalobular.svg, and
• "This vector image was created with Inkscape, and then manually replaced" as seen here: https://commons.wikimedia.org/w/index.php?title=File:Flag_of_the_United_Kingdom.svg&oldid=190022053
• This: File:Linux kernel ubiquity.svg —User000name 06:10, 4 April 2016 (UTC)

I think your 2nd point is in essence the same as H for {{Inkscape-hand}}. Your 3rd point is an ordinary {{igen}}, the edit instruction creep can go to the description or /dev/null. For your 1st point {{igen|SVG-edit|+}} might be good enough if there are only a few SVG-edit, inline example:

 

This graphic was created with SVG-edit.

.

Be..anyone (talk) 13:31, 4 April 2016 (UTC)

"...invalid due to v errors."

@Be..anyone: and others: The template currently turns the code {{igen|A|v|+}} into "W3C the source code for this SVG is invalid due to v errors" and "This vector graphic was created with Adobe Illustrator." Not only does this not seem to make sense ("v errors"??) but it looks like it is labeling files incorrectly: isn't the letter "v" in the second parameter supposed to mean "valid"? I realize there are other ways to get it to display a "valid" tag on an "Adobe Illustrator" file, but I don't understand why the above code should label such a file as "invalid". This is particularly confusing as the documentation never actually explains what the letters "n" and "v" in the second parameter mean. Could we get an explanation added for this parameter, could we have it marking files as valid rather than invalid, and could we have it produce a sentence that doesn't say "...due to v errors" where the "v" doesn't mean something like a Roman numeral 5 or an abstruse code of some kind? (or could someone explain why it should be doing exactly what it is doing?). Thanks! KDS4444 (talk) 23:27, 29 April 2016 (UTC)

I confirm. It seems that this behaviour has been introduced by @Jarekt in this edition. --jdx ^Re: 22:32, 6 May 2016 (UTC)

that was edit request by user:sarang. I can not fix it right now, if something is broken please undo my edit --Jarekt (talk) 01:35, 7 May 2016 (UTC)

Sorry, at the moment it is in a temporarely not-well-working state, due to major adjustments. The repair will occur today when the sandbox is ready tested and I ask Jarekt to do the edit. sarang♥사랑 05:29, 7 May 2016 (UTC)

---

{{Edit request}} Image generation/sandbox has now passed all tests and should be copied (as-it-is). Afterwards I will maintain the docu. sarang♥사랑 13:31, 7 May 2016 (UTC)

 Done Checked as few files, seems to be working just fine. --Hedwig in Washington ^(mail?) 00:06, 8 May 2016 (UTC)

---

I just had a look at the template— it seems it is now correctly marking files as valid with the "v" parameter (yay! Thank you!) but could we still get the explanation of the "v" added to the template description? Because it still isn't there. Thanks! KDS4444 (talk) 00:27, 8 May 2016 (UTC)

@KDS4444: Thanks to Hedwig we have now the corrections, and I tried to document everything - in special the use of the v. Please look at the new paragraph for the description! If anything needs a better explanation, just tell me. Thank you, sarang♥사랑 06:09, 8 May 2016 (UTC)

Hedwig in Washington is a dream. Thanks to all of you for helping fix this issue! KDS4444 (talk) 12:24, 2 June 2016 (UTC)

Other tool / graphic

How do I specify "Other tool" which creates a graphic, not a vector image? I tried {{Image generation|O|n|name=foo}} but always get "This vector image was created with foo". – Jberkel (talk) 13:04, 25 May 2016 (UTC)

Hello @Jberkel this template is only for vector images. ↔ User: Perhelion 12:37, 2 June 2016 (UTC)

It would of course be possible to expand the template; but at the moment I cannot see an advantage to tag raster graphic files that they are created with an unknown tool - while for vector graphics it is another thing, to mark them valid or invalid. If somebody shows me a reason that there is a need, e.g. to display the source code, I will make the expansion. sarang♥사랑 08:22, 11 July 2016 (UTC)

More than one program?

Can this template express that a file has been created with two different tools? I have many files (e.g. these) that are created with Python and with bin2svg. If not, I would like to revert Template:Created with bin2svg back to its earlier stage, where it shows only one box, and not the one for SVG validity. Greetings, Watchduck (quack) 23:06, 29 June 2016 (UTC)
@Sarang: , did you see this? Watchduck (quack) 13:32, 10 July 2016 (UTC)

Hi Tilman, now I got it, thank you. It was not planned to show more than one (e.g. the most essential) program if several programs are used to create an image. As at this example it can be varied, esp. when source code should be shown.

At the moment source code can only be displayed with Python, but not with bin2svg; if there is a need, the latter can be expanded to display the python source code. Because AFAIK bin2svg uses python, there may be no need to express it in special? But, if I am convinced that it will bear a helpful information, I will care for the possibility to somehow tag a file with more creating tools. Maybe an additional parameter for bin2svg, creating the python tag and categorizing it, is what you want? sarang♥사랑 08:22, 11 July 2016 (UTC)

So, you think you're probably not doing it right, but you "care" so much you'll only fix it if "you are convinced". No arrogance there, then... Stop abusing the word "care", please. I'm very close to asking for you to be prevented from these edits entirely. Begoon - talk 16:26, 11 July 2016 (UTC)

@Begoon: I have no issue with Sarangs statement. He is not doing it wrong, nor did he imply that he does. Not every feature request will or should be turned into a feature.

@Sarang: If you know no other cases where people use two programs, don't bother. You are right that bin2svg is written in Python, but it is a separate program, and it makes sense to mention it. (I originally wrote it in Matlab, and it could be rewritten in any other language.) As you ask me what I want: I would prefer to use the bin2svg template in the old-fashioned way, where it just makes one little box, without including the validity stuff or anything else. Maybe you could add a plain parameter to it.

Just thinking aloud: I guess your igen template is already too complicated, and you probably expect too much when you expect more than a few people to use it correctly. As far as I have observed, people can't even be bothered to properly categorize their images contentwise, although it would be incredibly easy. The average user does not care about image creation, and will almost certainly not spend any time with the documentation. The simple old inkscape or commonist or valid SVG templates were at least more likely to be used. Watchduck (quack) 21:18, 11 July 2016 (UTC)

@Sarang: I think the correct way is to nest the smaller program in the box for the bigger one (see here), so other small programs could be listed alongside with it. Please just give me some way to remove the validity box from Template:Created with bin2svg. Watchduck (quack) 11:46, 21 July 2016 (UTC)

@Watchduck: Hi, I gave it a try with 3-ary Boolean functions; cube permutations; 0.svg; it needs to be brought into a better format, without the 2^nd "valid", and all of that with a very simple template usage. I am thinking that {{Bin2svg}} can contain all of them (bin2svg, python, commonist and whatever you want) either automatically (without any parameter needed) or variable with a very simple parameterizing. How about that? sarang♥사랑 17:59, 21 July 2016 (UTC)

I actually found the nesting quite good. Please think about two things that may not seem important now, but may be in the future:

• bin2svg may be used with a different language, e.g. Matlab, in which it was originally written. (E.g. this file was not created with Python.)
• There could be other little programs, that should be listed alongside bin2svg - also nested in the Python box.

So I think the future-proof solution is the nesting as it was. Actually all I want from you right now is the ability to make a plain bin2svg box without the validity box. Watchduck (quack) 18:32, 21 July 2016 (UTC)

This can be done. There are two different things not necessarily fixed together: (1) showing boxes, (2) proper categorizing. Displaying boxes can be suppressed if desired, but categories should always reflect the current state.

As far as I understand bin2svg is the "leading" tool, so I suggest that it is shown on first position. When it uses other creation tools they can be shown or not, but should be reflected by categorizing. Validity box can be shown or not, but when then of course only once.

At the moment by bin2svg the validity is implied (because you create only W3C-valid SVG); IMHO it should be shown by the box, but that is not a dogma and the display can be suppressed.

Can a single file have more than one other program you think useful to show and/or categorize? Or it's either Matlab or Python? Or something else? Is there always another tool to mention? Will there be something like secondary and tertiary tools? Does Python also need to show secondary tools? May be a cascadic sequence that a file is created with bin2svg that uses Python which itself uses somthing else?

Should bin2svg display source code? I will offer you my suggestions as soon as I know enough. sarang♥사랑 05:44, 22 July 2016 (UTC)

The primary tool in this case is clearly Python. Bin2svg is used by it, thus secondary.

I might write other little programs (secondary tools), e.g. one for creating arrows.

Validity is not implied. A file like this could easily contain an Inkscape error.

Of course there can be the weirdest combinations, and that's why I think that a simple list of simple templates is actually the best way to do this. Look at this file. Three simple boxes created by three simple templates. There is not really a primary tool in this case.

Maybe we should forget that whole nesting thing. It's just too complicated and unlikely to be used correctly by more than a few people. And it wrongly suggests that there is always a primary tool.

I think it would be great if you just equip the Igen template with the ability to display a list of any other templates, and make sure that the validity box is shown only once.

BTW: Just because source code is available, does not automatically mean, that it should be shown on the page as part of the template. Both the Python and the POV-Ray source for the linked image are on Pastebin. I would never put so much code on a file description page. Greetings, Watchduck (quack) 00:27, 24 July 2016 (UTC)

@Watchduck: Hi Tilman, now I can offer you to add every desired tool to the file description, without the W3C box but with correct categorizing. Just specify the first or main one, and then add as many of SVG created with ... templates as you like, each with the parameters |v|vo=n (and more parameters if needed; "v" is for the category, and "vo=n" suppresses the W3C). For adding use e.g. the T= parameter. Example

 

This graphic was created with Python.

 

This file was uploaded with Commonist.

 

This table was created with bin2svg by v.

 

This diagram was created with MATLAB by v.

 

This map was created with OpenOffice.org by v.

 

This vector image was created with CorelDRAW by v.

 

This vector image was created with Asymptote by v.

 

This vector image was created with Scribustypeset by v.

 

This vector image was created with QGIS by v.

 

This vector image was created with Visio by v.

 

This vector image was created with MetaPost by v.

 

This plot was created with mplwp, the Matplotlib extension for Wikipedia plots by v.

 

This plot was created with Matplotlib by v.

 

This structural formula was created with Name2Struct - CS ChemDraw Ultra by v.

 

This plot was created with Gnuplot by v.

 

This structural formula was created with Vim by v.

See also parameters "T". If you need more information or template functions, just tell me. sarang♥사랑 05:32, 20 August 2016 (UTC)

More tags

(moved from user talk page)

Hallo - gute Idee, diesen Giganten mit einer Editier-Sperre zu versehen. Ich habe eine Bitte: kannst Du unter "Other tags" bitte noch das Template:TracedSVG einfügen. Macht das Sinn an dieser Stelle? -- MaxxL - talk 08:23, 28 July 2016 (UTC) PS: So langsam kann ich mich wieder in die Anwendung einarbeiten. Die Varianten scheinen ja schier unendlich.

Macht durchaus Sinn - alles was mit der SVG-Erzeugung zu tun hat soll hier zusammengefasst werden. Natürlich kann ich auch dafür (und für noch viel mehr) Kurzcodes ausdenken, die dann eine (vielleicht etwas reduzierte) Box darunterstellen. Das macht die Vorlage dann allerdings noch etwas komplexer! Jedes nicht allzuoft gebrauchte tag kann mit dem Parameter t= zugefügt werden; T= macht dasselbe mit "clear" wenn erforderlich. Siehe das Beispiel in deiner Coat of arms of Fairfax County, Virginia.svg, und die Beschreibung in der Vorlagenduku mit dem Beispiel nach Additional notes kurz vor Parameter table. mfg sarang♥사랑 08:47, 28 July 2016 (UTC)

Vielen Dank für die prompte Bedienung. Ich halte dann mal weiter die Augen offen und studiere die Anwendung weiter. Heute fange ich mal an,. meine Uploads rückwärts mit den Templates zu versehen. Dabei ist der Rechercheaufwand zu den Quellendaten größer als der Gestaltungsaufwand, aber es muss ja gemacht werden. -- MaxxL - talk 08:56, 28 July 2016 (UTC)

Sehr löbliches Vorhaben! Ich weiss dass es viel Aufwand ist, aber wie du sagst sollte es sein. Zumindest was {{Igen}} betrifft, gibt es da ein neues Werkzeug zur Vereinfachung. Wenn dich das interessiert sag ich dir gerne mehr dazu. sarang♥사랑 10:45, 28 July 2016 (UTC)

Jetzt bin aber erstmal verwirrt. In der Beschreibung File:Eco Pfad Kloster Hasungen Logo.svg taucht eine Anmerkung auf: This SVG file uses embedded text that can be easily translated using this automated tool. Learn more.. Da ist kein TEXT-Element im Code. -- MaxxL - talk 15:45, 28 July 2016 (UTC)

War falscher Parameter, es enthält vielmehr "path text". Gut dass du es gemerkt hast... sarang♥사랑

Admin required

{{Edit request}} {{ping|Hedwig in Washington|Revent}} After more than three months a lot of maintenance has become necessary. After many tests of the new code it should now get a go.
Please replace the complete code of {{Image generation|this template}} with that of {{Image generation/sandbox}}. Thank you sarang♥사랑 13:33, 17 August 2016 (UTC) {{ping|Morgankevinj}} Thank you for your change on 08-21 of my request from 08-17. AFAIK "technical" requests are such needing an admin with special knowlwdge, e.g. Java. My request affords nothing than the admin rights to edit a page from which I am locked off, and the skill of copying some preprepared code. The code changes are tested and the admin does not need to check anything. I would have appriciated when you had modified the template! sarang♥사랑 12:24, 21 August 2016 (UTC)

 Done MorganKevinJ^(talk) 00:06, 23 August 2016 (UTC) 000000 Thanx sarang♥사랑 11:46, 23 August 2016 (UTC)

Revert please

{{Sudo}} @Morgankevinj: Please revert, the inclusion of the invalid html tag <div/> appears to be causing pages to end up in Category:Pages using invalid self-closed HTML tags. Sarang please review your sandbox. — xaosflux ^Talk 21:01, 23 August 2016 (UTC)

 Done Also left msg here. --Hedwig in Washington ^(mail?) 00:53, 24 August 2016 (UTC)

 Acknowledged MorganKevinJ^(talk) 01:29, 24 August 2016 (UTC)

@Sarang: Please review my edit to the sandbox MorganKevinJ^(talk) 02:30, 24 August 2016 (UTC)

Please note, in section T3 there still appears to be a self-closing div tag in the sandbox. — xaosflux ^Talk 03:02, 24 August 2016 (UTC)

That is an HTML comment so it should not cause a problem. However the comment may mean that the code there generates a div tag so I want Sarang to look in to that first. MorganKevinJ^(talk) 04:43, 24 August 2016 (UTC)

@Morgankevinj: Thank you for your edit of the sandbox. Sorry this error happended... either I did not test this very special case, or I didn't see the message about the self-close. Thank you also for reverting. Now it is repaired - would you please copy again the content of the sandbox. sarang♥사랑 16:50, 24 August 2016 (UTC)

 Done MorganKevinJ^(talk) 21:26, 24 August 2016 (UTC)

Looking good now (no category flooding! ) — xaosflux ^Talk 03:45, 26 August 2016 (UTC)

About categorizing

• Categorizing by a template gives more flexibility for possible future changes: changing at one point inside the template alters all transclusions. On the other hand, with the tool Cat-a-lot individual changes are possible. Both changing possibilities can be used with VFC.
• This considerations influenced the construction of this template: Most categories are selected by it and by the "Created with ..." templates and its subtemplates. If a category exists and it seems useful, files are assigned to it.
• The template is assigned to tag everything belonging to the file creation. It can be discussed whether quality assessments belong to creation, or not; anyway the possibility is offered to tag it with the template.
• It will be possible to expand the template for more shortcut categorizings even with not such a direct connection to the file creation. Shortcuts are fine - but too many of them are not an advantage.
• In the commons exist categories of somehow dubious advantage: IMHO it is of not much use to show which tool was used for uploading, or to specify that a file does not require any localization.

sarang♥사랑 05:44, 1 September 2016 (UTC)

t= broken?

{{Igen|U|v|+|!|t={{RetouchedPicture|1=Cropped}}}} breaks this for me recently. 80.221.159.67 14:07, 5 September 2016 (UTC)

@Sarang: anything to do with recent changes. --Jarekt (talk) 22:06, 5 September 2016 (UTC)

It is still working fine and like it is documented. Boxes created as tables need something like a "newline" before their {|, and this occurs when {{Retouched}} is added. Either insert a {{Clr}} like e.g. {{Igen|U|+|!|t={{clr}}{{RetouchedPicture|1=Cropped}}}} or simply use the upper case "T" like {{Igen|U|!|+|T={{RetouchedPicture|1=Cropped}}}}. Sorry about that inconvenience, sarang♥사랑 05:29, 6 September 2016 (UTC)

Heraldry and Graphic_Lab

With the version of 2016 Oct 03 the tag "gl" for {{Graphic Lab}} can be used. Some abbreviations ease its usage for localized versions (de, en, fr, it).
With this version the tag "()" becomes deprecated; it is still useable for the next future but its usages will be replaced. IMHO the choice for "()" is not such a good idea, and since the code "g[l]" is implemented for graphic lab, it seemed better to use "h[p]" for the heraldic project.
The abbreviations are gd, ge, gf for the national templates. sarang♥사랑 11:11, 3 October 2016 (UTC)

Because all heraldry can also be expressed by the "g[l]" parameters, "h[p]" becomes obsolete and deprecated and is removed. sarang♥사랑 12:59, 30 November 2016 (UTC)

Not a very user friendly template

It takes me quite a bit of screen-staring to figure out where to start with the documentation, and for most other templates it is possible to see what the template does just by looking at the source code which calls it in mainspace/filespace pages. I suggest splitting the template up into simpler parts, or at least avoiding the use of single-character symbols. I'll get there, but other users may be too confused and just give up. --BurritoBazooka (talk) 22:17, 10 November 2016 (UTC)

You are completely right, it is not userfriendly at all. To have everything about file development in one template makes it much too complicated. Users should install the script, which makes the use simple even to novices. If experts want to use more options they can study - and test - how to do that. Sorry sarang♥사랑 12:59, 30 November 2016 (UTC)

More discussions, from user talk pages

Chem. Formeln

Hallo Kopiersperre, du hast neulich wieder eine Reihe guter Grafiken hochgeladen. Leider hast du sie in eine Metakategorie gestellt, deswegen musste ich sie alle wie diese nachbearbeiten. Ea wäre IMHO natürlich besser wenn gleich die "richtige" Kategorie gewählt würde. Freundlicher Gruss sarang♥사랑 09:14, 6 December 2016 (UTC)

{{Igen|c|+|<}} ist extrem kryptisch und damit maximal benutzerfeindlich … --Leyo 12:59, 6 December 2016 (UTC)

Hallo Leyo, es geht auch total unkryptisch; genau dasselbe lässt sich so codieren:

{{Information field|Name=SVG{{I18n/COA|development}}|Value={{Created with ChemDraw|errors=0|vstyle=float:left}} {{TextSVG-s|s=sf}}}}

womit die Benutzerfreundlichkeit offensichtlich gewahrt ist. Verzeih mir bitte dass ich das umständlich finde!

Vom Script erfolgt der Vorschlag folgenden Codes: {{Igen|ChemDraw|+|s=|T={{Text-SVG}}}} was zwar nur marginal besser ist, aber -sehr benutzerfreundlich!- den Anwender weitgehend entlastet und die wesentlichsten Zuordnungen gewährleistet. mfg sarang♥사랑 18:16, 7 December 2016 (UTC)

Da gäbe es auch was dazwischen: Statt {{Igen|c|+|<}} wäre z.B. {{Image generation|ChemDraw|pathtext}} (oder ähnlich) VIEL weniger kryptisch und dennoch einigermassen kurz. Und für Ergänzungen per Script/Bot spielen ein paar Zeichen mehr ja eh keine Rolle. Versuche dich doch bitte mal in andere Benutzer reinzuversetzen. --Leyo 12:57, 27 June 2018 (UTC)

There is no reason against extending the switch list copied below in order to also enabling the use of full names.

|A|a=Illustrator
|B|b=BKchem
|C|c=ChemDraw
|D|d=CorelDRAW
|E|e=ElCompLib
|F|f=Fig2SVG
|G|g=Gnuplot
|H|h=Inkscape-hand
|I|Im|i|im|=Inkscape
|J|j=...
|L|l=LibreOffice
|M|m=MetaPost 
|O|o=Other tool
|P|p=Pstoedit
|Q|q=QGIS
|R|r=R
|S|s=Sodipodi
|T|t=HandSVG
|U|u=Unknown tool
|V|v=Vim
|W|w=Winplot
|X|x=Inkscape-extract

|A|a=Illustrator may become |A|a|Illustrator|illustrator=Illustrator etc. --Leyo 09:08, 6 July 2018 (UTC)

As the explanation in the docu said, and the template code realizes, you can either use one of the shortcuts above, or any other string - it will be preceeded with "Created with " to get a template name. So your above example will work with A, a, Adobe, Illustrator but not with "illustrator" because no uppercasing is done by the template. The user may use full names, with the restriction that they are case sensitive and they will prefixed to become a template name. The case sensitivity is sometimes a bit troublesome, with names like BKchem, ChemDraw but CorelDRAW, and others (neither ChemDRAW nor CorelDraw will work!). -- sarang♥사랑 14:53, 7 July 2018 (UTC)

Well, using {{lc:text}} or {{uc:text}} would solve this issue. --Leyo 21:11, 7 July 2018 (UTC)

---

@Leyo: Your desire depends just the present abbreviations - the other tool names can remain as-they-are,
they need to be specified case-sensitive (e.g. "perl" or "Dia" or "GIMP", other cases remain unknown).
In the same way that it is necessary to specify tool names without Igen correctly, it must be with Igen - just that the following list will tolerate every case (but no other errors):

.... {{#switch:{{lc:{{{1|}}}}}
|a|a$|ia|adobe|illustrator=Illustrator
|b|bkchem=BKchem
|c|chemdraw=ChemDraw
|d|coreldraw=CorelDRAW
|e|elcomplib=ElCompLib
|f|fig2svg=Fig2SVG
|g|gnuplot=Gnuplot
|h|inkscape-hand=Inkscape-hand
|i|im|inkscape|inkscape-important=Inkscape
|j=...<!--
   k -->
|l|libreoffice=LibreOffice
|m|metapost=MetaPost <!--
   n -->
|o|other tool=Other tool
|ooo|openoffice|openoffice.org=OpenOffice.org
|p|pstoedit=Pstoedit
|q|qgis=QGIS
|r=R
|s|sodipodi=Sodipodi
|t|text editor|handsvg=HandSVG
|u|unknown tool=Unknown tool
|v|vim=Vim
|w|winplot=Winplot
|x|inkscape-extract=Inkscape-extract
|-=-

Do you want any more changes?

To avoid misunderstandings

the template accepts full names, and the script proposes the full names; it is just possible to use also abbreviations. When an abbreviation is used, each novice user can see what the template has generated from it, without necessity to study the templates documentation. IMHO it is much more essential to get a well formatted description page displayed, than to care for a fluent readability of its source. -- sarang♥사랑 23:10, 1 August 2018 (UTC)

I support the change that you proposed based on my comments. Thanks.

There are situations, in which an image has to be replaced. If the Image generation template has very cryptic parameters, this may not be done correctly. It is also helpful not to have cryptic parts in the file description page source text, if other changes to that page are done by inexperienced users. --Leyo 23:00, 2 August 2018 (UTC)

Users which are too inexperienced will always have their difficulties to edit correctly; but of course they can be helped: either by giving good documentation with clarifying descriptions and explanations (if these users read them!), by making templates parameters self-explaining (ok, may be I missed that point), or by offering a tool that does all (or most) of the investigation how an image had been generated.

We have such a good tool, and it is easy to use. A minimum of experience is sufficient to work successful with the script.

Of course, it is always more difficult to describe image generation afterwards than it would have been for the creator itself; later it can be done just for best faith.

To help the less experienced users, I am thinking of another support. One way works well: the template expands very few parameter characters to a generation description which in most cases is translated in many languages (for some languages translation help is searched); the other way can be a tool which converts items offered in a check list to the parameters. I am not quite sure whether this will be helpful in reality; it will be another tool unknown to the inexperienced and novice users. Just in one case I see an advantage: something like a pop-up window which shows all possible topics, allowing to select with a simple tick the desired one. How about that? -- sarang♥사랑 08:50, 26 August 2018 (UTC)

Kryptik

Hallo Perhelion, wie wir wissen gibt es nicht nur Fans für unsere Aufräumbemühungen. Die deutliche Kritik der Gegner finde ich durchaus berechtigt - aber ich habe keine rechte Idee, wie ihnen entgegenzukommen wäre. Es liessen sich zwei Ansatzpunkte unterscheiden: die Eingabe zur ev. Ergänzung des Script-Edits, und die Leserlichkeit des erzeugten Codes; die angezeigte Ausgabe lässt IMHO nichts zu wünschen übrig? Dein Script erzeugt weitgehend leserlichen Code, während mein Extremismus von Vertretern der altehrwürdigen OMA angefeindet wird. Ich finde es besser die descriptions kurz zu halten - lange Texte machen sie nicht unbedingt leserlicher.
Die Einordnung in komplexe Kategoriestrukturen erfordert eine komplexe Beschreibung; die Kritik scheint sich nicht an die Komplexität der Strukturen zu richten sondern an meinen Versuch, komplexe Zuordnungen stark vereinfacht und abgekürzt darzustellen. Tatsache ist dass der Umgang mit Igen ohne eine gewisse Einarbeitung unverständlich bleibt. Ich habe unlängst eine ausführliche und komplette und sortierte Parameterreferenz erstellt, wo alles nachgelesen werden kann, aber nach meiner Erfahrung werden Dokumentationen eher nicht gelesen. Das scheint mit Sicherheit auch beim User & Admin Leyo der Fall zu sein.
Hast du vielleicht einen konstruktiven Vorschlag? sarang♥사랑 08:55, 8 December 2016 (UTC)

Hallo Sarang, auf Anhieb nicht, derart Bedenken habe ich allerdings auch schon kommen sehen. Ich werde morgen mal darüber nachsinnen, ich bin recht müde... (von der Woche) LG ↔ User: Perhelion 00:29, 9 December 2016 (UTC)

Der oben bereits erwähnte User & Admin Leyo scheint jeder Änderung solcher Art feindlich gegenüberzustehen. Sogar die automatische script-Anpassung der Parameternamen missfällt ihm. Jetzt muss ich noch darauf achten dass ich keine Dateien von ihm kategorisere!

Hätte ich statt |other fields={{Igen|u|+|s=sf}} die Langform |Other fields={{Information field|Name=SVG{{I18n/COA|development}}|Value={{Created with Other tool|errors=0|vstyle=float:left|subcat=:Structural formulas}}}} oder etwas abgekürzt |Other fields={{InFi|SVG{{I18n/COA|development}}|{{Other tool|v|vs=fl|sub=:Structural formulas}}}} geschrieben - er hätte sicher auch angemeckert, dass es zu unleserlich und zu kryptisch ist... Dabei fehlt hier noch das Kategorisierungs-tag für path_text ("<" bezw. "{{TextSVG-s|s=sf}}").

Ich denke es ist völlig unmöglich es allen recht zu machen. Es bleibt lediglich zu versuchen es möglichst gut zu machen, und dabei die Bedürfnisse der Mehrheit von Normal-usern im Blick zu behalten. Image generation ist entwickelt worden um die Kategoriedifferenzierung zu vereinfachen - dabei sind Kategorien den meisten recht egal! Nun gut, ich mache halt weiter, und achte darauf keine Leyo-Dateien anzufassen, bleiben diese eben unkategorisiert. sarang♥사랑 11:51, 12 December 2016 (UTC)

@Sarang: Hm ja, dann füge doch bei ihm die ausführliche Form ein. :P Meinst du ich sollte dafür einen extra Button schaffen? PS: Das mit Category:Uploaded with UploadWizard hat sich nun auch erl. Auf jeden Fall wollte ich das Script dahingehend erweitern Syntax-Formatierungen auch ohne API-Anfrage (ans W3, wenn schon ausgeführt, oder mittels 2. Button) zu erl.!? LG ↔ User: Perhelion 13:45, 12 December 2016 (UTC)

Nein, ich finde wir müssen nicht Sonderbehandlungen für mäkelige Admins einführen! Und komplexere Kategorien benötigen eben komplexere Links, da ist die Langform nun mal nicht auf einen Blick lesbar. Und die Kurzform zu kryptisch. Ich lasse den Leyo und seine Dateien künftig in Ruhe, das ist für mich erledigt.

Wenn du aber meinst es bringt einen heuristisch relevanten Gewinn die Igen-Parameter in der Langform zu verwenden, also statt kurzem den sprecherenden Alias zu bevorzugen (wie dein script es ohnehin meist vorschlägt) und defaults auszuschreiben statt wegzulassen, bleibt noch die Frage ob es jemand zu würdigen weiss wenn du dir diese Zusatzarbeit antust. Ich bin da etwas skeptisch. mfg sarang♥사랑 14:08, 12 December 2016 (UTC)

Siehe auch User_talk:Perhelion/simpleSVGcheck.js#Proposal_for_"Image_generation"

Lua-it the template!

It uses many lines of code. Can them create a Lua version of it? GXXF T • C 13:02, 3 December 2016 (UTC)

The template uses several Lua modules, which reduced the needed code. May be it can be realized with higher efficiency when using Lua. sarang♥사랑 16:26, 8 December 2016 (UTC)

PNG created with Inkscape

As per Commons:Categories for discussion/2012/03/Category:Bitmap from Inkscape, [[Category:Bitmap from Inkscape]] has been moved to Category:PNG created with Inkscape but some files remain in the original category, I think because they've been placed there by this template. Can that please be remedied? Thanks. - Themightyquill (talk) 18:53, 12 December 2016 (UTC)

 Done; I changed the template {{Created with ItB}}, and removed all your cat-a-lot because this had not been the solution. sarang♥사랑 06:08, 13 December 2016 (UTC)

Created with CorelDRAW

can be detected by the typical document type declaration

• <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">

The script will recognise it automatically. sarang♥사랑 07:22, 15 December 2016 (UTC)

A flawed heuristics. Such DOCTYPE is very common in my SVG works, because some years ago I found convenient to imitate patterns of professional vector software. Rather than to learn myself how and why should I arrange and encode numerous components, including such important as the stylesheet. Most of my works are actually purely hand-made to such extent that all computations in File:Absolute value composition.svg were made in mind when I stared at the text editor screen. Sometimes I help myself with calculator or use some software to generate tedious code (but not files as a whole). Very few of my SVGs were made in any vector software at all. Maybe only 2 or 3 were made in CorelDRAW. Incnis Mrsi (talk) 16:19, 26 June 2017 (UTC)

Thank you for the hint. In the meantime I learned that the mentioned DOCTYPE is often found in CorelDRAW files but does not guarantee that this tool was used. It is difficult to find out the tool when nothing is told by the uploader (of the last version), and I try not to throw all into the "Unknown Tool"-category if I can find out how the drawing was made. -- sarang♥사랑 19:56, 30 June 2017 (UTC)

V like Vim

.. is senseless. There is no difference in results between Vim and other plain text editors. --Itu (talk) 19:26, 2 March 2017 (UTC)

It seems that often it is not Vim but an error in the description - instead of e.g. "Igen|T|+|s=..." it contains "Igen|v|+", the "v" intended for validity but at parameter position 1 it's correctly interpreted for "Vim". -- sarang♥사랑 20:29, 30 June 2017 (UTC)

cat= a.k.a. c=

Existence of this parameter is documented, whereas its values are not. I could deduce the list of possibilities analyzing the code, browsing pages, and looking for maintenance categories… but aren’t developers willing fix the manual first? Incnis Mrsi (talk) 15:51, 26 June 2017 (UTC)

Its values are documented, in the box; the description (said: category/categories, complete with the brackets; suppress with c=-) says now: category/categories, complete with brackets (and sorting), or without; or suppress with c=- / plain text without brackets becomes completed with [[Category: ]]. This information is not repeated in the "Reference of all parameters" where just a shorter note says that categorization can be changed or suppressed.

These short descriptions tell all the facts. The values can be e.g. cat=[[Category:xyz]] or cat=[[Category:abc]] [[Category:def]][[Category:hij]]; suppression of automatic categorization is possible with cat=-. Any other text without the brackets [[Category:...]] is completed as above.

I know that the template has many many parameters and the documentation is not easy to read. The template offers too many possibilities; but the standard usage (tool, validity, subcat/topic) is not very difficult. And with Perhelions script it is quite easy. -- sarang♥사랑 19:39, 30 June 2017 (UTC)

And the other Template:File generation description (with only almost all parameters) is easier to use, hopefully – but with much more typing needed. -- sarang♥사랑 16:37, 5 September 2019 (UTC)

If no tool is added

If, as on File:Spiegel-Online-Logo.svg, no tool is added to the template ({{Igen||+|s=tl}}) is it possible for the template not to default to Inkscape, and just display the "valid svg" instead. --Jonatan Svensson Glad (talk) 12:36, 1 July 2017 (UTC)

+1 I'm also not really happy with the current situation, to make make one preferred tool as default without any statement. -- User: Perhelion 13:43, 1 July 2017 (UTC)

A useful default could be "u" (for unknown tool), it will create "Other tool" but with the textual hint that the tool is not known. When the script will pre-set that "u" anytime when it cannot decide for another tool, everything will be fine. I defaulted then tool with Inkscape, and the error count with zero, because the predominant cases are valid Inkscape; so {{Igen|+}} will often be a good choice. If somebody preferes it a bit more talkative, the same can be expressed like e.g. {{Image generation|Inkscape|v|+}}.

@Perhelion: Kopierst du bitte wieder mal die sandbox - ich musste wegen Graphic workshop erweitern. Danke -- sarang♥사랑 17:55, 1 December 2017 (UTC)

@Sarang and Josve05a: Short is good but user friendliness has much more importance. I'm with Jonatan Svensson, this all should be traceable and suggestive. As others have said, this is going to cryptic (now we are too much Commons template nerds). I'm against Inkscape as default and/or against optionality to this tool parameter, except "unknown tool" or only valid SVG is meant. Greetings (PS: done) -- User: Perhelion 13:05, 3 December 2017 (UTC)

Perhelion, I appreciate your sight of view, and I agree that I made things much to cryptic for others to understand. Instead of working with the default Inkscape it might have been better to set at least an I, easy to expand by VFC to 'Inkscape' - much easier than to add it now (but not impossible!). We would not have any problem when every uploader of a vector graphic would have specified tool & validity; tagging it afterwards, with poor knowledge, is second choice. Your script helps a lot and eases that belated tagging, but before we had it I tried to minimize the typing needs - and to avoid the bloating of the file descriptions. -- sarang♥사랑 07:40, 4 December 2017 (UTC)

Unclear explanation in s=

I think the explantation on Template:Image_generation could be improved:

„With a one-letter-code for s= the topics-subcategory may be defined, as :CoA, :Diagrams, :Flags, :Icons, :Logos, :Maps, :Signs, :Unicode, :Trigonometry,“

– Template:Image_generation

• Which letter? The capital ones? Or the first one?
• With colon?
• captital letter or lower case?
• The linked sites Template:Igen/top, Template:Igen/sub, Template:Image_generation#Subcategory_specification makes it even more confusing.

Maybe something like

shortcut	0topic
s=c	Coat of arms
s=d	Diagrams
s=f	Flags
s=i	Icons
s=l	Logos
s=m	Maps
s=s	Seals
s=t	Trigonometry
s=u	Unicode
s=v	Signs {Verkehrszeichen)
s=y	Symbols

should be added to Template:Igen/top?

 — Johannes Kalliauer - Talk | Contributions 08:51, 20 January 2018 (UTC)

You are welcome to edit Template:Igen/sub to add docs. I don’t think that {{Image generation/doc}} should be ridden with details of secondary importance. Incnis Mrsi (talk) 09:07, 20 January 2018 (UTC)

The (small) problem is that Igen/sub and Igen/top are frequently expanded, and when a swift edit occurs a documentation will be also in need of an update; now, with checking the source code, you are always up-to-date. But as a mere example for (more) shortcuts the stub of a docu would be fine! -- sarang♥사랑 16:25, 27 March 2018 (UTC)

---

The codes for the parameters s= and w= (Some codes exist only in one of both templates!) as of 09:09, 09 September 2018 (UTC)
(w= is the topic only for textual description, s= is the topic fur subcategorizing - and for the text if no w= is specified)

Presorted by code

code	subcat	topic (en)
7	:Digits	digit
a	:Arrows	arrow
acm	:Australian census maps	census map
ai	:Antu icons	icon
b	:Buttons	button
bi	:BSicons	BSicon
bri	:Breeze icons	icon
bs	:Barnstars	barnstar
c	:CoA	coat of arms
ce	:CoA elements	CoA element
ch	:Charts	chart
ci	:Crystal icons	icon
cp	:Church plans	church plan
cr	:Crowns	crown
cti	:Creative tail icons	icon
d	:Diagrams	diagram
dr	:Drawings	drawing
e	:Emblems	emblem
ed	:Electrical diagrams	diagram
eh	:Ecclesiastical heraldry	ecclesial CoA
ei	:Echo icons	icon
em	:Emblems	insignia
eq	:Structural formulas	chemical equation
esd	:ElectronSD	diagram
et	:Elegant themes icons	icon
ey	:Electrical symbols	symbol
f	:Flags	flag
ffi	:Football flag icons	flag icon
fi	:Flag icons	icon
fm	:Flag maps	flag map
g	:Geometrics	geometry
ggg	:World maps (gggs)	world map
gi	:Gnome icons	icon
gl	:Glyphs	glyph
gv	:Gigillo signs	sign
hd	:Hasse diagrams	diagram
i	:Icons	icon
jc	:Japanese crests	emblem
je	:Japanese emblems	emblem
jf	:Japanese flags	flag
l	:Logos	logo
lb	:Labels	label
lp	:License plates	license plate
m	:Maps	map
mbs	:Maps by User:Sémhur	map
mlw	:CoA by MaxxL	coat of arms
mn	:Musical notations	notation
♫	:Musical notations	notation
ni	:Nuvola icons	icon
npi	:Noun project icons	icon
o	:Orders	military insignia
oc	:OpenClipart	drawing
oi	:Oxygen icons	icon
p	:Pictograms	pictogram
pi	:Padlock icons	icon
pom	:Maps by UserPomfuttge	map
r	:Roundels	roundel
rf	:Rainbow flags	flag
rm	:Royal monograms	monogram
s	:Seals	seal
sd	:Shell Diagrams	diagram
sf	:Structural formulas	structural formula
sig	:Signatures	signature
sp	:Sport pictograms	pictogram
t	:Trigonometry	trigonometry
tai	:Tango arrow icons	icon
ti	:Tango icons	icon
tl	:Text logos	text-logo
ts	:Typesets	typeset
u	:Unicode	Unicode character
v	:Signs	sign
wm	:World maps	world map
wmd	:World destination maps	world map
wp	:Patterns	pattern
y	:Symbols	symbol

Presorted by subcat

code	subcat	topic (en)
ai	:Antu icons	icon
a	:Arrows	arrow
acm	:Australian census maps	census map
bs	:Barnstars	barnstar
bri	:Breeze icons	icon
bi	:BSicons	BSicon
b	:Buttons	button
ch	:Charts	chart
cp	:Church plans	church plan
c	:CoA	coat of arms
mlw	:CoA by MaxxL	coat of arms
ce	:CoA elements	CoA element
cti	:Creative tail icons	icon
cr	:Crowns	crown
ci	:Crystal icons	icon
d	:Diagrams	diagram
7	:Digits	digit
dr	:Drawings	drawing
eh	:Ecclesiastical heraldry	ecclesial CoA
ei	:Echo icons	icon
ed	:Electrical diagrams	diagram
ey	:Electrical symbols	symbol
esd	:ElectronSD	diagram
et	:Elegant themes icons	icon
e	:Emblems	emblem
em	:Emblems	insignia
fi	:Flag icons	icon
fm	:Flag maps	flag map
f	:Flags	flag
ffi	:Football flag icons	flag icon
g	:Geometrics	geometry
gv	:Gigillo signs	sign
gl	:Glyphs	glyph
gi	:Gnome icons	icon
hd	:Hasse diagrams	diagram
i	:Icons	icon
jc	:Japanese crests	emblem
je	:Japanese emblems	emblem
jf	:Japanese flags	flag
lb	:Labels	label
lp	:License plates	license plate
l	:Logos	logo
m	:Maps	map
mbs	:Maps by User:Sémhur	map
pom	:Maps by UserPomfuttge	map
mn	:Musical notations	notation
♫	:Musical notations	notation
npi	:Noun project icons	icon
ni	:Nuvola icons	icon
oc	:OpenClipart	drawing
o	:Orders	military insignia
oi	:Oxygen icons	icon
pi	:Padlock icons	icon
wp	:Patterns	pattern
p	:Pictograms	pictogram
eq	:Structural formulas	chemical equation
rf	:Rainbow flags	flag
r	:Roundels	roundel
rm	:Royal monograms	monogram
s	:Seals	seal
sd	:Shell Diagrams	diagram
sig	:Signatures	signature
v	:Signs	sign
sp	:Sport pictograms	pictogram
sf	:Structural formulas	structural formula
y	:Symbols	symbol
tai	:Tango arrow icons	icon
ti	:Tango icons	icon
tl	:Text logos	text-logo
t	:Trigonometry	trigonometry
ts	:Typesets	typeset
u	:Unicode	Unicode character
ggg	:World maps (gggs)	world map
wm	:World maps	world map
wmd	:World destination maps	world map

Presorted by English translation of topic

code	subcat	topic (en)
a	:Arrows	arrow
bs	:Barnstars	barnstar
b	:Buttons	button
ch	:Charts	chart
cp	:Church plans	church plan
ce	:CoA elements	CoA element
c	:CoA	coat of arms
eq	:Structural formulas	chemical equation
mlw	:CoA by MaxxL	coat of arms
eh	:Ecclesiastical heraldry	ecclesial CoA
cr	:Crowns	crown
d	:Diagrams	diagram
ed	:Electrical diagrams	diagram
esd	:ElectronSD	diagram
hd	:Hasse diagrams	diagram
sd	:Shell Diagrams	diagram
7	:Digits	digit
dr	:Drawings	drawing
oc	:OpenClipart	drawing
e	:Emblems	emblem
jc	:Japanese crests	emblem
je	:Japanese emblems	emblem
f	:Flags	flag
jf	:Japanese flags	flag
rf	:Rainbow flags	flag
ffi	:Football flag icons	flag icon
fm	:Flag maps	flag map
g	:Geometrics	geometry
gl	:Glyphs	glyph
ai	:Antu icons	icon
bri	:Breeze icons	icon
bi	:BSicons	BSicon
cti	:Creative tail icons	icon
ci	:Crystal icons	icon
ei	:Echo icons	icon
et	:Elegant themes icons	icon
fi	:Flag icons	icon
gi	:Gnome icons	icon
i	:Icons	icon
npi	:Noun project icons	icon
ni	:Nuvola icons	icon
oi	:Oxygen icons	icon
pi	:Padlock icons	icon
tai	:Tango arrow icons	icon
ti	:Tango icons	icon
em	:Emblems	insignia
lb	:Labels	label
lp	:License plates	license plate
l	:Logos	logo
tl	:Text logos	text-logo
acm	:Australian census maps	census map
m	:Maps	map
mbs	:Maps by User:Sémhur	map
pom	:Maps by UserPomfuttge	map
o	:Orders	military insignia
rm	:Royal monograms	monogram
mn	:Musical notations	notation
♫	:Musical notations	notation
wp	:Patterns	pattern
p	:Pictograms	pictogram
sp	:Sport pictograms	pictogram
r	:Roundels	roundel
s	:Seals	seal
gv	:Gigillo signs	sign
v	:Signs	sign
sig	:Signatures	signature
sf	:Structural formulas	structural formula
ey	:Electrical symbols	symbol
y	:Symbols	symbol
t	:Trigonometry	trigonometry
ts	:Typesets	typeset
u	:Unicode	Unicode character
ggg	:World maps (gggs)	world map
wm	:World maps	world map
wmd	:World destination maps	world map

currently not working

Edit request please change (in line 7) --><span style="float:left;height:1.2em;vertical-align:middle"><!--   to --><span style="vertical-align:middle"><!-- .

{{#if:{{{C|}}}|{{InFi|{{I18n/COA|tincture}}|{{{T0|{{{t0|}}}}}}<!--
  -->{{Tincture|{{{C}}}|tc={{{Ct|}}}|cat={{{Cc|}}}|s={{{s|}}}|k={{{k|}}}}}}}}}<!--

-->{{{{#if:{{{fn|}}}|InFi|{{#switch:+|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}|{{{5}}}|{{{6}}}|{{{7}}}|{{{8}}}|{{{9}}}=InFi|Nil2}}}}<!-- 
-->|1={{{fn|{{uc:{{#invoke:File|extension|file={{PAGENAME}}}}}}{{I18n/COA|development}}}}}|2=<!-- 
-->{{#if:{{{T1|}}}|{{clr}}{{{T1}}}|{{{t1|}}}}}<!-- 
--><span style="vertical-align:middle"><!-- 
-->{{{p|{{{P|}}}}}}{{#if:{{{P|}}}|{{clr}}}}<!-- 
-->{{#ifeq:.....

JoKalliauer (talk) 16:59, 24 April 2018 (UTC)

Don’t exactly understand the problem, but the present code is poor because “em” is a unit of width, not height. Height is measured in “ex”. Also, technically it is the 8th line. Incnis Mrsi (talk) 21:24, 24 April 2018 (UTC)

There was a problem with this template (overlapping of text, see User talk:JoKalliauer/Archiv#Neues Problem, in german), it seemes that ?action=purge solved the problem JoKalliauer (talk) 16:36, 25 April 2018 (UTC)

Incnis Mrsi I think here is still the problematic version: Charlotte uptown map.svg (As long as nobody purges it (please don't))JoKalliauer (talk) 18:36, 27 April 2018 (UTC) Ups, does not work any more, with reuploading the page is rerendered. JoKalliauer (talk) 18:51, 27 April 2018 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. JoKalliauer (talk) 18:36, 27 April 2018 (UTC)

Link to program

Right now, the link that appears at the program name in the final template will automatically point to a Wikipedia page. However not all used programs have a Wikipedia page and some probably never will. It would be really helpful if the link can also point to something else, like a Commons page or GitLab for example. --Geek3 (talk) 10:09, 30 May 2018 (UTC)

Asymptote Bug

The Asymptote template doesn't link to the right wiki page for the program. Should link to: w:Asymptote (vector graphics language) See example of bug here: c:File:Colored_neural_network.svg#Summary — Preceding unsigned comment was added by 86.18.4.164 (talk) 10:59, 22 July 2018 (UTC)

 Done (sorry, didn't see it earlier)

This section is resolved and can be archived. If you disagree, replace this template with your comment. -- sarang♥사랑 12:36, 1 August 2018 (UTC)

Transfer request

{{Edit request}} Es war notwendig einiges zu verbessern, machst du bitte wieder einen Transfer- -- sarang♥사랑 12:16, 4 September 2018 (UTC)

 Done Bist du sicher? (bin jetzt off) -- User: Perhelion 12:50, 4 September 2018 (UTC)

Naja, relativ sicher. Danke fur transfer! Und dir eine gute off-Zeit. -- sarang♥사랑 13:02, 4 September 2018 (UTC)

New {{Edit request}}: @Perhelion: ich habe wieder einiges verbessert und begradigt, und kleine Fehler behoben. Ab Mitte Oktober werde ich wieder 6 Wochen weg sein, vielleicht sollte bald transferiert werden - falls doch irgendwas nicht stimmt und nachgebessert werden muss, solange ich noch da bin.
Bez. der Kryptik mangelt es mir an tollen Ideen, wie die zu vermeiden wäre. In seiner Verzweiflung hat der Kryptikgegner unlängst in vielen hundert Dateien den string "Igen" durch "Image generation" ersetzt; erscheint mir nicht so arg sinnhaft und hilfreich, soll mir aber recht sein. Leider sehe ich nicht viele Möglichkeiten, ihm entgegenzukommen. Natürlich kann ich Eingaben mit Langtext-Aliases zulassen, aber die bereits bestehenden Aufrufe bleiben davon unberührt kurz und prägnant; solange sie nicht auch per VFC expandiert werden... und einfacher würde es davon keineswegs! Die Sache mit den "lesbaren" Toolnamen ist auch noch nicht weitergediehen.
Ich weiss nicht, wer damit zu tun hat - ich habe mal Fileicon-svg.png vektorisiert, falls das jemand verwenden will. -- sarang♥사랑 16:58, 30 September 2018 (UTC)

 Done

Current parse time table for Fileicon-svg.svg

NewPP limit report Parsed by mw2238 Cached time: 20181001153928 Cache expiry: 86400 Dynamic content: true CPU time usage: 0.240 seconds Real time usage: 0.325 seconds Preprocessor visited node count: 4374/1000000 Preprocessor generated node count: 0/1500000 Post‐expand include size: 35441/2097152 bytes Template argument size: 10783/2097152 bytes Highest expansion depth: 32/40 Expensive parser function count: 6/500 Unstrip recursion depth: 0/20 Unstrip post‐expand size: 791/5000000 bytes Number of Wikibase entities loaded: 0/400 Lua time usage: 0.086/10.000 seconds Lua memory usage: 1.79 MB/50 MB <!-- Transclusion expansion time report (%,ms,calls,template) 100.00% 291.801 1 -total 97.89% 285.658 1 Template:Information 33.95% 99.066 1 Template:Igen 28.50% 83.154 3 Template:Autotranslate 23.33% 68.073 1 Template:InFi 22.48% 65.610 4 Template:F 20.80% 60.705 1 Template:Attrib 20.34% 59.361 1 Template:Own_based 19.75% 57.620 4 Template:F/name 17.84% 52.071 1 Template:Created_with_HandSVG -->

Als nächstes würde ich mal die Lua-Module einbauen und die Performance vergleichen... -- User: Perhelion 16:21, 1 October 2018 (UTC)

unbestimmte Inkscapedatei

Wenn ich {{Image generation|Inkscape|-1}} schreibe kommt:

 

This W3C-uncheckable vector image was created with another tool.

mir fehlt das Inkscape, oder geht man davon aus, dass Inkscape so was nicht macht?  — Johannes Kalliauer - Talk | Contributions 10:45, 28 October 2018 (UTC)

@JoKalliauer: Wenn uncheckability angegeben ist, immer andere Werkzeuge impliziert. Pbroks13 (talk) 18:37, 15 December 2018 (UTC)

Sorry for using German.

@Pbroks13: Thanks

@Sarang: Is there a reason why "uncheckability" is equal to "other tools"?.

 — Johannes Kalliauer - Talk | Contributions 19:38, 15 December 2018 (UTC)

Die "Fehleranzahl" -1 ist ein Code der (von Igen) verwendet wird, um genau diese Situation zu markieren. Kann naturlich auch von dir manuell gesetzt werden:

Es bedeutet, dass der Validator sich weigert, etwas zu diesem SVG-Code auszusagen. Er verweigert daruber hinaus sogar, den Code anzuzeigen; das ist eine Neuerung (und Verschlimmerung) seit ca. einem Jahr.

Da nichts uber das Werzeug ausgesagt werden kann, wird immer "other tools" eingestellt - was sonst? Ist leider so, liegt an den W3C-Machern. -- sarang♥사랑 19:25, 17 December 2018 (UTC)

Error with link

{{Edit request}} I cannot figure out how to fix this code. Theres an issue with the template {{Igen|g=en}}:

 

This graphic was created with Inkscape.

This image was improved or created by the Wikigraphists of the Graphic Lab (en). You can propose images to clean up, improve, create or translate as well.

Namely, "propose images" sends you to en:Graphic Lab/Image workshop, which I made a redirect to the correct link. How is this fixed? Pbroks13 (talk) 05:42, 14 December 2018 (UTC)

 Done you mean this? -- User: Perhelion 21:56, 24 February 2019 (UTC)

Thank you, Pbroks, for this information. I found an error within the template's code, it is now repaired in the sandbox:

 

This flag was created with Inkscape.

This flag was improved or created by the Wikigraphists of the Graphic Lab (en). You can propose images to clean up, improve, create or translate as well.

I did not test the {{Igen|g=en}}; it's better to use {{Igen|gl}}:

 

This map was created with Inkscape.

This W3C-invalid map was improved or created by the Wikigraphists of the Graphic Lab (en). You can propose images to clean up, improve, create or translate as well.

With the next transfer of the sandbox, the error is repaired and you can write g= with every language code. -- sarang♥사랑 16:36, 4 April 2019 (UTC)

lightened Commonist icon

vs.

@Sarang: You have replaced the original icon File:Commonist.svg with a your new version File:Commonist2.svg (diff), stating on its description page that you "changed the too dark red". To me it looks like you arbitrarily decided to change the icon to someone elses software. Please change it back, unless there was consent from the developers of Commonist.
BTW: Where does the width come from? It looks lousy with 18px, and the other icons have 20px. Watchduck (quack) 14:29, 11 May 2019 (UTC)

I thought that it looked better - but when you dislike it it will be undone; 20px is now restored, and the darker color will be changed back as soon as the new Image generation becomes operational. -- sarang♥사랑 15:12, 11 May 2019 (UTC)

Thanks. The original colors are (almost) the same as in the Commons logo. That makes sense, and is probably intentional. For these tiny icons a cropped version might look better: File:Commonist icon.svg (For those who care: The width came from here.) Greetings, Watchduck (quack) 20:35, 11 May 2019 (UTC)

Many changes

After a substantial redesign of parameter handling, I cannot find anymore errors, and hope that I corrected all of them. {{Edit request}} as usual - Image generation/sandbox to Image generation. -- sarang♥사랑 17:11, 3 June 2019 (UTC)

 Done 4nn1l2 (talk) 20:19, 3 June 2019 (UTC)

{{Edit request}} @4nn1l2: Thank you. After some days I found the first issue: there was a categorizing error, now repaired in the sandbox. -- sarang♥사랑 05:13, 8 June 2019 (UTC)

 Done 4nn1l2 (talk) 18:12, 11 June 2019 (UTC)

Grammar

In German “SVG Editor” is incorrect. It must read “SVG-Editor”. Please fix this. --Leyo 12:24, 25 June 2019 (UTC)

Sorry, I cannot find it. Where had you seen that? -- sarang♥사랑 09:14, 27 June 2019 (UTC)

In File:Cobalt - world production trend.svg. --Leyo 20:55, 8 July 2019 (UTC)

Cat moved

Anyone can edit the code meant to categorise OOjs from Category:Valid SVG created with Text Editor:OOjs UI icons to Category:Valid SVG created with Text Editor:OOUI icons? 大诺史 (Talk/留言/토론/Discussion) 05:10, 30 June 2019 (UTC)  Done Sarangbot (talk) 17:34, 2 July 2019 (UTC)

Parameter "Image"

The template:{{Information}} got finally the required parameter image, making obsolete to abuse in future other fields for descriptions of the image and its howabouts. At the moment it is usable exactly like the other fields, i.e. the "+" parameter is still necessary. It is intended for a later stage that the "+" becomes unnecessary but won't disturb if specified.
Currently without the "+" it does not work correctly, because no {{Information field}} is generated for the values of the "image" field

{{Information |description = description |date = date |source = source |author = author |image = image |permission = permission |other versions = o_versions |other fields = {{InFi|Other fields|o_fields}} }}

DescriptionImage generation/Archive 1 description Date date Source source Author author Permission (Reusing this file) permission Other versions o_versions WWWOther fields InfoField o_fields

DescriptionImage generation/Archive 1	description
Date	date
Source	source
Author	author
Permission (Reusing this file)	permission
Other versions	o_versions
other fields InfoField	o_fields

i.e. id should be like the optional fields permission or other versions – invisible when not specified, and otherwise like all the fields above of it:

• the field name needs to be internationalized, somehow like in {{development}}
• it's irrelevant whether it will have a second linefeed, like the other fields above
• much better adequate reaction would be possible when somehow the template could get information from where it is transcluded
  e.g. the field name ("image" or "other fields" when it is trancluded from {{Information}})

DescriptionImage generation/Archive 1	description to show {{File generation description}}
Date	date
Source	source
Author	author
Permission (Reusing this file)	permission
Other versions	o_versions

Improper highlighting in the invalid SVG message

The highlighting for the invalid SVG message bothers me; the space before the word invalid is highlighted:

The source code of this SVG is invalid.

This happens because there's a space after the template's plainlinks span (which is also used to do the highlighting). The space after should be moved to before, instead. {{InvalidSVG/en}} is what would need to be edited, but it's protected so I can't do it myself. Some of the other translations (such as {{InvalidSVG/es}}) are also affected but not protected; I don't want to change those myself until this one is handled though (in case there's some actual reason why that space should be highlighted). --Pokechu22 (talk) 21:58, 29 March 2020 (UTC)

Sarang corrected the English version back on December 3rd; I've updated all of the foreign-language ones now. {{InvalidSVG/ja}}, {{InvalidSVG/th}}, {{InvalidSVG/zh}}, and {{InvalidSVG/zh-tw}} may need to be double-checked because the rules for spacing may be different in those languages (I didn't add one if there wasn't already one there before). --Pokechu22 (talk) 19:52, 28 December 2020 (UTC)

Two dots

{{Edit request}} Hello, on end of this template are two dots. Can someone fix it? Thanks, --janbery (talk) 18:06, 14 April 2020 (UTC)

@Janbery: Hello. Can you please link to an example? Thanks. Ahmad^talk 04:58, 25 April 2020 (UTC)

@Ahmad: Hi, I see that English version is okay. Mistake is in Czech version of template. Mistake in translation? I don't know, where/how to fix that. Looks like this. Take care, --janbery (talk) 11:19, 25 April 2020 (UTC)

 Done Thank you! Ahmad^talk 12:21, 25 April 2020 (UTC)

unable to add symbol | in the source code

A very useful template to add to provide image generation details. The symbol | cannot be used in the source code text when using the template as it gets interpreted as the beginning of a new key. Is there a protocol that is not documented for this scenario? If not, can there be a protocol on how this can be avoided? For example:

• the |code= should come at the end of the template thus ensuring that all | symbols will be interpreted as part of the code or
• use of two new-line characters to identify the end of code?

Thank you. --Rubber Duck (☮ • ✍) 14:01, 18 May 2020 (UTC)

DrawShield

The DrawShield tool at https://drawshield.toolforge.org places SVG images in the Category:Created with DrawShield. Please could it be added to the template? Charles Matthews (talk) 16:40, 5 July 2020 (UTC)

 Done Charles Matthews: It is now established, see one of your currently 102 files of how to use it. -- sarang♥사랑 13:29, 21 September 2020 (UTC)

Thank you. Charles Matthews (talk) 14:18, 21 September 2020 (UTC)

Lint concern...

Moved to User talk:ShakespeareFan00#Lint concern...

animated SVG

is there a way to specify that the animation commands are linted separately? Arlo James Barnes 00:02, 16 November 2020 (UTC)

"Uncheckable" has an extra dot - need to fix

Using {{Image generation|err=-1}} produces:

 

This W3C-uncheckable vector image was created with another tool.

An extra dot somehow sneaked in after "uncheckable" - and I can't find the subtemplate where this is generated. Please fix if you can. Cherkash (talk) 20:31, 24 February 2021 (UTC)

One of the dots comes from {{InvalidSVG/en}} (when the more arg is not present). Not sure about the other one. --Pokechu22 (talk) 20:35, 24 February 2021 (UTC)

It came from a failure; repaired in the sandbox, will be also in the template soon.

 

This W3C-uncheckable vector image was created with another tool.

. -- sarang♥사랑 10:10, 29 March 2021 (UTC)

I have done a perhaps related edit on {{File generation description}}. --ZandDev (talk) 22:30, 8 October 2023 (UTC)

edit request

Edit request Please copy from oldid 547143444, This eliminates duplicate punctuation marks. -- LaMagiaaa (talk) 15:24, 27 March 2021 (UTC)

@LaMagiaaa: Thank you for your help. The change will be made with the next update of the template. -- sarang♥사랑 10:07, 29 March 2021 (UTC)

Should now be fine since upload from April 10, 2021 -- sarang♥사랑 11:01, 16 April 2021 (UTC)

Grammar

{{Edit protected}} Request: Add a definite article between the first 2 words in the Hungarian translation of the template: „Ez számítógépes grafika (vektorgrafikus kép, címer stb.) … segítségével készült.” → „Ez a számítógépes grafika (vektorgrafikus kép, címer stb.) … segítségével készült.” (Suggestion: {{A(z)}}). Alfa-ketosav (talk) 17:24, 19 June 2021 (UTC)

 Not done You may have this template mistaken for something else. 1989 (talk) 18:21, 1 August 2021 (UTC)

Created with JFreeChart

{{Edit request}} Template:Created with JFreeChart places images in one of the the Category:Created with JFreeChart subcategories. Could it be added to this template please? (if possible using the letter J). vip (talk) 10:16, 25 July 2021 (UTC)

 Done 1989 (talk) 18:14, 1 August 2021 (UTC)

Quality image parameter categorization.

As in Template talk:Igen/qui#Categorization

"Other tool" is not necessarily correct for "uncheckable" files

Currently, e=-1 assumes "Other tool" and cannot be overwritten even if the tool is explicitly specified. This is probably not right and needs to be fixed. Case in point: File:CIA_WorldFactBook-Political_world.svg - it's a file generated by Inkscape, but it's uncheckable (likely due to its size, although it's not explicitly stated why since the server gives a generic 500 error). Cherkash (talk) 00:58, 1 May 2022 (UTC)

@Cherkas: when it is impossible to check the SVG source code, the script is unable yo determine the tool. But I can think it over whether to allow a manual tool specification -- sarang♥사랑 14:29, 20 October 2022 (UTC)

Is there a way to localize the option Important?

Hi, I would like to know how to localize the option Important (e.g. Italian importante instead of important).--Carnby (talk) 20:18, 9 June 2022 (UTC)

The source code of this SVG is invalid due to Python errors

It does not make sense to say, that an SVG source if invalid because of errors in a different language.
No need to fix anything on that file. I just want to point out, that "due to Foo errors" is a bad idea.
This is the code:     {{Igen|^|Python|+|T2={{created with bin2svg|v|vo=n}}|cf=|$}}
Watchduck (quack) 10:31, 25 October 2022 (UTC)

@Watchduck: See the correct ordering of parameters: ^ and + could be positioned anywhere (see note 1), but Python not, so the value of the second field (Python) is the number of validity errors. The correctly interpreted sequence of parameters is:

{{Igen|Python|^|+|T2={{created with bin2svg|v|vo=n}}|cf=|$}}

The first parameter calls {{Created with Python}}, for the complete list of possible values see Category:SVG created with ... templates. --ZandDev (talk) 22:42, 8 October 2023 (UTC)

Subcategory problem with Inkscape-hand

When using igen with Inkscape-hand and subcategory, it adds two categories: one is Category:Valid SVG created with Text Editor and the other is Category:Valid SVG created with Inkscape-hand:Topics. The second one is correctly subcategorized but the first one is not. I would suggest removing the first category because it is not necessary to have the files in both categories at the same time. Xeror (talk) 20:01, 7 January 2023 (UTC)

Wikimedia SVG Chart

@Sarang: bezüglich File:Minor planet count.svg, was ist die Korrekte Syntax für Created with "Wikimedia SVG Chart" ?  — Johannes Kalliauer - Talk | Contributions 17:12, 19 January 2023 (UTC)

@JoKalliauer: Da gibt es keine einzige "Korrekte Syntax"; moglich ist zB

{{Information
|description={{en|1=The numbers of total, numbered, and named {{W|minor planets}} from 1995 to 2013. Produced with data from IAU Minor Planet Center.}}{{zh|1=從1995年至2013年{{Wz|小行星}}總數、已編號小行星數以及已命名小行星數。}}{{ru|1=Общее число, а также число нумерованных и именованных малых планет с 1995 по 2016 годы.}}
|date=2014-01-02
|source=Graph generated from archive statistics by IAU Minor Planet Center, at [http://www.minorplanetcenter.net/iau/lists/ArchiveStatistics.html]。
|author=Graph is own work.
|permission=Freely-available datasets may be redistributed as long as the source for the data is clearly specified.[http://www.minorplanetcenter.net/iau/WWWPolicy.html]
|other versions=Chinese version: 中文版：{{F|小行星數目.svg}}
|other fields={{InFi|SVG Chart|{{SVG Chart/box|1}}}}
}}

oder besser

{{Information
|description={{en|1=The numbers of total, numbered, and named {{W|minor planets}} from 1995 to 2013. Produced with data from IAU Minor Planet Center.}}{{zh|1=從1995年至2013年{{Wz|小行星}}總數、已編號小行星數以及已命名小行星數。}}{{ru|1=Общее число, а также число нумерованных и именованных малых планет с 1995 по 2016 годы.}}
|date=2014-01-02
|source=Graph generated from archive statistics by IAU Minor Planet Center, at [http://www.minorplanetcenter.net/iau/lists/ArchiveStatistics.html]。
|author=Graph is own work.
|permission=Freely-available datasets may be redistributed as long as the source for the data is clearly specified.[http://www.minorplanetcenter.net/iau/WWWPolicy.html]
|other versions=Chinese version: 中文版：{{F|小行星數目.svg}}
}}
{{SVG Chart/box|1}}

ev. noch mit dem source code. War das deine Frage, oder habe ich falsch verstanden? -- sarang♥사랑 09:55, 20 January 2023 (UTC)

Created with Excel

The New version (Since 2013) of Excel can exprot chart to SVG directly, but this Template has no value about it, please add it to the template, thanks. --HFWMan (talk) 04:12, 14 February 2023 (UTC)

@HFWMan: The template doesn't support directly software used for generating images. This job is done by the Created with ... templates. I found {{Created with Microsoft Excel}} which to be used in Igen the first parameter should be Microsoft Excel. I have just created the shortcut {{Created with Excel}}. --ZandDev (talk) 22:49, 8 October 2023 (UTC)

Translation using <switch> vs Toolforge

The documentation says that %s means "the file contains multilingual text using the switch option and it should not be maintained with Toolforge".

Doesn't Toolforge use <switch> fo the translation?

Why not display a link to Toolforge like {{Translate}} does? The RedBurn (talk) 07:46, 28 February 2023 (UTC)

429 Too Many Requests error on validator.w3.org

It seems that validator.w3.org no longer works. I noticed this with my new uploaded files. When I check the file I get a "429 Too Many Requests" error (see this quick video). Sometimes I get redirected to their new validator.w3.org/nu website. Is this happening to everyone or is it just me? If this is happening to everyone, we might have to switch to their new URL which works. Regards Kirilloparma (talk) 19:38, 10 March 2023 (UTC)

I was able to successfully check File:Chess xod45.svg multiple times with this link, but I got a 429 for File:Cities Skylines II horizontal logo.svg this link. Not sure if there's a reason for that though. --Pokechu22 (talk) 20:23, 10 March 2023 (UTC)

Seems that this applies not only to new files uploaded by me or some other participant, but to absolutely all files without exception. Another example. For some unknown reason, the current validator simply does not check them, although it still accepts some old logos. It can be assumed that the current validator is outdated. Regards Kirilloparma (talk) 21:45, 10 March 2023 (UTC)

@Kirilloparma and Pokechu22: By insisting or waiting a bit you can eventually validate the files, but this is a waste of time and patience consuming, especially if there are many. --ZandDev (talk) 22:53, 8 October 2023 (UTC)

Template appears outside of summary sometimes

Made an edit on File:Nuvola apps bookcase pastel.svg where I changed

{{Igen|+}}

to

{{Igen|IA}}

The template appeared in its own section of the file summary description under "SVG development" initially, after the edit it moved outside of the summary entirely. ReneeWrites (talk) 00:14, 24 July 2023 (UTC)

@ReneeWrites: What happened is the expected behavior: when used inside {{Information}} the {{Igen}} template should use + (see parameter 3 and its note) parameter, so the correct use of the template is:

{{Igen|IA|+}}

--ZandDev (talk) 21:02, 8 October 2023 (UTC)

Edit requested on subpage

{{Edit request}} Change Template:Igen/sub at line 41

from

|ff=:SVG special or fictional flags

to

|ff=:Special or fictional flags

--ZandDev (talk) 22:12, 8 October 2023 (UTC)

@ZandDev: I’m not familiar with this template and couldn’t figure it out at the moment – do you have an example file (or other page) where this change would be visible? Lucas Werkmeister (talk) 19:36, 9 October 2023 (UTC)

@Lucas Werkmeister: The template is used for categorizing. I moved the category Category:Valid SVG created with Inkscape:SVG special or fictional flags‎ to Category:Valid SVG created with Inkscape:Special or fictional flags‎. This edit would influence only the two files inside: File:Anarchist black cat flag.svg and File:The Man in the High Castle (Ridley Scott's series).svg. --ZandDev (talk) 11:20, 10 October 2023 (UTC)

thanks,  Done --Lucas Werkmeister (talk) 17:43, 10 October 2023 (UTC)

Web Content Accessibility Guidelines

It would be good to add Web Content Accessibility Guidelines Stamps. Web Content Accessibility Guidelines (WCAG) 2 Level Conformance would be very useful. J.Stalin S ^Talk 04:21, 11 December 2023 (UTC)