# Re: h() doesn't have any parameter for encoding being used?

**URL:** <https://www.ruby-forum.com/t/re-h-doesnt-have-any-parameter-for-encoding-being-used/149689>\
**Category:** Rails\
**Created:** [September 28, 2008, 11:22am UTC](https://www.ruby-forum.com/t/re-h-doesnt-have-any-parameter-for-encoding-being-used/149689 "2008-09-28T11:22:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![fcheung](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/90db22/32.png) [@fcheung](https://www.ruby-forum.com/u/fcheung)\
**Post date:** [September 28, 2008, 11:22am UTC](https://www.ruby-forum.com/t/re-h-doesnt-have-any-parameter-for-encoding-being-used/149689/1 "2008-09-28T11:22:53Z")

</div>

On 28 Sep 2008, at 05:18, Ryan B. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> I don’t think Rails supports UTF8 yet… but I could be wrong.

Actually it should handle utf-8 just fine. Rails 1.2 added a whole  
bunch of stuff to augment ruby’s somewhat lackluster support. What  
does h do to utf-8 strings that it shouldn’t?

Fred