Google Code Exporter
Google Code Exporter
``` PyBlazon should be able to have, and ship with, grammar files for other languages than English. ``` Original issue reported on code.google.com by `[email protected]` on 24 Mar 2008 at...
``` Stuff like "Or on a bend sable between a mullet and a roundel gules, crescent argent" is going to be near impossible from a grammar standpoint, without putting some...
``` The kludge that makes "per bend or and sable a crescent and a goute counterchanged" work, in joining the crescent and the goute into a single chargegroup, is, well,...
``` What steps will reproduce the problem? 1. "Argent six roundels azure each charged with an escutcheon or" What is the expected output? What do you see instead? The escutcheons...
``` Compony/gobony should be supported. This is, I believe, a fairly exhaustive list of charges that can reasonably have compony: Bend Bend sinister Fesse Bar Chevron ``` Original issue reported...
``` What steps will reproduce the problem? 1. "Or a fesse embattled sable." What is the expected output? What do you see instead? This has embattlings both above and below,...
``` PyBlazon should have the option, possibly with a command-line switch, to draw heraldry in a style that has very thin outlines (akin to fimbriations) on everything. ``` Original issue...
``` What steps will reproduce the problem? 1. "Quarterly: I and IV gules a mullet argent; II and III argent a lozenge azure." What is the expected output? What do...
``` Resolving this may have to wait for the SVG standard to be amended.(!) ``` Original issue reported on code.google.com by `[email protected]` on 24 Mar 2008 at 10:16
``` Charges or groups "between" charges or groups should do the right thing. ``` Original issue reported on code.google.com by `[email protected]` on 24 Mar 2008 at 10:12