[sip-comm-dev] i18n support


#1

Hi devs,

I have translated the message.properties file from the gui in french and
I'd like to contribute it. There are 2 problems however :

. The file seems to be parsed using iso-8859-1 encoding, because my �
only show up when I save the file using iso-xxxx encoding. When using
UTF-8 I get 2 garbage characters. Maybe it's caused by my jvm or system
locales or something ? This is important because we have a japanese
version coming soon.

. There does not seem to be a mechanism to choose which language to use,
so that I have to overwrite the message.properties file in my tree. Is
it possible to make this configurable ?

I think the multilanguage stuff is very important, because my mother
will refuse to use a non-french computer program :wink: .

Cheers,
jean

···

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


#2

Hi all,

Damian Minkov wrote:

Hi Jean,
Jean Lorchat wrote:

Hi devs,

I have translated the message.properties file from the gui in french and
I'd like to contribute it. There are 2 problems however :

. The file seems to be parsed using iso-8859-1 encoding, because my �
only show up when I save the file using iso-xxxx encoding. When using
UTF-8 I get 2 garbage characters. Maybe it's caused by my jvm or system
locales or something ? This is important because we have a japanese
version coming soon.
  

Which java version are you using ? As in java 1.4 the java.util.Properties.load method is not correct - always opens the file
with iso-8859-1 encoding.
> new InputStreamReader(inStream, "8859_1").

Hmm this is a nasty one. I guess we should then write our own (e.g.) PropertyStreeamReader and make sure it uses UTF-8

Emil

···

damencho

---------------------------------------------------------------------
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 Jean,
Jean Lorchat wrote:

Hi devs,

I have translated the message.properties file from the gui in french and
I'd like to contribute it. There are 2 problems however :

. The file seems to be parsed using iso-8859-1 encoding, because my �
only show up when I save the file using iso-xxxx encoding. When using
UTF-8 I get 2 garbage characters. Maybe it's caused by my jvm or system
locales or something ? This is important because we have a japanese
version coming soon.
  

Which java version are you using ? As in java 1.4 the java.util.Properties.load method is not correct - always opens the file
with iso-8859-1 encoding.
> new InputStreamReader(inStream, "8859_1").

damencho

···

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

I get this :

$ java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)

and that :

$ javac -version
javac 1.6.0

Does java look at some environment variable to try and guess the locales
settings ?

jean

Damian Minkov wrote:

···

Hi Jean,

Jean Lorchat wrote:

Hi devs,

I have translated the message.properties file from the gui in french and
I'd like to contribute it. There are 2 problems however :

. The file seems to be parsed using iso-8859-1 encoding, because my �
only show up when I save the file using iso-xxxx encoding. When using
UTF-8 I get 2 garbage characters. Maybe it's caused by my jvm or system
locales or something ? This is important because we have a japanese
version coming soon.
  

Which java version are you using ? As in java 1.4 the
java.util.Properties.load method is not correct - always opens the file
with iso-8859-1 encoding.

   new InputStreamReader(inStream, "8859_1").

damencho

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

Hey,

Just wanted to let you know that I've created the following issue for the i18n resource problem

https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=330

We'd have to look at it at some point.

Emil

Emil Ivov wrote:

···

Hi all,

Damian Minkov wrote:

Hi Jean,
Jean Lorchat wrote:

Hi devs,

I have translated the message.properties file from the gui in french and
I'd like to contribute it. There are 2 problems however :

. The file seems to be parsed using iso-8859-1 encoding, because my �
only show up when I save the file using iso-xxxx encoding. When using
UTF-8 I get 2 garbage characters. Maybe it's caused by my jvm or system
locales or something ? This is important because we have a japanese
version coming soon.
  

Which java version are you using ? As in java 1.4 the java.util.Properties.load method is not correct - always opens the file
with iso-8859-1 encoding.
> new InputStreamReader(inStream, "8859_1").

Hmm this is a nasty one. I guess we should then write our own (e.g.) PropertyStreeamReader and make sure it uses UTF-8

Emil

damencho

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


#6

Hi Emil,

Could this be the reason why we cannot load the contact list in some cases? (I suspect this comes from the fact I have some japanese characters in my contact list...)

thanks,
romain

Emil Ivov wrote:

···

Hey,

Just wanted to let you know that I've created the following issue for the i18n resource problem

https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=330

We'd have to look at it at some point.

Emil

Emil Ivov wrote:

Hi all,

Damian Minkov wrote:

Hi Jean,
Jean Lorchat wrote:

Hi devs,

I have translated the message.properties file from the gui in french and
I'd like to contribute it. There are 2 problems however :

. The file seems to be parsed using iso-8859-1 encoding, because my �
only show up when I save the file using iso-xxxx encoding. When using
UTF-8 I get 2 garbage characters. Maybe it's caused by my jvm or system
locales or something ? This is important because we have a japanese
version coming soon.
  

Which java version are you using ? As in java 1.4 the java.util.Properties.load method is not correct - always opens the file
with iso-8859-1 encoding.
> new InputStreamReader(inStream, "8859_1").

Hmm this is a nasty one. I guess we should then write our own (e.g.) PropertyStreeamReader and make sure it uses UTF-8

Emil

damencho

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

--
Romain KUNTZ
kuntz@sfc.wide.ad.jp

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


#7

Hi Emil,

Thanks for creating the issue. Actually it is not an issue but a Java
feature :(. Please look here :
http://java.sun.com/javase/technologies/core/basic/intl/faq.jsp#properties-escape

So I guess we can close the issue and give this URL as an explanation,
or provide a better one for people doing translations.

Jean

Emil Ivov wrote:

···

Hey,

Just wanted to let you know that I've created the following issue for
the i18n resource problem

https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=330

We'd have to look at it at some point.

Emil

Emil Ivov wrote:

Hi all,

Damian Minkov wrote:

Hi Jean,

Jean Lorchat wrote:

Hi devs,

I have translated the message.properties file from the gui in french
and
I'd like to contribute it. There are 2 problems however :

. The file seems to be parsed using iso-8859-1 encoding, because my �
only show up when I save the file using iso-xxxx encoding. When using
UTF-8 I get 2 garbage characters. Maybe it's caused by my jvm or system
locales or something ? This is important because we have a japanese
version coming soon.
  

Which java version are you using ? As in java 1.4 the
java.util.Properties.load method is not correct - always opens the file
with iso-8859-1 encoding.
> new InputStreamReader(inStream, "8859_1").

Hmm this is a nasty one. I guess we should then write our own (e.g.)
PropertyStreeamReader and make sure it uses UTF-8

Emil

damencho

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


#8

Even so. We should be able to avoid escaping by implementing our own property reader.

Emil

Jean Lorchat wrote:

···

Hi Emil,

Thanks for creating the issue. Actually it is not an issue but a Java
feature :(. Please look here :
http://java.sun.com/javase/technologies/core/basic/intl/faq.jsp#properties-escape

So I guess we can close the issue and give this URL as an explanation,
or provide a better one for people doing translations.

Jean

Emil Ivov wrote:

Hey,

Just wanted to let you know that I've created the following issue for
the i18n resource problem

https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=330

We'd have to look at it at some point.

Emil

Emil Ivov wrote:

Hi all,

Damian Minkov wrote:

Hi Jean,
Jean Lorchat wrote:

Hi devs,

I have translated the message.properties file from the gui in french
and
I'd like to contribute it. There are 2 problems however :

. The file seems to be parsed using iso-8859-1 encoding, because my �
only show up when I save the file using iso-xxxx encoding. When using
UTF-8 I get 2 garbage characters. Maybe it's caused by my jvm or system
locales or something ? This is important because we have a japanese
version coming soon.
  

Which java version are you using ? As in java 1.4 the
java.util.Properties.load method is not correct - always opens the file
with iso-8859-1 encoding.
> new InputStreamReader(inStream, "8859_1").

Hmm this is a nasty one. I guess we should then write our own (e.g.)
PropertyStreeamReader and make sure it uses UTF-8

Emil

damencho

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


#9

A while ago I thought it was, then I fixed the XML reader but I hear Mac users are still having significant problems when loading their stored contact lists. I'd like to work on this with someone that has this problem. I'd need to see exceptions (and logs in general) that get thrown while reading or storing a contact list so if some of you, guys with macs, wants to help me out with this we could arrange for a debug session one of these days.

Incidentally I don't think we have an issue for this. Romain, would it be too much trouble if I asked you to log one?

Thanks
Emil

Romain KUNTZ wrote:

···

Hi Emil,

Could this be the reason why we cannot load the contact list in some cases? (I suspect this comes from the fact I have some japanese characters in my contact list...)

thanks,
romain

Emil Ivov wrote:

Hey,

Just wanted to let you know that I've created the following issue for the i18n resource problem

https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=330

We'd have to look at it at some point.

Emil

Emil Ivov wrote:

Hi all,

Damian Minkov wrote:

Hi Jean,
Jean Lorchat wrote:

Hi devs,

I have translated the message.properties file from the gui in french and
I'd like to contribute it. There are 2 problems however :

. The file seems to be parsed using iso-8859-1 encoding, because my �
only show up when I save the file using iso-xxxx encoding. When using
UTF-8 I get 2 garbage characters. Maybe it's caused by my jvm or system
locales or something ? This is important because we have a japanese
version coming soon.
  

Which java version are you using ? As in java 1.4 the java.util.Properties.load method is not correct - always opens the file
with iso-8859-1 encoding.
> new InputStreamReader(inStream, "8859_1").

Hmm this is a nasty one. I guess we should then write our own (e.g.) PropertyStreeamReader and make sure it uses UTF-8

Emil

damencho

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


#10

Hi Emil,

Emil Ivov wrote:

A while ago I thought it was, then I fixed the XML reader but I hear Mac users are still having significant problems when loading their stored contact lists. I'd like to work on this with someone that has this problem. I'd need to see exceptions (and logs in general) that get thrown while reading or storing a contact list so if some of you, guys with macs, wants to help me out with this we could arrange for a debug session one of these days.

I can help you on that. I'll prepare some log and exceptions messages in the next days (certainly tomorrow).

Incidentally I don't think we have an issue for this. Romain, would it be too much trouble if I asked you to log one?

Of course not, I'll gather some information and create a new issue for that.

Thanks,
Romain

···

Romain KUNTZ wrote:

Hi Emil,

Could this be the reason why we cannot load the contact list in some cases? (I suspect this comes from the fact I have some japanese characters in my contact list...)

thanks,
romain

Emil Ivov wrote:

Hey,

Just wanted to let you know that I've created the following issue for the i18n resource problem

https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=330

We'd have to look at it at some point.

Emil

Emil Ivov wrote:

Hi all,

Damian Minkov wrote:

Hi Jean,
Jean Lorchat wrote:

Hi devs,

I have translated the message.properties file from the gui in french and
I'd like to contribute it. There are 2 problems however :

. The file seems to be parsed using iso-8859-1 encoding, because my �
only show up when I save the file using iso-xxxx encoding. When using
UTF-8 I get 2 garbage characters. Maybe it's caused by my jvm or system
locales or something ? This is important because we have a japanese
version coming soon.
  

Which java version are you using ? As in java 1.4 the java.util.Properties.load method is not correct - always opens the file
with iso-8859-1 encoding.
> new InputStreamReader(inStream, "8859_1").

Hmm this is a nasty one. I guess we should then write our own (e.g.) PropertyStreeamReader and make sure it uses UTF-8

Emil

damencho

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

--
Romain KUNTZ
kuntz@sfc.wide.ad.jp

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