That's still pretty Rails-bound... I'd like something that I can run
without needing to set up a Rails app at all (i.e. with the haml
executable).

On Tue, Mar 24, 2009 at 11:24 AM, Erik Dahlstrand
<[email protected]> wrote:
>
> I'm no longer sure it is a HAML problem...
>
> A simple template
>
> %h1
>  = h @news_item.title
>
>
> As long as title contains only ASCII characters there is no problem.
> When title equals e.g. "this is a string containing å ä ö" it fails.
>
> incompatible character encodings: ASCII-8BIT and UTF-8
>
> Maybe it is the sqlite3-ruby driver?
>
>
>
> On 24 Mar, 18:57, Nathan Weizenbaum <[email protected]> wrote:
>> Can you give us an example template that displays this problem?
>> Preferably with no Rails stuff that needs to be set up.
>>
>> On Tue, Mar 24, 2009 at 6:00 AM, Erik Dahlstrand
>>
>> <[email protected]> wrote:
>>
>> > Hi,
>>
>> > I'm trying to migrate an application to Ruby 1.9/Rails 2.3.2
>>
>> > In some views I get the following error:
>>
>> > incompatible character encodings: ASCII-8BIT and UTF-8
>>
>> > /opt/local/lib/ruby1.9/gems/1.9.1/gems/haml-2.0.9/lib/haml/buffer.rb:
>> > 137:in `push_script'
>> > /Users/erdah/Sites/test/app/views/catalogs/show.html.haml:16:in `block
>> > (2 levels) in _run_haml_app47views47catalogs47show46html46haml'
>> > /Users/erdah/Sites/test/app/views/catalogs/show.html.haml:6:in `block
>> > in _run_haml_app47views47catalogs47show46html46haml'
>> > /Users/erdah/Sites/test/app/views/catalogs/show.html.haml:5:in
>> > `_run_haml_app47views47catalogs47show46html46haml'
>>
>> > The views and actions are really simple and are just fetching and
>> > displaying some db records.
>>
>> > Any ideas?
>>
>> > /Erik
>>
>>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/haml?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to