[sip-comm-dev] Improving translatability?


#1

Hello,

I'd like to start a discussion on how we could improve translatability of SIP Communicator. The way we currently handle translations is far from perfect.

Right now I see various problems:
- hard to know the translation status, most of them are heavily out of sync
- no identified maintainer for some of the translation files
- outdated wiki page, containing misleading information

Furthermore, .properties files won't let you easily notice strings that have been changed and need to be updated in the translation file.

It would be good to revise the translation procedure for the upcoming release. I think the project will suffer from a bad image if we ship the release with poor translations as it is the case now. We must at least inform the user about the translation status.

Should we consider making use of an online translation tool, such as pootle [1], to help us improve translations? Look at how the Creative Common project is using it [2]. I'm not an expert in i18n, but I think this kind of tool would help us a lot.

I'd like to know you opinion.

Cheers,
Martin

[1] http://translate.sourceforge.net/wiki/ (check out the screencast)
[2] http://wiki.creativecommons.org/Translating_with_Pootle

···

---------------------------------------------------------------------
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 Martin,

Martin André wrote:

Hello,

I'd like to start a discussion on how we could improve translatability
of SIP Communicator. The way we currently handle translations is far
from perfect.

Couldn't agree more. I've been quite frustrated with the state of our
translations for a while, which is why I haven't even committed some of
those I've received off and on the list (apologies Javi).

Tanks for bringing up the issue!

Right now I see various problems:
- hard to know the translation status, most of them are heavily out of sync
- no identified maintainer for some of the translation files
- outdated wiki page, containing misleading information

Furthermore, .properties files won't let you easily notice strings that
have been changed and need to be updated in the translation file.

It would be good to revise the translation procedure for the upcoming
release. I think the project will suffer from a bad image if we ship the
release with poor translations as it is the case now. We must at least
inform the user about the translation status.

Should we consider making use of an online translation tool, such as
pootle [1], to help us improve translations? Look at how the Creative
Common project is using it [2]. I'm not an expert in i18n, but I think
this kind of tool would help us a lot.

Hey that looks really nice! It also seems like it could work directly
with SVN and hence always deal with the latest versions. Do you think
you could install it so that we could give it a try?

Cheers
Emil

···

I'd like to know you opinion.

Cheers,
Martin

[1] http://translate.sourceforge.net/wiki/ (check out the screencast)
[2] http://wiki.creativecommons.org/Translating_with_Pootle

---------------------------------------------------------------------
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

Hi,

Otherwise, we can try something like this

https://open-language-tools.dev.java.net/

It might be a great ally to compare the properties files

···

2009/2/20 Emil Ivov <emcho@sip-communicator.org>:

Hey Martin,

Martin André wrote:

Hello,

I'd like to start a discussion on how we could improve translatability
of SIP Communicator. The way we currently handle translations is far
from perfect.

Couldn't agree more. I've been quite frustrated with the state of our
translations for a while, which is why I haven't even committed some of
those I've received off and on the list (apologies Javi).

Tanks for bringing up the issue!

Right now I see various problems:
- hard to know the translation status, most of them are heavily out of sync
- no identified maintainer for some of the translation files
- outdated wiki page, containing misleading information

Furthermore, .properties files won't let you easily notice strings that
have been changed and need to be updated in the translation file.

It would be good to revise the translation procedure for the upcoming
release. I think the project will suffer from a bad image if we ship the
release with poor translations as it is the case now. We must at least
inform the user about the translation status.

Should we consider making use of an online translation tool, such as
pootle [1], to help us improve translations? Look at how the Creative
Common project is using it [2]. I'm not an expert in i18n, but I think
this kind of tool would help us a lot.

Hey that looks really nice! It also seems like it could work directly
with SVN and hence always deal with the latest versions. Do you think
you could install it so that we could give it a try?

Cheers
Emil

I'd like to know you opinion.

Cheers,
Martin

[1] http://translate.sourceforge.net/wiki/ (check out the screencast)
[2] http://wiki.creativecommons.org/Translating_with_Pootle

---------------------------------------------------------------------
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

Hi,

Your positive feedbacks make me think I was not the only one being frustrated with SC translations.

I'll be playing a bit with pootle this week to see what can be done, in particular about the integration with svn. This may be tricky since pootle does not natively read java .properties translation files and they should be converted to .po in order to be usable.
I'll get back to you soon to report what I have found.

Cheers,
Martin

Emil Ivov wrote:

···

Hey Martin,

Martin Andr� wrote:

Hello,

I'd like to start a discussion on how we could improve translatability of SIP Communicator. The way we currently handle translations is far from perfect.

Couldn't agree more. I've been quite frustrated with the state of our
translations for a while, which is why I haven't even committed some of
those I've received off and on the list (apologies Javi).

Tanks for bringing up the issue!

Right now I see various problems:
- hard to know the translation status, most of them are heavily out of sync
- no identified maintainer for some of the translation files
- outdated wiki page, containing misleading information

Furthermore, .properties files won't let you easily notice strings that have been changed and need to be updated in the translation file.

It would be good to revise the translation procedure for the upcoming release. I think the project will suffer from a bad image if we ship the release with poor translations as it is the case now. We must at least inform the user about the translation status.

Should we consider making use of an online translation tool, such as pootle [1], to help us improve translations? Look at how the Creative Common project is using it [2]. I'm not an expert in i18n, but I think this kind of tool would help us a lot.

Hey that looks really nice! It also seems like it could work directly
with SVN and hence always deal with the latest versions. Do you think
you could install it so that we could give it a try?

Cheers
Emil

I'd like to know you opinion.

Cheers,
Martin

[1] http://translate.sourceforge.net/wiki/ (check out the screencast)
[2] http://wiki.creativecommons.org/Translating_with_Pootle

---------------------------------------------------------------------
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