LL 9.5 and UTF-8 properties files

Hello all!I've been having some problems with using Greek in my properties files. First of all, the format that the current filed are in is not UTF-8, it's ANSI, so Greek characters are not even saved properly.This is solved by using Notepad and saving as UTF-8. However livelink does not seem to understand the Greek characters and displays akward strings.However, I have no problem creating nodes with Greek names, so I'm thinking that maybe the encoding by notepad for Greek is not what livelink expects?Could you please recomend an editor that will work for livelink or any other solution to this? Thanks in advance!p.s.I have also tried UltraEdit32, same results and I've installed the UTF-8 version of the Windows installation

Find more posts tagged with

Comments

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Java property files don't support UTF-8 characters.

At the sun site there is a spec about how to encode UTF-8 characters in propery files.

Hans

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: donderdag 14 april 2005 9:32
To: eLink Recipient
Subject: LL 9.5 and UTF-8 properties files

LL 9.5 and UTF-8 properties files Posted by ap_stavzeti (Zeti, Stavroula) on 04/14/2005 03:31 AM

Hello all!

I've been having some problems with using Greek in my properties files. First of all, the format that the current filed are in is not UTF-8, it's ANSI, so Greek characters are not even saved properly.

This is solved by using Notepad and saving as UTF-8. However livelink does not seem to understand the Greek characters and displays akward strings.

However, I have no problem creating nodes with Greek names, so I'm thinking that maybe the encoding by notepad for Greek is not what livelink expects?

Could you please recomend an editor that will work for livelink or any other solution to this? Thanks in advance!

p.s.
I have also tried UltraEdit32, same results and I've installed the UTF-8 version of the Windows installation

ATHANASSIOS_FAMELIARIS

Hi HansThanks for the reply, but I meant the property used by oscript modules. Do they have the same problems as Java property files?

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

If you talking about the property files in Livelink 9.5 to store your UI strings (what used to be XDB files) then the answer is yes. This are java property files and not something Open Text specific.

Hans

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: vrijdag 15 april 2005 10:56
To: eLink Recipient
Subject: Java?

Java? Posted by ap_stavzeti (Zeti, Stavroula) on 04/15/2005 04:56 AM
In reply to: RE LL 9.5 and UTF-8 properties files Posted by hstoop (Stoop, Hans) on 04/14/2005 04:57 PM

Hi Hans

Thanks for the reply, but I meant the property used by oscript modules. Do they have the same problems as Java property files?

ATHANASSIOS_FAMELIARIS

I know you are going to say that I should talk to opentext support about this. I have, but they just keep ignoring me. Anyway, since property files don't support UTF-8 how is one supposed to translate livelink? At least with the old XDBs I could use Greek!Any idead, anyone? Any links to a guide making property files UTF-8 compatible? I couldn't find one on sun's site.Thanks again!

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

You need to use to native2ascii tool to convert a UTF-8 file to what java expects. More info at http://java.sun.com/j2se/1.3/docs/tooldocs/win32/native2ascii.html

Hans

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: maandag 18 april 2005 9:15
To: eLink Recipient
Subject: Internationalization?

Internationalization? Posted by ap_stavzeti (Zeti, Stavroula) on 04/18/2005 03:12 AM
In reply to: RE Java? Posted by hstoop (Stoop, Hans) on 04/18/2005 02:48 AM

I know you are going to say that I should talk to opentext support about this. I have, but they just keep ignoring me.

Anyway, since property files don't support UTF-8 how is one supposed to translate livelink? At least with the old XDBs I could use Greek!

Any idead, anyone? Any links to a guide making property files UTF-8 compatible? I couldn't find one on sun's site.

Thanks again!

Raymond_Tsui

They are Java style properties files. The files are ISO 8859-1 encoded. Characters that cannot be encoded using this encoding must be Unicode escaped. When localization for Greek, you can edit and save the files in ISO 8859-7 or Code Page 1253. Once you are happy with the translation, you can use the native2ascii tool to convert the files into ISO 8859-1 encoding, properly Unicode escaped. The native2ascii is included in the J2EE distribution from Sun.Please forward me your correspondence with our Support department. I will follow up so that questions of this nature are redirected properly in the future.Hope this helps.Best regards,Raymond TsuiManager, Multi-lingual SupportOpen Text Corporation

ATHANASSIOS_FAMELIARIS

Thanks! This is the email we sent to support. I haven;t tryied using native2ascii yet. But should I do it with the reverse option enabled?-----------------------------To: 'me-support@opentext.com'Subject: GREEK TRANSLATION Hi AllRegarding our new project for Greek Ministry Of Press where we are going to use Livelink 9.5 we face a problem that we cannot write greek characters into the properties files (the new files used to translate livelink user interface) The encoding of the Web Browser is UTF-8 and we can see all greek labels entered by the User Interface (I.e document names etc)When we try to translate some existing string when we change the relative string directly into the properties file the string that is actually displayed is not understandable from the user interface (strange characters)When we try to translate the string directly from within builder (relative xlate file) the actual string written in the property file is empty Regards -----------------------------