overwritten file

I'll revert your "updated" File:Nuvola_apps_locale.svg back to the original file that was uploaded under that name because yours has different content, doesn't fit the style of the Nuvola icon set, and doesn't match File:Gswitchit-applet.svg anymore, which might be keeping people from using the file instead of the PNG version. Please always upload files with different content under a new file name. And maybe reupload your file under a different name and maybe check uses of File:Nuvola_apps_locale.svg if you believe that they actually should/want to use your version instead.--Reseletti (talk) 15:32, 15 December 2017 (UTC)Reply

In fact, I'd like to revert all of your "updates" to David Vignoni's Nuvola files. And maybe even have all your original content you labeled "Nuvola" renamed. See here and here for more detailed rationale.--Reseletti (talk) 17:55, 24 December 2017 (UTC)Reply

File:Flag of the Federal Republic of Southern Cameroons.svg

 

Hi! I'm afraid I've messed up a little. I've been trying to change the proportions of the flag from the arbitrary 585:360 to the standard 3:2. However, something always goes wrong; for instance, I just realized that the olive branch has only one leaf left. Would you be able to restore the version you uploaded back in 2014, but with the proportions 3:2? Regards, Mikrobølgeovn (talk) 20:00, 16 February 2019 (UTC)Reply

Done. The differences I can see between the 2014 file and yours, besides the malformed olive branch, are the smaller eye and the removal/replacement of the gradients on the wings and beak—should those changes be redone? SiBr4 (talk) 10:08, 17 February 2019 (UTC)Reply
Thank you very much! The differences you mentioned were not intentional, and owed entirely to the fact that I'm a complete noob at editing svg files. The gradients looked different because they changed positions when I uploaded the file to the software I used, so I had to manually move them back. The eye also disappeared, so I had to make a new one. I'll probably refrain from uploading new versions of svg images before I've gained some experience in editing them. Thanks for responding so soon, and cheers! Mikrobølgeovn (talk) 18:14, 17 February 2019 (UTC)Reply
What is the software you used? The problem with the eye and leaves indicates that the program can't handle path elements with multiple sub-paths, only keeping the first sub-path and discarding the rest. The gradients moving sounds like a rendering issue on the software's part as well. SiBr4 (talk) 16:28, 18 February 2019 (UTC)Reply
I just used one of those free online ones. Lesson learned! Mikrobølgeovn (talk) 16:36, 18 February 2019 (UTC)Reply

Category:Districts_in_the_United_Kingdom

 

Districts in the United Kingdom 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!


Rodhullandemu (talk) 17:52, 8 October 2019 (UTC)Reply


Notification about possible deletion

 
Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.

If you created these pages, please note that the fact that they have 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 them, 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!

Finnusertop (talk) 15:13, 19 February 2020 (UTC)Reply

File:Flag of Kiribati.svg

 

Hi, due to Corona I started to use my time at home to learn some basic SVG coding. To experience it on a real example, I tried to code the Flag of Kiribati according to the official flag design from the Kiribati National Identity Act [1]. I managed to get the correct British Standardization Colours translated into HEX code from the website perbang.dk and applied the waves, the rising sun and the plane triangles correctly according to the measurements (which can also be found on fotw [2]). The code looks like this:

   <svg width="600" height="300">
      <rect width="600" height="162" fill="#C81010" />
      <g fill="#f8d000" stroke="#000" stroke-width="0.5">
      <polygon points="300,63 291,106 266,69 273,113 237,87 259,125 217,115 251,142 207,147 249,161 211,181 226,212 251,235 283,247 317,247 349,235 374,212 389,181 351,161 393,147 349,142 383,115 341,125 363,87 327,113 334,69 309,106" style="fill-rule:evenodd" />
      <circle cx="300" cy="156" r="51"/>
      </g>
      <rect x="0" y="162" width="600" height="138" fill="#183070" />
      <g id="wave">
      <path d="M-36,168 Q-6,156 24,168 54,180 84,168 114,156 144,168 174,180 204,168 234,156 267,168 300,180 333,168 366,156 396,168 426,180 456,168 486,156 516,168 546,180 576,168 T636,168"
      fill="none" stroke="#fff" stroke-width="24"  />
      </g>
      <use xlink:href="#wave" y="48"/>
      <use xlink:href="#wave" y="96"/>
   </svg>

I couldn't code the curvy triangles and the bird though. Do you have an idea how to implement them according to the legal measurments into the flag?

Best greets, --Hanzlan (talk) 13:10, 19 March 2020 (UTC)Reply

@Hanzlan: Nice find. Commons is usually quite good at following official specifications when they exist, though this file doesn't seem to have been changed geometrically since its first version. The act is more detailed than I'd have thought, especially in the bird, but it is not completely geometrically conclusive. It's also odd how the central part of the waves has a specified width (61/100−39/100 = 22/100) contradicting the overall "wavelength" of 20/100.
Regarding the sun, the act does not clarify the exact shape of the wavy sunrays; it does refer to them as "spherical triangles", which I'm assuming means they should be circular arcs of unspecified radius. These are quite easy to implement in SVG code, since unlike Beziers (such as the Qs you've used above) they don't require knowing any intermediate control points or angles:
<path d="M290.63,105.87 A 50,50 0 0,1 300,66 A 50,50 0 0,0 309.37,105.87"/>
Other than the start and end points of the two curves (290.63,105.87, 300,66 and 309.37,105.87), the only number determining the shape is the arc radius, which I've arbitrarily set to 50. (Tbe zeroes and ones in between specify which way around the arc goes; see here for details.)
Another thing the act doesn't specify is the (angular) spacing of the rays. Since they should be "contiguous" (which probably means touching on the edge of the circle), this also impacts their width and thus their start and end points. I've gone with the 17-gonal symmetry your sun uses (i.e., 360°/17 = 21.18° between the rays); the current version has 18-gonal symmetry, though it doesn't conform to the qualification that "[t]he first and ninth [straight] triangles are partially obscured by the crests of the waves". Here is a mockup of the full half-sun, using cloning and rotation around the sun's midpoint (300,156) to complete the number of rays. The 12-degree rotation on the original wavy ray is the offset from the adjacent straight ray, and was again arbitrarily chosen based on what looks best.
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="600" height="300">
  <g fill="#f8d000" stroke="#000" stroke-width="0.5">
    <g id="rays_6">
      <g id="rays_2" transform="rotate(-84.706,300,156)">
        <path id="wavy" d="M290.63,105.87 A 50,50 0 0,1 300,66 A 50,50 0 0,0 309.37,105.87" transform="rotate(12,300,156)"/>
        <path id="straight" d="M290.63,105.87 300,63 309.37,105.87"/>
      </g>
      <use xlink:href="#rays_2" transform="rotate(21.18,300,156)"/>
      <use xlink:href="#rays_2" transform="rotate(42.35,300,156)"/>
    </g>
    <use xlink:href="#rays_6" transform="rotate(63.53,300,156)"/>
    <use xlink:href="#rays_6" transform="rotate(127.06,300,156)"/>
    <circle cx="300" cy="156" r="51"/>
  </g>
</svg>
As for the bird, that's definitely the kind of thing I would just do in a GUI vector editor like Inkscape, by tracing from a raster image (or just copying the current SVG's bird) and modifying it according to the given measures. The whole process of creating SVGs starts visually for me, most often messing around in Inkscape before either recreating the parts in plain code or, for more complex or less geometrically defined shapes and symbols, saving the file as optimized SVG and going from there.
I probably didn't do a great job explaining what I did, but please ask if there is anything specific that is unclear. SiBr4 (talk) 14:00, 25 March 2020 (UTC)Reply
@SiBr₄: Thank you for your detailed description, and no, it was fully comprehensible to me. I agree with you in the inconsistency of the act in geometrical flag definitions, especially when it comes to the spherical triangles. For now, I have updated the flag and added a more detailed version of the frigate bird, where I have to thank Mr Villascán for sending me the svg graph he created for FOTW. I think it looks much better now than before, but I am still struggling with the spherical triangles: On one hand they are really accurate now having their tips exactly between the tips of the straight triangles and being triangles whose sides start from the sun disc. On the other hand they give a kind of asymmetry to the sun as they are leaning to the left due to their spherical character, especially when looking at the triangles of the "red sky" between the rays of the sun. So, there are many options left:
  1. Leave it like it is.
  2. Sacrificing the symmetry of the triangle's tips by shifting the spherical triangles slightly clockwise.
  3. Sacrificing the base of the spherical triangles at the sun disc and move it further outwards to make them look wider.
  4. Sacrificing the isoscelity of the spherical triangles by making the right sides rounder.
  5. A combined solution of 2 and/or 3 and/or 4.
I'm curious about your opinion of the redesigned version and thank you a lot for the code! With best regards, --Hanzlan (talk) 13:29, 27 March 2020 (UTC)Reply
The current version actually already uses option 2. I originally had the tips of the wavy points exactly halfway between those of the straight points, by setting the offset I mentioned to 10.59° (360/34, or half of 21.18), but moved them clockwise to 12° because they looked off. Since the act doesn't specify anything about the rays other than the circle the tips lie on, you/we are free to vary this offset (or the ray's width or the radii of the two arcs, for the other options) and choose what looks best.
With the current shape of the rays, the angle where a wavy ray intersects the adjacent straight rays at equal distances from the center seems to be around 14.4°. A larger offset of course also moves the tip further away from the center, so there is no objective "best" angle. I think the low 13s strike a nice balance. SiBr4 (talk) 16:03, 27 March 2020 (UTC)Reply