Home → Problems →

Author name encoding

• Edit

José P. Airosa

10 May, 2012 04:37 PM

Hello,

I just submitted a gem to rubygems and my name, on the gem page, shows with the wrong encoding: https://rubygems.org/gems/ohm-expire

I checked the gemspec and it's in UTF-8 and with the proper character.
Anyway to get this fixed?

Thank you

1. 1 Posted by Luis Lavena on 10 May, 2012 04:48 PM

   

   Please provide details from which platform/ruby/environment you created such gem and pushed.

   The entire output of gem env will help.

   • Edit

2. 2 Posted by Luis Lavena on 10 May, 2012 04:50 PM

   

   BTW, looking at your repository:

   https://github.com/joseairosa/ohm-expire/blob/master/ohm-expire.gem...

   Seems your gemspec file is missing an encoding header to tell Ruby which encoding should be using.

   • Edit

3. 3 Posted by José P. Airosa on 10 May, 2012 04:58 PM

   

   Just added the encoding, which didn't seem to help :(

   This is my gem env:

   RubyGems Environment:
   - RUBYGEMS VERSION: 1.8.10 - RUBY VERSION: 1.9.3 (2011-10-30 patchlevel 0) [x86_64-darwin11.2.0] - INSTALLATION DIRECTORY: /Users/joseairosa/.rvm/gems/ruby-1.9.3-p0 - RUBY EXECUTABLE: /Users/joseairosa/.rvm/rubies/ruby-1.9.3-p0/bin/ruby - EXECUTABLE DIRECTORY: /Users/joseairosa/.rvm/gems/ruby-1.9.3-p0/bin - RUBYGEMS PLATFORMS: - ruby - x86_64-darwin-11 - GEM PATHS: - /Users/joseairosa/.rvm/gems/ruby-1.9.3-p0 - /Users/joseairosa/.rvm/gems/ruby-1.9.3-p0@global - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - "gem" => "--no-ri --no-rdoc" - REMOTE SOURCES: - http://rubygems.org/

   • Edit

4. 4 Posted by Luis Lavena on 10 May, 2012 05:04 PM

   

   Please check with gem spec --local pkg/my-gem.gem instead of pushing the gem expecting it to work.

   All the gem information is serialized in YAML, if for some reason your Ruby installation has problems with that, will be great to solve before you push another gem.

   Please test locally ensuring the encoding of your gemspec file are right and test it locally prior pushing a newer gem.

   We heard of issues when reading encodings but not when creating them.

   Please test and if you want to report a RubyGems bug, do it here:

   https://github.com/rubygems/rubygems/issues?labels=category+-+platf...

   • Edit