EIA Writing Style Guide April 2015

Total Page:16

File Type:pdf, Size:1020Kb

EIA Writing Style Guide April 2015 EIA Writing Style Guide April 2015 U.S. Energy Information Administration Office of Communications This publication is available on the EIA employee intranet and at: www.eia.gov/eiawritingstyleguide.pdf U.S. government publications are not subject to copyright protection, but you should acknowledge EIA as the source if you use or reproduce this content. Contents Introduction to the EIA Writing Style Guide ........................................................................ 1 Chapter 1: Editorial Voice and Words and Phrases To Avoid .............................................. 9 Chapter 2: Policy-Neutral Writing ....................................................................................... 19 Chapter 3: Advice for Good Writing .................................................................................... 21 Chapter 4: Grammar ........................................................................................................... 29 Chapter 5: Commonly Misused Words .............................................................................. 33 Chapter 6: Capitalization.................................................................................................... 47 Chapter 7: Numbers ............................................................................................................ 57 Chapter 8: Commas .............................................................................................................. 67 Chapter 9: Hyphens and Dashes .......................................................................................... 73 Chapter 10: Colons and Semicolons ..................................................................................... 83 Chapter 11: Periods .............................................................................................................. 87 Chapter 12: Symbols ............................................................................................................. 91 Chapter 13: Punctuating and Formatting Quoted Text........................................................ 93 Chapter 14: Abbreviations and Units................................................................................... 97 Chapter 15: Itemized Lists and Bullets ................................................................................ 107 Chapter 16: Footnotes, Sources, and Notes ........................................................................ 113 Chapter 17: Hypertext Links ................................................................................................ 121 Chapter 18: British versus American English...................................................................... 125 Index .................................................................................................................................... 129 Introduction to the EIA Writing Style Guide This style guide is an update of the edition released in November 2012. 1 Why a writing style guide? We wrote this Writing Style Guide to help EIA writers produce consistent, correct, and readable content. It provides guidance on those style issues—including capitalization, punctuation, word usage, tone—most relevant to EIA writing. This edition includes new content: • An index to help you find major topics • Information on using and sourcing nonoriginal work and third-party data • Direction to use CO2, b (rather than bbl for barrel), and the % sign in all EIA Did you know? content This version of the EIA • An update on classic writing guidance Writing Style Guide • An alphabetized list of hyphenated and nonhyphenated words reflects the latest • Advice on copyediting and using spellcheck to find mistakes thinking of writers • Guidance on using endnotes as a sourcing option and editors at EIA. • Description of different uses of the letter M in energy units The fundamental principles are the • Format for writing mathematical equations same, but a few • Information about writing in plain language rules have changed. This new edition also includes more examples, explanations, advice, and notes. We included this additional material to answer the hundreds of questions asked by EIA staff, to address writing mistakes caught while editing EIA content, and to cover a few new writing style preferences. The 2015 EIA Writing Style Guide is provided in html on the EIA employee intranet (InsideEIA) and at www.eia.gov/eiawritingstyleguide.pdf, which allows you to search or link to related sections of the document. Two rules were changed since the 2012 Writing Style Guide was published and have already been incorporated into EIA writing: • Use the % sign in all EIA writing • Write online as one word in all uses (on the computer, when a pipeline or electricity generator opens or is operating) Because the content was written to help you and has been improved by your questions and comments, the Office of Communications welcomes feedback, suggestions, corrections, and general comments. The Writing Style Guide is designed to save you time. Have you ever wondered or worried about which was correct: • Periods or no punctuation for bullets? • Which or that? • % sign or percent? You can quickly find answers to these questions—and most of your style-related questions—in this Writing Style Guide. 2 U.S. Energy Information Administration | EIA Writing Style Guide Do these guidelines apply to print and web content? This Writing Style Guide will help you produce uniform documents, regardless of office, function, or publication form. The purpose of the Writing Style Guide is to provide style consistency in all EIA content. It addresses some issues that are particular to web writing, such as writing effective hypertext links. But most of the advice applies to all the writing you do including reports, website content, and PowerPoint presentations. Are these hard-and-fast rules? This is a Writing Style Guide—not a rule book. Unlike grammar, which has specific rules that should not be broken, many style issues are preferences, such as how and when to write out numbers, whether to use the serial comma, or when to use ending punctuation for bullets. Writers and editors may differ. Famous style guides differ. Areas of the world differ. Our goal is to provide guidance on style issues, so EIA content has uniformity that conveys professionalism. Examples labeled preferred mean preferred by EIA. Style consistency enhances our credibility. Inconsistencies in style or misused words cause users of our information to question the accuracy of our data. A uniform style tells users that EIA has high quality standards for our words as well as for our numbers. Where can I get more guidance on editorial style? We’ve addressed the most common style issues that EIA writers face. If you have a question that isn’t covered in this guide, or if there is a topic you’d like to know more about, consult these online references: • The Chicago Manual of Style, the most widely used style manual. EIA has a subscription to The Chicago Manual of Style • U.S. Government Printing Office (GPO) Style Manual, an authoritative source of information about issues that are specific to writing for the federal government • Merriam-Webster’s Collegiate Dictionary, EIA’s preferred dictionary Other sources consulted in the preparation of EIA’s Writing Style Guide: • Grammar Girl’s Quick and Dirty Tips for Better Writing, Mignon Fogarty, 2008 • Merriam-Webster’s Dictionary of English Usage, 1994 • The Elements of Style, William Strunk and E. B. White, 1999 • OECD Style Guide, Second edition, 2007 • The Subversive Copy Editor: Advice from Chicago, Carol Fisher Saller, 2009 • EERE Communication Standards and Guidelines: Style Guide, from the U.S. Department of Energy’s Office of Energy Efficiency and Renewable Energy • Woe Is I, Patricia T. O’Connor, 2003 Please contact Colleen Blessing or Dale Sweetnam in the Office of Communications with any questions, comments, or suggestions about writing or about the Writing Style Guide. U.S. Energy Information Administration | EIA Writing Style Guide 3 Writing well at EIA Use short sentences Short sentences are easier to read, so aim for a maximum of 20 to 30 words. Consider breaking a long sentence into two shorter sentences or eliminating unnecessary words. Use short paragraphs Did you know? Avoid long paragraphs or large blocks of text. Long paragraphs are daunting and difficult for readers to scan. Try to write paragraphs of four or five sentences, or Plain language is approximately 100–125 words. Paragraphs as short as one sentence are fine. Use the law, not just bullets to list points. something nice to do every so often or Avoid jargon s o m e t h i n g E I A i n v e n t e d . Jargon may be appropriate when writing exclusively for experts. But EIA’s web content The Plain Writing Act is accessible to a wide range of readers, from experts on your topic to novices. signed by President As much as possible, choose nontechnical terms so all your intended readers can Obama in October understand what you’ve written. If you must use jargon or technical language, be 2010 is a federal law sure to explain the term in simple language. You might also link to an EIA glossary that requires federal definition or to other source material. To make the concept clear to the layperson, executive agencies to you can provide an example or an analogy. use plain writing and to train employees in plain Be consistent writing. The law says Good writing is built on patterns, so be consistent within your content. federal agencies should write
Recommended publications
  • DCSA API Design Principles 1.0
    DCSA API Design Principles 1.0 September 2020 Table of contents Change history ___________________________________________________ 4 Terms, acronyms, and abbreviations _____________________________________ 4 1 Introduction __________________________________________________ 5 1.1 Purpose and scope ________________________________________________ 5 1.2 API characteristics ________________________________________________ 5 1.3 Conventions ____________________________________________________ 6 2 Suitable _____________________________________________________ 6 3 Maintainable __________________________________________________ 6 3.1 JSON _________________________________________________________ 6 3.2 URLs __________________________________________________________ 6 3.3 Collections _____________________________________________________ 6 3.4 Sorting ________________________________________________________ 6 3.5 Pagination______________________________________________________ 7 3.6 Property names __________________________________________________ 8 3.7 Enum values ____________________________________________________ 9 3.8 Arrays _________________________________________________________ 9 3.9 Date and Time properties ___________________________________________ 9 3.10UTF-8 _________________________________________________________ 9 3.11 Query parameters _______________________________________________ 10 3.12 Custom headers ________________________________________________ 10 3.13 Binary data _____________________________________________________ 11
    [Show full text]
  • The IHO S-100 Standard and E-Navigation Information
    e-NAV10/INF/7 e-NAV10 Information paper Agenda item 12 Task Number Author(s) Raphael Malyankar, Jeppesen Jarle Hauge, Norwegian Coastal Administration The IHO S-100 Standard and e-Navigation Information Concept Exploration with Ship Reporting Data and Product Specification 1 SUMMARY The papers describe an exploration in modeling substantially non-geographic maritime information using the S-100 framework, specifically notice of arrival and pilot requests in Norway. The Norwegian Coastal Administration is the National Competent Authority for the European SafeSeaNet (SSN) in Norway and thereby maintains a vessel and voyage reporting system intended for use by commercial marine traffic arriving and departing Norwegian ports. Data used in this system describes vessels, HAZMAT cargo, voyages, and information used in arranging pilotage. Jeppesen and the NCA has developed a product specification (the “NOAPR product specification”) based on the S-100 standard, for a subset of information used in the abovementioned system. The product specification describes the data model for ship reporting and pilot requests. The current version is a “proof-of-concept” intended to explore the development of S-100 compatible data models for non-geographic maritime information. The papers also discuss the use of the Geospatial Information Registry and the NOAPR Model. 1.1 Purpose of the document The product specification [NOAPR] demonstrates the feasibility of modelling ship notice of arrival and pilot requests using the data model compatible with S-100. 2 BACKGROUND The papers are a result of a mutual work between Jeppesen and the Norwegian Coastal Administration within the Interreg project; BLAST (http://www.blast-project.eu/index.php).
    [Show full text]
  • Syntactic Variation in English Quantified Noun Phrases with All, Whole, Both and Half
    Syntactic variation in English quantified noun phrases with all, whole, both and half Acta Wexionensia Nr 38/2004 Humaniora Syntactic variation in English quantified noun phrases with all, whole, both and half Maria Estling Vannestål Växjö University Press Abstract Estling Vannestål, Maria, 2004. Syntactic variation in English quantified noun phrases with all, whole, both and half, Acta Wexionensia nr 38/2004. ISSN: 1404-4307, ISBN: 91-7636-406-2. Written in English. The overall aim of the present study is to investigate syntactic variation in certain Present-day English noun phrase types including the quantifiers all, whole, both and half (e.g. a half hour vs. half an hour). More specific research questions concerns the overall frequency distribution of the variants, how they are distrib- uted across regions and media and what linguistic factors influence the choice of variant. The study is based on corpus material comprising three newspapers from 1995 (The Independent, The New York Times and The Sydney Morning Herald) and two spoken corpora (the dialogue component of the BNC and the Longman Spoken American Corpus). The book presents a number of previously not discussed issues with respect to all, whole, both and half. The study of distribution shows that one form often predominated greatly over the other(s) and that there were several cases of re- gional variation. A number of linguistic factors further seem to be involved for each of the variables analysed, such as the syntactic function of the noun phrase and the presence of certain elements in the NP or its near co-text.
    [Show full text]
  • AP Style Style Versus Rules
    Mignon Fogarty AP Style Style Versus Rules AP Style Why the AP Stylebook? AP Style What are the key differences in AP style? AP Style AP Style — Does not use italics. AP Style No Italics This means most titles go in quotation marks. AP Style Quotation Marks “Atomic Habits” (book) “Candy Crush”(computer game) “Jumanji” (movie) + opera titles, poem titles, album titles, song titles, TV show titles, and more AP Style No Quotation Marks — Holy Books (the Bible, the Quran) — Reference Books (Webster’s New World College Dictionary, Garner’s Modern English Usage) AP Style No Quotation Marks — Newspaper and Magazine Names (The Washington Post, Reader’s Digest) — Website and App Names (Yelp, Facebook) — Board Games (Risk, Settlers of Catan) AP Style Quotation Marks — Billy waited 30 seconds for “Magic the Gathering” to launch on his iPad. — The boys meet every Saturday at the game store to play Magic the Gathering. AP Style AP Style — Does not use italics. — Doesn’t always use the serial comma. AP Style Serial Comma red, white, and blue AP Style AP Style red, white and blue AP Style Serial Comma Do use it when series elements contain conjunctions. AP Style Serial Comma — Peanut butter and jelly — Ham and eggs — Macaroni and cheese AP Style AP Style I like peanut butter and jelly, ham and eggs, and macaroni and cheese. AP Style AP Style I like peanut butter and jelly, ham, and cheese. AP Style Serial Comma Do use it when series elements contain complex phrases. AP Style AP Style Squiggly wondered whether Aardvark had caught any fish, whether Aardvark would be home for dinner, and whether Aardvark would be in a good mood.
    [Show full text]
  • Number and Adjectives : the Case of Activity and Quality Nominals Delphine Beauseroy, Marie-Laurence Knittel
    Number and adjectives : the case of activity and quality nominals Delphine Beauseroy, Marie-Laurence Knittel To cite this version: Delphine Beauseroy, Marie-Laurence Knittel. Number and adjectives : the case of activity and quality nominals. 2012. hal-00418040v2 HAL Id: hal-00418040 https://hal.archives-ouvertes.fr/hal-00418040v2 Preprint submitted on 11 Jun 2012 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. 1 NUMBER AND ADJECTIVES: THE CASE OF FRENCH ACTIVITY AND QUALITY NOMINALS 1. INTRODUCTION This article is dedicated to the examination of the role of Number with regards to adjective distribution in French. We focus on two kinds of abstract nouns: activity nominals and quality nominals. Both display particular behaviours with regards to adjective distribution: activity nominals need to appear as count nouns to be modified by qualifying adjectives; concerning quality nominals, they are frequently introduced by the indefinite un(e) instead of the partitive article (du / de la) when modified. Our analysis of adjectives is based on the idea that they can have two uses, which correlate with syntactic and semantic restrictions and are distinguishable on semantic grounds. Adjectives are understood either as taxonomic, i.e.
    [Show full text]
  • Cross-Linguistic Evidence for Semantic Countability1
    Eun-Joo Kwak 55 Journal of Universal Language 15-2 September 2014, 55-76 Cross-Linguistic Evidence for Semantic Countability1 2 Eun-Joo Kwak Sejong University, Korea Abstract Countability and plurality (or singularity) are basically marked in syntax or morphology, and languages adopt different strategies in the mass-count distinction and number marking: plural marking, unmarked number marking, singularization, and different uses of classifiers. Diverse patterns of grammatical strategies are observed with cross-linguistic data in this study. Based on this, it is concluded that although countability is not solely determined by the semantic properties of nouns, it is much more affected by semantics than it appears. Moreover, semantic features of nouns are useful to account for apparent idiosyncratic behaviors of nouns and sentences. Keywords: countability, plurality, countability shift, individuation, animacy, classifier * This work is supported by the Sejong University Research Grant of 2013. Eun-Joo Kwak Department of English Language and Literature, Sejong University, Seoul, Korea Phone: +82-2-3408-3633; Email: [email protected] Received August 14, 2014; Revised September 3, 2014; Accepted September 10, 2014. 56 Cross-Linguistic Evidence for Semantic Countability 1. Introduction The state of affairs in the real world may be delivered in a different way depending on the grammatical properties of languages. Nominal countability makes part of grammatical differences cross-linguistically, marked in various ways: plural (or singular) morphemes for nouns or verbs, distinct uses of determiners, and the occurrences of classifiers. Apparently, countability and plurality are mainly marked in syntax and morphology, so they may be understood as having less connection to the semantic features of nouns.
    [Show full text]
  • Abbreviation with Capital Letters
    Abbreviation With Capital Letters orSometimes relativize beneficentinconsequentially. Quiggly Veeprotuberate and unoffered her stasidions Jefferson selflessly, redounds but her Eurasian Ronald paletsTyler cherishes apologizes terminatively and vised wissuably. aguishly. Sometimes billed Janos cancelled her criminals unbelievingly, but microcephalic Pembroke pity dustily or Although the capital letters in proposed under abbreviations entry in day do not psquotation marks around grades are often use Use figures to big dollar amounts. It is acceptable to secure the acronym CPS in subsequent references. The sources of punctuation are used to this is like acronyms and side of acronym rules apply in all capitals. Two words, no bag, no hyphen. Capitalize the months in all uses. The letters used with fte there are used in referring to the national guard; supreme courts of. As another noun or recognize: one are, no hyphen, not capitalized. Capitalize as be would land the front porch an envelope. John Kessel is history professor of creative writing of American literature. It introduces inconsistencies, no matter how you nurture it. Hyperlinks use capital letters capitalized only with students do abbreviate these varied in some of abbreviation pair students should be abbreviated even dollar amounts under. Book titles capitalized abbreviations entry, with disabilities on your abbreviation section! Word with a letter: honors colleges use an en dash is speaking was a name. It appeared to be become huge success. Consider providing a full explanation each time. In the air national guard, such as well as individual. Do with capital letter capitalized abbreviations in capitals where appropriate for abbreviated with a huge success will.
    [Show full text]
  • Time: Fifteen Minutes Goal: Use the Character Panel in Adobe Illustrator
    Activity 9: Type Hierarchy and Business Cards Time: Fifteen minutes Goal: Use the Character Panel in Adobe Illustrator and what you’ve learned about type to create a visual hierarchy and customize a personal business card. Activity: 1. Download Activity9_TypeHierarchy.ai from Canvas and open. 2. Explore the Character Panel. Change case here (CAPS, Camel case, etc.) Typeface Style Size Leading (space between lines) Kerning (space between Tracking (space between individual letters) letters) 3. Pick a typeface. 4. Fill in the business card with your information or fake information. You must include 5 pieces of information. 5. Style the text to create a clear visual hierarchy using using Typefaces, Size, Styling, Case, Tracking, and Leading. Visual Hierarchy: The visual order of elements on your business card or map. Big, bold elements draw your eye and rise to figure. Small, thin elements detract and are pushed into the background. Visual hierarchies layer elements visually and move your eye around a given page. Questions, Tips, and Tricks: How can you draw the eye using type (typeface, size, style, case, tracking, leading)? What do you want to stand out and what should be pushed further into the background? Make a list of elements on your business card and rank them from most important to least important. Style them accordingly. Submit: Export a (.png) of your business card and submit to Canvas. To Export, File > Export > Export As > Make sure Use Artboards is checked > Save. .
    [Show full text]
  • Examples of Sentences Using Quotation Marks
    Examples Of Sentences Using Quotation Marks Biogenous Parrnell misquotes presumingly while Sloane always overprizes his Goidelic interlaid semplice, he unhumanizes so insanely. Brilliant-cut Goose sometimes disafforest his maximum eastward and buss so strategically! Coronary Moises canvasses epigrammatically. This section for direct speech is to forget the quote remain in the proposition that the street in using quotation of examples sentences Either way, they are a very important type of punctuation! Everything else is secondary. Glad the post was helpful. This is a string in Markdown. Maybe a pirate ship. Put question marks and exclamation marks inside the quotation marks if the marks relate directly and only to the text within quotation marks. Jill told her mother. Come get a treat! Inside the US, inside the quotation marks. However, the closing quotation mark is only applied to the paragraph that contains the end of the quote. Why is it such a big deal? On the mysteries of combining quotation marks with other punctuation marks. Quotation marks used around words to give special effect or to indicate irony are usually unnecessary. DOL grammar, spelling and vocabulary lists, and assorted worksheets. The alien spaceship appeared right before my own two eyes. What time is the meeting? Perhaps the price was too high or you decided to go with another company. Nikki: The comma is perfect where it is. Punctuation marks are tools that have set functions. For those of you familiar with British English conventions, this is a change in style. Note first that what is enclosed in quotes must be the exact words of the person being quoted.
    [Show full text]
  • A Case Study in Language Change
    Western Michigan University ScholarWorks at WMU Honors Theses Lee Honors College 4-17-2013 Glottopoeia: A Case Study in Language Change Ian Hollenbaugh Western Michigan University, [email protected] Follow this and additional works at: https://scholarworks.wmich.edu/honors_theses Part of the Other English Language and Literature Commons Recommended Citation Hollenbaugh, Ian, "Glottopoeia: A Case Study in Language Change" (2013). Honors Theses. 2243. https://scholarworks.wmich.edu/honors_theses/2243 This Honors Thesis-Open Access is brought to you for free and open access by the Lee Honors College at ScholarWorks at WMU. It has been accepted for inclusion in Honors Theses by an authorized administrator of ScholarWorks at WMU. For more information, please contact [email protected]. An Elementary Ghau Aethauic Grammar By Ian Hollenbaugh 1 i. Foreword This is an essential grammar for any serious student of Ghau Aethau. Mr. Hollenbaugh has done an excellent job in cataloguing and explaining the many grammatical features of one of the most complex language systems ever spoken. Now published for the first time with an introduction by my former colleague and premier Ghau Aethauic scholar, Philip Logos, who has worked closely with young Hollenbaugh as both mentor and editor, this is sure to be the definitive grammar for students and teachers alike in the field of New Classics for many years to come. John Townsend, Ph.D Professor Emeritus University of Nunavut 2 ii. Author’s Preface This grammar, though as yet incomplete, serves as my confession to what J.R.R. Tolkien once called “a secret vice.” History has proven Professor Tolkien right in thinking that this is not a bizarre or freak occurrence, undergone by only the very whimsical, but rather a common “hobby,” one which many partake in, and have partaken in since at least the time of Hildegard of Bingen in the twelfth century C.E.
    [Show full text]
  • DTMB – MDE State of Michigan Coding Standards and Guidelines
    DTMB – MDE State of Michigan Coding Standards and Guidelines Revision History Date Version Description Author 01/04/2013 1.0 Initial Version Tammy Droscha 2/08/2013 1.1 Updated based on senior development teams Tammy Droscha and Drew Finkbeiner feedback. 12/07/2016 1.2 Updated the ADA Compliance Standards section Simon Wang and the Exceptions/Errors section DTMB – MDE Coding Standards and Guidelines V1.0, 2013 1 Introduction This document defines the coding standards and guidelines for Microsoft .NET development. This includes Visual Basic, C#, and SQL. These standards are based upon the MSDN Design Guidelines for .NET Framework 4. Naming Guidelines This section provides naming guidelines for the different types of identifiers. Casing Styles and Capitalization Rules 1. Pascal Casing – the first letter in the identifier and the first letter of each subsequent concatenated word are capitalized. This case can be used for identifiers of three or more characters. E.G., PascalCase 2. Camel Casing – the first letter of an identifier is lowercase and the first letter of each subsequent concatenated word is capitalized. E.G., camelCase 3. When an identifier consists of multiple words, do not use separators, such as underscores (“_”) or hyphens (“-“), between words. Instead, use casing to indicate the beginning of each word. 4. Use Pascal casing for all public member, type, and namespace names consisting of multiple words. (Note: this rule does not apply to instance fields.) 5. Use camel casing for parameter names. 6. The following table summarizes
    [Show full text]
  • Package 'Snakecase'
    Package ‘snakecase’ May 26, 2019 Version 0.11.0 Date 2019-05-25 Title Convert Strings into any Case Description A consistent, flexible and easy to use tool to parse and con- vert strings into cases like snake or camel among others. Maintainer Malte Grosser <[email protected]> Depends R (>= 3.2) Imports stringr, stringi Suggests testthat, covr, tibble, purrrlyr, knitr, rmarkdown, magrittr URL https://github.com/Tazinho/snakecase BugReports https://github.com/Tazinho/snakecase/issues Encoding UTF-8 License GPL-3 RoxygenNote 6.1.1 VignetteBuilder knitr NeedsCompilation no Author Malte Grosser [aut, cre] Repository CRAN Date/Publication 2019-05-25 22:50:03 UTC R topics documented: abbreviation_internal . .2 caseconverter . .2 check_design_rule . .6 parsing_helpers . .7 preprocess_internal . .8 relevant . .9 replace_special_characters_internal . .9 to_any_case . 10 to_parsed_case_internal . 14 1 2 caseconverter Index 16 abbreviation_internal Internal abbreviation marker, marks abbreviations with an underscore behind. Useful if parsing_option 1 is needed, but some abbrevia- tions need parsing_option 2. Description Internal abbreviation marker, marks abbreviations with an underscore behind. Useful if parsing_option 1 is needed, but some abbreviations need parsing_option 2. Usage abbreviation_internal(string, abbreviations = NULL) Arguments string A string (for example names of a data frame). abbreviations character with (uppercase) abbreviations. This marks abbreviations with an un- derscore behind (in front of the parsing). Useful if parsing_option
    [Show full text]