All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@maven.pl>
To: aelder@sgi.com
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] [xfsprogs]: Don't translate command name.
Date: Wed, 4 May 2011 07:22:20 +0200	[thread overview]
Message-ID: <201105040722.21080.arekm@maven.pl> (raw)
In-Reply-To: <1304458906.9841.2.camel@doink>

On Tuesday 03 of May 2011, Alex Elder wrote:
> On Fri, 2011-04-15 at 11:07 +0200, Arkadiusz Miśkiewicz wrote:
> > Command names should never be translated. Currently there is
> > 'xfs_quota -x -c "project"...' in one locale (C) while
> > 'xfs_quota -x -c "projekt"...' in another (pl_PL).
> 
> I haven't looked at this closely yet, but it looks
> pretty straightforward.
> 
> I have tried to do a little research on localization
> though, so I'm a little better informed.  I accept
> your statement that command names should never be
> translated, but is that a well-known convention?

It isn't written anywhere as a "rule" afaik. I simply "makes sense". We don't 
want documentation to be valid only for C/en_US locale. We want scripts that 
use xfs tools to be portable and not locale dependant etc, etc.

There are cases when translating commands makes sense - MUDs or some text 
based games and surely not admin tools.

> Thanks.
> 
> 					-Alex
> 
> > Signed-off-by: Arkadiusz Miśkiewicz <arekm@maven.pl>


-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

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

  reply	other threads:[~2011-05-04  5:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15  9:07 [PATCH] [xfsprogs]: Don't translate command name Arkadiusz Miśkiewicz
2011-05-03 21:41 ` Alex Elder
2011-05-04  5:22   ` Arkadiusz Miskiewicz [this message]
2011-05-10 21:41 ` Alex Elder

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=201105040722.21080.arekm@maven.pl \
    --to=arekm@maven.pl \
    --cc=aelder@sgi.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.