Re: [nvda-translations] About translating application into another language
- From: Mesar Hameed <mesar.hameed@xxxxxxxxx>
- To: nvda-translations@xxxxxxxxxxxxx
- Date: Fri, 13 Jul 2012 12:47:39 +0100
I think Bernd and some other translators started a simular discussion here:
http://www.nvda-project.org/ticket/189
With a little discussion, we should be able to come to some consensus on this.
Thanks,
Mesar
On Tue 10/07/12,04:21, Joseph Lee wrote:
> Hi,
> I think what's required would be some kind of a glossary of frequently used
> terms in NVDA and Windows so translators would have easier approach when
> translating. The method I've personally used was to translate using machine
> or software, then fine tune the translation using a product that is known to
> have been produced in the language you are translating into. Also, having a
> thorough knowledge of how a software works and reading the user guides would
> work too.
> Cheers,
> Joseph
>
> -----Original Message-----
> From: nvda-translations-bounce@xxxxxxxxxxxxx
> [mailto:nvda-translations-bounce@xxxxxxxxxxxxx] On Behalf Of G.Braille
> Sent: Tuesday, July 10, 2012 4:07 AM
> To: nvda-translations@xxxxxxxxxxxxx
> Subject: [nvda-translations] About translating application into another
> language
>
> Dear all,
> Greeting!
> I would like to give my opinion with regards to the application Poedit which
> is translating into another language that I have appreciated!
> Translation is the transference of meaning from text to text written or
> recorded, with the translator having time and access to resources
> dictionaries, glossaries, to produce an accurate document or verbal artifact.
> Translators should have time to consider and revise each word and sentence
> before delivering the final outcome to the users.
> Indeed, the goal of translating is to create accessible and easy
> understanding environment for the end user.
> However, if the original language and the end users don't say the name of the
> original product or in this case, (Interface), in the same sound, it will
> create a problem to understand each other.
> For Example, in the nvda.po, the word Button in Ethiopic and Arabic has been
> translated as: (Azrar አዝራር)። Ok, let us take the following terms of
> interfaces, Button, RadioBox, Scroll-bar and the Windows ETC.
> Those terms can be given the actual or the closest meaning in the language of
> the end users. But, if the original term has different sound from the
> translated term, we are going to confuse the user by teaching new language
> and concept.
> Again, if we are teaching how to use window operating system to non English
> speakers, do we tell them this is "Azrar/Button?"
> I know anyone would like his/her language to be integrated or translated into
> any technological products.
> However, the main thing is the concepts not necessarily the terminology.
> Don't you think that we are creating problem on our self by taking time to
> explain for the non English speaker the meaning of the terms and concepts
> while they could understand if the right sound has assigned in their own
> characters?
> I don't mean here that there is no Microsoft Windows in other languages.
> My suggestion is:
> How about if we keep the original terms, Button and put it in the sound of
> the non English speaker's in the method of their writing and sound?
> For example, Button in Ethiopic is sound like: "ባተን b-a-t-e-n"
> I know there are many users in this list from different ethnic background and
> mother tang who are trying translate the language either for Braille or
> Speech.
> Finally, I'm not a linguist or related with the field. I just thought to put
> for a discussion on this aspect.
> I would ask an apology if my subject went too far.
> Cordially,
> Dr. Tamru Belay.
> point your browser to:
> http://www3.sympatico.ca/tamru
>
>
>
Other related posts:
