Template talk:SOlicense

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Extract Unicode Codepoint as well from file name[edit]

Step 2[edit]

Extract informations need from the image name :

  • the chinese character
  • the country code
  • the "graphic style code + extension"
  • the Unicode code point

I suggest using a simple function that will convert the character to its codepoint so there can be a link to the Unicode Unihan database as this is only good for code point values and not for characters. The new license would then have to look somewhat like this:

{{SOlicense|<character>|<unicode codepoint>|<variant>|<image-type>.<suffix>|<extra info>}}

as to preserve grouping of like data, i moved the codepoint after the character.

Also, the last tag, other versions, should probably not search for the same filename, as it is always going to find itself! It should be somehow possible to change {{#ifexist: Media:{{{1}}}-{{{2}}}{{{3}}}|[[Image:{{{1}}}-{{{2}}}{{{3}}}|30px]]|not available.}} to something that looks for all other files {{{1}}}-{{{2}}}{{{gif|jpg|svg}} or something. ✓ Done

--Tauwasser (talk) 22:36, 16 January 2009 (UTC)[reply]

Can you give a more detailed rational for this? --Swift (talk) 04:00, 21 January 2009 (UTC)[reply]

Step 3[edit]

Another requirement is to categorize each of this files automatically by SOlicense into the Category:Radical ###, by its radical number. This would be done by an additional parameter giving this number. The other option would be to add an additional line to each file with [[Category:Radical ###]]. --Sarang (talk) 09:00, 26 June 2009 (UTC) ✓ Done (now: Radical ###–0)[reply]

New template[edit]

There are a lot of changes that should/need to be made to this template. Rather than discuss each individually in some hypothetical manner, I'm starting a new template at {{SOP license}}. --Swift (talk) 08:38, 21 January 2009 (UTC)[reply]

Japanese source to add[edit]

If I remember well, user user:M4RC0 made his japanese stroke order pics according to:

Kanji et Kana , Manuel de l'écriture japonaise et dictionnaire des 1945 caractères officiels, by Wolfgang Hadamitzky, Pierre Durmous, 1991.

I didn't found the ISBN. Yug (talk) 17:31, 28 January 2009 (UTC)[reply]

978-0804833929 and 978-0804835053? There are different versions, too. Those are the English versions, however, I know one German book that also has the "1945 characters" in its booktitle, can't find it at the moment, though. Those books should have the same contents, regardless. Also, there is WWWJDIC for many stroke orders, many of the basic ones as well! --Tauwasser (talk) 18:40, 28 January 2009 (UTC)[reply]

spelling[edit]

{{Editprotected}} should "RPC authoritative work" be changed to "PRC authoritative work"? (People's Republic of China) --Liangent (talk) 06:44, 24 August 2009 (UTC)[reply]

It is already changed in the new Template:SOP license, but yeah, we might want to petition an admin. Maybe it is like that because some of the project's original creators were french? --Tauwasser (talk) 09:03, 25 August 2009 (UTC)[reply]
✓ Done, thanks. Pruneautalk 18:14, 25 August 2009 (UTC)[reply]

4th param[edit]

The 4th parameter <extra info> is not checked or evaluated at all. It is almost nowhere used, may be there is no need for it? Because of the rendering effort (the template is used about 1650 times), I hesitate with the minor fix to repair that obviously obsolete bug. -- sarang사랑 12:14, 26 January 2010 (UTC)[reply]

SVG images[edit]

Hi, I just uploaded an SVG image for 本 here: I also manually uploaded a png version of that here: . The problem is that the png version doesn't give any details about the svg file. If there any way that I can change it? Thanks. Durand (talk) 02:22, 30 January 2010 (UTC)[reply]

Good work! FanNihongo (talk) 23:34, 14 November 2021 (UTC)[reply]

Edit request for section headings[edit]

{{Edit request}} Add section headings == {{int:filedesc}} == and == {{int:filedesc}} ==. Per Commons:Guide to layout. 80.221.159.67 18:09, 16 September 2016 (UTC)[reply]

Edit request to change license to public domain[edit]

{{Edit request}} It seems unlikely the images where this template sees actual use is enough to meet the threshold of originality to be eligible for copyright. Use {{PD-text}} or {{PD-ineligible}}? 80.221.159.67 18:12, 16 September 2016 (UTC)[reply]

 Not done Each individual frame might be PD-text, but I doubt a whole animation would be. If you disagree please demonstrate consensus has been acheived on COM:VPC or another suitable forum. Storkk (talk) 11:03, 29 September 2016 (UTC)[reply]

Edit request to change license for to public domain for "red images"[edit]

{{Edit request}}

An edit request was made in 2016 to change the license for these images to the public domain. I agree that the copyright statuses of the animations and even possibly the arrow graphics may be in dispute, but the "red" images are unambiguously in the public domain because they are a raster rendering of a single character of text. Coloring a single character in various shades of red is not sufficient to meet the threshold of originality required under copyright law. Please change this template such that all SO files ending in "-red.png" have a public domain license tag.  Mysterymanblue  07:47, 1 March 2021 (UTC)[reply]

As this is not a protected template, I made the changes myself. Here is my rationale for the changes I made:
* I made it such that the "red.png" images will have a public domain tag in addition to their already existing licensing tags. This is because these images are unambiguously below the threshold of originality.
* I also made it such that the permission field for "red.png" images says "Public domain" instead of "Courtesy & permission & copyright by the uploader."
* There is an undocumented yet still supported "license" parameter that may be used with this template. Setting this parameter to "PD" would set the license on the file to {{PD-ancient-script}}, allowing the uploader to enter the file into the public domain. This was problematic because {{PD-ancient-script}} only applies to SVG renderings, so this parameter would show an incorrect license for non-SVG templates. Therefore, I changed the template such that it would use {{PD-self}} for non SVG files; the public domain dedications for {{PD-self}} and {{PD-ancient-script}} are essentially identical, so the two are equivalent.
* I also made it such that setting the "license" parameter to "PD" would cause the permission field to read "Released into the public domain by the uploader"  Mysterymanblue  09:03, 11 July 2021 (UTC)[reply]