forum.opsi.org

Hello,

I would like to use non ASCII (lithuanian) characters in my packages (for messages), but clients see "?" instead of them.. Do you have any problems with german characters as well? I use OPSI PackageBuilder's script editor, could this be the source of this problem?

Thank you for suggestions and good luck!

Hello mirkt,

most of our applications should be able to handle unicode.
Where do you have the problem with the displaying of the messages? (Configed, logfile, popups...?)


King regards

N. Wenselowski

n.wenselowski hat geschrieben:most of our applications should be able to handle unicode.
Where do you have the problem with the displaying of the messages? (Configed, logfile, popups...?)

Thank you for reply!

When I use lithuanian characters in scripts' messages, for example:
Message "šššš"

Clients see "????" during execution..

Hi,

mirkt hat geschrieben:I use OPSI PackageBuilder's script editor, could this be the source of this problem?

Could be, but don't need to be

The Problem is, that opsi-winst don't fully support unicode at the moment. We are working on it. You should check your Scripts, which Encoding is used. The PackageBuilder writes the scripts on a Windows Machine. Windows has default UTF-16 not UTF-8. It could be a problem in this area.

The easiest way to check this, is to use an editor like jedit, that can handle with file-encodings, and try a little bit in converting the file.

Hope that is helpful for you.

regards
e. ueluekmen

When using proper UTF-8 scripts there are no problems with Lithuanian characters in opsi-winst messages..
viewtopic.php?f=22&t=4382&start=60#p24759

Thank you for your replies!

Good luck

Hi,

the next opsi-winst version family 4.11. will have some special encoding functions for a better handling of this problems.
It will appear in testing about February 2014 ....

regards
d.oertel

Hello,

After opsi-client-agent update to latest version 4.0.7.6 (and opsi-winst 4.11.6.1) I encounter problems with Lithuanian symbols in messages:



That message in example is: Išdiegiamas doPDF...

Script's encoding: UTF-8.

Everything was ok with older opsi-client-agent (or is it opsi-winst related?) versions..

Good luck

Hi,

if your script is encoded in uft8, than you shoud notice this in (anywhere) the script: For more details on encoding in opsi-script look here:
http://download.uib.de/opsi_stable/doc/ ... t-encoding
and here:
http://download.uib.de/opsi_stable/doc/ ... codingfunc

If this don't helps, please give a reply.

cheers
d.oertel

Hi,

in addition:
Perhaps you are intersted for a localization.
Have look here:
http://download.uib.de/opsi_stable/doc/ ... calization
and contact locales_at_uib.de

cheers
d.oertel

d.oertel, thank you for the information, setting "encoding" in scripts helps.

So now I have to modify all my packages (all the scripts and includes where messages are used) or is there a way of setting encoding for package or maybe changing default encoding for opsi-winst installation?

As far as I see, it's not enough to set encoding in "main" scripts, I also have to set it in every include and setting it in include does not affect "main" scripts.