asciidoctor-gb 0.1.5 → 0.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0e74c10bb5c5ef4dcbb40fa28b9a2b95315ef490
-  data.tar.gz: d4e2cf404084836479de5227a6edc20386a7d3cf
+  metadata.gz: dde71ee22c7d9f57a034fff500279cd20f9f63f4
+  data.tar.gz: 8bec67da431dc355fe300e148d5aad1671ade332
 SHA512:
-  metadata.gz: d7b096f300072f93091ad9c45f4a2f1c89aa899f2fcedc8a66dc360c2d2312f3aae30bfabcea163106afa885efd1eb2af3e6aade90d13cff629b34a570b2ae52
-  data.tar.gz: f94152cb53559addd5c825a53cec42470969457543b4cb0f1257d3138bc0193bf076663aa50065e3da8db7e9153577b89abe9f1e92448e0d96a0237a9e497957
+  metadata.gz: ec348da462b2dee6d45ecbcdf4511d4b8d1af91d30488d68ab844859b16c7c0fc8260ca49c7d31367a5bbfb3de9fa649e999b302a58d8f7e12e510caa1c7751e
+  data.tar.gz: ed293d2f15a9fb3bf81d73df1385f01e0836c05d8f6e9c54e85b1f29fc44865a63a3eabb244a0054a55f89511cb0e41b07a42084880b5af6a2408e762ff5e007

data/.rubocop.tb.yml

@@ -352,8 +352,18 @@ Style/TrailingCommaInArguments:
     - no_comma
   Enabled: true
 
-Style/TrailingCommaInLiteral:
-  Description: 'Checks for trailing comma in array and hash literals.'
+Style/TrailingCommaInArrayLiteral:
+  Description: 'Checks for trailing comma in array literals.'
+  StyleGuide: 'https://github.com/bbatsov/ruby-style-guide#no-trailing-array-commas'
+  EnforcedStyleForMultiline: comma
+  SupportedStylesForMultiline:
+    - comma
+    - consistent_comma
+    - no_comma
+  Enabled: true
+
+Style/TrailingCommaInHashLiteral:
+  Description: 'Checks for trailing comma in hash literals.'
   StyleGuide: 'https://github.com/bbatsov/ruby-style-guide#no-trailing-array-commas'
   EnforcedStyleForMultiline: comma
   SupportedStylesForMultiline:
@@ -398,6 +408,13 @@ Layout/AlignParameters:
   StyleGuide: 'https://github.com/bbatsov/ruby-style-guide#no-double-indent'
   Enabled: false
 
+Layout/ConditionPosition:
+  Description: >-
+                 Checks for condition placed in a confusing position relative to
+                 the keyword.
+  StyleGuide: 'https://github.com/bbatsov/ruby-style-guide#same-line-condition'
+  Enabled: false
+
 Layout/DotPosition:
   Description: 'Checks the position of the dot in multi-line method calls.'
   StyleGuide: 'https://github.com/bbatsov/ruby-style-guide#consistent-multi-line-chains'
@@ -450,13 +467,6 @@ Lint/CircularArgumentReference:
   Description: "Don't refer to the keyword argument in the default value."
   Enabled: false
 
-Lint/ConditionPosition:
-  Description: >-
-                 Checks for condition placed in a confusing position relative to
-                 the keyword.
-  StyleGuide: 'https://github.com/bbatsov/ruby-style-guide#same-line-condition'
-  Enabled: false
-
 Lint/DeprecatedClassMethods:
   Description: 'Check for deprecated class method calls.'
   Enabled: false
@@ -523,7 +533,7 @@ Lint/UnderscorePrefixedVariableName:
   Description: 'Do not use prefix `_` for a variable that is used.'
   Enabled: false
 
-Lint/UnneededDisable:
+Lint/UnneededCopDisableDirective:
   Description: >-
                  Checks for rubocop:disable comments that can be removed.
                  Note: this cop is not disabled when disabling all cops.

data/LICENSE

@@ -0,0 +1,25 @@
+BSD 2-Clause License
+
+Copyright (c) 2018, Ribose
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/README.adoc

@@ -1,45 +1,157 @@
-= asciidoctor-gb
+= asciidoctor-gb: Authoring Chinese standards (GuoBiao, sector...) in AsciiDoc
 
 image:https://img.shields.io/gem/v/asciidoctor-gb.svg["Gem Version", link="https://rubygems.org/gems/asciidoctor-gb"]
 image:https://img.shields.io/travis/riboseinc/asciidoctor-gb/master.svg["Build Status", link="https://travis-ci.org/riboseinc/asciidoctor-gb"]
 image:https://codeclimate.com/github/riboseinc/asciidoctor-gb/badges/gpa.svg["Code Climate", link="https://codeclimate.com/github/riboseinc/asciidoctor-gb"]
 
-Gem for generating https://en.wikipedia.org/wiki/Guobiao_standards[Guibiao standards]
-(Chinese national standards), using Asciidoc. This gem inherits from 
-https://github.com/riboseinc/asciidoctor-iso, a gem used to generate ISO standards
-using Asciidoc. The two standards formats are closely aligned. Refer to the ISO gem
-for guidance, including https://github.com/riboseinc/asciidoctor-iso/wiki/Guidance-for-authoring
+Ruby gem for generating
+https://en.wikipedia.org/wiki/Guobiao_standards[Guibiao standards]
+(Chinese national standards), using AsciiDoc.
 
-The Gem can also be used to generate Chinese local or sector standards, which have the 
-same format; the gem formats the title page to have the correct metadata displayed.
+This gem implements the https://github.com/riboseinc/gbdoc[GbDoc] data model,
+which inherits from
+https://github.com/riboseinc/isodoc-models[IsoDoc and StandardDocument].
 
-== Differences from asciidoctor-iso
+The code of this gem inherits from
+https://github.com/riboseinc/asciidoctor-iso[asciidoctor-iso], a gem used to
+generate ISO standards using Asciidoc.
+
+The two standards formats are closely aligned. Refer to the ISO gem
+for guidance, including
+https://github.com/riboseinc/asciidoctor-iso/wiki/Guidance-for-authoring[IsoDoc: Guidance for authoring]
+
+The gem can also be used to generate Chinese local or sector standards, which
+have the same format; the gem formats the title page to have the correct
+metadata displayed.
+
+The gem generates Word and HTML output. The Word output of the gem is strictly
+aligned to the GB/T 1.1 specification, including the fonts and font sizes
+prescribed, and the measurements for element positioning on the page.
+
+== Differences from `asciidoctor-iso`
 
 === Document Attributes
 
-In the following, "GB standard" should be read to refer to any Chinese national, sector or local standard. Asterisked document attributes are mandatory.
-
-`:title-intro-zh:`, `:title-main-zh:`*, `:title-part-zh:`:: These are the title introduction, main title, and part title in Chinese. (They replace their French counterparts in asciidoctor-iso.)
-`:title-intro-en:`, `:title-main-en:`*, `:title-part-en:`:: These are the title introduction, main title, and part title in English. (They form the document subtitle, instead of the document title as in asciidoctor-iso.)
-`:technical-committee-type:`:: The type of the technical committee (`technical` or `provisional`).
-`:iso-standard`: A corresponding ISO standard that the GB standard relates to. Format is full document code, then optionally comma followed by document title; e.g. `ISO/IEC 27001:2013, Information security management systems`
-`:equivalence:`:: The relation of the GB standard to the corresponding ISO standard (`equivalent`, `identical`, `nonequivalent`). Defaults to `equivalent`.
-`:obsoletes`:: A corresponding GB standard that this GB standard obsoletes. Format is full document code, then optionally comma followed by document title; e.g. `GB/T 22080-2008`
-`:obsoletes-parts:`: A list of bibliographic localities in the corresponding GB standard that this GB standard obsoletes. These are formatted the same way as the localities in citations; e.g. `clause 7-9, clause 11`
-`:scope:`:: The scope of the GB standard (`national`, `sector`, `professional`, `local`, `enterprise`). Defaults to `national`.
-`:mandate:`:: The mandate of the GB standard (`mandatory`, `recommended`, `guidelines`). Defaults to `mandatory`.
-`:prefix:*`:: The prefix classifying the GB standard. (Refer to https://github.com/riboseinc/gbdoc/blob/master/models/gb-standard-national-prefix.adoc, https://github.com/riboseinc/gbdoc/blob/master/models/gb-standard-sector-prefix.adoc, https://github.com/riboseinc/gbdoc/blob/master/models/gb-standard-local-prefix.adoc.)
-`:published-date:`* :: The date on which the GB standard was published.
-`:activated-date:`* :: The date on which the GB standard was activated.
-`:library-ics:`* :: The international categorisation number for the GB standard
-`:library-l:`* :: The L-identifier (library) for the GB standard
+In the following, "GB standard" should be read to refer to any Chinese
+national, sector or local standard. Asterisked document attributes are
+mandatory.
+
+`:title-intro-zh:`, `:title-main-zh:`*, `:title-part-zh:`::
+These are the title introduction, main title, and part title in Chinese.
+The intro and part titles are optional.
+(They replace their French counterparts in
+https://github.com/riboseinc/asciidoctor-iso[asciidoctor-iso].)
+
+`:title-intro-en:`, `:title-main-en:`*, `:title-part-en:`::
+These are the title introduction, main title, and part title in English.
+The intro and part titles are optional.
+(They form the document subtitle, instead of the document title as in
+https://github.com/riboseinc/asciidoctor-iso[asciidoctor-iso].)
+
+`:technical-committee-type:`::
+The type of the technical committee (`technical` or `provisional`).
+
+`:iso-standard:`::
+(optional) A corresponding ISO standard that the GB standard relates to. Format
+is full document code, then optionally comma followed by document title;
+e.g. `ISO/IEC 27001:2013, Information security management systems`
+
+`:equivalence:`::
+(optional, only valid if there is a corresponding `:iso-standard:`)
+The relation of the GB standard to the corresponding ISO standard
+(`equivalent`, `identical`, `nonequivalent`). Defaults to `equivalent`.
+
+`:obsoletes:`::
+(optional)
+A corresponding GB standard that this GB standard obsoletes. Format is full
+document code, then optionally comma followed by document title;
+e.g. `GB/T 22080-2008`
+
+`:obsoletes-parts:`::
+A list of bibliographic localities in the corresponding GB standard that this
+GB standard obsoletes. These are formatted the same way as the localities in
+citations; e.g. `clause 7-9, clause 11`
+
+`:scope:`::
+The scope of the GB standard (`national`, `sector`, `professional`, `local`,
+`enterprise`). Defaults to `national`.
+
+`:mandate:`::
+The mandate of the GB standard (`mandatory`, `recommended`, `guidelines`).
+Defaults to `mandatory`.
+
+`:topic:`::
+The topic of the GB standard (`basic`, `health-and-safety`, `environment-protection`, `engineering-and-construction`, `product`, `method`, `management-techniques`, `other`). Defaults to `basic`.
+
+`:prefix:`::
+The prefix classifying the GB standard.
+(Refer to
+https://github.com/riboseinc/gbdoc/blob/master/models/gb-standard-national-prefix.adoc[GB National Standard Prefixes],
+https://github.com/riboseinc/gbdoc/blob/master/models/gb-standard-sector-prefix.adoc[GB Sector Standard Prefixes],
+https://github.com/riboseinc/gbdoc/blob/master/models/gb-standard-local-prefix.adoc[GB Local Standard Prefixes],
+https://github.com/riboseinc/asciidoctor-gb/issues/54[GB Social and Enterprise Standard Prefixes].)
+Any `/Z` or `/T` suffix (indicating "recommended" and "guidelines" mandate) is 
+ignored unless the `:mandate:` attribute is not given. Any `Q/` or `T/` prefix for social and enterprise
+standards is ignored unless the `:scope:` attribute is not given.
+
+`:issued-date:`::
+The date on which the GB standard was issued (authorised for publication by the issuing authority).
+
+`:published-date:`::
+The date on which the GB standard was published (distributed by the publisher).
+
+`:implemented-date:`::
+The date on which the GB standard became active.
+
+`:created-date:`::
+The date on which the first version of the GB standard was created.
+
+`:updated-date:`::
+The date on which the current version of the GB standard was updated.
+
+`:obsoleted-date:`::
+The date on which the GB standard was obsoleted/revoked.
+
+`:confirmed-date:`::
+The date on which the GB standard was reviewed and approved by the issuing authority.
+
+`:library-ics:`::
+The ICS (International Categorization for Standards) number for the GB standard. There may be more than one ICS for a document; if so, they should be comma-delimited. (Unlike the case for ISO, the ICS identifier is output to the front page of the GB standard.)
+
+`:library-ccs:`::
+The CCS (Chinese Categorization Scheme) code for the GB standard. See https://github.com/riboseinc/cn-ccs-codes
+
+`:plan-number:`::
+The Plan Number (计划单号) for the GB standard.
+
+`:issuer:`::
+The issuer of the standard. This is the authority which authors, manages, and issues the standard. For social standards, this is the social group; for enterprise standards, this is the company. The issuer appears on the standard frontispiece. By default, the issuer is inferred from the prefix of the standard; this attribute overrides the value inferred from the prefix. It is required for social and entperprise standards.
+
+`:publisher:`::
+The publisher of the standard, which distributes the standard. This is distinct from the issuer, the authority which authors, manages, and issues the standard.
+
+`:proposer:`::
+The party which proposed the standard.
+
+`:authority:`::
+The authority which sponsored the standard.
+
+`:author:`::
+The individuals who drafted the standard.
+
+`:author-committee:`::
+The committees which drafted the standard.
+
+`:title-font:`::
+The font to use for the standard class and issuer on the (Word) cover page; described in GB/T 1.1 as 
+"custom font". If not provided, the font is inferred from the scope of the standard, aligning
+with existing practice: SimSun for national scope, SimHei for all other scopes.
 
 === Language macros
 
-In Terms and Definitions, preferred terms, alternate terms and deprecated
-terms are expected to be given in both Chinese and English. By default,
-the gem does this by detecting space-delimited runs of Han or Latin script
-text:
+In Terms and Definitions, preferred terms, alternate terms and deprecated terms
+are expected to be given in both Chinese and English. By default, the gem does
+this by detecting space-delimited runs of Han or Latin script text:
 
 [source,asciidoc]
 --
@@ -54,7 +166,7 @@ alt:[rough rice 糙米]
 However if there is script mixing in a term -- if the Chinese term contains
 a Latin script acronym or a mathematical expression, for example -- the
 Chinese term will not be detected correctly. To address this, the formatting macros
-+`[zh]#...#`+ and +`[en]#...#`+ are used. If they are present, then the content
+`+[zh]#...#+` and `+[en]#...#+` are used. If they are present, then the content
 of those macros is treated as the Chinese and English equivalents of the
 parent node instead:
 
@@ -70,8 +182,124 @@ alt:[[en]#rough rice# [zh]#糙米#]
 <admitted language="zh">糙米</admitted> <admitted language="en">rough rice</admitted>
 --
 
-Unfortunately no further markup is permitted within the +`[zh]#...#`+ and +`[en]#...#`+ 
-macros by Asciidoctor, and Asciidoctor does not correctly nest inline macros within other
-inline macros (so +`alt:[en:[_xyz_] zh:[xyz]`+  would not give correct behaviour either.)
+Unfortunately no further markup is permitted within the `+[zh]#...#+` and
+`+[en]#...#+` macros by Asciidoctor, and Asciidoctor does not correctly nest
+inline macros within other inline macros (so `+alt:[en:[_xyz_] zh:[xyz]+`
+would not give correct behaviour either.)
+
+Localisation strings can be used anywhere else in the document where the
+grammar permits localised strings (notably in bibliographic data). For example,
+a bibliographic title can be given in two languages as follows. (Note that formatting appears outside the language macros.)
+
+[source,asciidoc]
+--
+[[[ISO7301,ISO 7301:2011]]], _[zh]#大米 - 规格# [en]#Rice -- Specification#_
+--
+
+[source,xml]
+--
+  <bibitem id="ISO7301" type="standard">
+   <title language="zh">大米 - 规格</title> <title language="en">Rice&#x2011;Specification</title>
+  <docidentifier>ISO 7301</docidentifier>
+  <date type="published">
+    <from>2011</from>
+  </date>
+  <contributor>
+    <role type="publisher"/>
+    <organization>
+      <name>International Organization for Standardization</name>
+      <abbreviation>ISO</abbreviation>
+    </organization>
+  </contributor>
+</bibitem>
+--
+
+The gem also supports `+[zh-Hant]#...#+` and `+[zh-Hans]#...#+` to
+differentiate traditional and simplified script in ISOXML; `zh-Hant` is
+provisionally supported through changing font in the output.
+
+== Caveats
+
+=== Microsoft Word
+
+The Word output is meticulously aligned to the GB/T 1.1 specification, which is highly
+prescriptive on the positioning of elements on the page. This means that the Word output
+uses http://www.addbalance.com/word/frames_textboxes.htm[frames] and 
+https://en.wikipedia.org/wiki/Vector_Markup_Language[VML] extensively, as the best mechanism 
+Word HTNL has to ensure precise positioning of elements. However, the use of frames
+makes Word documents more cumbersome to edit; it is envisaged that the bulk of document
+editing should be happening in Asciidoctor, with Word treated as a write-only output format.
+
+The use of VML and frames is mostly confined to the cover page, which is the most heavily
+prescribed by GB/T 1.1. However, Word as of 2016 suppresses space before a paragraph
+after a page break (though not a section break--which means that the Foreword, Introduction,
+Document Title, Annex and Bibliography titles would all either lose their mandated initial
+space in Word, or else would all have to be treated as separate sections. For that reason,
+those headings are instead treated by this gem as frames (in-line with their following text),
+which preserve their initial spacing.
+
+=== GB/T 1.1 Compliance
+
+GB/T 1.1-2009 prescribes the format of GB standards meticulously, and is based on ISO/IEC DIR 2-2004
+(though it is not equivalent, and ISO/EIC DIR 2 is less prescriptive about layout). 
+GB issued a template program for generating compliant Word documents
+in 2010; this program no longer executes on Windows. (This gem has extracted its stylesheet for
+use in formatting output, but the stylesheet itself had to be modified in places to comply with
+GB/T 1.1.)
+
+Compliance of GB standards with GB/T 1.1 has been patchy. This has been exacerbated by the fact that
+ISO/IEC DIR 2 was substantially revised in 2011 and again in 2016. Although GB/T 1.1 has not been
+updated to align with ISO/IEC DIR 2-2016, published GB standards increasingly are formatted according
+to ISO in most areas where ISO and GB now conflict.
+
+This gem attempts to align with current best practice of GB standards, and does so in consultation with
+GB. GB/T 19018-2017 has been used as the exemplar standard.
+
+The following area the areas where the gem's Word output aligns with or deviates from GB/T 1.1-2009.
+
+* https://github.com/riboseinc/asciidoctor-gb/issues/58[Measurements (GB/T 1.1 Annex I.)] The gem
+scrupulously aligns with the measurements prescribed in GB/T, to a greater extent than the 2010
+template tool. As already noted, it makes extensive use of frames to ensure correct vertical positioning
+of headers, and of elements on the cover page.
+
+* https://github.com/riboseinc/asciidoctor-gb/issues/56[Fonts (GB/T 1.1 Annex J.)] The gem aligns
+with the fonts and font sizes prescribed in GB/T. (The only exception is the standard name, for which a
+point size of 72 is quite unrealistic: 26pt is used instead, in compliance with the preexisting Word 
+template.) For Simplified Chinese script, the gem uses by default SimSun as its "serif" font, and SimHei 
+has its "sans-serif" font; this reflects practice in the 
+Word templates used for GB. For Latin script, it uses Cambria as its serif font, and Calibri as its
+sans-serif font; this is to minimise disruption moving between scripts. (Note that the stylesheets
+make minimal use of boldface and italics, as these are not well-matched with Chinese typography;
+the sans-serif font occupies the niche that boldface occupies in ISO Latin-script documents.)
++
+GB/T 1.1 prescribes a "custom font" for the standard class and standard issuer on the cover page.
+By default, this is the serif font for standards with national scope, and the sans-serif font for
+all other scopes. All font selections can be overriden in the document attributes (`:bodyfont:`,
+`:headerfont:`, `:titlefont:`.)`
+
+* https://github.com/riboseinc/asciidoctor-gb/issues/57[Layout (GB/T 1.1 Clause 9.)]. The gem complies
+with GB/T 1.1, with the following exceptions where it follows ISO/IEC DIR 2-2016 practice instead:
+
+** 9.3: There are no separate tables of figures, tables of tables, or tables of annexes. Table of Contents
+indentation in the 2010 stylesheet did not comply with GB/T 1.1.
+
+** 9.5.2: Normal references and Bibliography references are indented like normal paragraphs, instead of
+having a hanging indent ("on overflow they should be indented to the top level"); in fact, GB/T 1.1
+does not follow this in its own references list.
+
+** 9.5.3: Terms and Definitions is aligned with ISO/IEC DIR 2: there is provision for alternate and
+deprecated terms, and term sources are notated in brackets whether they are modified or direct citations
+from the source document, instead of being treated as a note in the latter case. 
+(https://github.com/riboseinc/asciidoctor-gb/issues/67) Clauses numbers are separated from the term
+source reference by a dash. References to terms defined elsewhere in the Terms and Definitions clause
+are accompanied with clause references.
+
+** 9.9.3: Figure footnotes are not longer treated as footnotes, but are instead merged into the figure
+key, as is done in ISO/IEC DIR 2. Footnote indentation and note indentation in the 2010 stylesheet 
+did not comply with GB/T 1.1.
+
+** 9.9.4: Example labels do not appear on a separate line. Examples like notes have a hanging indent,
+so that their content is left-aligned.
 
-The gem also supports +`[zh-Hant]#...#`+ and +`[zh-Hans]#...#`+ to differentiate traditional and simplified script in ISOXML; `zh-Hant` is provisionally supported through changing font in the output.
+** 9.9.5: Formulas are centered in the page, but are not connected with the formula number with a
+dotted tab.

data/asciidoctor-gb.gemspec

@@ -31,11 +31,12 @@ Gem::Specification.new do |spec|
   spec.add_dependency "htmlentities", "~> 4.3.4"
   spec.add_dependency "image_size"
   spec.add_dependency "mime-types"
-  spec.add_dependency "nokogiri", "~> 1.8.1"
+  spec.add_dependency "nokogiri"
   spec.add_dependency "ruby-jing"
   spec.add_dependency "ruby-xslt"
   spec.add_dependency "thread_safe"
   spec.add_dependency "uuidtools"
+  spec.add_dependency "twitter_cldr"
   spec.add_dependency "asciidoctor-iso"
   spec.add_dependency "isodoc"
 

data/bin/rspec

@@ -0,0 +1,18 @@
+#!/usr/bin/env ruby
+  
+# This file was generated by Bundler.
+#
+# The application 'rspec' is installed as part of a gem, and
+# this file is here to facilitate running it.
+#
+
+require "pathname"
+ENV["BUNDLE_GEMFILE"] ||= File.expand_path(
+  "../../Gemfile", Pathname.new(__FILE__).realpath
+)
+
+require "rubygems"
+require "bundler/setup"
+
+load Gem.bin_path("rspec-core", "rspec")
+