rubypants-unicode 0.2.3 → 0.2.4

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 4116600599d67f38ec6adc0e3fad5e3d1d384ebc
+  data.tar.gz: 506e211a87944fe3a0a630946ed86cbfc412f461
+SHA512:
+  metadata.gz: b3e36d228bc33887dd6ec7835c99a820fb59db420442b52c1cb6fa932933fcc0fccbd8a91d865a8521c6c97970995f1c272181cb4b209164d117d6ed3e346edb
+  data.tar.gz: 957fd53c28e61ed65acc22fab96566689a6c55d8d0ad3a1a932f41cc45e991fe5c35e0219de7e2cbd161e2bd707243f33301a1d27d457fc4ae9c611fbf5fcc27

data/lib/rubypants-unicode/rubypants-unicode.rb

@@ -44,7 +44,7 @@
 # quotes, em-dashes, and proper ellipses.
 # 
 # RubyPants does not modify characters within <tt><pre></tt>,
-# <tt><code></tt>, <tt><kbd></tt>, <tt><math></tt> or
+# <tt><code></tt>, <tt><kbd></tt>, <tt><math></tt>, <tt>style</tt>, or
 # <tt><script></tt> tag blocks. Typically, these tags are used to
 # display text where smart quotes and other "smart punctuation" would
 # not be appropriate, such as source code or example markup.
@@ -262,7 +262,7 @@ class RubyPants < String
     tokens.each { |token|
       if token.first == :tag
         result << token[1]
-        if token[1] =~ %r!<(/?)(?:pre|code|kbd|script|math)[\s>]!
+        if token[1] =~ %r!<(/?)(?:pre|code|kbd|script|style|math)[\s>]!
           in_pre = ($1 != "/")  # Opening or closing tag?
         end
       else

data/lib/rubypants-unicode/version.rb

@@ -1,3 +1,3 @@
-class RubyPants
-  VERSION = "0.2.3"
+class RubyPants < String
+  VERSION = "0.2.4"
 end

metadata

@@ -1,83 +1,74 @@
 --- !ruby/object:Gem::Specification
 name: rubypants-unicode
 version: !ruby/object:Gem::Version
-  version: 0.2.3
-  prerelease: 
+  version: 0.2.4
 platform: ruby
 authors:
+- John Gruber
+- Chad Miller
 - Christian Neukirchen
+- Jeremy McNevin
 - Chris Chapman
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-08-13 00:00:00.000000000 Z
+date: 2014-10-11 00:00:00.000000000 Z
 dependencies: []
-description: ! 'It just occurred to me that if we are encoding our HTML pages in UTF-8
-  to
-
+description: |
+  It just occurred to me that if we are encoding our HTML pages in UTF-8 to
   handle multiple languages and using web fonts with multilanguage support,
-
-  shouldn''t we be able to directly insert the simple apostrophe, ellipsis, and
-
+  shouldn't we be able to directly insert the simple apostrophe, ellipsis, and
   em-dash?
 
-
   RubyPants-Unicode is a Ruby port of the smart-quotes library SmartyPants that outputs
-
   unicode characters (UTF-8) instead of HTML entities.
 
-
   The original "SmartyPants" is a free web publishing plug-in for
-
   Movable Type, Blosxom, and BBEdit that easily translates plain ASCII
-
   punctuation characters into "smart" typographic punctuation HTML
-
   entities.
-
-'
 email: chris.chapman@aggiemail.usu.edu
 executables: []
 extensions: []
 extra_rdoc_files:
 - README.md
 files:
-- lib/rubypants-unicode/rubypants-unicode.rb
-- lib/rubypants-unicode/version.rb
-- lib/rubypants-unicode.rb
 - README.md
 - Rakefile
+- lib/rubypants-unicode.rb
+- lib/rubypants-unicode/rubypants-unicode.rb
+- lib/rubypants-unicode/version.rb
 - test/test_rubypants.rb
 homepage: https://github.com/cdchapman/rubypants-unicode
-licenses: []
+licenses:
+- MIT
+metadata: {}
 post_install_message: 
 rdoc_options:
-- --main
+- "--main"
 - README.md
-- --line-numbers
-- --inline-source
-- --all
-- --exclude
+- "--line-numbers"
+- "--inline-source"
+- "--all"
+- "--exclude"
 - test
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.17
+rubygems_version: 2.2.2
 signing_key: 
-specification_version: 3
+specification_version: 4
 summary: RubyPants-Unicode is a Ruby port of the smart-quotes library SmartyPants.
 test_files:
 - test/test_rubypants.rb