Re: Translation of the AppDB

[James Mckenzie]

Yaron Shahrabani  wrote:
> On Wed, Oct 20, 2010 at 6:48 AM, James McKenzie
> wrote:

[snip]
> So you mean you have got to get some input and there's no other way of
> getting input from the users without typing...
> Do you feel like you get enough feedback or that automating parts of the
> reporting system would make it more widely used.
> I'm maintaining lots of translations in the open source world, I never feel
> like I get enough feedback and I truly think that if the input was at the
> user's fingertips it would help a lot, just my way of looking at it...

Correct.  There is quite a wide variation of what can and cannot work that having a bunch of selections would be tedious at best, confusing at worst.
> > There are many 'drop down' menus that it would be nice to input Hebrew and
> > have English populate them.  Would this be a good idea?
>
> The drop down boxes would be great, the simplest way of interaction is what
> needed, no ways of typing Hebrew...

Again, the existing drop downs could be translated into Hebrew and then used to select the English equivilent.  However, the text boxes will have to remain due to wide variations in 'What works' and 'What does not work'.  Too many selections can be confusing and makes the web site appear to be slow (I work with a web application that has 35,000+ selections, it takes about two minutes for the menu to load on a high speed connection and not all Wine users have that luxury.)
> (I was thinking of a small Javascript code that will check for foreign
> scripts and if the script is different than the Latin script, a Red message
> will appear on top of the box and after clicking the button a message will
> pop up saying that this message contains non-universal characters and ask
> the user if he is sure about sending this report).

I would just block it.  Again, English, for now, is the world's universal language.  If someone does not know English, there are sites like Babblefish that cover just about all languages, including (but not limited to) Hebrew, Farsi, Persian, Arabic, Simplified and Traditional Chinese.  Users can avail themselves of them and copy/paste into the boxes.  I can understand quite a bit of 'translated' English.

James McKenzie

Translation of the AppDB

[Yaron Shahrabani]

On Wed, Oct 20, 2010 at 3:57 PM, James Mckenzie
wrote:
> Yaron Shahrabani  wrote:
> > On Wed, Oct 20, 2010 at 6:48 AM, James McKenzie
> > wrote:
>
> [snip]
> > So you mean you have got to get some input and there's no other way of
> > getting input from the users without typing...
> > Do you feel like you get enough feedback or that automating parts of the
> > reporting system would make it more widely used.
> > I'm maintaining lots of translations in the open source world, I never
>
> feel
> > like I get enough feedback and I truly think that if the input was at the
> > user's fingertips it would help a lot, just my way of looking at it...
>
> Correct.  There is quite a wide variation of what can and cannot work that
> having a bunch of selections would be tedious at best, confusing at worst.
> > > There are many 'drop down' menus that it would be nice to input Hebrew
>
> and
> > > have English populate them.  Would this be a good idea?
> >
> > The drop down boxes would be great, the simplest way of interaction is
>
> what
> > needed, no ways of typing Hebrew...
>
> Again, the existing drop downs could be translated into Hebrew and then
> used to select the English equivilent.  However, the text boxes will have to
> remain due to wide variations in 'What works' and 'What does not work'.  Too
> many selections can be confusing and makes the web site appear to be slow (I
> work with a web application that has 35,000+ selections, it takes about two
> minutes for the menu to load on a high speed connection and not all Wine
> users have that luxury.)
> > (I was thinking of a small Javascript code that will check for foreign
> > scripts and if the script is different than the Latin script, a Red
>
> message
> > will appear on top of the box and after clicking the button a message will
> > pop up saying that this message contains non-universal characters and ask
> > the user if he is sure about sending this report).
>
> I would just block it.  Again, English, for now, is the world's universal
> language.  If someone does not know English, there are sites like Babblefish
> that cover just about all languages, including (but not limited to) Hebrew,
> Farsi, Persian, Arabic, Simplified and Traditional Chinese.  Users can avail
> themselves of them and copy/paste into the boxes.  I can understand quite a
> bit of 'translated' English.

So what you are saying is that even if we want to translate the boxes there
are many boxes to translate...
I'm cool with that, its just an idea :).

I want to see what will the Hebrew website bring along, so far I can't
measure any changes in interest but this kind of things takes time so I
won't jump into conclusions...

Kind regards,
> James McKenzie