linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Ring <stefanrin@gmail.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Strange XFS problem
Date: Tue, 12 Jun 2018 20:53:36 +0200	[thread overview]
Message-ID: <CAAxjCExfy6ysDCOPX7G9HNJvqojbgQHu54QwMrcGROhu1JnMLg@mail.gmail.com> (raw)
In-Reply-To: <a2dbfee3-f5dc-b4c3-24c9-153fe3304d10@sandeen.net>

On Tue, Jun 5, 2018 at 4:19 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
> In all seriousness, if you would like to update the translations that would
> be great.  The Polish translation is the only one that receives regular
> updates today.

I've looked into it, but this seems to me like a gargantuan task
because there is so much internal inconsistency that I wouldn't even
know where to start. "Extent" for example: sometimes this is
translated as "Erweiterung" (nonsense, that's extension). Sometimes
it's left verbatim. This is what I'd be leaning towards as well. Other
times, it got translated as "Ausmaß", which in another context is in
fact a translation for "extent" (as in: the extent of a catastrophy),
but makes no sense here. Also "Bereich" and "Umfang" are used
sometimes, of which only the former makes a slight bit of sense. That
in addition to my general under-appreciation of low-level technical
translation. They are usually much less comprehensible and the
gibberish needs to be translated back anyway in order to any sense of,
apart from the fact that the original text is searchable, in stark
contrast to the translation.

  parent reply	other threads:[~2018-06-12 18:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-03  1:51 Strange XFS problem Thorsten Hufnagel
2018-06-03  2:32 ` Thorsten Hufnagel
2018-06-05  8:29   ` Carlos Maiolino
2018-06-05 13:46     ` Stefan Ring
2018-06-05 14:19       ` Eric Sandeen
2018-06-05 14:46         ` Stefan Ring
2018-06-05 17:34           ` Chris Murphy
2018-06-12 18:53         ` Stefan Ring [this message]
2018-06-12 18:56           ` Eric Sandeen
2018-06-13 22:02             ` Dave Chinner
2018-06-14  2:11               ` Eric Sandeen
2018-06-14 15:47             ` Stefan Ring
  -- strict thread matches above, loose matches on Subject: below --
2018-09-12  8:07 Troels Hansen
2018-09-12 10:59 ` Carlos Maiolino
2018-09-12 11:39   ` Troels Hansen
     [not found]     ` <notmuch-sha1-960c954e5404b5b2f083d150633af0b7848ec14c>
2018-09-12 16:39       ` Carlos Maiolino
2018-09-13  4:19 ` Dave Chinner
2018-09-13  5:21   ` Troels Hansen
2018-09-13  6:18     ` Dave Chinner

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=CAAxjCExfy6ysDCOPX7G9HNJvqojbgQHu54QwMrcGROhu1JnMLg@mail.gmail.com \
    --to=stefanrin@gmail.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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 NNTP newsgroup(s).