Re: [Geany-i18n] I18n Digest, Vol 75, Issue 2

[Benno Schulenberg]

On 2016-01-16 20:53, André Glória wrote:
> [...] if the plugin's name is more of its function/action than a name
> per se it still brings more value to [be] translated than not.

I fully agree with this general idea.

Benno
___
I18n mailing list
I18n@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/i18n

Re: [Geany-i18n] I18n Digest, Vol 75, Issue 2

[André Glória]

Hello,

I just want to give you my 2 cents on this discussion.
I agree with you, proper names should never be translated. And those
examples are quite good, Geany, MS Word, LibreOffice, etc.

In this plugin's particular case I would never translated "Bird's Eye" but
I would say that since it is called "Overview" it should. My reasoning is
the following, the former name does not really imply the plugin's
functionality while the latter is more of its function/action than its name.
And if you look at other Geany's plugins I would say that this is their
main idea also, GeanyPy is a name but "Split Window" is a function/action.

Ultimately you have to assume that the translation is made to help people
that have zero knowledge on the original's program language, and therefore
the more you translate the better. While translating a name like "Geany
"does not give you any benefits (imho), translating a  function/action does.
Off course you could argue that at least in Geany's case the plugins are
presented on a list with a succinct description right under their name
which could make translating their "name" irrelevant. I would agree with
such argument but I would still stand by the fact that if the plugin's name
is more of its function/action than a name per se it still brings more
value to translated than not.

Kind regards,
André


2016-01-16 9:00 GMT+00:00 :

> Send I18n mailing list submissions to
> i18n@lists.geany.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.geany.org/cgi-bin/mailman/listinfo/i18n
> or, via email, send a message with subject or body 'help' to
> i18n-requ...@lists.geany.org
>
> You can reach the person managing the list at
> i18n-ow...@lists.geany.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of I18n digest..."
>
> Today's Topics:
>
>1. Re: Incorrect russian translation of overview plugin
>   (Matthew Brush)
>2. Re: Incorrect russian translation of overview plugin
>   (Yan Pashkovskiy)
>3. Re: Incorrect russian translation of overview plugin
>   (Matthew Brush)
>
>
> -- Mensagem reencaminhada --
> From: Matthew Brush 
> To: i18n@lists.geany.org
> Cc:
> Date: Fri, 15 Jan 2016 06:56:44 -0800
> Subject: Re: [Geany-i18n] Incorrect russian translation of overview plugin
> On 2016-01-15 12:48 AM, Yan Pashkovskiy wrote:
>
>> I was talking about View - Show overview. If this string was
>> untranslated - it was hard to understand what is it. Plugin name
>> should be translateable too imho.
>>
>>
> Mostly I was just wondering why it should be translated in some places and
> not in others. Looking at other plugins, it seems to be a mix of plugin
> names being translated or not. I was previously under the impression that
> proper names weren't to be translated, for example how plugin author names
> aren't translated. Is the rule that you only translate names of things but
> not people?
>
> I guess an example would be 'Geany', does it get translated as well?
> Something with meaning of 'magic man who comes out of bottle'? If Geany
> doesn't get translated, would 'Overview' be translated if it's name was
> 'Goverview'? What about 'GeanyPy', would it be translated as 'Snake of the
> editor' or something?
>
> Apologies if these are stupid questions, I just want to understand as I
> only speak English and French. In Canadian English and French I don't think
> proper names of things get translated (although people's names sometimes
> are - my name sometimes becomes Mathieu). But, for example, 'Hitachi'
> company name is not translated to 'Sunrise' in English, and 'Apple'
> computer name is not translated to 'Pomme' in French here.
>
> I don't care either way, I just want to know what rule to consistently
> apply to my plugins' names, if possible.
>
> Cheers,
> Matthew Brush
>
> As for Russian language: I don't know whether name should be
>> capitalized or not (grammar rules say that shouldn't, but it is
>> plugin name!). I just think it shouldn't be more than 20 symbols:
>> "карта документа", "обзор документа" are valid, but "показать обзор
>> документа" not (show document overview). And I also think that
>> "затемнение" is definitely bad l10n  :)
>>
>> Regards, Yan
>>
>>
>> 15 янв. 2016 г., в 11:22, Matthew Brush 
>>> написал(а):
>>>
>>> On 2016-01-14 7:25 PM, Baurzhan Muftakhidinov wrote:
 Hi,

 In Russian writing "Обзор Документа" is incorrect - it should be
 "Обзор документа"

 On Fri, Jan 15, 2016 at 4:21 AM, Yan Pashkovsky 
> wrote:
> Oh, I've forgot to mention original naming, it is "затемнение". How can
> I participate in renaming? I may provide git patch of ru.po (or just
> new
> .po file)
> By the way are there any plans to move to transifex or launchpad
> translations? :) Seems to be handy tools

Re: [Geany-i18n] I18n Digest, Vol 75, Issue 2

[Matthew Brush]

On 2016-01-16 11:53 AM, André Glória wrote:

Hello,

I just want to give you my 2 cents on this discussion.
I agree with you, proper names should never be translated. And those
examples are quite good, Geany, MS Word, LibreOffice, etc.

In this plugin's particular case I would never translated "Bird's Eye" but
I would say that since it is called "Overview" it should. My reasoning is
the following, the former name does not really imply the plugin's
functionality while the latter is more of its function/action than its name.
And if you look at other Geany's plugins I would say that this is their
main idea also, GeanyPy is a name but "Split Window" is a function/action.

Ultimately you have to assume that the translation is made to help people
that have zero knowledge on the original's program language, and therefore
the more you translate the better. While translating a name like "Geany
"does not give you any benefits (imho), translating a  function/action does.
Off course you could argue that at least in Geany's case the plugins are
presented on a list with a succinct description right under their name
which could make translating their "name" irrelevant. I would agree with
such argument but I would still stand by the fact that if the plugin's name
is more of its function/action than a name per se it still brings more
value to translated than not.



Thanks for the explanation, it makes sense.

Cheers,
Matthew Brush

___
I18n mailing list
I18n@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/i18n