Project internationalization

alexandrehaguiar

Hi all,

I'm developing the internationalization of this project using gettext and launchpad. I had seen other attempts to translate this project but poorly implemented. Using gettext the internationalization is integrated with launchpad, thereby enabling any one help with translations.

The project is at https://launchpad.net/osticketplus(https://launchpad.net/osticketplus) all are invite to help developing and translating.

alexandrehaguiar

Internacionalization finished

Hi all,

I finished the implementation of the internalization of this project. More than 1000 speachs was reconized to be translated into launchpad. Now it's just fill the translation task into launchpad to get the entire system translated to any language. I already start the translation to brazilian portuguese.

If you want to test this peace of code, i just ask for some feedback to fix any problem with this implementation.

alexandrehaguiar

Now we have friends working with Brazillian Portuguese, Czech, Spanish and Turkish languages.

greno

Alexandre,

This is a great idea. I already have lots of PHP developed using PHP gettext. And now I should be able to use those gettext message stores with osTicket.

I wish every PHP app would do this as the default localisation. Gettext has been around a long time and works very well and I wish all apps, carts and frameworks would use it instead of trying to reinvent the wheel.

-Gerry

greno

I've been working with the gettext version and it is doing very well.

Some of my concerns/observations:

Due to the way in which different languages and translators interpret things it is best to:

1. try to keep all gettext strings to full complete sentences or just plain single words.

2. do not mix ANY markup in with gettext strings to be translated; translators invariably get confused by this and we end up redoing these translations.

3. do not put any param substitution %s type variables in the gettext strings.

4. use full form instead of contractions: (cannot) instead of can't; (they are) instead of they're, etc.

5. avoid highlighting things by using quotes; translations resulting from mid-sentence quoting sometimes causes problems for the gettext tools and other translation tools; rather should use parentheses to highlight (important) things.

A lot of the osticket strings are very unfriendly to being translated currently. I'm trying to clean some of these up. Like most of the markup can just be stripped out or the string broken into multiple gettext strings with markup concatenated separately. Most of it is trivial bolding, underline, etc. And mid-sentence links need moved all the way to the end of the sentence so that the gettext string can be a full, uninterrupted sentence.

If the strings can be cleaned up then this osTicket-gettext version should work very nicely.

-Gerry

ozkr

it would be very helpfull for everyone if you could document every step to add the internationalization in our osticket because every person have diferents ostickets versions with a lots of mods of the forums or made by our self.

so it would be nice if you can do that.

alexandrehaguiar

Hi all,

The project is open to new colaborators, just send me a email and i'll add to the develper team. The rules is just that we are open to fix anything on the internacionalization and any new development must be voted by the deveper team before get commited. To submit a new ideia just open a bug with importance set to wishlist.

Until now this is not a fork, but if we get a strong comunity, maybe in future it can be.

Until now there was started translations to: Brazilian Portuguese, Bulgarian,

Croatian, Czech, German, Greek, Spanish, Turkish.

alexandrehaguiar

greno,

How to solve this question "3. do not put any param substitution %s type variables in the gettext strings."?

Do you can put some example, like how is the best way to internacionalise this "The script is version %s while the database is version %s."

alexandrehaguiar

ozkr,

To internacionalize the project i have to identify all phrases inside the code and hack adding the gettext functions. Today there are 1102 phrases identified. To internacionalize older version will need do all this again.

greno

greno,
Do you can put some example, like how is the best way to internacionalise this "The script is version %s while the database is version %s."

printf( _("The script is version: ")."%s "._("while the database is version: ")."%s.\n", $scriptversion, $dbversion);

The text needs to be organized as much as possible into sentences or pseudo-sentences. This makes the translators job much easier and more accurate and it keeps markup and processing directives out of the translatable strings. There should be nothing in the translatable strings but text.

-Gerry

greno

Hi all,
Until now this is not a fork, but if we get a strong comunity, maybe in future it can be.

I think it would be best after doing this conversion successfully that osticket would adopt it as the osticket core. Of course if osticket doesn't want it then a fork would be in order certainly. But this is a great addition.

I just recently took OpenCart and converted it to using gettext. I'm still working trying to get the OC developers to adopt that conversion. Over there a few third-party guys are resisting because they sell translations for the old arcane OC translation system which is quite ridiculous. Same strings have to be translated 20-30 times in different language files. Gettext made all that unnecessary and so simple that even users can do their own translations. With osticket I do not think there is this third-party problem so much.

The nice part about using gettext is that the gettext strings are just interpreted as regular strings when there is no translation. So it is quite transparent and many mods can easily be adjusted to just convert their strings like "a simple string", to _("a simple string"). Pretty easy, really.

-Gerry

Cooltom

hi guys, i used *your* osticket plus and i have problem with czech letters. If i change page encoding into win-1250 all is good but with next click www browser use utf8 again. All page headers show utf8, php scripts are utf8.Where is the problem. Thnx Tom

Tomark

Italian translation

The Italian translation is almost complete. Still working on it for details, but it's already usable.

Hope it's useful.

Tomark

HTML character entities

hi guys, i used *your* osticket plus and i have problem with czech letters. If i change page encoding into win-1250 all is good but with next click www browser use utf8 again. All page headers show utf8, php scripts are utf8.Where is the problem. Thnx Tom

I think you can solve the problem using HTML character entities to display certain pre-defined non-ASCII characters. For example, é or ü.

elartedeganar

Is this package functional

I have a question about this osticketplus package.

I've downloaded, installed, but everything keeps coming out in English and not in Spanish.

I have to upload only the contents of the upload folder?

What am I doing wrong?

regards

Francisco

elartedeganar

Is this package functional

Nobody????

elartedeganar

Versión en Español

Muy buenas a todos,

He preparado una versión en español que traduce back y frontend...

esta traducción esta echa a pelo así que no tenéis que estar subiendo ningún archivo extra, el mensaje de bienvenida se puede cambiar en el index.php dentro de la carpeta raíz de osTicket.

miren aqui:

http://osticket.com/forums/showthread.php?t=6173&highlight=spanish+version(http://osticket.com/forums/showthread.php?t=6173&highlight=spanish+version)