p--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.
--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To view this discussion on the web visit https://groups.google.com/d/msg/in-portal-bugs/-/VSNuuhVBBEAJ.
To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.
We don't allow translating interfaces with DBG off at all - I believe we should keep it this way.Not true. We have content modes functionality (which allows phrase translations) in all interface presets with and without debug mode enabled.By the way, Translations section is closed from End website User/Admin too - unless it's an advanced one.Exactly - "unless it's an advanced one". That's what Phil is talking about - users, who manually set non-simple interface preset with no limits still don't see these HintTranslation/ColumnTranslation fields while using Browse Mode.This is happening, because we manually remove these fields in template no matter what is told by interface preset chosen by user.If in turn we set these HintTranslation/ColumnTranslation fields on phrase editing form (from browse mode) to be debug-only in simple interface preset and not directly in TPL then this all would work the same way and HintTranslation/ColumnTranslation fields won't be visible in "Labels & Phrases" section edit page and on "Regional" section edit page.
On Tue, Mar 27, 2012 at 11:23 PM, Dmitry A. <dand...@gmail.com> wrote:
The main problem is that it will confuse some people on our end.We don't allow translating interfaces with DBG off at all - I believe we should keep it this way. By the way, Translations section is closed from End website User/Admin too - unless it's an advanced one.DA--To view this discussion on the web visit https://groups.google.com/d/msg/in-portal-bugs/-/VSNuuhVBBEAJ.
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To post to this group, send email to in-portal-bugs@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bugs+unsubscribe@googlegroups.com.
Then, I propose to display them even in content mode, for advanced interface only.
What do you think guys?
Envoyé avec Sparrow (http://www.sparrowmailapp.com/?sig)
Le mardi 27 mars 2012 à 23:44, Dmitry A. a écrit :
> I was actually thinking about ability to translate Admin Interface Phrases and Hints.
>
> Alex we can do it the way you proposing I guess.
>
> DA
>
> On Tuesday, March 27, 2012 3:58:01 PM UTC-5, Alexander Obuhovich wrote:
> > We don't allow translating interfaces with DBG off at all - I believe we should keep it this way.
> >
> > Not true. We have content modes functionality (which allows phrase translations) in all interface presets with and without debug mode enabled.
> >
> >
> > By the way, Translations section is closed from End website User/Admin too - unless it's an advanced one.
> >
> > Exactly - "unless it's an advanced one". That's what Phil is talking about - users, who manually set non-simple interface preset with no limits still don't see these HintTranslation/ColumnTranslation fields while using Browse Mode.
> > This is happening, because we manually remove these fields in template no matter what is told by interface preset chosen by user.
> >
> > If in turn we set these HintTranslation/ColumnTranslation fields on phrase editing form (from browse mode) to be debug-only in simple interface preset and not directly in TPL then this all would work the same way and HintTranslation/ColumnTranslation fields won't be visible in "Labels & Phrases" section edit page and on "Regional" section edit page.
> >
> >
> >
> > On Tue, Mar 27, 2012 at 11:23 PM, Dmitry A. <dand...@gmail.com (mailto:dand...@gmail.com)> wrote:
> > > The main problem is that it will confuse some people on our end.
> > >
> > > We don't allow translating interfaces with DBG off at all - I believe we should keep it this way. By the way, Translations section is closed from End website User/Admin too - unless it's an advanced one.
> > >
> > > DA
> > > --
> > > You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
> > > To view this discussion on the web visit https://groups.google.com/d/msg/in-portal-bugs/-/VSNuuhVBBEAJ.
> > >
> > > To post to this group, send email to in-port...@googlegroups.com (mailto:in-port...@googlegroups.com).
> > > To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com (mailto:in-portal-bugs%2Bunsu...@googlegroups.com).
> > > For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.
> >
> >
> >
> >
> > --
> > Best Regards,
> >
> > http://www.in-portal.com
> > http://www.alex-time.com
>
> --
> You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/in-portal-bugs/-/kQGtw6dqFKMJ.
> To post to this group, send email to in-port...@googlegroups.com (mailto:in-port...@googlegroups.com).
> To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com (mailto:in-portal-bug...@googlegroups.com).
I am ready said what I think in my prev. post - it's okay with me.
DA
--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To view this discussion on the web visit https://groups.google.com/d/msg/in-portal-bugs/-/jkLOkX-64cUJ.
To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.