Hi Rich,
A couple of points. If you intend on doing view translation ( <%=t :translate_this %>), I'd recommend using the t helpers everywhere instead of regular strings, even for just one language. Otherwise it will be a pain to go through and change them all.
For model translations (translations of db data), the main issue is the db schema. If you use a regular db schema you will have to migrate the schema later on for it to work with Globalize. There are plugins out there that do this automatically, so it's not that big a deal. Also, most ActiveRecord functionality will work with Globalize but there are still some more esoteric features that don't work the way they should on translated columns. So that's another reason it might be a good idea to go with Globalize from the start. It works fine for just one language.
Best,
Josh
On Tue, Feb 3, 2009 at 12:55 PM, Metin Oezkan
<metin_tt@...> wrote:
You can add Globalize at any time. No problem.
Metin Özkan
----- Ursprüngliche Mail ----
Von: Rich Pav <rich.pav@...>
An: users@...
Gesendet: Dienstag, den 3. Februar 2009, 09:26:34 Uhr
Betreff: Is it safe to develop now, add i18n later
I need to get started on developing a new website soon. Can I safely
start coding now and add Globalize2 later to handle
internationalization of the content that's stored in the database?
Or, is there anything important I should be aware of from the
beginning so that I don't end up painting myself into a corner?
Thanks,
Rich
