Re: Serbian translation

Hi Милорад,

Looking into the subtag registry, it seems like sr-Cyrl and sr-Latn are
indeed the appropriate file names. Please use the ISO-8859-5 and
ISO-8859-2 character sets for your files, respectively. Remember to also
update the "Package" section of your local files.

Actually, this file is not the ONLY file you need to translate, you'll
find similar translation files in any additional packages (FAQ, ITSM,
etc) you'd install on your system. These are considerably smaller.

Also, please notice the fact that the version you pointed at on the
source code repository is for the current HEAD branch, which is OTRS
3.x. If you are looking into deploying OTRS 2.4.x it might be smarter to
translate the 2.4.x translation file. Please use the 'Tag' dropdown on
the source code site to select the 2_4 branch.

Finally, there is the subject of notifications. Usually translators
don't bother to get them translated, as they will be customized anyway
most of the time. There are 10 agent notifications that come
pre-populated in your database. We currently only have them in English,
German and Dutch (for 3.x). You could also add them in Serbian if you
wish. You'll find the 10 notifications at the very end of this file:

http://source.otrs.org/viewvc.cgi/otrs/scripts/database/otrs-initial_insert.xml?view=log

Once you're done with your translation, please just send your results
here on this mailing list and we'll make sure it is bundled with the
next OTRS release.

--
Michiel

On wo, 2010-09-29 at 14:42 +0200, Милорад Јовановић wrote:
> Hello to everyone
> 
> We just made decision to start using OTRS for our technical support
> and we start preparations for that. We successfully installed system,
> everything works just fine and we start test phase to get acquainted
> with the functions and administration.
> Before we put it in production use some additional work have to be
> done and localization-translation is  the most important part of that.
> 
> I already begin translation using de.pm file from
> http://source.otrs.org/viewvc.cgi/otrs/Kernel/Language/  - as a start
> point (updating with new version would not be a problem). 
> 
> Now we came to my actual problem - encoding and naming files. I
> suppose that encoding won't be a problem - I use Unicode UTF-8 for
> translation (I saw somewhere that OTRS 3.x will use only  UTF-8) and
> can produce it almost any other suitable encoding. 
> Other part of problem is language naming convention. Serbian language
> have one quite rare characteristic - synchronic digraphia, which means
> that we at the same time for the same language use two different
> writing systems - Cyrilic alphabet and Latin alphabet. Difference
> between them are just technical and transliteration from Cyrillic to
> Latin is straightforward and can be easily done, but is necessity to
> have them both. 
> Before I send You translated files It is essential that we agree about
> naming convention. Here is one example table with Language name
> (English and original), usual abbreviated name, code page ...
> 
> Language
> name            
> 
> Serbian                sr-SR
> Serbian Cyrilic        Српски  sr-Cyrl        Cyrillic    ISO-8859-5
> Windows-1251    
> Serbian Latin        Srpski  sr-Latn        Latin-2     ISO-8859-2
> Windows-1250 
>    
> As You don't have Serbian language jet, my sugestion is that we use
> some from example above (e.g. sr-Cyrl.pm for Cyrilic sr-Latn.pm for
> Latinic ) or something else suitable at Your discretion.
> 
> I have another little question. Is this file only with text strings or
> some of them are in some other files which have to be translated too
> and finally, where and how to send translated files.
> ---------------------------------------------------------------------
> 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

---------------------------------------------------------------------
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