public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Bogusz <qboosh@pld-linux.org>
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>
Subject: Polish translation update + localization remark for xfsprogs 4.3.0
Date: Sun, 24 Jan 2016 16:58:53 +0100	[thread overview]
Message-ID: <20160124155853.GA10063@stranger.qboosh.pl> (raw)

Hello,

I've just updated Polish translation for xfsprogs 4.3.0, it's available
at:
http://qboosh.pl/pl.po/xfsprogs-4.3.0.pl.po

I have noticed untranslatable message part in repair/versions.c:228:

_("WARNING: you have a V1 inode filesystem. It %s be converted to a\n"
  "\tversion 2 inode filesystem. If you do not want this, run an older\n"
  "\tversion of xfs_repair.\n"), no_modify ? "would" : "will");

There are untranslatable "would"/"will" strings.
This code could look for example like this:

_("WARNING: you have a V1 inode filesystem. %s to a\n"
  "\tversion 2 inode filesystem. If you do not want this, run an older\n"
  "\tversion of xfs_repair.\n"),
  no_modify ? _("It would be converted") : _("It will be converted"));

(note: using _("would") : _("will") is not enough - these words are
untranslatable to many languages without wider context)


-- 
Jakub Bogusz    http://qboosh.pl/

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2016-01-24 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 15:58 Jakub Bogusz [this message]
2016-01-24 17:08 ` [PATCH] xfs_repair: Fix untranslatable strings Eric Sandeen
2016-01-26 16:47   ` Christoph Hellwig
2016-01-26 16:47 ` Polish translation update + localization remark for xfsprogs 4.3.0 Christoph Hellwig

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=20160124155853.GA10063@stranger.qboosh.pl \
    --to=qboosh@pld-linux.org \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.com \
    /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