Hi Ryoko and Josh,
Ryoko -- I totally agree, this looks like a recent change (I've only
noticed it the past couple of days); automatically updating the
translation on pressing enter would actually be a pretty good idea if
it worked properly, but unfortunately in my browser at least (very
recent Firefox) the behaviour is unpredictable. I'm not sure what
event hook is actually being used (hence, why it's behaving like
this), but sometimes the return is processed normally and everything
is fine, although more often the return is lost across the reload, so
the only way to get a new line is to paste one in there... really
frustrating!
Josh -- actually re-asking your question, what browser are you using?
Have you tried with larger blocks of text (many paragraphs, as opposed
to a few lines)??
Cheers,
Alex.
On Feb 23, 9:35 pm, Josh. wrote:
> Hi Ryoko,
>
> I'm not sure I understand the problem.
>
> When I type a sentence, hitenter, it translates it, *and* the cursor
> goes to the next line.
> So if I have multiple lines to type in, it translates after each
> line.
>
> It doesn't seem to prevent me from editing the text however I like, it
> just triggers a translation when I hitenter. I like this feature.
>
> Is this not how it's working for you? What browser are you using?
> Maybe it doesn't work correctly in your browser?
>
> Cheers,
> Josh
>
> On Feb 21, 1:41 pm, Ryoko wrote:
>
> > When ever I pressEnterin the dialog box Google translates the page
> > instead of moving the cursor to the next line. this is an
> > inconvenience especially when translating large amount of text because
> > I have to open a notepad to edit the text and copy and past it in to
> > Google Translate. can this be fixed?
