User talk:Sarang/Archive/2016

Please can you change your annoying edit summary

I keep getting notes in my watchlist that say "image generation".

When I look, no image has been "generated", but a description has been edited.

So, just say "edited description", please, then we don't have to wonder what on earth is going on.

Thanks. Begoon - talk 14:10, 18 June 2016 (UTC)

Sorry about disturbing you! I have no own experiences with watchlist, and I cannot see whether a file is on anybodies (e.g. your) list or not.

When the tagging about the SVG development is missing I try to add this tagging, and I am doing that with the template Image generation.

My actions would not be necessary when you cared about the file description earlier; it should be done when uploading, or soon after it. At least it should be done when the file needs some editing.

Of course I can select another description in the Edit Summary, e.g. "(Script) & imgen tag added" or so. sarang♥사랑 17:36, 18 June 2016 (UTC)

@Begoon, sarang: Maybe it is more intuitive (and international) to wrap "image generation" simply in template brackets +{{Image-generation}} (the "+" is simply a common international abbreviation for "add"). It is really better we use "imgen"? But I'm also not sure Begoon meant the edit-summary from the script⁉ ↔ User: Perhelion 18:41, 18 June 2016 (UTC)

I don't know either which notification Begoon gets, I just think that it comes from the summary. If so, "Script + imgen tag" could be a solution? sarang♥사랑

I meant the edit summary in my watchlist, as I thought I'd indicated. It implies that the image has been altered, to me. Still, no matter, because I see I'm told that if I'd "cared" enough in the first place this would not be "necessary". Carry on. Good luck. Begoon - talk 11:43, 19 June 2016 (UTC)

@Begoon Okay it seems you mean the naked "image generation" and not this, which is now for all more clear⁉ ↔ User: Perhelion 12:29, 19 June 2016 (UTC)

Yes, I guess it's better - thanks. Begoon - talk 14:24, 19 June 2016 (UTC)

This section was archived on a request by: ↔ User: Perhelion 23:36, 20 June 2016 (UTC)

File:South Africa - No Unauthorized Vehicles (temporary).svg

File:South Africa - No Unauthorized Vehicles (temporary).svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Fry1989 ^eh? 04:45, 20 January 2016 (UTC):This section was archived on a request by: sarang♥사랑 08:57, 12 July 2016 (UTC)

File:South Africa - Additional Information Plate (temporary).svg

File:South Africa - Additional Information Plate (temporary).svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Fry1989 ^eh? 02:40, 10 March 2016 (UTC):This section was archived on a request by: sarang♥사랑 08:57, 12 July 2016 (UTC)

Terminology

The best description I can think of offhand is "unenclosed structures". The word "building" might often imply being enclosed... AnonMoos (talk) 13:43, 12 April 2016 (UTC):This section was archived on a request by: sarang♥사랑 08:57, 12 July 2016 (UTC)

Thank you. I am astonished of using "unenclosed" to describe that it is in the open nature. I rather had thought of something like "landscape architecture". But "structures" sounds very good; how about "outdoor structures"? May describe it better (esp. for non-English readers) because "outdoor" is a well-known and often-used term in that context. sarang♥사랑 14:02, 12 April 2016 (UTC)

"Unenclosed" means that something doesn't have walls and a roof to create closed internal spaces (like the rooms of a house, etc.). "Outdoors" would seem to refer more to the location where something is built than what type of thing it is, and I'm not sure how unambiguous it would be... AnonMoos (talk) 15:00, 12 April 2016 (UTC)

"Unenclosed" is sure exact; "Outdoors" fits better to the location where it is built and the connection where it is designed for, and it comprises the unenclosed attribute.

Your explanations helped me to come to a first decision - until somebody will move the categories... sarang♥사랑 16:03, 12 April 2016 (UTC)

SVG translations

Could you please check Commons talk:Translation possible/Learn more #Update for project page and #Hyphenated language codes not working? --Obsuser (talk) 03:47, 21 May 2016 (UTC):This section was archived on a request by: sarang♥사랑 08:57, 12 July 2016 (UTC)

Category:PNG_created_with_Scribus

PNG created with Scribus has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you!

AbdealiJK (talk) 08:30, 12 June 2016 (UTC):This section was archived on a request by: sarang♥사랑 08:57, 12 July 2016 (UTC)

Text problem in File:Matrix representing a 6-cube.svg

Hi Sarang, you usually know such things, so I wanted to show this to you. I also asked on Stackoverflow. Maybe you can also give me some other hints what I could improve. This file is going to be the basis of other files with red entries like here, and similar files in other sizes. Greetings, Watchduck (quack) 19:04, 16 June 2016 (UTC)

Hello Watchduck, (and sorry sarang that I answer :P) this is an extreme example for combination of phab:T36947 and phab:T65703 (which get fixed in the next Wikimedia update) PS: Why you have changed the Bin2svg logo.svg to Polish air-force insignia? ↔ User: Perhelion 19:48, 16 June 2016 (UTC)

Hello Perhelion, thanks for the hint. So there is nothing I can do? I tried a version with smaller width and height, which at least works on my desktop, but it looks the same.

looks neat and resembles the matrices I create with bin2svg. I guess no one will mistake them for Polish planes now. Watchduck (quack) 20:29, 16 June 2016 (UTC)

I uploaded a new version where the text is not scaled, and that did the trick. Watchduck (quack) 22:31, 16 June 2016 (UTC)

@Sarang: I think it is a terrible idea to create duplicates, because a different name makes more sense in a different context. (Here I wrote about a particularly bad case of this kind.) I also think there is no reason to purge PNGs as if they were the plague. Watchduck (quack) 18:57, 18 June 2016 (UTC)

@Matrix representing: Good to see you resolve this.

@Duplicates: This is sometimes an adequate method, compare also a case with more reason:[1]

I mean this all is an good intention from Sarang, the only fault here is maybe the lack of discussion from him. It is only logical (at minimum practically) that bin2svg should have his own logo file, or not? ↔ User: Perhelion 22:23, 18 June 2016 (UTC)

Hi Perhelion, I don't think the arms of Gera should have a duplicate. Can you guess how many duplicates of File:Flag of the United Kingdom.svg we would have, if we made files like File:Flag of Canada (1801–1964).svg? I find Blackcats statement "Duplicate is not itself a reason for deleting" a bit weird. If this is the case, it should be clearly stated at Commons:Duplicate. However, I agree that in extremely rare cases like File:Flag of England.svg vs. File:Flag of Genoa.svg (even if they were exactly the same), this is permissiblish due to convention. (Although the good solution would be File:St George's flag.svg.)

Of course Sarangs change was in good faith. I was just a bit annoyed, because I myself had already reverted back from SVG to PNG. If it is really necesseary to categorize all the icons - fine. I put in Category:Free software logos (vector graphics). Watchduck (quack) 10:29, 19 June 2016 (UTC)

Bin2svg logo red.svg looks exactly like, but its code is not a duplicate of Roundel of Poland (until 1993).svg; this depends also the size. BTW, I believe such logos/icons (especially the Free software logos) should be SVG wherever possible.

I cannot see why a "Szachownica" is better than a "Bin2svg" to tag a Bin2svg-drawing. Furthermore, it is common consent that SVG is always preferable to raster.

The useless and superfluous change back to PNG in Created with bin2svg destroyed also the format. sarang♥사랑 16:35, 19 June 2016 (UTC)

Sarang, I don't remember in which occasion I wrote that but that must be meant in the sense that the duplicated file might be used across several projects and thus deleting it without having substistuted it with the vector version would cause a problem in the related articles. Now I don't remember what was the situation when I wrote that but I said "itself", not that I don't agree that a duplicate file should be deleted. -- SERGIO ^{(aka the Blackcat)} 13:37, 20 June 2016 (UTC)

This is such a great topic to get into a big fight about. :) I have reverted back to the PNG, because I liked the darker red and the smaller margin better. Two SVGs that generate the same PNG for a given size are duplicates. Maybe I am a bit oversensitive to duplicates with context-optimized filenames, since I came along the beforementioned polytope mess. Watchduck (quack) 22:12, 20 June 2016 (UTC):This section was archived on a request by: sarang♥사랑 08:57, 12 July 2016 (UTC)

File:Logo-Emerson, Lake and Palmer.svg

File:Logo-Emerson, Lake and Palmer.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Hasenläufer (talk) 22:23, 19 June 2016 (UTC)

This section was archived on a request by: sarang♥사랑 08:57, 12 July 2016 (UTC)

Copyright status: File:Planetenbahnen-de.svg

This media may be deleted.

Thanks for uploading File:Planetenbahnen-de.svg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear. If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

No required license templates were detected at this file page. Please correct it, or if you have any questions please check my FAQ or contact me on my talk page. Yours sincerely, Jarekt (talk) 13:14, 11 August 2016 (UTC) :This section was archived on a request by: sarang♥사랑 06:47, 12 August 2016 (UTC)

File:Port-Valais Coat of Arms.svg

Hier taucht plötzlich ein roter Kategorienlink "MainAutVec" auf. Was mache ich falsch? -- MaxxL - talk 10:31, 8 September 2016 (UTC)

Du machst nix falsch, ich habe gerade eine Untersuchung laufen wg. der Anfrage oberhalb. Wird gleich wieder weg sein! sarang♥사랑 10:35, 8 September 2016 (UTC)

ok. Danke. -- MaxxL - talk 10:42, 8 September 2016 (UTC):This section was archived on a request by: sarang♥사랑 11:03, 8 September 2016 (UTC)

created with R

Hello. {{Created with R}} template puts the files into Category:Created with R. But there is also an older category (category:Images with R source code) with the same goal. Could you change the template to move the files to the older category? Or perhaps you have another solution. - Joxemai (talk) 13:23, 12 September 2016 (UTC)

Yes, there is another solution. It is the same as for ~50 other "Created with" systems:

1. Created with R is a Meta-category. Currently it contains files, but this should change.
2. The categories to be used are created with R prefixed with "Valid SVG ", "Invalid SVG " or "PNG ", and optionally suffixed with " code". No other catogories are to be used!

This may seem a very diffused categorization, but it is useful, esp. compared with the other systems. Images with R source code will also be replaced.

By using the template with the needed parameters all categorizing is done by itself. The best way is with Image generation as I showed with the examples Sektore bi.pdf, Binomial distribution cdf.svg and some more.

It is something new, but I hope you soon will become used to this handling. It bears real advantages. sarang♥사랑 15:56, 12 September 2016 (UTC) ‎:This section was archived on a request by: sarang♥사랑 13:20, 26 September 2016 (UTC)

File source is not properly indicated: File:Bahnhof Beilstein.jpg

This media was probably deleted.

A file that you have uploaded to Wikimedia Commons, File:Bahnhof Beilstein.jpg, was missing information about where it comes from or who created it, which is needed to verify its copyright status. The file probably has been deleted. If you've got all required information, request undeletion providing this information and the link to the concerned file ([[:File:Bahnhof Beilstein.jpg]]). If you created the content yourself, enter {{Own}} as the source. If you did not add a licensing template, you must add one. You may use, for example, {{self|GFDL|cc-by-sa-all}} or {{Cc-zero}} to release certain rights to your work. If someone else created the content, or if it is based on someone else's work, the source should be the address to the web page where you found it, the name and ISBN of the book you scanned it from, or similar. You should also name the author, provide verifiable information to show that the content is in the public domain or has been published under a free license by its author, and add an appropriate template identifying the public domain or licensing status, if you have not already done so. Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing. Please add the required information for this and other files you have uploaded before adding more files. If you need assistance, please ask at the help desk. Thank you!

Rosenzweig τ 17:05, 14 September 2016 (UTC) :This section was archived on a request by: sarang♥사랑 13:20, 26 September 2016 (UTC)

File tagging File:Bahnhof Beilstein.jpg

This media was probably deleted.

Thanks for uploading File:Bahnhof Beilstein.jpg. This media is missing permission information. A source is given, but there is no proof that the author or copyright holder agreed to license the file under the given license. Please provide a link to an appropriate webpage with license information, or ask the author or copyright holder to send an email with copy of a written permission to VRT (permissions-commons@wikimedia.org). You may still be required to go through this procedure even if you are the author yourself; please see Commons:But it's my own work! for more details. After you emailed permission, you may replace the {{No permission since}} tag with {{subst:PP}} on file description page. Alternatively, you may click on "Challenge speedy deletion" below the tag if you wish to provide an argument why evidence of permission is not necessary in this case. Please see this page for more information on how to confirm permission, or if you would like to understand why we ask for permission when uploading work that is not your own, or work which has been previously published (regardless of whether it is your own). The file probably has been deleted. If you sent a permission, try to send it again after 14 days. Do not re-upload. When the VRT-member processes your mail, the file can be undeleted. Additionally you can request undeletion here, providing a link to the File-page on Commons where it was uploaded ([[:File:Bahnhof Beilstein.jpg]]) and the above demanded information in your request.

 

Rosenzweig τ 17:06, 14 September 2016 (UTC) :This section was archived on a request by: sarang♥사랑 13:20, 26 September 2016 (UTC)

Verschlimmbesserung GIMP-label

Hello Sarang,

I see you modify the Category entries "Created with GIMP".

For the JPEG file there is now the hidden category "PNG created with GIMP" and this is wrong.

Even more, most correctly there should be a category "Modified with GIMP" as GIMP was only the last program used in a tool chain.

Cheers--KlausFoehl (talk) 09:30, 20 September 2016 (UTC) (answered at pump) :This section was archived on a request by: sarang♥사랑 13:20, 26 September 2016 (UTC)

Tongariro National Park?

Hi Sarang! Did you mean "Great Walk Hiking shelters in the Tongariro National Park" or is Category:Great Walk Hiking shelters in the National Park correct? Regards, --Podzemnik (talk) 01:48, 24 April 2016 (UTC)

There is discussion possible. As you know, within NZ this park is called normally just "National Park" without the "Tongariro" specification. So it is correct.

But because outside of the NZ-context it may lead to ambiguities/mnohoznačnost I am thinking that it will be advised to move the categories and clarify which national park is meant. There is not such a need to move Great Walk Hiking shelters in the National Park because it is a subcategory to Hiking shelters in the Tongariro National Park (now Hiking shelters in the National Park), and "Great Walk" specifies it in addition.

BTW, do you think I should care for a template to be used for all the not-Tararua huts? If you have ideas how it should be designed... sarang♥사랑 07:28, 24 April 2016 (UTC)

I gave it now a try with Kaweka-Back Ridge Hut where I used the template; the template docu is expanded at the end.

Of course it will be possible to give the template another name (without Tararua) like "NZhuts"; just tell me! -- sarang♥사랑 16:32, 24 April 2016 (UTC)

Oh really? I didn't know that they call it here just "National Park". As far as I know, National Park is just a village. Anyway, I think the only official name is "Tongariro National Park" and it would be nice to have it with this name, otherwise it can be confusing for people who don't know that - including me :)

Using the template for non-Tararua Huts - it's up to you. I don't understand much to templates and I like things, including my life, as simple as possible. I'm happy to take pictures and sort them into categories, templates for categories make it a bit more complicated and it's another thing to mantain - but I don't want to say that I don't care. It's nice, do it if you think it's useful! By the way, I climbed Mt Ruapehu a few days ago. It was beautiful! Have a good day and thanks again for your work here. You're helping a lot! --Podzemnik (talk) 20:17, 24 April 2016 (UTC)

As I understand, it is up to me whether e.g. huts are described carefully with more details and links; and because I am thinking that is is better to give this infos I will care for it, time by time. Three years ago I walked the "Round the Mountain Track" a second time, since then many pictures are waiting for the upload: Whakapapaiti Hut, Mangaehuehu Hut, Mangaturuturu Hut, Rangipo Hut and what are all the names. Also Ohinepango source; but sure you will make a lot of good pics and mine are not needed! Enjoy your time there, even when it's now autumn. sarang♥사랑 21:18, 24 April 2016 (UTC)

This section was archived on a request by: sarang♥사랑 06:51, 19 November 2016 (UTC)

Category:Smilies - happy

Hello Sarang, was hast du denn auf einmal gegen die Cat? :-o Es sieht aus als ob du diese auflösen willst?? Jedenfalls hast du nur die SVGs dort "entfernt". LG ↔ User: Perhelion 14:20, 28 April 2016 (UTC)

Eigentlich wollte ich die sehr stark bevölkerte Kategorie etwas entlasten und einen Teil der Smilies unterkategorisieren; das ist mir offensichtlich nicht so gut gelungen.

Die nun angelegte SVG Smilies - happy ist wohl besser geeignet diesen Teil aufzunehmen und zu differenzieren. In Ordnung? sarang♥사랑 05:12, 29 April 2016 (UTC)

Aja hm ja ok. Jetzt brauchst du wohl nur noch jemanden (falls du es nicht mit VFC schaffst) der deine Log-Liste mit enstpr. Files ausliest!? :P PS: Evtl. hilft dir dieser Abschnitt weiter. ↔ User: Perhelion 11:45, 29 April 2016 (UTC)

 Done Ich habs mal erl. (wie du wahrsch. schon bemerkt hast) wobei der Code von Rillke nicht mehr gefunzt hat. Zudem ich wohl auch einem Bug von HotCat aufgesessen bin, sprich, nur SVG zur Anzeige gebracht und trotzdem hat HotCat alles ausgewählt (was ich gleich mal melden werde). An sich ist die Cat ja auch irgendwie sinnlos, da Smilies vom Namen her schon "happy" sein sollten. Schönes Wochenende LG ↔ User: Perhelion 06:12, 30 April 2016 (UTC)

Danke! Ich hätte es schon noch gemacht (ich versuch immer meine Fehler auch gleich wieder auszubügeln…) wobei ich in diesem Fall "Cat-a-lot" verwende.

"Smilies" sind nicht alle happy, wie der Name nahelegt, es werden auch daraus entwickelte ganz andere Stimmungen unter diesem Gattungsnamen subsumiert. 사랑

Ok, für's nächste Mal, da ich die Seiten und den Code alles schon aufgerufen hatte, wollte ich dir nur die Anweisung und Arbeit ersparen. Wobei der Code nun behelfsmäßig so aussah (da direktes click wohl nicht mehr funzt):

$('.mw-rollback-link a').slice(0, -1).attr('href', function(i,href){window.open(href);} ); Die 0 musste ich dann schrittweise um 20 erhöhen (also 19, - 39) da Firefox (oder was anderes) nur 20 neue Tabs zulassen. Ohne Tabs müsste man wohl eine API-Function vorschalten (ich frage mal Rillke :P). ↔ User: Perhelion 06:43, 30 April 2016 (UTC)

Wenn ich nun schon mal mit dir Zauberkünstler plaudere: hast du irgendwas rausbekommen wie der W3C als Funktion/Unterprogramm verwendet werden kann? Dann wäre eine Vorlage möglich die automatisch valid/invalid ermittelt. Wäre sicherlich zu aufwendig und resourcenfressend um viel eingesetzt zu werden aber könnte in speziellen Fällen verwendet werden. Zur Erinnerung: von der Funktion werden "0" für "valide", >0 als Fehleranzahl, oder ein anderer festzulegender Wert für "nicht prüfbar" retourniert. sarang♥사랑 07:06, 30 April 2016 (UTC)

Aja (da war ja was), ich stell das mal als mein nächstes Projekt an (nächste Woche). Wie ich gesehen habe nutzt Rillke das schon (allerdings nur im SVG edit). Was hältst du davon das Check-Tool von Menner auch gleich anzufügen (da wo jetzt schon der/mein "Valid SVG?" link ist)!? ↔ User: Perhelion 07:50, 30 April 2016 (UTC):This section was archived on a request by: sarang♥사랑 06:51, 19 November 2016 (UTC)

Category:Kanji tattoos

This seems somewhat redundant to Category:Chinese glyph tattoos; you may want to redirect one to the other. AnonMoos (talk) 17:59, 21 June 2016 (UTC)

You are right @AnonMoos: something should be done there. It had been discussed and the conclusion might be the category Tattoos in Chinese, or Tattoos with Chinese characters comprising all Chinese, Japanese, Korean and Vietnamese tattoos in Chinese writing. "Glyph" is not correct, anyway - "character" will describe it better. Or do you have any other suggestion? sarang♥사랑 09:45, 30 June 2016 (UTC):This section was archived on a request by: sarang♥사랑 06:51, 19 November 2016 (UTC)

A question

Do these wide ranging (automated?) changes you are making to image description pages all over the place have a community consensus somewhere which I can look at?

Seems to me there are a lot of complaints (which somebody else answers - what's up with that?), but no clear answer about why you are doing this.

Anyway, a link to the consensus authorising you to make these mass alterations would be lovely. Thanks. Begoon - talk 12:34, 2 July 2016 (UTC)

Thank you for asking. AFAIK there is no explicit consensus to care for proper categorization of SVG files, and many users are avoiding the little effort to create the description; your file Italy Labelled Map Scalable.svg was just one example.

IMHO it is a good idea to start a discussion, to achieve a community consent whether such categorizing is complete nonsense or worthful and wanted. You are invited to create the questions at the appropriate page!

My edits are not at all automated mass edits. For each single file I need to check explicitly for the tool (Inkscape, Adobe or another one), for the validity and for other properties. Thanks to Perhelion it is now a bit script-supported, but still by no means self-doing.

About authorization: a good faith edit never needed one, neither in a Wikipedia nor in the Commons. But of course you may chose any appropriate counteraction if you dislike changes somebody else makes.

Best of all would be if you add the outstanding parts of the description by yourself! Kind regards, sarang♥사랑 15:06, 2 July 2016 (UTC)

Yeah, I noticed my comment here led to "pointy" edits, in the same way my previous one had done - no need to link them, thanks, I saw the knee jerk. Please don't ever presume to tell me how much or little I "care" again. I find that offensive. I have spent many volunteer hours here creating images, and your obsession with fiddling with description pages is no basis for that kind of slur.

+ This is just personal advice, and you are free to take it or leave it, but here goes: I've seen many, many folks take the attitude and approach which you are taking here. I have never once seen it end well for them. Begoon - talk 13:09, 5 July 2016 (UTC)

No need to answer. I can see you are busy. Begoon - talk 18:45, 12 July 2016 (UTC):This section was archived on a request by: sarang♥사랑 06:51, 19 November 2016 (UTC)

File:Coat of arms of Heraldry itself.svg

Your edits seem to have added the image to non-existent category Or, argent, gules, azure, vert, sable, purpure in heraldry... AnonMoos (talk) 16:02, 20 July 2016 (UTC)

Yes, seems to be required to define this cat. It contains other pics. I'll do it.

But the colors are not FIAV, I will therefore as well remove the FIAV-tag. sarang♥사랑 17:36, 20 July 2016 (UTC)

IMHO it's now corrrect in any sense. I converted also the redlink above. sarang♥사랑 12:52, 21 July 2016 (UTC):This section was archived on a request by: sarang♥사랑 06:51, 19 November 2016 (UTC)

File:U+262F.svg

I would strongly recommend that no area inside the overall circle be transparent, since that would go against the basic symbolism involved... AnonMoos (talk) 15:05, 27 October 2016 (UTC)

Thank you. With text embedding I cannot do it, therefore I reverted my tries. sarang♥사랑 15:10, 27 October 2016 (UTC):This section was archived on a request by: sarang♥사랑 06:51, 19 November 2016 (UTC)

Category:St._James_Churches

St. James Churches has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you!

AFBorchert (talk) 13:19, 13 November 2016 (UTC):This section was archived on a request by: sarang♥사랑 06:51, 19 November 2016 (UTC)

SVG rendered in wrong color

Hi Sarang, I thought you might find this interesting. My red sphere is rendered as green. Maybe you can see what is wrong here. This is by no means an urgent problem. But if you feel rewriting it with a few lines of code, I would surely be curious to see it. Greetings, Watchduck (quack) 22:03, 18 November 2016 (UTC)

FRrepaired by swift AnonMoos.  :This section was archived on a request by: sarang♥사랑 06:51, 19 November 2016 (UTC)

Errors in my BKchem files

Hi! BKchem seems to create invalid SVG files [2]. Is there any way I can fix this (manually)? I know XML basics, but I'm not familiar with SVG markup. --ἀνυπόδητος (talk) 15:30, 16 July 2016 (UTC)

BKChem always generates W3C-invalid SVG files, as mentioned in Invalid SVG created with BKchem because of the cdml references. You can remove all cdml statements manually before uploading the file, then it will be W3C-valid. Delete line 3 and lines 744 to 1549; the file size will shrink from 40.052 to 20.865 bytes, and everything is fine! Best tool for editing SVG source code is Notepad++, a mighty freeware program.

Thank you for categorizing your file; I have done some format changing of the file description, as you may see. sarang♥사랑 15:58, 16 July 2016 (UTC)

Thanks, I think I got it. Notepad++ is of course the only text editor I ever use :-) --ἀνυπόδητος (talk) 16:44, 16 July 2016 (UTC)

You did very well! The added tag for embedded text is not very useful, because there is nothing to translate - but some letters are embedded, so the % might be seen more or less justified. sarang♥사랑 17:40, 16 July 2016 (UTC)

I was wondering about the %. When I click on "this automated tool", I get a fatal error. I'm fixing my other uploads by and by; hope it's okay not to include the %. --ἀνυπόδητος (talk) 08:47, 17 July 2016 (UTC)

I get also this error, seems to be something new. I'll look whether it will be fixed. No, the % is not at all necessary, it fits not so well in these cases with only single letters where not translation makes sense. But because the letters are text and not path, it is not explicitely wrong either.

About your fixing: It is nice to upload W3C-valid SVGs whenever possible. Fixing mere formal errors of existing files is not such an urgent need; the display is the same, and W3C-"invalid" does not say "bad"! I would neither discourage nor encourage you, but I would not do the work, there are many things to do of much more importance and usability. sarang♥사랑 14:02, 17 July 2016 (UTC):This section was archived on a request by: sarang♥사랑 07:52, 6 February 2017 (UTC)

File:Amtlicher Stimmzettel 2016 Dritter Wahlgang (II).jpg

File:Amtlicher Stimmzettel 2016 Dritter Wahlgang (II).jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

WahlzettelUploader1 (talk) 17:29, 16 November 2016 (UTC)

Somebody removed this incomplete DR from the file; and there is/was no entry for the request, to express my opinion. The requesting user uploaded his version a week after my upload, and because his file quality is so poor I requested its deletion. Contrary to him, I explained him the reason for my request. Due to my experience it is sometimes difficult to talk with Austrian people, but I am always hoping for exceptions. sarang♥사랑 15:20, 18 November 2016 (UTC):This section was archived on a request by: sarang♥사랑 07:52, 6 February 2017 (UTC)

Template:Igen/upl

The category:Uploaded with UploadWizard is being deleted due to this community decision. Do not add it anywhere. If you wish, you can add another, SVG-specific category to SVG files. Ankry (talk) 20:22, 19 November 2016 (UTC)

Thank you for informing me. BTW, I never understood the benefit of tagging a file how it was uploaded. I think it useful to tell which tool was used to create SVG drawings; but whether the file was uploaded with Commonist, VicuñaUploader or whatsever seems to me of no importance.

IMHO it is of he same uselessness to tag billions of files file with "Location not applicable". sarang♥사랑 08:02, 20 November 2016 (UTC):This section was archived on a request by: sarang♥사랑 07:23, 25 February 2017 (UTC)

SimplSVG

Hallo Sarang,
nunja so wichtig ist es wohl tatsächlich nicht, eine kleine diskrete Erweiterung der Doku schadet jedoch nicht.

OT: Das mit deiner Reise hört sich ja spannend an, ein beliebtes Auswanderungsland. :-) Ich hoffe du hast eine gute Zeit.

@SVG‑Erstellung: Anbei hätte ich noch eine Frage: Dass die Vorlage SimplSVG in ein extra Feld des Information Templates rutscht ist sehr zu begrüßen. Nun kannst du einen Hinweis geben (oder evtl. gleich umsetzen) wie das mit anderen Vorlagen, wie zB. {{PoorSVG}} geht? (hier Bsp-Datei) VG ↔ User: Perhelion 15:07, 12 March 2016 (UTC)

Schau mal Wappen von Eicklingen.svg - hab ich gleich umgesetzt; solche taggings lassen sich gut mit t= (oder T=, ggf mit zusätzlichem {{clr}}) integrieren. Gruss sarang♥사랑 01:38, 22 March 2016 (UTC)  :This section was archived on a request by: -- sarang♥사랑 05:57, 1 August 2018 (UTC)

User:Perhelion/simpleSVGcheck.js

Hej Sarang, das Script-Grundgerüst ist soweit fertig, allerdings wollte ich den SVG-Validator-Bot () von Rillke benutzen, allerdings ist dieser irgendwie defekt (conf fehlt, s SVGedit).

Could not read configuration.  Set the W3C_VALIDATOR_CFG environment variable
or copy conf/* to /etc/w3c/. Make sure that the configuration file and all
included files are readable by the web server user. The error was:
'Config::General The file "/etc/w3c/validator.conf" does not exist within ConfigPath: /etc/w3c! at /data/project/validator/validator/cgi-bin/check line 128.
'
BEGIN failed--compilation aborted at /data/project/validator/validator/cgi-bin/check line 230.

Nun jetzt habe ich allerdings noch eine Alternative gefunden… Bis dahin noch eine Frage, benutzt du auch ein paar RegExps für die Ersetzung/Einfügung in den Dateibeschreibungsseiten (ich habe deine neuerlichen Massenedits gesehen)? Wenn ja, könntest du sie mir geben und ich baue sie in die neue Funktion ein (neuer Link bei dem roten Badge, welcher nun auch einen Link erzeugt der die Werte einträgt). ↔ User: Perhelion 10:58, 25 May 2016 (UTC)

Du machst da ja grossartige Hilfsmittel, wie ich sehe. RegExp habe ich fast gar nicht verwendet, höchstens extrem einfache Ausdrücke, meist sind es ganz simple Ersetzungen. Deine Idee ist brillant, den W3C-Wert (Fehleranzahl) einmal zu ermitteln und dann einzutragen, mit weitgehender automatischer Vorgabe.

Oft ändere ich Angaben wie (hier ein recht extremes Beispiel)

Source=*[[:Image:Archimedes_circle_area_proof_-_inscribed_polygons.png|Archimedes_circle_area_proof_-_inscribed_polygons.png]] gegen das weit einfachere

Source={{F|Archimedes_circle_area_proof_-_inscribed_polygons.png}} wobei ich die hässlichen understrokes belassen kann, weil {{F}} sie in spaces umsetzt. Erstaunlich viele machen das so umständlich!

Oder das hier Author=[[User:Magog_the_Ogre|Magog the Ogre]] ([[User talk:Magog_the_Ogre|<span class="signature-talk">talk</span>]]) in Author={{Ult|Magog the Ogre}}, erzeugt genau denselben output, inklusive <span (wobei sehr fraglich bleibt ob die Diskussionsseite eines Benutzers in den Author gehört…)

Ich sollte mir mal ansehen wie du diese Automatismen bastelst, und mir ähnliche tools erstellen die das Aufräumen erleichtern. Zur Zeit versuche ich (mit wechselndem Erfolg…) ein Modul zu erstellen, mit dem ich diese other fields umgehen kann. Das umständliche {{Information field}} war relativ einfach wegzubekommen, aber einstweilen macht mir noch die Kommunikation zwischen Vorlage und Modul einige Probleme. Das #titleparts: ist keine brauchbare Lösung, hat zu starke Einschränkungen. Leider weiss ich viel zu wenig über LUA und kann diese Sprache nur sehr primitiv einsetzen – von Eleganz bisher keine Spur! sarang♥사랑 12:25, 25 May 2016 (UTC)

 Done Ich habe tatsächlich nun den W3C-API-Validator-Service gefunden und gleich eingebaut, zum Testen! (PS: Man muss schon ein bisschen suchen um noch SVG ohne Igen zu finden :P) Ich kann das Script dahingehend einfach erweitern, dass solche Dinge (wie bei Magog_the_Ogre) aufgeräumt werden. Wobei folgendes momentan getan wird:

1. Alle Parameter werden standardmäßig klein (nach Upload Wizard), ich stimme dir dahingehend zu dass hier entweder alle groß oder alle kleine sein sollten.
2. other fields wird natürlich bei Bedarf hinzugefügt, wobei ein leeres other versions nicht gelöscht wird (ich glaube fast du bist einer der sehr Wenigen die die beiden Parameter groß schreiben).
3. Entfernen von Template „valid SVG“ und „invalid SVG“ (wobei ich momentan die Werte ignoriere, kann man aber ändern⁉). Welche soll ich noch hinzufügen?

Ein Sonderfall stellt ja wieder COAInformation da, was wieder Mehraufwand ist, kannst du die Wesentlichen Unterschiede kurz erklären? Und wie meinst du das Problem mit other fields?

@F: Ich bin eher für eine sparsame Verwendung von extra Syntax-Templates. In den meisten Fällen ist nichts gegen die Anzeige das Namesscapes zu sagen, wie [[:File:Archimedes_circle_area_proof_-_inscribed_polygons.png]] (den man auch noch mit einem Leerzeichen Abstand abtrennen kann)

@Information field: Hast du ein Beispiel wie dieses Template am besten ersetzt werden sollte? ↔ User: Perhelion 13:39, 25 May 2016 (UTC)

Ansonsten benutze ich zurzeit den automatisch startenden (nur bei Files) und selbst erweiterbaren WikiSyntaxTextMod, siehe meiner Perhelion/global.js]./global.js] (wobei ich für Dateiseiten noch keine spezielle eigene Definition habe.) Wenn du willst könnte ich die ein Grundgerüst bauen, welches du dann selber einfach in der Form per Listen (Tupel) Eintrag [ "bad string", "good string" ] erweitern kannst in deiner .global.js (oder anderer lokaler Unterseite).

LG ↔ User: Perhelion 13:30, 25 May 2016 (UTC)

PPS: Der API-Validator ist deutlich freundlicher zu den SVGs, z.B. wird proprietäre Inkscape-Syntax ignoriert (was jetzt für Kritiker wie NNW sicher entgegenkommend ist). Naja, man kann noch das Tool von Rillke testen (sobald es wieder läuft).

@Menner: möchte ich hier nicht vergessen zu erwähnen, da man evtl. erwähnen kann dass mein Script zu jeder Datei auf sein Tool – vorausfüllend – verweist. Allerdings würde ich noch eine Option (in der URL) begrüßen die den Check automatisch ausführt⁉ ↔ User: Perhelion 13:52, 25 May 2016 (UTC)

Erst mal muss ich gestehen dass ich den UploadWizard noch nie verwendet habe; ich lade mit dem link „upload file“ (in den commons habe ich alles auf English) an der linken Seite; und der bringt in "basic upload form" ein Formular für die descriptions das grösstenteils upper, teils lower case ist, nämlich

{{Information
|Description=
|Source=
|Date=
|Author=
|Permission=
|other_versions=
}}

, deswegen habe ich eher die upper-case-Variante. Meist kopiere ich alles inklusive =={{int:filedesc}}== etc.

Ich versuche eine description einheitlich zu schreiben (obwohl das vollkommen egal ist), und ohne understrokes; wenn alles klein ist dann auch |other fields={{igen|a|...}}, sonst |Other fields={{Igen|A|...}}. Aber das ist reine Pingelei, dem System ist es ja wurscht ob upper, lower, understroke oder spaces.

• Information field: weil {{Igen}} sowohl innerhalb als auch ausserhalb der Info-box funktionieren muss habe ich es mit dem Parameter "+" gelöst, dass ggf. {{InFi}} oder auch nicht verwendet wird. In COAInformation und {{Map}} wird dann wieder das Igen aufgerufen ({{COAInformation/Imgen}} bzw. {{Map/Imgen}}; das sieht der Benutzer ja nicht, zum Glück, mit welchen Krüken das erreicht wird!), wobei Vereinfachungen möglich sind. Ich versuche auch in der Information einen Imgen-Parameter etabliert zu bekommen, damit könnten dann die Other fields übergangen werden.
• Valid/InvalidVG entfernen: ist gut; ich kann ja jederzeit sehen, was geändert bzw. entfernt worden ist.
• COAInformation bzw. Map: es gibt die Kurzform mit imgen=, die Langform mit other fields= ist alternativ möglich. Ich bin gerade daran, auch in der Kurzform mehr Parameter zuzulassen, sodass die other fields obsolet werden. Wird noch dauern bis das geht, am besten mach da nichts und warte ab.

Jetzt muss ich mir mal alle deine Neuerungen ansehen. Gruss sarang♥사랑 17:17, 25 May 2016 (UTC)

---

Das funktioniert ja alles grossartig! Ich würde eher keine Leerzeichen um die "=" machen, sie erhöhen IMHO nicht die Leserlichkeit. Ein erster Validationstest ist auch ganz gut, allerdings muss ich schon die source sehen um zu wissen womit die Datei erstellt worden ist – und andere Dinge zu erkennen, wie bei HTML5 video icon.svg (Adobe, raster embedded, <text oder path, etc.). Ich bin sehr angetan von deiner Arbeit! sarang♥사랑 17:46, 25 May 2016 (UTC)

Aja gut gut, freut mich dass es dir gefällt. :) Wegen Bedenken zu der völligen Inkonsistenz der Parameter Groß/Kleinschreibweise, eröffne ich gleich einen Thread in den VP.Commons:Village pump#Template:Information consistent? Gut dann entferne ich das Leerzeichen vor dem "=" allerdings wird auch Einrückung verwendet, diese belasse ich bzw. passe das other fields mit extra Leerzeichen an.Bsp. Wenn dir Vorschläge einfallen, nur her damit. ↔ User: Perhelion 17:55, 25 May 2016 (UTC)

Deine vorsichtige Anfrage wg. Inkonsistenz ist, genau so wie einige vorhergehende von mir, abgeschmettert worden. Mich hat immer schon ein klein wenig irritiert, dass zwar "Description Date Source Author Permission Other versions …" angezeigt wird, in dieser Schreibweise und Reihenfolge (bei user lang=en), es aber im Formular ganz anders ist (vom Anzeigebild rührt auch meine gelegentliche Präferenz der Großschreibung); deshalb habe ich das beim Aufräumen manchmal vorsichtig angepasst. Wie gesagt, die Parameterreihenfolge und -schreibweise ist völlig egal – dennoch hätte ich es vorgezogen wenn das vorgegebene Formular (siehe oben) der Anzeige entspräche.

Die COAInformation ist ja anders als die Information, und ich habe da auch bereits das imgen unterjubeln können, was manches sehr vereinfacht. Der JarektBot hat (zB am 26 March 2015) in einsamer Aktion tausende Beschreibungen umgestellt, und ohne jede Prüfung mal vorab das "Created with Inkscape|…|v|....." reingestellt. Als Angabe in der Source, was ohnehin unerwünscht ist; und kategorisiert in Valid SVG created with Inkscape-Blasons mit 12000 anderen.

Einige habe ich bereits überarbeitet, so in Invalid SVG created with Inkscape:CoA by Spax89; wie ich sehe, habe ich das hier in der „source“ belassen und nur err und sub korrigiert. Mit solchen Sonderfällen hat dein Automatismus Probleme, doch ist das so speziell und unique dass es nicht sinnvoll ist das auch noch programmtechnisch in den Griff zu bekommen! In den mehr standardgemäßen Fällen funktioniert alles bestens.

Deine Einfügung in other fields {{Igen|+|err|s=}} ist meist brauchbar; aber falls es nicht Inkscape ist muss mehr umgedreht werden, dann wäre {{Igen|I|err|+|s=}} (mit dem meist redundanten I) eine Winzigkeit leichter anzupassen.

Ich nehme mal an dass die API-Validation zu aufwendig und resourcebelastend ist um sie in eine Vorlage zu integrieren. Kannst du sie aber mal probeweise in das Module:File einbauen, als Funktion „valid“ – geht schneller als wenn ich es versuche. Schon mal danke! sarang♥사랑 06:13, 26 May 2016 (UTC)

Aber das kannst du verbessern: in Moqua Well mk.svg kommen die other fields in die gallery. sarang♥사랑 06:28, 26 May 2016 (UTC)

Nun beides behoben (und weitere Verbesserungen)! @cleanup.js Ich habe mal einen Fork aufgesetzt (der auch keine Warnungen ausspuckt):User talk:Magog the Ogre/cleanup.js#More deprecated vars + feature User:Perhelion/cleanup.js Dort können wir deine/unsere Wünsche umsetzen. Also z.B. Benutzer-Signaturen bei Autor in einfache Benutzerlinks umwandeln… Template u usw…⁉

@Modul: Also mit Lua kenne ich mich soweit nicht aus, ich bezweifle auch ehrlich gesagt (oder hast du ein Bsp?), dass dies mit Lua geht (geschweige denn mit Template-Syntax :P)

Wenn ich wieder Zeit habe werde ich mich auch mal wieder um Listenarbeit kümmern. ↔ User: Perhelion 15:38, 26 May 2016 (UTC)

Noch nicht ganz gut: du vorbelegst mit |other fields={{Igen|I|+|0|s=}}; das geht nicht. Ich weiss dass das Igen sehr kompliziert ist, und als vielleicht einziger ich manchmal durchblicke; jedenfalls kann die Fehleranzahl nur im 2. Parameter übergeben werden! Also z.B. {{Igen|I|0|+|s=}}, damit ginge es, und kann leicht variiert werden. sarang♥사랑 16:46, 26 May 2016 (UTC)

Verrückt ^^ ist gefixt. Wie wärs noch mit einer Schaltfläche im Editmodus? ↔ User: Perhelion 17:01, 26 May 2016 (UTC)

Nun verstehe ich wieder mal nicht - was meinst du mit Schaltfläche? Und wo? sarang♥사랑 17:04, 26 May 2016 (UTC)

Ach einfach irgendwo ein Button, am besten als Ersatz für deinen Size Button!? Hast du eine kleine Grafik-Idee dafür? ↔ User: Perhelion 17:34, 26 May 2016 (UTC)

Noch mangelt es mir an tollen Ideen, ich werde mir Gedanken machen. So wie ich das sehe haben nur drei Benutzer den Zugriff auf all diese neuen Hilfen; von U:Menner wird kein Igen editiert, von dir wohl vor allem testhalber, also verwende einstweilen nur ich das so exzessiv? Denkst du, das vielleicht mal als eine Option ("Helferlein") allgemein zugänglich zu machen?

Ich habe den Eindruck dass manche nur das Inkscape/Adobe-tag setzen, wenige mehr erzählen ("mit Code" etc), und das nur beim Hochladen; vorhandene Dateien untersuchen und kategorisieren, wie es jetzt dank deiner Neuerungen viel einfacher geworden ist, scheint vor allem meine Domäne zu sein. Die Aussagen zum SVG halten wohl viele für überflüssig, und das Igen mit allen Optionen ist zu kompliziert? sarang♥사랑 04:49, 27 May 2016 (UTC)

Ja das ist wohl so. Ich habe jetzt den Button hinzugefügt, als Logo das kleine vom W3-SVG genommen. Den Size Button brauchst du wohl nicht mehr? Aus deiner common.js kannst du ihn wohl so oder so löschen (da ich ihn auf Bedarf angepasst auch ins Script nehmen könnte). :P LG ↔ User: Perhelion 13:08, 27 May 2016 (UTC)

Nun scheint bei mir einiges nicht mehr so recht zu stimmen. Liegt das am Script? Cache leeren hilft nicht.

• Beim upload gibt es kein "preview" mehr; auch der destination file name wird nicht mehr eingesetzt.
• Annotations kann ich nicht mehr erstellen
• VFC kann nicht mehr aufgrufen werden; steht zwar da, aber keine Reaktion bei Anklick
• jetzt gibt es links:

• cleanup JS: ruft den edit-mode auf, aber sonst geschieht überhaupt nichts.
• fast cleanup TS (new): sagt kurz "Loading", ohne sonst was
• cleanup TS: eine Sekundenbruchteil leuchtet "Click me if you have JavaScript disabled" auf, wenn ich es schaffe da zu klicken geschieht auch nichts weiter. Und es gibt Probleme, von da wieder zurückzukommen, d.h. den mode zu verlassen.

Den Size Button brauche ich nur gelegentlich, aber er ist\war sehr hilfreich wenn ich es denn doch genau wissen will. Ich sehe auch kein W3-SVG-Logo.

Das Generieren der other fields war gestern eine grosse Hilfe, wenn es auch manchmal an der falschen Stelle eingefügt worden ist; zuletzt war es dann gestern abend vor der {{Information und ich musst es nach unten cut\pasten, aber es hatte die richtigen Werte. sarang♥사랑 15:10, 27 May 2016 (UTC)

Aja ganz oben ist der Fallback, wenn keine Position gefunden wurde. Gib mal die Beispiele her. Hm, sollte gleich neben dem Size-Button sein. @C&P noch einfacher gehts mit der Maus, gedrückt halten und ziehen (nur ein Tipp falls du es noch nicht wusstest). :)

@Fehler: Das sieht in der Tat nach irgendeinem JavaScript-Fehler aus, schaue mal in die Konsole. Welchen Browser benutzt du denn? Allerdings erklärt das nicht die zusätzlichen Links!? Oder hast du irgendwo schon mein cleanupFork eingebunden (ich habe keine Änderung bei dir gefunden)?? Und das ist seit heute? ↔ User: Perhelion 19:08, 27 May 2016 (UTC)

Alles tut wieder! Gestern gelang es mir den ganzen Tag nicht vernünftig zu editieren, was immer ich auch versucht habe. Hat vielleicht am Wikipediasystem gelegen, dass was abgeschaltet war? Kommt ja manchmal vor, aber meist mit Hinweismeldung.

Mit dem Browser ist das so eine Sache. Ich benutzte normalerweise FF, und gelegentlich MSE oder auch Chrome, um Unterschiede zu prüfen. Als dann vor ca. einem Jahr bei FF die Neuerung eingeführt wurde, dass man nicht mehr zurück kann und stattdessen erfährt dass die "Seite nicht mehr verfügbar" sei und alle gemachten Änderungen weg sind, habe ich versucht das irgendwie zu ändern. Vergeblich. Als Behelf habe ich dann im Netz irgendeine alte FF-Version gefunden und installiert, allerdings konnte ich nur eine französiche Variante (FF 9.0.1) finden die mit mir ausländisch redet... Aber ich kann damit so lala arbeiten, auch wenn Mail etc. warnen dass diese Version nicht mehr unterstützt würde. Du weisst fast alles, kennst du einen Browser der wieder auf die vorhergehenden Seiten lässt, nachdem ich irgendwo anders was nachgesehen habe, zB probeweise einem Link gefolgt bin, und wieder weitereditieren will? sarang♥사랑 07:07, 28 May 2016 (UTC)

Hej Sarang, gut. Also ich benutze da einfach die normale History-Funktion (jedes Browsers?) mittels alt+→ oder ←. Ansonsten kann ich dir (wiederum) das Tool von Schnark ans Herz legen (welches ich tatsächlich hier auch benutze):

mw.loader.load('//de.wikipedia.org/w/index.php?title=User:Schnark/js/journal.js&action=raw&ctype=text/javascript');

Des Weiteren habe ich jetzt eine erweiterte Funktion (deines alten Requests) die du schon in ganz einfacher Form in der deiner /global.js hast, nämlich zu jeder Seite im anderen Projekt zu springen (auch auf Special-Seiten, Schnark hat hier ebenfalls ein Script, allerdings wohl nur für Special-Seiten). Also ohne Interwiki einfach von c:Template:SVG auf w:de:Vorlage:SVG oder w:de:Benutzer:Perhelion/common.js auf c:User:Perhelion/common.js (falls du das nützlich fändest) LG ↔ User: Perhelion 09:52, 30 May 2016 (UTC)

Danke, bisher war ich sehr zufrieden mit dem Projektwechsel, auch wenn ich vom fest definierten Landeplatz erst zur beabsichtigten Seite muss. Aber ich werde mir mal ansehen, was du beschreibst.

Deine Vor-Formatierung vom 26. Mai hat viel Editierung abgenommen, sie ist nicht mehr im Angebot? sarang♥사랑 17:16, 30 May 2016 (UTC)

Ähm* du meinst den Igen-Button? Da war tatsächlich ein kleiner Fehler drinnen, nun gefixt. LG ↔ User: Perhelion 20:27, 30 May 2016 (UTC)

danke, der button ist wieder da und der Zugang zum Editieren - aber es wird nicht mehr prüf-validiert und vorbereitet. sarang♥사랑 04:29, 31 May 2016 (UTC)

Wie meinst du das jetzt, im Editmodus (hat es ja noch nie :P)? PS: mir ist gerade aufgefallen Template:Extracted_with_Inkscape, sollte allgemein verfasst werden, also "PDF" durch "einem anderen Format" ersetzen. Zudem steht PDF wohl eher ganz hinten an um Vektordaten zu extrahieren. Naja evtl. aus dem Mangel her, dass es Template:Converted_with_Inkscape nicht gibt. Daher die Frage, spielt der Unterschied eine Rolle, muss man das jetzt für jeden Editor machen? Ich denke nicht. ↔ User: Perhelion 08:34, 31 May 2016 (UTC)

PS: Validity-Check nun auch im Editmodus. ↔ User: Perhelion 09:38, 31 May 2016 (UTC)

• Extracted: Ich bin noch nie auf die Idee gekommen etwas mit I. zu extrahieren (auch sonst habe ich noch nichts mit I. gemacht). Ich habe einfach die Vorlage angepasst an die anderen. PDF stammt nicht von mir, das war so hart codiert. Natürlich kann da auch ein Parameter rein, um ein anderes Dateiformat anzugeben. Zur Zeit gibt es gerade mal 233 transclusions, es scheint also nicht sooo toll wichtig zu sein. Aber kein Problem, komplizieren von einfachen Vorlagen ist meine grosse Spezialität (jemand sagte mal "...jetzt kann es auch Eier legen und Kaffee kochen..."). Die Änderung in "...anderes Format" ist leicht, oder kann auch aus demselben (SVG) Format extrahiert werden??? Änderungen in allen Sprachen einzubauen ist einfach da es zZ nur de und en gibt.
• Converted: Wenn das wirklich sinnvoll ist und gebraucht wird, kann ich das schnell machen.
• Editing: Früher mal, vor 5 Tagen, hat der Button 1) in den Editiermodus geschaltet, 2) die Validität gecheckt, 3) ggf. den Parameter |other fields= mit Vorbelegung eingefügt und 4) einige weitere sinnvolle Berichtigungen vorgenommen. Jetzt macht er nur noch (1). Ich habe es sehr angenehm gefunden dass ich nicht immer wieder |other fields={{igen|... tippen oder kopieren muss. sarang♥사랑 12:37, 31 May 2016 (UTC)
  • @Editing: Ähm* ja genau das macht er bei mir auch noch. Ich benutze ich die URL-Technik, du solltest nach dem Öffnen in der URL den Parameter "simpleSVGcheck=" + Anzahl Fehler zu stehen haben!? Gibt es Fehler in der Konsole? Ist das bei jeder Datei?
  • @Converted: Naja eigentlich nicht sonderlich. Die Erwähnung des Formats ist wohl nur um sprachlich nicht nur einen halben Satz zu sagen. "Die SVG wurde mit Dinges extrahiert". Also da die Vorlage eh wenig Benutzung hat, aber durchaus ihre Berechtigung hat (da wohl sehr oft "nur" extrahiert wird und nicht "erstellt"), bin ich dafür diese zu verallgemeinern (wie ich herausgelesen habe, würdest du es per Parameter für alle Arten Edtitoren...). An sich hast du Recht, das erwähnen eines Formates kann man ganz weglassen. PS: Eine extra Vorlage Converted wird keinen Sinn machen, da dieser Begriff von vielen synonym (wohl fälschlich) für Created gebraucht wird. ↔ User: Perhelion 14:05, 31 May 2016 (UTC)
• Deutscher Extract-Text ist geändert, hat halbe Sekunde gedauert. Auch den Englischen?
• Weiterleitung "Converted with" zu "Extracted with .." kann gemacht werden, mit entspr. anderen Ausgabetexten in en&de. sarang♥사랑 14:29, 31 May 2016 (UTC)  :This section was archived on a request by: -- sarang♥사랑 05:57, 1 August 2018 (UTC)

Removed "created with Inkscape"

Hello Sarang, on June 12 between 16:08 and 17:44 you removed the information from several files I created that they were made using Inkscape. Best regards, Kraaiennest (talk) 19:55, 26 June 2016 (UTC)

Hello Kraaiennest, (because Sarang is at holidays, I answer first) okay, this seems collides with the purpose of template:image generation. It seems you used 2 tools for creation, maybe this need another mixed sorting option. What you have done with Inkscape? ↔ User: Perhelion 21:22, 27 June 2016 (UTC)

Hi Kraaiennest, the information is not removed! But when you use the template {{Created with Inkscape}} you categorize into [[Created with Inkscape]] which should be a Meta category. And when you use the template {{Valid SVG}} you categorize into [[Valid SVG]] which should also be a Meta category. My changes cared for more diffused categorization into the provided subcategories, e.g. [[Valid SVG created with Inkscape:Diagrams]]. If you find something else made worse by me, please tell me more detailed! sarang♥사랑 14:25, 29 June 2016 (UTC)

Hi Sarang, I very much appreciate the good work you are doing. With regard to Perhelion's question:

Matlab was used to compute the shapes used in the images, exported either as encapsulated postscript or SVG;

Inkscape was used – amongst others – to accomplish one or more tasks of the following:

• add annotations, arrows, lines, etc. to the graphs;
• change line styles, thicknesses, colors;
• change fonts;
• add fills and gradients to the shape interiors;
• import encapsulated postscript.

Best regards, Kraaiennest (talk) 18:14, 30 June 2016 (UTC)

Hi again. The categorizing system is designed to show only the main creation tool, even if the usage of Inkscape is implied by some tools.

If later changements are done with e.g. Inkscape, Adobe or Text_editor, it depends whether they are more essential than the previous MATLAB works.

Furthermore, while the MATLAB template can show the code, this is not possible with Inkscape. So if code should be shown, always use MATLAB.

Use MATLAB also when the initial generation work is done by it, and another tool only when the image is completely (or most of it) new drawn.

• If you are perfectly unhappy with these restrictions, tell your suggestions how it should be, and we can search for a solution. It is possible to make the category system more complex, and we can do it if it will be useful and gives better access to the files. Kind regards, sarang♥사랑 10:57, 1 July 2016 (UTC)  :This section was archived on a request by: -- sarang♥사랑 05:57, 1 August 2018 (UTC)

File:Map of USA with state names.svg

Could you please let me know what tool was used to identify the three errors in the SVG in File:Map of USA with state names.svg? I am aware of the messages "*Warning* You appear to have specified a font that does not exist on Wikimedia wikis. " There are three flavors of these and 17 instances and I removed a lot of these but the rest are relatively difficult to remove unless you know an easy way. Delphi234 (talk) 05:06, 7 October 2016 (UTC)

Hi, I am not sure whether I understand your question. There are different tools to check SVG files, our SVG checker, two tools from W3C and others. Errors are shown when you follow the colored link in "The source code of this SVG is invalid..." (or "The source code of this SVG is valid"). As long as the contents of a picture are properly shown some formal errors don't harm, and warnings can be ignored completely - when I looked for the first six files in your SVG Charts I saw that you are doing good work! Just in some cases the file description can be slightly edited.

My suggestion: Don't upload better versions of existing files just because of warnings (or mere formal errors); if possible try to create new files error-free, which means that you check them before uploading and repair errors in advance. Of course you can as well care for the warnings, when any are shown by the pre-upload check. I do not know a general easy way to change such source texts. sarang♥사랑 06:53, 7 October 2016 (UTC)

I was asking which tool you used. When I go to validator check I find

Line 396, Column 6: Text not allowed in SVG element switch in this context.

<text systemLanguage="ta">வாஷிங்டன்</text>

Error Source text is not in Unicode Normalization Form C.

Error Line 1361, Column 6: Text not allowed in SVG element switch in this context.

<text systemLanguage="arc">ܝܘܬܐ</text>

I have no idea what those mean. They look fine to me. And when I check it says:

Line 2, Column 39: attribute values may not contain '&lt;'

<svg xmlns="http://www.w3.org/2000/svg" height="600px" width="800px" version="1…

While no where in the source code can I find &lt;, although I use it in many other charts as < can not be used in SVG. Perhaps because of these odd error indicators I instead use this.

But honestly the last thing I would want anyone to do is clutter up commons with invalid SVG by creating a separate file instead of just fixing that one. And instead of drive by tagging I would recommend fixing any errors you find if it can be done in say 10 minutes or less. I certainly do not mind not being listed as the last uploader on record of any file I have created or if I was the one who introduced the invalid SVG. This is a collaborative project and really it does not matter who makes most edits. Delphi234 (talk) 10:04, 7 October 2016 (UTC)

I removed the spurious switch text 22 October 2016. I fixed the UNF C errors 26 October 2016. Glrx (talk) 00:43, 10 April 2018 (UTC)  :This section was archived on a request by: -- sarang♥사랑 05:57, 1 August 2018 (UTC)

File:Heart-symbol-vulva-shape-hypothesis-illustration.svg

Your Javascript syntax highlighting mode really didn't seem to do too much for the PostScript code. Also, the "%!" at the beginning is part of the actual code; traditionally, if you sent a PostScript file to a laserprinter without the "%!" at the beginning, the PostScript code would be printed out in Courier font, rather than being executed. (Not too sure how it works nowadays...) -- AnonMoos (talk) 03:01, 14 December 2016 (UTC)

I tried to find a suiting syntax highlighting but couldn't finde one for PostScript code. Sorry that I made something wrong instead of better. I'll take more care in future. sarang♥사랑 06:17, 14 December 2016 (UTC)

PostScript is an extensible language with basic "Forth"-like syntax, so in the general case, you couldn't effectively highlight it without fully interpreting it. See File:Iraq-flag-map_1959-1963.svg for one example of setting up a new sub-language within PostScript. I don't see Forth on the syntax highlighting list either (not surprised).. AnonMoos (talk) 08:24, 14 December 2016 (UTC)

Yes, with lang=basic4gl some highlighting occurs - but IMHO not extremly helpful. The code in the Iraq-flag-map looks very impressing ... sarang♥사랑 08:34, 14 December 2016 (UTC)

2017

Apparently there is actually a PostScript highlighting mode, but I'm not sure that it does much more than put reserved keywords in one color and so-called "comments" (which are not always merely comments) in another: [3] [4] -- AnonMoos (talk) 18:30, 20 February 2017 (UTC)

After some investigation I found this syntaxhighlighting used in "PostScript" since 25 June 2015, but it had not been mentioned in this list. sarang♥사랑 07:23, 21 February 2017 (UTC) :This section was archived on a request by: -- sarang♥사랑 05:57, 1 August 2018 (UTC)

Translation

Hallo! regarding what you asked me, I did the best I could, I perspired a lot with the cache refresh because I could not see the modifications that I made, but I think there is something quite decent now. When you need something do not hesitate to ask me. A big hug from Argentina. --J3D3 (talk) 16:51, 25 December 2016 (UTC)  :This section was archived on a request by: -- sarang♥사랑 05:57, 1 August 2018 (UTC)

File:Palestine-Mandate-Ensign-1927-1948.svg

I'm kind of surprised that it didn't come to your attention long ago that SVG "TextPath" doesn't work on Commons... -- AnonMoos (talk) 23:56, 30 December 2016 (UTC)

I fear that are a lot of things I do not know yet... but by trial & error I shall find out some of them time by time.

Sorry that I spoiled that flag with my unsuccessful attempt sarang♥사랑 05:55, 31 December 2016 (UTC)

I got that notice: "You just made your hundred thousandth edit; thank you for an amazing contribution!"  :This section was archived on a request by: -- sarang♥사랑 05:57, 1 August 2018 (UTC)