User:FanNihongo
I am studying Chinese on Duolingo, and creating new images for the Stroke Order project is part of my studies, because these images along with Anki, help me learn the stroke order of the characters. Because I prefer the animated images(-order.gif) over the black and white images(-bw.png), I specialize on making animated gif files for the mentioned project.
I am also the leader of the Stroke Order Project's animated images, I have developed my own method for the creation of these images, which I recommend and can be consulted on this this page.
Stroke Order Project Letters[edit]
en:wikt:User:FanNihongo/Unicode CJK Radicals Supplement
| Babel user information | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Users by language | |||||||||
The future of the Stroke Order Project[edit]
Due to my decision of still working on the Stroke Order Project(Only with the reward or having images to study, if in the future maybe I retake my Japanese studies), and due that the work seems interminable.
I decided to developed a new method in order to ease the work, with the purpose of creating new animated images. I will explain: first I had came with the idea of making components, which could be joined like pieces of puzzle. That idea worked well but was not enough.
Now I came with this idea: what if we do strokes(of what is made every Chinese letter), and join them like pieces of puzzle.
Because of that I will be working slowly. This method has a lot of advantages:
- This lets you edit the stroke order, and then create the pairs: -order and -jorder.
- Every stroke that is created can be reused multiple times, as it is need it.
But also has disadvantages:
- It is great but due to the characteristics of this method I cannot share it, with anybody. I currently (22/Jun/2021) being the only active contributor of the animated images and the lack of interest of the people, also discourages sharing it.
I have a theory, of which I am confident it will be fulfilled: I will work slowly, but the more I work, the more amount of strokes will be stored on my stroke library, ergo allowing me create these files faster.
Roughly these are the steps of my method:
- Stroke creation and its animation: This is the most complex and painstaking step.
- Stroke storing: Every stroke must have a unique name, and graphically in a way that lets you locate it with ease.
- Stroke joining: This is the easiest part.
- Stroke anti aliasing: Because the strokes have a fully transparent background, the final images end up pixelated, and a non automatized anti alias process must be done, which although is very tedious, it does achieve great results.
Example:
This image was done following that method and it is the first of many, that will come in the future.
[edit]
Well, I want consistency, and to achieve this, a lot of organization and communications is needed among the work group. The team members have to understand the work to do.
Sharing the method, would mean that having a common stroke order library is required. Hypothetically this is a great idea, because not only the contributors can make use of that vast library, but they can help to add more material into it. Even complete it, ergo completing the animated Stroke Order images in no time.
But for these reasons that library cannot be done.
- Wikimedia commons could serve as common stroke library, but I am not agree, because I feel like it would be abusing. Let me explain: let's imagine a case where the library is created, and then completed, ergo the animated series of the SOP are completed too. Ending up with the purpose of the library fulfilled, leaving Wikimedia commons with a now useless common stroke library. Maybe if we find another server to store the images.
- The stroke files must be stored in GIMP format, because the GIF format is not suited for that, it makes the images pixelated.