© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I've found that bug reports are least confusing when they concentrate on describing problems to be solved, rather than pieces of work to be done.
For example, "Cant print all of pan-Nigerian in Ubuntu font" is a problem to be solved. "Cover more Latin-based African languages" is not. If you focus too much on the work rather than the problem, you can easily end up doing work that isn't necessary (for example here, having the introduction of contemporary characters bogged down by historical characters), discouraging contributors, or not being sure when to mark the bug as fixed.
It may be a good idea to have consistency requirements like the one Denis mentions, requiring all variants of an individual character (e.g. upper-case and lower-case) at the same time, or requiring all weights of a character at the same time. But that is something to be documented elsewhere, not something to be tracked by bugs reported by people who don't necessarily know those requirements.
So, I think this bug report would be most effective if it was split up into one per language. I've started by reporting bug 1396511 on Lingala.