# (no subject)

**URL:** <https://www.ruby-forum.com/t/no-subject/113914>\
**Category:** Radiant CMS\
**Created:** [September 6, 2007, 4:51am UTC](https://www.ruby-forum.com/t/no-subject/113914 "2007-09-06T04:51:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mark.a.brand](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/34f0e0/32.png) [@mark.a.brand](https://www.ruby-forum.com/u/mark.a.brand)\
**Post date:** [September 6, 2007, 4:51am UTC](https://www.ruby-forum.com/t/no-subject/113914/1 "2007-09-06T04:51:46Z")

</div>

hi:

Wondering if radiant is suitable out of the box for a multi-language  
site.

cheers  
mark

---

<div class="post-metadata">

**Author:** ![mark.a.brand](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/34f0e0/32.png) [@mark.a.brand](https://www.ruby-forum.com/u/mark.a.brand)\
**Post date:** [September 6, 2007, 9:25am UTC](https://www.ruby-forum.com/t/no-subject/113914/2 "2007-09-06T09:25:07Z")

</div>

Not really. There is a “language redirect” extension, but to use it you  
must duplicate all the pages for the different languages. It could be  
useful to you though.

```
I think that for Radiant a good solution would be to define the 

```

content  
in different languages in different parts of a page. For example,  
“body\_en”, “body\_es”. Or have a single “body” part and multiple  
“content\_en”, “content\_es” parts. Then somehow the correct parts are  
selected based on user agent “accept” headers or user selection. Nice  
work  
of an extension developer.

```
There is ongoing work on i18n in a "jargon" branch, but i don't know

```

exactly what new functionality has been implemented.

```
/AITOR
```

---

<div class="post-metadata">

**Author:** ![mark.a.brand](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/34f0e0/32.png) [@mark.a.brand](https://www.ruby-forum.com/u/mark.a.brand)\
**Post date:** [September 6, 2007, 11:37am UTC](https://www.ruby-forum.com/t/no-subject/113914/3 "2007-09-06T11:37:25Z")

</div>

thanks for the input. i will have to check out this jargon branch.