Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot specify quartered or otherwise marshalled shields #6

Open
GoogleCodeExporter opened this issue Feb 15, 2016 · 3 comments
Open

Comments

@GoogleCodeExporter
Copy link

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 you see instead?
The parser chokes on "I".

This should render in the obvious way. 

Original issue reported on code.google.com by [email protected] on 24 Mar 2008 at 10:27

@GoogleCodeExporter
Copy link
Author

No, you say "Quarterly argent and gules." The first tincture defines the first 
and forth quarter, and the second one defines the second and third quarters. 
Doing something exotic like one tincture for each quarter isn't allowed in 
heraldry anyway.

Original comment by robb1701 on 27 Sep 2010 at 8:44

  • Changed state: Invalid

@GoogleCodeExporter
Copy link
Author

It appears that this kind of blazon is valid. For instance, see 
http://en.wikipedia.org/wiki/Coat_of_arms_of_the_United_Kingdom

Original comment by [email protected] on 27 Sep 2010 at 9:12

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Well in that case you are requesting support for a new blazon element. That 
will likely be possible with the upcoming parser rewrite. I however would 
suggest a more fluid syntax that simply counts the number of fields stated and 
then adjusts itself accordingly.

Original comment by robb1701 on 28 Sep 2010 at 12:25

  • Added labels: Milestone-Release1.0, Type-Enhancement
  • Removed labels: Type-Defect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant