Re: [Gaim-i18n] Bad language in Gaim

[<vi...@ci...>]

On Apr 25, 2006, at 5:37 AM, Clytie Siddall wrote:
> I think there is a sensible compromise. If a string is normal  
> language, which you would expect the average user to understand,  
> then you can also expect us to understand it. If it is not normal  
> language, if it's more technical, more idiomatic or more obtuse,  
> then you need to supply context.
>

(Most) Developers are not linguists.  To many of them, idioms do  
constitute 'normal language'.


> If there is an issue with a string and a particular language, then  
> certainly that translator will try to deal with it. If there are  
> cultural difficulties, we will advise you of them. That is part of  
> our job. However, that part of our job is not actually useful  
> unless you pay attention to our advice. ;)

I agree with you here.  If an expression seems overly colorful  
(idiomatic) to you, or insulting, bring it up, which is what Bjoern  
did.  That is the purpose for which this mailing list exists.



>>
>> Getting back to this case... If "lazy bum" is a strong insult in your
>> language, then don't translate it literally. If there's no  
>> appropriate
>> translation, you could translate that portion of the string to the  
>> empty
>> string.
>
> Again, you're expecting us to know what you mean. How do we know  
> that you're not insulting this person seriously? The fact that  
> you're insulting him at all is confusing to us.

Nobody is expecting to know what it means, but I think we are  
expecting people to not assume the worst about an expression.   
Attacking someone's strings because, if translated, it would be  
terribly insulting in your language means you should discuss (not  
attack) what it means in a suitable forum, such as this mailing list,  
and then it should either be left blank in your language or a  
suitable replacement be found.


>>
>> If you take the approach of "I'll translate everything (often  
>> literally)
>> without understanding it", you're going to end up with a bad  
>> translation
>> that results in user complaints. It's entirely reasonable for us (and
>> users) to expect that translators fully understand what they're
>> translating.
>
> Yes indeed. That's why you supply context with obtuse strings, so  
> we have enough information to understand fully what we're translating.


After this line of discussion on these particular strings, I'm sure  
some comments as to their meanings might be added.  I'd even supply  
them.



--V