Hi Alecs,

actually I am pretty happy with the current way symfony handles i18n,
so why changing a winning team?


Thanks for your feedback though and have a nice day,
Christian



On Oct 28, 8:38 pm, Alexandru-Emil Lupu <gang.al...@gmail.com> wrote:
> Hello!
>
> Why don't you move your i18n to your database? this allows you / your team to 
> easily add / remove / change the texts without any "deploy" / 
> "cache-clearing" or other kind of task ...
>
> Alecs
>
> On Oct 28, 2010, at 1:46 PM, cestcri wrote:
>
> > Actually this was even easier then expected, I just moved the i18n to
> > a new plugin directory, included it in the
> > ProjectConfiguration.class.php and that's it.
>
> > Thank you symfony!
>
> > Have a nice day,
> > Christian
>
> > On Oct 28, 12:13 pm, cestcri <cest...@yahoo.fr> wrote:
> >> Thanks for your immediate reply, Damien!
>
> >> I actually looked already into the nice and neat sfView extension, but
> >> a whole new application is the better way in my case.
>
> >> I will try my luck with a private i18n plugin... and will report back
> >> if this turns out to be a good choice.
>
> >> Thanks again,
> >> Christian
>
> >> On Oct 28, 12:09 pm, Damien Alexandre <dalexan...@clever-age.com>
> >> wrote:
>
> >>> The main goal is to avoid code duplication,
> >>> for your mobile version, if the changes are only different templates, you
> >>> can extend sfView to return a myView::MOBILE_SUCCESS and create your
> >>> indexMobileSuccess.php views right to your indexSuccess.php.
>
> >>> If you have change to make in your actions, then a new app is a good way 
> >>> to
> >>> do,
> >>> but again, avoid code duplication.
>
> >>> For the shared datas like i18n, auth modules, etc a private plugin IS
> >>> actualy the right way to go.
>
> >>> Cheers.
> >>> Damien.
>
> >>> On Thu, Oct 28, 2010 at 12:01 PM, cestcri <cest...@yahoo.fr> wrote:
> >>>> Hi all,
>
> >>>> I am currently building a mobile version for my symfony site. I chose
> >>>> to create a new app next to the frontend, since the mobile version
> >>>> will be very different, basically with fewer features.
>
> >>>> I wonder now if:
>
> >>>> a) this is a good choice
> >>>> b) how to access shared data like my i18n files
>
> >>>> Thanks in advance for your opinions. This is a critical point and I
> >>>> would like to hear if there is a sort of "best practice" regarding
> >>>> mobile (or whatever other sub-) application. Is the "private plugin"
> >>>> the way to go (http://www.symfony-project.org/jobeet/1_4/Propel/en/
> >>>> 20)?
>
> >>>> Have a nice day,
> >>>> Christian
>
> >>>> --
> >>>> If you want to report a vulnerability issue on symfony, please send it to
> >>>> security at symfony-project.com
>
> >>>> You received this message because you are subscribed to the Google
> >>>> Groups "symfony users" group.
> >>>> To post to this group, send email to symfony-users@googlegroups.com
> >>>> To unsubscribe from this group, send email to
> >>>> symfony-users+unsubscr...@googlegroups.com<symfony-users%2bunsubscr...@googlegroups.com>
> >>>> For more options, visit this group at
> >>>>http://groups.google.com/group/symfony-users?hl=en
>
> > --
> > If you want to report a vulnerability issue on symfony, please send it to 
> > security at symfony-project.com
>
> > You received this message because you are subscribed to the Google
> > Groups "symfony users" group.
> > To post to this group, send email to symfony-users@googlegroups.com
> > To unsubscribe from this group, send email to
> > symfony-users+unsubscr...@googlegroups.com
> > For more options, visit this group at
> >http://groups.google.com/group/symfony-users?hl=en

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en

Reply via email to