@airmark/quiver 0.32.2 → 0.34.0

package/quills/afmc_moa/0.0.1/example.md

@@ -0,0 +1,114 @@
+~~~
+$quill: afmc_moa
+$kind: main
+first_party_name: Air Force Example Test Center (AFETC)
+second_party_name: Navy Example Warfare Laboratory (NEWL)
+subject: Thermal-Vacuum Chamber Test Support
+agreement_number: FA1234-26-M-0017
+second_party_mailing_address:
+  - NEWL/CD
+  - 200 Sample Road, Building 12
+  - Example NAS ST 23456-7890
+reimbursable: true
+reimbursable_support: Scheduled use of the AFETC thermal-vacuum chamber, with operator and instrumentation technician support, for NEWL sensor qualification tests.
+estimated_amount: "$184,500"
+appropriation_fy: "2027"
+cost_center_provider: "AFETC-7730"
+cost_center_receiver: "NEWL-4102"
+financial_poc_provider: "Ms. Dana R. Whitfield, AFETC/FM, DSN 555-0140, dana.whitfield@example.mil"
+financial_poc_receiver: "Mr. Luis M. Ortega, NEWL/FM, DSN 555-0240, luis.ortega@example.mil"
+financial_additional_info: Funds are provided by Military Interdepartmental Purchase Request (MIPR) on a reimbursable basis. No advance payment is authorized.
+first_party_signatory: "HAROLD J. KESSLER, Commander"
+second_party_signatory: "MEREDITH A. CALLOWAY, Director"
+mid_point_review_due_date: 2029-04-01
+~~~
+
+~~~
+$kind: authorities
+~~~
+AUTHORITIES: This MOA is entered into under the authority of the Economy Act, Section 1535 of Title 31, United States Code, and DoD Instruction 4000.19, "Support Agreements."
+
+~~~
+$kind: purpose_and_scope
+~~~
+PURPOSE AND SCOPE: This MOA establishes the terms under which the AFETC provides thermal-vacuum chamber test support to the NEWL for the qualification of NEWL sensor payloads. It covers scheduling, test execution, data delivery and reimbursement for that support, and no other AFETC facility.
+
+~~~
+$kind: responsibilities_of_the_parties
+~~~
+RESPONSIBILITIES OF THE PARTIES:
+
+- The AFETC will—
+  - Schedule up to four chamber test windows per fiscal year for NEWL test articles.
+  - Provide chamber operators and instrumentation technicians for each scheduled test window.
+  - Deliver raw and reduced test data to the NEWL within 10 business days of test completion.
+- The NEWL will—
+  - Request each test window at least 60 days before its start.
+  - Deliver test articles, test procedures and hazard analyses to the AFETC at least 14 days before each test window.
+  - Reimburse the AFETC for the support in Attachment A.
+- Both Parties will—
+  - Conduct a joint safety review before each test window.
+  - Protect test data in accordance with its marking.
+
+~~~
+$kind: personnel
+~~~
+PERSONNEL: Each Party is responsible for all costs of its personnel, including pay and benefits, support, and travel. Each Party is responsible for supervision and management of its personnel. NEWL personnel present in the chamber area follow the direction of the AFETC test director on matters of safety.
+
+~~~
+$kind: general_provisions
+~~~
+GENERAL PROVISIONS:
+
+- POINTS OF CONTACT (POCS). The following POCs will be used by the Parties to communicate matters concerning this MOA. Each Party may change its POC upon reasonable notice to the other Party.
+  - For the AFETC—
+    - Primary POC: Mr. Thomas E. Brandt, Chamber Facility Manager, AFETC/TEO, DSN 555-0110, thomas.brandt@example.mil.
+    - Alternate POC: Capt Alicia N. Moreno, Test Director, AFETC/TEO, DSN 555-0111, alicia.moreno@example.mil.
+  - For the NEWL—
+    - Primary POC: Dr. Evan P. Hollis, Sensor Program Lead, NEWL/CD, DSN 555-0210, evan.hollis@example.mil.
+    - Alternate POC: LT Priya S. Raman, Test Engineer, NEWL/CD, DSN 555-0211, priya.raman@example.mil.
+- CORRESPONDENCE. All correspondence to be sent and notices to be given pursuant to this MOA will be addressed, if to the AFETC, to AFETC/TEO, 100 Example Avenue, Example AFB ST 12345-6789, and, if to the NEWL, to NEWL/CD, 200 Sample Road, Building 12, Example NAS ST 23456-7890, or as may from time to time otherwise be directed by the Parties.
+- REVIEW OF AGREEMENT. This MOA will be reviewed on or around the anniversary of its effective date annually for financial impacts; if there are substantial changes in resource requirements, the agreement will be reviewed in its entirety.
+- MODIFICATION OF AGREEMENT. This MOA may only be modified by the written agreement of the Parties, duly signed by their authorized representatives.
+- DISPUTES. Any disputes relating to this MOA will, subject to any applicable law, Executive Order, or DoD issuance, be resolved by consultation between the Parties.
+- TERMINATION OF AGREEMENT. This MOA may be terminated by either Party by giving at least 90 days' written notice to the other Party. The MOA may also be terminated at any time upon the mutual written consent of the Parties.
+- TRANSFERABILITY. This MOA is not transferable except with the written consent of the Parties.
+- ENTIRE AGREEMENT. It is expressly understood and agreed that this MOA embodies the entire agreement between the Parties regarding the MOA's subject matter, thereby merging and superseding all prior agreements and representations by the Parties with respect to such subject matter.
+- EFFECTIVE DATE. This MOA takes effect beginning on the day after the last Party signs.
+- EXPIRATION DATE. This MOA expires on 30 September 2031.
+- CANCELLATION OR MODIFICATION OF PREVIOUS AGREEMENT. This MOA modifies or cancels and supersedes the previously signed agreement between the same Parties with the subject Environmental Test Facility Support, Agreement # FA1234-21-M-0009 and effective date of 1 October 2021.
+- NO THIRD PARTY BENEFICIARIES. Nothing in this MOA, express or implied, is intended to give to, or will be construed to confer upon, any person or entity not a party any remedy or claim under or by reason of this MOA and this MOA will be for the sole and exclusive benefit of the Parties.
+- SEVERABILITY. If any term, provision, or condition of this MOA is held to be invalid, void, or unenforceable by a governmental authority and such holding is not or cannot be appealed further, then such invalid, void, or unenforceable term, provision, or condition shall be deemed severed from this MOA and all remaining terms, provisions, and conditions of this MOA shall continue in full force and effect. The Parties shall endeavor in good faith to replace such invalid, void, or unenforceable term, provision, or condition with valid and enforceable terms, provisions, or conditions which achieve the purpose intended by the Parties to the greatest extent permitted by law.
+- OTHER FEDERAL AGENCIES. This MOA does not bind any federal agency, other than the Parties, nor waive required compliance with any law or regulation.
+
+~~~
+$kind: financial_details
+~~~
+FINANCIAL DETAILS:
+
+- AVAILABILITY OF FUNDS. This MOA does not document the obligation of funds between the Parties. The obligation of funds by the Parties, resulting from this MOA, is subject to the availability of funds pursuant to the DoD Financial Management Regulation. No provision in this MOA will be interpreted to require obligation or payment of funds in violation of the Anti-Deficiency Act, Section 1341 of Title 31, United States Code.
+- BILLING. The AFETC will bill the NEWL on a monthly basis in accordance with the procedures of the Billing Party. A record of the transaction will be sent to the NEWL within 30 calendar days after the month in which the transaction occurred.
+- PAYMENT OF BILLS. The NEWL paying office will forward payments, along with a copy of billed invoices, to the AFETC within 30 calendar days of the date of invoice. Bills rendered will not be subject to audit in advance of payment.
+- FINANCIAL SPECIFICS. See Attachment A for all other details and information on the reimbursable support identified in this MOA. No allowance or advance payment is made under this MOA.
+- ECONOMY ACT DETERMINATION AND FINDINGS (D&F). If the MOA is being entered into in accordance with Section 1535 of Title 31, United States Code (the Economy Act), both Parties agree that the requirements listed in Paragraph (a) of the Economy Act have been met. The provider has determined that the capabilities exist to render the requested support without jeopardizing its assigned missions. Any required Economy Act D&F has been completed.
+
+~~~
+$kind: list_of_attachments
+~~~
+LIST OF ATTACHMENTS:
+
+- Attachment A, Financial Details
+- Attachment B, Chamber Test Window Schedule
+
+~~~
+$kind: attachment
+title: Chamber Test Window Schedule
+~~~
+The AFETC reserves the following thermal-vacuum chamber test windows for the NEWL in fiscal year 2027. Each window includes one day of chamber pump-down and one day of return to ambient.
+
+- 2-13 November 2026: NEWL Sensor Block 2, thermal balance.
+- 8-19 February 2027: NEWL Sensor Block 2, thermal cycling.
+- 10-21 May 2027: NEWL Sensor Block 3, thermal balance.
+- 9-20 August 2027: Reserved for retest.
+
+The NEWL confirms or releases each window at least 60 days before its start. A released window returns to the AFETC schedule without charge.

package/quills/afmc_moa/0.0.1/packages/typst-afmc-moa/src/config.typ

@@ -11,7 +11,7 @@
 // =============================================================================
 // TYPOGRAPHY
 // =============================================================================
-#let DEFAULT_BODY_FONTS = ("NimbusRomNo9L", "times new roman")
+#let DEFAULT_BODY_FONTS = ("NimbusRomNo9L",)
 
 // =============================================================================
 // DECIMAL OUTLINE NUMBERING

package/quills/classic_resume/0.0.1/Quill.yaml

@@ -0,0 +1,281 @@
+quill:
+  name: classic_resume
+  version: 0.0.1
+  backend: typst
+  description: Classic single-page resume
+
+typst:
+  plate_file: plate.typ
+
+# A resume is a stack of sections, and each kind of section is a card kind: a
+# heading, optional prose under it, and the rows that section holds. The rows
+# are the section's own, so an entry cannot land under the wrong heading.
+main:
+  description: "Your name and contacts head the page. Each section under them is a card, printed in the order the cards stand: add a card for every section you want."
+  ui:
+    groups: [identity, page]
+  # Everything prints under a section heading, so main carries no body: a
+  # summary is a Summary card.
+  body:
+    enabled: false
+  fields:
+    name:
+      type: string
+      ui:
+        group: identity
+      description: "Your name as you want it read, set large at the top. It also titles the exported PDF."
+
+    contacts:
+      type: array
+      items:
+        type: string
+      ui:
+        group: identity
+      description: "How to reach you, one per line and the one you want used first: an email address, a phone number, a profile such as linkedin.com/in/you, a city. They print in that order across the page under your name, a diamond between each. An email address, a web address or a phone number becomes a live link in the PDF."
+
+    paper:
+      type: enum
+      values:
+        - us-letter
+        - a4
+      default: us-letter
+      ui:
+        group: page
+        compact: true
+      description: "Page size."
+
+    font_size:
+      type: number
+      default: 12
+      ui:
+        group: page
+        compact: true
+      description: "Body text size in points, such as 11 or 11.5. Along with the margin, this is the lever for fitting a resume onto one page — drop a half point before you drop a bullet."
+
+    margin:
+      type: number
+      default: 0.5
+      ui:
+        group: page
+        compact: true
+      description: "Page margin in inches, the same on all four sides. The layout is dense by design; below about 0.4 a printer starts clipping."
+
+
+# Each kind opens with the heading it prints. Its `default:` is the usual one,
+# so a new card shows the heading it will print, and an authored "" prints
+# none.
+card_kinds:
+  summary:
+    title: Summary
+    description: "Prose under a heading: a few lines on who you are and the work you want next. Retitled, it is any section that is only prose, such as an objective."
+    seed:
+      $body: An engineer. Likes climbing rocks and making useful things.
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: Summary
+        description: "Printed in uppercase over a rule. An empty title prints no heading, which sets the summary straight under your name."
+
+  experience:
+    title: Experience
+    description: "Jobs, most recent first: employer and dates on the first line, role and location on the second, details under them."
+    seed:
+      jobs:
+        - company: Employer
+          dates: Month YYYY – Present
+          role: Job Title
+          location: City, ST
+          details: |
+            - What you did, and what it changed.
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: Work Experience
+        description: &title_description "Printed in uppercase over a rule. An empty title prints no heading."
+      jobs:
+        type: array
+        items:
+          type: object
+          properties:
+            company:
+              type: plaintext
+              inline: true
+              description: "Set in bold at the left of the first line."
+            dates: &dates
+              type: plaintext
+              inline: true
+              default: ""
+              description: "Set in bold at the right of the first line. Free text rather than a date, so a range reads as you write it: 'August 2024 – Present', 'December 2025'. Keep the form the same down the page."
+            role:
+              type: plaintext
+              inline: true
+              default: ""
+              description: "Your title, set in italics under the employer. Leave blank to omit."
+            location: &location
+              type: plaintext
+              inline: true
+              default: ""
+              description: "Set in italics at the right of the second line. 'Pittsburgh, PA', 'Remote'. Leave blank to omit; with the line's other half blank too, the second line is not printed."
+            details: &details
+              type: richtext
+              default: ""
+              description: "Set under the entry. Usually a bulleted list, one line each and strongest first; a sentence, *italics* and **bold** set as well, and a heading sets as a bold line. Leave blank for nothing under the entry."
+        description: "One row per job. A row is never split across a page break."
+
+  education:
+    title: Education
+    description: "Schools, most recent first: school and date on the first line, degree and location on the second."
+    seed:
+      schools:
+        - school: School
+          dates: Month YYYY
+          degree: Degree
+          location: City, ST
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: Education
+        description: *title_description
+      schools:
+        type: array
+        items:
+          type: object
+          properties:
+            school:
+              type: plaintext
+              inline: true
+              description: "Set in bold at the left of the first line."
+            dates: *dates
+            degree:
+              type: plaintext
+              inline: true
+              default: ""
+              description: "Degree and field, set in italics under the school. Leave blank to omit."
+            location: *location
+            details:
+              <<: *details
+              description: "Honors, activities, coursework, set under the entry. Most degrees need none."
+        description: "One row per school or degree."
+
+  skills:
+    title: Skills
+    description: "Skills in labelled groups, filled across the columns and then down."
+    seed:
+      skills:
+        - label: Category
+          items: Skill, Skill, Skill
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: Skills
+        description: *title_description
+      skills:
+        type: array
+        ui:
+          layout: table
+        items:
+          type: object
+          properties:
+            label:
+              type: plaintext
+              inline: true
+              description: "Set in bold, with its items on the line under it."
+            items:
+              type: plaintext
+              inline: true
+              description: "Usually comma separated. Printed as written — markup is the one thing a labeled row does not carry."
+        description: "One label and its items per row."
+      columns: &columns
+        type: integer
+        default: 2
+        ui:
+          compact: true
+        description: "Number of columns. Two suits items that run most of a line; three suits single words."
+
+  projects:
+    title: Projects
+    description: "Projects: name and link on the first line, details under them."
+    seed:
+      projects:
+        - name: Project
+          link: github.com/you/project
+          details: |
+            - What it does, and your part in it.
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: Projects
+        description: *title_description
+      projects:
+        type: array
+        items:
+          type: object
+          properties:
+            name:
+              type: plaintext
+              inline: true
+              description: "Set in bold at the left."
+            link:
+              type: string
+              default: ""
+              description: "Where to see it, set small and italic at the right as written: github.com/you/project reads better than its https:// form. A web address becomes a live link; anything else, such as 'closed source', prints as written. Leave blank to omit."
+            details: *details
+        description: "One row per project."
+
+  certifications:
+    title: Certifications
+    description: "A list filled across the columns and then down. Retitled, it holds any short items: awards, languages, clearances."
+    seed:
+      items:
+        - Certification (ABBREVIATION)
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: Certifications
+        description: *title_description
+      items:
+        type: array
+        items:
+          type: richtext
+          inline: true
+        description: "One item per line. Keep each to a line at the column width. Italicize with *asterisks*."
+      columns: *columns
+
+  other:
+    title: Other section
+    description: "A section the kinds above do not name — volunteer work, military service, publications, a competition. Rows take the Experience shape with neutral names."
+    seed:
+      title: Section Title
+      entries:
+        - heading: Entry
+          details: |
+            - What it was, and what came of it.
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        description: "Printed in uppercase over a rule. This section has no usual heading, so this one is yours to write."
+      entries:
+        type: array
+        items:
+          type: object
+          properties:
+            heading:
+              type: plaintext
+              inline: true
+              description: "Set in bold at the left of the first line."
+            dates: *dates
+            subtitle:
+              type: plaintext
+              inline: true
+              default: ""
+              description: "Set in italics under the heading. Leave blank to omit."
+            location: *location
+            details: *details
+        description: "One row per item. A section that is only prose is a Summary with a title of its own."

package/quills/classic_resume/0.0.1/example.md

@@ -0,0 +1,111 @@
+~~~
+$quill: classic_resume
+$kind: main
+name: John Doe
+contacts:
+  - john.doe@example.com
+  - (555) 123-4567
+  - github.com/johndoe
+  - linkedin.com/in/johndoe
+  - Pittsburgh, PA
+paper: us-letter
+font_size: 11.5
+margin: 0.5
+~~~
+
+~~~
+$kind: summary
+~~~
+
+An engineer. Likes climbing rocks and making useful things.
+
+~~~
+$kind: certifications
+title: Active Certifications
+columns: 2
+items:
+- Offensive Security Certified Professional (OSCP)
+- GIAC Cyber Threat Intelligence (GCTI)
+- CompTIA CASP+, CySA+, Sec+, Net+, A+, Proj+
+- GIAC Machine Learning Engineer (GMLE)
+~~~
+
+~~~
+$kind: skills
+columns: 2
+skills:
+- label: Programming
+  items: Python, R, JS, C#, Rust, PowerShell, CI/CD
+- label: Data Science
+  items: ML/statistics, TensorFlow, AI Engineering
+- label: IT & Cybersecurity
+  items: AD DS, Splunk, Metasploit, Wireshark, Nessus
+- label: Cloud
+  items: AWS EC2/S3, Helm, Docker, Serverless
+~~~
+
+~~~
+$kind: experience
+jobs:
+- company: Templar Archives Research Division
+  dates: August 2024 – Present
+  role: Psionic Research Analyst
+  location: Aiur
+  details: |
+    - Analyzed Khala disruption patterns following Amon's corruption, developing countermeasures to protect remaining neural link infrastructure.
+    - Building automated threat detection pipelines using Khaydarin crystal arrays to monitor Void energy signatures across the sector.
+- company: Terran Dominion Ghost Academy
+  dates: May 2025 – July 2025
+  role: Covert Ops Trainee
+  location: Tarsonis (Remote)
+  details: |
+    - Developed tactical HUD displays for Ghost operatives integrating real-time Zerg hive cluster intelligence.
+- company: Raynor's Raiders
+  dates: January 2018 – June 2020
+  role: Combat Engineer
+  location: Mar Sara
+  details: |
+    - Administered Hyperion shipboard systems, SCV maintenance protocols, and bunker defense automation for 30,000+ colonists.
+~~~
+
+~~~
+$kind: education
+schools:
+- school: Carnegie Mellon University
+  dates: December 2025
+  degree: Master of Information Technology Strategy
+  location: Pittsburgh, PA
+- school: United States Air Force Academy
+  dates: May 2024
+  degree: BS, Data Science
+  location: Colorado Springs, CO
+  details: |
+    - Distinguished Graduate (top 10%); Chinese language minor (L2+/R1 on DLPT).
+~~~
+
+~~~
+$kind: other
+title: Cyber Competition
+entries:
+- heading: 1st in SANS Academy Cup 2024
+  details: |
+    - Competed as the Delogrand Web Exploit SME, solving SQLi, API, and HTTP packet crafting problems.
+- heading: 1st in NCX 2023
+  details: |
+    - Developed strategies, defensive scripts, and exploits for the Cyber Combat event.
+    - Analyzed logs with Bash and Python for the Data Analysis event.
+~~~
+
+~~~
+$kind: projects
+title: Selected Projects
+projects:
+- name: TongueToQuill
+  link: tonguetoquill.com
+  details: |
+    - Rich markdown editor for perfectly formatted USAF and USSF documents with Claude MCP integration.
+- name: Quillmark
+  link: github.com/nibsbin/quillmark
+  details: |
+    - Parameterization engine for generating arbitrarily typesetted documents from markdown content.
+~~~

package/quills/classic_resume/0.0.1/packages/ttq-classic-resume/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Nibs
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/quills/classic_resume/0.0.1/packages/ttq-classic-resume/fonts/EBGaramond/OFL.txt

@@ -0,0 +1,94 @@
+Copyright 2017 The EB Garamond Project Authors (https://github.com/octaviopardo/EBGaramond12)
+Copyright 2025 Deborah Khodanovich (RCS citation glyphs)
+
+This Font Software is licensed under the SIL Open Font License, Version 1.1.
+This license is copied below, and is also available with a FAQ at:
+http://scripts.sil.org/OFL
+
+
+-----------------------------------------------------------
+SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded, 
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.