discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Jan Stary <hans@stare.cz>
To: discuss@mandoc.bsd.lv
Subject: Re: HTML output: section headers with diacritics not in table of contents
Date: Fri, 25 Mar 2022 21:58:23 +0100	[thread overview]
Message-ID: <Yj4s758exmAm6ti+@www.stare.cz> (raw)
In-Reply-To: <CAHi0vA-GTGOP=8pC1gFOn6=yERZycuT3Mm_iOYrN1DsYY7Rozg@mail.gmail.com>

[OT, but anyway]

On Mar 25 17:07:13, mario.blaettermann@gmail.com wrote:
> > > For example, the "SYNOPSIS" is "ÜBERSICHT" in German,
> >
> > What a terrible mistranslation...
> >
> > You know, German happens to be my native language, and in
> > general English usage, "synopsis" can indeed mean "Zusammenfassung,
> > Kurzfassung, Uebersicht", but in a manual page, "SYNOPSIS" really means
> > "short syntax display", so an exact name for the section would be
> > "Kurzdarstellung der Syntax" oder "Syntax-Kurzdarstellung" or some
> > similar wording; "Uebersicht" with no further qualification is badly
> > misleading.
> >
> Thanks you for your honest opinion. We use this translation already
> for years, and no one ever complained about it.

Exactly: nobody cares about (mis)translated manpages.

> > Such mistranslations obviously not only happen for reserved words
> > like "SYNOPSIS", but also in the main text of manual pages.
> > That's why i hate translated manual pages so much.  Reading German
> > manual pages, i usually find them pretty unitelligible.
> >
> OK, if you hate German man pages anyway, why get upset...?

Without speaking for Ingo, I don't think it's specific to German
in any way. For a random example, see Debian's Czech version of ln(1):

https://salsa.debian.org/manpages-l10n-team/manpages-l10n/-/blob/master/po/cs/man1/ln.1.po

	msgid "ln - make links between files"
	msgstr "ln - vytváří odkazy na soubory"

"odkaz" is not a "link", and nobody ever says "odkaz", ever,
for either hardlink or symlink. These translations invariably
opt for some home-grown quasi-equivalents; I don't understand
why people bother with these at all.

	Jan

PS: To be honest, there is a difference between a Czech version of a manpage,
    and, say, a Hungarian translation. The Hungarian is irrelevant to me;
    the Czech one, being in my mother tongue, is laughable.
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv


  reply	other threads:[~2022-03-25 20:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 17:13 Mario Blättermann
2022-03-24 17:33 ` Michael Stapelberg
2022-03-24 18:00   ` Mario Blättermann
2022-03-25 12:27 ` Ingo Schwarze
2022-03-25 16:07   ` Mario Blättermann
2022-03-25 20:58     ` Jan Stary [this message]
2022-03-26 12:34     ` Ingo Schwarze
2022-03-26 13:35       ` Mario Blättermann
2022-03-25 16:21   ` Anthony J. Bentley
2022-03-25 21:15     ` Jan Stary
2022-03-26 10:33     ` Ingo Schwarze
2022-03-26 17:55       ` Anthony J. Bentley
2022-03-27 11:17         ` Ingo Schwarze
2022-03-27 11:44           ` Ingo Schwarze
2022-03-25 16:57   ` Mario Blättermann
2022-03-25 20:36     ` Jan Stary
2022-03-25 20:59       ` Mario Blättermann
2022-03-25 21:20         ` Jan Stary
2022-03-26  9:25           ` Ingo Schwarze

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yj4s758exmAm6ti+@www.stare.cz \
    --to=hans@stare.cz \
    --cc=discuss@mandoc.bsd.lv \
    --subject='Re: HTML output: section headers with diacritics not in table of contents' \
    /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

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 NNTP newsgroup(s).