Robert K. wrote in post #966327:
> Hallo all,
>>Marnen Laibow-Koser wrote in post #965696:
>> Git exists in Windows.
> Yes, but I don't know to work with it
Learn.
> and therefore I cannot imagine,
> how to update the core of rails without not to break it ):
I note that you conveniently neglecte
Hallo all,
>Marnen Laibow-Koser wrote in post #965696:
> Git exists in Windows.
Yes, but I don't know to work with it and therefore I cannot imagine,
how to update the core of rails without not to break it ):
> but why are you torturing yourself with Windows? :)
Well, most of my job I make on MS
Gjermund Lunder wrote in post #965337:
> Robert K. wrote in post #965170:
>>
>> A monkey work-around
>>
>> A better work-around
>>
>
> Thanks! Perfect.
>
> I'm also waiting for a fix in 3.0.4. As you asked: Does anyone know if
> patch and Git exists in wind
Robert K. wrote in post #965170:
>
> A monkey work-around
>
> A better work-around
>
Thanks! Perfect.
I'm also waiting for a fix in 3.0.4. As you asked: Does anyone know if
patch and Git exists in windows? If no; how to apply std nix patch
files?
About
Gjermund Lunder wrote in post #964821:
> Robert K. (or others), If you do have have the exact line for the
> enforce coding and in witch erb files to put it I would be happy.
To replicate this error, call:
rails -v
> Rails 3.0.3
ruby - v
> ruby 1.9.2p0 (2010-08-18) [i386-mingw32]
Mysql version:
Marnen Laibow-Koser wrote in post #965150:
> It's a standard *nix patch file. The patch command could read it (see
> its man page for more details), but the a/ and b/ file naming scheme
> means that you'd probably be better off using git apply.
Is possible use a patch command also under Windows?
Gjermund Lunder wrote in post #965049:
> Anyone know how to add this patch?:
> 0001-enforced-utf-8-encoding-for-ruby-19-and-mysql-text.patch
>
(https://rails.lighthouseapp.com/projects/8994/tickets/4683-ascii-8bit-and-utf-8-in-hell)
>
> I've never applied such a pacth.
It's a standard *nix patch
Anyone know how to add this patch?:
0001-enforced-utf-8-encoding-for-ruby-19-and-mysql-text.patch
(https://rails.lighthouseapp.com/projects/8994/tickets/4683-ascii-8bit-and-utf-8-in-hell)
I've never applied such a pacth.
Thanks
Gjermund
--
Posted via http://www.ruby-forum.com/.
--
You receiv
Please quote when replying.
Gjermund Lunder wrote in post #964821:
> Because unfortunately innoDB tables don’t support full text searching of
> UTF-8 encoded content.
I know that, but I didn't think full-text searching was at issue here.
Perhaps I misread.
The fact that you have to choose is a
Because unfortunately innoDB tables don’t support full text searching of
UTF-8 encoded content. But innoDB tables are more flexible in general.
Source of information:
http://dev.mysql.com/doc/refman/5.1/en/fulltext-restrictions.html and
http://www.dotmana.com/?p=95.
This might not be relevant, b
Gjermund Lunder wrote in post #964675:
> all,
> Thanks for good ideas, but like for Robert K. it's not working for me
> (ruby 1.9.2 and rails 3.0.3).
>
> Robert K., check that your tables are of type = MyISAM and CHARACTER SET
> utf8 in Mysql.
Er, why MyISAM? That's generally a poor idea, since y
all,
Thanks for good ideas, but like for Robert K. it's not working for me
(ruby 1.9.2 and rails 3.0.3).
Robert K., check that your tables are of type = MyISAM and CHARACTER SET
utf8 in Mysql.
I get the same error as you; the problem appears almost every time, but
suddenly it works for again r
Hallo, I face a similar problem, but here mentioned solutions seem to
not work.
When I try to display string with non-ascii chars from a mysql database
in form, sometimes the program stops with the 'incompatible character
encodings: ASCII-8BIT' error. This issue appears only at some fileds in
a ta
Hi,
Just for your information - switching to 'mysql2' gem solved my issue -
I was storing Chinese in my DB..
Plus, mysql2 should be the default mysql adapter of Rails 3 anyways...
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google
It's not a satisfying solution but whenever I ran into this problem I
added
# Encoding: utf-8
to the top of the file causing this problem and it worked.
Would love to know how to get rid of all these comments and fix it for
real though :)
--
Posted via http://www.ruby-forum.com/.
--
You rece
Hi, thanks for responding.
It's very simple, before acces any database, I have a presentation menu,
and a text in the view saying than user have to choose an option:
Seleccione una opción del menú
If I change "ó" with "o" and "ú" with "u" works fine.
--
Posted via http://www.ruby-forum.com
Albert C. wrote in post #955265:
> Hi, I began reading this post because i have the same problem:
>
> Just start the aplicacion with new ruby 1.9.2 raises the error
>
> "incompatible character encodings: ASCII-8BIT and UTF-8".
>
> But I have the problem before reading database, in the main menu
Hi, I began reading this post because i have the same problem:
Just start the aplicacion with new ruby 1.9.2 raises the error
"incompatible character encodings: ASCII-8BIT and UTF-8".
But I have the problem before reading database, in the main menu when
ruby read "opción" and "menú"
Does a
On 22 August 2010 23:08, Sven Koesling wrote:
> Gudleik Rasch wrote:
>> I've been struggling with the same issue a few times, and the solution
>> that worked for me was to use a different mysql driver: ruby-mysql
>>
>> # in config/environment.rb:
>> config.gem 'ruby-mysql'
>>
>> # or in Gemfile:
>
Gudleik Rasch wrote:
> I've been struggling with the same issue a few times, and the solution
> that worked for me was to use a different mysql driver: ruby-mysql
>
> # in config/environment.rb:
> config.gem 'ruby-mysql'
>
> # or in Gemfile:
> gem 'ruby-mysql'
>
> The encoding must also be set i
forgot to say: a workaround that works for me is to add the method
".force_encoding('utf-8')" to any variable with date from my database
eg.:
student.name.force_encoding('utf-8')
Good Night for now :-)
S.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are
Hi,
did You find a solution? I have the same problem on all of my projects.
DB in UTF8, rails in UTF8, but when it comes to partials with data with
german umlauts I get the mentioned error.
As far as I understand it's a problem with the erb rendering engine that
forces ASCII encoding.
This en
Oh what I forgot. The icompati... error is showing on a line where I'm
using I18n.t and it would return a string with a umlaut.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this gr
Manos wrote:
> Are you sure you don't have hard coded strings in the partial or
> strings assigned
> to variables through controller?
I'm only using I18n.t for strings and globalize2 for model translation.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are su
Andre Lewis wrote:
>
> Most likely, you are outputting content stored in your DB as UTF-8 onto
> a template that is ASCII. This fix works for me:
> http://gist.github.com/273741 -- drop this into
> config/initializers/ruby_191_hacks.rb. I posted more about upgrading to
> 1.9.1 here:
> http://
Are you sure you don't have hard coded strings in the partial or
strings assigned
to variables through controller?
Andre Lewis wrote:
> > I just tried to migrate one of my applications from ruby 1.8 to ruby 1.9
> > and get following error:
> > Showing app/views/layouts/application.html.erb where
> I just tried to migrate one of my applications from ruby 1.8 to ruby 1.9
> and get following error:
> Showing app/views/layouts/application.html.erb where line #48 raised:
> incompatible character encodings: ASCII-8BIT and UTF-8
Most likely, you are outputting content stored in your DB as U
FYI: I execute these commands:
db:drop
db:create
db:setup
Still same error.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-t...@googlegroups.com
I tried it, no it doesn't :(
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-t...@googlegroups.com.
To unsubscribe from this group, send email to
That means if I do a "db:migrate:reset" (recreate the db with Ruby 1.9)
that error would disappear?
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrai
If you have have hard coded strings in ruby code you should try
Mystring ="bla bla"
Mystring.force_encoding('ASCII-8BIT')
Before using it.
For database strings you should search for mysql to force encoding
(this is for db created with ruby 1.8)
Good luck
Heinz Strunk wrote:
> Not yet, had to switch
Not yet, had to switch back to Ruby 1.8.6.
Maybe someone else has an idea?
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-t...@googlegroups.com.
I'm ran into the same problems after switching to Ruby 1.9.1. Have you
found a solution yet?
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-t...
Any one knows what's wrong?
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-t...@googlegroups.com.
To unsubscribe from this group, send email to
Gudleik Rasch wrote:
> I've been struggling with the same issue a few times, and the solution
> that worked for me was to use a different mysql driver: ruby-mysql
>
> # in config/environment.rb:
> config.gem 'ruby-mysql'
>
> # or in Gemfile:
> gem 'ruby-mysql'
>
> The encoding must also be set i
On 29 March 2010 15:08, Heinz Strunk wrote:
> No, all I found on google said I have to put it as a comment, <%- gives
> a syntax error.
You seem to have snipped the useful stuff. How about encoding rather
than coding? Though I am not convinced.
Colin
>
> I just run into the same problem in tw
No, all I found on google said I have to put it as a comment, <%- gives
a syntax error.
I just run into the same problem in two other projects. Is there a way
to set the encoding application wide?
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribe
37 matches
Mail list logo
