[sip-comm-dev] Translation implementation


#1

Hi, before coding I think it's a good idea to explain the way I intend to implement the translation service as it easier to modify/correct/add ideas and pseudo-code than actual code.

http://www.sip-communicator.org/index.php/Development/Babelfish

Briefly the idea is to write translation service-independent code only, while using XML files to describe the actual available services and their usage (ex. Google translate or BabelFish).

Thanks for the feedback,

Ernesto

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hey Ernesto,

I've just went through your wiki page and what you suggest definitely
sounds like a good idea. I guess my only suggestion would be to keep the
xml part for last. Try to hard code one particular service for starters
and then, once you have the rest of the plugin working, you can go back
to abstracting the service through an XML file.

My point here is that a plugin that works with one translation service
is more important than the beginnings of a plugin that would work with
any translation service.

Besides, once you get it working for one service you'd know a lot more
clearly what is it you need from the service, and how you would be able
to best abstract it.

Then, concerning your display options, I'd say that personally I'd
prefer the first one but the second one would be easier to implement
with SC so you may want to start with it.

One last question, I didn't see in your documentation anything about
translating outgoing messages. Any plans on this one?

Cheers
Emil

Rivera Ernesto написа:

···

Hi, before coding I think it's a good idea to explain the way I intend
to implement the translation service as it easier to modify/correct/
add ideas and pseudo-code than actual code.

http://www.sip-communicator.org/index.php/Development/Babelfish

Briefly the idea is to write translation service-independent code
only, while using XML files to describe the actual available services
and their usage (ex. Google translate or BabelFish).

Thanks for the feedback,

Ernesto

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

I've just went through your wiki page and what you suggest definitely
sounds like a good idea. I guess my only suggestion would be to keep the
xml part for last. Try to hard code one particular service for starters
and then, once you have the rest of the plugin working, you can go back
to abstracting the service through an XML file.

I agree, it will also reveal some parameters XML files will need that I have not taken into account yet.

Then, concerning your display options, I'd say that personally I'd
prefer the first one but the second one would be easier to implement
with SC so you may want to start with it.

I think that depending on the translation accuracy displaying both original and translated text together may be useful/not needed. The idea anyway would be to let users choose the one they prefere and save those parameters (as well as the language pair used with a given contact) for future sessions.

One last question, I didn't see in your documentation anything about
translating outgoing messages. Any plans on this one?

I think translation should be activated from the receiver side as:

- He's the one who knows if he needs a translation.
- He can decide into which language it should be translated.

So outgoing messages should go untranslated in my opinion. Outgoing messages could however specify the language being used.

Thanks for the feedback ;o)

Ernesto

···

Rivera Ernesto написа:

Hi, before coding I think it's a good idea to explain the way I intend
to implement the translation service as it easier to modify/correct/
add ideas and pseudo-code than actual code.

http://www.sip-communicator.org/index.php/Development/Babelfish

Briefly the idea is to write translation service-independent code
only, while using XML files to describe the actual available services
and their usage (ex. Google translate or BabelFish).

Thanks for the feedback,

Ernesto

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Hey Ernesto,

Rivera Ernesto написа:

Then, concerning your display options, I'd say that personally I'd
prefer the first one but the second one would be easier to implement
with SC so you may want to start with it.

I think that depending on the translation accuracy displaying both
original and translated text together may be useful/not needed. The
idea anyway would be to let users choose the one they prefere and save
those parameters (as well as the language pair used with a given
contact) for future sessions.

What I meant to say is that right now you don't have the possibility to
play with the html pane that shows received messages and it would
therefore be tricky to implement translation display the way you
describe it. I know some of us are currently working on implementing
themes for that pane which should make it easier.

One last question, I didn't see in your documentation anything about
translating outgoing messages. Any plans on this one?

I think translation should be activated from the receiver side as:

- He's the one who knows if he needs a translation.
- He can decide into which language it should be translated.

True but only if they were also using SIP Communicator or another
messenger that had this option.

So outgoing messages should go untranslated in my opinion. Outgoing
messages could however specify the language being used.

I completely agree with the fact that translation for incoming messages
is very important but if someone really needs it then chances are that
they might also need help with the outgoing messages. Therefore it would
probably be a good idea to preview that option as well.

This one would actually be easier to handle than the incoming messages
since we already have the methods that allow you to replace the text in
the typing area of the chat window.

Cheers
Emil

···

Thanks for the feedback ;o)

Ernesto

Rivera Ernesto написа:

Hi, before coding I think it's a good idea to explain the way I
intend
to implement the translation service as it easier to modify/correct/
add ideas and pseudo-code than actual code.

http://www.sip-communicator.org/index.php/Development/Babelfish

Briefly the idea is to write translation service-independent code
only, while using XML files to describe the actual available services
and their usage (ex. Google translate or BabelFish).

Thanks for the feedback,

Ernesto

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-
communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

One last question, I didn't see in your documentation anything about
translating outgoing messages. Any plans on this one?

I think translation should be activated from the receiver side as:

- He's the one who knows if he needs a translation.
- He can decide into which language it should be translated.

True but only if they were also using SIP Communicator or another
messenger that had this option.

That's true, I was only thinking inside SIP, yup, now I don't see a reason why to lock the option of translating outgoing messages.

Thanks for the enlightenment ;o)

Ernesto

···

On 2008/06/16, at 20:06, Emil Ivov wrote:

Hey Ernesto,

Rivera Ernesto написа:

Then, concerning your display options, I'd say that personally I'd
prefer the first one but the second one would be easier to implement
with SC so you may want to start with it.

I think that depending on the translation accuracy displaying both
original and translated text together may be useful/not needed. The
idea anyway would be to let users choose the one they prefere and save
those parameters (as well as the language pair used with a given
contact) for future sessions.

What I meant to say is that right now you don't have the possibility to
play with the html pane that shows received messages and it would
therefore be tricky to implement translation display the way you
describe it. I know some of us are currently working on implementing
themes for that pane which should make it easier.

One last question, I didn't see in your documentation anything about
translating outgoing messages. Any plans on this one?

I think translation should be activated from the receiver side as:

- He's the one who knows if he needs a translation.
- He can decide into which language it should be translated.

True but only if they were also using SIP Communicator or another
messenger that had this option.

So outgoing messages should go untranslated in my opinion. Outgoing
messages could however specify the language being used.

I completely agree with the fact that translation for incoming messages
is very important but if someone really needs it then chances are that
they might also need help with the outgoing messages. Therefore it would
probably be a good idea to preview that option as well.

This one would actually be easier to handle than the incoming messages
since we already have the methods that allow you to replace the text in
the typing area of the chat window.

Cheers
Emil

Thanks for the feedback ;o)

Ernesto

Rivera Ernesto написа:

Hi, before coding I think it's a good idea to explain the way I
intend
to implement the translation service as it easier to modify/correct/
add ideas and pseudo-code than actual code.

http://www.sip-communicator.org/index.php/Development/Babelfish

Briefly the idea is to write translation service-independent code
only, while using XML files to describe the actual available services
and their usage (ex. Google translate or BabelFish).

Thanks for the feedback,

Ernesto

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-
communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net