User settings to restrict language

[Tobi]

Hello,

First of all: this is a great project!!!! I was looking a long time
and I was about to give up. I like how flexible your solution is. In
our app we have just plain text files and it is so easy to import
them.

What I wanted to ask is if it is possible to restrict the users. We
got a user for each language and it would be great that if they log
in, they only see their language and maybe the default language.
Good would also be some sort of filter that enables to show all
keywords where there is no translation.

If such a feature does not exist and you think it could be
interesting, I would offer to put it in place and send you the
sources. We would be happy to help.

Cheers,
Tobi

[Ben Sion]

Hi Tobi,

Thanks for the feedback. Its nice to know that this project is of use.

Currently, there is no way to restrict users by language. The issue with this is language is not the only differentiator. Country and Bundle are also ways to differentiate between translations. It is on my todo list but it is not a simple task so I have postponed it for a future major release as role based security and permissions was easier to implement.

Unfortunately, I wont be able to work on such a big refactor for a while as my day job takes up a lot of time at the moment, so let me know if you are interested to work on it and we can flesh out the details.

I will get back to you on the keyword filter.

Cheers,
Ben

--
You received this message because you are subscribed to the Google Groups "Tongue Tied Users" group.
To post to this group, send an email to tongueti...@googlegroups.com.
To unsubscribe from this group, send email to tonguetied-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tonguetied-users?hl=en-GB.

[Tobi]

Hello Ben,

I get your point. I also looked at the code, indeed it would need some
extra engineering.
I believe your application is very well done. A lot of options for
administrating the bundles and so on.
What is missing is acutally a view for the translator. If you imagine
that you have e.g. 20 languages to manage and one guy for each
language, they would be overwhelmed by the keywords view. There is to
much information that is not useful for their workflow. Especially
since its normally not computer addicts :-)
What I would imagine is another user type. Let us say TRANSLATOR who
can or can not have language and countries associated.
When a TRANSLATOR logs in (s)he sees a 3 column list:
keyword | default translation | input box for the translation
Rows where no translation exists should be marked in red.

For the beginning it would be fine if in the top you just have a drop
down to choose the tranlation, bundle and country that you want to do.
So the user object does not need to be modified.

This would be very efficient and less confusing.

What do you think about that? If you want I can send you a screen
mockup.

Cheers,

Tobias

On Jan 21, 3:40 am, Ben Sion <bjs...@gmail.com> wrote:
> Hi Tobi,
>
> Thanks for the feedback. Its nice to know that this project is of use.
>
> Currently, there is no way to restrict users by language. The issue with
> this is language is not the only differentiator. Country and Bundle are also
> ways to differentiate between translations. It is on my todo list but it is
> not a simple task so I have postponed it for a future major release as role
> based security and permissions was easier to implement.
>
> Unfortunately, I wont be able to work on such a big refactor for a while as
> my day job takes up a lot of time at the moment, so let me know if you are
> interested to work on it and we can flesh out the details.
>
> I will get back to you on the keyword filter.
>
> Cheers,
> Ben
>

> On Wed, Jan 20, 2010 at 8:56 PM, Tobi <tobias.ro...@sunnymail.mobi> wrote:
> > Hello,
>
> > First of all: this is a great project!!!! I was looking a long time
> > and I was about to give up.  I like how flexible your solution is. In
> > our app we have just plain text files and it is so easy to import
> > them.
>
> > What I wanted to ask is if it is possible to restrict the users. We
> > got a user for each language and it would be great that if they log
> > in, they only see their language and maybe the default language.
> > Good would also be some sort of filter that enables to show all
> > keywords where there is no translation.
>
> > If such a feature does not exist and you think it could be
> > interesting, I would offer to put it in place and send you the
> > sources. We would be happy to help.
>
> > Cheers,
> > Tobi
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Tongue Tied Users" group.
> > To post to this group, send an email to tongueti...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > tonguetied-use...@googlegroups.com<tonguetied-users%2Bunsu...@googlegroups.com>

[Ben Sion]

Hi Tobias,

I think what you say about translators is very true. I have been looking at it from a developers perspective and have not considered their workflow well. Regradless of the permissions issue (which I will get to eventually :), having some sort of view filter on the keyword page for the translators to ease their use and improve the workflow would be a good idea. I am however hesitant to restrict the view only by language. For example the translations for Chinese in China and Chinese in Hong Kong or Taiwan could be different and would need the country differentiator.

I think the best solution would be to extend the Translations Filter feature on the main keyword listing page, so that the filter also applies to the keyword page.

As for your earlier question about a filter to show all keywords where there is no translation. At the moment there is no such feature. I was hoping that I could massage the current search feature to do this task, but as it stands TongueTied does not support this feature and I will have to add it.

All of these are great ideas which I will raise enhancement issues for, however it will take a while to complete these tasks. My apologies for this, but I am just short of time at the moment.

cheers,
Ben

To unsubscribe from this group, send email to tonguetied-use...@googlegroups.com.