User talk:Jc86035

From Wikimedia Commons, the free media repository
Jump to: navigation, search
Welcome to Wikimedia Commons, Jc86035!

-- Wikimedia Commons Welcome (talk) 14:48, 30 July 2012 (UTC)

Picture of the Year 2013 R2 Announcement[edit]

Round 2 of Picture of the Year 2013 is open![edit]

2012 Picture of the Year: A pair of European Bee-eaters in Ariège, France.

Dear Wikimedians,

Wikimedia Commons is happy to announce that the second round of the 2013 Picture of the Year competition is now open. This year will be the eighth edition of the annual Wikimedia Commons photo competition, which recognizes exceptional contributions by users on Wikimedia Commons. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2013) to produce a single Picture of the Year.

Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year were entered in this competition. These images include professional animal and plant shots, breathtaking panoramas and skylines, restorations of historical images, photographs portraying the world's best architecture, impressive human portraits, and so much more.

There are two total rounds of voting. In the first round, you voted for as many images as you liked. The top 30 overall and the most popular image in each category have continued to the final. In the final round, you may vote for just one image to become the Picture of the Year.

Round 2 will end on . Click here to learn more and vote »

the Wikimedia Commons Picture of the Year committee

You are receiving this message because you voted in the 2013 Picture of the Year contest.

This Picture of the Year vote notification was delivered by MediaWiki message delivery (talk) 19:21, 22 February 2014 (UTC)

Picture of the Year 2013 Results Announcement[edit]

Picture of the Year 2013 Results[edit]

The 2013 Picture of the Year. View all results »

Dear Jc86035,

The 2013 Picture of the Year competition has ended and we are pleased to announce the results: We shattered participation records this year — more people voted in Picture of the Year 2013 than ever before. In both rounds, 4070 different people voted for their favorite images. Additionally, there were more image candidates (featured pictures) in the contest than ever before (962 images total).

  • In the first round, 2852 people voted for all 962 files
  • In the second round, 2919 people voted for the 50 finalists (the top 30 overall and top 2 in each category)

We congratulate the winners of the contest and thank them for creating these beautiful images and sharing them as freely licensed content:

  1. 157 people voted for the winner, an image of a lightbulb with the tungsten filament smoking and burning.
  2. In second place, 155 people voted for an image of "Sviati Hory" (Holy Mountains) National Park in Donetsk Oblast, Ukraine.
  3. In third place, 131 people voted for an image of a swallow flying and drinking.

Click here to view the top images »

We also sincerely thank to all 4070 voters for participating and we hope you will return for next year's contest in early 2015. We invite you to continue to participate in the Commons community by sharing your work.

the Picture of the Year committee

You are receiving this message because you voted in the 2013 Picture of the Year contest.

Delivered by MediaWiki message delivery (talk) 22:59, 26 March 2014 (UTC)

MTR map[edit]

I guess you missed my message in your English WP talk page, but more importantly I don't think it's a good a idea to remove the ID attributes of the station nodes in the MTR map last updated by you. Those IDs indicate which node belongs to which station without guesswork when editing the SVG with text editor. In the name of AGF, you removed them unintentionally in graphical software but still it's better to restore them anyway. -- Sameboat - 同舟 (talk) 00:48, 8 August 2014 (UTC)

NYC Subway map[edit]

I just noticed your edit request in File talk:NYC subway-4D.svg for a weird reason (not because I stalked your contributions). CountZ certainly isn't entirely dormant on English WP but not quite active either. I can help you to create a new NYC Subway map, whether you start it with Inkscape or Notepad (nonetheless I hope you opt for the latter). The only thing prevents me from starting it by myself is that I am not yet familiar with the rail system so someone other than me has to take the initiative. You can think of this as an opportunity to improve what is lacking or unsatisfying in NYC subway-4D.svg. -- Sameboat - 同舟 (talk · contri.) 11:18, 24 May 2016 (UTC)

@Sameboat: I won't be able to do much work on that until the start of June due to exams; maybe you might want to begin some work on it first. I'd probably base the map on one of the templates on your userpage. Jc86035 (talkcontributionsuploads) 11:27, 24 May 2016 (UTC)
OK. If you're terribly bored during your exam days, you may list the rest of changes/improvements you want from NYC subway-4D.svg. -- Sameboat - 同舟 (talk · contri.) 04:04, 26 May 2016 (UTC)

Platform number position accuracy[edit]

I know what is happening, and I can firmly tell you that there is no cure for the inaccuracy. Your best bet is to convert the numerals into path in Inkscape and copy the path data to Notepad. This issue plagues my Moscow Metro map as well and frankly I just let it go, let it go, that perfect boy is gone~~ -- Sameboat - 同舟 (talk · contri.) 09:32, 10 June 2016 (UTC)

Renaming horizontal double lines[edit]

After this you cannot claim I don’t have good faith or loyalty toweards the BSicon community. Please however refrain from renaming my correctly named vFOO-q icons into the inane naming scheme FOO-. As explained, its main raison d’être is the fact that it was used for many icons; lets keep it that way and dicuss the naming criteria on their merits. Or else I’ll do the opposite work and, within 24 h, rename/move to vFOO-q all those named as FOO-, using the same decieving tactics you’re attempting, just more effectively. Thanks very much. -- Tuválkin 12:35, 4 August 2016 (UTC)

@Tuvalkin: When adding the move requests, I thought I was reverting my own erroneous moves from last October (because I didn't know about the FOO-FOO naming pattern). On Talk:BSicon/Renaming, when I questioned your use of the vFOO-FOOq naming I was only referring to the KRZ set, which – for the most part – adds v after KRZ instead of using dashes or q or whatever. If we were to review the naming of (non-KRZ[1]) FOO-FOO icons, I would probably prefer to move them to vFOO-FOOq. Maybe you should start a section at the bottom of Talk:BSicon/Renaming. —Jc86035 (talkcontributionsuploads) 12:52, 4 August 2016 (UTC)


  1. The o and u suffices work nicely instead, so q, I guess, isn't necessary for most of the icons.
I already explained in Talk:BSicon/Renaming how to use the q suffix properly and solve with one simple rule all these cases for which some people keep inventing more and more complex and detailed rules and exceptions. Good luck with that.
Also: Keep renaming my images against my will as a wait to create a fait accompli in renaming dicsussions and I’ll stop creating new images. To go against people who should be working with me for a common goal because they cannot understand simple concepts is something I do when only I get paid to.
-- Tuválkin 01:17, 5 August 2016 (UTC)

About Akc1902[edit]

TBH s/he drives me crazy and I really want to apply topic ban on all MTR articles for this person. Maybe I have low acceptance or tolerance. -- Sameboat - 同舟 (talk · contri.) 21:56, 29 October 2016 (UTC)

@Sameboat: I think that they do, at least, have good intentions; but in any case, it's probably a good idea to warn them that if they keep being disruptive they could be topic-banned (if you haven't already). Jc86035 (talk) Use {{ping|Jc86035}}
to reply to me
04:07, 30 October 2016 (UTC)

Autopatrol given[edit]

Commons Autopatrolled.svg

Hello. I just wanted to let you know that I have granted autopatrol rights to your account; the reason for this is that I believe you are sufficiently trustworthy and experienced to have your contributions automatically sighted. This will have no effect on your editing, and is simply intended to help users watching Recent changes or Recent uploads to find unproductive edits amidst the productive ones. Thank you.

Welcome, Dear Filemover![edit]

Commons File mover.svg

Hi Jc86035, you're now a filemover. When moving files please respect the following advice:

  • Use the CommonsDelinker link in the {{rename}} template to order a bot to replace all ocurrences of the old title with the new one. Or, if there was no rename-request, please use the Move & Replace-tab.
  • Please do not tag redirects as {{speedy}}. Other projects, including those using InstantCommons, might be using the file even though they don't show up in the global usage. Deleting the redirects would break their file references.
  • Please know and follow the file rename guidelines.

Deutsch | English | 한국어 | മലയാളം | Русский | Українська | +/−

--Hedwig in Washington (mail?) 00:30, 6 December 2016 (UTC)

@Hedwig in Washington: Thank you! 🙂 Jc86035 (talk) Use {{ping|Jc86035}}
to reply to me
00:53, 6 December 2016 (UTC)

About File:MTR map.svg[edit]

Sorry for inactivity because I have recently been studying C Sharp which obviously takes lot of time and efforts. About your MTR map.svg, nice work and I'm proud that you make good use of my "tutorial" (which lacks a ton of explanations). But there is always "but". Let's begin with the technical one about libRSVG. As user:Perhelion pointed out to me, libRSVG has trouble to render text accurately if the font-size is small to begin with possibly because of decimal truncation, so it's actually better if you multiply all size and position values within the SVG tag by a constant like 10 and then scale down the whole image by width and height attributes in SVG element, see File:Sameboat temp cc0.svg.

The design itself isn't bad, but I feel the typography doesn't flow smoothly. When I was making my tube map, I did move the route paths to make room for the text to allow minimal overlapping and line break and keep the adjacent station labels on the same side of the route. For example, Olympic label should be moved to the left side of TCL and AE for Yau Ma Tei label to stay in line with Prince Edward and Mong Kok, but in order to avoid the station tick of Olympic to overlap AE, you may want to move the route of AE away from TCL by 1 route-path width just like how you did to TCL-WRL. I think this is justifiable considering that you have already left gaps for TCL-WRL and TCL-TWL (at Lai King) which run closely parallel in reality. The separation also avoids confusion at Nam Cheong, Lai King and Sunny Bay because the route of AE would not touch the edges of the interchange roundels. And yes you do need to move MOSL further rightwards to avoid Racecourse label to overlap the route even though MOSL and ERL aren't that far apart in reality which isn't wrong in topological map. Certain curves can be straightened: Mong Kok East of ERL, Kowloon Tong to Choi Hung of KTL. Keep up good work and Merry Christmas. -- Sameboat - 同舟 (talk · contri.) 23:09, 21 December 2016 (UTC)

@Sameboat: Thanks for your feedback! I probably won't be working on this for a while though, maybe I'll finish it up in February. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
06:29, 22 December 2016 (UTC)


Moved to Talk:BSicon/Renaming. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
15:02, 31 December 2016 (UTC)

BRIDGEc icons[edit]

Those icons were deliberately drawn with the formations spread as wide as possible to give some latitude when used with curves (not only with straight through/across lines). (e.g. BSicon .svgBSicon uv-STR.svgBSicon BRIDGEc2q.svgBSicon vSTRlf-.svg , BSicon .svgBSicon u-STRq.svgBSicon BRIDGEc3.svgBSicon vSTR+1-.svg ) Please revert. Thanks! Useddenim (talk) 13:47, 22 January 2017 (UTC)

@Useddenim: Shouldn't curves use their own curved bridges? I've tested it with the wider bridge and the formations still overlap with the curves, so I don't think it's going to work. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me
13:55, 22 January 2017 (UTC)