Languagefiles in 1.6

isaBERLIN

Where are the languagefiles located at ?

Can't find any :(

wanted to start translating into german? ;)

isaBERLIN

blank

There is no languagefile-system so far.

i translated most of it, but it is still hardcoded !

You Probably need to wait for RC 4 or 5.

as far as i am informed there will be debugging followed by

templatesystem and then language file support

This is RC1 and not a propper release so far !

blank

Es gibt noch kein Sprachdatei-System !

ich habe zwar das meiste übersetzt für uns, aber es ist alles

noch hardcoded (d.h. in den PHP files drin)

Ihr müsst euch also noch etwas gedulden so bis RC 4 oder 5

Geplant sind zunächst Fehlerbeseitigung, dann ein Templatesystem und

dann erst Sprachdateien-Unterstützung

Dir Download (RC1) ist eine entwicklerversion und keine fertige version !

Mark Harris

If you know PHP maybe you could work on implementing Smarty or a similar template system with Peter?

isaBERLIN

I think peter knows best what to do.

and i agree with him : its more important to get rid of errors

than implementing templates and languagefiles.

Kian

Sure, and I'll have to wait until then to use osTicket in french.

Meanwhile I wonder if eTicket 1.5.x ( http://eticket.sourceforge.net(http://eticket.sourceforge.net) ) can later be upgraded to osTicket 1.6.x, 'cause I'm quite in an emergent need for either one of them, but the better definitely seems to be osTicket.

isaBERLIN

ok. little update :

i'm actually working on smarty and language support right now.

but i'm afraid it could take till end of year / beginning of next year because of x-mas in between.

but the better definitely seems to be osTicket.

*hehehe* eticket is based on osticket ;)

but i don't quite know how much changes they made in SQL so could be complicated to switch

okidoki

isa,

any updates on the language system? also your language system will be incorporated into future osticket release candidates right (and not a addon)?

thanks!

prioserve

ok so language support is coming, nice.

what about the buttons? gdlib? or are they going to stay static?

if so, it would be nice if updates are friendly to people who customize the images of ostick

timdubi

osticket-1.3-multilang.

Hi,

I found here -> http://www.scriptworker.com/osticket.0.html(http://www.scriptworker.com/osticket.0.html) an mutlilang File of Version 1.3. It looks like ostiket. It includes German, Portuguese-BR and English! Mayby this is the LNG-Basic for the Future?

Thomas

4ice

Hi Thomas,

unfortunately this is not something we can use. 1.3 is really outdated. The new version is a complete re-write.

But nevertheless thanks for the response.

I hope to finish the languages as soon as possible.

giorgio

we are planning to use osticket, but therefore need a dutch version. Is there any hint on how the language files will look like? I would like to start translating already, but only if it is relatively easy to integrate my translation in a future release.

4ice

we are planning to use osticket, but therefore need a dutch version. Is there any hint on how the language files will look like? I would like to start translating already, but only if it is relatively easy to integrate my translation in a future release.
tx

Then this is your lucky day... because I will try to translate as much as I can in Dutch while I am implementing this.

So hopefully by the time I will be done, the Dutch version will be available as well....

saaiber

I am translating the osticket for my website into Dutch and I got stuck on the closed status of tickets.

I tried to translate the viewticket (staff and clientside) from closed to "Gesloten" so that everywhere it shows "Gesloten Tickets" instead of "Closed Tickets" but this doesn't work because in the database I see a (enum type) statusfield with (open/closed) so that the correct info can't be drawn from the database.

Someone has any solution to this please?

Grtz,

Nic

feel

portuguese

I'm translating to Brazilian portuguese.

Anyone intersted on a colaborative work, talk to me :)

Visor1999

Roadmap?

Is there a scheduling for the language files? When will this feature be usable?

weblu

feel

Hi,

feel, I'm interested in collaborate with you,

I add your msn.

Tell me in portuguese please!

kkk

zagrad

I tried to translate the viewticket (staff and clientside) from closed to "Gesloten" so that everywhere it shows "Gesloten Tickets" instead of "Closed Tickets" but this doesn't work because in the database I see a (enum type) statusfield with (open/closed) so that the correct info can't be drawn from the database.
Someone has any solution to this please?
Grtz,
Nic

Hi Nic,

In stead of simply printing the database value on screen you should check the database value ("open" or "closed") and from that you get the correct translation from the language-file.

In the English version this will be something like:

$language = 'open';

$language = 'closed';

In the Dutch version this will be something like:

$language = 'open';

$language = 'gesloten';

This is the method I would use. Ofcourse this totally depends on how you are implementing the languages.

I hope this helped you out a bit ('cause I am waiting for the Dutch version as well :) ).

Greetz,

Paul

EDIT: Errrr... this reply was probably a little bit late :)

n2s

in spanish

I need translate at spanish ?

is it possible....

zagrad

Well errr.. do you speak Spanish? ;)

Is translation available to the Spanish?

regards