From: Christopher Bertels <mailinglist@flasht.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] i18n?
Date: Wed, 21 Oct 2009 20:37:34 +0200 [thread overview]
Message-ID: <1256149858-sup-8291@thinkpad-ubuntu> (raw)
In-Reply-To: <1256127705-sup-5539@doma>
[-- Attachment #1.1: Type: text/plain, Size: 1179 bytes --]
Excerpts from Fabio Riga's message of Mi Okt 21 14:29:59 +0200 2009:
> Well, I'm really interested, but I'm just a user. I could only make
> Italian translation, but how? Is it a normal gettext .po file? What I
> have to do?
Get my sup clone git repository at gitorious:
$ git clone git://gitorious.org/~bakkdoor/sup/bakkdoors-clone.git
Then, checkout the i18n branch.
$ cd bakkdoors-clone
$ git checkout i18n
Then have a look at the m17n folder. You should find a de.yaml and
en.yaml file. They are for german and english translations. You can
create your own translation files in there. For example, fr.yaml for
french or it.yaml for italian. Have a look at en.yaml to see, what
the original texts are (in english) and come up with your own
translation. That's basically it. Then, if you have sup set up to run
from that branch, you can set within your sup config file
(~/.sup/config.yaml) to use any language, e.g.:
:language: de
for german. Sup will then look into the m17n folder for a file called "de.yaml"
I hope that helped.
Cheers,
Christopher.
--
================================
Christopher Bertels
http://www.adztec-independent.de
GPG Key ID: 0x2345b203
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-21 18:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 23:30 Christopher Bertels
2009-10-01 16:44 ` William Morgan
2009-10-01 18:15 ` Christopher Bertels
2009-10-01 18:24 ` William Morgan
2009-10-02 0:19 ` Christopher Bertels
2009-10-02 12:52 ` Christopher Bertels
2009-10-05 16:00 ` Christopher Bertels
2009-10-06 15:38 ` William Morgan
2009-10-06 20:35 ` Christopher Bertels
2009-10-06 21:56 ` Christopher Bertels
2009-10-20 12:33 ` Christopher Bertels
2009-10-21 12:29 ` Fabio Riga
2009-10-21 16:41 ` Guillaume Quintard
2009-10-21 18:37 ` Christopher Bertels [this message]
2009-10-23 7:00 ` Tero Tilus
2009-10-23 11:23 ` Fabio Riga
2009-11-02 12:12 ` William Morgan
2009-11-02 13:58 ` Tero Tilus
2009-11-02 14:59 ` William Morgan
2009-11-03 0:01 ` Fabio Riga
2009-11-03 1:22 ` Tero Tilus
2009-11-02 12:13 ` William Morgan
2009-11-03 14:05 ` Christopher Bertels
2009-11-03 15:08 ` Tero Tilus
2009-11-03 15:13 ` William Morgan
2009-11-03 15:23 ` Christopher Bertels
2009-10-01 18:21 ` Christopher Bertels
2009-10-01 18:33 ` Christopher Bertels
2009-10-01 18:47 ` Rich Lane
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=1256149858-sup-8291@thinkpad-ubuntu \
--to=mailinglist@flasht.de \
--cc=sup-talk@rubyforge.org \
/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