Commons:Graphics village pump

From Wikimedia Commons, the free media repository
(Redirected from Commons:GVP)
Jump to navigation Jump to search

Shortcut

color palette logo WELCOME TO THE GRAPHICS VILLAGE PUMP!

This Graphics village pump aims to be technical support forum for all the local Labs, graphists (graphic artists), and volunteers 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: Graphics abilities page | Graphic Tool | Project Insignia | Stroke Order Project | Current requests/discussions


To have the opinion of graphists check

Illustration Workshop   Map Workshop   Photography Workshop   Video and Sound Workshop

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
2018 Jan Feb Mar May Jun Jul Aug Sep Nov Dec
2019 Jan Feb Mar Apr May Jun Jul Aug Sep Nov Dec
2020 Jan Feb Mar Apr May Jun Jul Aug Sep
2021 Mar Apr Jun Jul Aug Sep
2022 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2023 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Topic-specific archives

This map lacks an legend. What do the colours mean? Grullab (talk) 19:57, 11 August 2023 (UTC)Reply[reply]

Possible clue: File:Berber Language Tutlayt Tamazight-HE.png. See subcategories of Category:Linguistic maps of Berber languages. Glrx (talk) 13:25, 12 August 2023 (UTC)Reply[reply]

On the file page this looked good, but when I clicked on it it was 90 degrees off so I requested rotation. Now it still looks good on the file page and also when you click on it. However in the file history section it looks 90 degrees off. What's weird with this file? Jonteemil (talk) 23:11, 25 August 2023 (UTC)Reply[reply]

@Jonteemil: The file has an EXIF orientation instruction of "Rotate 270 CW". The file was uploaded in 2014, which (if I remember correctly) was before the thumbnailing system got support for reading EXIF orientation instructions. This means it would produce a thumbnail pointing to the left. This thumbnail was then cached indefinitely, which is why you still saw it today. The file has been purged since, so the thumbnail has been regenerated and should appear correctly if you bypass your cache. Because the file is below a certain size, the file page displays the original file, which means that your browser interpreted the EXIF orientation instruction. --AntiCompositeNumber (talk) 22:52, 4 October 2023 (UTC)Reply[reply]
I see. So we can either have https://upload.wikimedia.org/wikipedia/commons/thumb/2/28/%22Lord_Mayor%27s_Show%22_London_2006_%28295241830%29.jpg/400px-%22Lord_Mayor%27s_Show%22_London_2006_%28295241830%29.jpg look good or https://upload.wikimedia.org/wikipedia/commons/2/28/%22Lord_Mayor%27s_Show%22_London_2006_%28295241830%29.jpg, but not both? What is more preferable? — Preceding unsigned comment added by Jonteemil (talk • contribs) 22:57, 4 October 2023‎ (UTC)Reply[reply]
@Jonteemil: They look the same to me. Any difference is probably just cached by your browser. --AntiCompositeNumber (talk) 01:11, 5 October 2023 (UTC)Reply[reply]

The svg is valid according to Validator.nu and is rendered flawlessly by Chrome, Firefox, and https://svgcheck.toolforge.org/index.php, which states "This image was rendered using rsvg-convert version 2.40.21, almost certainly the same version as in use on Wikimedia wikis."

Still, the text in the automatically generated PNGs is grossly misplaced. I have resized a screenshot to 800×318. How can I use that PNG as a substitute for the rsvg-generated ones? --Rainald62 (talk) 21:30, 13 November 2023 (UTC)Reply[reply]

@Rainald62: WMF renders the image using the 5 year old librsvg v 2.44.10. That version has a bug with centered and right aligned text. That bug was fixed in the more recent librsvg v2.40. Glrx (talk) 21:35, 13 November 2023 (UTC)Reply[reply]
@Rainald62: I have worked around this problem by avoiding <tspan> elements completely. I now use separate <text> elements, and specify attributes (especially "x=" and "y=" attributes) inside each <text ...> element. RCraig09 (talk) 22:22, 13 November 2023 (UTC)Reply[reply]
You can still use tspan as long as you specify x – the bug arises when there are multiple non-left-justified tspan on a line with x unspecified. It might be better to keep related tspan together as styling their parent text keeps their appearance consistent. cmɢʟee ⋅τaʟκ 23:45, 13 November 2023 (UTC)Reply[reply]
@RCraig09: <tspan> elements nicely fit together and keep doing so on a change of font, while separately positioned <text> elements could overlap or leave gaps.
@Glrx: Do you really mean that v2.40 is more recent than v2.44? Because svgcheck uses another version as WMF, I had to do experiments by uploading several versions.
The latest experiment (00:34) was a copy of the original file from User:DeWikiMan. It is also not converted properly to PNG. Obviously, there was a regression in PNG generation since the original version had been uploaded in 2018.
I reverted to my first version, which (viewed as svg) is the best one. Just ignore the bad thumbnail PNG. WMF has enough money to fix the problem. --Rainald62 (talk) 00:26, 14 November 2023 (UTC)Reply[reply]
@Rainald62:
Yes, I really mean it. Version 2.44.10 is an early release of the Rust language conversion. It is older than the most recent version of 2.40, the last release of the C++ version. WMF should be running version 2.50 or later. WMF's "update" in April 2023 introduced a few regression errors.
I would not modify SVG files to work around this problem. WMF should run more recent versions of librsvg.
Glrx (talk) 01:39, 14 November 2023 (UTC)Reply[reply]
Thanks for the clarification and the endordsement not to work around. Who can clean up the file's version history (delete all but the first two versions)? --Rainald62 (talk) 08:40, 14 November 2023 (UTC)Reply[reply]
@Rainald62: Inkscape makes the .svg text files too long and complicated. I still think the simplest solution is to simplify <text> specifications as I do in File:1880- Global average sea level rise (SLR) - annually.svg, though it requires manual text editing. Whatever your approach, good luck! (I don't know who to ask, to remove unwanted versions; it usually isn't done. Maybe open a separate section here on the Village Pump if it's important to remove earlier versions.) RCraig09 (talk) 17:27, 14 November 2023 (UTC)Reply[reply]
Nice code. I won't further edit the Inkscape mess. I won't proceed at all without an idea how to get "CO2" with subscript and 90° rotation. Here is what I tried: File:Test workaround.svg (some comment lines contain the test result for the previous version). Feel free to continue. --Rainald62 (talk) 17:41, 14 November 2023 (UTC)Reply[reply]
I removed unnecessary #text nodes; a newline after a tspan element exacerbates the issue. Unicode subscripts can be used for carbon dioxide: CO2 → CO₂, but it is not needed here because the librsvg bug has little impact on the placement of the text. Glrx (talk) 19:00, 14 November 2023 (UTC)Reply[reply]