Re: Update for pt_BR files
Edson - Lists <[email protected]>
| Newsgroups | gmane.comp.otrs.internationalization |
|---|---|
| Message-ID | <[email protected]> |
I really need developers help...
I'm trying to write a script to help me synchronize the translation
files based on key matching, but having hard times...
Looking on the frontend translation files (aka Language files) I found 4
different ways in the translation string attribution. Sure that Perl is
an amazing and flexible language, but why same sort/type of files don't
use the same structure in a same project? Is there any really hard
reason to not share the same structure in all files of a kind?
In the pt_BR set that I collected (14 files), I founded 7 files with:
my $Self = shift;
my $Lang = $Self->{Translation};
return if ref $Lang ne 'HASH';
$Lang->{'You have already voted!'} = 'Você já votou!';
...
4 files with:
my ( $Self, %Param ) = @_;
$Self->{Translation}->{'Create Directory'} = 'Criar Diretório';
...
2 files with:
my $Self = shift;
...
$Self->{Translation} = {
'Yes' => 'Sim',
...
and 1 file with:
my $Self = shift;
my $Translation = $Self->{Translation};
return if ref $Translation ne 'HASH';
$Translation->{'CW'} = 'Semana';
...
Did the OTRS DEVEL-Team adopt any coding guide? If not, I would suggest
convert all different coding styles, present on the translation files to
use just one. I'd sugest the one used on "de.pm", which in my own
opinion seems cleaner... but I'm not OTRS owner, ot even a developer...
That's why I opened this e-mail asking for help.
Who can shine me some light???
Edson.
Em 26/05/2010 04:13, Shawn Beasley escreveu:
> Hmmm,
>
> you got me there!
>
> On May 25, 2010, at 22:54 , Udo Bretz wrote:
>
>> I would rather suggest to use the german file as reference for other
>> translations, as the english files do not contain as all strings
>> (because they are in english already).
>
> I did not think about it (explain it correctly). You are totally correct, and I apologize :">
>
> ///Shawn
> ---------------------------------------------------------------------
> OTRS mailing list: i18n - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/i18n
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/i18n
>
> NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
> http://www.otrs.com/en/support/enterprise-subscription/
>
---------------------------------------------------------------------
OTRS mailing list: i18n - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/i18n
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/i18n
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/