Commons:Graphics village pump

Shortcut
COM:GVP

Graphics community: Graphic Lab · Graphics Village Pump · Picture Requests · Photography Critiques · Photography terms

Welcome to the Graphics village pump!

Hello and Welcome to this Graphics village pump of Commons. This Graphics village pump aims to provide help and information about the several Graphic Labs spread in the Wikipedias, and to be the technical support forum for all the local Labs, graphists (graphic artists), and users interested in graphic works, and is a page where graphists and users from all the Labs can talk about graphics, tutorials, graphic software, help to build new Graphic Labs, etc. Also for exchanging opinions, ideas, protocols, and ways of improvement.

See also: Other graphic community pages (list on top) | Graphics abilities page | Graphic Tool | Project Insignia | Stroke Order Project | Current requests/discussions

Commons discussion pages (index)

Commons Help desk Community-wide general discussion Copyright Proposals Graphics and photography discussion Image improvement Photography critiques Categories for discussion Deletion requests Undeletion requests OTRS noticeboard Translators' noticeboard Work requests for bots Contact administrators Vandalism User problems (Dispute resolution) Blocks and protections Bureaucrats' noticeboard CheckUser requests #wikimedia-commons  webchat Commons mailing list (archive) Commons' bugs on Phabricator

Start a new topic

Graphics village pump archives

Monthly archives
2007	–	–	–	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2008	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2009	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2010	Jan	Feb	–	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2011	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	–	Dec
2012	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2013	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	–	Dec
2014	Jan	Feb	Mar	Apr	May	–	Jul	Aug	Sep	Oct	Nov	Dec
2015	Jan	–	Mar	Apr	May	Jun	Jul	–	Sep	Oct	Nov	Dec
2016	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	–	Nov	Dec
2017	–	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
Topic-specific archives /GIF thread

svg file size

Hi. I have made a 4 MB svg file. It is smaller then 10 MB limit. When I click on the image ( like here but please reload the page ) I see some animations. It takes a few ( 5) seconds to open full image on my computer ( 15 GB Ram)

When I ask other people about it :

• "for me both the new and the old version do not really show an animation, but after some time of loading there is a presumably complete image. I did not complain about this earlier, because i blames it on my old hardware and slow internet connection ..."
• "I clicked on the image yesterday, but I am travelling, with a very small laptop with only 2GB RAM and when I clicked on it, the CPU went to 100% for two minutes and nothing happened."

Could you check it ? TIA --Adam majewski (talk) 15:49, 6 April 2018 (UTC)

The problem is that your script is generating a large number of circles along the curves, which increase the file size and slow down the rendering, but aren't actually visible. Unfortunately I'm not familiar with Maxima's draw2d function, but what you want to do is to completely disable the rendering of points wherever you use "points_joined = true". TilmannR (talk) 13:09, 16 May 2018 (UTC)

I have diminished the number of points inside curves ( not all are circles) so that size also diminished, but still is to big for many computers. Thx. --Adam majewski (talk) 17:26, 19 May 2018 (UTC)

Diagonally striped pattern on svg country map

Hello guys,

I'm trying to fill countries with a diagonally striped pattern on a svg world map in this kind of style, however, just filling countries instead of regions would be fine. Colors should be able to be determined with the ability to create transparent stripes. There are instructions on how to entirely fill and circle countries, but the above feature is missing. Anyone here who could extend the instructions or comment? Would like to use this map outside of Wikipedia in case there are different rendering requirements.

— Preceding unsigned comment added by MiMoHo (talk • contribs) 09:42, 11 April 2018 (UTC)

Getting full resolution from Apple Photos on OS-X

I have been trying to upload photos taken with my iPhone X. I used to use the Commons app, but that is no longer supported. The method I am now using is to import the photos using Apple's Photos application on OS-X (everything up to date). I then export the photos from Photos as jpg files, which I then upload to Commons using the standard upload tool. Even at Photo's maximum jpg export setting I get reduced resolution. For example in File:Differential Analyzer CHM.agr.jpg, which I recently uploaded, the labels on the various controls appear crisp and fully legible on my Photos screen, but are somewhat blurry on Commons even when selecting full resolution. Is there another way to upload the file at the full resolution the iPhone produces? I have many more photos that I would like to upload at full resolution.--agr (talk) 15:47, 30 May 2018 (UTC)

@ArnoldReinhold: Have you tried backing up your iPhone to iCloud and then downloading the photos from icloud.com using a web browser?   — Jeff G. ツ _{please ping or talk to me} 06:06, 31 May 2018 (UTC)

@Jeff G.: Thanks for your suggestion. I looked at the same Differential Analyzer CHM.agr.jpg Commons file again today and it looks fine. There must have been some database delay in updating the higher resolution image I uploaded. It's a relief actually as I have a number of photos to upload and there are too many steps as is.--agr (talk) 16:25, 31 May 2018 (UTC)

@ArnoldReinhold: You're welcome.   — Jeff G. ツ _{please ping or talk to me} 17:55, 31 May 2018 (UTC)

SVG text rendered incorrectly despite using officially supported fonts

Hi,

meta:SVG fonts explicitly mentions DejaVu Sans and Liberation Sans. Also, Wikimedia pages themselves use the "Linux Libertine" font for section headings. The heading of this section is rendered in Linux Libertine!

I have created four SVGs containing text in Inkscape. The text should be easily editable using a text editor, the file should stay PD-ineligible, and the file size should not increase too much. For these three reasons, I do not want the text to be replaced by paths. Instead, I would like to use a font that allows correct rendering of thumbnails. I tried the three fonts mentioned above and failed.

The four SVGs: File:Smartscreen-warning-1.svg, File:Smartscreen-warning-1-arrow.svg, File:Smartscreen-warning-2.svg, File:Smartscreen-warning-2-arrow.svg

The text in these images has characters which overlap each other for no apparent reason. Instead of a normal text flow, characters are incorrectly moved to the left/right, causing them to stick together visually. It almost looks as if these characters are stored in the SVG one-by-one, each with a specific (wrong) position. This, however, does not actually seem to be the case, as opening the SVG with a text editor shows.

I tried searching the village pump archive and the Help:SVG page, but I might have overlooked something. If the issue is known, I would be happy about someone pointing me to a relevant FAQ entry or previously solved case. ~ ToBeFree (talk) 16:15, 6 June 2018 (UTC)

Additional note: The "more info" text has a "text-decoration: underline;" CSS attribute, which is rendered correctly in Firefox when opening the SVG. The MediaWiki thumbnail renderer, however, appears to completely ignore it. ~ ToBeFree (talk) 16:19, 6 June 2018 (UTC)

You've run into the librsvg small font-size quantization bug: Phab:T36947. Small font escapement and baseline placement have problems. For example, one of your files (File:Smartscreen-warning-2-arrow.svg) uses font sizes of 2.82222223px, 4.23333311px, 6.3499999px, 10.58333302px, 16.93333244px. That's small enough to tickle the bug.

For font-families, the list of supported fonts is not always right. I think your fonts can be found by librsvg, but they may not be found by other user agents (such as my browser). In any event, the font-family should include a generic font such as serif, sans-serif, or monospace.

The coordinate system used in the diagram is contorted (viewBox="0 0 132.29166 66.145833", translate(0,-230.85417)).

See also Help:SVG, Commons:Commons SVG Checker.

Glrx (talk) 02:03, 7 June 2018 (UTC)

Wow Glrx, this is amazing. Thank you very much for taking the time to explain all these points; I would probably never have found out!

I'm copying this to my talk page on en.wikipedia to remind myself of fixing these issues as soon as I can. The contorted coordinate system is a really strange thing. I was already surprised that Inkscape's SVG coordinate system seems to begin at the bottom left, but it made sense to me (mathematical x-y-coordinate systems do look like that). I have no idea where the crazy value of "-230.85417" comes from, and I will have a look at SVG manuals to learn what this "translate" attribute does. I'll inspect the source code and do a lot of cleanup there. The phabricator bug is also very nice to know. About the font-families, strange, I would have expected Inkscape to do that sort of thing automatically, at least for the very basic "serif" or "sans-serif" or "monospace" fallback. I wasn't aware that this is likely missing from all SVGs I have ever created!

The Commons SVG checker seems to be an awesome tool and just what I have been looking for, too. Thanks again! ~ ToBeFree (talk) 04:10, 7 June 2018 (UTC)

White space around SVG image

I uploaded a SVG file and did not notice it had a large white space around it. Do I start over or can I edit in Commons?

@BrucePL

— Preceding unsigned comment added by BrucePL (talk • contribs) 19:48, 6 June 2018 (UTC)

Hi @BrucePL:! You can overwrite existing files. If you don't have access to the original file anymore, you can download it from Commons. Edit it, possibly using a text editor or your SVG editing tool, correct the whitespace, and then feel free to "Upload a new version of this file". The link for that is available on the image page. ~ ToBeFree (talk) 21:19, 6 June 2018 (UTC)

Stripping metadata

Tracked in Phabricator
Task T20871

Wikimedia Commons strips IPTC metadata - descriptions, attribution, copyright management information and that sort of thing - from all but its “full resolution” downloads.

Note that I’m not talking about Exif camera logging information here. I’m talking about information that creators deliberately attach to their work to enhance its cultural value and to protect its copyright. (The same information that we require of all contributors, actually.) And note also, that we DO respect that information on ONE of the offered renditions of a photo.

Clearly, this is a bad thing. Karmically, it’s an unkind thing to do to contributors’ works. Legally, decisions are slowly marching toward the day when penalties for the removal of copyright management information will be applied specifically to the removal of embedded metadata. (And regardless of Terms of Use or Safe Harbor defenses.) At scale, those penalties can be ghastly. (As penalties should be, really. That’s the point of them.)

I doubt there would be any argument that we shouldn’t fix this. So, the question is: HOW do we fix this? WHO, exactly, needs to fix this, for that matter?

On most tiny little websites like mine, it’s a matter of a few minutes effort and it’s all fine. For a site this big, it could be a whole different kettle of fish. Or not, it could actually be easier. The first step is to figure out how to proceed.

Now, I’m also not addressing the fairly obvious question of why people - in droves - who are sharing works that depend on attribution would post them without taking the effort to write their names on them. (Ah, because they didn’t know that they could, let alone should?) That’s an education issue. But prerequisite to educating, scolding, and cajoling, we should make sure that we don’t delete contributors’ good efforts.

Education and encouragement is a conversation that we absolutely should have, but later, IMHO.

I advocate on this issue. I have a blog that’s full of sometimes-nerdy information on the subject: metadatamatters.blog

I’ll help in any way I can.

— Preceding unsigned comment added by Carlseibert (talk • contribs) 19:01, 21 June 2018 (UTC)

Hi @Carlseibert:, thanks for posting here. This particular feature has been debated for years now − you may see some historical information on phab:T20871.

To answer your question « would there be any argument against this », my understanding of why it’s being done is because EXIF take up a lot of space (in some cases bigger than the thumbnail itself).

Hope that helps, Jean-Fred (talk) 07:02, 22 June 2018 (UTC)

Ok, so I checked and there are some EXIF fields preserved in Thumbnails, including Author and Copyright.

@Carlseibert:, could you clarify which fields you would like to see preserved? I realise you said IPTC and I read EXIF :) but it would be helpful nonetheless to understand which fields matter and which not.

Jean-Fred (talk) 07:17, 22 June 2018 (UTC)