ログインしていません。ログインしていない状態でのチケット投稿では、報告者へのチケット状態変更のメールでの通知が行われません。変更を逐次追いたい場合は、ログインするか、作成されたチケットのRSSを取得してください。 » ログインする
Use this ticket type for submitting problems with existing functionality in the Tsukurimashou Project: things that are implemented but do not work as they are intended to work.
Problems in third-party systems that we need to be aware of (to work around, complain about, or if necessary, fix) but that do not represent errors in Tsukurimashou should be reported as "hairy yaks" instead.
Things that are not implemented in Tsukurimashou, but you think should be implemented, should be reported as "feature requests" instead.
Do not submit a ticket at all for things that are implemented and that work as designed, but represent design decisions with which you disagree; contact the maintainer(s) by email to discuss such issues instead.
Use this ticket type if there is something in the system that seems to be working as designed, but that you don't understand. Also submit one of these tickets for compatibility issues between Tsukurimashou and other things.
Use this ticket to propose new features for future implementation.
If you are reporting a problem with a feature that already exists but doesn't work, please submit a "bug" instead.
Tickets of this type represent features or tasks that are part of the definite plan for future development, such as blocks of kanji glyphs. Usually, they are also associated with specific release milestones. Only maintainers should create tickets of this type; others with suggestions for future development should submit them as "feature request" tickets instead.
The current plan, at least through release 2.0, is to have one "development task" ticket for each block of 20 kanji. Every time I complete one, I'll submit two more, until tickets exist for all planned kanji.
These tickets are given "accepted" status when finished.
Use this ticket type for reporting problems in third-party systems that affect the Tsukurimashou Project.
If Tsukurimashou's code is actually incorrect (does not do what it is intended to do) then report that as a "bug" instead; this category is for issues which are not ours, but affect us in such a way that it makes sense to track them.
Normally it makes sense to file a hairy yak ticket here if and only if you are also filing a ticket of some sort in some other project's tracker - and please include a link to the other project's ticket in the report here.