From: Jean Louis <bugs@gnu.support>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: wie kann ich Emacs so einstellen, dass ich drucken kann
Date: Sun, 18 Dec 2022 10:24:07 +0300 [thread overview]
Message-ID: <Y57AFx+vT84Wz2zt@protected.localdomain> (raw)
In-Reply-To: <87pmchea6o.fsf@web.de>
* Michael Heerdegen <michael_heerdegen@web.de> [2022-12-18 05:09]:
> Drew Adams <drew.adams@oracle.com> writes:
>
> > And trying to learn a language by translating
> > as you go is hard, and not necessarily helpful.
>
> I don't know if I would do anyone a favor when I would try to translate
> every Emacs specific term (and there are a lot) literally. I would try
> to describe the terms using my own words, but use those own words to
> introduce the original English terms.
>
> That's because I think when you really want to get something out of
> Emacs, if you don't want to use it only like Notepad or Nano or those
> simplistic editors -- with other words, when you want to use the
> commands, the menus, the customize interface and an init file, you have
> to know the original terms anyway.
IMHO, that is because of habits and environment, you are personally
used to English language and that is how it goes in German
language.
From personal experience I know that there is tendency in various
languages to use one's own national language. Some countries have the
habit to translate words into one's own language, for example Croatia,
or Hungary, while some countries have rather the habbit to adopt
English words, for example Serbia.
I can't see practically that one "has to know" English words. We had
computer club were teaching numerous people including those from
village who had no clues about English language. All of the computer
terminology we had it translated to local language, and people could
immediately adapt.
If people are faced with their own language, they will learn it in
that language.
There is nothing simpler but learning words in one's own language.
It cannot be simpler to learn new words in different language.
I was just searching how Italian people call various Emacs terms and I
could find here:
http://www2.ing.unipi.it/~a008149/corsi/so/materiale/Esercitazioni/E2-Emacs.pdf
that they use "Buffer" but for modeline "Barra di stato", instead of
"ENTER" in sense of entering information, document uses "<invio>"
which shows that there is, rather smaller, tendency to translate it to
Italian.
Judging by TUTORIAL in French the word "Buffer" is translated as
"tampon" and I am not so sure if it is correct, French speaker could
tell it.
Slovenian TUTORIAL, speaks of buffer as »delovno področje« -- which
shows tendency to translate it to local language.
Emacs hrani besedilo vsake datoteke v takoimenovanem »delovnem
področju« (angl. buffer). Ko poiščemo datoteko, Emacs ustvari zanjo
novo delovno področje. Vsa obstoječa delovna področja v Emacsu vidimo
z ukazom:
Some languages have that English and foreign language adoption
tendencies while others tend to have it all localized.
In my personal programming in Emacs, I do not like using exclusively
English as I have to serve people in various languages.
Following construct I use instead of plain English strings:
(rcd-db-words-get "I am sharing this information with you" language)
that means that instead of using plain English string "I am sharing
this information with you" I use the function that is to get the
translated from from the database in specified LANGUAGE, whatever it
may be.
People speak various languages, so for people and lists of people, I
can designate the communication language:
Person "Joe Doe"
People type "Individual Person"
Communication Language "Italian"
Now when I am to share Org heading, file, task, music, anything, there
are some pieces of text that are always same like word "Hello" and
many others.
Those pieces of text get semi-automatically translated.
If word is not translated, Emacs will ask me to translate it at the
moment of running the function. Next time it will go smoothly.
That would be my recommended approach for all mainstream Emacs
strings, including Menu strings.
Would the interface be translatable to other languages, Emacs would be
spread more into other countries and tendencies to use English would
be minimized.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-12-18 7:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 16:08 wie kann ich Emacs so einstellen, dass ich drucken kann Drew Adams
2022-12-18 2:07 ` Michael Heerdegen
2022-12-18 7:00 ` tomas
2022-12-18 15:27 ` [External] : " Drew Adams
2022-12-18 16:02 ` tomas
2022-12-19 19:43 ` Emanuel Berg
2022-12-20 21:28 ` Drew Adams
2022-12-18 7:24 ` Jean Louis [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-14 16:38 Gottfried
2022-12-14 17:27 ` Philip Kaludercic
2022-12-14 21:30 ` Michael Heerdegen
2022-12-17 9:00 ` Jean Louis
2022-12-17 9:29 ` Michael Heerdegen
2022-12-17 9:41 ` Jean Louis
2022-12-17 10:34 ` Michael Heerdegen
2022-12-17 10:39 ` Michael Heerdegen
2022-12-18 8:04 ` Eduardo Ochs
2022-12-18 17:18 ` Jean Louis
2022-12-18 12:06 ` Gottfried
2022-12-18 17:20 ` Jean Louis
2022-12-19 13:49 ` Gottfried
2022-12-19 17:19 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y57AFx+vT84Wz2zt@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).