[Bf-committers] Bulgarian translation - update

[Victor Dachev]

Ivailo Stoimenov написа:
> On Wed, 07 Mar 2007 01:20:03 +0200, Victor Dachev <vdachev at gmail.com> 
> wrote:
>
>> Ivailo Stoimenov написа:
>>> On Tue, 06 Mar 2007 21:02:37 +0200, Victor Dachev 
>>> <vdachev at gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Here is the update for the Bulgarian translation of Blender (to the 
>>>> last string I had :) )
>>>>
>>>> http://blender.cult.bg/upload/blender_updated.tar.gz
>>>>
>>>> http://bgfreaks.org/blender_updated.tar.gz (just a mirror)
>>>>
>>>> Best,
>>>> Victor Dachev
>>>> _______________________________________________
>>>> Bf-committers mailing list
>>>> Bf-committers at projects.blender.org
>>>> http://projects.blender.org/mailman/listinfo/bf-committers
>>>>
>>>>
>>>
>>> Nice job :)
>>>
>>> But is it possible string translation to be done before further 
>>> procesing?
>>> What I mean is than now strings are translated just before drawing. 
>>> But that
>>> is after clipping them to fit in a button for example or replacing 
>>> \s\d..... with
>>> values. For first case we need to translate all possible short forms 
>>> (Make, Mak, Ma, M) and
>>> second case makes the strings with C forward slash controls ( \ ) 
>>> untranslatable...
>>>
>> I think I didn't get it...
>> For translation I use gtranslator. Lame, so chances for syntax 
>> mismatch are minimal - original string at one side, mine translation 
>> at the other. Of course slashes, \s\d, \n, html tags if any and so on 
>> the same places in the translation as well. After tranalating some 
>> part > .mo > test how it works, reads and feels, make some 
>> corrections and then another part.
>> As I'm managing the same way the translations of several programs, I 
>> rarely face problems, regardles the different approaches of the 
>> programmers.
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at projects.blender.org
>> http://projects.blender.org/mailman/listinfo/bf-committers
>>
>>
>> -- 
>> No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.5.446 / Virus Database: 268.18.7/711 - Release Date: 
>> 05.3.2007 09:41
>>
>
> Не става въпрос за превода :)
>
> It is not the translation itself I am refering to but the way than 
> Blender handles
> displayable strings. It first translates them (gettext) then tryes to 
> fit them in
> to the place for the button and if the string is too long it cuts some 
> chars from the end
> and then tryes again. but since this char are cut from the original 
> untranslated string
> the resulting string is not translated. Thus "Make" becomes "Mak" then 
> "Ma" and so on.
> How to translate "Manual" cut to "Man"?
> The \... tags are first replaced with the actual values and then 
> translated.
> It is impossible to translate "Vertices:\s" fos s from 1 to 650000 :)
>
:) Just risks of the task :).
That's why I am testing all the way and sometimes change 5 or 6 times a 
single string till it fits and feels good. As the spaces in Blender are 
fixed and generally bulgarian word are a bit longer then corresponding 
english this was the hardest translation I've ever made. Of course I had 
to shorten sometimes, of course it took time and lots of nerves.

At milestones  I used to send it to friends and the local community to 
be tested, received marks and ideas, considered them and so on. There 
must be room for improvement, but there always is - no human work is 
perfect but nothing done is worst.
By the way, I'm the local translator of The GIMP and Inkscape as well, 
the experience helped a lot and the overal experience as a user too.