unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: wie kann ich Emacs so einstellen, dass ich drucken kann
Date: Sun, 18 Dec 2022 08:00:15 +0100	[thread overview]
Message-ID: <Y566f8JuaZy3iBiv@tuxteam.de> (raw)
In-Reply-To: <87pmchea6o.fsf@web.de>

[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]

On Sun, Dec 18, 2022 at 03:07:43AM +0100, Michael Heerdegen wrote:
> 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 think we aren't aware how full of strange buried metaphors our
languages are... until we try. Some travel well, some less so,
depending on the source and target languages.

"May contain nuts or parts of nuts" as an allergy warning on a
candy package I bought once was translated into Spanish by
disambiguating the nut into the bolt-and-nut side of things.

OTOH, "crane" as a lifting device, which is obviously a metaphor
based on the bird's look with its long beak does travel surprisingly
well whithin Western European languages. Up to the historians to
explain why (my hunch is that craftspeople travelled across Western
Europe at the time this device found widespread use, but I'm not a
historian).

"Literal" translation (the term becomes fuzzier and fuzzier
the closer you get) is bound to get tangled in that mess.

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-12-18  7:00 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 [this message]
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
  -- 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=Y566f8JuaZy3iBiv@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@gnu.org \
    /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).