From: Akim Demaille <demaille@inf.enst.fr>
To: hjl@lucon.org (H.J. Lu)
Cc: law@cygnus.com, egcs@cygnus.com
Subject: Re: texinfo-3.11 merge
Date: Tue, 24 Mar 1998 00:03:00 -0000 [thread overview]
Message-ID: <qylwwdkv7lc.fsf@ubu.enst.fr> (raw)
In-Reply-To: <m0yHKJo-00058JC@ocean.lucon.org>
hjl@lucon.org (H.J. Lu) writes:
> > Just an FYI, I imported texinfo-3.11 into the egcs source tree
> > to replace whatever old version we were still running.
Texinfo 3.11 is buggy (especially install-info which should not affect
your users though), take 3.12.
> I saw many data files like *.po/*.gmo. Does egcs really need them?
These are related to internationalization. po files are readable
(they're just a mapping from English strings to <``foreign'' language>
strings. They are meant to be edited by humans. gmo files are GNU
gettext native ``compiled'' form of the po files for run time, read by
machines.
Regards,
Akim
--
P-mail: Akim Demaille, 107 rue Bobillot, F-75013 Paris, France
E-mail: demaille@inf.enst.fr
V-mail: +33 (1) 45-81-78-68
next prev parent reply other threads:[~1998-03-24 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-23 16:39 Jeffrey A Law
1998-03-23 19:24 ` H.J. Lu
1998-03-23 20:58 ` Jeffrey A Law
1998-03-24 8:18 ` Lee Iverson
1998-03-24 17:35 ` Jeffrey A Law
1998-03-24 0:03 ` Akim Demaille [this message]
1998-03-24 11:16 ` texinfo-3.11 merge (or 3.12 ?) Philippe De Muyter
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=qylwwdkv7lc.fsf@ubu.enst.fr \
--to=demaille@inf.enst.fr \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=law@cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).