Translate outgoing templates

Hello List,

how should be outgoing templates translated? I just took a row
for Autoreply template, changed it’s column “content” to ru_RU.UTF-8
text, set “language” to “ru” and “translationof” to 2 (is that a
pointer to the id of not translated original?).

Then I send a email for a test ticket and got a reply in english
(well, with the exception of field names which have been defined
at RT dase in Russian). The user language is set to Russian (I
don’t think it’s relevant here).

For outgoing messages I use “sendmailpipe” with defaults.

Here are language settings from RT_SiteConfig.pm:
Set( @LexiconLanguages, qw(ru en) );
Set( @EmailInputEncodings, qw(utf-8 koi8-r win1251 iso-8859-1 us-ascii) );

But they seem to be for the site and incoming messages, not outgoing.

I use RT-3.8.4, postgresql-server-8.3.7 at FreeBSD-9.

Any help is appreciated. Thanks.
WBR, bsam

Hello Boris,

Do you really need both languages? Just translate it in the UI.

The problem with multi-language templates is that it’s hard to guess
user’s language and each email may have multiple recipients with
different languages, but RT generates email from template only once.

All this can be improved, but I saw only one system where it can be
used. Company supports users in many countries, but even then it is
easier for them to make several queues: support_en, support_xx… A
supporter knows usually two languages when they have almost ten langs
to support, so they just hide queues per supporters groups. As well,
in this case they just have global scrips and in each queue they have
templates with matching names and translated content.

Those columns you mention are in the DB for a while, but have never been used.On Thu, Oct 22, 2009 at 10:01 PM, Boris Samorodov bsam@ipt.ru wrote:

Hello List,

how should be outgoing templates translated? I just took a row
for Autoreply template, changed it’s column “content” to ru_RU.UTF-8
text, set “language” to “ru” and “translationof” to 2 (is that a
pointer to the id of not translated original?).

Then I send a email for a test ticket and got a reply in english
(well, with the exception of field names which have been defined
at RT dase in Russian). The user language is set to Russian (I
don’t think it’s relevant here).

For outgoing messages I use “sendmailpipe” with defaults.

Here are language settings from RT_SiteConfig.pm:

Set( @LexiconLanguages, qw(ru en) );
Set( @EmailInputEncodings, qw(utf-8 koi8-r win1251 iso-8859-1 us-ascii) );

But they seem to be for the site and incoming messages, not outgoing.

I use RT-3.8.4, postgresql-server-8.3.7 at FreeBSD-9.

Any help is appreciated. Thanks.

WBR, bsam


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Best regards, Ruslan.

Hello Ruslan,

Ruslan Zakirov ruslan.zakirov@gmail.com writes:

Do you really need both languages?

No, it was just my impression of The Right Thing to Do.

Just translate it in the UI.

Thanks, that worked fine.

The problem with multi-language templates is that it’s hard to guess
user’s language and each email may have multiple recipients with
different languages, but RT generates email from template only once.

All this can be improved, but I saw only one system where it can be
used. Company supports users in many countries, but even then it is
easier for them to make several queues: support_en, support_xx… A
supporter knows usually two languages when they have almost ten langs
to support, so they just hide queues per supporters groups. As well,
in this case they just have global scrips and in each queue they have
templates with matching names and translated content.

Agreed.

Those columns you mention are in the DB for a while, but have never been used.

I see. Thanks for your quick help!

WBR, bsam