Wiki Forum Sign up! Explore Home

Not signed in (Sign In)

LiveSearch

Welcome, Guest

Want to take part in these discussions? Sign in if you have an account, or apply for one below

Vanilla 1.1.2 is a product of Lussumo. More Information: Documentation, Community Support.

General: Problem with french accent

Bottom of Page

1 to 4 of 4

  1.  
    • CommentAuthorlebill
    • CommentTimeJan 28th 2010
     permalink
    We just install ClockingIt on our server, everything works great in english, except when we enter a french accent somewhere.

    Ex. No problem to create a project "Allo", but if I try a project name "été" I got this error "We're sorry, but something went wrong."

    And it's a lot worst when we change the interface language to french, nothing works, I got the same error everywhere.

    Is there someone who got a direction where I have to look to fix the problem.

    Thanks
    • CommentAuthorari
    • CommentTimeJan 29th 2010
     permalink
    When you get the error, there will also be a stack trace in the log/production.log file. That is what is needed.
    • CommentAuthorlebill
    • CommentTimeFeb 1st 2010
     permalink
    Thanks Ari for the quick response,

    In the log file I have this error

    incompatible character encodings: UTF-8 and ASCII-8BIT
    On line #19 of app/views/projects/_form.html.erb

    16: <span style="padding-top:0.3em;padding-right:0.5em;float:left;"> <%= _'and copy permissions from'%></span><div style="float:left;">
    17: <select name="copy_project" id="copy_project">
    18: <option value="0" class="select_default"><%= _("[None]") %></option>
    19: <%= options_for_select current_user.all_projects.collect{|p| ["#{p.name} [#{p.customer.name}]",p.id]}, params[:copy_project].to_i %>
    20: </select>
    21: </div>
    22: <% end %>


    It give us the error we already know, the code try to deal with a french accent (in this case a "é" in a Project name)

    I'm pretty sure, it's a config problem somewhere, but we look again everywhere we think of. Everything look ok to us.

    Thanks again for your great work and support
    • CommentAuthorari
    • CommentTimeFeb 2nd 2010
     permalink
    Make sure:

    1. You upgrade to Ruby 1.9 instead of 1.8. UTF handling is better.
    2. You are running the absolute most recent version from git. Some code in the area you have problems in has been improved.
    3. All the text fields in your database are UTF. In particular look at project and customer fields.

1 to 4 of 4

  1.