pyblazon
pyblazon copied to clipboard
clsn
Automatically exported from code.google.com/p/pyblazon
``` We need to be able to know where we are drawing stuff, instead of relying on fire-and-forget. This would be tremendously helpful in order to be able to both...
``` Currently, the SVG produced by pyBlazon is rather messy and difficult to work with in post-processing. The SVG should be at least so simple that it displays correctly in...
``` What steps will reproduce the problem? 1. Quarterly Or and sable, four annulets countercharged. What is the expected output? What do you see instead? For once, the charges are...
``` What steps will reproduce the problem? 1. Or two lozenges vert. What is the expected output? What do you see instead? The lozenges should fill much more of the...
``` pyblazon currently faults when parsing "pily fesswise sable and argent". The grammar currently lacks the notion of an inversion/direction modification ("optinverted") following "pily" (a "LINEY"). For other "LINEY"s, it's...
``` What steps will reproduce the problem? 1. "Quarterly azure and argent a fret couped counterchanged." 2. 3. What is the expected output? What do you see instead? The expected...
``` Errors don't usually give a whole lot of background, and when the parser recovers from an error, it often yields strange results. Should probably fail more gracefully. ``` Original...
``` The makefile should create a tarball of everything that should be distributed, and nothing more. ``` Original issue reported on code.google.com by `[email protected]` on 24 Mar 2008 at 11:28
``` 1. Finish/write sections set off with [] 2. Update dependencies to reflect current situation 3. Remove stuff about regression tests to a special text file that is not in...
``` PyBlazon should have an option to render the blazon on a flag instead of a shield. ``` Original issue reported on code.google.com by `[email protected]` on 24 Mar 2008 at...