On 07/17/2016 04:02 PM, Jean-Marc Lasgouttes wrote:
> Le 15/07/2016 20:01, Richard Heck a écrit :
>> The problem is that postats.py is passed the paths to the po files,
>> which are of the form ../../po/POFILE.po. But make first cd's to the
>> *main* po directory, under the root of the source tree.
Le 15/07/2016 20:01, Richard Heck a écrit :
The problem is that postats.py is passed the paths to the po files,
which are of the form ../../po/POFILE.po. But make first cd's to the
*main* po directory, under the root of the source tree. So the paths no
longer make sense.
Is it better now?
JMar
Am Sonntag, 17. Juli 2016 um 14:14:33, schrieb Richard Heck
> On 07/17/2016 01:06 PM, Jean-Marc Lasgouttes wrote:
> > Le 15/07/2016 20:01, Richard Heck a écrit :
> >> Suppose I configure and build LyX in a separate directory build/. Then,
> >> to update stats, I have to run "make i18n.inc" from bu
On 07/17/2016 01:06 PM, Jean-Marc Lasgouttes wrote:
> Le 15/07/2016 20:01, Richard Heck a écrit :
>> Suppose I configure and build LyX in a separate directory build/. Then,
>> to update stats, I have to run "make i18n.inc" from build/po/, since
>> that is where the Makefile is. But this fails:
> [.
Le 15/07/2016 20:01, Richard Heck a écrit :
Suppose I configure and build LyX in a separate directory build/. Then,
to update stats, I have to run "make i18n.inc" from build/po/, since
that is where the Makefile is. But this fails:
[...]
The problem is that postats.py is passed the paths to the
Suppose I configure and build LyX in a separate directory build/. Then,
to update stats, I have to run "make i18n.inc" from build/po/, since
that is where the Makefile is. But this fails:
cd ../../po ; /usr/bin/python postats.py "2.3.0dev" ../../po/ar.po
../../po/ca.po ../../po/cs.po ../../po/da.p
