Translating ITSM

[IT4Fun]

Hi guys,

I'm a newbie with OTRS, but, until now, I've managed to customize everything I need to deploy OTRS 4.0 in my company. However, in the last few days I've faced a problem that is driving me nuts. So, I translate almost everything that I need in the pt_Custom.pm, but unfortunately I can't change the translations of the ITSM Modules. Of course, if I change directly the .pm files of the module the job is done, but, in this case, the Package Manager shows me the error "Package is not correctly deployed" for all of the ITSM modules that I changed. There is a way to do these translations without change the main .pm files? Maybe there is a way to create a _Custom.pm for the ITSM files.

Thank you in advance,
Cesar

[eandrex]

OTRS 4 no longer uses .pm files to manage the translations..

take a look into <OTRS_HOME>/i18n/*.po

[reneeb]

@eandrex: OTRS still uses the *.pm files. The .po files are the base for the *.pm files

@IT4Fun: You can create as many pt_*.pm files as you need. So you can create a pt_MyCustomITSM.pm file for your translations. Your translation file has to be loaded *after* the orginal file. So the filename of your file has to come after the original filename (alphabetically).

So pt_MyCustomITSM.pm overrides pt_ITSM.pm, but pt_CustomITSM.pm doesn't.

[eandrex]

Ops, my bad then!.. Im sorry .

Every day you get to learn something . Thank you for the clarification, reneeb.

It is being time to start deeping into OTRS 4

[IT4Fun]

@reneeb: It worked like a charm!

Thanks a lot!

[RStraub]

Did you just randomly post twice my last response from this thread?

viewtopic.php?f=64&t=28372

[ainwee]

Of course, if I change directly the .pm files of the module the job is done, but, in this case, the Package Manager shows me the error "Package is not correctly deployed" for all of the ITSM modules that I changed. There is a way to do these translations without change the main .pm files? Maybe there is a way to create a _Custom.pm for the ITSM files. ????

[RStraub]

You sure can. Take a look at the xx_Custom.pm file. That is a template for translation files.

What you need to do is, copy this file with a new name to the same folder and change the first line according to the filename. So if you copy xx_Custom.pm to MyITSMTranslation.pm the first line should read:

Code: Select all

package Kernel::Language::MyITSMTranslation;

But be aware that those files are processed alphabetically.

[jannu]

Hi,

die Übersetzung ist fehlerhaft.
Der Teil Kernel/Output/HTML/ArticleAttachmentDownload.pm ist falsch eingeordnet.

Zudem kann man erwähnen, was ersetzt werden muss.

[andrep]

Dear all,

I'm fighting with the translation of specific topics like Services name, Ticket Type, Dynamic Field Drop down list,....

The only way that I find is to type this in a fr_Custom.pm file

$Self->{Translation}->{'Service Request'} = 'Demande de service';

But unfortunately it doesn't work. Obviously a wrong syntax.

Thank you for your help.

André

[RStraub]

Hello André and welcome to the forum.

You might want to consider opening new threads if you have a somewhat unrelated problem.

Certain Strings are not meant to be translated. This includedes for example the Type-List in Overviews or new tickets. This block shows how the TypeString is generated:

Code: Select all

        $Param{TypeStrg} = $Self->{LayoutObject}->BuildSelection(
            Class => 'Validate_Required' . ( $Param{Errors}->{TypeIDInvalid} || ' ' ),
            Data  => $Param{Types},
            Name  => 'TypeID',
            SelectedID   => $Param{TypeID},
            PossibleNone => 1,
            Sort         => 'AlphanumericValue',
            Translation  => 0,
        );

As you can see, the deactivation of translation is hardcoded in the perl file.

[reneeb]

fr_Custom.pm is loaded *before* the fr_ITSM....pm . Therefor your custom translation is overridden by the standard module.

You should create a fr_ZZZMyITSM.pm

[andrep]

Thank you Renée and Rolf for your answers.

@Renée : to start step by step, I didn't install the ITSM Module; I read in your previous post this behaviour. Thank you !

@Rolf : Ok, thank you for telling me that some field can't be translated.

But do you have some guidelines on which fields can be translated and which syntax should be use in the xx_Custom.pm file ?

I'm a swiss guy, french speaker, but based in Vietnam close to Ho Chi Minh City for promoting OTRS. In Vietnam, some people can work in English but it's not the majority. It's the reason why I'm fighting with this translation.

Thank you.

Regards

André

[wurzel]

Hi,

instead using local (and your personal) translation files, it is much more better to extend the translation files for the community.

https://www.transifex.com/otrs/OTRS/

Florian

[RStraub]

The syntax in the files? There's an example file (xx_Custom.pm) which you can copy and modify.

Just make sure that the package name is the same as the file-name, and that it starts with the shorthand name for the language.

As for wurzel's suggestion:
This is of course the wise path if there are missing translations, but there are alot of other uses for custom translations. You could have very company-branded terms that won't align with the default translation. Another example is the usage of internal technical names for fields and processes, so that you have them neatly grouped. If you then want the frontend to show human readable strings, you'd need your custom translations:
(DynamicField_)100HR::Duration -> Duration