|(P.S. Would you like to provide feedback on this message?)|
- 1 Kanji stroke order
- 2 Stroke order (2008)
- 3 Chinese kanji stroke order
- 4 Korean orthographies
- 5 stroke order
- 6 Your candidacy for adminship
- 7 Thanks~
- 8 Proposal to change allowable scope of userpage content
- 9 Stroke order Project
- 10 Ni hao!
- 11 Your Opinion/Critique
- 12 Restored
- 13 Stroke Order Project
- 14 Stroke Order Project Needs
- 15 kanjiVG
- 16 File:Eccentricity.svg
- 17 Notification about possible deletion
Kanji stroke order
Hello and thanks for your support ("I recently came across the excellent Stroke Order Project" ^_^y ). We work on this in owr free time, and we are aware of some difference between official order in Japan, China and Taiwan. as you can see in Chinese stroke order:214 keys, we try to see all the existant official order variants, specific to one or an other country.
In exemple, 王 and 田 ( -jbw.png):
- Japanese official stroke order is :
- when Chinese official order is (-bw.png):
About 九-9, Image:九-order.gif is, for sure, the right stroke order in China.
According to the japanese site : http://www.sky.sannet.ne.jp/kyoshio/DW/Hitsujun/Hitsujun.htm (with the exemple of 九), that's also the japanese stroke order.
Your japanese friend probably made a mistake: to write faster, native Kanji/hanji write frequently change the stroke order, and then mix up every thing. (Ask him/her confirmation slowly: japanese people are really proud... :]) But that can be a mistake of the previous japanese site, and we will be aware about 九.
We already see several official differences such as these, and we work to make all official order, so if know one official japanese variant (for order), your suggestion is welcome, and we will be aware for this characters. And then we just should be a [[九-jorder.gif]].
- PS: I'm the unofficial boss for organisation, but M4RC0 and WikiC made really more pics than me.
- Thanks for the reply, Yug. Regarding the "boss" issue; I saw it mentioned somewhere that User:Wikic was the one in charge. A quick look around reveals Chinese_stroke_order:Protocols/Order.gif and Category:Chinese_stroke_order_in_animated_GIF.
- Soon after leaving my message, I did happen to stumble across a page that discussed some of the differences. Unfortunately, this was a while ago and I didn't note the address down :-(. I searched for where it might be, but without luck. I might well come back to this later, and if I do find anything of interest, I'll let you know.
- All the best for your project! --Swift 09:38, 30 June 2006 (UTC)
Stroke order (2008)
Chinese kanji stroke order
I bow to you expertise. If I recall correctly I was faced with merging in an orphan category with multiple uncatted images-with an existing well catted group, so the decisions I made were on the principle of doing the least unreversible damage. Apologies if it has caused problems.ClemRutter (talk) 08:28, 9 October 2008 (UTC)
- Done. I added them to Category:Korean writing. One of them, by the way, was already categorised. --Swift (talk) 03:55, 10 October 2008 (UTC)
- Fantastic! Thank you so much, Yug. I incorporated them into b:Template:Japanese kanji readings yesterday, but frustratingly couldn't get it to work. As you point out, the "ifexist" statment needs to point to "Media:", not "Image:". Thanks a lot! --Swift (talk) 02:59, 11 October 2008 (UTC)
Your candidacy for adminship
I see you have withdrawn Commons:Administrators/Requests and votes/Swift. I am sorry it did not succeed. A sign of something I like to see in a potential admin is to withdraw things rather than belabor the point, so kudos for that decision. I hope you take the feedback on board in the spirit it was offered. The big thing for me and others is to demonstrate a sustained interest in the project... spend some time working and participating in areas outside your specific interest, as well as in your area of interest, and then try again, if you still want to. Best wishes, and should you need anything, or have any questions please don't hesitate to ask. ++Lar: t/c 03:12, 4 November 2008 (UTC)
- Thanks. It was a little frustrating to get no support seeing that I filled the requirements and figured my work would be eased by not having to chase down admins. That alone, of course, doesn't guarantee being granted these rights and it's reasonable that community members reject requests that they don't consider necessary. I fully understand and accept the concerns raised and recognise that their aim was the benefit of the project as a whole.
- Thanks a lot as well for your offer of help. I might well take you up on it at some stage. Cheers, --Swift (talk) 04:59, 4 November 2008 (UTC)
- Oh... I was not aware about your candidacy, which Micheletb and myself would have support for sure. I think its need to grant you this admin tools, since the SOP is a really large and complex project, we can't be all the time requesting other admins help.
- You may be interested to look at my old candidacy, and the Micheletb one. In any case, a candidacy need some further preparations, such as ask advices of 'close' wiki-friend to copyedit your draft-candidacy, to rewrite your user page, and to be ready to support you in the first days of the vote, explaining with other words why you are need (cf my vote on the Micheletb candidacy).
- Admin tools as, are you may know, tiny and time consuming tools, but sadly, some believe that they are REALLY IMPORTANT, and that clearly helpful but medianly active users don't need them. I personally thing that users such you [not hyper active, but the current 'expert' on one field] need such basic admin tools.
- (PS: may I still vote ? that may help a 2nd candidacy.)
- Yug (talk) 11:20, 15 December 2008 (UTC)
- Thanks a lot, Yug, but I don't see myself requesting admin tools again for a while. When I arrived first it seemed a good idea to request them given the lack of responses to requests and remoteness of the COM:SOP. I reckoned that I fulfilled the requirements and the guidelines made it seem that would be sufficient. Those weighing in on the discussion thought otherwise, so I withdrew. While having the tools myself would be useful, I've found a few very helpful admins that I believe would be gracious enough to help out with admin related things. Besides, there are plenty of things to be done that doesn't need admin tools! Cheers, --Swift (talk) 03:52, 31 December 2008 (UTC)
Proposal to change allowable scope of userpage content
I have made a proposal to specify more clearly what is and what is not allowed on usepages. You have expressed interest in this issue, and you may wish to comment at Commons_talk:Project_scope/Pages,_galleries_and_categories#The use of userpages to advance personal political opinions. --MichaelMaggs (talk) 21:45, 17 January 2009 (UTC)
Stroke order Project
Hi, so I'd really like to get into this project and help out, however, I noticed that the categories and everything is pretty messed up. Just wondering what to do here, basically. Also, the tutorials are really lacking in my opinion and should be redone. On the same note, I edited the Asian_alphabets page yesterday and also categorized the single Hangeul character done already (ㄱ, with updating the license, as I saw it fit the old one, too). In my opinion the categories should be created with the template, that is, the style, the character and the type should all be done via the license template. Also, I propose not to have categories that are like Category:Japanese_kana_stroke_order_in_BW_pictures, but sepearate Category:bg-style pictures (or similar) and "Japanese kana stroke order". That way, they are searchable both ways and you can "mix and match" the searched categoies as much as you'd like. Search for "Japanese kana stroke order" and you'll get all the images, regardless of red, bw, order, anim etc. Then you'll also get the seperate categories listed on top of that so you can really look in all directions. IMHO this is lacking at the moment. Se yeah, I'd like to help out, but basically, this needs some organization page or something so contributors actually know what's on the slate to be done. --Tauwasser (talk) 16:46, 21 January 2009 (UTC)
- Hi Tauwasser,
- Great to have company! I agree that we need to make it easier to find characters. The phonetic character categories need some tweaking, but that should be simple enough. I tink the Han characters would benefit from being searchable by character (and code-point?), stroke order and radical.
- Browsing categories of thousands of files are of limited value, but I think these are fine to keep. Both for when small sub-projects are getting started, but mainly for the metadata that they provide (e.g. through automatically generated numbers of files in cagegory) and any future MediaWiki features that might allow for listing the intersections of categories.
- We can discuss these and other issues on the project talk pages. Where? I'm not sure. I hadn't really bothered thinking too much about this since it's been so quiet on the project. I guess Commons talk:Stroke Order Project for project structure, and Commons talk:Stroke Order Project/Roadmap for stroke order verifications and image contributions. --Swift (talk) 08:00, 22 January 2009 (UTC)
How do you do, Mr. Swift?
22.214.171.124 05:12, 28 January 2009 (UTC)
- Ni hao 126.96.36.199!
- I'm doing all right. How about yourself?
- Take care! --Swift (talk) 05:14, 28 January 2009 (UTC)
- Good news Swift ! I had free time today and I create the 2 last section of User:Yug/Stroke order, which is COMPLETE, containing ALL, on stroke order and rules to writes Chinese characters. I still have some very minor check, clean ups and maybe some rewording to do, but the page will be 'finish & stable' within some few days. :] I postponed this for so long~ I'm really happy to annouce that this will be finish ! Yug (talk) 17:48, 30 January 2009 (UTC)
Hi, I made an image for a Korean character, but it's probably not up to the Stroke Order Project standards yet, so I was hoping you could let me know how to better improve it so that I might submit some characters in the future. http://www.koreanwikiproject.com/wiki/index.php?title=Image:Giuk_stroke.gif
Please reply on my page. I will ask Yug to do the same.
Stroke Order Project
please see Commons_talk:Stroke_Order_Project#Taiwan.27s_stroke_order_is_not_Imperial_China.27s. I cannot really tell if it is correct to rename "traditional Chinese" to "Taiwanese" just because we don't show stroke order with a calligraphic font... I don't really know these peculiar distinctions well enough :D Other than that, how are we going to implement the categorization of current glyphs once we change to SOP license? Do you have any script to do that already??
Stroke Order Project Needs
please see at Commons talk:Stroke Order Project#3 Categories my opinion; can you do something to help my problem with the Template:SOlicense which is kept locked all time by User:Gmaxwell who seems idle since some weeks? --Sarang (talk) 12:13, 22 August 2009 (UTC)
Do you know about the KanjiVG project?
They are coding stroke orders in an easy-to-handle file format (text-based, XML).
Would it be possible to have a similar format for this project? Do you see any collaboration possible with this projects?
|File:Eccentricity.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has 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 it, such as a copyright issue.
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.