>>From: Alvaro Tejero Cantero <[EMAIL PROTECTED]>
>>To: "LyX Users" <[EMAIL PROTECTED]>
>>Subject: Making a translation: po-file testing
>>Date: Sun, 22 Oct 2000 11:53:01 +0200
>>
>>Hi, LyXers
>>
>>I have an improved version of es.po ready for testing. I have
>>downloaded, configured, compiled and installed lyx-1.1.6cvs.
>>As I don't have the slightest clue on how to incorporate my
>>corrections, I have overwritten the previous es.po in the po
>>directory with my own. I have recompiled and reinstalled. No trace of
>>my po file when starting LyX: it seems to be using the old one.
>>
>>Please note that I have been configuring with the flags
>>--with-lyxname=lyx-1.1.6cvs --prefix=/usr/local
>>
>>Anybody knows what to do?
>>I would like to start committing my translation files asap, but I
>>need to do some testing,
>>
>>thanks to all,
>>
>>
>>--
>>�lvaro Tejero Cantero
>>p42.org
It's true that the old README file in po/ disappeared...
The .po file is only used to record translation, you must
- create a file named es.gmo using msgfmt (gettext msgfmt, not native one
if it exists, so check that there exists a msgfmt executable in
/usr/local/bin); shell command:
msgfmt es.po
creates a binary file named messages that you can rename as es.gmo t
- if you have kept a record of the output of make install, a grep gmo
should recall you wher to put it (here it reads e.g. for spanish,
and lyxname=lyx-1.1.5:
installing es.gmo as /usr/local/share/locale/es/LC_MESSAGES/lyx-1.1.5.mo
You only need these steps to check, no lyx rtebuild is needed.
Beware that --with-lyxname=lyx-1.1.6cvs does not change the name of the
executable, which is still lyx and not lyx-1.1.6cvs, so here I wrapped
the make install step to protect the current lyx executable, which is in
public use.
--
Jean-Pierre
