VexilAlpaca
Our first steps tour and our frequently asked questions will help you a lot after registration. They explain how to customize the interface (for example the language), how to upload files and our basic licensing policy (Wikimedia Commons only accepts free content). You don't need technical skills in order to contribute here. Be bold when contributing and assume good faith when interacting with others. This is a wiki. More information is available at the community portal. You may ask questions at the help desk, village pump or on IRC channel #wikimedia-commons (webchat). You can also contact an administrator on their talk page. If you have a specific copyright question, ask at the copyright village pump. |
|
-- Wikimedia Commons Welcome (talk) 22:44, 22 November 2022 (UTC)
Reducing file sizes of national flags.
editPlease refrain from using SVGOMG to reduce file sizes of national flags on Wikimedia Commons.
- You have removed comments, linefeed characters, and tab characters which are intended to make the SVG source code easier to read. The code should be readable so that people (including you) can spot errors, redundancies, and inaccuracies.
- Some people have gone to great efforts to encode "perfect stars" which rely on rotations on SVG "use" elements. I don't tend to use them myself because they add a certain amount of bloat, but I accept that some people like them. What you have done is replaced the "perfect stars" with approximations while leaving behind the "use" elements; this means the stars are no longer perfect but the bloat remains. This is clearly not an optimization.
- You have in some cases gone overboard in rounding SVG path coordinates. I am not stating that rounding coordinates is never a bad thing; we don't need 10 significant digits when drawing and animals, trees, etc. But rounding coordinates on small text that is drawn as an SVG path may damage the text. MapGrid (talk) 22:54, 6 December 2022 (UTC)
- @VexilAlpaca: I am going to repeat: Please stop removing newlines, comments, title tags, and tabs from SVG files. These are useful elements that serve a purpose. Instead of discussing the problem you keep steamrollering ahead clobbering file after file. Your edits are causing far more harm than good. You are creating a toxic situation because you won't pause to even discuss the issue. MapGrid (talk) 00:54, 8 December 2022 (UTC)
Blocked
editRefusal to communicate with other editors is not acceptable, especially when you are making controversial changes to highly visible files. I have blocked you from editing until you start communicating properly. That includes, but is not necessarily limited to, clearly indicating that you understand why your changes were disruptive and how you will change that. Pi.1415926535 (talk) 05:33, 8 December 2022 (UTC)
- Okay, I will try to double check the file source code. VexilAlpaca (talk) 13:17, 8 December 2022 (UTC)
- @Pi.1415926535 I understand because I usually don't zoom in that far when making SVG files. Tiny imperfections are critical to other users, now I understand. Also, are line feed and tab characters necessary according to Commons policies, or is it just a preference? VexilAlpaca (talk) 13:29, 8 December 2022 (UTC)
- If there is an actual error in the SVG code, then fix the error. Otherwise, stop removing material you find unnecessary, as other editors may find these elements useful. Stop rounding coordinates as that disrupts the sometimes very precise placement of elements within the image. Take heed of what MapGrid writes above; they are very experienced when it comes to vector graphics.
- In general, stop using automated methods to compress SVGs, as these tools often cause more harm than good; generally it means saving only a few hundred bytes anyway. — Huntster (t @ c) 16:30, 8 December 2022 (UTC)
- See Help:SVG_guidelines#Useless_elements_that_should_be_kept for information about linefeeds and tabs. It is explicit in that
\n
,\r
, and\t
should be kept for better readablity. - Also, according to Help:SVG_guidelines#Optimizing_SVGs_that_have_already_been_uploaded, no SVG file should be overwritten unless the "content" is being improved. There are some exceptions, one of them being that it is okay to optimize a file if it can be reduced by more than 1MB. MapGrid (talk) 16:57, 8 December 2022 (UTC)
- I have known for about a month that, in SVGOMG, you can adjust the number of decimal places being rounded to, and if you select "Prettify markup", it keeps the line feed and tab characters. VexilAlpaca (talk) 00:00, 4 February 2023 (UTC)
- @Pi.1415926535 I understand because I usually don't zoom in that far when making SVG files. Tiny imperfections are critical to other users, now I understand. Also, are line feed and tab characters necessary according to Commons policies, or is it just a preference? VexilAlpaca (talk) 13:29, 8 December 2022 (UTC)
Unofficial rendition of the Emblem of Qatar
editCurrently we are missing the emblem of Qatar. There are currently unofficial versions of the coat of arms of Canada, Cyprus, Singapore, South Africa, and other countries, which are reconstructed from a description. I think someone should contact User:Sodacan because he has made many coats of arms, so we should ask him to draw an unofficial rendition of the emblem of Qatar, reconstructed from a description. VexilAlpaca (talk) 23:58, 3 February 2023 (UTC)
Sheild on Equatorial Guinea flag should be white
editthe sheild should be white on the flag since in vexillology silver on flags are colored white also the official website depicts the sheild white
https://www.guineaecuatorialpress.com/gobierno Skunkcrew (talk) 23:39, 5 September 2023 (UTC)
File:Flag of Kyrgyzstan.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. |