From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Please help translating gfs2-utils
Date: Mon, 19 Nov 2012 17:56:36 +0000 [thread overview]
Message-ID: <50AA72D4.5080305@redhat.com> (raw)
Hi all,
gfs2-utils is an open source project containing tools necessary for
creating, checking, tuning and manipulating gfs2 file systems. The
gfs2-utils package is required wherever gfs2 file systems are used,
particularly in Linux clusters.
I'm currently trying to improve the strings in upstream gfs2-utils for
localisation. In the meantime, I'd like to drum up interest in
progressing the translation effort. We have a Transifex project set up
and open for translations:
https://www.transifex.com/projects/p/gfs2-utils/
i18n support is a fairly recent addition to the project so the strings
likely require some work to make life easy for translators. If there are
any issues please contact me or file a bug report at
http://bugzilla.redhat.com/ under the gfs2-utils package in Fedora /
Rawhide, and I'll try to get the strings updated as soon as I can.
Whether bug reports or translations, any help you can provide in
translating gfs2-utils into different languages, and making it easier to
do so, would be greatly appreciated.
Regards,
Andy Price
reply other threads:[~2012-11-19 17:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50AA72D4.5080305@redhat.com \
--to=anprice@redhat.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;
as well as URLs for NNTP newsgroup(s).