I guess I mist this when posted, but this is really cool. Thanks !
On 9/13/07, Loren Johnson [EMAIL PROTECTED] wrote:
I'm a little late to the discussion, but here is the solution I
recently implemented for a client based on similar needs:
Peter,
I'm glad this looks like something you can use. Let me know how it
goes. The extension was developed for a client whose translated site
has not yet been put into production so this extension is somewhat
untested. It works and hopefully your purposes won't reveal any dark/
sharp
No problem, thanks for the headsup anyway
if I run into something I will try to fix it and mail you the patch.
Peter.
On 10/10/07, Loren Johnson [EMAIL PROTECTED] wrote:
Peter,
I'm glad this looks like something you can use. Let me know how it
goes. The extension was developed for a
I'm a little late to the discussion, but here is the solution I
recently implemented for a client based on similar needs:
http://svn.fn-group.com/radiant_extensions/language_switch
I think it may be useful as-is but at least should be worth
referencing. There is some hackery involved with
For this idea we also need parts for layouts and snippets, since they
must be translated too.
/AITOR
On 9/10/07, Sylvestre Mergulhão [EMAIL PROTECTED] wrote:
On 9/10/07, Aitor Garay-Romero [EMAIL PROTECTED] wrote:
- define different page parts for the language versions. For
Hi Everyone,
In my site [currently being tried out at http://tec.onghu.com ] that is
powered by Radiant, I have a number of articles and news pieces. For
some of them, translations in other languages exist. In those cases,
when I display the article, I would like to show a link to the same
Interesting problem. No, the language-redirect behavior/extension
reads the preferred language sent by your browser and sends the user
to a whole different subsite based on that language. Multiple
language support in Radiant is still very nascent; we'd love to hear
some ideas or see some unique
Hi Sean,
This is what I have in mind for it right now. I didn't want to propose
anything in the first email so that I wouldn't bias people :)
Given the Rails philosophy, this 'workaround' assumes a few things -
let's call it convention over configuration :D
1. I was thinking that it should
i need a good multi-language facility also and would be happy to help
implement if this idea is the way fwd.
On 11/09/2007, Mohit Sindhwani [EMAIL PROTECTED] wrote:
Hi Sean,
This is what I have in mind for it right now. I didn't want to propose
anything in the first email so that I wouldn't
The scheme described by Mohit below addresses the selection of the
language, but we still need to store the translations.
Given the simple tree structure of Radiant pages, i don't think that
duplicating the pages in different languages is a good idea. A solution
could be:
-
Mark, Aitor,
Thanks for your mails. Actually, my needs are simpler - that's where
the idea started out. In my case,
Aitor - I agree that it seems a bit of a waste to duplicate the tags,
but I'm not sure if there will be different tags for different
languages. Also, there may be multiple
On 9/10/07, Aitor Garay-Romero [EMAIL PROTECTED] wrote:
- define different page parts for the language versions. For example,
have the parts body_en, body_fr and body_es. Or just body, fr,
es. They could be special parts or not.
I agree with this, some weeks ago I spent some time
12 matches
Mail list logo
