properly designate gemspec file encoding #356

wants to merge 1 commit into


None yet

2 participants


I noticed this line in the gemspec which appeared to have been accidentally changed:

# coding: utf-8

This reverts it to:

# encoding: utf-8

While I was at it, I added myself to the gemspec 😎


Actually, that change was intentional. coding is correct. encoding is a Python thing (but it works in Ruby because it contains the substring coding). See This is less relevant than it used to be, since UTF-8 is the new default (en)coding for source files in Ruby 2.0.0.

I'm going to close this pull request but it's my honor to add you as an author in the gemspec, which I've just done here: 987ec69.

@sferik sferik closed this Feb 27, 2013
@sferik sferik deleted the gemspec_encoding branch Feb 27, 2013

I had a feeling it was intentional but couldn't find the requisite source referring to the right way to represent it.

Thanks for adding me ❤️


Actually, I was slightly wrong. It doesn't actually match the substring. Here’s the relevant code in parse.y:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment