Databases
StackOverflow2013
Postsdbo
POAsset pipeline encoding problems (UTF-8 vs. ASCII-8BIT) with external gem
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAsset pipeline encoding problems (UTF-8 vs. ASCII-8BIT) with external gem
    primarykey
    data
    text
    <p>I'm trying to create a gem that wraps d3.js, Source can be found at <a href="https://github.com/iblue/d3-rails" rel="nofollow noreferrer">https://github.com/iblue/d3-rails</a></p> <p>So when I include this gem in my Gemfile</p> <pre><code>gem "d3-rails", :git =&gt; "git://github.com/iblue/d3-rails.git" </code></pre> <p>And when I include the javascript in my application.js:</p> <pre><code>//=require d3 </code></pre> <p>Then my asset compilation fails and my compiled application.js just contains</p> <pre><code>throw Error("Encoding::CompatibilityError: incompatible character encodings: UTF-8 and ASCII-8BIT") </code></pre> <p>I am using Rails 3.1.3 and ruby-1.9.3-p125. jQuery uses exactly the same gem structure and it works. What am I doing wrong?</p> <p><strong>EDIT</strong>:</p> <p>I also saw this question: <a href="https://stackoverflow.com/questions/9116752/ruby-1-9-throwing-javascript-encoding-error">Ruby 1.9 throwing javascript encoding error</a>. This does not apply here, my file is valid UTF-8:</p> <pre><code>ruby-1.9.3-p125 :001 &gt; d = File.read("./d3.js") =&gt; [...] ruby-1.9.3-p125 :002 &gt; d.encoding =&gt; #&lt;Encoding:UTF-8&gt; ruby-1.9.3-p125 :003 &gt; d.valid_encoding? =&gt; true </code></pre> <p><strong>EDIT 2</strong>:</p> <p>I also tried to insert some voodoo in my <code>config/environment.rb</code>. It does not work:</p> <pre><code># -*- encoding : utf-8 -*- # Load the rails application require File.expand_path('../application', __FILE__) # --------- VOODOO BEGINS HERE ----------------- Encoding.default_external = Encoding::UTF_8 Encoding.default_internal = Encoding::UTF_8 # --------- END VOODO -------------------------- # Initialize the rails application Ratecode::Application.initialize! </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USiblue
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAsset pipeline encoding problems (UTF-8 vs. ASCII-8BIT) with external gem
      1. USiblue
      1. VTBountyStart
    2. VO
      singulars
      1. POAsset pipeline encoding problems (UTF-8 vs. ASCII-8BIT) with external gem
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAsset pipeline encoding problems (UTF-8 vs. ASCII-8BIT) with external gem
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COEver tried to check presence of http://en.wikipedia.org/wiki/Byte_order_mark ? Also try bisection: remove parts of the file to see, whether things would start working.
      singulars
      1. POAsset pipeline encoding problems (UTF-8 vs. ASCII-8BIT) with external gem
      1. USkirilloid
    2. COCan you also check the encoding of the application.js? The error says the two files are incompatible, you should check not only that the d3 file is UTF-8, but also that your application.js is.
      singulars
      1. POAsset pipeline encoding problems (UTF-8 vs. ASCII-8BIT) with external gem
      1. USmixonic
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload