From: Progga <abulfazl@juniv.edu>
To: Mihai RUSU <dizzy@roedu.net>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: i18n questions
Date: Thu, 1 Apr 2004 21:05:22 +0600 [thread overview]
Message-ID: <20040401210522.D336@Imrashi.net.bd> (raw)
In-Reply-To: <Pine.LNX.4.58L0.0404011331350.11046@ahriman.bucharest.roedu.net>; from dizzy@roedu.net on Thu, Apr 01, 2004 at 01:43:31PM +0300
On Thu, Apr 01, 2004 at 01:43:31PM +0300, Mihai RUSU wrote:
> projects like KBabel to write such dictionary files. Anyone here has a
> pointer to some detalied explanation of the .po and .gpo files (I see in
> "gaim" that .gpo is some "compiled" form) ? Couse I might do some ".po to
> CDB" compiler and go with this solution :)
$ info gettext
Basicallly, the PO file contains the translated messages in text form whereas
the MO files have them in Binary form. In anycase, gettext works in user
application only (AFAIK). So, I don't think it'll be of any help to you in
this client-server context ;-(
Khoda Hafez
Progga
prev parent reply other threads:[~2004-04-01 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 10:43 i18n questions Mihai RUSU
2004-04-01 14:58 ` Glynn Clements
2004-04-01 15:05 ` Progga [this message]
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=20040401210522.D336@Imrashi.net.bd \
--to=abulfazl@juniv.edu \
--cc=dizzy@roedu.net \
--cc=linux-c-programming@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).