diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..0c6e33c
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,3 @@
+_site
+.sass-cache
+website.iml
diff --git a/404.md b/404.md
new file mode 100644
index 0000000..9c2150b
--- /dev/null
+++ b/404.md
@@ -0,0 +1,4 @@
+---
+layout: page
+title: 404 - Page Not Found
+---
diff --git a/README.md b/README.md
index 21e2d27..0fd3c57 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,30 @@
-We migrated to [GitLab](https://gitlab.com/mathml/)!
-A updated version of this repository can be found [here](https://gitlab.com/mathml/website).
-
# MathML Website
-This is the website for the Mondial Association for Tools Handling MathML, ltd (for short, MathML Association).
+This is the website for
+the Mondial Association for Tools Handling MathML, ltd
+(for short, MathML Association).
+
+## Setup
+
+1. Get the source code with
+
+ ~~~
+ $ git clone git@github.com:MathML/website.git
+ ~~~
+
+2. Follow the instructions in `logo/README.md` in order to build the logos.
+
+3. Install [Jekyll](http://jekyllrb.com/).
+
+4. Build the website with
+
+
+ ~~~
+ $ jekyll server
+ ~~~
+
+5. Check the website at http://localhost:4000/ in your web browser.
+
+## Adding new posts
+
+Please check http://jekyllrb.com/docs/posts/.
diff --git a/_config.yml b/_config.yml
new file mode 100644
index 0000000..3417ea1
--- /dev/null
+++ b/_config.yml
@@ -0,0 +1,53 @@
+# Site settings
+title: MathML Association
+email: info@mathml-association.org
+emaildomain: mathml-association.org
+description: A group action for MathML
+baseurl: "" # the subpath of your site, e.g. /blog/
+url: "http://mathml-association.org" # the base hostname & protocol for your site
+twitter_username: mathml3
+github_username: mathml
+reedit_username: mathml
+
+# Build settings
+markdown: kramdown
+
+# Header
+header:
+ - title: Manifesto
+ url: /legal-documents/manifesto.html
+ - title: News
+ url: /news.html
+ sub:
+ - title: Reports
+ url: /reports/index.html
+ - title: Meetings
+ url: /meetings/meetings.html
+ - title: Twitter
+ url: https://twitter.com/mathml3
+ - title: Activities
+ url: https://github.com/MathML/website/wiki
+ - title: About
+ url: /about.html
+ sub:
+ - title: People
+ url: /people/index.html
+ - title: Logos
+ url: /logo/index.html
+ - title: Documents
+ url: /legal-documents/index.html
+ - title: FAQ
+ url: /faq.html
+ - title: Affiliates
+ url: /affiliates/index.html
+ sub:
+ - title: Sponsors
+ url: /affiliates/sponsors.html
+ - title: Partners
+ url: /affiliates/partners.html
+ - title: Friends
+ url: /affiliates/friends.html
+ - title: Donate
+ url: /affiliates/donate.html
+ - title: Contact
+ url: /contact.html
diff --git a/_includes/email-icon.html b/_includes/email-icon.html
new file mode 100644
index 0000000..6878404
--- /dev/null
+++ b/_includes/email-icon.html
@@ -0,0 +1,5 @@
+
+
+
+
+
diff --git a/_includes/footer.html b/_includes/footer.html
new file mode 100644
index 0000000..25b7c5b
--- /dev/null
+++ b/_includes/footer.html
@@ -0,0 +1,66 @@
+
diff --git a/_includes/github-icon.html b/_includes/github-icon.html
new file mode 100644
index 0000000..32bd9f6
--- /dev/null
+++ b/_includes/github-icon.html
@@ -0,0 +1,5 @@
+
+
+
+
+
diff --git a/_includes/head.html b/_includes/head.html
new file mode 100644
index 0000000..4d1c2b8
--- /dev/null
+++ b/_includes/head.html
@@ -0,0 +1,12 @@
+
+
+
+
+
+ {% if page.title %}{{ page.title }}{% else %}{{ site.title }}{% endif %}
+
+
+
+
+
+
diff --git a/_includes/header.html b/_includes/header.html
new file mode 100644
index 0000000..1880c2b
--- /dev/null
+++ b/_includes/header.html
@@ -0,0 +1,39 @@
+
diff --git a/_includes/reedit-icon.html b/_includes/reedit-icon.html
new file mode 100644
index 0000000..6878404
--- /dev/null
+++ b/_includes/reedit-icon.html
@@ -0,0 +1,5 @@
+
+
+
+
+
diff --git a/_includes/rss-icon.html b/_includes/rss-icon.html
new file mode 100644
index 0000000..ad2e52a
--- /dev/null
+++ b/_includes/rss-icon.html
@@ -0,0 +1,5 @@
+
+
+
+
+
diff --git a/_includes/twitter-icon.html b/_includes/twitter-icon.html
new file mode 100644
index 0000000..5bfabb4
--- /dev/null
+++ b/_includes/twitter-icon.html
@@ -0,0 +1,5 @@
+
+
+
+
+
diff --git a/_includes/website-icon.html b/_includes/website-icon.html
new file mode 100644
index 0000000..b17f836
--- /dev/null
+++ b/_includes/website-icon.html
@@ -0,0 +1,5 @@
+
+
+
+
+
diff --git a/_layouts/default.html b/_layouts/default.html
new file mode 100644
index 0000000..e4ab96f
--- /dev/null
+++ b/_layouts/default.html
@@ -0,0 +1,20 @@
+
+
+
+ {% include head.html %}
+
+
+
+ {% include header.html %}
+
+
+
+ {% include footer.html %}
+
+
+
+
diff --git a/_layouts/page.html b/_layouts/page.html
new file mode 100644
index 0000000..74c1a11
--- /dev/null
+++ b/_layouts/page.html
@@ -0,0 +1,14 @@
+---
+layout: default
+---
+
+
+
+
+
+ {{ content }}
+
+
+
diff --git a/_layouts/post.html b/_layouts/post.html
new file mode 100644
index 0000000..a2b4e52
--- /dev/null
+++ b/_layouts/post.html
@@ -0,0 +1,15 @@
+---
+layout: default
+---
+
+
+
+
+
+ {{ content }}
+
+
+
diff --git a/_posts/2015-03-01-declaration.md b/_posts/2015-03-01-declaration.md
new file mode 100644
index 0000000..99e62db
--- /dev/null
+++ b/_posts/2015-03-01-declaration.md
@@ -0,0 +1,11 @@
+---
+layout: post
+title: "Declaration of the MathML Association"
+category: announcement
+tags: [announcements]
+---
+
+On February 24, we submitted our application as a charitable organization under
+the Not-for-Profit Corporation Law of the State of New York and we are pleased
+to announce that the Mondial Association for Tools Handling MathML, ltd
+(for short, MathML Association) is now [officially registered](http://appext20.dos.ny.gov/corp_public/CORPSEARCH.ENTITY_INFORMATION?p_nameid=4765945&p_corpid=4714991&p_entity_name=Mondial&p_name_type=A&p_search_type=BEGINS&p_srch_results_page=0)! This is the first step towards a legal structure to promote MathML and fund MathML developments... Stay tuned for further progress!
diff --git a/_posts/2015-06-05-minutes.md b/_posts/2015-06-05-minutes.md
new file mode 100644
index 0000000..652f1dd
--- /dev/null
+++ b/_posts/2015-06-05-minutes.md
@@ -0,0 +1,11 @@
+---
+layout: post
+title: "Board Meeting, May 2015"
+category: minutes
+tags: [minutes]
+---
+
+Two weeks ago, we held our first board meeting, where we elected our
+[directors](/directors.html) and voted for our [by laws](/legal-documents/non-profit-corporate-by-laws.html) and [conflict of interest policy](/legal-documents/conflict-of-interest-policy.html). For more details, you can read
+the [minutes](/meetings/board-2015-05-20.html). The next meeting will take place
+in August!
diff --git a/_posts/2015-08-19-minutes.md b/_posts/2015-08-19-minutes.md
new file mode 100644
index 0000000..23fb5c6
--- /dev/null
+++ b/_posts/2015-08-19-minutes.md
@@ -0,0 +1,13 @@
+---
+layout: post
+title: "Board Meeting, August 2015"
+category: minutes
+tags: [minutes]
+---
+
+Two weeks ago, we held our second board meeting, where we voted for
+our [manifesto](/legal-documents/manifesto.html), for our [logo](/logo/)
+for the [document about affiliates](/legal-documents/affiliates.html) and
+for minor amendments of [our by laws](/legal-documents/non-profit-corporate-by-laws.html). For more details, you can read
+the [minutes](/meetings/board-2015-08-05.html). The next meeting will take place
+at the end of September!
diff --git a/_posts/2015-09-18-minutes.md b/_posts/2015-09-18-minutes.md
new file mode 100644
index 0000000..df966b8
--- /dev/null
+++ b/_posts/2015-09-18-minutes.md
@@ -0,0 +1,17 @@
+---
+layout: post
+title: "Board Meeting, September 2015"
+category: minutes
+tags: [minutes]
+---
+
+Last week we held our third board meeting, where among other things we elected
+our [board officers](/people/officers.html):
+
+ * Michael Kohlhase (President)
+ * Frédéric Wang (Vice-president)
+ * Deyan Ginev (Secretary)
+ * Raniere Silva (Treasurer)
+
+For more details on other votes and dicussions, you are invited to read the
+[minutes](/meetings/board-2015-09-18.html).
diff --git a/_posts/2015-09-18-w3c.md b/_posts/2015-09-18-w3c.md
new file mode 100644
index 0000000..c85ed87
--- /dev/null
+++ b/_posts/2015-09-18-w3c.md
@@ -0,0 +1,8 @@
+---
+layout: post
+title: "MathML Association featured on the W3C site"
+category:
+tags: [w3c]
+---
+
+Today, the [Math WG mentions the MathML Association on its Web page](https://lists.w3.org/Archives/Public/www-math/2015Sep/0026.html). Thank you very much for making more people aware of the association and of its [mission](/legal-documents/manifesto.html)!
diff --git a/_posts/2015-10-10-mathml-in-html5.md b/_posts/2015-10-10-mathml-in-html5.md
new file mode 100644
index 0000000..85b19b8
--- /dev/null
+++ b/_posts/2015-10-10-mathml-in-html5.md
@@ -0,0 +1,43 @@
+---
+layout: post
+title: "\"MathML in HTML5\" implementation note and test suite"
+category: announcement
+tags: [announcements]
+---
+
+Today, we published a first draft of the ["MathML in HTML5" implementation note](http://www.mathml-association.org/MathMLinHTML5/). This note takes into
+account feedback from browser vendors or web users about the fact that the rules
+described in the [MathML specification](http://www.w3.org/TR/MathML3/) are not
+precise enough for consistent, high quality and easily implementable
+mathematical rendering. Hence this note provides detailed rules based on
+[TeXBook’s Appendix G](/MathMLinHTML5/bib.html#bibx16) and from the
+[Open Font Format version 3](http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=66391).
+
+As suggested by the name, the priority is to be compatible with existing
+technologies of web rendering engines by relying as much as possible on CSS,
+text & table layout and box models. We also used the experience gained
+by several years of development in the [Mozilla's MathML Project](https://wiki.mozilla.org/MathML:Home_Page) and took into account problems found in the
+more recent [WebKit's implementation](https://trac.webkit.org/wiki/MathML).
+We hope that the present document will be
+understandable by any implementer with sufficient knowledge of web rendering
+engines and text layout. Parts of presentation MathML that do not fit well into
+this framework or are rarely used in practice have been ommited. Future versions
+may extend the subset of MathML considered but we expect that the present
+document will already be enough to render with high quality the majority of
+mathematical formulas used in practice.
+
+As indicated in our [Manifesto](/legal-documents/manifesto.html), we believe
+that open standards are important and we strongly relied on the MathML
+and Open Font Format specifications to propose these math rendering rules.
+We want all the actors to get involved and we already received very positive
+feedback from the Math WG and from WebKit developers. We are interested
+in hearing more opinion and we will refine and improve this document based
+on feedback from implementers, users and specification editors. In the future,
+we may consider proposing it as an official W3C note from the Math WG.
+
+Last but not least, we also started to write a
+[test suite for "MathML in HTML5" implementation note](http://tests.mathml-association.org/). We relied on [existing approaches](http://testthewebforward.org/)
+used to ensure conformance with W3C specifications and to provide tests for
+continuous integration by browser vendors. By following practices developers
+are used to, we hope that this test suite will be instrumental to implement
+and improve native MathML in all browsers.
diff --git a/_posts/2015-10-28-minutes.md b/_posts/2015-10-28-minutes.md
new file mode 100644
index 0000000..c07981a
--- /dev/null
+++ b/_posts/2015-10-28-minutes.md
@@ -0,0 +1,15 @@
+---
+layout: post
+title: "Board Meeting, October 2015"
+category: minutes
+tags: [minutes]
+---
+
+Last week we held our fourth board meeting, results:
+
+* vote on friends process
+* elected Moritz Schubotz as "friends officer".
+* adopted two slogans: "A group action for MathML" for the website and "Web Math Matters" for twitter.
+
+For more details on other votes and dicussions, you are invited to read the
+[minutes](/meetings/board-2015-10-28.html).
diff --git a/_posts/2015-11-05-friends.md b/_posts/2015-11-05-friends.md
new file mode 100644
index 0000000..b116ab3
--- /dev/null
+++ b/_posts/2015-11-05-friends.md
@@ -0,0 +1,16 @@
+---
+layout: post
+title: "Become a MathML Friend"
+category: announcement
+tags: [announcements]
+---
+
+On November 5. 2015, the MathML Association opened the [MathML Friends
+list](http://mathml-association.org/affiliates/friends.html) page and [mailing
+list](http://lists.mathml-association.org/mailman/listinfo/friends). You can express your
+support for the [MathML
+Manifesto](http://mathml-association.org/legal-documents/manifesto.html) by [signing
+up](http://mathml-association.org/affiliates/friends.html).
+
+Go ahead, sign up, and tell your friends!
+
diff --git a/_posts/2015-11-07-math-fonts.md b/_posts/2015-11-07-math-fonts.md
new file mode 100644
index 0000000..04b4f53
--- /dev/null
+++ b/_posts/2015-11-07-math-fonts.md
@@ -0,0 +1,39 @@
+---
+layout: post
+title: "Supporting mathematical fonts"
+category:
+tags: [fonts]
+---
+
+As stated in [our manifesto](/legal-documents/manifesto.html),
+mathematical fonts are extremely important to provide good mathematical
+rendering.
+In a [previous announcement](/announcement/2015/10/10/mathml-in-html5.html), we
+mentioned the publication of a ["MathML in HTML5" implementation note](/MathMLinHTML5/), relying on [Open Font Format 3](http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=66391) and more specifically the [OpenType MATH table](http://www.microsoft.com/typography/otspec/math.htm) introduced by Microsoft. Initially used
+for [Microsoft Word](https://products.office.com/word), this table was later implemented in modern TeX typesetting engines such as [XeTeX](http://xetex.sourceforge.net/), [LuaTeX](http://luatex.org/) or [ConTeXt](http://www.pragma-ade.nl/). During a [crowdfunding project from 2014](http://www.ulule.com/mathematics-ebooks/), one of our [directors](/people/directors.html) submitted patches to Mozilla, Apple and Google in order to implement parsing for the OpenType MATH table in [Gecko](https://en.wikipedia.org/wiki/Gecko_%28software%29), [WebKit](https://en.wikipedia.org/wiki/WebKit) and [OTS](https://github.com/khaledhosny/ots) respectively. This opened the way to better mathematical rendering in browsers. Gecko and WebKit already use this table for their MathML support.
+
+MathML formula rendered by Firefox.
Left:
Noto Serif (no MATH table) ; Right: Latin Modern Math (MATH table)
+
+The use of math fonts with an OpenType MATH table has been
+the opportunity for the MathML community to build relationships with font
+designers. We would like to thank Microsoft for creating the Cambria Math
+and making it available on Windows systems. In particular,
+[Murray Sargent](http://blogs.msdn.com/b/murrays/) was very helpful in private
+discussions on the MATH table and he was involved in its submission for
+standardization in Open Font Format 3. [Khaled Hosny](http://www.khaledhosny.org/) by his long experience in mathematical typesetting, familiarity with Arabic notations and deep knowledge of font formats has also provided prominent support to MathML implementers. Several of his fonts are freely available on [his GitHub repository](https://github.com/khaledhosny/). The work of the [GUST e-foundry group](http://www.gust.org.pl/projects/e-foundry/) was also instrumental in providing a [modernization of the classical Computer Modern font](http://www.gust.org.pl/projects/e-foundry/lm-math) as well as many other [math fonts](http://www.gust.org.pl/projects/e-foundry/tg-math), some of them still in development. Thanks also to the [STI Pub Consortium](http://stixfonts.org/) for designing and distributing the STIX Math font and its impressive Unicode coverage for mathematical and technical symbols. We are involved in the discussion for the development of STIX 2 and we are confident that this next release will be usable for MathML rendering soon. Finally, other designers have [created fonts with a MATH table](https://github.com/fred-wang/MathFonts/) and we are very grateful for their effort.
+
+MathML formula rendered by Firefox using the Latin Modern Math font. Left: "Windows" metrics ; Right: Typo metrics
+
+An important issues raised during the discussion with the
+font designers is the interpretation of [vertical font metrics](https://en.wikipedia.org/wiki/Typeface#Font_metrics). The Open Font Format contains three different metrics but only the "typo" metrics are really relevant for mathematical rendering. Especially, some metrics used on Windows must take into account the tallest glyphs of the font which can be excessively large in the case of a mathematical font (e.g. when it contains big integrals). To solve that issue, Microsoft introduced a [USE_TYPO_METRICS](http://www.microsoft.com/typography/otspec/os2.htm#fss) bit that tells implementers to really use the "typo" metrics.
+The MathML Association has thus been involved in implementing this feature in
+Web rendering engines with the help of Mozilla and Apple developers.
+More specifically, patches for [Gecko](https://bugzilla.mozilla.org/show_bug.cgi?id=598900) landed in May while patches for [WebKit](https://bugs.webkit.org/show_bug.cgi?id=131839) landed during the past two weeks. The USE_TYPO_METRICS bit is thus taken into account on all platforms in the current Firefox release. The same is true for WebKit Nightly with the exception of iOS and OS X where for now it only applies to fonts with a MATH table.
+
+The OpenType MATH table and USE_TYPO_METRICS feature were two of the requirements of the ["MathML in HTML5" implementation note](/MathMLinHTML5/).
+We will continue to support the projects of font designers and
+encourage OS vendors to make mathematical fonts widely available.
+Collaborating with browser vendors to
+improve the use of the MATH table for MathML rendering is also one of our
+top priority. We already had encouraging discussions with some WebKit developers
+and we will announce more in future updates. Stay tuned!
diff --git a/_posts/2015-11-30-minutes.md b/_posts/2015-11-30-minutes.md
new file mode 100644
index 0000000..56a38ff
--- /dev/null
+++ b/_posts/2015-11-30-minutes.md
@@ -0,0 +1,12 @@
+---
+layout: post
+title: "Board Meeting November 2015"
+category: minutes
+tags: [minutes]
+---
+Two weeks ago, we held our first board meeting, results:
+
+ * re-elected current slate of directors for 2016.
+ * progress on financial matters.
+
+Details can be found in the [minutes](/meetings/board-2015-11-30.html).
diff --git a/_posts/2016-02-15-annual-activity-report.md b/_posts/2016-02-15-annual-activity-report.md
new file mode 100644
index 0000000..1a8ef57
--- /dev/null
+++ b/_posts/2016-02-15-annual-activity-report.md
@@ -0,0 +1,14 @@
+---
+layout: post
+title: "Annual Activity Report 2015"
+category: announcement
+tags: [announcement]
+---
+
+We recently celebrated the first year of existence of the MathML Association!
+In 2015, we set up the organization structure, started
+outreach campaigns, liaised with other MathML-related organizations, and
+launched first technical projects to enhance
+MathML support in browsers. We just published our
+[annual activity report](/reports/2015.html) where you can find
+further details.
diff --git a/_posts/2016-02-15-borrero-law.md b/_posts/2016-02-15-borrero-law.md
new file mode 100644
index 0000000..045b6b9
--- /dev/null
+++ b/_posts/2016-02-15-borrero-law.md
@@ -0,0 +1,8 @@
+---
+layout: post
+title: "Welcome to Borrero Law"
+category: announcement
+tags: [announcement]
+---
+
+We are very glad to announce that the [Borrero Law Firm of New York](http://borrerolegal.com/) have agreed to come on board as our legal advisors. Their expertise in business, technology, and law will be instrumental to continue the development of the MathML Association and reach a legally solid non-profit structure where all [Affiliates](/affiliates/index.html) can get involved for the benefit of MathML... Welcome to Borrero Law!
diff --git a/_posts/2016-05-31-wikipedia.md b/_posts/2016-05-31-wikipedia.md
new file mode 100644
index 0000000..9fa1e8f
--- /dev/null
+++ b/_posts/2016-05-31-wikipedia.md
@@ -0,0 +1,94 @@
+---
+layout: post
+title: "MathML on Wikipedia"
+category: announcement
+tags: [announcement]
+---
+
+## Overview
+
+Our director Moritz Schubotz has been working for several months on a new MathML
+mode with SVG fallback for the MediaWiki Math engine. After intensive
+development and testing to ensure that existing features and performance are
+preserved, this mode finally became the default in all MediaWiki and Wikipedia
+web sites. This opens new perspectives for better rendering, accessibility,
+search, equation sharing, font & unicode support, styling, line breaking... and
+more!
+
+## Standard Improvements
+
+Until recently, mathematical formulas were output as PNG images contrary to the
+rest of the text of the page. This was the source of many inconsistencies and
+problems, the most famous being the bad rendering on high resolution display,
+at a large zoom level or when printed on paper.
+To solve that, SVG images are now served by default to all but old browsers.
+Hence this gives a clear picture at all scales. Using SVG also improves the
+integration of formulas with the surrounding text e.g. baseline alignment or
+text size.
+
+Formula from Wikipedia's article on the
Gamma function with PNG (above) or SVG (below)
+
+## More Enhancements
+
+Although using scalable images brings a significant rendering improvements, the
+mathematical formulas are still not treated as normal text but drawn with vector
+graphic primitives. For instance, if you try looking for the character "λ"
+using the standard search interface of your browser then you will never get a
+match for variables in mathematical formulas.
+
+At the moment OpenType math fonts are not widespread and MathML support in
+browsers is inconsistent. However, if you are ready for the next level of
+enhancements you can easily decide to replace the SVG display with the MathML
+display using this
+[Gecko addon](https://addons.mozilla.org/en-US/firefox/addon/native-mathml/) or by
+inserting [a few CSS lines](https://www.mediawiki.org/wiki/Extension:Math/advancedSettings#CSS_for_the_MathML_with_SVG_fallback_mode)
+in your custom style sheet. Depending on the font shipped with your systems,
+you may also need to [install math fonts](https://developer.mozilla.org/en-US/docs/Mozilla/MathML_Project/Fonts).
+
+After these configurations, the math rendering will be performed using standard
+font selection & text shaping methods which provides better rendering, unicode
+coverage, CSS customization (font-family, font-size etc.), text search,
+selection etc.
+
+Formula from Wikipedia's article on the
Gamma function rendered with various math fonts.
+
+With the MathML available in the DOM, you also have access to new enhancements. For example, you can use this
+[MathML copy](https://addons.mozilla.org/en-US/firefox/addon/mathml-copy/)
+to transfer MathML or TeX between Wiki pages and external programs like
+Computer Algebra Systems, or a
+[MathJax plugin](https://chrome.google.com/webstore/detail/math-anywhere/gebhifiddmaaeecbaiemfpejghjdjmhc)
+to render formulas on browsers that do not natively support MathML yet.
+
+
+On the left, there is a screen-shot, displaying a section of the book
+on quantum mechanics taken on May’16 2016 as non registered
+visitor using Firefox version 45, with the Native MathML plugin enabled. The
+photon momentum was selected, to demonstrate the bounding boxes of the symbols,
+and to copy and paste it to the computer Algebra System Mathematica (screen-shot
+on the right) as In[8]. The same step was performed for the relativistic momentum
+In[9]. Thereafter, an additional = sign has been manually inserted to In[8]. Thereafter
+Solve[%8,λ] was typed to compute the De-Broglie wavelength.
+
+One improvement that is worth mentioning is that assistive technologies can use
+the MathML content to provide better accessibility support for mathematical
+formulas. We have successfully tested this on a wide range of tools such as
+NVDA/MathPlayer, VoiceOver, Orca or ChromeVox.
+
+
+
+
+## Conclusion
+
+We expect that this new mode will encourage developers of web engines and
+assistive technologies to improve their MathML support. We also hope that type
+designers and operating system maintainers will continue to make OpenType font
+more widespread in order so that math text can be handled as any other human
+languages. We are excited about the current achievement and we are looking
+forward to continuing collaboration with all the developers and users in order
+to provide the best experience for math on the web!
diff --git a/_posts/2017-02-15-annual-activity-report.md b/_posts/2017-02-15-annual-activity-report.md
new file mode 100644
index 0000000..d966f7a
--- /dev/null
+++ b/_posts/2017-02-15-annual-activity-report.md
@@ -0,0 +1,14 @@
+---
+layout: post
+title: "Annual Activity Report 2016"
+category: announcement
+tags: [announcement]
+---
+
+We recently celebrated the second year of existence of the MathML Association!
+
+2016 was a slow year, due to personal circumstances of the directors (e.g. moving between
+universities, jobs, and continents).
+
+We just published our [annual activity report](/reports/2016.html) where you can find
+further details.
diff --git a/_posts/2017-04-29-mozilla-addons.md b/_posts/2017-04-29-mozilla-addons.md
new file mode 100644
index 0000000..7d2ba27
--- /dev/null
+++ b/_posts/2017-04-29-mozilla-addons.md
@@ -0,0 +1,10 @@
+---
+layout: post
+title: "Update on Mozilla Addons (MathZilla)"
+category: announcement
+tags: [announcement]
+---
+There is an interesting post about the state of the MathZilla addons, see
+http://frederic-wang.fr/mathzilla-collection-ported-to-webextensions.html
+
+
diff --git a/_posts/2017-05-qe-for-screen-readers.md b/_posts/2017-05-qe-for-screen-readers.md
new file mode 100644
index 0000000..f5de723
--- /dev/null
+++ b/_posts/2017-05-qe-for-screen-readers.md
@@ -0,0 +1,153 @@
+---
+layout: post
+title: "MathML Accessibility via Aria Labels: a Practice Test"
+category:
+tags:
+---
+
+# MathML Accessibility via Aria Labels: a Practice Test
+## Daniel Hajas, Michael Kohlhase, Ulrich Rabenstein
+
+### Introduction
+
+Access to Science, Technology, Engineering, Mathematics (STEM) information can
+be particularly challenging for visually impaired people. The routes of the
+challenges are
+* the extensive use of graphical information e.g. graphs and diagrams,
+* the highly symbolic language used for expressing mathematical relations,
+* often in an out-of-line mode for example sub-, and superscripts, or fractions.
+People with insufficient sight rely on screen reader software solutions either
+complementary or completely substituting screen magnification solutions. Screen
+readers can process computerised input and return output in either refreshable
+braille, or synthetic speech, known as Text-To-Speech (TTS). The principal way
+screen readers work is a line by line rendering of text. This is why WYSIWYG
+equation editors producing a visual “2D” output (e.g. fractions, binomial
+coefficients) are often inaccessible. Markup languages such as, LaTeX, or
+MathML offer in-line text processing and therefore are considered to be
+screen reader compatible.
+
+We have investigated the use of aria labels for better accessibility of HTML
+documents including MathML for blind people. Concretely, we looked at adding
+aria labels to MathML expressions in order to improve the output of screen
+reading programs. As an application for that, we have used the output of
+Ulrich Rabenstein's master thesis about the spotting of quantity expressions in
+arXMLiv documents. With these results, we want to add semantic information in
+the form of aria labels to the original documents.
+
+While humans are capable of assigning semantic meaning to quantity expressions
+and distinguish their meaning dependent of content, screen readers have trouble
+performing the same task, hence leading to potential confusion and
+inconveniences for visually impaired people. Examples are notation for measuring
+units, or meaning of superscripts. Currently, screen reading programs can not
+distinguish between a superscript symbolising a power, notation for chemical
+elements, or as notation for covariant vector components, indications of order
+of perturbation. Although attempts have been made for the interpretation of
+measuring unit notation, this usually only extends to a small number of cases
+such as, "A" for "Ampere", "mm" for "millimetres". These semantic definitions
+are stored in dictionary or script files of the relevant speech synthesiser and
+are linked to rule sets. For example a numerical character (e.g. 3) preceding
+the symbol “m” may be rendered as “three meters” or “three minutes” depending
+on manufacturer. The small set of defined measuring units, and the occasional
+incorrect interpretation require improvements in the field. Here, we focus on
+measuring units and report an alternative way to overcome the problem outlined.
+As a running example, we use "1500 V", for which a screen reader that access
+the aria labels should read "1500 Volt".
+
+### Forms of adding aria labels
+
+We have looked at three different ways to add aria labels to the documents.
+The first one is to add them directly to their corresponding MathML nodes as in
+the following snippet:
+```
+
+ 1500
+ V
+
+```
+Additionally we have also wrapped the presentation MathML inside a ```div```
+node and added the aria label to the ```div``` node.
+```
+
+
+ 1500
+ V
+
+
+```
+In the processed documents, quantity expressions occur not only in MathML but
+also in text. To preserve the structure of the documents, we also included the
+textual nodes inside ```div```s with aria labels as in this snippet:
+```
+
+ 1500
+
+ V
+
+```
+For verification of results presented below, we also performed tests on textual
+nodes wrapped in ```div```s using ```none``` as a value for the ```role```
+attribute.
+
+### Results
+
+In conjunction with [Grapheel](http://www.grapheel.com) represented by Daniel
+Hajas, we have tested these encodings with different screen readers, different browsers
+and on different platforms. As screen readers, we used
+[NVDA 2016](https://www.nvaccess.org/) and
+[JAWS 17.0](http://www.freedomscientific.com/Products/Blindness/JAWS) on Windows
+with Firefox 50 and Internet Explorer 11 as browsers. Additionally on Windows, there
+is the option to activate or deactivate
+[MathPlayer](https://www.dessci.com/en/products/mathplayer/tech/accessibility.htm)
+for the screen reader + browser setup. On Mac, we used
+[VoiceOver](http://www.apple.com/accessibility/mac/vision/) with Safari.
+
+However for the first option of snippets, all of the setups ignored the deep aria labels
+completely.
+
+For the second way of adding aria labels, we found one working configuration,
+namely NVDA with Internet Explorer with MathPlayer being deactivated. This way,
+it was possible to read the label and not only the content of the ```div```.
+
+We were surprised to observe the following completely different results for the
+third case:
+- NVDA with Internet Explorer (with or without MathPlayer) reads "1500 V", but
+ not the aria label
+- NVDA with Firefox (with or without MathPlayer) reads nothing at all, not even
+ "1500 V"
+- JAWS 17.0 with Internet Explorer 11 (with or without MathPlayer) reads "1500
+ V"
+- JAWS 17.0 with Firefox (with or without MathPlayer) actually reads "1500
+ Volt" from the aria label!
+- VoiceOver with Safari reads only "1500 V"
+
+So the previous configuration for presentation MathML inside a ```div``` node
+(NVDA + Internet Explorer + MathPlayer deactivated) fails when there is text
+inside the ```div```, but JAWS with Firefox works now, although it did not work
+for the former case. We are currently investigating whether different values of
+the role-attribute change the behaviour of the screen readers. Preliminary results
+show that ARIA labels are only taken in account if we set the attribute to ```math```.
+Using ```none``` in every possible permutation only ```1500 V``` is read.
+Interestingly however, with this attribute the NVDA plus FireFox again reads
+```1500 V``` instead of completely ignoring it. From our current
+point of view, we do not see a configuration that works with both presentation
+MathML and text inside ```div```s. Hence as a current workaround, we replace
+textual quantity expressions by presentation MathML in the documents and then
+use NVDA and Internet Explorer for screen reading. This enables us to open the
+same html document in the same browser, and simply switching between NVDA and JAWS,
+we can reveal the information encoded in the ARIA label, namely, that 1500 V means 1500 Volts.
+
+### Interpretation of results
+
+Our experiments suggest that recent introduction of solutions for exploring MathML content
+such as Math Viewer introduced in JAWS 16.0 or the MathPlayer add-on to enable
+NVDA explore MathML ignore ARIA labels completely. This is understandable since
+ARIA labels were means of providing textual descriptions for equations prior to
+explore features. Since symbol names are defined in character tables based on
+their unicode values, and XML processing is also taken care of a screen reader,
+MathML content is considered accessible with enhanced features compared to a
+single ARIA label. This is why NVDA could access the ARIA label in Internet
+Explorer when MathPlayer is deactivated. However, we argue that ARIA labels can
+be a valuable tool for purposes of encoding semantic interpretation. We propose,
+screen reader developers should enable their mathematical explorer to process
+deep ARIA labels within presentational MathML, while rendering HTML documents
+to speech or braille.
diff --git a/_sass/_base.scss b/_sass/_base.scss
new file mode 100644
index 0000000..035b485
--- /dev/null
+++ b/_sass/_base.scss
@@ -0,0 +1,208 @@
+/**
+ * Reset some basic elements
+ */
+body, h1, h2, h3, h4, h5, h6,
+p, blockquote, pre, hr,
+dl, dd, ol, ul, figure {
+ margin: 0;
+ padding: 0;
+}
+
+
+
+/**
+ * Basic styling
+ */
+body {
+ font-family: $base-font-family;
+ font-size: $base-font-size;
+ line-height: $base-line-height;
+ font-weight: 300;
+ color: $text-color;
+ background-color: $background-color;
+ -webkit-text-size-adjust: 100%;
+}
+
+strong {
+ font-weight: bold;
+}
+
+
+
+/**
+ * Set `margin-bottom` to maintain vertical rhythm
+ */
+h1, h2, h3, h4, h5, h6,
+p, blockquote, pre,
+ul, ol, dl, figure,
+%vertical-rhythm {
+ margin-bottom: $spacing-unit / 2;
+}
+
+
+
+/**
+ * Images
+ */
+img {
+ max-width: 100%;
+ vertical-align: middle;
+}
+
+
+
+/**
+ * Figures
+ */
+figure > img {
+ display: block;
+}
+
+figcaption {
+ font-size: $small-font-size;
+}
+
+
+
+/**
+ * Lists
+ */
+ul, ol {
+ margin-left: $spacing-unit;
+}
+
+li {
+ > ul,
+ > ol {
+ margin-bottom: 0;
+ }
+}
+
+
+
+/**
+ * Headings
+ */
+h1, h2, h3, h4, h5, h6 {
+ font-weight: 300;
+}
+
+
+
+/**
+ * Links
+ */
+a {
+ color: $brand-color;
+ text-decoration: none;
+
+ &:visited {
+ color: darken($brand-color, 15%);
+ }
+
+ &:hover {
+ color: $text-color;
+ text-decoration: underline;
+ }
+}
+
+
+
+/**
+ * Blockquotes
+ */
+blockquote {
+ color: $grey-color;
+ border-left: 4px solid $grey-color-light;
+ padding-left: $spacing-unit / 2;
+ font-size: 18px;
+ letter-spacing: -1px;
+ font-style: italic;
+
+ > :last-child {
+ margin-bottom: 0;
+ }
+}
+
+
+
+/**
+ * Code formatting
+ */
+pre,
+code {
+ font-size: 15px;
+ border: 1px solid $grey-color-light;
+ border-radius: 3px;
+ background-color: #eef;
+}
+
+code {
+ padding: 1px 5px;
+}
+
+pre {
+ padding: 8px 12px;
+ overflow-x: scroll;
+
+ > code {
+ border: 0;
+ padding-right: 0;
+ padding-left: 0;
+ }
+}
+
+
+
+/**
+ * Wrapper
+ */
+.wrapper {
+ max-width: -webkit-calc(#{$content-width} - (#{$spacing-unit} * 2));
+ max-width: calc(#{$content-width} - (#{$spacing-unit} * 2));
+ margin-right: auto;
+ margin-left: auto;
+ padding-right: $spacing-unit;
+ padding-left: $spacing-unit;
+ @extend %clearfix;
+
+ @include media-query($on-laptop) {
+ max-width: -webkit-calc(#{$content-width} - (#{$spacing-unit}));
+ max-width: calc(#{$content-width} - (#{$spacing-unit}));
+ padding-right: $spacing-unit / 2;
+ padding-left: $spacing-unit / 2;
+ }
+}
+
+
+
+/**
+ * Clearfix
+ */
+%clearfix {
+
+ &:after {
+ content: "";
+ display: table;
+ clear: both;
+ }
+}
+
+
+
+/**
+ * Icons
+ */
+.icon {
+
+ > svg {
+ display: inline-block;
+ width: 16px;
+ height: 16px;
+ vertical-align: middle;
+
+ path {
+ fill: $grey-color;
+ }
+ }
+}
diff --git a/_sass/_layout.scss b/_sass/_layout.scss
new file mode 100644
index 0000000..61c98ca
--- /dev/null
+++ b/_sass/_layout.scss
@@ -0,0 +1,338 @@
+/**
+ * Site header
+ */
+.site-header {
+ text-align: center;
+
+ // Positioning context for the mobile navigation icon
+ position: relative;
+
+ .site-nav-wrapper {
+ background: $scheme-color-1;
+ background: linear-gradient(to bottom, white, 10%, $scheme-color-1);
+ @include media-query($on-palm) {
+ background: white;
+ }
+ }
+}
+
+.site-title {
+ font-size: 26px;
+ line-height: 32px;
+ letter-spacing: -1px;
+ margin-bottom: 0;
+
+ &,
+ &:visited {
+ color: white;
+ }
+}
+
+.site-nav {
+ line-height: 32px;
+ display:table;
+ margin:0 auto;
+
+ .menu-icon {
+ display: none;
+ }
+
+ ul {
+ margin: 0;
+ padding: 0;
+ list-style: none;
+ }
+ ul li {
+ display: block;
+ position: relative;
+ float: left;
+ min-width: 120px;
+ }
+ li ul {
+ display: none;
+ margin-left: 0;
+ }
+ ul li a {
+ display: block;
+ text-decoration: none;
+ padding: 5px 15px 5px 15px;
+ color: white;
+ }
+ ul li a:hover {
+ background: white;
+ color: $scheme-color-1;
+ }
+ li:hover ul {
+ display: block;
+ position: absolute;
+ }
+ li:hover li {
+ float: none;
+ }
+ li:hover ul li { background: $scheme-color-1; }
+ li:hover li a:hover { background: white; }
+
+ @include media-query($on-palm) {
+ position: absolute;
+ top: 9px;
+ right: 30px;
+ background-color: $background-color;
+ border: 1px solid $grey-color-light;
+ border-radius: 5px;
+ text-align: right;
+
+ .menu-icon {
+ display: block;
+ float: right;
+ width: 36px;
+ height: 26px;
+ line-height: 0;
+ padding-top: 10px;
+ text-align: center;
+
+ > svg {
+ width: 18px;
+ height: 15px;
+
+ path {
+ fill: $grey-color-dark;
+ }
+ }
+ }
+
+ .trigger {
+ clear: both;
+ display: none;
+ }
+
+ ul {
+ margin-left: 0;
+ }
+ li ul {
+ display: block;
+ }
+ ul li {
+ display: block;
+ position: relative;
+ float: none;
+ }
+ ul li a {
+ display: block;
+ text-decoration: none;
+ padding: 5px 15px 5px 15px;
+ margin-left: 1px;
+ color: $scheme-color-1;
+ }
+ li:hover a:hover {
+ background-color: $scheme-color-1;
+ color: white;
+ }
+ li:hover ul {
+ display: block;
+ position: relative;
+ }
+ li:hover li {
+ float: none;
+ }
+ li:hover a { background: white; }
+ li:hover li a:hover {
+ background-color: $scheme-color-1;
+ color: white;
+ }
+
+ &:hover .trigger {
+ display: block;
+ padding-bottom: 5px;
+ }
+
+ .page-link {
+ display: block;
+ padding: 5px 10px;
+ }
+ }
+}
+
+
+
+/**
+ * Site footer
+ */
+.site-footer {
+ border-top: 1px solid $grey-color-light;
+ padding: $spacing-unit 0;
+}
+
+.footer-heading {
+ font-size: 18px;
+ margin-bottom: $spacing-unit / 2;
+}
+
+.contact-list,
+.social-media-list {
+ list-style: none;
+ margin-left: 0;
+}
+
+.contact-list img,
+.social-media-list img {
+ height: 15px;
+}
+
+.footer-col-wrapper {
+ font-size: 15px;
+ color: $grey-color;
+ margin-left: -$spacing-unit / 2;
+ @extend %clearfix;
+}
+
+.footer-col,
+.footer-multi-col {
+ margin-bottom: $spacing-unit / 2;
+ padding-left: $spacing-unit / 2;
+}
+
+.footer-multi-col {
+ float: left;
+}
+
+.footer-col-1 {
+ width: -webkit-calc(50% - (#{$spacing-unit} / 2));
+ width: calc(50% - (#{$spacing-unit} / 2));
+}
+
+.footer-col-2 {
+ width: -webkit-calc(40% - (#{$spacing-unit} / 2));
+ width: calc(40% - (#{$spacing-unit} / 2));
+}
+
+@include media-query($on-laptop) {
+ .footer-col-1,
+ .footer-col-2 {
+ width: -webkit-calc(50% - (#{$spacing-unit} / 2));
+ width: calc(50% - (#{$spacing-unit} / 2));
+ }
+
+ .footer-col-3 {
+ width: -webkit-calc(100% - (#{$spacing-unit} / 2));
+ width: calc(100% - (#{$spacing-unit} / 2));
+ }
+}
+
+@include media-query($on-palm) {
+ .footer-col {
+ float: none;
+ width: -webkit-calc(100% - (#{$spacing-unit} / 2));
+ width: calc(100% - (#{$spacing-unit} / 2));
+ }
+}
+
+
+
+/**
+ * Page content
+ */
+.page-content {
+ padding: $spacing-unit 0;
+}
+
+.page-heading {
+ font-size: 20px;
+}
+
+.post-list {
+ margin-left: 0;
+ list-style: none;
+
+ > li {
+ margin-bottom: $spacing-unit;
+ }
+}
+
+.post-meta {
+ font-size: $small-font-size;
+ color: $grey-color;
+}
+
+.post-link {
+ display: block;
+ font-size: 24px;
+}
+
+
+
+/**
+ * Posts
+ */
+.post-header {
+ margin-bottom: $spacing-unit;
+}
+
+.post-title {
+ font-size: 42px;
+ letter-spacing: -1px;
+ line-height: 1;
+
+ @include media-query($on-laptop) {
+ font-size: 36px;
+ }
+}
+
+.post-content {
+ margin-bottom: $spacing-unit;
+
+ h2 {
+ font-size: 32px;
+
+ @include media-query($on-laptop) {
+ font-size: 28px;
+ }
+ }
+
+ h3 {
+ font-size: 26px;
+
+ @include media-query($on-laptop) {
+ font-size: 22px;
+ }
+ }
+
+ h4 {
+ font-size: 20px;
+
+ @include media-query($on-laptop) {
+ font-size: 18px;
+ }
+ }
+}
+
+/* People */
+
+.people {
+ clear: both;
+}
+
+.people-photo {
+ float: left;
+ margin: 5px;
+ width: 130px;
+ height: 120px;
+}
+
+.people-info {
+ float: left;
+ margin: 5px;
+ max-width: -webkit-calc(100% - 150px);
+ max-width: calc(100% - 150px);
+}
+
+.people-info a {
+ text-decoration: none;
+}
+
+/* Projects */
+
+.project {
+ margin: 1em;
+ padding: 0.5em;
+ background-color: $scheme-color-1;
+}
diff --git a/_sass/_syntax-highlighting.scss b/_sass/_syntax-highlighting.scss
new file mode 100644
index 0000000..e36627d
--- /dev/null
+++ b/_sass/_syntax-highlighting.scss
@@ -0,0 +1,67 @@
+/**
+ * Syntax highlighting styles
+ */
+.highlight {
+ background: #fff;
+ @extend %vertical-rhythm;
+
+ .c { color: #998; font-style: italic } // Comment
+ .err { color: #a61717; background-color: #e3d2d2 } // Error
+ .k { font-weight: bold } // Keyword
+ .o { font-weight: bold } // Operator
+ .cm { color: #998; font-style: italic } // Comment.Multiline
+ .cp { color: #999; font-weight: bold } // Comment.Preproc
+ .c1 { color: #998; font-style: italic } // Comment.Single
+ .cs { color: #999; font-weight: bold; font-style: italic } // Comment.Special
+ .gd { color: #000; background-color: #fdd } // Generic.Deleted
+ .gd .x { color: #000; background-color: #faa } // Generic.Deleted.Specific
+ .ge { font-style: italic } // Generic.Emph
+ .gr { color: #a00 } // Generic.Error
+ .gh { color: #999 } // Generic.Heading
+ .gi { color: #000; background-color: #dfd } // Generic.Inserted
+ .gi .x { color: #000; background-color: #afa } // Generic.Inserted.Specific
+ .go { color: #888 } // Generic.Output
+ .gp { color: #555 } // Generic.Prompt
+ .gs { font-weight: bold } // Generic.Strong
+ .gu { color: #aaa } // Generic.Subheading
+ .gt { color: #a00 } // Generic.Traceback
+ .kc { font-weight: bold } // Keyword.Constant
+ .kd { font-weight: bold } // Keyword.Declaration
+ .kp { font-weight: bold } // Keyword.Pseudo
+ .kr { font-weight: bold } // Keyword.Reserved
+ .kt { color: #458; font-weight: bold } // Keyword.Type
+ .m { color: #099 } // Literal.Number
+ .s { color: #d14 } // Literal.String
+ .na { color: #008080 } // Name.Attribute
+ .nb { color: #0086B3 } // Name.Builtin
+ .nc { color: #458; font-weight: bold } // Name.Class
+ .no { color: #008080 } // Name.Constant
+ .ni { color: #800080 } // Name.Entity
+ .ne { color: #900; font-weight: bold } // Name.Exception
+ .nf { color: #900; font-weight: bold } // Name.Function
+ .nn { color: #555 } // Name.Namespace
+ .nt { color: #000080 } // Name.Tag
+ .nv { color: #008080 } // Name.Variable
+ .ow { font-weight: bold } // Operator.Word
+ .w { color: #bbb } // Text.Whitespace
+ .mf { color: #099 } // Literal.Number.Float
+ .mh { color: #099 } // Literal.Number.Hex
+ .mi { color: #099 } // Literal.Number.Integer
+ .mo { color: #099 } // Literal.Number.Oct
+ .sb { color: #d14 } // Literal.String.Backtick
+ .sc { color: #d14 } // Literal.String.Char
+ .sd { color: #d14 } // Literal.String.Doc
+ .s2 { color: #d14 } // Literal.String.Double
+ .se { color: #d14 } // Literal.String.Escape
+ .sh { color: #d14 } // Literal.String.Heredoc
+ .si { color: #d14 } // Literal.String.Interpol
+ .sx { color: #d14 } // Literal.String.Other
+ .sr { color: #009926 } // Literal.String.Regex
+ .s1 { color: #d14 } // Literal.String.Single
+ .ss { color: #990073 } // Literal.String.Symbol
+ .bp { color: #999 } // Name.Builtin.Pseudo
+ .vc { color: #008080 } // Name.Variable.Class
+ .vg { color: #008080 } // Name.Variable.Global
+ .vi { color: #008080 } // Name.Variable.Instance
+ .il { color: #099 } // Literal.Number.Integer.Long
+}
diff --git a/about.md b/about.md
new file mode 100644
index 0000000..91c0e91
--- /dev/null
+++ b/about.md
@@ -0,0 +1,53 @@
+---
+layout: page
+title: About us
+---
+
+The need to write mathematics dates back to the creation of the Web
+by researchers at CERN where it was intended to be used to exchange
+scientific documents. A `` tag was proposed in a HTML 3.0 Draft from
+1995 and the MathML 1.0 standard was released in 1998.
+Years later, MathML is not supported consistently and reliably by all Web
+rendering engines, assistive technologies or
+mathematical tools. We still face a chicken-and-egg problem where some browser
+vendors are reluctant to put effort on native MathML developments while other
+companies, organizations or individuals have kept promoting their own hacks
+to workaround the lack of MathML support in browsers:
+PNG/SVG images of formula, CSS stylesheets, Javascript code for mathematical
+layout...
+
+This means that today, all browsers do not support the simplest Web features
+like CSS styling to select a mathematical font for your formulas, Javascript
+programming to edit the DOM of an equation and have its rendering automatically
+updated, using arbitrary Unicode characters in formulas or embedding formulas
+in SVG schemas. While the Web community has been promoting browser speed,
+accessibility (e.g. zooming or screen reading of equations),
+responsive layout (e.g. automatic linebreaking of mathematical formulas),
+internationalization (e.g. formulas
+with Arabic characters written from right-to-left and using typographic
+ligatures), these features are hardly possible for mathematics without proper
+integration into the web engines. Many other features like copy and paste
+transfers, search engines, feed aggregators, emails, etc are limited by the
+lack of MathML support or by the use of non-standard alternatives.
+
+Given the above, it appeared necessary to:
+
+* Create a nonprofit organization to collect money and fund native MathML
+ developments in Web rendering engines. The various volunteers who have worked
+ on native MathML implementations and the successful crowdfunding project
+ [Mathematics in ebooks](http://www.ulule.com/mathematics-ebooks/) showed that
+ there is a strong interest. However, a legal entity seems necessary to
+ encourage the participation of major actors and go farther than an individual
+ or short-term effort.
+
+* Encourage the developments of concrete mathematical tools and Web-based
+ applications demonstrating the benefits of a good integration of mathematical
+ support in the Web platform. This requires a desinterested entity in contrast
+ to companies, organizations or individuals focusing more on developing their
+ mathematical tools and promoting their own products.
+
+As a consequence, a group of math-on-the-web enthusiasts decided to create
+a nonprofit organization in order to provide a solid foundation for MathML
+development efforts and a legal entity to speak for people willing to make
+mathematics a first class citizen on the Web. In 2015, the Mondial Association
+for Tools Handling MathML, Ltd (for short, "MathML association") was born.
diff --git a/affiliates/donate.md b/affiliates/donate.md
new file mode 100644
index 0000000..eea734c
--- /dev/null
+++ b/affiliates/donate.md
@@ -0,0 +1,7 @@
+---
+layout: page
+title: Donate
+---
+
+**Note: Online donations are not possible yet. Please come back later or send
+ an email to [{{site.email}}](mailto:{{site.email}}).**
diff --git a/affiliates/friends.md b/affiliates/friends.md
new file mode 100644
index 0000000..b2eaeb6
--- /dev/null
+++ b/affiliates/friends.md
@@ -0,0 +1,46 @@
+---
+layout: page
+title: Friends
+---
+
+Thank you to the crowd of MathML enthusiasts for their volunteer work in
+MathML projects and for spreading the word about native MathML support...
+You're awesome! Special thanks to our current (7th November 2015) friends:
+
+* [Corinna Breitinger](http://www.isg.uni-konstanz.de/people/corinna-breitinger) (Researcher at the Information Science Group in the Department of Computer and Information Science at the University of Konstanz, Germany)
+* [Howard Cohl](http://www.nist.gov/itl/math/msg/howard-s-cohl.cfm) (Mathematician in the Applied and Computational Mathematics Division at the National Institute of Standards and Technology, Gaithersburg, MD, USA)
+* Adrian Fellhauer (Student of mathematics at Technical University Munich)
+* [Bela Gipp](http://www.gipp.com) (Professor for Information Science in the Department of Computer and Information Science at the University of Konstanz, Germany)
+* [Felix Hamborg](https://www.isg.uni-konstanz.de/people/felix-hamborg) (Researcher at the Information Science Group in the Department of Computer and Information Science at the University of Konstanz, Germany)
+* [Samuel Lelièvre](http://www.math.u-psud.fr/~lelievre) Maître de conférences in Mathematics, Orsay Math
+department, Université Paris-Sud, Université Paris-Saclay, France
+* [Norman Meuschke](http://www.meuschke.org) (Researcher at the Information Science Group in the Department of Computer and Information Science at the University of Konstanz, Germany)
+* [Bruce Miller](http://math.nist.gov/~BMiller/) (Software Developer/Architect in the Applied and Computational Mathematics Division at National Institute of Standards and Technology, Gaithersburg, MD, USA)
+* [Jim Pitman](http://www.stat.berkeley.edu/users/pitman/) (Professor of Statistics and Mathematics, University of California, Berkeley, USA.)
+* [Franz-Josef Schmitt](http://www.uniwind.org/schmitt) (PostDoc at TU Berlin, researcher in bioenergetics, teaching mathematics and chemistry)
+* [Frédéric Wang](http://frederic-wang.fr/) (Igalia developer)
+* [Abdou Youssef](http://www.seas.gwu.edu/~ayoussef/) (Professor of Computer Science at the George Washington University, USA.)
+* Hang Yuan (2nd year computer science student at Jacobs University Bremen)
+
+## Becoming a MathML Friend
+
+Interested in becoming a MathML Friend? Great! Please check the terms of the
+[Affiliates document](/legal-documents/affiliates.html) and
+submit an email to the [MathML directors](/people/directors.html) using
+[this template](mailto:directors@mathml-association.org?subject=Becoming%20a%20Friend&body=%5BPlease%20remove%20the%20text%20in%20brackets%20and%20replace%20it%20with%20the%20requested%20content.%5D%0A%0ADear%20MathML%20directors,%0A%0AI'm%20applying%20to%20become%20a%20MathML%20Friend.%20Please%20find%20my%20information%20below.%0A%0AFull%20name:%20%5Brequired%5D%0ABrief%20introduction:%20%5Brequired%20;%20for%20example%20'PhD%20student%20in%20the%20Department%20of%20Physics%20at%20Harvard%20University'%5D%0A%0ALink:%20%5Boptional%20;%20homepage%20or%20social%20media%20accounts%5D%0A%0AI%20hereby%20state%20that%20I%20read%20the%20terms%20of%20the%20Affiliates%20document%20(1),%20that%20I%20want%20to%20become%20a%20%22MathML%20Friend%22%20and%20that%20I%20fulfill%20all%20the%20requirements.%20In%20particular,%20I%20attest%20that%20I%20am%2018%20years%20of%20age%20or%20older%20and%20that%20I%20agree%20my%20collaborative%20efforts%20with%20the%20MathML%20Association%20will%20be%20in%20keeping%20with%20the%20Manifesto%20(2).%20I%20also%20give%20you%20the%20permission%20to%20publish%20the%20information%20provided%20in%20the%20'required'%20fields%20above.%0A%0A(1)%20http%3A%2F%2Fmathml-association.org%2Flegal-documents%2Faffiliates.html%0A(2)%20http%3A%2F%2Fmathml-association.org%2Flegal-documents%2Fmanifesto.html%0A)
+(alternatively, try [this link](data:text/plain,mailto:%20directors@mathml-association.org%0Asubject:%20Becoming%20a%20Friend%0A%0A%5BPlease%20remove%20the%20text%20in%20brackets%20and%20replace%20it%20with%20the%20requested%20content.%5D%0A%0ADear%20MathML%20directors,%0A%0AI'm%20applying%20to%20become%20a%20MathML%20Friend.%20Please%20find%20my%20information%20below.%0A%0AFull%20name:%20%5Brequired%5D%0ABrief%20introduction:%20%5Brequired%20;%20for%20example%20'PhD%20student%20in%20the%20Department%20of%20Physics%20at%20Harvard%20University'%5D%0A%0ALink:%20%5Boptional%20;%20homepage%20or%20social%20media%20accounts%5D%0A%0AI%20hereby%20state%20that%20I%20read%20the%20terms%20of%20the%20Affiliates%20document%20(1),%20that%20I%20want%20to%20become%20a%20%22MathML%20Friend%22%20and%20that%20I%20fulfill%20all%20the%20requirements.%20In%20particular,%20I%20attest%20that%20I%20am%2018%20years%20of%20age%20or%20older%20and%20I%20agree%20my%20collaborative%20efforts%20with%20the%20MathML%20Association%20will%20be%20in%20keeping%20with%20the%20Manifesto%20(2).%20I%20also%20give%20you%20the%20permission%20to%20publish%20the%20information%20provided%20in%20the%20'required'%20fields%20above.%0A%0A(1)%20http%3A%2F%2Fmathml-association.org%2Flegal-documents%2Faffiliates.html%0A(2)%20http%3A%2F%2Fmathml-association.org%2Flegal-documents%2Fmanifesto.html%0A)),
+including at least your name and a brief introduction.
+Note that your message will be stored on our server and will only be accessible
+to the [directors](/people/directors.html).
+
+Once we receive your message, we will try to come back to you within three business days.
+If your application is approved, **your name, the brief introduction and
+optional link will be used on this Friends page and for public announcements**.
+Also, note that
+**your email address will be used for communication with the MathML
+Association**, including notifications of changes to the terms of the
+[Affiliates document](/legal-documents/affiliates.html).
+
+Finally, you are also encouraged to
+[subscribe to this public MathML Friends mailing list](http://lists.mathml-association.org/mailman/listinfo/friends) now so that you can keep updated about latest news and discuss with other members of the MathML community!
+
diff --git a/affiliates/index.md b/affiliates/index.md
new file mode 100644
index 0000000..250ed4f
--- /dev/null
+++ b/affiliates/index.md
@@ -0,0 +1,29 @@
+---
+layout: page
+title: Affiliates
+---
+
+The MathML Association intends to gather all the individuals and organizations
+willing to advance the mission of the [MathML manifesto](/legal-documents/manifesto.html). For that purpose, we have settled
+a [status of affiliates](/legal-documents/affiliates.html) that enables each
+one to contribute at the desired level:
+
+- [Sponsors](sponsors.html) are companies or organizations recognizing the
+ importance of MathML and willing to help MathML Association projects by
+ making an annual contribution and possibly getting involved in the
+ MathML Advisory Board.
+
+- [Partners](partners.html) are companies, organizations, or individuals with
+ technical expertise in open source development of Web engines or related
+ technologies (math fonts, accessibility tools etc). They are privileged
+ interlocutors for technical discussions, collaborations and contracts on
+ MathML Association projects.
+
+- [Friends](friends.html) are individuals willing to support our mission and are
+ free to contribute as they wish. For example, they can
+ [make a donation](donate.html) to the MathML Association or do volunteer work
+ on MathML Association projects. Prominent friends may be invited to become
+ members of the MathML Advisory Board.
+
+Please send an email to [{{site.email}}](mailto:{{site.email}}) if you are
+interested in becoming an affiliate.
diff --git a/affiliates/partners.md b/affiliates/partners.md
new file mode 100644
index 0000000..4c0540c
--- /dev/null
+++ b/affiliates/partners.md
@@ -0,0 +1,11 @@
+---
+layout: page
+title: Partners
+---
+
+We are grateful to our MathML Partners for their technical expertise
+and collaborations on MathML-related developments. Your help is invaluable!
+
+**Note: We plan to update this page once we start the affiliate program.
+If you wish to become a MathML Partner, please send an email to
+[{{site.email}}](mailto:{{site.email}}).**
diff --git a/affiliates/sponsors.md b/affiliates/sponsors.md
new file mode 100644
index 0000000..a14961d
--- /dev/null
+++ b/affiliates/sponsors.md
@@ -0,0 +1,12 @@
+---
+layout: page
+title: Sponsors
+---
+
+We would like to thank our generous sponsors for their support... This help
+is crucial to lead MathML developments and advance the mission of
+the [MathML Manifesto](/legal-documents/manifesto.html)!
+
+**Note: We plan to update this page once we start the affiliate program.
+If you wish to become a MathML Sponsor, please send an email to
+[{{site.email}}](mailto:{{site.email}}).**
diff --git a/contact.md b/contact.md
new file mode 100644
index 0000000..13d8e44
--- /dev/null
+++ b/contact.md
@@ -0,0 +1,12 @@
+---
+layout: page
+title: Contact
+---
+
+Mondial Association For Tools Handling MathML, Ltd.
+
+[{{site.email}}](mailto:{{site.email}})
+
+Deyan Ginev
+40 Waterside Plaza 26D
+New York, New York, 10010
diff --git a/css/main.scss b/css/main.scss
new file mode 100755
index 0000000..400ae5e
--- /dev/null
+++ b/css/main.scss
@@ -0,0 +1,56 @@
+---
+# Only the main Sass file needs front matter (the dashes are enough)
+---
+@charset "utf-8";
+
+
+
+// Our variables
+$base-font-family: Helvetica, Arial, sans-serif;
+$base-font-size: 16px;
+$small-font-size: $base-font-size * 0.875;
+$base-line-height: 1.5;
+
+$spacing-unit: 30px;
+
+$text-color: #111;
+$background-color: #fdfdfd;
+$brand-color: #2a7ae2;
+
+$grey-color: #828282;
+$grey-color-light: lighten($grey-color, 40%);
+$grey-color-dark: darken($grey-color, 25%);
+
+$scheme-color-1: #53C270;
+$scheme-color-2: #B7EC65;
+$scheme-color-3: #4892A3;
+
+// Width of the content area
+$content-width: 800px;
+
+$on-palm: 600px;
+$on-laptop: 800px;
+
+
+
+// Using media queries with like this:
+// @include media-query($on-palm) {
+// .wrapper {
+// padding-right: $spacing-unit / 2;
+// padding-left: $spacing-unit / 2;
+// }
+// }
+@mixin media-query($device) {
+ @media screen and (max-width: $device) {
+ @content;
+ }
+}
+
+
+
+// Import partials from `sass_dir` (defaults to `_sass`)
+@import
+ "base",
+ "layout",
+ "syntax-highlighting"
+;
diff --git a/faq.md b/faq.md
new file mode 100644
index 0000000..d04aa5a
--- /dev/null
+++ b/faq.md
@@ -0,0 +1,82 @@
+---
+layout: page
+title: FAQ
+---
+
+* [The table of contents will go here]
+{:toc}
+
+## 1. What are the goals of the MathML association?
+
+The goals of the MathML association are:
+
+* Native implementation of the MathML language in all Web rendering engines.
+* Development of software tools to let users read, write, search, store and
+ transfer MathML formulas; with particular attention to make them accessible
+ to people with disabilities.
+* Usage of the MathML language to publish educational, technical and scientific
+ content in Web sites, ebooks or Web apps.
+* Other developmental and promotional activities to further the dissemination
+ of mathematical content in Web sites, ebooks or Web apps.
+
+For more details, take a look at our [Manifesto](/legal-documents/manifesto.html).
+
+## 2. What are your plans to implement MathML in Web rendering engines?
+
+In general, we started to write a detailed technical document
+"[MathML in HTML5](http://www.mathml-association.org/MathMLinHTML5/)" to
+describe how to implement a core subset of MathML 3 in a way that is both
+compatible with the existing browser codebase and with the requirement of
+"high-quality" mathematical rendering. We expect that it will be instrumental
+in getting native MathML implementations accepted by browser vendors.
+
+Gecko (e.g. Firefox) and WebKit (e.g. Safari) are open source, have some MathML
+support and there are developers from companies working on these rendering
+engines who accept to review patches. Hence we will continue to collaborate
+with them to fix bugs and improve the MathML support.
+
+Blink (e.g. Chrome) is open source but Google has indicated they will only
+consider native MathML once it becomes more popular on the Web. Hence we instead
+want to get in touch with other companies working on the Blink codebase and see
+if they are interested in starting a development branch with MathML support.
+Fortunately, we can rely on the effort made for WebKit.
+
+EdgeHTML (Microsoft Edge) is proprietary so we do not have any control on
+the codebase. Note that according to [a blog post from Murray Sargent](http://blogs.msdn.com/b/murrays/archive/2014/04/27/opentype-math-tables.aspx), an
+implemention of "Office MathML" exists in Microsoft Office and could be use for
+Microsoft's browser. We would very like to convince Microsoft to give a try.
+
+## 3. Where can I vote for MathML support in Chrome and Microsoft Edge?
+
+Try to vote for [MathML in Chrome](https://code.google.com/p/chromium/issues/detail?id=152430) and [MathML in Microsoft Edge](https://dev.windows.com/en-us/microsoft-edge/platform/status/mathml).
+
+## 4. How is the MathML association different from the OpenMath Society?
+
+As stated on the [OpenMath website](www.openmath.org), the goal of OpenMath Society is to "coordinate OpenMath activities" with focus on "semantic meaning or content" of mathematical formulas. The MathML association is instead focused on making MathML well-integrated into the Web platform and natively supported by Web browsers and assistive technologies.
+
+That said, "the two technologies may be seen as highly complementary". OpenMath is strongly related to Content MathML and the <semantics> element can be used to provide MathML formulas with both presentation and meaning. The MathML manifesto highlights the importance of combining these two languages.
+
+Many members of the Open Society are already involved in the MathML Association. We hope that more of them will support the MathML Manifesto and could become MathML affiliates.
+
+## 5. How is the MathML association different from the MathJax Consortium?
+
+As stated on the [MathJax website](https://www.mathjax.org), "The core of the MathJax project is the development of its state-of-the-art, open source, JavaScript platform for display of mathematics" while the MathML Association does not focus on a particular product but on native support everywhere.
+
+We are happy that MathJax has already embraced MathML, which is used as its core formula representation language. While MathJax has provided an invaluable bridge solution for displaying beautiful math-on-the-web today, the MathML association is focusing on advancing the state of web mathematics tomorrow.
+
+Our goal towards standards-compliant web mathematics, via native MathML support in all browsers, aims at faster rendering, better accessibility and towards building a healthy ecosystem of math web application development. [Quoting MathJax's Manager](http://exchanges.wiley.com/blog/2015/03/02/making-math-and-science-first-class-citizens-on-the-web/), "While we are proud of our accomplishments at MathJax, we know that we can only provide half the solution: native browser support must be the goal". Consequently, we hope that the MathJax Consortium will support our manifesto and could become a MathML affiliate.
+
+## 6. How is the MathML association different from the W3C Math Working Group?
+
+The [World Wide Web Consortium (W3C)](http://w3.org) is an "international community that
+develops open standards to ensure the long-term growth of the Web". The
+[Math working Group (Math WG)](http://www.w3.org/Math/) instantiates this to "facilitate
+and promote the use of the Web for mathematical and scientific communication". The Math WG
+has developed the MathML representation langauge for the presentation and content of
+mathematical formulae since 1997, the current recommendation is
+[MathML3](http://www.w3.org/TR/MathML3/) (April 2014), which was approved as ISO/IEC
+International Standard in June 2015.
+
+The MathML association wants to promote the standards (W3C recommendations) developed by
+the W3C Math WG, support their implementation in web technologies, and raise public
+awareness about MathML.
diff --git a/feed.xml b/feed.xml
new file mode 100644
index 0000000..a6628bd
--- /dev/null
+++ b/feed.xml
@@ -0,0 +1,30 @@
+---
+layout: null
+---
+
+
+
+ {{ site.title | xml_escape }}
+ {{ site.description | xml_escape }}
+ {{ site.url }}{{ site.baseurl }}/
+
+ {{ site.time | date_to_rfc822 }}
+ {{ site.time | date_to_rfc822 }}
+ Jekyll v{{ jekyll.version }}
+ {% for post in site.posts limit:10 %}
+ -
+
{{ post.title | xml_escape }}
+ {{ post.content | xml_escape }}
+ {{ post.date | date_to_rfc822 }}
+ {{ post.url | prepend: site.baseurl | prepend: site.url }}
+ {{ post.url | prepend: site.baseurl | prepend: site.url }}
+ {% for tag in post.tags %}
+ {{ tag | xml_escape }}
+ {% endfor %}
+ {% for cat in post.categories %}
+ {{ cat | xml_escape }}
+ {% endfor %}
+
+ {% endfor %}
+
+
diff --git a/img/background.jpg b/img/background.jpg
new file mode 100644
index 0000000..3a6de78
Binary files /dev/null and b/img/background.jpg differ
diff --git a/img/github-48x48.png b/img/github-48x48.png
new file mode 100755
index 0000000..af6d280
Binary files /dev/null and b/img/github-48x48.png differ
diff --git a/img/logo16x16.ico b/img/logo16x16.ico
new file mode 100644
index 0000000..9499cf0
Binary files /dev/null and b/img/logo16x16.ico differ
diff --git a/img/nomath-vs-math.png b/img/nomath-vs-math.png
new file mode 100644
index 0000000..59fb599
Binary files /dev/null and b/img/nomath-vs-math.png differ
diff --git a/img/people/ginev.deyan.jpg b/img/people/ginev.deyan.jpg
new file mode 100644
index 0000000..8bb5c67
Binary files /dev/null and b/img/people/ginev.deyan.jpg differ
diff --git a/img/people/kohlhase.michael.jpg b/img/people/kohlhase.michael.jpg
new file mode 100644
index 0000000..1ee3a2a
Binary files /dev/null and b/img/people/kohlhase.michael.jpg differ
diff --git a/img/people/schubotz.moritz.jpg b/img/people/schubotz.moritz.jpg
new file mode 100644
index 0000000..f383d26
Binary files /dev/null and b/img/people/schubotz.moritz.jpg differ
diff --git a/img/people/silva.raniere.jpg b/img/people/silva.raniere.jpg
new file mode 100644
index 0000000..a260736
Binary files /dev/null and b/img/people/silva.raniere.jpg differ
diff --git a/img/people/wang.frederic.jpg b/img/people/wang.frederic.jpg
new file mode 100644
index 0000000..f7ac76c
Binary files /dev/null and b/img/people/wang.frederic.jpg differ
diff --git a/img/wikipedia-cas.png b/img/wikipedia-cas.png
new file mode 100644
index 0000000..4413ee7
Binary files /dev/null and b/img/wikipedia-cas.png differ
diff --git a/img/wikipedia-math-fonts.png b/img/wikipedia-math-fonts.png
new file mode 100644
index 0000000..44a60db
Binary files /dev/null and b/img/wikipedia-math-fonts.png differ
diff --git a/img/wikipedia-png-vs-svg.png b/img/wikipedia-png-vs-svg.png
new file mode 100644
index 0000000..111a55f
Binary files /dev/null and b/img/wikipedia-png-vs-svg.png differ
diff --git a/img/win-vs-typo.png b/img/win-vs-typo.png
new file mode 100644
index 0000000..776626d
Binary files /dev/null and b/img/win-vs-typo.png differ
diff --git a/index.md b/index.md
new file mode 100644
index 0000000..0aa9473
--- /dev/null
+++ b/index.md
@@ -0,0 +1,41 @@
+---
+layout: default
+---
+
+The [MathML association](/about.html)
+is a charitable organization under the Not-for-Profit Corporation Law of the
+State of New York, with the following goals:
+
+* Native implementation of the MathML language in all Web rendering engines.
+* Development of software tools to let users read, write, search, store and
+ transfer MathML formulas; with particular attention to make them accessible
+ to people with disabilities.
+* Usage of the MathML language to publish educational, technical and scientific
+ content in Web sites, ebooks or Web apps.
+* Other developmental and promotional activities to further the dissemination
+ of mathematical content in Web sites, ebooks or Web apps.
+
+For more details, take a look at our [Manifesto](/legal-documents/manifesto.html).
+
+## Latest Updates
+
+
+
+{% for post in site.posts limit:3 %}
+{% if site.wpm %}
+{% assign readtime = post.content | strip_html | number_of_words | append: '.0' | divided_by:site.wpm %}
+{% else %}
+{% assign readtime = post.content | strip_html | number_of_words | append: '.0' | divided_by:180 %}
+{% endif %}
+{% assign modifiedtime = post.modified | date: "%Y%m%d" %}
+{% assign posttime = post.date | date: "%Y%m%d" %}
+
+
+{{ post.title }}
+
+
+{{ post.date | date: "%d %b %Y" }} {% if post.modified %}{% if modifiedtime != posttime %} and last modified on {{ post.modified | date: "%d %b %Y" }} {% endif %}{% endif %}
+
+{% endfor %}
+
+
diff --git a/legal-documents/affiliates.md b/legal-documents/affiliates.md
new file mode 100644
index 0000000..e91c53d
--- /dev/null
+++ b/legal-documents/affiliates.md
@@ -0,0 +1,140 @@
+---
+layout: page
+title: Affiliates
+---
+
+## General Description
+
+* Individuals, businesses or organizations that seek to support the mission of
+ the MathML Association may become affiliates, after approval by the directors
+ of the MathML Association. At any time and with at least one month notice,
+ they may resign from the status of affiliates, or may have this status removed
+ by decision of the directors of the MathML Association.
+
+* The MathML Association shall inform affiliates about any public decision
+ voted by the directors of the MathML Association. The MathML Association
+ shall highlight changes that may affect agreement with affiliates.
+
+* Affiliates shall adhere to the goals described in the [MathML manifesto](/legal-documents/manifesto.html). They shall
+ engage to conduct their own activities in accordance with these goals.
+
+* Affiliates are not members of the MathML Association and shall continue to
+ act and express in their names. The MathML Association shall not be held
+ responsible for any actions or public statements made by affiliates. The
+ MathML Association shall have authority to refuse or remove the status of
+ affiliate to individuals, businesses or organizations who violated
+ agreement with the MathML Association or the existing legislations.
+
+* Affiliates may get involved in discussions or projects of the MathML
+ Association that aim at reaching the goals of the MathML manifesto.
+ Affiliates shall have no voting rights and shall not directly influence votes
+ made by the directors of the MathML Association.
+
+* Affiliates and MathML Association may exchange information in private or
+ public communication channels. At no time they shall share or sold
+ confidential information to other organizations or groups without mutual
+ consent.
+
+* Affiliates may benefit from transaction or arrangement with the MathML
+ Association. The MathML Association shall ensure that these transaction or
+ arrangement do not violate the [Conflict of Interest policy](/legal-documents/conflict-of-interest-policy.html) of the MathML Association.
+ Affiliates shall be aware of this policy and shall inform the MathML
+ Association of any potential violation in the transaction or arrangement
+ passed with the MathML Association.
+
+## Affiliate Categories
+
+Affiliates shall belong to one of the categories described in the next
+sections with more specific rights, privileges, and obligations.
+
+### MathML Friends
+
+MathML Friends are individuals who must be 18 years of age and are
+nominated as affiliates of the MathML Association for an undetermined
+period. They are invited, but not required, to get involved in the
+realization of the manifesto goals by getting involved in public
+discussions, collaborating on projects related to activities of the
+MathML Association as a volunteer or by making donations to the MathML
+Association. They shall get the following benefits:
+
+- name, brief introduction and optional link displayed on the website of the
+ MathML Association in the list of "MathML Friends"
+- one-sentence introduction on the MathML Association news feed in grouped
+ announcement of new affiliates.
+- opportunity to get nominated as an Advisory Board member
+
+### MathML Sponsors
+
+MathML Sponsors are companies or organizations willing to advance the
+mission of the MathML manifesto by making an annual financial contribution to the
+MathML project. MathML Sponsors are nominated as an affiliate for a
+duration of one year renewable. They shall get the following benefits,
+according to their contribution level:
+
+1. Bronze MathML Sponsor (annual financial contribution: 128$ or more)
+ - use of the term "Bronze MathML Sponsor" in corporate communications
+ - name displayed on the website of the MathML Association in the list of
+ "MathML Sponsors" together with a link to their website
+ - special announcement as a new "MathML Sponsor" on the MathML Association
+ news feed, with a short introduction to their activities
+
+2. Silver MathML Sponsor (annual financial contribution: 512$ or more)
+ - all the benefits of the Bronze Sponsor plus
+ - use of the term "Silver MathML Sponsor" in corporate communications
+ - small logo displayed on the website of the MathML Association in the list
+ of "MathML Sponsors" together with a link to their website
+ - opportunity to send one representative to the Advisory Board
+
+3. Gold MathML Sponsor (annual financial contribution: 1024$ or more)
+ - all the benefits of the Bronze and Silver Sponsors plus
+ - use of the term "Gold MathML Sponsor" in corporate communications
+ - big logo displayed on the website of the MathML Association in the list
+ of "MathML Sponsors" together with a link to their website
+ - opportunity to send a second representative to the Advisory Board
+ - special announcement as a new "MathML Sponsor" on the MathML Association
+ news feed, with a detailed presentation of their activities and how they
+ relate to the achievement of the MathML manifesto
+
+### MathML Partners
+
+MathML Partners are companies or organizations with technical expertise in
+open source development of Web rendering engines or of related
+technlogies. MathML Partners are nominated as an affiliate for an
+undetermined period. They shall get the following benefits:
+
+- personal name (for one-person business) or logo displayed on the list
+ of "MathML Partners" together with a link to their website
+- special announcement as a new "MathML Partner" on the MathML Association
+ news feed, with a short introduction to their activities
+- opportunity to write technical posts on MathML-related topics on the
+ MathML Association news feed
+- privileged interlocutor for technical discussions or contracts on
+ MathML Association projects
+
+## Advisory Board
+
+The Advisory Board is a body made of affiliates of the MathML Association,
+providing non-binding advice to the directors of the MathML Association.
+
+The Advisory Board shall be made of:
+
+* An arbitrary number of "MathML Friends"
+* At most one representative of each "Silver MathML Sponsor"
+* At most two representatives of each "Gold MathML Sponsor"
+* No representatives of "MathML Partners" or "Bronze MathML Sponsor"
+
+The member of the Advisory Board shall be nominated by the directors of the
+MathML Association for a duration of one year. The number of proportion of
+"MathML Friends" should be kept in a way that the Advisory Board provides
+a good balance between "corporate" affiliate and "individual" affiliates.
+
+The Advisory Board shall elect a chair who takes care of the internal
+organization and who communicates with the directors of the MathML Association.
+
+The Advisory Board shall have the following rights and obligations:
+
+* Publically comment on the annual activity report made by the directors of
+ the MathML Association
+* Get informed on new software developments run by the MathML Association
+ and comment on them
+* Get informed on grant applications and comment on them
diff --git a/legal-documents/conflict-of-interest-policy.md b/legal-documents/conflict-of-interest-policy.md
new file mode 100644
index 0000000..7fb0d0f
--- /dev/null
+++ b/legal-documents/conflict-of-interest-policy.md
@@ -0,0 +1,193 @@
+---
+layout: page
+title: Conflict of interest policy
+---
+
+
+
+## ARTICLE I - PURPOSES
+
+It is important for Mondial Association for Tools Handling MathML, Ltd.
+directors, officers, and staff to be aware that both real and apparent
+conflicts of interest or dualities of interest sometimes occur in the course of
+conducting the affairs of the corporation and that the appearance of conflict
+can be troublesome even if there is in fact no conflict whatsoever. Conflicts
+occur because the many persons associated with the corporation should be
+expected to have, and do in fact generally have multiple interests and
+affiliations and various positions of responsibility within the community. In
+these situations a person will sometimes owe identical duties of loyalty to two
+or more corporations. The purpose of the conflict of interest policy is to
+protect the corporation's tax-exempt interest when it is contemplating entering
+into a transaction or arrangement that might benefit the private interest of an
+officer or director of the corporation or might result in a possible excess
+benefit transaction. The policy is intended to supplement but not replace any
+applicable state and federal laws governing conflict of interest applicable to
+nonprofit and charitable organizations.
+
+Conflicts are undesirable because they potentially or eventually place the
+interests of others ahead of the corporation's obligations to its charitable
+purposes and to the public interest. Conflicts are also undesirable because
+they often reflect adversely upon the person involved and upon the institutions
+with which they are affiliated, regardless of the actual facts or motivations
+of the parties. However, the long-range best interests of the corporation do
+not require the termination of all association with persons who may have real
+or apparent conflicts that are harmless to all individuals or entities involved.
+
+Each member of the board of directors and the staff of the corporation has a
+duty of loyalty to the corporation. The duty of loyalty generally requires a
+director or staff member to prefer the interests of the corporation over the
+director's/staff's interest or the interests of others. In addition, directors
+and staff of the corporation shall avoid acts of self-dealing which may
+adversely affect the tax-exempt status of the corporation or cause there to
+arise any sanction or penalty by a governmental authority.
+
+In connection with any actual or possible conflict of interest, an interested
+person must disclose the existence of the financial interest and be given the
+opportunity to disclose all material facts to the directors and members of
+committees with governing board delegated powers considering the proposed
+transaction or arrangement.
+
+## ARTICLE II - DEFINITIONS
+
+### 2.1 Interested Person
+
+Any director, principal officer, or member of a committee with governing board
+delegated powers, who has a direct or indirect financial interest, as defined
+below, is an interested person.
+
+### 2.2 Financial Interest
+
+A person has a financial interest if the person has, directly or indirectly,
+thorough business, investment, or family:
+
+1. An ownership or investment interest in any entity with which the corporation
+ has a transaction or arrangement,
+
+2. A compensation arrangement with the corporation or with any entity or
+ individual with which the corporation has a transaction or arrangement, or
+
+3. A potential ownership or investment interest in, or compensation
+ arrangement with, any entity or individual with which the corporation is
+ negotiating a transaction or arrangement.
+
+Compensation includes direct and indirect remuneration as well as gifts or
+favors that are not insubstantial. A financial interest is not necessarily a
+conflict of interest. Under Article III, Section 2, a person who has a
+financial interest may have a conflict of interest only if the appropriate
+governing board or committee decides that a conflict of interest exists.
+
+## ARTICLE III - PROCEDURES
+
+### 3.1 Duty to Disclose
+
+In connection with any actual or possible conflict of interest, an interested
+person must disclose the existence of the financial interest and be given the
+opportunity to disclose all material facts to the directors and members of
+committees with governing board delegated powers considering the proposed
+transaction or arrangement
+
+### 3.2 Determining Whether a Conflict of Interest Exists
+
+After disclosure of the financial interest and all material facts, and after
+any discussion with the interested person, he/she shall leave the governing
+board or committee meeting while the determination of a conflict of interest is
+discussed and voted upon. The remaining board or committee members shall decide
+if a conflict of interest exists.
+
+### 3.3 Procedures for Addressing the Conflict of Interest
+
+1. An interested person may make a presentation at the governing board or
+ committee meeting, but after the presentation, he/she shall leave the
+ meeting during the discussion of, and the vote on, the transaction or
+ arrangement involving the possible conflict of interest. By no means
+ shall he/she influence improperly the deliberation of that vote.
+
+2. The chairperson of the governing board or committee shall, if appropriate,
+ appoint a disinterested person or committee to investigate alternatives to
+ the proposed transaction or arrangement.
+
+3. After exercising due diligence, the governing board or committee shall
+ determine whether the corporation can obtain with reasonable efforts a more
+ advantageous transaction or arrangement from a person or entity that would
+ not give rise to a conflict of interest.
+
+4. If a more advantageous transaction or arrangement is not reasonably
+ possible under circumstances not producing a conflict of interest, the
+ governing board or committee shall determine by a majority vote of the
+ disinterested directors whether the transaction or arrangement is in the
+ corporation's best interest, for its own benefit, and whether it is fair
+ and reasonable. In conformity with the above determination it shall make
+ its decision as to whether to enter into the transaction or arrangement.
+
+### 3.4 Violations of the Conflicts of Interest Policy
+
+1. If the governing board or committee has reasonable cause to believe a
+ member has failed to disclose actual or possible conflicts of interest, it
+ shall inform the member of the basis for such belief and afford the member
+ an opportunity to explain the alleged failure to disclose.
+
+2. If, after hearing the member's response and after making further
+ investigation as warranted by the circumstances, the governing board or
+ committee determines the member has failed to disclose an actual or
+ possible conflict of interest, it shall take appropriate disciplinary and
+ corrective action.
+
+## ARTICLE IV - RECORDS OF PROCEEDINGS
+
+### 4.1 Minutes
+
+The minutes of the governing board and all committees with board delegated
+powers shall contain:
+
+1. The names of the persons who disclosed or otherwise were found to have a
+ financial interest in connection with an actual or possible conflict of
+ interest, the nature of the financial interest, any action taken to
+ determine whether a conflict of interest was present, and the governing
+ board's or committee's decision as to whether a conflict of interest in
+ fact existed.
+
+2. The names of the persons who were present for discussions and votes
+ relating to the transaction or arrangement, the content of the discussion,
+ including any alternatives to the proposed transaction or arrangement, and
+ a record of any votes taken in connection with the proceedings.
+
+## ARTICLE V - COMPENSATION
+
+1. A voting member of the governing board who receives compensation, directly
+ or indirectly, from the corporation for services is precluded from voting
+ on matters pertaining to that member's compensation.
+
+2. A voting member of any committee whose jurisdiction includes compensation
+ matters and who receives compensation, directly or indirectly, from the
+ corporation for services is precluded from voting on matters pertaining to
+ that member's compensation.
+
+3. No voting member of the governing board or any committee whose
+ jurisdiction includes compensation matters and who receives compensation,
+ directly or indirectly, from the corporation, either individually or
+ collectively, is prohibited from providing information to any committee
+ regarding compensation.
+
+## ARTICLE VI - ANNUAL STATEMENTS
+
+Prior to their initial election or appointment, and annually thereafter,
+directors and officers shall complete, sign and submit to the
+secretary of the corporation a written statement identifying, to the best of
+their knowledge, any potential conflict of interest.
+
+## ARTICLE VII - PERIODIC REVIEWS
+
+The board will, on an ongoing basis, collect information about conflict of
+interests in transactions with the corporation and will act in accordance with
+the conflict of interest policy to remedy or eliminate them.
+
+## ARTICLE VIII - USE OF OUTSIDE EXPERTS
+
+When conducting the periodic reviews as provided for in Article VII, the
+corporation may, but need not, use outside advisors. If outside experts are
+used, their use shall not relieve the governing board of its responsibility for
+ensuring periodic reviews are conducted.
diff --git a/legal-documents/index.md b/legal-documents/index.md
new file mode 100644
index 0000000..3bf8db1
--- /dev/null
+++ b/legal-documents/index.md
@@ -0,0 +1,9 @@
+---
+layout: page
+title: Legal Documents
+---
+
+- [Manifesto (Mission Statement)](manifesto.html)
+- [By laws](non-profit-corporate-by-laws.html)
+- [Conflict of Interest Policy](conflict-of-interest-policy.html)
+- [Affiliates](affiliates.html)
diff --git a/legal-documents/manifesto.md b/legal-documents/manifesto.md
new file mode 100644
index 0000000..5b37d63
--- /dev/null
+++ b/legal-documents/manifesto.md
@@ -0,0 +1,101 @@
+---
+layout: page
+title: The MathML Manifesto (Mission Statement)
+---
+
+#### 0) Preamble
+
+Mathematics is the foundation of modern science, technology, and engineering. Mathematical
+knowledge is complex in structure, rich in presentation, and supported by a globally
+accepted writing system subject to local notational preferences. Mathematical
+communication is well-supported in conventional publishing, but *communication of
+mathematics on the web does not make use of the inherent structure* of mathematical
+knowledge in general and mathematical formulae in particular.
+
+Hence we, mathematical practitioners, educators, tool developers, and MathML enthusiasts
+postulate the following agenda for supporting mathematics more fully on the Web and thus
+*bringing the communication of mathematical knowledge to the new millennium*.
+
+#### 1) Mathematical Language
+
+*Mathematical language* is fundamental for scientific, technical, and educational
+communication. *It must be supported by internet tools with the same consideration as any
+other human language*.
+
+#### 2) Open Standards
+
+In order to guarantee compatibility for data exchange, mathematical rendering and
+authoring tools must rely on *open formats and standards*. When extension or improvements
+are necessary, they must be conducted in a *public standardization process*.
+
+#### 3) Mathematical Formulae
+
+Modern mathematical language relies on *mathematical formulae*, highly structured and
+condensed expressions composed of previously introduced identifiers that are presented in
+a conventionalized non-linear notation.
+
+#### 4) MathML: Mathematical Markup Language
+
+The pertinent open standard for representing the meaning and layout of mathematical
+formulae is the [Mathematical Markup Language (MathML)](http://www.w3.org/TR/MathML/)
+maintained by the [World Wide Web Consortium (W3C)](http://www.w3.org). MathML3
+provides
+
+* a set of layout primitives (*presentation MathML*) for the encoding of the
+ presentational aspect of mathematical formulae as a layout tree, and
+* a set of meaning composition primitives and operators (*content MathML*) for the
+ encoding the meaning of formulae - the operator tree.
+
+These two sublanguages are well-integrated: presentation and meaning can be combined in
+one mixed expression (*parallel MathML markup*) for cross-fertilization and interactive
+presentation.
+
+#### 5) MathML Tool Support
+
+*MathML must be used to encode mathematical formulae on the internet*.
+
+Software applications must use content MathML to *communicate partial results among each
+other without loss of meaning* and generate parallel MathML markup for the *communication
+with humans*. For mathematical web documents (e.g. web pages, electronic mails or
+whitepapers) suitable MathML encodings must be provided in the source code to make them
+*usable by the largest number of tools*.
+
+These tools are not limited to the dominant web browsers alone, they include web crawlers,
+screen readers, content aggregators, and browsers without support for script languages
+such as JavaScript. All tools must be able to process the respective aspects of MathML,
+in particular:
+
+##### 5.1) Layout Engines
+
+Web engines providing visual rendering of documents with complex layout must also support
+native and fast display of MathML formulae, in a way *compatible with the layout, styling
+or dynamic update* that are available to other web content.
+
+##### 5.2) Mathematical Fonts
+
+Fonts for displaying mathematical formulae must be widely available and must
+contain appropriate data so that Web engines can use them to produce good
+mathematical rendering.
+
+##### 5.3) Accessibility
+
+Assistive technologies used to read or edit documents must be able to handle MathML in
+order to make *mathematical formulae accessible to disabled persons* based on the the
+layout & content structure of MathML-encoded formulae.
+
+##### 5.4) Internationalization
+
+Mathematical tools must support the miscellaneous scripts and notations permitted by
+MathML and Unicode in order to take into account the *cultural differences of mathematical
+writing*. This includes supporting non-latin alphabets and bidirectional writing.
+
+##### 5.5) Security and Privacy
+
+Security and Privacy are important features for internet users. MathML must be implemented
+in web engines and assistive technologies without losing these features. Web services for
+mathematical content should also guarantee these features to their users.
+
+##### 5.6) Authoring
+
+Authoring tools must give individuals the opportunity to write and edit the *content & layout
+structure of MathML formulae* or to convert them from other mathematical representations.
diff --git a/legal-documents/non-profit-corporate-by-laws.md b/legal-documents/non-profit-corporate-by-laws.md
new file mode 100644
index 0000000..c46c20b
--- /dev/null
+++ b/legal-documents/non-profit-corporate-by-laws.md
@@ -0,0 +1,874 @@
+---
+layout: page
+title: Non-profit corporate bylaws
+---
+
+
+
+## ARTICLE I - NAME
+
+### 1.01 Name
+
+The name of this corporation shall be Mondial Association for Tools Handling
+MathML, Ltd. The business of the corporation may be conducted as Mondial
+Association for Tools Handling MathML, Ltd. or The MathML Association.
+
+## ARTICLE II - PURPOSES AND POWERS
+
+### 2.01 Purpose
+
+Mondial Association for Tools Handling MathML, Ltd. is a non-profit corporation
+and shall be operated exclusively for educational and charitable purposes
+within the meaning of Section 501 (c)(3) of the Internal Revenue Code of 1986,
+or the corresponding section of any future Federal tax code.
+
+The goals of Mondial Association for Tools Handling MathML, Ltd are:
+
+1. Native implementation of the MathML language in all Web rendering engines.
+
+2. Development of software tools to let users read, write, search, store and
+ transfer MathML formulas; with particular attention to make them accessible
+ to people with disabilities.
+
+3. Usage of the MathML language to publish educational, technical and
+ scientific content in Web sites, ebooks or Web apps.
+
+4. Other developmental and promotional activities to further the dissemination
+ of mathematical content in Web sites, ebooks or Web apps.
+
+### 2.02 Powers
+
+The corporation shall have the power, directly or indirectly, alone or in
+conjunction or cooperation with others, to do any and all lawful acts which may
+be necessary or convenient to affect the charitable purposes, for which the
+corporation is organized, and to aid or assist other organizations or persons
+whose activities further accomplish, foster, or attain such purposes. The
+powers of the corporation may include, but not be limited to, the acceptance of
+contributions from the public and private sectors, whether financial or in-kind
+contributions.
+
+### 2.03 Nonprofit Status and Exempt Activities Limitation.
+
+1. **Nonprofit Legal Status.** Mondial Association for Tools Handling MathML,
+ Ltd. is a charitable organization under the Not-for-Profit Corporation Law
+ of the State of New York, recognized as tax exempt under Section 501(c)(3)
+ of the United States Internal Revenue Code.
+
+2. **Exempt Activities Limitation.** Not withstanding any other provision of
+ these Bylaws, no director, officer, employee, member, or representative of
+ this corporation shall take any action or carry on any activity by or on
+ behalf of the corporation not permitted to be taken or carried on by an
+ organization exempt under Section 501(c)(3) of the Internal Revenue Code as
+ it now exists or may be amended, or by any organization contributions to
+ which are deductible under Section 170(c)(2) of such Code and Regulations
+ as it now exists or may be amended. No part of the net earnings of the
+ corporation shall inure to the benefit or be distributable to any director,
+ officer, member, or other private person, except that the corporation shall
+ be authorized and empowered to pay reasonable compensation for services
+ rendered and to make payments and distributions in furtherance of the
+ purposes set forth in the Articles of Incorporation and these Bylaws.
+
+3. **Distribution Upon Dissolution.** Upon termination or dissolution of the
+ Mondial Association for Tools Handling MathML, Ltd., any assets lawfully
+ available for distribution shall be distributed to one (1) or more
+ qualifying organizations described in Section 501(c)(3) of the 1986
+ Internal Revenue Code (or described in any corresponding provision of any
+ successor statute) which organization or organizations have a charitable
+ purpose which, at least generally, includes a purpose similar to the
+ terminating or dissolving corporation.
+
+ The organization to receive the assets of the Mondial Association for Tools
+ Handling MathML, Ltd. hereunder shall be selected in the discretion of a
+ majority of the managing body of the corporation, and if its members cannot
+ so agree, then the recipient organization shall be selected pursuant to a
+ verified petition in equity filed in a court of proper jurisdiction against
+ the Mondial Association for Tools Handling MathML, Ltd., by one (1) or more
+ of its managing body which verified petition shall contain such statements
+ as reasonably indicate the applicability of this section. The court upon a
+ finding that this section is applicable shall select the qualifying
+ organization or organizations to receive the assets to be distributed,
+ giving preference if practicable to organizations located within the State
+ of New York.
+
+ In the event that the court shall find that this section is applicable but
+ that there is no qualifying organization known to it which has a charitable
+ purpose, which, at least generally, includes a purpose similar to the
+ Mondial Association for Tools Handling MathML, Ltd., then the court shall
+ direct the distribution of its assets lawfully available for distribution
+ to the Treasurer of the State of New York to be added to the general fund.
+
+## ARTICLE III - MEMBERSHIP
+
+### 3.01 No Membership Classes
+
+The corporation shall have no members who have any right to vote or title or
+interest in or to the corporation, its properties and franchises.
+
+### 3.02 Non-Voting Affiliates
+
+The board of directors may approve classes of non-voting affiliates with rights,
+privileges, and obligations established by the board. Affiliates may be
+individuals, businesses, and other organizations that seek to support the
+mission of the corporation. The board, a designated committee of the board, or
+any duly elected officer in accordance with board policy, shall have authority
+to admit any individual or organization as an affiliate, to recognize
+representatives of affiliates, and to make determinations as to affiliates'
+rights, privileges, and obligations. At no time shall affiliate information be
+shared with or sold to other organizations or groups without the affiliate's
+consent. At the discretion of the board of directors, affiliates may be given
+endorsement, recognition and media coverage at fundraising activities,
+other events or at the corporation website. Affiliates have no voting rights,
+and are not members of the corporation.
+
+### 3.03 Dues
+
+Any dues for affiliates shall be determined by the board of directors.
+
+## ARTICLE IV - BOARD OF DIRECTORS
+
+### 4.01 Number of Directors
+
+Mondial Association for Tools Handling MathML, Ltd. shall have a board of
+directors consisting of at least 4 and no more than 15 directors. Within these
+limits, the board may increase or decrease the number of directors serving on
+the board, including for the purpose of staggering the terms of directors.
+
+### 4.02 Powers
+
+All corporate powers shall be exercised by or under the authority of the board
+and the affairs of the Mondial Association for Tools Handling MathML, Ltd.
+Shall be managed under the direction of the board, except as otherwise provided
+by law.
+
+### 4.03 Terms
+
+1. All directors shall be elected to serve a two-year term, however the term
+ may be extended until a successor has been elected.
+
+2. Director terms shall be staggered so that approximately half the number of
+ directors will end their terms in any given year.
+
+2. Directors may serve terms in succession.
+
+3. The term of office shall be considered to begin January 1 and end December
+ 31 of the second year in office, unless the term is extended until such
+ time as a successor has been elected.
+
+### 4.04 Qualifications and Election of Directors
+
+In order to be eligible to serve as a director on the board of directors, the
+individual must be 18 years of age. Directors may be elected at
+any board meeting by the majority vote of the existing board of directors. The
+election of directors to replace those who have fulfilled their term of office
+shall take place in January of each year.
+
+### 4.05 Vacancies
+
+The board of directors may fill vacancies due to the expiration of a director's
+term of office, resignation, death, or removal of a director or may appoint new
+directors to fill a previously unfilled board position, subject to the maximum
+number of directors under these Bylaws.
+
+1. **Unexpected Vacancies.** Vacancies in the board of directors due to
+ resignation, death, or removal shall be filled by the board for the balance
+ of the term of the director being replaced.
+
+### 4.06 Removal of Directors
+
+A director may be removed by two-thirds (2/3) vote of the board of directors
+then in office, if:
+
+1. the director is absent and unexcused from two or more meetings of the board
+ of directors in a twelve month period. The board president is empowered to
+ excuse directors from attendance for a reason deemed adequate by the board
+ president. The president shall not have the power to excuse him/herself
+ from the board meeting attendance and in that case, the board vice president
+ shall excuse the president. Or:
+
+2. for cause or no cause, if before any meeting of the board at which a vote
+ on removal will be made the director in question is given electronic or
+ written notification of the board's intention to discuss her/his case and
+ is given the opportunity to be heard at a meeting of the board.
+
+### 4.07 Board of Directors Meetings.
+
+1. Regular Meetings. The board of directors shall have a minimum of four (4)
+ regular meetings each calendar year at times and places fixed by the board.
+ Board meetings shall be held upon four (4) days notice by first-class mail,
+ electronic mail, or facsimile transmission or forty-eight (48) hours notice
+ delivered personally or by telephone. If sent by mail, facsimile
+ transmission, or electronic mail, the notice shall be deemed to be
+ delivered upon its deposit in the mail or transmission system. Notice of
+ meetings shall specify the place, day, and hour of meeting. The purpose of
+ the meeting need not be specified.
+
+2. Special Meetings. Special meetings of the board may be called by the
+ president, vice president, secretary, treasurer, or any two (2) other
+ directors of the board of directors. A special meeting must be preceded by
+ at least 2 days notice to each director of the date, time, and place, but
+ not the purpose, of the meeting.
+
+3. Waiver of Notice. Any director may waive notice of any meeting, in
+ accordance with New York law.
+
+### 4.08 Manner of Acting.
+
+1. Quorum. A majority of the directors in office immediately before a meeting
+ shall constitute a quorum for the transaction of business at that meeting
+ of the board. No business shall be considered by the board at any meeting
+ at which a quorum is not present.
+
+2. Majority Vote. Except as otherwise required by law or by the articles of
+ incorporation, the act of the majority of the directors present at a
+ meeting at which a quorum is present shall be the act of the board.
+
+3. Hung Board Decisions. On the occasion that directors of the board are
+ unable to make a decision based on a tied number of votes, the president or
+ treasurer in the order of presence shall have the power to swing the vote
+ based on his/her discretion.
+
+4. Participation. Except as required otherwise by law, the Articles of
+ Incorporation, or these Bylaws, directors may participate in a regular or
+ special meeting through the use of any means of communication by which all
+ directors participating may simultaneously communicate with each other
+ during the meeting, including in person, internet video meeting or by
+ telephonic conference call.
+
+### 4.09 Compensation for Board Service
+
+Directors shall receive no compensation for carrying out their duties as
+directors. The board may adopt policies providing for reasonable reimbursement
+of directors for expenses incurred in conjunction with carrying out board
+responsibilities, such as travel expenses to attend board meetings.
+
+### 4.10 Compensation for Professional Services by Directors
+
+Directors are not restricted from being remunerated for professional services
+provided to the corporation. Such remuneration shall be reasonable and fair to
+the corporation and must be reviewed and approved in accordance with the board
+Conflict of Interest policy and state law.
+
+## ARTICLE V - COMMITTEES
+
+### 5.01 Committees
+
+The board of directors may, by the resolution adopted by a majority of the
+directors then in office, designate one or more committees, each consisting of
+two or more directors, to serve at the pleasure of the board. Any committee, to
+the extent provided in the resolution of the board, shall have all the
+authority of the board, except that no committee, regardless of board
+resolution, may:
+
+1. take any final action on matters which also requires board members'
+ approval or approval of a majority of all members;
+
+2. fill vacancies on the board of directors of in any committee which has the
+ authority of the board;
+
+3. amend or repeal Bylaws or adopt new Bylaws;
+
+5. amend or repeal any resolution of the board of directors which by its
+ express terms is not so amendable or repealable;
+
+6. appoint any other committees of the board of directors or the members of
+ these committees;
+
+7. expend corporate funds to support a nominee for director; or
+
+8. approve any transaction;
+
+ 1. to which the corporation is a party and one or more directors have a
+ material financial interest; or
+
+ 2. between the corporation and one or more of its directors or between
+ the corporation or any person in which one or more of its directors have a
+ material financial interest.
+
+### 5.2 Meetings and Action of Committees
+
+Meetings and action of the committees shall be governed by and held and taken
+in accordance with, the provisions of Article IV of these Bylaws concerning
+meetings of the directors, with such changes in the context of those Bylaws as
+are necessary to substitute the committee and its members for the board of
+directors and its members, except that the time for regular meetings of
+committees may be determined either by resolution of the board of directors or
+by resolution of the committee. Special meetings of the committee may also be
+called by resolution of the board of directors. Notice of special meetings of
+committees shall also be given to any and all alternate members, who shall have
+the right to attend all meetings of the committee. Minutes shall be kept of
+each meeting of any committee and shall be filed with the corporate records.
+The board of directors may adopt rules for the governing of the committee not
+inconsistent with the provision of these Bylaws.
+
+### 5.3 Informal Action By The Board of Directors
+
+Any action required or permitted to be taken by the board of directors at a
+meeting may be taken without a meeting if consent in writing, setting forth the
+action so taken, shall be agreed by the consensus of a quorum. For purposes of
+this section an e-mail transmission from an e-mail address on record
+constitutes a valid writing. The intent of this provision is to allow the board
+of directors to use email to approve actions, as long as a quorum of board
+members gives consent.
+
+## ARTICLE VI - OFFICERS
+
+### 6.01 Board Officers
+
+The officers of the corporation shall be a board president, vice-president,
+secretary, and treasurer, all of whom shall be chosen by, and serve at the
+pleasure of, the board of directors. Each board officer shall have the
+authority and shall perform the duties set forth in these Bylaws or by
+resolution of the board or by direction of an officer authorized by the board
+to prescribe the duties and authority of other officers. The board may also
+appoint additional vice-presidents and such other officers as it deems
+expedient for the proper conduct of the business of the corporation, each of
+whom shall have such authority and shall perform such duties as the board of
+directors may determine. One person may hold two or more board offices, but no
+board officer may act in more than one capacity where action of two or more
+officers is required.
+
+### 6.02 Term of Office
+
+Each officer shall serve a one-year term of office and may not serve more than
+three (3) consecutive terms of office. Unless unanimously elected by the board
+at the end of his/her three (3) year terms or to fill a vacancy in an officer
+position, each board officer's term of office shall begin upon the adjournment
+of the board meeting at which elected and shall end upon the adjournment of the
+board meeting during which a successor is elected.
+
+### 6.03 Removal and Resignation
+
+The board of directors may remove an officer at any time, with or without
+cause. Any officer may resign at any time by giving written notice to the
+corporation without prejudice to the rights, if any, of the corporation under
+any contract to which the officer is a party. Any resignation shall take effect
+at the date of the receipt of the notice or at any later time specified in the
+notice, unless otherwise specified in the notice. The acceptance of the
+resignation shall not be necessary to make it effective.
+
+### 6.04 Board President
+
+The board president shall be the chief volunteer officer of the corporation.
+The board president shall lead the board of directors in performing its duties
+and responsibilities, including, if present, presiding at all meetings of the
+board of directors, and shall perform all other duties incident to the office
+or properly required by the board of directors.
+
+### 6.05 Vice President
+
+In the absence or disability of the board president, the ranking vice-president
+or vice-president designated by the board of directors shall perform the duties
+of the board president. When so acting, the vice-president shall have all the
+powers of and be subject to all the restrictions upon the board president. The
+vice-president shall have such other powers and perform such other duties
+prescribed for them by the board of directors or the board president. The
+vice-president shall normally accede to the office of board president upon the
+completion of the board president's term of office.
+
+### 6.06 Secretary
+
+The secretary shall keep or cause to be kept a book of minutes of all meetings
+and actions of directors and committees of directors. The minutes of each
+meeting shall state the time and place that it was held and such other
+information as shall be necessary to determine the actions taken and whether
+the meeting was held in accordance with the law and these Bylaws. The secretary
+shall cause notice to be given of all meetings of directors and committees as
+required by the Bylaws. The secretary shall have such other powers and perform
+such other duties as may be prescribed by the board of directors or the board
+president. The secretary may appoint, with approval of the board, a director
+to assist in performance of all or part of the duties of the secretary.
+
+### 6.07 Treasurer
+
+The treasurer shall be the lead director for oversight of the financial
+condition and affairs of the corporation. The treasurer shall oversee and keep
+the board informed of the financial condition of the corporation and of audit
+or financial review results. In conjunction with other directors or officers,
+the treasurer shall oversee budget preparation and shall ensure that
+appropriate financial reports, including an account of major transactions and
+the financial condition of the corporation, are made available to the board of
+directors on a timely basis or as may be required by the board of directors.
+The treasurer shall perform all duties properly required by the board of
+directors or the board president. The treasurer may appoint, with approval of
+the board a qualified fiscal agent or member of the staff to assist in
+performance of all or part of the duties of the treasurer.
+
+### 6.08 Non-Director Officers
+
+The board of directors may designate additional officer positions of the
+corporation and may appoint and assign duties to other non-director officers of
+the corporation.
+
+## ARTICLE VII - CONTRACTS, CHECKS, LOANS, INDEMNIFICATION AND RELATED MATTERS
+
+### 7.01 Contracts and other Writings
+
+Except as otherwise provided by resolution of the board or board policy, all
+contracts, deeds, leases, mortgages, grants, and other agreements of the
+corporation shall be executed on its behalf by the treasurer or other persons
+to whom the corporation has delegated authority to execute such documents in
+accordance with policies approved by the board.
+
+### 7.02 Checks, Drafts
+
+All checks, drafts, or other orders for payment of money, notes, or other
+evidence of indebtedness issued in the name of the corporation, shall be signed
+by such officer or officers, agent or agents, of the corporation and in such
+manner as shall from time to time be determined by resolution of the board.
+
+### 7.03 Deposits
+
+All funds of the corporation not otherwise employed shall be deposited from
+time to time to the credit of the corporation in such banks, trust companies,
+or other depository as the board or a designated committee of the board may
+select.
+
+### 7.04 Loans
+
+No loans shall be contracted on behalf of the corporation and no evidence of
+indebtedness shall be issued in its name unless authorized by resolution of the
+board. Such authority may be general or confined to specific instances.
+
+### 7.05 Indemnification
+
+1. Mandatory Indemnification. The corporation shall indemnify a director or
+ former director, who was wholly successful, on the merits or otherwise, in
+ the defense of any proceeding to which he or she was a party because he or
+ she is or was a director of the corporation against reasonable expenses
+ incurred by him or her in connection with the proceedings.
+
+2. Permissible Indemnification. The corporation shall indemnify a director or
+ former director made a party to a proceeding because he or she is or was a
+ director of the corporation, against liability incurred in the proceeding,
+ if the determination to indemnify him or her has been made in the manner
+ prescribed by the law and payment has been authorized in the manner
+ prescribed by law.
+
+3. Advance for Expenses. Expenses incurred in defending a civil or criminal
+ action, suit or proceeding may be paid by the corporation in advance of the
+ final disposition of such action, suit or proceeding, as authorized by the
+ board of directors in the specific case, upon receipt of (I) a written
+ affirmation from the director, officer, employee or agent of his or her
+ good faith belief that he or she is entitled to indemnification as
+ authorized in this article, and (II) an undertaking by or on behalf of the
+ director, officer, employee or agent to repay such amount, unless it shall
+ ultimately be determined that he or she is entitled to be indemnified by
+ the corporation in these Bylaws.
+
+4. Indemnification of Officers, Agents and Employees. An officer of the
+ corporation who is not a director is entitled to mandatory indemnification
+ under this article to the same extent as a director. The corporation may
+ also indemnify and advance expenses to an employee or agent of the
+ corporation who is not a director, consistent with New York Law and public
+ policy, provided that such indemnification, and the scope of such
+ indemnification, is set forth by the general or specific action of the
+ board or by contract.
+
+## ARTICLE VIII - MISCELLANEOUS
+
+### 8.01 Books and Records
+
+The corporation shall keep correct and complete books and records of account
+and shall keep minutes of the proceedings of all meetings of its board of
+directors, a record of all actions taken by board of directors without a
+meeting, and a record of all actions taken by committees of the board. In
+addition, the corporation shall keep a copy of the corporation's Articles of
+Incorporation and Bylaws as amended to date.
+
+### 8.02 Fiscal Year
+
+The fiscal year of the corporation shall be from February 1 to January 31 of
+each year.
+
+### 8.03 Conflict of Interest
+
+The board shall adopt and periodically review a conflict of interest policy to
+protect the corporation's interest when it is contemplating any transaction or
+arrangement which may benefit any director, officer, employee, affiliate, or
+member of a committee with board-delegated powers.
+
+### 8.04 Nondiscrimination Policy
+
+The officers, directors, committee members, employees, and persons served by
+this corporation shall be selected entirely on a nondiscriminatory basis with
+respect to age, sex, race, religion, national origin, and sexual orientation.
+It is the policy of Mondial Association for Tools Handling MathML, Ltd. not to
+discriminate on the basis of race, creed, ancestry, marital status, gender,
+sexual orientation, age, physical disability, veteran's status, political
+service or affiliation, color, religion, or national origin.
+
+### 8.05 Bylaw Amendment
+
+These Bylaws may be amended, altered, repealed, or restated by a vote of the
+majority of the board of directors then in office at a meeting of the Board,
+provided, however,
+
+1. that no amendment shall be made to these Bylaws which would cause the
+ corporation to cease to qualify as an exempt corporation under
+ Section 501 (c)(3) of the Internal Revenue Code of 1986, or the
+ corresponding section of any future Federal tax code; and,
+
+2. that an amendment does not affect the voting rights of directors. An
+ amendment that does affect the voting rights of directors further requires
+ ratification by a two-thirds (2/3) vote of a quorum of directors at a Board
+ meeting.
+
+3. that all amendments be consistent with the Articles of Incorporation.
+
+## ARTICLE IX - COUNTERTERRORISM AND DUE DILIGENCE POLICY
+
+In furtherance of its exemption by contributions to other organizations,
+domestic or foreign, Mondial Association for Tools Handling MathML, Ltd. shall
+stipulate how the funds will be used and shall require the recipient to provide
+the corporation with detailed records and financial proof of how the funds were
+utilized.
+
+Although adherence and compliance with the US Department of the Treasury's
+publication the "Voluntary Best Practice for US. Based Charities" is not
+mandatory, Mondial Association for Tools Handling MathML, Ltd. willfully and
+voluntarily recognizes and puts to practice these guidelines and suggestions
+to reduce, develop, re-evaluate and strengthen a risk-based approach to guard
+against the threat of diversion of charitable funds or exploitation of
+charitable activity by terrorist organizations and their support networks.
+
+Mondial Association for Tools Handling MathML, Ltd. shall also comply and put
+into practice the federal guidelines, suggestion, laws and limitation set forth
+by pre-existing U.S. legal requirements related to combating terrorist
+financing, which include, but are not limited to, various sanctions programs
+administered by the Office of Foreign Assets Control (OFAC) in regard to its
+foreign activities.
+
+## ARTICLE X - PRIVACY AND DOCUMENT RETENTION POLICY
+
+### 10.01 Purpose
+
+The purpose of this privacy and document retention policy is establishing
+standards for document integrity, retention, and destruction and to promote the
+proper treatment of Mondial Association for Tools Handling MathML, Ltd. records.
+It also specifies how Personally Identifiable Information shall be handled.
+
+### 10.02 Policy
+
+#### Section 1. General Guidelines.
+
+Records should not be kept if they are no longer needed for the operation of
+the business or required by law. Unnecessary records should be eliminated from
+the files. The cost of maintaining records is an expense which can grow
+unreasonably if good housekeeping is not performed. A mass of records also
+makes it more difficult to find pertinent records.
+
+From time to time, Mondial Association for Tools Handling MathML, Ltd. may
+establish retention or destruction policies or schedules for specific
+categories of records in order to ensure legal compliance, and also to
+accomplish other objectives, such as preserving intellectual property and cost
+management. Several categories of documents that warrant special consideration
+are identified below. While minimum retention periods are established, the
+retention of the documents identified below and of documents not included in
+the identified categories should be determined primarily by the application of
+the general guidelines affecting document retention, as well as the exception
+for litigation relevant documents and any other pertinent factors.
+
+#### Section 2. Exception for Litigation Relevant Documents.
+Mondial Association for Tools Handling MathML, Ltd. expects all officers,
+directors, and employees to comply fully with any published records retention
+or destruction policies and schedules, provided that all officers, directors,
+and employees should note the following general exception to any stated
+destruction schedule: If you believe, or the Mondial Association for Tools
+Handling MathML, Ltd. informs you, that corporate records are relevant to
+litigation, or potential litigation (i.e. a dispute that could result in
+litigation), then you must preserve those records until it is determined that
+the records are no longer needed. That exception supersedes any previously or
+subsequently established destruction schedule for those records.
+
+#### Section 3. Minimum Retention Periods for Specific Categories
+
+1. Corporate Documents. Corporate records include the corporation's Articles
+ of Incorporation, By-Laws and IRS Form 1023 and Application for Exemption.
+ Corporate records should be retained permanently. IRS regulations require
+ that the Form 1023 be available for public inspection upon request.
+
+2. Tax Records. Tax records include, but may not be limited to, documents
+ concerning payroll, expenses, proof of contributions made by donors,
+ accounting procedures, and other documents concerning the corporation's
+ revenues. Tax records should be retained for at least seven years from the
+ date of filing the applicable return.
+
+3. Employment Records/Personnel Records. State and federal statutes require
+ the corporation to keep certain recruitment, employment and personnel
+ information. The corporation should also keep personnel files that reflect
+ performance reviews and any complaints brought against the corporation or
+ individual employees under applicable state and federal statutes. The
+ corporation should also keep in the employee's personnel file all final
+ memoranda and correspondence reflecting performance reviews and actions
+ taken by or against personnel. Employment applications should be retained
+ for three years. Retirement and pension records should be kept permanently.
+ Other employment and personnel records should be retained for seven years.
+
+4. Board and Board Committee Materials. Meeting minutes should be retained in
+ perpetuity in one or more secure, digital repositories posted publicly or
+ known to the secretary. A clean copy of all other
+ Board and Board Committee materials should be kept for no less than three
+ years by the corporation.
+
+5. Press Releases/Public Filings. The corporation should retain permanent
+ copies of all press releases and publicly filed documents under the theory
+ that the corporation should have its own copy to test the accuracy of any
+ document a member of the public can theoretically produce against the
+ corporation.
+
+6. Legal Files. Legal counsel should be consulted to determine the retention
+ period of particular documents, but legal documents should generally be
+ maintained for a period of ten years.
+
+7. Marketing and Sales Documents. The corporation should keep final copies of
+ marketing and sales documents for the same period of time it keeps other
+ corporate files, generally three years. An exception to the three-year
+ policy may be sales invoices, contracts, leases, licenses, and other legal
+ documentation. These documents should be kept for at least three years
+ beyond the life of the agreement.
+
+8. Development/Intellectual Property and Trade Secrets. Development documents
+ are often subject to intellectual property protection in their final form
+ (e.g., patents and copyrights). The documents detailing the development
+ process are often also of value to the corporation and are protected as a
+ trade secret where the corporation:
+
+ 1. derives independent economic value from the secrecy of the information; and
+
+ 2. has taken affirmative steps to keep the information confidential.
+
+ The corporation should keep all documents designated as containing trade secret information for at least the life of the trade secret.
+
+9. Contracts. Final, execution copies of all contracts entered into by the
+ corporation should be retained. The corporation should retain copies of the
+ final contracts for at least three years beyond the life of the agreement,
+ and longer in the case of publicly filed contracts.
+
+10. Correspondence. Unless correspondence falls under another category listed
+ elsewhere in this policy, correspondence should generally be saved for two
+ years.
+
+11. Banking and Accounting. Accounts payable ledgers and schedules should be
+ kept for seven years. Bank reconciliations, bank statements, deposit slips
+ and checks (unless for important payments and purchases) should be kept for
+ three years. Any inventories of products, materials, and supplies and any
+ invoices should be kept for seven years.
+
+12. Insurance. Expired insurance policies, insurance records, accident reports,
+ claims, etc. should be kept permanently.
+
+13. Audit Records. External audit reports should be kept permanently. Internal
+ audit reports should be kept for three years.
+
+#### Section 4. Electronic Mail.
+
+E-mail that needs to be saved should be either:
+
+1. printed in hard copy and kept in the appropriate file; or
+
+2. downloaded to a computer file and kept electronically or on disk as a
+ separate file. The retention period depends upon the subject matter of the
+ e-mail, as covered elsewhere in this policy.
+
+#### Section 5. Personally Identifiable Information
+
+Personally Identifiable Information of donors, officers or affiliates should be
+kept in a secure (encrypted or otherwise) data store and shall not be made
+available to any person outside the corporation except the authorized
+governmental agencies. However, these restrictions do not apply to any
+Personally Identifiable Information whose owner granted
+Mondial Association for Tools Handling MathML, Ltd. the right to make it public.
+
+## ARTICLE XI - Transparency and Accountability, Disclosure of Financial Information With The General Public
+
+### 11.01 Purpose
+
+By making full and accurate information about its mission, activities, finances,
+and governance publicly available, Mondial Association for Tools Handling
+MathML, Ltd. practices and encourages transparency and accountability to the
+general public. This policy will:
+
+1. indicate which documents and materials produced by the corporation are
+ presumptively open to staff and/or the public
+
+2. indicate which documents and materials produced by the corporation are
+ presumptively closed to staff and/or the public
+
+3. specify the procedures whereby the open/closed status of documents and
+ materials can be altered.
+
+The details of this policy are as follow:
+
+### 11.02 Financial and IRS documents (The form 1023 and the form 990)
+
+Mondial Association for Tools Handling MathML, Ltd. shall provide its Internal
+Revenue forms 990, 990-T, 1023 and 5227, bylaws, conflict of interest policy,
+and financial statements to the general public for inspection free of charge.
+
+### 11.03 Means and Conditions of Disclosure
+
+Mondial Association for Tools Handling MathML, Ltd. shall make
+"Widely Available" the aforementioned documents on its internet website:
+www.mathml-association.org to be viewed and inspected by the general public.
+
+1. The documents shall be posted in a format that allows an individual using
+ the Internet to access, download, view and print them in a manner that
+ exactly reproduces the image of the original document filed with the IRS
+ (except information exempt from public disclosure requirements, such as
+ contributor lists).
+
+2. The website shall clearly inform readers that the document is available and
+ provide instructions for downloading it.
+
+3. Mondial Association for Tools Handling MathML, Ltd. shall not charge a fee
+ for downloading the information. Documents shall not be posted in a format
+ that would require special computer hardware or software (other than
+ software readily available to the public free of charge).
+
+4. Mondial Association for Tools Handling MathML, Ltd. shall inform anyone
+ requesting the information where this information can be found, including
+ the web address. This information must be provided immediately for
+ in-person requests and within 7 days for mailed requests.
+
+### 11.04 IRS Annual Information Returns (Form 990)
+
+Mondial Association for Tools Handling MathML, Ltd. shall submit the Form 990
+to its board of directors prior to the filing of the Form 990. While neither
+the approval of the Form 990 or a review of the 990 is required under Federal
+law, the corporation's Form 990 shall be submitted to each member of the board
+of director's via (hard copy or email) at least 10 days before the Form 990 is
+filed with the IRS.
+
+### 11.05 Board
+
+1. All board deliberations shall be open to the public except where the board
+ passes a motion to make any specific portion confidential.
+
+2. All board minutes shall be open to the public one week after the meeting,
+ except where the board passes a motion to make any specific portion
+ confidential.
+
+3. All papers and materials considered by the board shall be open to the
+ public following the meeting at which they are considered, except where the
+ board passes a motion to make any specific paper or material confidential.
+
+4. Attendance to all board meetings shall be opened to the public, except
+ where the board passes a motion to make any board meeting confidential.
+
+### 11.06 Staff Records
+
+1. All staff records shall be available for consultation by the staff member
+ concerned or by their legal representatives.
+
+2. No staff records shall be made available to any person outside the
+ corporation except the authorized governmental agencies.
+
+3. Within the corporation, staff records shall be made available only to those
+ persons with managerial or personnel responsibilities for that staff member,
+ except that
+
+4. Staff records shall be made available to the board when requested.
+
+### 11.07 Donor Records
+
+1. All donor records shall be available for consultation by the members and
+ donors concerned or by their legal representatives.
+
+2. No donor records shall be made available to any other person outside the
+ corporation except the authorized governmental agencies.
+
+3. Within the corporation, donor records shall be made available only to those
+ persons with managerial or personnel responsibilities for dealing with
+ those donors, except that ;
+
+4. donor records shall be made available to the board when requested.
+
+## ARTICLE XII - CODE OF ETHICS AND WHISTLEBLOWER POLICY
+
+### 12.01 Purpose
+
+Mondial Association for Tools Handling MathML, Ltd. requires and encourages
+directors, officers and employees to observe and practice high standards of
+business and personal ethics in the conduct of their duties and
+responsibilities. The employees and representatives of the corporation must
+practice honesty and integrity in fulfilling their responsibilities and comply
+with all applicable laws and regulations. It is the intent of Mondial
+Association for Tools Handling MathML, Ltd. to adhere to all laws and
+regulations that apply to the corporation and the underlying purpose of this
+policy is to support the corporation's goal of legal compliance. The support of
+all corporate staff is necessary to achieving compliance with various laws and
+regulations.
+
+### 12.02 Reporting Violations
+
+If any director, officer, staff or employee reasonably believes that some
+policy, practice, or activity of Mondial Association for Tools Handling MathML,
+Ltd. is in violation of law, a written complaint must be filed by that person
+with the vice president or the board president.
+
+### 12.03 Acting in Good Faith
+
+Anyone filing a complaint concerning a violation or suspected violation of the
+this Code of ARTICLE XII must be acting in good faith and have reasonable
+grounds for believing the information disclosed indicates such violation.
+Any allegations that
+prove not to be substantiated and which prove to have been made maliciously or
+knowingly to be false shall be viewed as a serious disciplinary offense.
+
+### 12.04 Retaliation
+
+Said person is protected from retaliation only if she/he brings the alleged
+unlawful activity, policy, or practice to the attention of Mondial Association
+for Tools Handling MathML, Ltd. and provides the Mondial Association for Tools
+Handling MathML, Ltd. with a reasonable opportunity to investigate and correct
+the alleged unlawful activity. The protection described below is only available
+to individuals that comply with this requirement.
+
+Mondial Association for Tools Handling MathML, Ltd. shall not retaliate against
+any director, officer, staff or employee who in good faith, has made a protest
+or raised a complaint against some practice of Mondial Association for Tools
+Handling MathML, Ltd. or of another individual or entity with whom Mondial
+Association for Tools Handling MathML, Ltd. has a business relationship, on the
+basis of a reasonable belief that the practice is in violation of law, or a
+clear mandate of public policy.
+
+Mondial Association for Tools Handling MathML, Ltd. shall not retaliate against
+any director, officer, staff or employee who disclose or threaten to disclose
+to a supervisor or a public body, any activity, policy, or practice of Mondial
+Association for Tools Handling MathML, Ltd. that the individual reasonably
+believes is in violation of a law, or a rule, or regulation mandated pursuant
+to law or is in violation of a clear mandate of public policy concerning the
+health, safety, welfare, or protection of the environment.
+
+### 12.05 Confidentiality
+
+Violations or suspected violations may be submitted on a confidential basis by
+the complainant or may be submitted anonymously. Reports of violations or
+suspected violations shall be kept confidential to the extent possible,
+consistent with the need to conduct an adequate investigation.
+
+### 12.06 Handling of Reported Violations
+
+The board president or vice president shall notify the sender and acknowledge
+receipt of the reported violation or suspected violation within five business
+days. All reports shall be promptly investigated by the board and its appointed
+committee and appropriate corrective action shall be taken if warranted by the
+investigation.
+
+This policy shall be made available to all directors, officers, staffs or
+employees and they shall have the opportunity to ask questions about the policy.
+
+## ARTICLE XIII - AMENDMENT OF Articles of Incorporation
+
+### 13.01 Amendment
+
+Any amendment to the Articles of Incorporation may be adopted by approval of
+two-thirds (2/3) of the board of directors.
diff --git a/logo/.gitignore b/logo/.gitignore
new file mode 100644
index 0000000..55c5926
--- /dev/null
+++ b/logo/.gitignore
@@ -0,0 +1,14 @@
+*-inline-style.svg
+*-text-as-path.svg
+*.eps
+*.otf
+*.pdf
+*.png
+*.woff
+Makefile
+autom4te.cache
+config.log
+config.status
+latinmodern-math.zip
+mathml-logos.zip
+texgyreheros.zip
diff --git a/logo/Makefile.in b/logo/Makefile.in
new file mode 100644
index 0000000..7515cd0
--- /dev/null
+++ b/logo/Makefile.in
@@ -0,0 +1,94 @@
+#!gmake
+# This Source Code Form is subject to the terms of the Mozilla Public
+# License, v. 2.0. If a copy of the MPL was not distributed with this
+# file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+LATIN_MODERN_MATH_URI=http://www.gust.org.pl/projects/e-foundry/lm-math/download/latinmodern-math-1959.zip
+TEX_GYRE_HEROS_URI=http://www.gust.org.pl/projects/e-foundry/tex-gyre/heros/qhv2.004otf.zip
+
+all: mathml-logos.zip \
+ webfonts/latinmodern-math.woff webfonts/texgyreheros-regular.woff
+
+mathml-logos.zip: manifest.txt \
+ mathml-logo-240x75.png \
+ mathml-logo-320x100.png \
+ mathml-logo-640x200.png \
+ mathml-logo-text-as-path.svg \
+ mathml-logo.eps \
+ mathml-logo.pdf \
+ mathml-logo.svg \
+ mathml-square-logo-128.png \
+ mathml-square-logo-256.png \
+ mathml-square-logo-500.png \
+ mathml-square-logo-64.png \
+ mathml-square-logo-text-as-path.svg \
+ mathml-square-logo.eps \
+ mathml-square-logo.pdf \
+ mathml-square-logo.svg
+ @ZIP@ $@ $^
+
+%-inline-style.svg: convert-to-inline-style.xsl %.svg
+ @XSLTPROC@ $^ > $@
+
+mathml-logo-640x200.png: mathml-logo-inline-style.svg
+ @INKSCAPE@ -f $< -C -T -y 0.0 -w 640 -e $@
+
+mathml-logo-320x100.png: mathml-logo-inline-style.svg
+ @INKSCAPE@ -f $< -C -T -y 0.0 -w 320 -e $@
+
+mathml-logo-240x75.png: mathml-logo-inline-style.svg
+ @INKSCAPE@ -f $< -C -T -y 0.0 -w 240 -e $@
+
+mathml-square-logo-500.png: mathml-square-logo-inline-style.svg
+ @INKSCAPE@ -f $< -C -T -y 0.0 -w 500 -e $@
+
+mathml-square-logo-256.png: mathml-square-logo-inline-style.svg
+ @INKSCAPE@ -f $< -C -T -y 0.0 -w 256 -e $@
+
+mathml-square-logo-128.png: mathml-square-logo-inline-style.svg
+ @INKSCAPE@ -f $< -C -T -y 0.0 -w 128 -e $@
+
+mathml-square-logo-64.png: mathml-square-logo-inline-style.svg
+ @INKSCAPE@ -f $< -C -T -y 0.0 -w 64 -e $@
+
+%.pdf: %-inline-style.svg
+ @INKSCAPE@ -f $< -C -T -y 0.0 -E $@
+
+%.eps: %-inline-style.svg
+ @INKSCAPE@ -f $< -C -T -y 0.0 -A $@
+
+%-text-as-path.svg: %-inline-style.svg remove-inline-style.xsl
+ @INKSCAPE@ -f $< -C -T -y 0.0 -l $@-tmp-1
+ @XSLTPROC@ remove-inline-style.xsl $@-tmp-1 > $@-tmp-2
+ @SCOUR@ -i $@-tmp-2 -o $@ \
+ --enable-comment-stripping \
+ --enable-id-stripping
+ rm $@-tmp-1 $@-tmp-2
+ touch $@
+
+latinmodern-math.zip:
+ @WGET@ $(LATIN_MODERN_MATH_URI) -O $@
+ touch $@
+
+texgyreheros.zip:
+ @WGET@ $(TEX_GYRE_HEROS_URI) -O $@
+ touch $@
+
+webfonts/latinmodern-math.otf: latinmodern-math.zip
+ @UNZIP@ -j $< latinmodern-math-1959/otf/latinmodern-math.otf -d webfonts
+ touch $@
+
+webfonts/texgyreheros-regular.otf: texgyreheros.zip
+ @UNZIP@ -j $< texgyreheros-regular.otf -d webfonts
+ touch $@
+
+webfonts/%.woff: webfonts/%.otf
+ @SFNT2WOFF@ $<
+
+clean:
+ rm -f *.eps *.png *.pdf webfonts/*.woff webfonts/*.otf \
+ *-text-as-path.svg \
+ *-inline-style.svg
+
+distclean: clean
+ rm -rf *.zip autom4te.cache config.log config.status Makefile
diff --git a/logo/README.md b/logo/README.md
new file mode 100644
index 0000000..62892d3
--- /dev/null
+++ b/logo/README.md
@@ -0,0 +1,36 @@
+# MathML logo
+
+This directory contains the scripts to generate various logos of the MathML
+Association.
+
+# Licenses
+
+Unless stated otherwise, all the scripts and associated files are distributed
+under the [MPL 2.0](https://www.mozilla.org/MPL/2.0/).
+
+The configure script is free software; the Free Software Foundation
+gives unlimited permission to copy, distribute and modify it.
+
+The scripts download the [Latin Modern Math](http://www.gust.org.pl/projects/e-foundry/lm-math) and [TeX Gyre Heros](http://www.gust.org.pl/projects/e-foundry/tex-gyre/heros) fonts and bundle them into WOFF files without any modification.
+These fonts are distributed under the [LPPL with renaming requirements](http://www.gust.org.pl/projects/e-foundry/licenses/GUST-FONT-LICENSE.txt/view). Please
+read the font metadata for details.
+
+The files packaged in the ZIP archive and listed in manifest.txt are distributed
+under the LaTeX Project Public License.
+
+# Build instructions
+
+You need an UNIX environment with
+[make](https://www.gnu.org/software/make/),
+[unzip](http://www.info-zip.org/UnZip.html),
+[wget](https://www.gnu.org/software/wget/),
+[inkscape](https://inkscape.org/),
+[xsltproc](http://xmlsoft.org/XSLT/),
+[zip](http://www.info-zip.org/Zip.html),
+[scour](http://codedread.com/scour/) and
+[sfnt2woff](https://people.mozilla.org/~jkew/woff/). You must also install
+Latin Modern Math and TeX Gyre Heros locally, since Web fonts are not supported
+by inkscape. To build everything, do:
+
+ ./configure
+ make all
diff --git a/logo/configure b/logo/configure
new file mode 100755
index 0000000..52ff0dc
--- /dev/null
+++ b/logo/configure
@@ -0,0 +1,3135 @@
+#! /bin/sh
+# Guess values for system-dependent variables and create Makefiles.
+# Generated by GNU Autoconf 2.69 for MathML Logo 1.0.
+#
+#
+# Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
+#
+#
+# This configure script is free software; the Free Software Foundation
+# gives unlimited permission to copy, distribute and modify it.
+## -------------------- ##
+## M4sh Initialization. ##
+## -------------------- ##
+
+# Be more Bourne compatible
+DUALCASE=1; export DUALCASE # for MKS sh
+if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then :
+ emulate sh
+ NULLCMD=:
+ # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
+ # is contrary to our usage. Disable this feature.
+ alias -g '${1+"$@"}'='"$@"'
+ setopt NO_GLOB_SUBST
+else
+ case `(set -o) 2>/dev/null` in #(
+ *posix*) :
+ set -o posix ;; #(
+ *) :
+ ;;
+esac
+fi
+
+
+as_nl='
+'
+export as_nl
+# Printing a long string crashes Solaris 7 /usr/bin/printf.
+as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
+as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
+as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
+# Prefer a ksh shell builtin over an external printf program on Solaris,
+# but without wasting forks for bash or zsh.
+if test -z "$BASH_VERSION$ZSH_VERSION" \
+ && (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
+ as_echo='print -r --'
+ as_echo_n='print -rn --'
+elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
+ as_echo='printf %s\n'
+ as_echo_n='printf %s'
+else
+ if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
+ as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
+ as_echo_n='/usr/ucb/echo -n'
+ else
+ as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
+ as_echo_n_body='eval
+ arg=$1;
+ case $arg in #(
+ *"$as_nl"*)
+ expr "X$arg" : "X\\(.*\\)$as_nl";
+ arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
+ esac;
+ expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
+ '
+ export as_echo_n_body
+ as_echo_n='sh -c $as_echo_n_body as_echo'
+ fi
+ export as_echo_body
+ as_echo='sh -c $as_echo_body as_echo'
+fi
+
+# The user is always right.
+if test "${PATH_SEPARATOR+set}" != set; then
+ PATH_SEPARATOR=:
+ (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
+ (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
+ PATH_SEPARATOR=';'
+ }
+fi
+
+
+# IFS
+# We need space, tab and new line, in precisely that order. Quoting is
+# there to prevent editors from complaining about space-tab.
+# (If _AS_PATH_WALK were called with IFS unset, it would disable word
+# splitting by setting IFS to empty value.)
+IFS=" "" $as_nl"
+
+# Find who we are. Look in the path if we contain no directory separator.
+as_myself=
+case $0 in #((
+ *[\\/]* ) as_myself=$0 ;;
+ *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
+ done
+IFS=$as_save_IFS
+
+ ;;
+esac
+# We did not find ourselves, most probably we were run as `sh COMMAND'
+# in which case we are not to be found in the path.
+if test "x$as_myself" = x; then
+ as_myself=$0
+fi
+if test ! -f "$as_myself"; then
+ $as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
+ exit 1
+fi
+
+# Unset variables that we do not need and which cause bugs (e.g. in
+# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1"
+# suppresses any "Segmentation fault" message there. '((' could
+# trigger a bug in pdksh 5.2.14.
+for as_var in BASH_ENV ENV MAIL MAILPATH
+do eval test x\${$as_var+set} = xset \
+ && ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || :
+done
+PS1='$ '
+PS2='> '
+PS4='+ '
+
+# NLS nuisances.
+LC_ALL=C
+export LC_ALL
+LANGUAGE=C
+export LANGUAGE
+
+# CDPATH.
+(unset CDPATH) >/dev/null 2>&1 && unset CDPATH
+
+# Use a proper internal environment variable to ensure we don't fall
+ # into an infinite loop, continuously re-executing ourselves.
+ if test x"${_as_can_reexec}" != xno && test "x$CONFIG_SHELL" != x; then
+ _as_can_reexec=no; export _as_can_reexec;
+ # We cannot yet assume a decent shell, so we have to provide a
+# neutralization value for shells without unset; and this also
+# works around shells that cannot unset nonexistent variables.
+# Preserve -v and -x to the replacement shell.
+BASH_ENV=/dev/null
+ENV=/dev/null
+(unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV
+case $- in # ((((
+ *v*x* | *x*v* ) as_opts=-vx ;;
+ *v* ) as_opts=-v ;;
+ *x* ) as_opts=-x ;;
+ * ) as_opts= ;;
+esac
+exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"}
+# Admittedly, this is quite paranoid, since all the known shells bail
+# out after a failed `exec'.
+$as_echo "$0: could not re-execute with $CONFIG_SHELL" >&2
+as_fn_exit 255
+ fi
+ # We don't want this to propagate to other subprocesses.
+ { _as_can_reexec=; unset _as_can_reexec;}
+if test "x$CONFIG_SHELL" = x; then
+ as_bourne_compatible="if test -n \"\${ZSH_VERSION+set}\" && (emulate sh) >/dev/null 2>&1; then :
+ emulate sh
+ NULLCMD=:
+ # Pre-4.2 versions of Zsh do word splitting on \${1+\"\$@\"}, which
+ # is contrary to our usage. Disable this feature.
+ alias -g '\${1+\"\$@\"}'='\"\$@\"'
+ setopt NO_GLOB_SUBST
+else
+ case \`(set -o) 2>/dev/null\` in #(
+ *posix*) :
+ set -o posix ;; #(
+ *) :
+ ;;
+esac
+fi
+"
+ as_required="as_fn_return () { (exit \$1); }
+as_fn_success () { as_fn_return 0; }
+as_fn_failure () { as_fn_return 1; }
+as_fn_ret_success () { return 0; }
+as_fn_ret_failure () { return 1; }
+
+exitcode=0
+as_fn_success || { exitcode=1; echo as_fn_success failed.; }
+as_fn_failure && { exitcode=1; echo as_fn_failure succeeded.; }
+as_fn_ret_success || { exitcode=1; echo as_fn_ret_success failed.; }
+as_fn_ret_failure && { exitcode=1; echo as_fn_ret_failure succeeded.; }
+if ( set x; as_fn_ret_success y && test x = \"\$1\" ); then :
+
+else
+ exitcode=1; echo positional parameters were not saved.
+fi
+test x\$exitcode = x0 || exit 1
+test -x / || exit 1"
+ as_suggested=" as_lineno_1=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_1a=\$LINENO
+ as_lineno_2=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_2a=\$LINENO
+ eval 'test \"x\$as_lineno_1'\$as_run'\" != \"x\$as_lineno_2'\$as_run'\" &&
+ test \"x\`expr \$as_lineno_1'\$as_run' + 1\`\" = \"x\$as_lineno_2'\$as_run'\"' || exit 1"
+ if (eval "$as_required") 2>/dev/null; then :
+ as_have_required=yes
+else
+ as_have_required=no
+fi
+ if test x$as_have_required = xyes && (eval "$as_suggested") 2>/dev/null; then :
+
+else
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+as_found=false
+for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ as_found=:
+ case $as_dir in #(
+ /*)
+ for as_base in sh bash ksh sh5; do
+ # Try only shells that exist, to save several forks.
+ as_shell=$as_dir/$as_base
+ if { test -f "$as_shell" || test -f "$as_shell.exe"; } &&
+ { $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$as_shell"; } 2>/dev/null; then :
+ CONFIG_SHELL=$as_shell as_have_required=yes
+ if { $as_echo "$as_bourne_compatible""$as_suggested" | as_run=a "$as_shell"; } 2>/dev/null; then :
+ break 2
+fi
+fi
+ done;;
+ esac
+ as_found=false
+done
+$as_found || { if { test -f "$SHELL" || test -f "$SHELL.exe"; } &&
+ { $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$SHELL"; } 2>/dev/null; then :
+ CONFIG_SHELL=$SHELL as_have_required=yes
+fi; }
+IFS=$as_save_IFS
+
+
+ if test "x$CONFIG_SHELL" != x; then :
+ export CONFIG_SHELL
+ # We cannot yet assume a decent shell, so we have to provide a
+# neutralization value for shells without unset; and this also
+# works around shells that cannot unset nonexistent variables.
+# Preserve -v and -x to the replacement shell.
+BASH_ENV=/dev/null
+ENV=/dev/null
+(unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV
+case $- in # ((((
+ *v*x* | *x*v* ) as_opts=-vx ;;
+ *v* ) as_opts=-v ;;
+ *x* ) as_opts=-x ;;
+ * ) as_opts= ;;
+esac
+exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"}
+# Admittedly, this is quite paranoid, since all the known shells bail
+# out after a failed `exec'.
+$as_echo "$0: could not re-execute with $CONFIG_SHELL" >&2
+exit 255
+fi
+
+ if test x$as_have_required = xno; then :
+ $as_echo "$0: This script requires a shell more modern than all"
+ $as_echo "$0: the shells that I found on your system."
+ if test x${ZSH_VERSION+set} = xset ; then
+ $as_echo "$0: In particular, zsh $ZSH_VERSION has bugs and should"
+ $as_echo "$0: be upgraded to zsh 4.3.4 or later."
+ else
+ $as_echo "$0: Please tell bug-autoconf@gnu.org about your system,
+$0: including any error possibly output before this
+$0: message. Then install a modern shell, or manually run
+$0: the script under such a shell if you do have one."
+ fi
+ exit 1
+fi
+fi
+fi
+SHELL=${CONFIG_SHELL-/bin/sh}
+export SHELL
+# Unset more variables known to interfere with behavior of common tools.
+CLICOLOR_FORCE= GREP_OPTIONS=
+unset CLICOLOR_FORCE GREP_OPTIONS
+
+## --------------------- ##
+## M4sh Shell Functions. ##
+## --------------------- ##
+# as_fn_unset VAR
+# ---------------
+# Portably unset VAR.
+as_fn_unset ()
+{
+ { eval $1=; unset $1;}
+}
+as_unset=as_fn_unset
+
+# as_fn_set_status STATUS
+# -----------------------
+# Set $? to STATUS, without forking.
+as_fn_set_status ()
+{
+ return $1
+} # as_fn_set_status
+
+# as_fn_exit STATUS
+# -----------------
+# Exit the shell with STATUS, even in a "trap 0" or "set -e" context.
+as_fn_exit ()
+{
+ set +e
+ as_fn_set_status $1
+ exit $1
+} # as_fn_exit
+
+# as_fn_mkdir_p
+# -------------
+# Create "$as_dir" as a directory, including parents if necessary.
+as_fn_mkdir_p ()
+{
+
+ case $as_dir in #(
+ -*) as_dir=./$as_dir;;
+ esac
+ test -d "$as_dir" || eval $as_mkdir_p || {
+ as_dirs=
+ while :; do
+ case $as_dir in #(
+ *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
+ *) as_qdir=$as_dir;;
+ esac
+ as_dirs="'$as_qdir' $as_dirs"
+ as_dir=`$as_dirname -- "$as_dir" ||
+$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
+ X"$as_dir" : 'X\(//\)[^/]' \| \
+ X"$as_dir" : 'X\(//\)$' \| \
+ X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
+$as_echo X"$as_dir" |
+ sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
+ s//\1/
+ q
+ }
+ /^X\(\/\/\)[^/].*/{
+ s//\1/
+ q
+ }
+ /^X\(\/\/\)$/{
+ s//\1/
+ q
+ }
+ /^X\(\/\).*/{
+ s//\1/
+ q
+ }
+ s/.*/./; q'`
+ test -d "$as_dir" && break
+ done
+ test -z "$as_dirs" || eval "mkdir $as_dirs"
+ } || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir"
+
+
+} # as_fn_mkdir_p
+
+# as_fn_executable_p FILE
+# -----------------------
+# Test if FILE is an executable regular file.
+as_fn_executable_p ()
+{
+ test -f "$1" && test -x "$1"
+} # as_fn_executable_p
+# as_fn_append VAR VALUE
+# ----------------------
+# Append the text in VALUE to the end of the definition contained in VAR. Take
+# advantage of any shell optimizations that allow amortized linear growth over
+# repeated appends, instead of the typical quadratic growth present in naive
+# implementations.
+if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then :
+ eval 'as_fn_append ()
+ {
+ eval $1+=\$2
+ }'
+else
+ as_fn_append ()
+ {
+ eval $1=\$$1\$2
+ }
+fi # as_fn_append
+
+# as_fn_arith ARG...
+# ------------------
+# Perform arithmetic evaluation on the ARGs, and store the result in the
+# global $as_val. Take advantage of shells that can avoid forks. The arguments
+# must be portable across $(()) and expr.
+if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then :
+ eval 'as_fn_arith ()
+ {
+ as_val=$(( $* ))
+ }'
+else
+ as_fn_arith ()
+ {
+ as_val=`expr "$@" || test $? -eq 1`
+ }
+fi # as_fn_arith
+
+
+# as_fn_error STATUS ERROR [LINENO LOG_FD]
+# ----------------------------------------
+# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are
+# provided, also output the error to LOG_FD, referencing LINENO. Then exit the
+# script with STATUS, using 1 if that was 0.
+as_fn_error ()
+{
+ as_status=$1; test $as_status -eq 0 && as_status=1
+ if test "$4"; then
+ as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
+ $as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4
+ fi
+ $as_echo "$as_me: error: $2" >&2
+ as_fn_exit $as_status
+} # as_fn_error
+
+if expr a : '\(a\)' >/dev/null 2>&1 &&
+ test "X`expr 00001 : '.*\(...\)'`" = X001; then
+ as_expr=expr
+else
+ as_expr=false
+fi
+
+if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
+ as_basename=basename
+else
+ as_basename=false
+fi
+
+if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
+ as_dirname=dirname
+else
+ as_dirname=false
+fi
+
+as_me=`$as_basename -- "$0" ||
+$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
+ X"$0" : 'X\(//\)$' \| \
+ X"$0" : 'X\(/\)' \| . 2>/dev/null ||
+$as_echo X/"$0" |
+ sed '/^.*\/\([^/][^/]*\)\/*$/{
+ s//\1/
+ q
+ }
+ /^X\/\(\/\/\)$/{
+ s//\1/
+ q
+ }
+ /^X\/\(\/\).*/{
+ s//\1/
+ q
+ }
+ s/.*/./; q'`
+
+# Avoid depending upon Character Ranges.
+as_cr_letters='abcdefghijklmnopqrstuvwxyz'
+as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
+as_cr_Letters=$as_cr_letters$as_cr_LETTERS
+as_cr_digits='0123456789'
+as_cr_alnum=$as_cr_Letters$as_cr_digits
+
+
+ as_lineno_1=$LINENO as_lineno_1a=$LINENO
+ as_lineno_2=$LINENO as_lineno_2a=$LINENO
+ eval 'test "x$as_lineno_1'$as_run'" != "x$as_lineno_2'$as_run'" &&
+ test "x`expr $as_lineno_1'$as_run' + 1`" = "x$as_lineno_2'$as_run'"' || {
+ # Blame Lee E. McMahon (1931-1989) for sed's syntax. :-)
+ sed -n '
+ p
+ /[$]LINENO/=
+ ' <$as_myself |
+ sed '
+ s/[$]LINENO.*/&-/
+ t lineno
+ b
+ :lineno
+ N
+ :loop
+ s/[$]LINENO\([^'$as_cr_alnum'_].*\n\)\(.*\)/\2\1\2/
+ t loop
+ s/-\n.*//
+ ' >$as_me.lineno &&
+ chmod +x "$as_me.lineno" ||
+ { $as_echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2; as_fn_exit 1; }
+
+ # If we had to re-execute with $CONFIG_SHELL, we're ensured to have
+ # already done that, so ensure we don't try to do so again and fall
+ # in an infinite loop. This has already happened in practice.
+ _as_can_reexec=no; export _as_can_reexec
+ # Don't try to exec as it changes $[0], causing all sort of problems
+ # (the dirname of $[0] is not the place where we might find the
+ # original and so on. Autoconf is especially sensitive to this).
+ . "./$as_me.lineno"
+ # Exit status is that of the last command.
+ exit
+}
+
+ECHO_C= ECHO_N= ECHO_T=
+case `echo -n x` in #(((((
+-n*)
+ case `echo 'xy\c'` in
+ *c*) ECHO_T=' ';; # ECHO_T is single tab character.
+ xy) ECHO_C='\c';;
+ *) echo `echo ksh88 bug on AIX 6.1` > /dev/null
+ ECHO_T=' ';;
+ esac;;
+*)
+ ECHO_N='-n';;
+esac
+
+rm -f conf$$ conf$$.exe conf$$.file
+if test -d conf$$.dir; then
+ rm -f conf$$.dir/conf$$.file
+else
+ rm -f conf$$.dir
+ mkdir conf$$.dir 2>/dev/null
+fi
+if (echo >conf$$.file) 2>/dev/null; then
+ if ln -s conf$$.file conf$$ 2>/dev/null; then
+ as_ln_s='ln -s'
+ # ... but there are two gotchas:
+ # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
+ # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
+ # In both cases, we have to default to `cp -pR'.
+ ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
+ as_ln_s='cp -pR'
+ elif ln conf$$.file conf$$ 2>/dev/null; then
+ as_ln_s=ln
+ else
+ as_ln_s='cp -pR'
+ fi
+else
+ as_ln_s='cp -pR'
+fi
+rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
+rmdir conf$$.dir 2>/dev/null
+
+if mkdir -p . 2>/dev/null; then
+ as_mkdir_p='mkdir -p "$as_dir"'
+else
+ test -d ./-p && rmdir ./-p
+ as_mkdir_p=false
+fi
+
+as_test_x='test -x'
+as_executable_p=as_fn_executable_p
+
+# Sed expression to map a string onto a valid CPP name.
+as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
+
+# Sed expression to map a string onto a valid variable name.
+as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
+
+
+test -n "$DJDIR" || exec 7<&0 &1
+
+# Name of the host.
+# hostname on some systems (SVR3.2, old GNU/Linux) returns a bogus exit status,
+# so uname gets run too.
+ac_hostname=`(hostname || uname -n) 2>/dev/null | sed 1q`
+
+#
+# Initializations.
+#
+ac_default_prefix=/usr/local
+ac_clean_files=
+ac_config_libobj_dir=.
+LIBOBJS=
+cross_compiling=no
+subdirs=
+MFLAGS=
+MAKEFLAGS=
+
+# Identity of this package.
+PACKAGE_NAME='MathML Logo'
+PACKAGE_TARNAME='mathml-logo'
+PACKAGE_VERSION='1.0'
+PACKAGE_STRING='MathML Logo 1.0'
+PACKAGE_BUGREPORT=''
+PACKAGE_URL=''
+
+ac_unique_file="mathml-logo.svg"
+ac_subst_vars='LTLIBOBJS
+LIBOBJS
+ZIP
+WGET
+XSLTPROC
+UNZIP
+SFNT2WOFF
+SCOUR
+INKSCAPE
+target_alias
+host_alias
+build_alias
+LIBS
+ECHO_T
+ECHO_N
+ECHO_C
+DEFS
+mandir
+localedir
+libdir
+psdir
+pdfdir
+dvidir
+htmldir
+infodir
+docdir
+oldincludedir
+includedir
+localstatedir
+sharedstatedir
+sysconfdir
+datadir
+datarootdir
+libexecdir
+sbindir
+bindir
+program_transform_name
+prefix
+exec_prefix
+PACKAGE_URL
+PACKAGE_BUGREPORT
+PACKAGE_STRING
+PACKAGE_VERSION
+PACKAGE_TARNAME
+PACKAGE_NAME
+PATH_SEPARATOR
+SHELL'
+ac_subst_files=''
+ac_user_opts='
+enable_option_checking
+'
+ ac_precious_vars='build_alias
+host_alias
+target_alias'
+
+
+# Initialize some variables set by options.
+ac_init_help=
+ac_init_version=false
+ac_unrecognized_opts=
+ac_unrecognized_sep=
+# The variables have the same names as the options, with
+# dashes changed to underlines.
+cache_file=/dev/null
+exec_prefix=NONE
+no_create=
+no_recursion=
+prefix=NONE
+program_prefix=NONE
+program_suffix=NONE
+program_transform_name=s,x,x,
+silent=
+site=
+srcdir=
+verbose=
+x_includes=NONE
+x_libraries=NONE
+
+# Installation directory options.
+# These are left unexpanded so users can "make install exec_prefix=/foo"
+# and all the variables that are supposed to be based on exec_prefix
+# by default will actually change.
+# Use braces instead of parens because sh, perl, etc. also accept them.
+# (The list follows the same order as the GNU Coding Standards.)
+bindir='${exec_prefix}/bin'
+sbindir='${exec_prefix}/sbin'
+libexecdir='${exec_prefix}/libexec'
+datarootdir='${prefix}/share'
+datadir='${datarootdir}'
+sysconfdir='${prefix}/etc'
+sharedstatedir='${prefix}/com'
+localstatedir='${prefix}/var'
+includedir='${prefix}/include'
+oldincludedir='/usr/include'
+docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
+infodir='${datarootdir}/info'
+htmldir='${docdir}'
+dvidir='${docdir}'
+pdfdir='${docdir}'
+psdir='${docdir}'
+libdir='${exec_prefix}/lib'
+localedir='${datarootdir}/locale'
+mandir='${datarootdir}/man'
+
+ac_prev=
+ac_dashdash=
+for ac_option
+do
+ # If the previous option needs an argument, assign it.
+ if test -n "$ac_prev"; then
+ eval $ac_prev=\$ac_option
+ ac_prev=
+ continue
+ fi
+
+ case $ac_option in
+ *=?*) ac_optarg=`expr "X$ac_option" : '[^=]*=\(.*\)'` ;;
+ *=) ac_optarg= ;;
+ *) ac_optarg=yes ;;
+ esac
+
+ # Accept the important Cygnus configure options, so we can diagnose typos.
+
+ case $ac_dashdash$ac_option in
+ --)
+ ac_dashdash=yes ;;
+
+ -bindir | --bindir | --bindi | --bind | --bin | --bi)
+ ac_prev=bindir ;;
+ -bindir=* | --bindir=* | --bindi=* | --bind=* | --bin=* | --bi=*)
+ bindir=$ac_optarg ;;
+
+ -build | --build | --buil | --bui | --bu)
+ ac_prev=build_alias ;;
+ -build=* | --build=* | --buil=* | --bui=* | --bu=*)
+ build_alias=$ac_optarg ;;
+
+ -cache-file | --cache-file | --cache-fil | --cache-fi \
+ | --cache-f | --cache- | --cache | --cach | --cac | --ca | --c)
+ ac_prev=cache_file ;;
+ -cache-file=* | --cache-file=* | --cache-fil=* | --cache-fi=* \
+ | --cache-f=* | --cache-=* | --cache=* | --cach=* | --cac=* | --ca=* | --c=*)
+ cache_file=$ac_optarg ;;
+
+ --config-cache | -C)
+ cache_file=config.cache ;;
+
+ -datadir | --datadir | --datadi | --datad)
+ ac_prev=datadir ;;
+ -datadir=* | --datadir=* | --datadi=* | --datad=*)
+ datadir=$ac_optarg ;;
+
+ -datarootdir | --datarootdir | --datarootdi | --datarootd | --dataroot \
+ | --dataroo | --dataro | --datar)
+ ac_prev=datarootdir ;;
+ -datarootdir=* | --datarootdir=* | --datarootdi=* | --datarootd=* \
+ | --dataroot=* | --dataroo=* | --dataro=* | --datar=*)
+ datarootdir=$ac_optarg ;;
+
+ -disable-* | --disable-*)
+ ac_useropt=`expr "x$ac_option" : 'x-*disable-\(.*\)'`
+ # Reject names that are not valid shell variable names.
+ expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
+ as_fn_error $? "invalid feature name: $ac_useropt"
+ ac_useropt_orig=$ac_useropt
+ ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
+ case $ac_user_opts in
+ *"
+"enable_$ac_useropt"
+"*) ;;
+ *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--disable-$ac_useropt_orig"
+ ac_unrecognized_sep=', ';;
+ esac
+ eval enable_$ac_useropt=no ;;
+
+ -docdir | --docdir | --docdi | --doc | --do)
+ ac_prev=docdir ;;
+ -docdir=* | --docdir=* | --docdi=* | --doc=* | --do=*)
+ docdir=$ac_optarg ;;
+
+ -dvidir | --dvidir | --dvidi | --dvid | --dvi | --dv)
+ ac_prev=dvidir ;;
+ -dvidir=* | --dvidir=* | --dvidi=* | --dvid=* | --dvi=* | --dv=*)
+ dvidir=$ac_optarg ;;
+
+ -enable-* | --enable-*)
+ ac_useropt=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'`
+ # Reject names that are not valid shell variable names.
+ expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
+ as_fn_error $? "invalid feature name: $ac_useropt"
+ ac_useropt_orig=$ac_useropt
+ ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
+ case $ac_user_opts in
+ *"
+"enable_$ac_useropt"
+"*) ;;
+ *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--enable-$ac_useropt_orig"
+ ac_unrecognized_sep=', ';;
+ esac
+ eval enable_$ac_useropt=\$ac_optarg ;;
+
+ -exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \
+ | --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \
+ | --exec | --exe | --ex)
+ ac_prev=exec_prefix ;;
+ -exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* \
+ | --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* \
+ | --exec=* | --exe=* | --ex=*)
+ exec_prefix=$ac_optarg ;;
+
+ -gas | --gas | --ga | --g)
+ # Obsolete; use --with-gas.
+ with_gas=yes ;;
+
+ -help | --help | --hel | --he | -h)
+ ac_init_help=long ;;
+ -help=r* | --help=r* | --hel=r* | --he=r* | -hr*)
+ ac_init_help=recursive ;;
+ -help=s* | --help=s* | --hel=s* | --he=s* | -hs*)
+ ac_init_help=short ;;
+
+ -host | --host | --hos | --ho)
+ ac_prev=host_alias ;;
+ -host=* | --host=* | --hos=* | --ho=*)
+ host_alias=$ac_optarg ;;
+
+ -htmldir | --htmldir | --htmldi | --htmld | --html | --htm | --ht)
+ ac_prev=htmldir ;;
+ -htmldir=* | --htmldir=* | --htmldi=* | --htmld=* | --html=* | --htm=* \
+ | --ht=*)
+ htmldir=$ac_optarg ;;
+
+ -includedir | --includedir | --includedi | --included | --include \
+ | --includ | --inclu | --incl | --inc)
+ ac_prev=includedir ;;
+ -includedir=* | --includedir=* | --includedi=* | --included=* | --include=* \
+ | --includ=* | --inclu=* | --incl=* | --inc=*)
+ includedir=$ac_optarg ;;
+
+ -infodir | --infodir | --infodi | --infod | --info | --inf)
+ ac_prev=infodir ;;
+ -infodir=* | --infodir=* | --infodi=* | --infod=* | --info=* | --inf=*)
+ infodir=$ac_optarg ;;
+
+ -libdir | --libdir | --libdi | --libd)
+ ac_prev=libdir ;;
+ -libdir=* | --libdir=* | --libdi=* | --libd=*)
+ libdir=$ac_optarg ;;
+
+ -libexecdir | --libexecdir | --libexecdi | --libexecd | --libexec \
+ | --libexe | --libex | --libe)
+ ac_prev=libexecdir ;;
+ -libexecdir=* | --libexecdir=* | --libexecdi=* | --libexecd=* | --libexec=* \
+ | --libexe=* | --libex=* | --libe=*)
+ libexecdir=$ac_optarg ;;
+
+ -localedir | --localedir | --localedi | --localed | --locale)
+ ac_prev=localedir ;;
+ -localedir=* | --localedir=* | --localedi=* | --localed=* | --locale=*)
+ localedir=$ac_optarg ;;
+
+ -localstatedir | --localstatedir | --localstatedi | --localstated \
+ | --localstate | --localstat | --localsta | --localst | --locals)
+ ac_prev=localstatedir ;;
+ -localstatedir=* | --localstatedir=* | --localstatedi=* | --localstated=* \
+ | --localstate=* | --localstat=* | --localsta=* | --localst=* | --locals=*)
+ localstatedir=$ac_optarg ;;
+
+ -mandir | --mandir | --mandi | --mand | --man | --ma | --m)
+ ac_prev=mandir ;;
+ -mandir=* | --mandir=* | --mandi=* | --mand=* | --man=* | --ma=* | --m=*)
+ mandir=$ac_optarg ;;
+
+ -nfp | --nfp | --nf)
+ # Obsolete; use --without-fp.
+ with_fp=no ;;
+
+ -no-create | --no-create | --no-creat | --no-crea | --no-cre \
+ | --no-cr | --no-c | -n)
+ no_create=yes ;;
+
+ -no-recursion | --no-recursion | --no-recursio | --no-recursi \
+ | --no-recurs | --no-recur | --no-recu | --no-rec | --no-re | --no-r)
+ no_recursion=yes ;;
+
+ -oldincludedir | --oldincludedir | --oldincludedi | --oldincluded \
+ | --oldinclude | --oldinclud | --oldinclu | --oldincl | --oldinc \
+ | --oldin | --oldi | --old | --ol | --o)
+ ac_prev=oldincludedir ;;
+ -oldincludedir=* | --oldincludedir=* | --oldincludedi=* | --oldincluded=* \
+ | --oldinclude=* | --oldinclud=* | --oldinclu=* | --oldincl=* | --oldinc=* \
+ | --oldin=* | --oldi=* | --old=* | --ol=* | --o=*)
+ oldincludedir=$ac_optarg ;;
+
+ -prefix | --prefix | --prefi | --pref | --pre | --pr | --p)
+ ac_prev=prefix ;;
+ -prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*)
+ prefix=$ac_optarg ;;
+
+ -program-prefix | --program-prefix | --program-prefi | --program-pref \
+ | --program-pre | --program-pr | --program-p)
+ ac_prev=program_prefix ;;
+ -program-prefix=* | --program-prefix=* | --program-prefi=* \
+ | --program-pref=* | --program-pre=* | --program-pr=* | --program-p=*)
+ program_prefix=$ac_optarg ;;
+
+ -program-suffix | --program-suffix | --program-suffi | --program-suff \
+ | --program-suf | --program-su | --program-s)
+ ac_prev=program_suffix ;;
+ -program-suffix=* | --program-suffix=* | --program-suffi=* \
+ | --program-suff=* | --program-suf=* | --program-su=* | --program-s=*)
+ program_suffix=$ac_optarg ;;
+
+ -program-transform-name | --program-transform-name \
+ | --program-transform-nam | --program-transform-na \
+ | --program-transform-n | --program-transform- \
+ | --program-transform | --program-transfor \
+ | --program-transfo | --program-transf \
+ | --program-trans | --program-tran \
+ | --progr-tra | --program-tr | --program-t)
+ ac_prev=program_transform_name ;;
+ -program-transform-name=* | --program-transform-name=* \
+ | --program-transform-nam=* | --program-transform-na=* \
+ | --program-transform-n=* | --program-transform-=* \
+ | --program-transform=* | --program-transfor=* \
+ | --program-transfo=* | --program-transf=* \
+ | --program-trans=* | --program-tran=* \
+ | --progr-tra=* | --program-tr=* | --program-t=*)
+ program_transform_name=$ac_optarg ;;
+
+ -pdfdir | --pdfdir | --pdfdi | --pdfd | --pdf | --pd)
+ ac_prev=pdfdir ;;
+ -pdfdir=* | --pdfdir=* | --pdfdi=* | --pdfd=* | --pdf=* | --pd=*)
+ pdfdir=$ac_optarg ;;
+
+ -psdir | --psdir | --psdi | --psd | --ps)
+ ac_prev=psdir ;;
+ -psdir=* | --psdir=* | --psdi=* | --psd=* | --ps=*)
+ psdir=$ac_optarg ;;
+
+ -q | -quiet | --quiet | --quie | --qui | --qu | --q \
+ | -silent | --silent | --silen | --sile | --sil)
+ silent=yes ;;
+
+ -sbindir | --sbindir | --sbindi | --sbind | --sbin | --sbi | --sb)
+ ac_prev=sbindir ;;
+ -sbindir=* | --sbindir=* | --sbindi=* | --sbind=* | --sbin=* \
+ | --sbi=* | --sb=*)
+ sbindir=$ac_optarg ;;
+
+ -sharedstatedir | --sharedstatedir | --sharedstatedi \
+ | --sharedstated | --sharedstate | --sharedstat | --sharedsta \
+ | --sharedst | --shareds | --shared | --share | --shar \
+ | --sha | --sh)
+ ac_prev=sharedstatedir ;;
+ -sharedstatedir=* | --sharedstatedir=* | --sharedstatedi=* \
+ | --sharedstated=* | --sharedstate=* | --sharedstat=* | --sharedsta=* \
+ | --sharedst=* | --shareds=* | --shared=* | --share=* | --shar=* \
+ | --sha=* | --sh=*)
+ sharedstatedir=$ac_optarg ;;
+
+ -site | --site | --sit)
+ ac_prev=site ;;
+ -site=* | --site=* | --sit=*)
+ site=$ac_optarg ;;
+
+ -srcdir | --srcdir | --srcdi | --srcd | --src | --sr)
+ ac_prev=srcdir ;;
+ -srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*)
+ srcdir=$ac_optarg ;;
+
+ -sysconfdir | --sysconfdir | --sysconfdi | --sysconfd | --sysconf \
+ | --syscon | --sysco | --sysc | --sys | --sy)
+ ac_prev=sysconfdir ;;
+ -sysconfdir=* | --sysconfdir=* | --sysconfdi=* | --sysconfd=* | --sysconf=* \
+ | --syscon=* | --sysco=* | --sysc=* | --sys=* | --sy=*)
+ sysconfdir=$ac_optarg ;;
+
+ -target | --target | --targe | --targ | --tar | --ta | --t)
+ ac_prev=target_alias ;;
+ -target=* | --target=* | --targe=* | --targ=* | --tar=* | --ta=* | --t=*)
+ target_alias=$ac_optarg ;;
+
+ -v | -verbose | --verbose | --verbos | --verbo | --verb)
+ verbose=yes ;;
+
+ -version | --version | --versio | --versi | --vers | -V)
+ ac_init_version=: ;;
+
+ -with-* | --with-*)
+ ac_useropt=`expr "x$ac_option" : 'x-*with-\([^=]*\)'`
+ # Reject names that are not valid shell variable names.
+ expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
+ as_fn_error $? "invalid package name: $ac_useropt"
+ ac_useropt_orig=$ac_useropt
+ ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
+ case $ac_user_opts in
+ *"
+"with_$ac_useropt"
+"*) ;;
+ *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--with-$ac_useropt_orig"
+ ac_unrecognized_sep=', ';;
+ esac
+ eval with_$ac_useropt=\$ac_optarg ;;
+
+ -without-* | --without-*)
+ ac_useropt=`expr "x$ac_option" : 'x-*without-\(.*\)'`
+ # Reject names that are not valid shell variable names.
+ expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
+ as_fn_error $? "invalid package name: $ac_useropt"
+ ac_useropt_orig=$ac_useropt
+ ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
+ case $ac_user_opts in
+ *"
+"with_$ac_useropt"
+"*) ;;
+ *) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--without-$ac_useropt_orig"
+ ac_unrecognized_sep=', ';;
+ esac
+ eval with_$ac_useropt=no ;;
+
+ --x)
+ # Obsolete; use --with-x.
+ with_x=yes ;;
+
+ -x-includes | --x-includes | --x-include | --x-includ | --x-inclu \
+ | --x-incl | --x-inc | --x-in | --x-i)
+ ac_prev=x_includes ;;
+ -x-includes=* | --x-includes=* | --x-include=* | --x-includ=* | --x-inclu=* \
+ | --x-incl=* | --x-inc=* | --x-in=* | --x-i=*)
+ x_includes=$ac_optarg ;;
+
+ -x-libraries | --x-libraries | --x-librarie | --x-librari \
+ | --x-librar | --x-libra | --x-libr | --x-lib | --x-li | --x-l)
+ ac_prev=x_libraries ;;
+ -x-libraries=* | --x-libraries=* | --x-librarie=* | --x-librari=* \
+ | --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*)
+ x_libraries=$ac_optarg ;;
+
+ -*) as_fn_error $? "unrecognized option: \`$ac_option'
+Try \`$0 --help' for more information"
+ ;;
+
+ *=*)
+ ac_envvar=`expr "x$ac_option" : 'x\([^=]*\)='`
+ # Reject names that are not valid shell variable names.
+ case $ac_envvar in #(
+ '' | [0-9]* | *[!_$as_cr_alnum]* )
+ as_fn_error $? "invalid variable name: \`$ac_envvar'" ;;
+ esac
+ eval $ac_envvar=\$ac_optarg
+ export $ac_envvar ;;
+
+ *)
+ # FIXME: should be removed in autoconf 3.0.
+ $as_echo "$as_me: WARNING: you should use --build, --host, --target" >&2
+ expr "x$ac_option" : ".*[^-._$as_cr_alnum]" >/dev/null &&
+ $as_echo "$as_me: WARNING: invalid host type: $ac_option" >&2
+ : "${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option}"
+ ;;
+
+ esac
+done
+
+if test -n "$ac_prev"; then
+ ac_option=--`echo $ac_prev | sed 's/_/-/g'`
+ as_fn_error $? "missing argument to $ac_option"
+fi
+
+if test -n "$ac_unrecognized_opts"; then
+ case $enable_option_checking in
+ no) ;;
+ fatal) as_fn_error $? "unrecognized options: $ac_unrecognized_opts" ;;
+ *) $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2 ;;
+ esac
+fi
+
+# Check all directory arguments for consistency.
+for ac_var in exec_prefix prefix bindir sbindir libexecdir datarootdir \
+ datadir sysconfdir sharedstatedir localstatedir includedir \
+ oldincludedir docdir infodir htmldir dvidir pdfdir psdir \
+ libdir localedir mandir
+do
+ eval ac_val=\$$ac_var
+ # Remove trailing slashes.
+ case $ac_val in
+ */ )
+ ac_val=`expr "X$ac_val" : 'X\(.*[^/]\)' \| "X$ac_val" : 'X\(.*\)'`
+ eval $ac_var=\$ac_val;;
+ esac
+ # Be sure to have absolute directory names.
+ case $ac_val in
+ [\\/$]* | ?:[\\/]* ) continue;;
+ NONE | '' ) case $ac_var in *prefix ) continue;; esac;;
+ esac
+ as_fn_error $? "expected an absolute directory name for --$ac_var: $ac_val"
+done
+
+# There might be people who depend on the old broken behavior: `$host'
+# used to hold the argument of --host etc.
+# FIXME: To remove some day.
+build=$build_alias
+host=$host_alias
+target=$target_alias
+
+# FIXME: To remove some day.
+if test "x$host_alias" != x; then
+ if test "x$build_alias" = x; then
+ cross_compiling=maybe
+ elif test "x$build_alias" != "x$host_alias"; then
+ cross_compiling=yes
+ fi
+fi
+
+ac_tool_prefix=
+test -n "$host_alias" && ac_tool_prefix=$host_alias-
+
+test "$silent" = yes && exec 6>/dev/null
+
+
+ac_pwd=`pwd` && test -n "$ac_pwd" &&
+ac_ls_di=`ls -di .` &&
+ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||
+ as_fn_error $? "working directory cannot be determined"
+test "X$ac_ls_di" = "X$ac_pwd_ls_di" ||
+ as_fn_error $? "pwd does not report name of working directory"
+
+
+# Find the source files, if location was not specified.
+if test -z "$srcdir"; then
+ ac_srcdir_defaulted=yes
+ # Try the directory containing this script, then the parent directory.
+ ac_confdir=`$as_dirname -- "$as_myself" ||
+$as_expr X"$as_myself" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
+ X"$as_myself" : 'X\(//\)[^/]' \| \
+ X"$as_myself" : 'X\(//\)$' \| \
+ X"$as_myself" : 'X\(/\)' \| . 2>/dev/null ||
+$as_echo X"$as_myself" |
+ sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
+ s//\1/
+ q
+ }
+ /^X\(\/\/\)[^/].*/{
+ s//\1/
+ q
+ }
+ /^X\(\/\/\)$/{
+ s//\1/
+ q
+ }
+ /^X\(\/\).*/{
+ s//\1/
+ q
+ }
+ s/.*/./; q'`
+ srcdir=$ac_confdir
+ if test ! -r "$srcdir/$ac_unique_file"; then
+ srcdir=..
+ fi
+else
+ ac_srcdir_defaulted=no
+fi
+if test ! -r "$srcdir/$ac_unique_file"; then
+ test "$ac_srcdir_defaulted" = yes && srcdir="$ac_confdir or .."
+ as_fn_error $? "cannot find sources ($ac_unique_file) in $srcdir"
+fi
+ac_msg="sources are in $srcdir, but \`cd $srcdir' does not work"
+ac_abs_confdir=`(
+ cd "$srcdir" && test -r "./$ac_unique_file" || as_fn_error $? "$ac_msg"
+ pwd)`
+# When building in place, set srcdir=.
+if test "$ac_abs_confdir" = "$ac_pwd"; then
+ srcdir=.
+fi
+# Remove unnecessary trailing slashes from srcdir.
+# Double slashes in file names in object file debugging info
+# mess up M-x gdb in Emacs.
+case $srcdir in
+*/) srcdir=`expr "X$srcdir" : 'X\(.*[^/]\)' \| "X$srcdir" : 'X\(.*\)'`;;
+esac
+for ac_var in $ac_precious_vars; do
+ eval ac_env_${ac_var}_set=\${${ac_var}+set}
+ eval ac_env_${ac_var}_value=\$${ac_var}
+ eval ac_cv_env_${ac_var}_set=\${${ac_var}+set}
+ eval ac_cv_env_${ac_var}_value=\$${ac_var}
+done
+
+#
+# Report the --help message.
+#
+if test "$ac_init_help" = "long"; then
+ # Omit some internal or obsolete options to make the list less imposing.
+ # This message is too long to be a string in the A/UX 3.1 sh.
+ cat <<_ACEOF
+\`configure' configures MathML Logo 1.0 to adapt to many kinds of systems.
+
+Usage: $0 [OPTION]... [VAR=VALUE]...
+
+To assign environment variables (e.g., CC, CFLAGS...), specify them as
+VAR=VALUE. See below for descriptions of some of the useful variables.
+
+Defaults for the options are specified in brackets.
+
+Configuration:
+ -h, --help display this help and exit
+ --help=short display options specific to this package
+ --help=recursive display the short help of all the included packages
+ -V, --version display version information and exit
+ -q, --quiet, --silent do not print \`checking ...' messages
+ --cache-file=FILE cache test results in FILE [disabled]
+ -C, --config-cache alias for \`--cache-file=config.cache'
+ -n, --no-create do not create output files
+ --srcdir=DIR find the sources in DIR [configure dir or \`..']
+
+Installation directories:
+ --prefix=PREFIX install architecture-independent files in PREFIX
+ [$ac_default_prefix]
+ --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
+ [PREFIX]
+
+By default, \`make install' will install all the files in
+\`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc. You can specify
+an installation prefix other than \`$ac_default_prefix' using \`--prefix',
+for instance \`--prefix=\$HOME'.
+
+For better control, use the options below.
+
+Fine tuning of the installation directories:
+ --bindir=DIR user executables [EPREFIX/bin]
+ --sbindir=DIR system admin executables [EPREFIX/sbin]
+ --libexecdir=DIR program executables [EPREFIX/libexec]
+ --sysconfdir=DIR read-only single-machine data [PREFIX/etc]
+ --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
+ --localstatedir=DIR modifiable single-machine data [PREFIX/var]
+ --libdir=DIR object code libraries [EPREFIX/lib]
+ --includedir=DIR C header files [PREFIX/include]
+ --oldincludedir=DIR C header files for non-gcc [/usr/include]
+ --datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
+ --datadir=DIR read-only architecture-independent data [DATAROOTDIR]
+ --infodir=DIR info documentation [DATAROOTDIR/info]
+ --localedir=DIR locale-dependent data [DATAROOTDIR/locale]
+ --mandir=DIR man documentation [DATAROOTDIR/man]
+ --docdir=DIR documentation root [DATAROOTDIR/doc/mathml-logo]
+ --htmldir=DIR html documentation [DOCDIR]
+ --dvidir=DIR dvi documentation [DOCDIR]
+ --pdfdir=DIR pdf documentation [DOCDIR]
+ --psdir=DIR ps documentation [DOCDIR]
+_ACEOF
+
+ cat <<\_ACEOF
+_ACEOF
+fi
+
+if test -n "$ac_init_help"; then
+ case $ac_init_help in
+ short | recursive ) echo "Configuration of MathML Logo 1.0:";;
+ esac
+ cat <<\_ACEOF
+
+Report bugs to the package provider.
+_ACEOF
+ac_status=$?
+fi
+
+if test "$ac_init_help" = "recursive"; then
+ # If there are subdirs, report their specific --help.
+ for ac_dir in : $ac_subdirs_all; do test "x$ac_dir" = x: && continue
+ test -d "$ac_dir" ||
+ { cd "$srcdir" && ac_pwd=`pwd` && srcdir=. && test -d "$ac_dir"; } ||
+ continue
+ ac_builddir=.
+
+case "$ac_dir" in
+.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
+*)
+ ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
+ # A ".." for each directory in $ac_dir_suffix.
+ ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
+ case $ac_top_builddir_sub in
+ "") ac_top_builddir_sub=. ac_top_build_prefix= ;;
+ *) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
+ esac ;;
+esac
+ac_abs_top_builddir=$ac_pwd
+ac_abs_builddir=$ac_pwd$ac_dir_suffix
+# for backward compatibility:
+ac_top_builddir=$ac_top_build_prefix
+
+case $srcdir in
+ .) # We are building in place.
+ ac_srcdir=.
+ ac_top_srcdir=$ac_top_builddir_sub
+ ac_abs_top_srcdir=$ac_pwd ;;
+ [\\/]* | ?:[\\/]* ) # Absolute name.
+ ac_srcdir=$srcdir$ac_dir_suffix;
+ ac_top_srcdir=$srcdir
+ ac_abs_top_srcdir=$srcdir ;;
+ *) # Relative name.
+ ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
+ ac_top_srcdir=$ac_top_build_prefix$srcdir
+ ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
+esac
+ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
+
+ cd "$ac_dir" || { ac_status=$?; continue; }
+ # Check for guested configure.
+ if test -f "$ac_srcdir/configure.gnu"; then
+ echo &&
+ $SHELL "$ac_srcdir/configure.gnu" --help=recursive
+ elif test -f "$ac_srcdir/configure"; then
+ echo &&
+ $SHELL "$ac_srcdir/configure" --help=recursive
+ else
+ $as_echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2
+ fi || ac_status=$?
+ cd "$ac_pwd" || { ac_status=$?; break; }
+ done
+fi
+
+test -n "$ac_init_help" && exit $ac_status
+if $ac_init_version; then
+ cat <<\_ACEOF
+MathML Logo configure 1.0
+generated by GNU Autoconf 2.69
+
+Copyright (C) 2012 Free Software Foundation, Inc.
+This configure script is free software; the Free Software Foundation
+gives unlimited permission to copy, distribute and modify it.
+_ACEOF
+ exit
+fi
+
+## ------------------------ ##
+## Autoconf initialization. ##
+## ------------------------ ##
+cat >config.log <<_ACEOF
+This file contains any messages produced by compilers while
+running configure, to aid debugging if configure makes a mistake.
+
+It was created by MathML Logo $as_me 1.0, which was
+generated by GNU Autoconf 2.69. Invocation command line was
+
+ $ $0 $@
+
+_ACEOF
+exec 5>>config.log
+{
+cat <<_ASUNAME
+## --------- ##
+## Platform. ##
+## --------- ##
+
+hostname = `(hostname || uname -n) 2>/dev/null | sed 1q`
+uname -m = `(uname -m) 2>/dev/null || echo unknown`
+uname -r = `(uname -r) 2>/dev/null || echo unknown`
+uname -s = `(uname -s) 2>/dev/null || echo unknown`
+uname -v = `(uname -v) 2>/dev/null || echo unknown`
+
+/usr/bin/uname -p = `(/usr/bin/uname -p) 2>/dev/null || echo unknown`
+/bin/uname -X = `(/bin/uname -X) 2>/dev/null || echo unknown`
+
+/bin/arch = `(/bin/arch) 2>/dev/null || echo unknown`
+/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null || echo unknown`
+/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null || echo unknown`
+/usr/bin/hostinfo = `(/usr/bin/hostinfo) 2>/dev/null || echo unknown`
+/bin/machine = `(/bin/machine) 2>/dev/null || echo unknown`
+/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null || echo unknown`
+/bin/universe = `(/bin/universe) 2>/dev/null || echo unknown`
+
+_ASUNAME
+
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ $as_echo "PATH: $as_dir"
+ done
+IFS=$as_save_IFS
+
+} >&5
+
+cat >&5 <<_ACEOF
+
+
+## ----------- ##
+## Core tests. ##
+## ----------- ##
+
+_ACEOF
+
+
+# Keep a trace of the command line.
+# Strip out --no-create and --no-recursion so they do not pile up.
+# Strip out --silent because we don't want to record it for future runs.
+# Also quote any args containing shell meta-characters.
+# Make two passes to allow for proper duplicate-argument suppression.
+ac_configure_args=
+ac_configure_args0=
+ac_configure_args1=
+ac_must_keep_next=false
+for ac_pass in 1 2
+do
+ for ac_arg
+ do
+ case $ac_arg in
+ -no-create | --no-c* | -n | -no-recursion | --no-r*) continue ;;
+ -q | -quiet | --quiet | --quie | --qui | --qu | --q \
+ | -silent | --silent | --silen | --sile | --sil)
+ continue ;;
+ *\'*)
+ ac_arg=`$as_echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;;
+ esac
+ case $ac_pass in
+ 1) as_fn_append ac_configure_args0 " '$ac_arg'" ;;
+ 2)
+ as_fn_append ac_configure_args1 " '$ac_arg'"
+ if test $ac_must_keep_next = true; then
+ ac_must_keep_next=false # Got value, back to normal.
+ else
+ case $ac_arg in
+ *=* | --config-cache | -C | -disable-* | --disable-* \
+ | -enable-* | --enable-* | -gas | --g* | -nfp | --nf* \
+ | -q | -quiet | --q* | -silent | --sil* | -v | -verb* \
+ | -with-* | --with-* | -without-* | --without-* | --x)
+ case "$ac_configure_args0 " in
+ "$ac_configure_args1"*" '$ac_arg' "* ) continue ;;
+ esac
+ ;;
+ -* ) ac_must_keep_next=true ;;
+ esac
+ fi
+ as_fn_append ac_configure_args " '$ac_arg'"
+ ;;
+ esac
+ done
+done
+{ ac_configure_args0=; unset ac_configure_args0;}
+{ ac_configure_args1=; unset ac_configure_args1;}
+
+# When interrupted or exit'd, cleanup temporary files, and complete
+# config.log. We remove comments because anyway the quotes in there
+# would cause problems or look ugly.
+# WARNING: Use '\'' to represent an apostrophe within the trap.
+# WARNING: Do not start the trap code with a newline, due to a FreeBSD 4.0 bug.
+trap 'exit_status=$?
+ # Save into config.log some information that might help in debugging.
+ {
+ echo
+
+ $as_echo "## ---------------- ##
+## Cache variables. ##
+## ---------------- ##"
+ echo
+ # The following way of writing the cache mishandles newlines in values,
+(
+ for ac_var in `(set) 2>&1 | sed -n '\''s/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'\''`; do
+ eval ac_val=\$$ac_var
+ case $ac_val in #(
+ *${as_nl}*)
+ case $ac_var in #(
+ *_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5
+$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;;
+ esac
+ case $ac_var in #(
+ _ | IFS | as_nl) ;; #(
+ BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #(
+ *) { eval $ac_var=; unset $ac_var;} ;;
+ esac ;;
+ esac
+ done
+ (set) 2>&1 |
+ case $as_nl`(ac_space='\'' '\''; set) 2>&1` in #(
+ *${as_nl}ac_space=\ *)
+ sed -n \
+ "s/'\''/'\''\\\\'\'''\''/g;
+ s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\''\\2'\''/p"
+ ;; #(
+ *)
+ sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
+ ;;
+ esac |
+ sort
+)
+ echo
+
+ $as_echo "## ----------------- ##
+## Output variables. ##
+## ----------------- ##"
+ echo
+ for ac_var in $ac_subst_vars
+ do
+ eval ac_val=\$$ac_var
+ case $ac_val in
+ *\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
+ esac
+ $as_echo "$ac_var='\''$ac_val'\''"
+ done | sort
+ echo
+
+ if test -n "$ac_subst_files"; then
+ $as_echo "## ------------------- ##
+## File substitutions. ##
+## ------------------- ##"
+ echo
+ for ac_var in $ac_subst_files
+ do
+ eval ac_val=\$$ac_var
+ case $ac_val in
+ *\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
+ esac
+ $as_echo "$ac_var='\''$ac_val'\''"
+ done | sort
+ echo
+ fi
+
+ if test -s confdefs.h; then
+ $as_echo "## ----------- ##
+## confdefs.h. ##
+## ----------- ##"
+ echo
+ cat confdefs.h
+ echo
+ fi
+ test "$ac_signal" != 0 &&
+ $as_echo "$as_me: caught signal $ac_signal"
+ $as_echo "$as_me: exit $exit_status"
+ } >&5
+ rm -f core *.core core.conftest.* &&
+ rm -f -r conftest* confdefs* conf$$* $ac_clean_files &&
+ exit $exit_status
+' 0
+for ac_signal in 1 2 13 15; do
+ trap 'ac_signal='$ac_signal'; as_fn_exit 1' $ac_signal
+done
+ac_signal=0
+
+# confdefs.h avoids OS command line length limits that DEFS can exceed.
+rm -f -r conftest* confdefs.h
+
+$as_echo "/* confdefs.h */" > confdefs.h
+
+# Predefined preprocessor variables.
+
+cat >>confdefs.h <<_ACEOF
+#define PACKAGE_NAME "$PACKAGE_NAME"
+_ACEOF
+
+cat >>confdefs.h <<_ACEOF
+#define PACKAGE_TARNAME "$PACKAGE_TARNAME"
+_ACEOF
+
+cat >>confdefs.h <<_ACEOF
+#define PACKAGE_VERSION "$PACKAGE_VERSION"
+_ACEOF
+
+cat >>confdefs.h <<_ACEOF
+#define PACKAGE_STRING "$PACKAGE_STRING"
+_ACEOF
+
+cat >>confdefs.h <<_ACEOF
+#define PACKAGE_BUGREPORT "$PACKAGE_BUGREPORT"
+_ACEOF
+
+cat >>confdefs.h <<_ACEOF
+#define PACKAGE_URL "$PACKAGE_URL"
+_ACEOF
+
+
+# Let the site file select an alternate cache file if it wants to.
+# Prefer an explicitly selected file to automatically selected ones.
+ac_site_file1=NONE
+ac_site_file2=NONE
+if test -n "$CONFIG_SITE"; then
+ # We do not want a PATH search for config.site.
+ case $CONFIG_SITE in #((
+ -*) ac_site_file1=./$CONFIG_SITE;;
+ */*) ac_site_file1=$CONFIG_SITE;;
+ *) ac_site_file1=./$CONFIG_SITE;;
+ esac
+elif test "x$prefix" != xNONE; then
+ ac_site_file1=$prefix/share/config.site
+ ac_site_file2=$prefix/etc/config.site
+else
+ ac_site_file1=$ac_default_prefix/share/config.site
+ ac_site_file2=$ac_default_prefix/etc/config.site
+fi
+for ac_site_file in "$ac_site_file1" "$ac_site_file2"
+do
+ test "x$ac_site_file" = xNONE && continue
+ if test /dev/null != "$ac_site_file" && test -r "$ac_site_file"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: loading site script $ac_site_file" >&5
+$as_echo "$as_me: loading site script $ac_site_file" >&6;}
+ sed 's/^/| /' "$ac_site_file" >&5
+ . "$ac_site_file" \
+ || { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
+$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
+as_fn_error $? "failed to load site script $ac_site_file
+See \`config.log' for more details" "$LINENO" 5; }
+ fi
+done
+
+if test -r "$cache_file"; then
+ # Some versions of bash will fail to source /dev/null (special files
+ # actually), so we avoid doing that. DJGPP emulates it as a regular file.
+ if test /dev/null != "$cache_file" && test -f "$cache_file"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: loading cache $cache_file" >&5
+$as_echo "$as_me: loading cache $cache_file" >&6;}
+ case $cache_file in
+ [\\/]* | ?:[\\/]* ) . "$cache_file";;
+ *) . "./$cache_file";;
+ esac
+ fi
+else
+ { $as_echo "$as_me:${as_lineno-$LINENO}: creating cache $cache_file" >&5
+$as_echo "$as_me: creating cache $cache_file" >&6;}
+ >$cache_file
+fi
+
+# Check that the precious variables saved in the cache have kept the same
+# value.
+ac_cache_corrupted=false
+for ac_var in $ac_precious_vars; do
+ eval ac_old_set=\$ac_cv_env_${ac_var}_set
+ eval ac_new_set=\$ac_env_${ac_var}_set
+ eval ac_old_val=\$ac_cv_env_${ac_var}_value
+ eval ac_new_val=\$ac_env_${ac_var}_value
+ case $ac_old_set,$ac_new_set in
+ set,)
+ { $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5
+$as_echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;}
+ ac_cache_corrupted=: ;;
+ ,set)
+ { $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was not set in the previous run" >&5
+$as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;}
+ ac_cache_corrupted=: ;;
+ ,);;
+ *)
+ if test "x$ac_old_val" != "x$ac_new_val"; then
+ # differences in whitespace do not lead to failure.
+ ac_old_val_w=`echo x $ac_old_val`
+ ac_new_val_w=`echo x $ac_new_val`
+ if test "$ac_old_val_w" != "$ac_new_val_w"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' has changed since the previous run:" >&5
+$as_echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;}
+ ac_cache_corrupted=:
+ else
+ { $as_echo "$as_me:${as_lineno-$LINENO}: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&5
+$as_echo "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;}
+ eval $ac_var=\$ac_old_val
+ fi
+ { $as_echo "$as_me:${as_lineno-$LINENO}: former value: \`$ac_old_val'" >&5
+$as_echo "$as_me: former value: \`$ac_old_val'" >&2;}
+ { $as_echo "$as_me:${as_lineno-$LINENO}: current value: \`$ac_new_val'" >&5
+$as_echo "$as_me: current value: \`$ac_new_val'" >&2;}
+ fi;;
+ esac
+ # Pass precious variables to config.status.
+ if test "$ac_new_set" = set; then
+ case $ac_new_val in
+ *\'*) ac_arg=$ac_var=`$as_echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;;
+ *) ac_arg=$ac_var=$ac_new_val ;;
+ esac
+ case " $ac_configure_args " in
+ *" '$ac_arg' "*) ;; # Avoid dups. Use of quotes ensures accuracy.
+ *) as_fn_append ac_configure_args " '$ac_arg'" ;;
+ esac
+ fi
+done
+if $ac_cache_corrupted; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
+$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
+ { $as_echo "$as_me:${as_lineno-$LINENO}: error: changes in the environment can compromise the build" >&5
+$as_echo "$as_me: error: changes in the environment can compromise the build" >&2;}
+ as_fn_error $? "run \`make distclean' and/or \`rm $cache_file' and start over" "$LINENO" 5
+fi
+## -------------------- ##
+## Main body of script. ##
+## -------------------- ##
+
+ac_ext=c
+ac_cpp='$CPP $CPPFLAGS'
+ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
+ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
+ac_compiler_gnu=$ac_cv_c_compiler_gnu
+
+
+
+
+for ac_prog in inkscape
+do
+ # Extract the first word of "$ac_prog", so it can be a program name with args.
+set dummy $ac_prog; ac_word=$2
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
+$as_echo_n "checking for $ac_word... " >&6; }
+if ${ac_cv_prog_INKSCAPE+:} false; then :
+ $as_echo_n "(cached) " >&6
+else
+ if test -n "$INKSCAPE"; then
+ ac_cv_prog_INKSCAPE="$INKSCAPE" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_INKSCAPE="$ac_prog"
+ $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+ done
+IFS=$as_save_IFS
+
+fi
+fi
+INKSCAPE=$ac_cv_prog_INKSCAPE
+if test -n "$INKSCAPE"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $INKSCAPE" >&5
+$as_echo "$INKSCAPE" >&6; }
+else
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
+$as_echo "no" >&6; }
+fi
+
+
+ test -n "$INKSCAPE" && break
+done
+
+for ac_prog in scour
+do
+ # Extract the first word of "$ac_prog", so it can be a program name with args.
+set dummy $ac_prog; ac_word=$2
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
+$as_echo_n "checking for $ac_word... " >&6; }
+if ${ac_cv_prog_SCOUR+:} false; then :
+ $as_echo_n "(cached) " >&6
+else
+ if test -n "$SCOUR"; then
+ ac_cv_prog_SCOUR="$SCOUR" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_SCOUR="$ac_prog"
+ $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+ done
+IFS=$as_save_IFS
+
+fi
+fi
+SCOUR=$ac_cv_prog_SCOUR
+if test -n "$SCOUR"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $SCOUR" >&5
+$as_echo "$SCOUR" >&6; }
+else
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
+$as_echo "no" >&6; }
+fi
+
+
+ test -n "$SCOUR" && break
+done
+
+for ac_prog in sfnt2woff
+do
+ # Extract the first word of "$ac_prog", so it can be a program name with args.
+set dummy $ac_prog; ac_word=$2
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
+$as_echo_n "checking for $ac_word... " >&6; }
+if ${ac_cv_prog_SFNT2WOFF+:} false; then :
+ $as_echo_n "(cached) " >&6
+else
+ if test -n "$SFNT2WOFF"; then
+ ac_cv_prog_SFNT2WOFF="$SFNT2WOFF" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_SFNT2WOFF="$ac_prog"
+ $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+ done
+IFS=$as_save_IFS
+
+fi
+fi
+SFNT2WOFF=$ac_cv_prog_SFNT2WOFF
+if test -n "$SFNT2WOFF"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $SFNT2WOFF" >&5
+$as_echo "$SFNT2WOFF" >&6; }
+else
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
+$as_echo "no" >&6; }
+fi
+
+
+ test -n "$SFNT2WOFF" && break
+done
+
+for ac_prog in unzip
+do
+ # Extract the first word of "$ac_prog", so it can be a program name with args.
+set dummy $ac_prog; ac_word=$2
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
+$as_echo_n "checking for $ac_word... " >&6; }
+if ${ac_cv_prog_UNZIP+:} false; then :
+ $as_echo_n "(cached) " >&6
+else
+ if test -n "$UNZIP"; then
+ ac_cv_prog_UNZIP="$UNZIP" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_UNZIP="$ac_prog"
+ $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+ done
+IFS=$as_save_IFS
+
+fi
+fi
+UNZIP=$ac_cv_prog_UNZIP
+if test -n "$UNZIP"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $UNZIP" >&5
+$as_echo "$UNZIP" >&6; }
+else
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
+$as_echo "no" >&6; }
+fi
+
+
+ test -n "$UNZIP" && break
+done
+
+for ac_prog in xsltproc
+do
+ # Extract the first word of "$ac_prog", so it can be a program name with args.
+set dummy $ac_prog; ac_word=$2
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
+$as_echo_n "checking for $ac_word... " >&6; }
+if ${ac_cv_prog_XSLTPROC+:} false; then :
+ $as_echo_n "(cached) " >&6
+else
+ if test -n "$XSLTPROC"; then
+ ac_cv_prog_XSLTPROC="$XSLTPROC" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_XSLTPROC="$ac_prog"
+ $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+ done
+IFS=$as_save_IFS
+
+fi
+fi
+XSLTPROC=$ac_cv_prog_XSLTPROC
+if test -n "$XSLTPROC"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $XSLTPROC" >&5
+$as_echo "$XSLTPROC" >&6; }
+else
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
+$as_echo "no" >&6; }
+fi
+
+
+ test -n "$XSLTPROC" && break
+done
+
+for ac_prog in wget
+do
+ # Extract the first word of "$ac_prog", so it can be a program name with args.
+set dummy $ac_prog; ac_word=$2
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
+$as_echo_n "checking for $ac_word... " >&6; }
+if ${ac_cv_prog_WGET+:} false; then :
+ $as_echo_n "(cached) " >&6
+else
+ if test -n "$WGET"; then
+ ac_cv_prog_WGET="$WGET" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_WGET="$ac_prog"
+ $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+ done
+IFS=$as_save_IFS
+
+fi
+fi
+WGET=$ac_cv_prog_WGET
+if test -n "$WGET"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $WGET" >&5
+$as_echo "$WGET" >&6; }
+else
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
+$as_echo "no" >&6; }
+fi
+
+
+ test -n "$WGET" && break
+done
+
+for ac_prog in zip
+do
+ # Extract the first word of "$ac_prog", so it can be a program name with args.
+set dummy $ac_prog; ac_word=$2
+{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
+$as_echo_n "checking for $ac_word... " >&6; }
+if ${ac_cv_prog_ZIP+:} false; then :
+ $as_echo_n "(cached) " >&6
+else
+ if test -n "$ZIP"; then
+ ac_cv_prog_ZIP="$ZIP" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_ZIP="$ac_prog"
+ $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+ done
+IFS=$as_save_IFS
+
+fi
+fi
+ZIP=$ac_cv_prog_ZIP
+if test -n "$ZIP"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ZIP" >&5
+$as_echo "$ZIP" >&6; }
+else
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
+$as_echo "no" >&6; }
+fi
+
+
+ test -n "$ZIP" && break
+done
+
+
+if test -z "$INKSCAPE" ||
+ test -z "$SCOUR" ||
+ test -z "$SFNT2WOFF" ||
+ test -z "$UNZIP" ||
+ test -z "$XSLTPROC" ||
+ test -z "$WGET" ||
+ test -z "$ZIP"; then
+ as_fn_error $? "Missing dependencies. Please read the README.md file." "$LINENO" 5
+fi
+
+ac_config_files="$ac_config_files Makefile"
+
+cat >confcache <<\_ACEOF
+# This file is a shell script that caches the results of configure
+# tests run on this system so they can be shared between configure
+# scripts and configure runs, see configure's option --config-cache.
+# It is not useful on other systems. If it contains results you don't
+# want to keep, you may remove or edit it.
+#
+# config.status only pays attention to the cache file if you give it
+# the --recheck option to rerun configure.
+#
+# `ac_cv_env_foo' variables (set or unset) will be overridden when
+# loading this file, other *unset* `ac_cv_foo' will be assigned the
+# following values.
+
+_ACEOF
+
+# The following way of writing the cache mishandles newlines in values,
+# but we know of no workaround that is simple, portable, and efficient.
+# So, we kill variables containing newlines.
+# Ultrix sh set writes to stderr and can't be redirected directly,
+# and sets the high bit in the cache file unless we assign to the vars.
+(
+ for ac_var in `(set) 2>&1 | sed -n 's/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'`; do
+ eval ac_val=\$$ac_var
+ case $ac_val in #(
+ *${as_nl}*)
+ case $ac_var in #(
+ *_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5
+$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;;
+ esac
+ case $ac_var in #(
+ _ | IFS | as_nl) ;; #(
+ BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #(
+ *) { eval $ac_var=; unset $ac_var;} ;;
+ esac ;;
+ esac
+ done
+
+ (set) 2>&1 |
+ case $as_nl`(ac_space=' '; set) 2>&1` in #(
+ *${as_nl}ac_space=\ *)
+ # `set' does not quote correctly, so add quotes: double-quote
+ # substitution turns \\\\ into \\, and sed turns \\ into \.
+ sed -n \
+ "s/'/'\\\\''/g;
+ s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\\2'/p"
+ ;; #(
+ *)
+ # `set' quotes correctly as required by POSIX, so do not add quotes.
+ sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
+ ;;
+ esac |
+ sort
+) |
+ sed '
+ /^ac_cv_env_/b end
+ t clear
+ :clear
+ s/^\([^=]*\)=\(.*[{}].*\)$/test "${\1+set}" = set || &/
+ t end
+ s/^\([^=]*\)=\(.*\)$/\1=${\1=\2}/
+ :end' >>confcache
+if diff "$cache_file" confcache >/dev/null 2>&1; then :; else
+ if test -w "$cache_file"; then
+ if test "x$cache_file" != "x/dev/null"; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: updating cache $cache_file" >&5
+$as_echo "$as_me: updating cache $cache_file" >&6;}
+ if test ! -f "$cache_file" || test -h "$cache_file"; then
+ cat confcache >"$cache_file"
+ else
+ case $cache_file in #(
+ */* | ?:*)
+ mv -f confcache "$cache_file"$$ &&
+ mv -f "$cache_file"$$ "$cache_file" ;; #(
+ *)
+ mv -f confcache "$cache_file" ;;
+ esac
+ fi
+ fi
+ else
+ { $as_echo "$as_me:${as_lineno-$LINENO}: not updating unwritable cache $cache_file" >&5
+$as_echo "$as_me: not updating unwritable cache $cache_file" >&6;}
+ fi
+fi
+rm -f confcache
+
+test "x$prefix" = xNONE && prefix=$ac_default_prefix
+# Let make expand exec_prefix.
+test "x$exec_prefix" = xNONE && exec_prefix='${prefix}'
+
+# Transform confdefs.h into DEFS.
+# Protect against shell expansion while executing Makefile rules.
+# Protect against Makefile macro expansion.
+#
+# If the first sed substitution is executed (which looks for macros that
+# take arguments), then branch to the quote section. Otherwise,
+# look for a macro that doesn't take arguments.
+ac_script='
+:mline
+/\\$/{
+ N
+ s,\\\n,,
+ b mline
+}
+t clear
+:clear
+s/^[ ]*#[ ]*define[ ][ ]*\([^ (][^ (]*([^)]*)\)[ ]*\(.*\)/-D\1=\2/g
+t quote
+s/^[ ]*#[ ]*define[ ][ ]*\([^ ][^ ]*\)[ ]*\(.*\)/-D\1=\2/g
+t quote
+b any
+:quote
+s/[ `~#$^&*(){}\\|;'\''"<>?]/\\&/g
+s/\[/\\&/g
+s/\]/\\&/g
+s/\$/$$/g
+H
+:any
+${
+ g
+ s/^\n//
+ s/\n/ /g
+ p
+}
+'
+DEFS=`sed -n "$ac_script" confdefs.h`
+
+
+ac_libobjs=
+ac_ltlibobjs=
+U=
+for ac_i in : $LIBOBJS; do test "x$ac_i" = x: && continue
+ # 1. Remove the extension, and $U if already installed.
+ ac_script='s/\$U\././;s/\.o$//;s/\.obj$//'
+ ac_i=`$as_echo "$ac_i" | sed "$ac_script"`
+ # 2. Prepend LIBOBJDIR. When used with automake>=1.10 LIBOBJDIR
+ # will be set to the directory where LIBOBJS objects are built.
+ as_fn_append ac_libobjs " \${LIBOBJDIR}$ac_i\$U.$ac_objext"
+ as_fn_append ac_ltlibobjs " \${LIBOBJDIR}$ac_i"'$U.lo'
+done
+LIBOBJS=$ac_libobjs
+
+LTLIBOBJS=$ac_ltlibobjs
+
+
+
+: "${CONFIG_STATUS=./config.status}"
+ac_write_fail=0
+ac_clean_files_save=$ac_clean_files
+ac_clean_files="$ac_clean_files $CONFIG_STATUS"
+{ $as_echo "$as_me:${as_lineno-$LINENO}: creating $CONFIG_STATUS" >&5
+$as_echo "$as_me: creating $CONFIG_STATUS" >&6;}
+as_write_fail=0
+cat >$CONFIG_STATUS <<_ASEOF || as_write_fail=1
+#! $SHELL
+# Generated by $as_me.
+# Run this file to recreate the current configuration.
+# Compiler output produced by configure, useful for debugging
+# configure, is in config.log if it exists.
+
+debug=false
+ac_cs_recheck=false
+ac_cs_silent=false
+
+SHELL=\${CONFIG_SHELL-$SHELL}
+export SHELL
+_ASEOF
+cat >>$CONFIG_STATUS <<\_ASEOF || as_write_fail=1
+## -------------------- ##
+## M4sh Initialization. ##
+## -------------------- ##
+
+# Be more Bourne compatible
+DUALCASE=1; export DUALCASE # for MKS sh
+if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then :
+ emulate sh
+ NULLCMD=:
+ # Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
+ # is contrary to our usage. Disable this feature.
+ alias -g '${1+"$@"}'='"$@"'
+ setopt NO_GLOB_SUBST
+else
+ case `(set -o) 2>/dev/null` in #(
+ *posix*) :
+ set -o posix ;; #(
+ *) :
+ ;;
+esac
+fi
+
+
+as_nl='
+'
+export as_nl
+# Printing a long string crashes Solaris 7 /usr/bin/printf.
+as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
+as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
+as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
+# Prefer a ksh shell builtin over an external printf program on Solaris,
+# but without wasting forks for bash or zsh.
+if test -z "$BASH_VERSION$ZSH_VERSION" \
+ && (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
+ as_echo='print -r --'
+ as_echo_n='print -rn --'
+elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
+ as_echo='printf %s\n'
+ as_echo_n='printf %s'
+else
+ if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
+ as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
+ as_echo_n='/usr/ucb/echo -n'
+ else
+ as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
+ as_echo_n_body='eval
+ arg=$1;
+ case $arg in #(
+ *"$as_nl"*)
+ expr "X$arg" : "X\\(.*\\)$as_nl";
+ arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
+ esac;
+ expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
+ '
+ export as_echo_n_body
+ as_echo_n='sh -c $as_echo_n_body as_echo'
+ fi
+ export as_echo_body
+ as_echo='sh -c $as_echo_body as_echo'
+fi
+
+# The user is always right.
+if test "${PATH_SEPARATOR+set}" != set; then
+ PATH_SEPARATOR=:
+ (PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
+ (PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
+ PATH_SEPARATOR=';'
+ }
+fi
+
+
+# IFS
+# We need space, tab and new line, in precisely that order. Quoting is
+# there to prevent editors from complaining about space-tab.
+# (If _AS_PATH_WALK were called with IFS unset, it would disable word
+# splitting by setting IFS to empty value.)
+IFS=" "" $as_nl"
+
+# Find who we are. Look in the path if we contain no directory separator.
+as_myself=
+case $0 in #((
+ *[\\/]* ) as_myself=$0 ;;
+ *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
+ done
+IFS=$as_save_IFS
+
+ ;;
+esac
+# We did not find ourselves, most probably we were run as `sh COMMAND'
+# in which case we are not to be found in the path.
+if test "x$as_myself" = x; then
+ as_myself=$0
+fi
+if test ! -f "$as_myself"; then
+ $as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
+ exit 1
+fi
+
+# Unset variables that we do not need and which cause bugs (e.g. in
+# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1"
+# suppresses any "Segmentation fault" message there. '((' could
+# trigger a bug in pdksh 5.2.14.
+for as_var in BASH_ENV ENV MAIL MAILPATH
+do eval test x\${$as_var+set} = xset \
+ && ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || :
+done
+PS1='$ '
+PS2='> '
+PS4='+ '
+
+# NLS nuisances.
+LC_ALL=C
+export LC_ALL
+LANGUAGE=C
+export LANGUAGE
+
+# CDPATH.
+(unset CDPATH) >/dev/null 2>&1 && unset CDPATH
+
+
+# as_fn_error STATUS ERROR [LINENO LOG_FD]
+# ----------------------------------------
+# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are
+# provided, also output the error to LOG_FD, referencing LINENO. Then exit the
+# script with STATUS, using 1 if that was 0.
+as_fn_error ()
+{
+ as_status=$1; test $as_status -eq 0 && as_status=1
+ if test "$4"; then
+ as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
+ $as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4
+ fi
+ $as_echo "$as_me: error: $2" >&2
+ as_fn_exit $as_status
+} # as_fn_error
+
+
+# as_fn_set_status STATUS
+# -----------------------
+# Set $? to STATUS, without forking.
+as_fn_set_status ()
+{
+ return $1
+} # as_fn_set_status
+
+# as_fn_exit STATUS
+# -----------------
+# Exit the shell with STATUS, even in a "trap 0" or "set -e" context.
+as_fn_exit ()
+{
+ set +e
+ as_fn_set_status $1
+ exit $1
+} # as_fn_exit
+
+# as_fn_unset VAR
+# ---------------
+# Portably unset VAR.
+as_fn_unset ()
+{
+ { eval $1=; unset $1;}
+}
+as_unset=as_fn_unset
+# as_fn_append VAR VALUE
+# ----------------------
+# Append the text in VALUE to the end of the definition contained in VAR. Take
+# advantage of any shell optimizations that allow amortized linear growth over
+# repeated appends, instead of the typical quadratic growth present in naive
+# implementations.
+if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then :
+ eval 'as_fn_append ()
+ {
+ eval $1+=\$2
+ }'
+else
+ as_fn_append ()
+ {
+ eval $1=\$$1\$2
+ }
+fi # as_fn_append
+
+# as_fn_arith ARG...
+# ------------------
+# Perform arithmetic evaluation on the ARGs, and store the result in the
+# global $as_val. Take advantage of shells that can avoid forks. The arguments
+# must be portable across $(()) and expr.
+if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then :
+ eval 'as_fn_arith ()
+ {
+ as_val=$(( $* ))
+ }'
+else
+ as_fn_arith ()
+ {
+ as_val=`expr "$@" || test $? -eq 1`
+ }
+fi # as_fn_arith
+
+
+if expr a : '\(a\)' >/dev/null 2>&1 &&
+ test "X`expr 00001 : '.*\(...\)'`" = X001; then
+ as_expr=expr
+else
+ as_expr=false
+fi
+
+if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
+ as_basename=basename
+else
+ as_basename=false
+fi
+
+if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
+ as_dirname=dirname
+else
+ as_dirname=false
+fi
+
+as_me=`$as_basename -- "$0" ||
+$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
+ X"$0" : 'X\(//\)$' \| \
+ X"$0" : 'X\(/\)' \| . 2>/dev/null ||
+$as_echo X/"$0" |
+ sed '/^.*\/\([^/][^/]*\)\/*$/{
+ s//\1/
+ q
+ }
+ /^X\/\(\/\/\)$/{
+ s//\1/
+ q
+ }
+ /^X\/\(\/\).*/{
+ s//\1/
+ q
+ }
+ s/.*/./; q'`
+
+# Avoid depending upon Character Ranges.
+as_cr_letters='abcdefghijklmnopqrstuvwxyz'
+as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
+as_cr_Letters=$as_cr_letters$as_cr_LETTERS
+as_cr_digits='0123456789'
+as_cr_alnum=$as_cr_Letters$as_cr_digits
+
+ECHO_C= ECHO_N= ECHO_T=
+case `echo -n x` in #(((((
+-n*)
+ case `echo 'xy\c'` in
+ *c*) ECHO_T=' ';; # ECHO_T is single tab character.
+ xy) ECHO_C='\c';;
+ *) echo `echo ksh88 bug on AIX 6.1` > /dev/null
+ ECHO_T=' ';;
+ esac;;
+*)
+ ECHO_N='-n';;
+esac
+
+rm -f conf$$ conf$$.exe conf$$.file
+if test -d conf$$.dir; then
+ rm -f conf$$.dir/conf$$.file
+else
+ rm -f conf$$.dir
+ mkdir conf$$.dir 2>/dev/null
+fi
+if (echo >conf$$.file) 2>/dev/null; then
+ if ln -s conf$$.file conf$$ 2>/dev/null; then
+ as_ln_s='ln -s'
+ # ... but there are two gotchas:
+ # 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
+ # 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
+ # In both cases, we have to default to `cp -pR'.
+ ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
+ as_ln_s='cp -pR'
+ elif ln conf$$.file conf$$ 2>/dev/null; then
+ as_ln_s=ln
+ else
+ as_ln_s='cp -pR'
+ fi
+else
+ as_ln_s='cp -pR'
+fi
+rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
+rmdir conf$$.dir 2>/dev/null
+
+
+# as_fn_mkdir_p
+# -------------
+# Create "$as_dir" as a directory, including parents if necessary.
+as_fn_mkdir_p ()
+{
+
+ case $as_dir in #(
+ -*) as_dir=./$as_dir;;
+ esac
+ test -d "$as_dir" || eval $as_mkdir_p || {
+ as_dirs=
+ while :; do
+ case $as_dir in #(
+ *\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
+ *) as_qdir=$as_dir;;
+ esac
+ as_dirs="'$as_qdir' $as_dirs"
+ as_dir=`$as_dirname -- "$as_dir" ||
+$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
+ X"$as_dir" : 'X\(//\)[^/]' \| \
+ X"$as_dir" : 'X\(//\)$' \| \
+ X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
+$as_echo X"$as_dir" |
+ sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
+ s//\1/
+ q
+ }
+ /^X\(\/\/\)[^/].*/{
+ s//\1/
+ q
+ }
+ /^X\(\/\/\)$/{
+ s//\1/
+ q
+ }
+ /^X\(\/\).*/{
+ s//\1/
+ q
+ }
+ s/.*/./; q'`
+ test -d "$as_dir" && break
+ done
+ test -z "$as_dirs" || eval "mkdir $as_dirs"
+ } || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir"
+
+
+} # as_fn_mkdir_p
+if mkdir -p . 2>/dev/null; then
+ as_mkdir_p='mkdir -p "$as_dir"'
+else
+ test -d ./-p && rmdir ./-p
+ as_mkdir_p=false
+fi
+
+
+# as_fn_executable_p FILE
+# -----------------------
+# Test if FILE is an executable regular file.
+as_fn_executable_p ()
+{
+ test -f "$1" && test -x "$1"
+} # as_fn_executable_p
+as_test_x='test -x'
+as_executable_p=as_fn_executable_p
+
+# Sed expression to map a string onto a valid CPP name.
+as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
+
+# Sed expression to map a string onto a valid variable name.
+as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
+
+
+exec 6>&1
+## ----------------------------------- ##
+## Main body of $CONFIG_STATUS script. ##
+## ----------------------------------- ##
+_ASEOF
+test $as_write_fail = 0 && chmod +x $CONFIG_STATUS || ac_write_fail=1
+
+cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
+# Save the log message, to keep $0 and so on meaningful, and to
+# report actual input values of CONFIG_FILES etc. instead of their
+# values after options handling.
+ac_log="
+This file was extended by MathML Logo $as_me 1.0, which was
+generated by GNU Autoconf 2.69. Invocation command line was
+
+ CONFIG_FILES = $CONFIG_FILES
+ CONFIG_HEADERS = $CONFIG_HEADERS
+ CONFIG_LINKS = $CONFIG_LINKS
+ CONFIG_COMMANDS = $CONFIG_COMMANDS
+ $ $0 $@
+
+on `(hostname || uname -n) 2>/dev/null | sed 1q`
+"
+
+_ACEOF
+
+case $ac_config_files in *"
+"*) set x $ac_config_files; shift; ac_config_files=$*;;
+esac
+
+
+
+cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
+# Files that config.status was made for.
+config_files="$ac_config_files"
+
+_ACEOF
+
+cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
+ac_cs_usage="\
+\`$as_me' instantiates files and other configuration actions
+from templates according to the current configuration. Unless the files
+and actions are specified as TAGs, all are instantiated by default.
+
+Usage: $0 [OPTION]... [TAG]...
+
+ -h, --help print this help, then exit
+ -V, --version print version number and configuration settings, then exit
+ --config print configuration, then exit
+ -q, --quiet, --silent
+ do not print progress messages
+ -d, --debug don't remove temporary files
+ --recheck update $as_me by reconfiguring in the same conditions
+ --file=FILE[:TEMPLATE]
+ instantiate the configuration file FILE
+
+Configuration files:
+$config_files
+
+Report bugs to the package provider."
+
+_ACEOF
+cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
+ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
+ac_cs_version="\\
+MathML Logo config.status 1.0
+configured by $0, generated by GNU Autoconf 2.69,
+ with options \\"\$ac_cs_config\\"
+
+Copyright (C) 2012 Free Software Foundation, Inc.
+This config.status script is free software; the Free Software Foundation
+gives unlimited permission to copy, distribute and modify it."
+
+ac_pwd='$ac_pwd'
+srcdir='$srcdir'
+test -n "\$AWK" || AWK=awk
+_ACEOF
+
+cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
+# The default lists apply if the user does not specify any file.
+ac_need_defaults=:
+while test $# != 0
+do
+ case $1 in
+ --*=?*)
+ ac_option=`expr "X$1" : 'X\([^=]*\)='`
+ ac_optarg=`expr "X$1" : 'X[^=]*=\(.*\)'`
+ ac_shift=:
+ ;;
+ --*=)
+ ac_option=`expr "X$1" : 'X\([^=]*\)='`
+ ac_optarg=
+ ac_shift=:
+ ;;
+ *)
+ ac_option=$1
+ ac_optarg=$2
+ ac_shift=shift
+ ;;
+ esac
+
+ case $ac_option in
+ # Handling of the options.
+ -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
+ ac_cs_recheck=: ;;
+ --version | --versio | --versi | --vers | --ver | --ve | --v | -V )
+ $as_echo "$ac_cs_version"; exit ;;
+ --config | --confi | --conf | --con | --co | --c )
+ $as_echo "$ac_cs_config"; exit ;;
+ --debug | --debu | --deb | --de | --d | -d )
+ debug=: ;;
+ --file | --fil | --fi | --f )
+ $ac_shift
+ case $ac_optarg in
+ *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;
+ '') as_fn_error $? "missing file argument" ;;
+ esac
+ as_fn_append CONFIG_FILES " '$ac_optarg'"
+ ac_need_defaults=false;;
+ --he | --h | --help | --hel | -h )
+ $as_echo "$ac_cs_usage"; exit ;;
+ -q | -quiet | --quiet | --quie | --qui | --qu | --q \
+ | -silent | --silent | --silen | --sile | --sil | --si | --s)
+ ac_cs_silent=: ;;
+
+ # This is an error.
+ -*) as_fn_error $? "unrecognized option: \`$1'
+Try \`$0 --help' for more information." ;;
+
+ *) as_fn_append ac_config_targets " $1"
+ ac_need_defaults=false ;;
+
+ esac
+ shift
+done
+
+ac_configure_extra_args=
+
+if $ac_cs_silent; then
+ exec 6>/dev/null
+ ac_configure_extra_args="$ac_configure_extra_args --silent"
+fi
+
+_ACEOF
+cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
+if \$ac_cs_recheck; then
+ set X $SHELL '$0' $ac_configure_args \$ac_configure_extra_args --no-create --no-recursion
+ shift
+ \$as_echo "running CONFIG_SHELL=$SHELL \$*" >&6
+ CONFIG_SHELL='$SHELL'
+ export CONFIG_SHELL
+ exec "\$@"
+fi
+
+_ACEOF
+cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
+exec 5>>config.log
+{
+ echo
+ sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
+## Running $as_me. ##
+_ASBOX
+ $as_echo "$ac_log"
+} >&5
+
+_ACEOF
+cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
+_ACEOF
+
+cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
+
+# Handling of arguments.
+for ac_config_target in $ac_config_targets
+do
+ case $ac_config_target in
+ "Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;;
+
+ *) as_fn_error $? "invalid argument: \`$ac_config_target'" "$LINENO" 5;;
+ esac
+done
+
+
+# If the user did not use the arguments to specify the items to instantiate,
+# then the envvar interface is used. Set only those that are not.
+# We use the long form for the default assignment because of an extremely
+# bizarre bug on SunOS 4.1.3.
+if $ac_need_defaults; then
+ test "${CONFIG_FILES+set}" = set || CONFIG_FILES=$config_files
+fi
+
+# Have a temporary directory for convenience. Make it in the build tree
+# simply because there is no reason against having it here, and in addition,
+# creating and moving files from /tmp can sometimes cause problems.
+# Hook for its removal unless debugging.
+# Note that there is a small window in which the directory will not be cleaned:
+# after its creation but before its name has been assigned to `$tmp'.
+$debug ||
+{
+ tmp= ac_tmp=
+ trap 'exit_status=$?
+ : "${ac_tmp:=$tmp}"
+ { test ! -d "$ac_tmp" || rm -fr "$ac_tmp"; } && exit $exit_status
+' 0
+ trap 'as_fn_exit 1' 1 2 13 15
+}
+# Create a (secure) tmp directory for tmp files.
+
+{
+ tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` &&
+ test -d "$tmp"
+} ||
+{
+ tmp=./conf$$-$RANDOM
+ (umask 077 && mkdir "$tmp")
+} || as_fn_error $? "cannot create a temporary directory in ." "$LINENO" 5
+ac_tmp=$tmp
+
+# Set up the scripts for CONFIG_FILES section.
+# No need to generate them if there are no CONFIG_FILES.
+# This happens for instance with `./config.status config.h'.
+if test -n "$CONFIG_FILES"; then
+
+
+ac_cr=`echo X | tr X '\015'`
+# On cygwin, bash can eat \r inside `` if the user requested igncr.
+# But we know of no other shell where ac_cr would be empty at this
+# point, so we can use a bashism as a fallback.
+if test "x$ac_cr" = x; then
+ eval ac_cr=\$\'\\r\'
+fi
+ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' /dev/null`
+if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then
+ ac_cs_awk_cr='\\r'
+else
+ ac_cs_awk_cr=$ac_cr
+fi
+
+echo 'BEGIN {' >"$ac_tmp/subs1.awk" &&
+_ACEOF
+
+
+{
+ echo "cat >conf$$subs.awk <<_ACEOF" &&
+ echo "$ac_subst_vars" | sed 's/.*/&!$&$ac_delim/' &&
+ echo "_ACEOF"
+} >conf$$subs.sh ||
+ as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
+ac_delim_num=`echo "$ac_subst_vars" | grep -c '^'`
+ac_delim='%!_!# '
+for ac_last_try in false false false false false :; do
+ . ./conf$$subs.sh ||
+ as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
+
+ ac_delim_n=`sed -n "s/.*$ac_delim\$/X/p" conf$$subs.awk | grep -c X`
+ if test $ac_delim_n = $ac_delim_num; then
+ break
+ elif $ac_last_try; then
+ as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
+ else
+ ac_delim="$ac_delim!$ac_delim _$ac_delim!! "
+ fi
+done
+rm -f conf$$subs.sh
+
+cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
+cat >>"\$ac_tmp/subs1.awk" <<\\_ACAWK &&
+_ACEOF
+sed -n '
+h
+s/^/S["/; s/!.*/"]=/
+p
+g
+s/^[^!]*!//
+:repl
+t repl
+s/'"$ac_delim"'$//
+t delim
+:nl
+h
+s/\(.\{148\}\)..*/\1/
+t more1
+s/["\\]/\\&/g; s/^/"/; s/$/\\n"\\/
+p
+n
+b repl
+:more1
+s/["\\]/\\&/g; s/^/"/; s/$/"\\/
+p
+g
+s/.\{148\}//
+t nl
+:delim
+h
+s/\(.\{148\}\)..*/\1/
+t more2
+s/["\\]/\\&/g; s/^/"/; s/$/"/
+p
+b
+:more2
+s/["\\]/\\&/g; s/^/"/; s/$/"\\/
+p
+g
+s/.\{148\}//
+t delim
+' >$CONFIG_STATUS || ac_write_fail=1
+rm -f conf$$subs.awk
+cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
+_ACAWK
+cat >>"\$ac_tmp/subs1.awk" <<_ACAWK &&
+ for (key in S) S_is_set[key] = 1
+ FS = ""
+
+}
+{
+ line = $ 0
+ nfields = split(line, field, "@")
+ substed = 0
+ len = length(field[1])
+ for (i = 2; i < nfields; i++) {
+ key = field[i]
+ keylen = length(key)
+ if (S_is_set[key]) {
+ value = S[key]
+ line = substr(line, 1, len) "" value "" substr(line, len + keylen + 3)
+ len += length(value) + length(field[++i])
+ substed = 1
+ } else
+ len += 1 + keylen
+ }
+
+ print line
+}
+
+_ACAWK
+_ACEOF
+cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
+if sed "s/$ac_cr//" < /dev/null > /dev/null 2>&1; then
+ sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g"
+else
+ cat
+fi < "$ac_tmp/subs1.awk" > "$ac_tmp/subs.awk" \
+ || as_fn_error $? "could not setup config files machinery" "$LINENO" 5
+_ACEOF
+
+# VPATH may cause trouble with some makes, so we remove sole $(srcdir),
+# ${srcdir} and @srcdir@ entries from VPATH if srcdir is ".", strip leading and
+# trailing colons and then remove the whole line if VPATH becomes empty
+# (actually we leave an empty line to preserve line numbers).
+if test "x$srcdir" = x.; then
+ ac_vpsub='/^[ ]*VPATH[ ]*=[ ]*/{
+h
+s///
+s/^/:/
+s/[ ]*$/:/
+s/:\$(srcdir):/:/g
+s/:\${srcdir}:/:/g
+s/:@srcdir@:/:/g
+s/^:*//
+s/:*$//
+x
+s/\(=[ ]*\).*/\1/
+G
+s/\n//
+s/^[^=]*=[ ]*$//
+}'
+fi
+
+cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
+fi # test -n "$CONFIG_FILES"
+
+
+eval set X " :F $CONFIG_FILES "
+shift
+for ac_tag
+do
+ case $ac_tag in
+ :[FHLC]) ac_mode=$ac_tag; continue;;
+ esac
+ case $ac_mode$ac_tag in
+ :[FHL]*:*);;
+ :L* | :C*:*) as_fn_error $? "invalid tag \`$ac_tag'" "$LINENO" 5;;
+ :[FH]-) ac_tag=-:-;;
+ :[FH]*) ac_tag=$ac_tag:$ac_tag.in;;
+ esac
+ ac_save_IFS=$IFS
+ IFS=:
+ set x $ac_tag
+ IFS=$ac_save_IFS
+ shift
+ ac_file=$1
+ shift
+
+ case $ac_mode in
+ :L) ac_source=$1;;
+ :[FH])
+ ac_file_inputs=
+ for ac_f
+ do
+ case $ac_f in
+ -) ac_f="$ac_tmp/stdin";;
+ *) # Look for the file first in the build tree, then in the source tree
+ # (if the path is not absolute). The absolute path cannot be DOS-style,
+ # because $ac_f cannot contain `:'.
+ test -f "$ac_f" ||
+ case $ac_f in
+ [\\/$]*) false;;
+ *) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";;
+ esac ||
+ as_fn_error 1 "cannot find input file: \`$ac_f'" "$LINENO" 5;;
+ esac
+ case $ac_f in *\'*) ac_f=`$as_echo "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac
+ as_fn_append ac_file_inputs " '$ac_f'"
+ done
+
+ # Let's still pretend it is `configure' which instantiates (i.e., don't
+ # use $as_me), people would be surprised to read:
+ # /* config.h. Generated by config.status. */
+ configure_input='Generated from '`
+ $as_echo "$*" | sed 's|^[^:]*/||;s|:[^:]*/|, |g'
+ `' by configure.'
+ if test x"$ac_file" != x-; then
+ configure_input="$ac_file. $configure_input"
+ { $as_echo "$as_me:${as_lineno-$LINENO}: creating $ac_file" >&5
+$as_echo "$as_me: creating $ac_file" >&6;}
+ fi
+ # Neutralize special characters interpreted by sed in replacement strings.
+ case $configure_input in #(
+ *\&* | *\|* | *\\* )
+ ac_sed_conf_input=`$as_echo "$configure_input" |
+ sed 's/[\\\\&|]/\\\\&/g'`;; #(
+ *) ac_sed_conf_input=$configure_input;;
+ esac
+
+ case $ac_tag in
+ *:-:* | *:-) cat >"$ac_tmp/stdin" \
+ || as_fn_error $? "could not create $ac_file" "$LINENO" 5 ;;
+ esac
+ ;;
+ esac
+
+ ac_dir=`$as_dirname -- "$ac_file" ||
+$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
+ X"$ac_file" : 'X\(//\)[^/]' \| \
+ X"$ac_file" : 'X\(//\)$' \| \
+ X"$ac_file" : 'X\(/\)' \| . 2>/dev/null ||
+$as_echo X"$ac_file" |
+ sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
+ s//\1/
+ q
+ }
+ /^X\(\/\/\)[^/].*/{
+ s//\1/
+ q
+ }
+ /^X\(\/\/\)$/{
+ s//\1/
+ q
+ }
+ /^X\(\/\).*/{
+ s//\1/
+ q
+ }
+ s/.*/./; q'`
+ as_dir="$ac_dir"; as_fn_mkdir_p
+ ac_builddir=.
+
+case "$ac_dir" in
+.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
+*)
+ ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
+ # A ".." for each directory in $ac_dir_suffix.
+ ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
+ case $ac_top_builddir_sub in
+ "") ac_top_builddir_sub=. ac_top_build_prefix= ;;
+ *) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
+ esac ;;
+esac
+ac_abs_top_builddir=$ac_pwd
+ac_abs_builddir=$ac_pwd$ac_dir_suffix
+# for backward compatibility:
+ac_top_builddir=$ac_top_build_prefix
+
+case $srcdir in
+ .) # We are building in place.
+ ac_srcdir=.
+ ac_top_srcdir=$ac_top_builddir_sub
+ ac_abs_top_srcdir=$ac_pwd ;;
+ [\\/]* | ?:[\\/]* ) # Absolute name.
+ ac_srcdir=$srcdir$ac_dir_suffix;
+ ac_top_srcdir=$srcdir
+ ac_abs_top_srcdir=$srcdir ;;
+ *) # Relative name.
+ ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
+ ac_top_srcdir=$ac_top_build_prefix$srcdir
+ ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
+esac
+ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
+
+
+ case $ac_mode in
+ :F)
+ #
+ # CONFIG_FILE
+ #
+
+_ACEOF
+
+cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
+# If the template does not know about datarootdir, expand it.
+# FIXME: This hack should be removed a few years after 2.60.
+ac_datarootdir_hack=; ac_datarootdir_seen=
+ac_sed_dataroot='
+/datarootdir/ {
+ p
+ q
+}
+/@datadir@/p
+/@docdir@/p
+/@infodir@/p
+/@localedir@/p
+/@mandir@/p'
+case `eval "sed -n \"\$ac_sed_dataroot\" $ac_file_inputs"` in
+*datarootdir*) ac_datarootdir_seen=yes;;
+*@datadir@*|*@docdir@*|*@infodir@*|*@localedir@*|*@mandir@*)
+ { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&5
+$as_echo "$as_me: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&2;}
+_ACEOF
+cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
+ ac_datarootdir_hack='
+ s&@datadir@&$datadir&g
+ s&@docdir@&$docdir&g
+ s&@infodir@&$infodir&g
+ s&@localedir@&$localedir&g
+ s&@mandir@&$mandir&g
+ s&\\\${datarootdir}&$datarootdir&g' ;;
+esac
+_ACEOF
+
+# Neutralize VPATH when `$srcdir' = `.'.
+# Shell code in configure.ac might set extrasub.
+# FIXME: do we really want to maintain this feature?
+cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
+ac_sed_extra="$ac_vpsub
+$extrasub
+_ACEOF
+cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
+:t
+/@[a-zA-Z_][a-zA-Z_0-9]*@/!b
+s|@configure_input@|$ac_sed_conf_input|;t t
+s&@top_builddir@&$ac_top_builddir_sub&;t t
+s&@top_build_prefix@&$ac_top_build_prefix&;t t
+s&@srcdir@&$ac_srcdir&;t t
+s&@abs_srcdir@&$ac_abs_srcdir&;t t
+s&@top_srcdir@&$ac_top_srcdir&;t t
+s&@abs_top_srcdir@&$ac_abs_top_srcdir&;t t
+s&@builddir@&$ac_builddir&;t t
+s&@abs_builddir@&$ac_abs_builddir&;t t
+s&@abs_top_builddir@&$ac_abs_top_builddir&;t t
+$ac_datarootdir_hack
+"
+eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$ac_tmp/subs.awk" \
+ >$ac_tmp/out || as_fn_error $? "could not create $ac_file" "$LINENO" 5
+
+test -z "$ac_datarootdir_hack$ac_datarootdir_seen" &&
+ { ac_out=`sed -n '/\${datarootdir}/p' "$ac_tmp/out"`; test -n "$ac_out"; } &&
+ { ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' \
+ "$ac_tmp/out"`; test -z "$ac_out"; } &&
+ { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file contains a reference to the variable \`datarootdir'
+which seems to be undefined. Please make sure it is defined" >&5
+$as_echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir'
+which seems to be undefined. Please make sure it is defined" >&2;}
+
+ rm -f "$ac_tmp/stdin"
+ case $ac_file in
+ -) cat "$ac_tmp/out" && rm -f "$ac_tmp/out";;
+ *) rm -f "$ac_file" && mv "$ac_tmp/out" "$ac_file";;
+ esac \
+ || as_fn_error $? "could not create $ac_file" "$LINENO" 5
+ ;;
+
+
+
+ esac
+
+done # for ac_tag
+
+
+as_fn_exit 0
+_ACEOF
+ac_clean_files=$ac_clean_files_save
+
+test $ac_write_fail = 0 ||
+ as_fn_error $? "write failure creating $CONFIG_STATUS" "$LINENO" 5
+
+
+# configure is writing to config.log, and then calls config.status.
+# config.status does its own redirection, appending to config.log.
+# Unfortunately, on DOS this fails, as config.log is still kept open
+# by configure, so config.status won't be able to write to it; its
+# output is simply discarded. So we exec the FD to /dev/null,
+# effectively closing config.log, so it can be properly (re)opened and
+# appended to by config.status. When coming back to configure, we
+# need to make the FD available again.
+if test "$no_create" != yes; then
+ ac_cs_success=:
+ ac_config_status_args=
+ test "$silent" = yes &&
+ ac_config_status_args="$ac_config_status_args --quiet"
+ exec 5>/dev/null
+ $SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false
+ exec 5>>config.log
+ # Use ||, not &&, to avoid exiting from the if with $? = 1, which
+ # would make configure fail if this is the last instruction.
+ $ac_cs_success || as_fn_exit 1
+fi
+if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then
+ { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: unrecognized options: $ac_unrecognized_opts" >&5
+$as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;}
+fi
+
diff --git a/logo/configure.ac b/logo/configure.ac
new file mode 100644
index 0000000..ca58881
--- /dev/null
+++ b/logo/configure.ac
@@ -0,0 +1,30 @@
+dnl -*- Mode: Autoconf; tab-width: 4; indent-tabs-mode: nil; -*-
+dnl vi: set tabstop=4 shiftwidth=4 expandtab syntax=m4:
+dnl This Source Code Form is subject to the terms of the Mozilla Public
+dnl License, v. 2.0. If a copy of the MPL was not distributed with this
+dnl file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+AC_PREREQ(2.13)
+AC_INIT(MathML Logo, 1.0)
+AC_CONFIG_SRCDIR(mathml-logo.svg)
+
+AC_CHECK_PROGS(INKSCAPE, inkscape)
+AC_CHECK_PROGS(SCOUR, scour)
+AC_CHECK_PROGS(SFNT2WOFF, sfnt2woff)
+AC_CHECK_PROGS(UNZIP, unzip)
+AC_CHECK_PROGS(XSLTPROC, xsltproc)
+AC_CHECK_PROGS(WGET, wget)
+AC_CHECK_PROGS(ZIP, zip)
+
+if test -z "$INKSCAPE" ||
+ test -z "$SCOUR" ||
+ test -z "$SFNT2WOFF" ||
+ test -z "$UNZIP" ||
+ test -z "$XSLTPROC" ||
+ test -z "$WGET" ||
+ test -z "$ZIP"; then
+ AC_MSG_ERROR(Missing dependencies. Please read the README.md file.)
+fi
+
+AC_CONFIG_FILES(Makefile)
+AC_OUTPUT
diff --git a/logo/convert-to-inline-style.xsl b/logo/convert-to-inline-style.xsl
new file mode 100644
index 0000000..23cfc76
--- /dev/null
+++ b/logo/convert-to-inline-style.xsl
@@ -0,0 +1,41 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/logo/fonts.css b/logo/fonts.css
new file mode 100644
index 0000000..21e05fc
--- /dev/null
+++ b/logo/fonts.css
@@ -0,0 +1,30 @@
+/** fonts.css
+ ** Copyright 2015 Mondial Association for Tools Handling MathML, Ltd.
+ *
+ * This work may be distributed and/or modified under the
+ * conditions of the LaTeX Project Public License, either version 1.3c
+ * of this license or (at your option) any later version.
+ * The latest version of this license is in
+ * http://www.latex-project.org/lppl.txt
+ *
+ * This work has the LPPL maintenance status `maintained'.
+ *
+ * The Current Maintainer of this work is Frederic Wang.
+ *
+ * This work consists of all files listed in manifest.txt.
+ */
+
+@font-face {
+ font-family: LatinModernMathWOFF;
+ src: url('https://mathml.github.io/logo/webfonts/latinmodern-math.woff');
+}
+@font-face {
+ font-family: TeXGyreHerosWOFF;
+ src: url('https://mathml.github.io/logo/webfonts/texgyreheros-regular.woff');
+}
+.mathFont {
+ font-family: 'Latin Modern Math', LatinModernMathWOFF, serif;
+}
+.textFont {
+ font-family: 'TeX Gyre Heros', TeXGyreHerosWOFF, sans-serif;
+}
diff --git a/logo/index.md b/logo/index.md
new file mode 100644
index 0000000..5b1d0d9
--- /dev/null
+++ b/logo/index.md
@@ -0,0 +1,158 @@
+---
+layout: page
+title: MathML Association Logo
+---
+
+Introduction
+------------
+
+This page contains a list of logos for the MathML Association in
+different formats and sizes. You can also download the SVG, PNG, EPS and
+PDF logos in a single [ZIP archive](mathml-logos.zip).
+
+The files listed in [manifest.txt](./manifest.txt)
+constitute a "Work" that may be distributed and/or modified under
+[LaTeX Project Public License](http://latex-project.org/lppl/)
+either version 1.3c of this license or (at your option) any later version.
+Here are some suggestions to easily use the logos in compliance with the
+license:
+
+- Directly use the "Work" distributed by the MathML Association (clause 1 of
+ the license). For example, if you want to insert the image in your Web page,
+ you can just use the URLs of the website of the MathML Association.
+- Distribute an unmodified copy of the "Work" (clause 2 of the license).
+ For example, extract the whole ZIP archive on your Web server to use
+ the SVG or PNG logos in your Web pages.
+- Distribute a "Derived Work" consisting of one or more unmodified image files
+ together with a modified `manifest.txt` listing only the files kept from the
+ original "Work" (clause 5 of the license). Update `manifest.txt` to clearly
+ state that the "Derived Work" is only a subset of the original "Work"
+ (clause 6.a of the license) and to provide a link to the present web page
+ (clause 6.d.2 of the license). For example, if you only wish to insert the EPS
+ logos in your LaTeX documents, you could distribute them with the following
+ `manifest.txt` file:
+
+ %% manifest.txt
+ %% Copyright 2015 Mondial Association for Tools Handling MathML, Ltd.
+ %
+ % This work may be distributed and/or modified under the
+ % conditions of the LaTeX Project Public License, either version 1.3c
+ % of this license or (at your option) any later version.
+ % The latest version of this license is in
+ % http://www.latex-project.org/lppl.txt
+ %
+ % This work has the LPPL maintenance status `maintained`.
+ %
+ % The Current Maintainer of this work is [PUT YOUR NAME HERE].
+ %
+ % This work consists of all files listed in manifest.txt.
+ %
+ % This work consists of a subset of the "MathML Association logos".
+ % You can get a copy of the original work on the website of the
+ % MathML Association: http://mathml-association.org/logo/
+ %
+ % The manifest.txt file has been modified in order to enumerate only the subset
+ % of files distributed in this work.
+ %
+ % The text in the logo files are drawn using some glyphs from the Latin Modern
+ % Math and TeX Gyre Heros fonts and have been converted into equivalent vector
+ % and bitmap formats in order to integrate them into the logo files. The
+ % original and complete version of these fonts can be found on the GUST website:
+ % http://www.gust.org.pl/projects/e-foundry/lm-math
+ % http://www.gust.org.pl/projects/e-foundry/tex-gyre/heros
+ %
+ manifest.txt
+ mathml-logo.eps
+ mathml-square-logo.eps
+
+Rectangular Logo (Image + Trademark)
+------------------------------------
+
+
+This is a rectangular logo, divided into two parts. The left hand-side
+contains an image of the mathematical formula
+
+
+ w w w
+ \sqrt[w]{w^w}
+
+
+
+ 𝑤
+
+
+ 𝑤
+ 𝑤
+
+
+
+
+
+written in green on a black background that has the shape of a square with
+rounded corner. This image suggests mathematics and the World Wide Web.
+The right hand-side contains the left-aligned sans-serif text "MathML
+Association" with "MathML" written in black on the first line and
+"Association" written in green on the second line.
+
+
+- [SVG, text drawn with system fonts and WOFF fallback
+ (original source)](mathml-logo.svg)
+- SVG, text drawn with paths (no fonts required):
+
+ [](mathml-logo-text-as-path.svg)
+- PNG (640x200):
+
+ [](mathml-logo-640x200.png)
+- PNG (320x100):
+
+ [](mathml-logo-320x100.png)
+- PNG (240x75):
+
+ [](mathml-logo-240x75.png)
+- Other formats: [PDF](mathml-logo.pdf) and [EPS](mathml-logo.eps)
+
+Square Logo (Image only)
+------------------------
+
+
+This is an image of the mathematical formula
+
+
+ w w w
+ \sqrt[w]{w^w}
+
+
+
+ 𝑤
+
+
+ 𝑤
+ 𝑤
+
+
+
+
+
+in green on a black background that has the shape of a square with
+rounded corner. This image suggests mathematics and the World Wide Web.
+
+
+- [SVG, text drawn with system fonts and WOFF fallback
+ (original source)](mathml-square-logo.svg)
+- SVG, text drawn with paths (no fonts required):
+
+ [](mathml-square-logo-text-as-path.svg)
+- PNG (500x500):
+
+ [](mathml-square-logo-500.png)
+- PNG (256x256):
+
+ [](mathml-square-logo-256.png)
+- PNG (128x128):
+
+ [](mathml-square-logo-128.png)
+- PNG (64x64):
+
+ [](mathml-square-logo-64.png)
+- Other formats: [PDF](mathml-square-logo.pdf) and
+ [EPS](mathml-square-logo.eps)
diff --git a/logo/manifest.txt b/logo/manifest.txt
new file mode 100644
index 0000000..49a8160
--- /dev/null
+++ b/logo/manifest.txt
@@ -0,0 +1,38 @@
+%% manifest.txt
+%% Copyright 2015 Mondial Association for Tools Handling MathML, Ltd.
+%
+% This work may be distributed and/or modified under the
+% conditions of the LaTeX Project Public License, either version 1.3c
+% of this license or (at your option) any later version.
+% The latest version of this license is in
+% http://www.latex-project.org/lppl.txt
+%
+% This work has the LPPL maintenance status `maintained'.
+%
+% The Current Maintainer of this work is Frederic Wang.
+%
+% This work consists of all files listed in manifest.txt.
+%
+% The text in the logo files are drawn using some glyphs from the Latin Modern
+% Math and TeX Gyre Heros fonts and have been converted into equivalent vector
+% and bitmap formats in order to integrate them into the logo files. The
+% original and complete version of these fonts can be found on the GUST website:
+% http://www.gust.org.pl/projects/e-foundry/lm-math
+% http://www.gust.org.pl/projects/e-foundry/tex-gyre/heros
+
+manifest.txt
+mathml-logo-240x75.png
+mathml-logo-320x100.png
+mathml-logo-640x200.png
+mathml-logo-text-as-path.svg
+mathml-logo.eps
+mathml-logo.pdf
+mathml-logo.svg
+mathml-square-logo-128.png
+mathml-square-logo-256.png
+mathml-square-logo-500.png
+mathml-square-logo-64.png
+mathml-square-logo-text-as-path.svg
+mathml-square-logo.eps
+mathml-square-logo.pdf
+mathml-square-logo.svg
diff --git a/logo/mathml-logo.svg b/logo/mathml-logo.svg
new file mode 100644
index 0000000..4bb8a3a
--- /dev/null
+++ b/logo/mathml-logo.svg
@@ -0,0 +1,84 @@
+
+
+
+
+
+
+
+ image/svg+xml
+
+ MathML Association Logo
+
+
+
+
+ MathML Association Logo
+ This is a rectangular logo, divided into two parts.
+ The left hand-side contains an image of the mathematical formula
+ "the W-th root of open paren W raised to the power W close paren" written
+ in green on a black background that has the shape of a square with rounded
+ corner. This image suggests mathematics and the World Wide Web.
+ The right hand-side contains the left-aligned sans-serif text
+ "MathML Association" with "MathML" written in black on the first line and
+ "Association" written in green on the second line.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 𝑤
+ 𝑤
+ 𝑤
+
+
+
+
+
+
+
+ MathML
+ Association
+
+
+
diff --git a/logo/mathml-square-logo.svg b/logo/mathml-square-logo.svg
new file mode 100644
index 0000000..8b44ef8
--- /dev/null
+++ b/logo/mathml-square-logo.svg
@@ -0,0 +1,60 @@
+
+
+
+
+
+
+
+ image/svg+xml
+
+ MathML Association Logo
+
+
+
+
+ MathML Association Square Logo
+ This is an image of the mathematical formula
+ "the W-th root of open paren W raised to the power W close paren" written
+ in green on a black background that has the shape of a square with rounded
+ corner. This image suggests mathematics and the World Wide Web.
+
+
+
+
+
+
+
+
+
+
+ 𝑤
+ 𝑤
+ 𝑤
+
+
+
diff --git a/logo/remove-inline-style.xsl b/logo/remove-inline-style.xsl
new file mode 100644
index 0000000..877ae11
--- /dev/null
+++ b/logo/remove-inline-style.xsl
@@ -0,0 +1,20 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/logo/webfonts/manifest.txt b/logo/webfonts/manifest.txt
new file mode 100644
index 0000000..398c94a
--- /dev/null
+++ b/logo/webfonts/manifest.txt
@@ -0,0 +1,24 @@
+%% manifest.txt
+%% Copyright 2015 Mondial Association for Tools Handling MathML, Ltd.
+%
+% This work may be distributed and/or modified under the
+% conditions of the LaTeX Project Public License, either version 1.3c
+% of this license or (at your option) any later version.
+% The latest version of this license is in
+% http://www.latex-project.org/lppl.txt
+%
+% This work has the LPPL maintenance status `maintained`.
+%
+% The Current Maintainer of this work is Frédéric Wang
+%
+% This work consists of all files listed in manifest.txt.
+%
+% This work consists of files from the Latin Modern Math and TeX Gyre Heros
+% fonts bundled without any modification into WOFF files. You can get a copy of
+% the original work on the GUST website:
+% - http://www.gust.org.pl/projects/e-foundry/lm-math
+% - http://www.gust.org.pl/projects/e-foundry/tex-gyre/heros
+
+manifest.txt
+latinmodern-math.woff
+texgyreheros-regular.woff
diff --git a/meetings/board-2015-05-20.md b/meetings/board-2015-05-20.md
new file mode 100644
index 0000000..c5e5c72
--- /dev/null
+++ b/meetings/board-2015-05-20.md
@@ -0,0 +1,51 @@
+---
+layout: page
+title: Board Meeting 2015-20-05
+---
+
+Attendees:
+
+- Deyan Ginev,
+- Frédéric Wang,
+- Michael Kohlhase,
+- Moritz Schubotz.
+
+Session Chair: Frédéric Wang.
+
+Minutes Scribe: Deyan.
+
+## Minutes
+
+0. Only the founding directors are eligible to vote for this meeting: Deyan, Frédéric and Moritz
+1. Vote on approving the [By-laws policy](/legal-documents/non-profit-corporate-by-laws.html)
+ * Unanimously accepted (3 votes "yes", 0 votes "no")
+2. Vote on approving the [Conflicts of interest policy](/legal-documents/conflict-of-interest-policy.html)
+ * Unanimously accepted (3 votes "yes", 0 votes "no")
+ * **By-laws and CoI policies are now active**
+3. Proceding to elect initial directors and settle terms of office.
+ **Moritz loses connection to the call**
+4. Vote on initial directors (Deyan, Frédéric and Moritz) to have their term end on 12.31.2015
+ * Unanimously accepted (2 votes "yes", 0 votes "no")
+ * **Moritz returns to the call**
+5. Vote on electing Michael and Raniere as directors for a 2 year term, ending on 12.31.2016:
+ * Unanimously accepted (3 votes "yes", 0 votes "no")
+ * **the first 5 MathML directors have been elected: Deyan, Frédéric, Michael, Moritz, Raniere**
+ * We need to decide on a proper election cycle, to avoid any gaps in the board.
+6. Next meeting will be no later than 3 months from today: August 20, 2015. Date to be decided separately. Also, we should use a different application so that we have proper sound.
+7. Agenda suggestions for next meeting:
+ * Appointment of the initial Board Officers: Secretary, President, Vice-president, Treasurer
+ * Start dicussing bank account, paypal etc to receive donations
+ * tax exempt status
+ * agenda should be open until meeting is announced, will work on details in the coming months
+ * proposals welcome
+
+8. Discussion on execution plans:
+ * prioritize:
+ - prepare and publish association website
+ - tax exemption filing. Deyan will investigate.
+ - recruiting MathML affiliates in the organization (Frédéric: maybe Igalia)
+ * brainstorm on strategy for making the associations impressive and impactful
+ * also brainstorm on collecting funding for association-promoted activities. Michael: list of tasks that can be sponsored? Frédéric could organize.
+ * we may need a private repository and mailing list for efficient communication
+
+9. Round of congratulations on starting the association and moving forward. Congrats!
diff --git a/meetings/board-2015-08-05.md b/meetings/board-2015-08-05.md
new file mode 100644
index 0000000..b56f189
--- /dev/null
+++ b/meetings/board-2015-08-05.md
@@ -0,0 +1,778 @@
+---
+layout: page
+title: Board Meeting 2015-05-08
+---
+
+Attendees:
+
+- Deyan Ginev,
+- Frédéric Wang,
+- Michael Kohlhase,
+- Moritz Schubotz,
+- Raniere Silva.
+
+Session Chair: Frédéric Wang.
+
+Minutes Scribe: Deyan.
+
+## Minutes
+* Agenda: [https://github.com/MathML/website/wiki/Board-Meeting-August-2015---Announcement](https://github.com/MathML/website/wiki/Board-Meeting-August-2015---Announcement)
+
+### Recap
+
+1. Michael, Moritz and Deyan met at CICM 15.
+2. There is broad board consensus on the MathML association's purpose in 2 directions:
+ * Promoting MathML
+ * Funding MathML projects
+
+3. There is still a lot of administrative work that needs to be done before we move forward.
+
+### Voting
+
+1. Vote on accepting the [MathML Manifesto](/legal-documents/manifesto.html)
+ * Unanimously accepted (5 yes, 0 no, 0 abstained)
+2. Vote on selecting a MathML Association logo
+ * After a discussion of [alternatives](https://github.com/MathML/website/wiki/Board-Meeting-August-2015---Announcement#logo-proposals), suggestion 5.g) had broadest appeal
+ * Multiple-choice vote on alternatives had unanimous support for suggestion 5.g) (5 yes, 0 no, 0 abstained)
+ * Congratulations on the new [official MathML Association logo](/logo/mathml-logo.svg) and thanks to all parties which contributed suggestions!
+3. Amendment of MathML Association bylaws
+ * Affiliate status should **not** be required for director election - unanimous approval (5 yes, 0 no, 0 abstained)
+ * Board meeting minutes automatically become public 1 week after the meeting - accepted with simple majority (3 yes, 0 no, 2 abstained)
+4. Vote on [Affiliates](/legal-documents/affiliates.html) structure and guidelines - unanimously accepted (5 yes, 0 no, 0 abstained)
+
+### Deferred Items and Next Steps
+1. Selection of a MathML Association "slogan"
+2. Directors interested in "communication" will work on making the website public, Raniere leads the effort
+3. Directors interested in "funding" will work on a tax-exemption application to the IRS
+4. Election of Board Officers in the next meeting
+5. Revisit Affiliates document to clarify tax-exemption language
+6. Start contacting potential affiliates
+7. Moritz will organize a Doodle for the next meeting, for the second half of September
+
+## Full meeting log
+
+>[23:01] <fredw> deyan: physikerwelt____ raniere kohlhase: Welcome to our second MathML board meeting!
+>
+>[23:01] <fredw> The agenda for this meeting is available on the MathML Wiki:
+>
+>[23:01] <fredw> https://github.com/MathML/website/wiki/Board-Meeting-August-2015---Announcement
+>
+>[23:01] <fredw> So basically after the CICM meeting, I think everybody now agree with the two goals: 1) promoting MathML and 2) funding MathML projects. For both of them we still need to make progress on our public image & on the paperwork...
+>
+>[23:01] <fredw> So today we will first start with the pending votes and then discuss the next steps...
+>
+>[23:01] <fredw> Does that sound good?
+>
+>[23:02] <raniere> yes
+>
+>[23:02] <physikerwelt____> +1
+>
+>[23:02] <deyan> I second that
+>
+>[23:02] <kohlhase> +1
+>
+>[23:03] <fredw> OK, so the first item is "Vote for the MathML Manifesto"
+>
+>[23:03] <fredw> The latest version published on the Website is Michael's one: http://dev.mathml-association.org/manifesto.html
+>
+>[23:03] <fredw> I've done minor corrections some days ago: https://github.com/MathML/website/commit/e45845ff956b476292b4e08ecf09b21f3960cecd
+>
+>[23:04] <kohlhase> I propose we accept the manifesto in the corrected form.
+>
+>[23:04] <deyan> minor note: formulas and formulae are both valid spellings, as long as they are used consistently
+>
+>[23:04] <fredw> deyan: yes, the "correction" was to make things consistent
+>
+>[23:05] <raniere> second the merge of corrections
+>
+>[23:05] <physikerwelt____> I vote yes for revision https://github.com/MathML/website/commit/e45845ff956b476292b4e08ecf09b21f3960cecd
+>
+>[23:05] <fredw> OK so let's start with the vote.
+>
+>[23:05] <raniere> +1
+>
+>[23:05] <deyan> +1 in favour
+>
+>[23:05] <kohlhase> +1
+>
+>[23:05] <physikerwelt____> *1
+>
+>[23:05] <physikerwelt____> *1
+>
+>[23:05] <fredw> +1 in favor
+>
+>[23:05] <physikerwelt____> +1
+>
+>[23:06] <fredw> OK, so the manifesto is approved. (Raniere will need to update the Website)
+>
+>[23:06] <kohlhase> great!
+>
+>[23:06] <deyan> second minor point: do we have a minute taker for this week, or are the IRC logs the official minutes?
+>
+>[23:07] <fredw> deyan: good question. I think someone should take the minute.
+>
+>[23:07] <physikerwelt____> I learned that there are no irc logs
+>
+>[23:07] <fredw> But we didn't decide about the Secretary yet
+>
+>[23:07] <raniere> fredw: I will do it after the meeting.
+>
+>[23:07] <kohlhase> I think the IRC logs are good as minutes. We should have a results summary though.
+>
+>[23:07] <physikerwelt____> at least no central
+>
+>[23:08] <kohlhase> the results summary should mainly cover the votes passed with the numbers.
+>
+>[23:08] <fredw> I think Deyan's summary was easier to read
+>
+>[23:08] <deyan> I volunteer to write the summary and attach the IRC log as an appendix to it.
+>
+>[23:08] <physikerwelt____> wikimedia operations use a logbot that logs only messages prefixed with log: I think that would be ideal
+>
+>[23:08] <raniere> I'm logging the meeting on my machine and can archive it somewhere if needed
+>
+>[23:08] <kohlhase> very good.
+>
+>[23:08] <deyan> I will upload it within 24 hours of finishing the meeting
+>
+>[23:08] <physikerwelt____> thanks deyan
+>
+>[23:08] <kohlhase> yes, thanks.
+>
+>[23:08] <fredw> thanks. So deyan and/or raniere you'll take care of that
+>
+>[23:09] <fredw> So the second item was the "MathML logo", for which we have had a very long discussion :-)
+>
+>[23:09] <kohlhase> I propose that we accept 5e as the logo
+>
+>[23:10] <fredw> So 5e) https://cloud.githubusercontent.com/assets/567455/8019144/60c74542-0c3f-11e5-9ce4-997914d7fea6.png is the one we currently use
+>
+>[23:10] <physikerwelt____> fredw: the background is transparent?
+>
+>[23:10] <fredw> Personally, I'd pref 5f) or 5g) with the "math italic" as suggested by Michael, but I'm fine with 5e)
+>
+>[23:11] <fredw> physikerwelt____: yes, it is in the SVG
+>
+>[23:11] <raniere> I prefer 5f or 5g
+>
+>[23:11] <fredw> I think this one is just a screenshot with the Gnome image previewer
+>
+>[23:11] <kohlhase> I am also fine with 5g
+>
+>[23:11] <deyan> Would the board members be open to considering different formats of the same logo as "official alternatives"? I.e. SVG, PNG, PDF, EPS versions of the same image would all be considered official logos.
+>
+>[23:12] <raniere> 5g > 5e > 5f
+>
+>[23:12] <kohlhase> deyan?
+>
+>[23:12] <kohlhase> Moritz?
+>
+>[23:13] <kohlhase> I think we should only agree on the "shape" of the logo, not the format.
+>
+>[23:13] <physikerwelt____> I like 5e best but 5?x is fine with me
+>
+>[23:13] <deyan> I would vote for 5g) , together with my remark on format alternatives all being official (if we need them)
+>
+>[23:13] <fredw> deyan: why do we need PDF / EPS?
+>
+>[23:14] <kohlhase> hmmm, seems a slight majority for 5g
+>
+>[23:14] <fredw> I think the official is SVG since it is the source (although the exact font-family should be given)
+>
+>[23:14] <physikerwelt____> I'm perfectly fine with 5g
+>
+>[23:14] <raniere> I have no problem with provide SVG, PNG, PDF and EPS version since sometimes people will need it
+>
+>[23:15] <deyan> fredw: pockets of publishing would require an EPS file instead of an SVG file. Hopefully we never need to think about this, I just wanted to clarify it in theory.
+>
+>[23:15] <physikerwelt____> who is not for 5g?
+>
+>[23:15] <fredw> deyan: OK. I think Michael's remark is correct (that we agree on the shape) and we can convert it in any format
+>
+>[23:16] <fredw> So let's summarize the vote again:
+>
+>[23:16] <kohlhase> I do not think we have a vote yet.
+>
+>[23:16] <fredw> me: 5g)
+>
+>[23:16] <kohlhase> this was open discussion.
+>
+>[23:17] <raniere> second 5g for the logo. Can we vote?
+>
+>[23:17] <kohlhase> yes.
+>
+>[23:17] <physikerwelt____> before we vote we should list the voting options
+>
+>[23:17] <physikerwelt____> I would propose a single vote on 5g with only yes or no
+>
+>[23:17] <kohlhase> yes.
+>
+>[23:17] <kohlhase> seconded
+>
+>[23:18] <fredw> So to summarize: we vote for the shape of the logo (based on the SVG source) but other formats that can be converted from the source and preserve the shape are valid.
+>
+>[23:18] <raniere> +1
+>
+>[23:18] <deyan> I also second this phrasing of the vote
+>
+>[23:18] <physikerwelt____> +1
+>
+>[23:18] <kohlhase> +1
+>
+>[23:18] <deyan> +1 (vote in favour)
+>
+>[23:19] <physikerwelt____> +1 (vote in favour)
+>
+>[23:19] <kohlhase> OK, I guess then we can vote for the actual logo.
+>
+>[23:19] <kohlhase> I propose to accept 5g as the logo
+>
+>[23:19] <physikerwelt____> yes for 5g
+>
+>[23:19] <fredw> So let's start the vote. Please choose one among https://github.com/MathML/website/wiki/Board-Meeting-August-2015---Announcement
+>
+>[23:19] <fredw> me: 5g)
+>
+>[23:19] <raniere> 5g
+>
+>[23:20] <kohlhase> 5g
+>
+>[23:20] <deyan> 5g) as well (a little chaotic, but it seems we are unanimous )
+>
+>[23:20] <kohlhase> excellent
+>
+>[23:20] <fredw> physikerwelt____: ?
+>
+>[23:21] <physikerwelt____> yes for 5g
+>
+>[23:21] <fredw> OK, so 5g) is accepted
+>
+>[23:21] <deyan> congratulations on our official logo !
+>
+>[23:21] <deyan> we have a face :)
+>
+>[23:22] <fredw> Just to clarify what I used in the SVG source => font-family: sans for the MathML Association text and font-family: Latin Modern Math for the W's
+>
+>[23:22] <physikerwelt____> great thanks to all of your for the contious effort to create a nice logo
+>
+>[23:22] <deyan> and I want to take this opportunity to thank everyone, including non-board affiliates such as Andrea and Bruce, for their discussions and mockup contributions to the logo brainstorming!
+>
+>[23:23] <fredw> So actually in the same item, there was the creation of a slogan. But I think I was the only one who proposed one.
+>
+>[23:23] <fredw> "The MathML Association, a math group acting on the Web"
+>
+>[23:23] <kohlhase> I will pass the thanks on to Andrea
+>
+>[23:23] <raniere> I'm OK with that slogan
+>
+>[23:23] <fredw> If you prefer we can postpone the vote for later, as this has not really been discussed before
+>
+>[23:23] <kohlhase> I do not really like the slogan.
+>
+>[23:24] <kohlhase> we should think more about this.
+>
+>[23:24] <fredw> kohlhase: OK, that's fine.
+>
+>[23:24] <deyan> I suggest postponing the vote and having an additional round of github discussion.
+>
+>[23:24] <physikerwelt____> ok letst postpone the slogan decision
+>
+>[23:24] <deyan> i.e. second kohlhase
+>
+>[23:24] <kohlhase> It is not very memorable.
+>
+>[23:24] <physikerwelt____> ^^
+>
+>[23:24] <deyan> fredw: still puntastic though ;)
+>
+>[23:25] <physikerwelt____> Do we have a bug for the slogan?
+>
+>[23:25] <fredw> So let's move to the next item
+>
+>[23:25] <kohlhase> How about something simple like "MathML advocacy and development"
+>
+>[23:25] <kohlhase> just for the record
+>
+>[23:26] <deyan> second fredw to move to the next vote item. Let's tackle the slogan on GitHub
+>
+>[23:26] <kohlhase> +1
+>
+>[23:26] <fredw> So the second items were the votes for amendment of the bylaws
+>
+>[23:26] <fredw> *next item*
+>
+>[23:27] <fredw> but I reverted the commits
+>
+>[23:27] <fredw> So for the first one: https://github.com/MathML/website/pull/2#issuecomment-124489652
+>
+>[23:27] <fredw> I'm not sure I understand "In order to be eligible to serve as a director on the board of directors, the individual must be 18 years of age and an affiliate within affiliate classifications created by the board of directors."
+>
+>[23:27] <fredw> this was in the original model of bylaws
+>
+>[23:28] <fredw> I believe directors don't need to be "affiliates"
+>
+>[23:28] <physikerwelt____> so we vote on https://github.com/MathML/website/commit/820e34a0fe87ddc042d30f10b2212745721e8097?
+>
+>[23:28] <physikerwelt____> so we vote on https://github.com/MathML/website/commit/820e34a0fe87ddc042d30f10b2212745721e8097 ?
+>
+>[23:28] <fredw> physikerwelt____: yes
+>
+>[23:28] <physikerwelt____> is there a need for discussion?
+>
+>[23:28] <kohlhase> no
+>
+>[23:28] <fredw> deyan: raniere ?
+>
+>[23:29] <deyan> I am ready to vote
+>
+>[23:29] <deyan> ... and raniere already merged them :)
+>
+>[23:29] <raniere> yes
+>
+>[23:29] <raniere> we can vote!
+>
+>[23:29] <physikerwelt____> ok so let's start the vote
+>
+>[23:29] <fredw> So let's vote
+>
+>[23:29] <kohlhase> I propose to accept the change
+>
+>[23:29] <physikerwelt____> +1
+>
+>[23:29] <kohlhase> +1
+>
+>[23:29] <deyan> +1
+>
+>[23:29] <fredw> me: I accept the change
+>
+>[23:29] <raniere> +1
+>
+>[23:30] <fredw> So the vote is accepted.
+>
+>[23:30] <kohlhase> unanimously
+>
+>[23:30] <fredw> raniere: you will be able to merge that one :-)
+>
+>[23:30] <fredw> The second was more controversial
+>
+>[23:30] <raniere> LOL
+>
+>[23:30] <physikerwelt____> should we agree on a voting sing?
+>
+>[23:30] <fredw> I don't remember where was the discussion
+>
+>[23:31] <fredw> but basically Moritz had concerned about making the minutes public immediately
+>
+>[23:31] <fredw> and Deyan noticed that anyway we want the board meeting to be public (and I agree with that)
+>
+>[23:31] <kohlhase> I like to have an upper limit for publishing the mintues.
+>
+>[23:31] <physikerwelt____> I just wanted to have clear rules
+>
+>[23:32] <physikerwelt____> I'm for https://github.com/MathML/website/commit/ed657615295095ac6536a2dc3a3ae920eaaac1b9
+>
+>[23:32] <kohlhase> do we need discussion?
+>
+>[23:32] <physikerwelt____> no that was the wrong commit
+>
+>[23:32] <physikerwelt____> I mean the opposite
+>
+>[23:32] <kohlhase> https://github.com/MathML/website/commit/73333e999bcaeae8f65c27269907d40e6b41b771
+>
+>[23:33] <physikerwelt____> thanks
+>
+>[23:33] <physikerwelt____> I have no need for discussion
+>
+>[23:33] <kohlhase> do we need discussion?
+>
+>[23:33] <deyan> it's a bit imprecise, but I think the common sense workflow will "just work". I can vote for that commit
+>
+>[23:33] <fredw> So to be clear we change the wording "once accepted by the board" to "one week after the meeting"
+>
+>[23:34] <kohlhase> yes.
+>
+>[23:34] <physikerwelt____> yes
+>
+>[23:34] <physikerwelt____> technically I like the logbot approach used by wikimedia but that's offtopic here
+>
+>[23:34] <deyan> I motion to start a vote
+>
+>[23:35] <physikerwelt____> for example " !log deployed parsoid version d5a5722c Logged the message at https://wikitech.wikimedia.org/wiki/Server_Admin_Log, Master"
+>
+>[23:35] <kohlhase> seconded
+>
+>[23:35] <physikerwelt____> +1
+>
+>[23:35] <raniere> +1
+>
+>[23:35] <kohlhase> +1 for accepting the change
+>
+>[23:35] <physikerwelt____> +1 for accepting the change
+>
+>[23:35] <deyan> +1 for accepting the change
+>
+>[23:36] <kohlhase> fred?
+>
+>[23:36] <fredw> +0 (I do not pronounce on this)
+>
+>[23:36] <deyan> raniere: ?
+>
+>[23:36] <raniere> +0
+>
+>[23:36] <kohlhase> OK, then the motion is carried
+>
+>[23:36] <fredw> So the commit is accepted
+>
+>[23:36] <deyan> 3 in favor, 2 abstained, the motion passes
+>
+>[23:37] <kohlhase> BTW, the logbot approach is a valid implementation.
+>
+>[23:37] <kohlhase> but summary + log is as well.
+>
+>[23:37] <deyan> the IRS will be happier to see executive summaries, than IRC logs
+>
+>[23:38] <physikerwelt____> just to familarize ourselfs with the bylaws would a 2 in favor vote still be accepted
+>
+>[23:38] <fredw> So finally: "Decide the next steps"
+>
+>[23:38] <physikerwelt____> or do we need to have 50% at least
+>
+>[23:38] <deyan> 2 in favour, 3 abstained is a successful vote I believe
+>
+>[23:39] <fredw> I think so
+>
+>[23:39] * raniere agrees with "2 in favour, 3 abstained is a successful vote I believe"
+>
+>[23:39] <deyan> you need majority favour in all cast ballots, and you need quorum when the vote starts
+>
+>[23:39] <kohlhase> we have both.
+>
+>[23:39] <deyan> yes, just clarifying
+>
+>[23:39] <fredw> (For 5 abstained, I'm not sure what happens...)
+>
+>[23:40] <deyan> 5 abstained should postpone the vote to the next meeting ^^
+>
+>[23:40] <kohlhase> not the majority, but a tie.
+>
+>[23:40] <fredw> OK, so can we move to the next item
+>
+>[23:40] <fredw> "Decide the next steps"
+>
+>[23:41] <physikerwelt____> yes... however I think this should be a discussion
+>
+>[23:41] <deyan> have we concluded all immediate voting items?
+>
+>[23:41] <raniere> fredw: the Web site need changes?
+>
+>[23:41] <fredw> yes, all the scheduled votes are done
+>
+>[23:41] <fredw> so the last item (from the wiki) is just a discussion
+>
+>[23:41] <deyan> good job to finishing all of that in 40 mins
+>
+>[23:42] <fredw> (good that we skip the slogan discussion :-))
+>
+>[23:42] <deyan> so, I think Michael had a great timeframe proposed
+>
+>[23:42] <deyan> we start with making the website public
+>
+>[23:42] <kohlhase> Don't we need to vote on these three being the next steps to work on?
+>
+>[23:43] <deyan> than whoever wants to do social media campaigning should track our Twitter account and tweet out reasonably
+>
+>[23:43] <fredw> Basically I think people have more or less expressed their personal priorities.
+>
+>[23:43] <kohlhase> I think we need to at least decide to move the website from dev to main.
+>
+>[23:43] <kohlhase> And do that.
+>
+>[23:43] <deyan> +1 on voting, +1 agreeing we should
+>
+>[23:44] <kohlhase> I also think that we are ready to adopt the affiliates document.
+>
+>[23:44] <kohlhase> that needs to go onto the web site.
+>
+>[23:44] <fredw> deyan: I think you had concerns about having a "beautiful" website
+>
+>[23:44] <physikerwelt____> +0 on voting, +1 on publishing the website
+>
+>[23:44] <raniere> I will take some time on the weekend to check the website
+>
+>[23:45] <raniere> And I can publish it on Monday morning
+>
+>[23:45] <kohlhase> very good.
+>
+>[23:45] <fredw> Should we postpone the affiliates to the next meeting (as this was not announced on the agenda)
+>
+>[23:45] <deyan> fredw: yes, I but I am also pragmatic. And I have personally failed to improve the site in the allotted time, so I'd rather have a great site rather than the Perfect site
+>
+>[23:45] <physikerwelt____> raniere: that would be awesome
+>
+>[23:45] <fredw> deyan: ok
+>
+>[23:45] <fredw> I think the main problems for the website were: 1) automatically generate from the source 2) make it work on mobile
+>
+>[23:45] <fredw> raniere: can you say something about the status?
+>
+>[23:46] <fredw> oh, and also kohlhase mentioned changing the colors to match the logo
+>
+>[23:46] <kohlhase> good idea :-).
+>
+>[23:46] <raniere> fredw: I have to setup a script to automatically generate from the source after each commit/merge
+>
+>[23:47] <raniere> but I can keep doing it manually for the next few months
+>
+>[23:47] <raniere> I don't remember the problem on mobile
+>
+>[23:47] <fredw> raniere: is there a technical issue? Or just that you haven't had time so far
+>
+>[23:47] <fredw> raniere: I think you mentioned something about the rendering not being good on mobile
+>
+>[23:48] <raniere> fredw: I didn't have time to play with web hooks and GGI
+>
+>[23:48] <raniere> s/GGI/CGI
+>
+>[23:48] <fredw> OK
+>
+>[23:48] <fredw> So basically, I let people interested in "communication" manage the website and so on.
+>
+>[23:48] <kohlhase> Can we reach a decision about the affiliates?
+>
+>[23:48] <fredw> Personally, I'd like to help with the paperwork & affiliates
+>
+>[23:49] <kohlhase> It is mentioned under "next steps".
+>
+>[23:49] <deyan> fredw: good plan. I would like to help with communication and NYC-local work (IRS ...)
+>
+>[23:49] <fredw> So the affiliates:
+>
+>[23:49] <fredw> I think everybody should re-read this
+>
+>[23:50] <fredw> and we can vote for it in the next meeting.
+>
+>[23:50] <fredw> At least that's what I propose
+>
+>[23:50] <kohlhase> OK
+>
+>[23:50] <physikerwelt____> I'm happy with the newly introduced categories for the sponsors
+>
+>[23:50] <kohlhase> this means that we cannot start getting them.
+>
+>[23:50] <kohlhase> s/getting/recruiting/
+>
+>[23:50] <fredw> kohlhase: Also, there is a question about whether we want to keep a separate document (like the conflict of interest policy) or integrate it into our bylaws
+>
+>[23:51] <kohlhase> I would not make it part of the bylaws.
+>
+>[23:51] <fredw> kohlhase: we can also do a board meeting in september
+>
+>[23:51] <kohlhase> maybe the categories alone have to become part of the bylaws.
+>
+>[23:51] <physikerwelt____> I think the sponsoring issue also depends on the IRS issue?
+>
+>[23:52] <deyan> I would suggest the next board meeting is *no sooner* than 6 weeks from today
+>
+>[23:52] <fredw> physikerwelt____: not necessarily, that would help for companies to have the IRS
+>
+>[23:52] <fredw> and for american citizens too
+>
+>[23:52] <fredw> but people can donate as long as we have a bank / paypal account
+>
+>[23:52] <deyan> btw, ideally we have all our internal documents finalized *before* we file to the IRS. We need to print+attach all of them for the tax-exemption application
+>
+>[23:53] <fredw> deyan: ok, so the affiliates doc should be done before
+>
+>[23:53] <deyan> I will consult with PlanetMath about these details again, hopefully Aaron can give me a couple of free lawyer hours
+>
+>[23:53] <fredw> deyan: I was suggesting doing a short meeting in september, just to vote for the affiliates doc
+>
+>[23:53] <physikerwelt____> deyan if that's the case I'd propose to accept the affilates.md as it is
+>
+>[23:54] <kohlhase> I second that .
+>
+>[23:54] <kohlhase> and then we can still amend it in September.
+>
+>[23:54] <fredw> ok, that sounds good
+>
+>[23:54] <fredw> so at least we can publish the doc on the website
+>
+>[23:54] <deyan> I'm a bit worried whether one part violates tax-exemption
+>
+>[23:54] <physikerwelt____> do we need to vote on that
+>
+>[23:55] <deyan> " Affiliates may benefit from transaction or arrangement with the MathML Association. "
+>
+>[23:55] <kohlhase> yes we should
+>
+>[23:55] <fredw> deyan: can you elaborate on that?
+>
+>[23:55] <deyan> this needs be constrained within the ideal mission of the NGO
+>
+>[23:55] <deyan> we should never exclusively serve private interest, that violates our tax-exempt status
+>
+>[23:55] <fredw> deyan: I think there is one part that mentions that
+>
+>[23:56] <deyan> there is a mention of conflicts of interest, but that is different
+>
+>[23:56] <fredw> ok
+>
+>[23:56] <fredw> so maybe this should be clarified
+>
+>[23:56] <deyan> however, I agree we should start recruiting affiliates asap
+>
+>[23:56] <physikerwelt____> if we need to amand the document we can do that in a circular resolution
+>
+>[23:56] <kohlhase> we can accept the affiliates document today --> recruiting
+>
+>[23:57] <kohlhase> and then amend it as necessary to clarify conflicts and tax.
+>
+>[23:57] <deyan> so maybe we can start tentative recruiting (warm-up calls) and we vote in 6 weeks on amending the document AND adding new affiliates
+>
+>[23:57] <deyan> I believe we need to vote new affiliates in, correct?
+>
+>[23:57] <kohlhase> correct
+>
+>[23:57] <fredw> yes
+>
+>[23:57] <kohlhase> (if we accept the doc)
+>
+>[23:58] <deyan> I am happy with the current document, modulo amendments that protect tax-exemption
+>
+>[23:58] <physikerwelt____> I would like to vote on the doc
+>
+>[23:58] <fredw> raniere: ?
+>
+>[23:58] <raniere> I'm OK
+>
+>[23:58] <kohlhase> OK as well
+>
+>[23:58] <raniere> we can vote on the doc
+>
+>[23:59] <fredw> OK so let's start the vote
+>
+>[23:59] <fredw> me: +1
+>
+>[23:59] <physikerwelt____> We vote on small fixes to affilliates text.
+>
+>[23:59] <physikerwelt____> +1
+>
+>[00:00] <raniere> +1
+>
+>[00:00] <kohlhase> +1
+>
+>[00:00] <deyan> +1
+>
+>[00:01] <fredw> OK so the doc is approved
+>
+>[00:01] <physikerwelt____> are there further things we need to vote on?
+>
+>[00:01] <fredw> I'd just like to come back to the manifesto one second. The mention "Warning: this is a draft." should be removed.
+>
+>[00:01] <raniere> +1
+>
+>[00:01] <kohlhase> obviously
+>
+>[00:01] <deyan> fredw: this is probably too obvious for a vote :) +1
+>
+>[00:01] <physikerwelt____> +1
+>
+>[00:02] <fredw> yes, but just wanted to be clarify
+>
+>[00:02] <fredw> as we didn't mention that during the vote
+>
+>[00:02] <fredw> +1
+>
+>[00:02] <deyan> ok, I think we are ready to wrap up for today
+>
+>[00:02] <kohlhase> Seems like we have covered all the agenda.
+>
+>[00:02] <physikerwelt____> in the german law this is called " Berichtigung einer offensichtlichen Unrichtigkeit "
+>
+>[00:02] <deyan> I would suggest we elect the official positions for our next meeting, we also need those set before we file the IRS forms
+>
+>[00:03] <kohlhase> which are they?
+>
+>[00:03] <fredw> deyan: ok that sounds good
+>
+>[00:03] <fredw> I think we didn't really discuss that
+>
+>[00:03] <deyan> President, Vice-president, Secretary, Treasurer
+>
+>[00:03] <kohlhase> that leaves one member-at-large.
+>
+>[00:04] <kohlhase> this is a good idea.
+>
+>[00:04] <kohlhase> nominations?
+>
+>[00:04] <deyan> yes, they are separate from the Board Directors. I am hoping the director without a position will be doing most of the actual work ;)
+>
+>[00:05] <kohlhase> Let's initially elect them from the board.
+>
+>[00:06] <physikerwelt____> kohlhase: today?
+>
+>[00:07] <kohlhase> that is what I understand deyan proposed.
+>
+>[00:08] <deyan> oh, my suggestion was for the next meeting
+>
+>[00:08] <deyan> we ran over 1 hour today, so I am personally ready to wrap up
+>
+>[00:08] <deyan> but if there is overwhelming desire to keep going, I'll manage
+>
+>[00:08] <kohlhase> OK, then I misunderstood "for the next meeting" as "so we have them in the next meeting"
+>
+>[00:08] <fredw> I think that's fine to discuss that on github and move this item to the next meeting
+>
+>[00:09] <kohlhase> seconded
+>
+>[00:09] <fredw> (so again I'm proposing doing the next meeting in september)
+>
+>[00:09] <physikerwelt____> +2 for the next meeting
+>
+>[00:09] <kohlhase> I would propose after september 15.
+>
+>[00:09] <physikerwelt____> let's limit the next meeting time to 60 min
+>
+>[00:09] <deyan> I would suggest September 18 or later
+>
+>[00:09] <physikerwelt____> for me everything after sep 13 is fine
+>
+>[00:10] <fredw> I'm fine with any date in september
+>
+>[00:10] <fredw> Summary:
+>
+>[00:10] <fredw> - Raniere will take care of publishing documents & updating the website
+>
+>[00:10] <fredw> - discussion about the slogan
+>
+>[00:10] <fredw> - check again about the affiliates doc (with respect to tax-exemptions form)
+>
+>[00:10] <fredw> - start contacting affiliates
+>
+>[00:10] <fredw> - Deyan & Fred will check the tax-exemptions form
+>
+>[00:10] <fredw> - Talk about officer and elect them in the next meeting
+>
+>[00:10] <raniere> I'm fine with any date in september
+>
+>[00:10] <physikerwelt____> Let's do a doodle for sept 15+
+>
+>[00:10] <fredw> anything else?
+>
+>[00:10] <deyan> physikerwelt____: are you volunteering to make the doodle? :)
+>
+>[00:10] <kohlhase> nothing else
+>
+>[00:11] <deyan> I think we can close a very productive meeting!
+>
+>[00:11] <physikerwelt____> deyan: I already started
+>
+>[00:11] <fredw> yes, thank you everybody
+>
+>[00:11] <deyan> physikerwelt____: wonderful
+>
+>[00:11] <raniere> this was a good meeting
+>
+>[00:11] <kohlhase> bye bye, good meeting.
+>
+>[00:11] <raniere> fredw: thanks very much for leading this
diff --git a/meetings/board-2015-09-18.md b/meetings/board-2015-09-18.md
new file mode 100644
index 0000000..15a74f6
--- /dev/null
+++ b/meetings/board-2015-09-18.md
@@ -0,0 +1,74 @@
+---
+layout: page
+title: Board Meeting 2015-09-18
+---
+
+Attendees:
+
+- Bruce R. Miller,
+- Deyan Ginev,
+- Frédéric Wang,
+- Michael Kohlhase,
+- Moritz Schubotz,
+- Raniere Silva,
+
+Session Chair: Frédéric.
+
+Minutes Scribe: Deyan.
+
+Venue: Mumble
+
+## Minutes
+
+0. We welcome Bruce as an observer to our meeting.
+
+1. First official communications between the Association and the Math WG were a little rocky, but we are now on the same page.
+
+ - The name of Frédéric's implementation document could be amended to be less controversial with the WG. The document aims to clarify common implementation uncertainties, and provide best practices.
+
+ - More importantly, we'll try to coordinate Frédéric's "MathML-in-HTML5 implementation" spec with the Math WG for ensuring higher quality and set a precedent for a good working relationship between both organizations.
+
+ - Michael will be our official Math WG ambassador
+
+2. "Logo follow-up items" - vote on approving the [logo alternatives](https://github.com/MathML/website/wiki/Board-Meeting-September-2015---Announcement).
+ - 5 in favour, 0 against, unanimously approved all 3 points.
+
+3. Vote for the License of Website content: Raniere proposes to release all the content under "Creative Commons Attribution 4.0 International License".
+ - 5 in favour, 0 against, unanimously approved
+
+4. Association Slogan. Suggestion to postpone vote and discuss further on GitHub.
+ - 5 in favour, 0 against, unanimously approved to postpone to next meeting.
+
+5. Appointing the initial Board Officers.
+
+ - Questions about the concrete voting procedure were raised, as to avoid bias when electing members.
+ - Agreed to proceed to a yes/no vote in public - as a practical exception
+ - We will investigate alternatives for future votes
+
+ - Official position suggestion for year 2015:
+ * **President**: Michael Kohlhase
+ * **Vice-president**: Frédéric Wang
+ * **Secretary**: Deyan Ginev
+ * **Treasurer**: Raniere Silva
+
+ - Yes/no vote for the suggestion
+ * 5 in favour, 0 against, unanimously approved.
+
+6. Tax-exempt status progress
+ * we have an EIN employer number in the state of New York
+ * we will file the EZ tax-exemption form
+ * need to make a decision between [B and U tax exemption class](http://www.nccsdataweb.urban.org/PubApps/nteeSearch.php?gQry=allMajor&codeType=NTEE)
+ * we may need to revise the language of the bylaws if we are to file in a specific category
+ * Deyan and Frédéric will finalize this offline
+
+7. Affiliates
+ - Frédéric reports 2 organizations have shown interest in becoming "MathML partners", as well as a couple of individuals have already shown enthusiasm for being "MathML friends".
+ - Moritz reports several potential "MathML friends", without yet investing any real time in raising awareness.
+ - Deyan, Raniere and Michael haven't approached anyone.
+ - We have general agreement that we should finalize the infrastructure and start contacting interested parties to join. Encouraging to already see early enthusiasm from potential partners.
+
+8. Next steps
+ - Make the process for becoming a "MathML Friend", as easy as possible (mailing list, other ideas). Finalize on GitHub and vote next meeting.
+ - Recruit high profile people in the advisory board
+ - Donations - we need to start researching bank accounts, and open one, in parallel to establishing tax-exempt status.
+ - Determine the end of the fiscal year, ask for expert advice on the accounting technicalities.
diff --git a/meetings/board-2015-10-28.md b/meetings/board-2015-10-28.md
new file mode 100644
index 0000000..a32fa9c
--- /dev/null
+++ b/meetings/board-2015-10-28.md
@@ -0,0 +1,81 @@
+---
+layout: page
+title: Board Meeting 2015-10-28
+---
+
+Attendees:
+
+- Deyan Ginev,
+- Frédéric Wang,
+- Michael Kohlhase,
+- Moritz Schubotz,
+- Raniere Silva,
+
+Session Chair: Frédéric.
+
+Minutes Scribe: Deyan.
+
+Venue: Mumble
+
+## Minutes
+
+1. Deyan's pending 2016 status, implications:
+ - Tax exemption - can not apply before certain
+ - Bank account - same, also needs further investigations in NYC. Decision to investigate alternatives in Germany.
+ - Maybe think of a sibling organization in Germany.
+ - Deyan will give an update the moment he knows more
+
+2. Companies want to give us financial backing, but we have no account.
+ - How about a private person accepting money with MathML association endorsement? We do not like this idea, prefer to wait for exemption+account.
+
+3. We welcome Moritz to the meeting
+
+4. Decision is reached to wait for more information on Deyan's situation in 2016.
+ - meanwhile look for alternatives in Germany and France in case of negative news.
+
+5. Friends
+ 1. Moritz alerts us to people being careful of their privacy and not wanting to immediately go on a public list.
+ - Maybe use the directors list for first signups?
+ - Michael suggests having two lists - a private and a public one.
+ - Deyan: maybe "MathML World" and "MathML Friends"?
+ - General agreement on: 1) sending applications to the directors@ list, 2) sending announcements to the friends@ and world@ lists.
+
+ 2. Vote: Friends applications are privately approved to directors@, the application grants us permission to publish their names, and optional affiliation and homepage of each friend on the affiliation's website, mailing lists and legal documents. Approved applications are announced on a public mailing list.
+ - unanimously approved, 5 in favour, 0 against
+
+ 3. Michael suggests a "drive for friends" after the infrastructure is in place, to enhance the legitimacy of the organization as a community venue. Everyone will contact their private networks, Deyan will make public announcements.
+
+ 4. Moritz suggests to aim for X friends until the end of 2015. Deyan suggests 100. Michael asks if we have an "approval officer" that accepts/rejects applications.
+
+ 5. Vote: Moritz becomes an approval officer who approves/rejects member applications unless a comment is raised by a MathML director on the directors@ mailing list prior to that in 24 hours. Directors can step in to help if Moritz asks them to.
+ - unanimously approved, 5 in favour, 0 against
+
+6. Slogan
+ 1. Moritz suggests a turn-based voting procedure that trims down suggestions until we reach a winner. We proceed to vote as follows:
+ 2. Vote, round 1:
+ - The MathML Association, a math group acting on the Web ; short: A group action for MathML (1 in favour)
+ - Math Meets Web (1 in favour)
+ - Mathemizing the web (1 in favour)
+ - Web Math Matters (1 in favour)
+ - Promoting Math on the Web for All (1 in favour)
+ - all others have 0 votes
+
+ 2. Discussion:
+ - The discussion is slowly homing in on two options
+ 1. "A group action for MathML"
+ 2. "Web Math Matters"
+
+ 3. Vote, round 2: We vote on "electing 2 slogans as a first step to deciding on 1."
+ - 4 in favour, 1 abstained - vote is approved
+ - we decide to use slogan "A group action for MathML" for the website and slogan "Web Math Matters" for twitter, for now.
+
+7. Next steps:
+ - Raniere creates mailing lists (public for world + private for friends)
+ - Frédéric helps with the application process for friends
+ - Once infrastructure is in place, we start the "friend drive"
+ - Deyan will send an update the moment he has more info about NYC status
+ - Frédéric should put a list of "fundable" topics on the website, so that patrons know what the association can do.
+ - Next meeting for end of November
+
+8. Misc:
+ - MathML working group update: Michael had a longer discussion, positive attitude at the end of discussion, for both association and note.
diff --git a/meetings/board-2015-11-30.md b/meetings/board-2015-11-30.md
new file mode 100644
index 0000000..024f4d0
--- /dev/null
+++ b/meetings/board-2015-11-30.md
@@ -0,0 +1,62 @@
+---
+layout: page
+title: Board Meeting 2015-11-30
+---
+
+Attendees:
+
+- Deyan Ginev,
+- Frédéric Wang,
+- Michael Kohlhase,
+- Moritz Schubotz,
+- Raniere Silva,
+
+Session Chair: Frédéric.
+
+Minutes Scribe: Deyan.
+
+Venue: Mumble
+
+## Minutes
+
+1. Discuss progress on Form 1023 EZ, bank account, donations
+ - Deyan made contact with Aaron Krowne, will receive legal opinion soon
+ - Deyan's details got postponed until mid-December 2015, so we'll wait for then before acting
+
+2. Discuss progress on affiliates. Vote for https://github.com/MathML/website/pull/43
+ - 5 in favour, unanimously accepted
+
+ - Association Friends discussion
+ - Michael asks we are more proactive in recruiting a larger number of friends
+ - Moritz suggests adding a web form
+ - General agreement that we should move forward with sending announcement emails to mailing lists for MathML Association, to not waste attention
+ - Michael will contact the W3C working group
+ - Deyan will prepare an announcement email that has a link to the Friends page.
+
+ - Project ideas
+ - Come up with a first association-backed project to fund-raise for. The association will give an official "thumbs up" endorsement, but won't hold the actual funds. Moritz points out that specific projects are easier to fund, as opposed to a general "anything mathml" fund.
+ - Frédéric: Math fonts project
+ - Moritz: WikiMedia Math project (mutliple possible funding sources), RESTbase? umbrella project for renderers
+ - Deyan: We should maintain a list of active MathML-related projects on our site.
+ - We should have at least one "donation opportunity" on the association web page.
+
+3. Vote: Re-elect Moritz, Deyan and Frédéric as board members for the following term
+ - Michael and Raniere have unanimously approved
+ - Details to be sorted out on github
+
+4. Discuss work to do for the end of the year: accounting, relections, Annual Activity Report
+ - Raniere asks for deyan to forward the end-of-the-year financial forms
+ - Michael will add a first draft of the Annual Activity Report
+
+ - Vote: Board office positions for 2016, all current board members agree to maintain their positions.
+ - +5 unanimously approved
+ - Domain renewals are done for 2016, mathml.org still taken, but mathml3.org is available
+
+5. Web Engine Hackfest http://www.webengineshackfest.org/
+ - Frédéric will help Igalia with WebKit MathML support, maybe recruite MathML friends
+ - We'll feature it as a MathML Association account
+ - Frédéric will post a short presentation for feedback from the directors
+
+6. Misc
+ - Frédéric: Fork of webkit mathml work under the MathML association to increase visibility?
+ - Next meeting in early January, Raniere will make a doodle for exact date and time
diff --git a/meetings/board-2016-01-07.md b/meetings/board-2016-01-07.md
new file mode 100644
index 0000000..92f1ed0
--- /dev/null
+++ b/meetings/board-2016-01-07.md
@@ -0,0 +1,54 @@
+---
+layout: page
+title: Board Meeting 2016-01-07
+---
+
+Attendees:
+
+- Deyan Ginev,
+- Frédéric Wang,
+- Michael Kohlhase,
+- Raniere Silva,
+
+Session Chair: Frédéric.
+
+Minutes Scribe: Deyan.
+
+Venue: https://meet.jit.si/mathml
+
+Agenda: https://github.com/MathML/website/wiki/Board-Meeting-January-2016---Announcement
+
+## Minutes
+
+0. We mark Moritz' absence (plane rerouted)
+
+1. yearly task: accounting, annual activity report, changing fiscal year.
+ 1. Vote on https://github.com/MathML/website/pull/48
+ - 4 in favour, unanimously approved
+ - We also agree to keep the annual reports with the Feb 1 - Jan 31 duration,
+
+ 2. Discuss progress on Form 1023 EZ, bank account, donations
+ - Bank account selection by end of next week, Deyan will email around
+ - Form submission of accounting and exemption by the end of January, by Deyan
+ - Raniere will proofread
+
+
+2. Budget brainstorming:
+ - Background costs for MathML association - web presence, bank account, possible legal costs
+ - Projects (with price tags), so that affiliates have an idea what to contribute to:
+ * Development of native MathML for browsers
+ - work on MathML in WebKit, later in Blink
+ - work on Noto Math fonts
+ * Funding hackathons/browser workshop meetings
+ - Ask Aaron about receiving and paying money before the tax exemption is official? Until then wait for the procedures to complete.
+
+4. Discuss progress on affiliates.
+ - We need more friends
+ - Should we call them "supporters"?
+ - Should we use PR to encourage more signups?
+ - Wait progress on adminstrative side before contacting back sponsors/partners.
+
+5. Misc:
+ - As possible actions: We can do PR, represent a community, and funnel money. We should work harder on all fronts.
+ - Devise a broader message to attract a wider community, who is not technical, and not yet familiar with MathML.
+ - Appeal to all directors: Work on growing our community, and raise awareness. Homework: bring in 5 friends
diff --git a/meetings/board-2016-10-25.md b/meetings/board-2016-10-25.md
new file mode 100644
index 0000000..68d60e9
--- /dev/null
+++ b/meetings/board-2016-10-25.md
@@ -0,0 +1,49 @@
+---
+layout: page
+title: Board Meeting 2016-10-25
+---
+
+Attendees:
+
+- Deyan Ginev,
+- Frédéric Wang,
+- Moritz Schubotz,
+
+Session Chair: Frédéric.
+
+Venue: #mathml freenode IRC
+
+Agenda: plan for next year.
+
+## Minutes
+
+0. Michael and Raniere are absent.
+
+1. We starts by reviewing the current status of each one since the last meeting:
+ * Moritz has left [TU Berlin](https://www.tu-berlin.de). He works at [University Konstanz](https://www.uni-konstanz.de) and focuses on his PhD.
+ * Fred joined [Igalia](http://igalia.com/) on March but still lives in Paris. He has worked on MathML in WebKit during first semester, but he is now on Chromium/Wayland development.
+ * Deyan has been on leave from [Authorea](https://www.authorea.com/) from mid-October to focus on his PhD at [FAU](https://www.fau.de/). He is in Bulgaria, still pending a visa to return to the US.
+ * We are not sure about the status & plan of Michael and Raniere. From sporatic email discussions, Raniere has moved from Brazil to Manchester while Michael is still moving from Jacobs University (Bremen) to [FAU](https://www.fau.de/) (Erlangen).
+ Given all these changes in everyone's life, we have been very busy to organize a meeting or work on the US Association paperwork.
+
+2. We checks the status of "MathML in HTML5" implementation note and test suite:
+ * Test suite has been moved to the offical [W3C repository](https://github.com/w3c/web-platform-tests/tree/master/mathml) ; yay!
+ * Igalia gave feedback on the Math WG mailing list. David Carlisle seemed positive about using this implementation note to help browser implementers. However, the Math WG is currently closed and it will take some time before it is re-chartered. We will count on Michael to continue discussion there.
+
+3. Fred explains the work done by Igalia:
+ * [MathML developments in WebKit](https://webkit.org/blog/6803/improvements-in-mathml-rendering/)
+ * Discussions between Google and Igalia on MathML at [BlinkOn6](https://blogs.igalia.com/mrego/2016/06/21/my-blinkon6-summary-grid-layout-houdini-and-mathml/) or the Web Engines Hackfest (see [rego](https://blogs.igalia.com/mrego/2016/11/15/recap-of-the-web-engines-hackfest-2016/), [fred](http://frederic-wang.fr/fonts-at-the-web-engines-hackfest-2016.html) and [javi](https://blogs.igalia.com/jfernandez/2016/10/09/web-engines-hackfest-2016/)'s reports).
+ * Basically, Igalia proposed to [import WebKit's new code](https://github.com/fred-wang/chromium.src/tree/mathml) but Google developers are refactoring their code to support a [new layout API](https://drafts.css-houdini.org/css-layout-api/) so they would prefer something based on it. Discussion is still in progress.
+ * Deyan and Moritz like what's happening and look forward to hear more.
+
+4. Moritz mentions some work he did:
+ * [Facebook page](https://www.facebook.com/mathml3)
+ * [Mention of MathML/Wikipedia](http://www.mathunion.org/fileadmin/imu-net/pdfs/2016/IMU-Net-79.pdf)
+ * Discussion at OpenMath Workshop at CICM.
+ * We have one new friend.
+
+5. Legal status for next year:
+ * We discuss the possibility to close the US association given the uncertainty on having a permanent resident to manage the paperwork. Deyan said we can keep it as it for now, there won't be any legal issues as we basically have done no financial transactions. Fred higlighted that 2017 is the last year to apply to the tax-exempt status.
+ * We discuss the possibility to move the association to Germany. Fred asks whether there are any specific concerns. Moritz thinks it should not be a problem at all. There is some work to do but many of his friends have experience on it.
+ * We agree to keep the US association open for now and consider moving to Germany when that becomes necessary. However, we want to continue this discussion with Raniere and Michael too.
+
diff --git a/meetings/board-2017-01-31.md b/meetings/board-2017-01-31.md
new file mode 100644
index 0000000..286a54d
--- /dev/null
+++ b/meetings/board-2017-01-31.md
@@ -0,0 +1,66 @@
+---
+layout: page
+title: Board Meeting 2016-01-31
+---
+
+Attendees:
+
+- Michael Kohlhase,
+- Moritz Schubotz,
+- Raniere Silva,
+- Deyan Ginev,
+
+Guest:
+
+- Frédéric Wang,
+
+Session Chair: Michael Kohlhase
+
+Scribe: Moritz Schubotz
+
+Venue: jitsi
+
+Agenda: plan for next year.
+
+## Minutes
+
+1. Moritz is the scribe. Raniere and Deyan have issues to connect to jitsi,
+ we had sporadic communication by other channels and were at least able to ask
+ their votes.
+1. We welcome Fred as a guest to the board meeting.
+1. Moritz and Deyan re-elect Michael and Raniere as directors.
+ **Unanimous agreement. 2 in favor. 0 against. 0 abstention.**
+1. State of the association:
+ Already discussed issues with the US organization, no
+ additional points.
+1. Vote to elect officers:
+ * President: Michael
+ * Vice-president: Moritz
+ * Secretary: Deyan
+ * Treasurer: Raniere
+ * Friends officer: Moritz
+
+ **Unanimous agreement. 4 in favor. 0 against. 0 abstention.**
+1. Moving the association to Germany and opening bank accounts
+ * We discuss potential issues (non-germans might have problems to donate
+ etc) but agree that it is now better than the situation of the US one.
+ * Vote to mandate Moritz and Michael to move ahead.
+ **Unanimous agreement. 4 in favor. 0 against. 0 abstention.**
+ * Vote to close the NYC association once MathML e.V. is established and working, latest to the end of the US business year. **Unanimous agreement. 4 in favor. 0 against. 0 abstention.**
+ * Proposed German charter. Fred raised changes/amendments with respect to
+ the US one.
+ Fred will merge the purposes of the two associations and Moritz will
+ translate it to german.
+ * We need 7 founding members for founding the German association.
+ Moritz and Michael have already found 6 members. Moritz and Fred have other
+ people in mind they can contact.
+ * We discuss bank accounts and processes for that.
+ Moritz will send the list again.
+1. Where do we want to be in Jan 2018?
+ This point is open for online discussion. We agree that we should at least
+ fund one project.
+1. Vote to approve the [report for 2016](http://mathml-association.org/reports/2016.html) written by Michael.
+ **Unanimous agreement. 3 in favor. 0 against. 1 abstention (Michael).**
+1. moving the web pages to github pages (less work, more reliable?)
+ Moritz is fine with that. However, Fred and Michael prefer to wait for
+ Raniere as he is the one who has managed this.
diff --git a/meetings/meetings.md b/meetings/meetings.md
new file mode 100644
index 0000000..0f5da06
--- /dev/null
+++ b/meetings/meetings.md
@@ -0,0 +1,20 @@
+---
+layout: page
+title: Meetings
+---
+
+# Board Meetings
+
+Below are the minutes for the board meetings, where the directors discuss
+future actions for the MathML Association and vote for important decisions.
+You may also read [the wiki page with agendas for the board meetings](https://github.com/MathML/website/wiki#agendas-of-board-meetings). In general,
+board meetings are open to the public and everybody is welcome to attend them.
+
+* [2017-01-31](board-2017-01-31.html)
+* [2016-10-25](board-2016-10-25.html)
+* [2016-01-07](board-2016-01-07.html)
+* [2015-11-30](board-2015-11-30.html)
+* [2015-10-28](board-2015-10-28.html)
+* [2015-09-18](board-2015-09-18.html)
+* [2015-08-05](board-2015-08-05.html)
+* [2015-05-20](board-2015-05-20.html)
diff --git a/news.md b/news.md
new file mode 100644
index 0000000..71f05f5
--- /dev/null
+++ b/news.md
@@ -0,0 +1,26 @@
+---
+layout: page
+title: News
+---
+
+
+
+{% for post in site.posts %}
+{% if site.wpm %}
+{% assign readtime = post.content | strip_html | number_of_words | append: '.0' | divided_by:site.wpm %}
+{% else %}
+{% assign readtime = post.content | strip_html | number_of_words | append: '.0' | divided_by:180 %}
+{% endif %}
+{% assign modifiedtime = post.modified | date: "%Y%m%d" %}
+{% assign posttime = post.date | date: "%Y%m%d" %}
+
+
+{{ post.title }}
+
+
+{{ post.date | date: "%d %b %Y" }} {% if post.modified %}{% if modifiedtime != posttime %} and last modified on {{ post.modified | date: "%d %b %Y" }} {% endif %}{% endif %}
+
+
+{% endfor %}
+
+
diff --git a/people/directors.md b/people/directors.md
new file mode 100644
index 0000000..320a562
--- /dev/null
+++ b/people/directors.md
@@ -0,0 +1,67 @@
+---
+layout: page
+title: Board of Directors
+directors:
+- name: Deyan Ginev (Secretary)
+ description: Deyan Ginev is pursuing a PhD in Computer Science at Jacobs University Bremen, with a focus on semantic enrichment of TeX formulas into Content MathML. He is also a core developer for LaTeXML, Authorea and PlanetMath.
+ photo: img/people/ginev.deyan.jpg
+ email:
+ github: dginev
+ twitter:
+ website:
+- name: Michael Kohlhase (President)
+ description: Dr. Michael Kohlhase is professor for Computer Science at FAU Erlangen-Nürnberg. His research interests range from automated reasoning to eLearning via natural language semantics and the Semantic Web.
+ photo: img/people/kohlhase.michael.jpg
+ email: michael.kohlhase@fau.de
+ github: kohlhase
+ twitter:
+ website: http://kwarc.info/kohlhase
+- name: Moritz Schubotz (Vice-President; Friends Officer)
+ description: Moritz Schubotz alias Physikerwelt is research associate at Technische Universität Berlin. His research vision is to find instantiations of mathematical concepts independent of the concrete representation in huge corpora of human readable documents.
+ photo: img/people/schubotz.moritz.jpg
+ email:
+ github: physikerwelt
+ twitter:
+ website:
+- name: Raniere Silva (Treasuere)
+ description: Raniere Silva holds a BSc in applied mathematics from University of Campinas and is involved with MathML as an enthusiast. He is also a core developer for Software Carpentry.
+ photo: img/people/silva.raniere.jpg
+ email: raniere@ime.unicamp.br
+ github: r-gaia-cs
+ twitter: rgaiacs
+ website: http://rgaiacs.com
+---
+
+{% for people in page.directors %}
+
+
+{%if people.photo %}
+
+{% endif %}
+
+
+
+{% endfor %}
diff --git a/people/index.md b/people/index.md
new file mode 100644
index 0000000..8c9e11e
--- /dev/null
+++ b/people/index.md
@@ -0,0 +1,7 @@
+---
+layout: page
+title: People
+---
+
+- [Directors](directors.html)
+- [Officers](officers.html)
diff --git a/people/officers.md b/people/officers.md
new file mode 100644
index 0000000..076bd84
--- /dev/null
+++ b/people/officers.md
@@ -0,0 +1,23 @@
+---
+layout: page
+title: Officers
+officers:
+ - name: Michael Kohlhase
+ role: President
+ email: president
+ - name: Moritz Schubotz
+ role: Vice-President; Friends Officer
+ email: vice-president
+ - name: Deyan Ginev
+ role: Secretary
+ email: secretary
+ - name: Raniere Silva
+ role: Treasurer
+ email: treasurer
+---
+
+
+{% for officer in page.officers %}
+{{officer.name}} , {{officer.role}}
+{% endfor %}
+
diff --git a/reports/2015.md b/reports/2015.md
new file mode 100644
index 0000000..c58bf1c
--- /dev/null
+++ b/reports/2015.md
@@ -0,0 +1,63 @@
+---
+layout: page
+title: Reports
+---
+
+# Annual Activity Report 2015: MathML Association
+
+The main activity of the Mondial Association for Tools Handling MathML, ltd (for short,
+MathML Association) in 2015 has been setting up the organization structure, starting
+outreach campaigns to make the Association more known, liaising with other MathML-related
+organizations, and starting first technical projects to enhance MathML support in
+browsers.
+
+In the following we tabulate the activities chronologically
+
+* ''2015-02-24'' submitted our application as a charitable organization under the Not-for-Profit Corporation Law of the State of New York.
+* ''2015-05-20'' May Board Meeting ([minutes](/meetings/board-2015-05-20.html))
+ * elected our [directors](/directors.html)
+ * approved [by laws](/legal-documents/non-profit-corporate-by-laws.html) and [conflict of interest policy](/legal-documents/conflict-of-interest-policy.html).
+
+* ''2015-05-29'' first web site at http://mathml-association.org
+* ''2015-08-05'' August Board Meeting ([minutes](/meetings/board-2015-08-05.html))
+ * approved [manifesto](/legal-documents/manifesto.html),
+ * approved [logo](/logo/)
+ * [document about affiliates](/legal-documents/affiliates.html)
+ * minor amendments of [by laws](/legal-documents/non-profit-corporate-by-laws.html).
+
+* ''2015-09-18'' September Board Meeting ([minutes](/meetings/board-2015-09-18.html))
+ * appointed [officers](/people/officers.html):
+ * worked towards tax-exempt status
+ * Association featured on W3C site
+
+* ''2015-10-10'' published a first draft of the
+["MathML in HTML5" implementation note](http://www.mathml-association.org/MathMLinHTML5/)
+to supplement the [MathML specification](http://www.w3.org/TR/MathML3/) with suggested
+rules for low-level presentation implementation rules.
+
+* ''2015-11-05'' started "MathML Friends program" with [MathML Friends
+list](http://mathml-association.org/affiliates/friends.html) page and [mailing
+list](http://lists.mathml-association.org/mailman/listinfo/friends).
+
+* ''2015-10-28'' October Board Meeting ([minutes](/meetings/board-2015-10-28.html))
+ * vote on friends process
+ * elected Moritz as "friends officer".
+ * adopted two slogans: "A group action for MathML" for the website and "Web Math Matters" for twitter.
+
+* ''2015-11-07'' started "MathML Fonts" initiative for (drastically) enhancing
+ [font MathML support in browsers](/2015/11/07/math-fonts.html).
+
+* ''2015-10-28'' October Board Meeting ([minutes](/meetings/board-2015-10-28.html))
+ * vote on friends process
+ * elected Moritz Schubotz as "friends officer".
+ * adopted two slogans: "A group action for MathML" for the website and "Web Math Matters" for twitter.
+
+* '' 2015-11-30" November Board Meeting ([minutes](/meetings/board-2015-11-30.html))
+ * re-elected current slate of directors for 2016.
+ * progress on financial matters.
+
+
+
+
+
diff --git a/reports/2016.md b/reports/2016.md
new file mode 100644
index 0000000..5e96224
--- /dev/null
+++ b/reports/2016.md
@@ -0,0 +1,37 @@
+---
+layout: page
+title: Reports
+---
+
+# Annual Activity Report 2016: MathML Association
+
+The main activity of the Mondial Association for Tools Handling MathML, ltd (for short,
+MathML Association) in 2016 has been starting outreach campaigns to make the Association
+more known, liaising with other MathML-related organizations, and starting first technical
+projects to enhance MathML support in browsers.
+
+In general the work of the Association in 2016 has been hindered by
+* constraints imposed by the incorporation as a New York organization
+* moves between institutions by its directors
+* insecurities about NY as a stable operational basis.
+In particular, as a cause of this, we have not resolved the matter of initiating financial
+transactions for funding browser enhancements as planned.
+
+In the following we tabulate the activities chronologically
+
+* ''2016-01-07'' January Board Meeting [minutes](/meetings/board-2016-01-07.html)
+* "2016-01-21" Frédéric Wang announced he will join Igalia the 1st of March and thus will step down as a director since this could potentially cause conflict of interests when the board has to decide funding of MathML projects.
+* "2016-02-15" [Borrero Law Firm of NY will act as legal advisors](http://mathml-association.org/announcement/2016/02/15/borrero-law.html).
+* "2016-05-31" Wikipedia enables MathML [news](http://mathml-association.org/announcement/2016/05/31/wikipedia.html).
+* "2016-07-22" Sharing [announcement on MathML]((https://twitter.com/webkit/status/756489720893411329) by WebKit's project.
+* "2016-08" Unsuccessfully tried to transfer project funds to the
+ [Web Engines Hackfest](http://www.webengineshackfest.org/2016/) to support MathML
+ enthusiasts and development.
+* "2016-07-21" OpenMath recognizes content MathML as an official OpenMath encoding.
+* "2016-10-19" Move MathML in HTML5 test suite to W3C's web-platform-tests (last pull requests merged on 2016/11/10).
+* ''2016-10-25'' October Board Meeting [minutes](/meetings/board-2016-10-15.html).
+* ''2017-01-31'' Janary 2017 Board Meeting [minutes](/meetings/board-2017-01-31.html).
+
+
+
diff --git a/reports/index.md b/reports/index.md
new file mode 100644
index 0000000..8a8805a
--- /dev/null
+++ b/reports/index.md
@@ -0,0 +1,15 @@
+---
+layout: page
+title: Reports
+---
+
+# Annual Activity Reports
+
+Below you will find annual reports on the activities of the MathML Association
+together with comments from the Advisory Board.
+
+* [2016](2016.html) (no comments from the Advisory Board yet; it still has to be formed)
+* [2015](2015.html) (no comments from the Advisory Board yet; it still has to be formed)
+
+**Note: For the activities of the current year you can follow our progress by reading
+ the minutes of our [meetings](/meetings/meetings.html).**