Feedback about the "TeamSpeak 3 Package Installer"

[darkdaz]

i have looked at the addons pages, but i cant find the package installer.
can you help me please?

[SmokinShark]

This is a TS-Client integrated Feature.

If you create a Pack you only have to do what you see at the Code from Peter.

[Jordi]

Well, we decided to use the package installer for our translations.
No problem with Firefox and Chrome. But Explorer-9 says it's a file.zip.

[PotaBlava]

Hello.

How to include accents in the description field? is it possible?

Greetings.

[dante696]

Save the package.ini as a UTF8 file
(Yes i have tesed that with russian language.)

[Jordi]

Save the package.ini as a UTF8 file
(Yes i have tesed that with russian language.)

A little problem, in UTF8, don't show the box Name content.


edit
There are any possibility to translate the installer's labels?.

[dante696]

As said i have tested the installer with russian letters.

And not you can't translate the package installer.

[PeterS]

There are any possibility to translate the installer's labels?.

Well, currently that would be only possible if you a) get an empty translation file to start with (I can provide that) and if b) the exe would load the translation dynamically from the <TS3>\translations\ directory (I'd need to do some minor code changes for that). Right now English is the standard language and a German translation is built into the exe. If there is demand for user-added translation, I could make those changes and provide the TS files. Adding user-generated content to the exe is probably no good idea, because that could only be updated with a new TeamSpeak client version, so dynamically loading like the main client sounds much better to me.

[Jordi]

Well, currently that would be only possible if you a) get an empty translation file to start with (I can provide that) and if b) the exe would load the translation dynamically from the <TS3>\translations\ directory (I'd need to do some minor code changes for that). Right now English is the standard language and a German translation is built into the exe. If there is demand for user-added translation, I could make those changes and provide the TS files. Adding user-generated content to the exe is probably no good idea, because that could only be updated with a new TeamSpeak client version, so dynamically loading like the main client sounds much better to me.

The installer's translation isn't really something vital, but helps to improve the Multilingual image.
For our part we are open to collaborate with 2 languages​​, Spanish(_es) and Catalan(_ca).

[Jordi]

A little problem, in UTF8, don't show the box Name content.

As said i have tested the installer with russian letters.

Solved
With Notepad ++ is required to encode: UTF-8 without BOM
With PSPad any problem with UTF-8

[PeterS]

The installer's translation isn't really something vital, but helps to improve the Multilingual image.

I agree and created a ticket for that as new feature. I cannot promise it will be ready for 3.0.3.

As a note, the NSIS installer is also translateable, but in this case the translation must be included at compilation time (NSIS uses an own translation mechanism, not Qt ts files). For all others (updater, package installer, error report) dynamically loading *.ts files from <install_root>/translations/ should be possible.

[PotaBlava]

Hello.

An issue with the add-on website: not all the suffixes related with the Package files are identified. Some (.ts3_addon, .ts3_style) appear with a button that says "Install Now" and others, case of ".ts3_translation", the button shows "Download".

Greetings.

[dante696]

I have sent that problem to one of our guys

[PotaBlava]

Hello.

I work in windows and everything is ok with the package installer. I've asked a colleague that works in Mac to use the translation package and it failed, he couldn't launch the .ts3_translation package. After, I asked a friend that works in Linux and it failed too, he couldn't use the .ts3_translation package.

Is the package only for windows?

Greetings.

[PeterS]

Mac: Seems I forgot the file associations for *.ts3_xxx on Mac. Will fix that.
Linux: Due to various window managers with their own handling of file associations this is difficult. However, Linux users can start the package_installer binary directly and give the *.ts3_xxx file as parameter.