# Best practice for internationalization

**URL:** <https://www.ruby-forum.com/t/best-practice-for-internationalization/125045>\
**Category:** Radiant CMS\
**Created:** [January 4, 2008, 8:09pm UTC](https://www.ruby-forum.com/t/best-practice-for-internationalization/125045 "2008-01-04T20:09:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisbotor](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/f14d63/32.png) [@chrisbotor](https://www.ruby-forum.com/u/chrisbotor)\
**Post date:** [January 4, 2008, 8:09pm UTC](https://www.ruby-forum.com/t/best-practice-for-internationalization/125045/1 "2008-01-04T20:09:34Z")

</div>

Hi everyone, and happy new year.  
We recently went live with our new web site, all done with Radiant, come  
and  
visit and leave us some feedback when you get a chance:

> **[Radiant Heating Systems | WarmlyYours](https://www.warmlyyours.com/en-US)**
>
> WarmlyYours offers industry leading warranties and 24/7 customer service for our affordable and effective radiant heating systems.

My question for the list is we are now looking at creating our canadian  
sites (bilingual) and we want to integrate this all into one radiant  
site.

What would be the best practice ?

Create subfolder for our US and canadian sites ?

[www.warmlyyours.com/us](http://www.warmlyyours.com/us)  
[www.warmlyyours.com/ca](http://www.warmlyyours.com/ca)

Then should we use language redirect within the canadian to handle en-ca  
vs  
fr-ca locale?

Thank you

–  
Christian B.  
Director of IT  
[Warmlyyours.com](http://Warmlyyours.com), inc.

Phone: (800) 875-5285 ext.800  
Fax: (847) 550-2600  
Email: removed\_email\_address@domain.invalid

WarmlyYours  
Honeywell authorized licensee  
2 Corporate Dr., Suite 100  
Long Grove, Illinois 60047

Visit the WarmlyYours website at: [www.warmlyyours.com](http://www.warmlyyours.com)

24/7 Installation Support • Lifetime Technical Assistance • Free Design  
Service  
This email and any files transmitted with it are confidential and  
intended  
solely for the use of the individual or entity to whom they are  
addressed.  
If you have received this email in error please notify the system  
manager.  
Please note that any views or opinions presented in this email are  
solely  
those of the author and do not necessarily represent those of the  
company.

---

<div class="post-metadata">

**Author:** ![chrisbotor](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/f14d63/32.png) [@chrisbotor](https://www.ruby-forum.com/u/chrisbotor)\
**Post date:** [January 28, 2008, 4:44pm UTC](https://www.ruby-forum.com/t/best-practice-for-internationalization/125045/2 "2008-01-28T16:44:55Z")

</div>

Christian B. wrote:

> Create subfolder for our US and canadian sites ?
> 
> [www.warmlyyours.com/us](http://www.warmlyyours.com/us)  
> [www.warmlyyours.com/ca](http://www.warmlyyours.com/ca)
> 
> Then should we use language redirect within the canadian to handle en-ca vs  
> fr-ca locale?
> 
> Thank you

Hi Christian

What exactly do you want to achieve?

1. Are the English and French ‘sites’ completely independent in terms of  
the content they have?
2. Will there be the same content on French and English pages? Will  
each English page have a French equivalent?
3. Do you want it to accommodate cases where some pages are present in  
English but not in French and vice versa?

I had started a couple of threads about this and these may help:

1. Initial Discussion -  
[http://lists.radiantcms.org/pipermail/radiant/2007-September/006364.html](http://lists.radiantcms.org/pipermail/radiant/2007-September/006364.html)
2. The solution I implemented -  
[http://lists.radiantcms.org/pipermail/radiant/2007-October/006881.html](http://lists.radiantcms.org/pipermail/radiant/2007-October/006881.html)
3. Another discussion -  
[http://lists.radiantcms.org/pipermail/radiant/2007-November/007243.html](http://lists.radiantcms.org/pipermail/radiant/2007-November/007243.html)

Hope this helps. Feel free to ring back if something appeals to you.

Cheers,  
Mohit.  
1/28/2008 | 11:44 PM.
