Re: Broken translation system

Hi Yuri,
I followed the steps mentioned in htdocs/uitranslationnotes.html and 
created 'make FontForge.pot' in the fontforge directory since it did not 
exist there, but I had done noting about the version that Barry created in 
directory po - yet.

If you do:
cd fontforge
make FontForge.pot

ls -l FontForge.pot
749997 Dec 14 23:56 FontForge.pot

If you do:
cd po
make FontForge.pot

ls -l FontForge.pot
259983 Dec 14 23:59 FontForge.pot

Is this what you mean (up above)?

Question 1:
A) Maintain backwards compatibility and keep the make inside fontforge 
directory like it's mentioned in htdocs/uitranslationnotes.html
B) Move thecommand from fontforge/Makefile.am to po/Makefile.am and modify 
htdocs/uitranslationnotes.html to reflect using po directory instead.
C) something else?

Question 2:
Take a look at the XGETTEXT OPTIONS in po/GNUmakefile.in and 
fontforge/Makefile.am and see if something needs to be changed that got 
missed, or could probably be improved.
(compare options to 'man xgettext' )



On December 14, 2013 10:41:52 PM Yuri Chornoivan wrote:
> Hi,
> 
> Some latest tweaks in the catalog generation system lead to the build
> system fail to create complete FontForge.pot translation catalog.
> 
> Now
> 
> make FontForge.pot
> 
> or
> 
> make -C po potfile
> 
> generates catalog with 2485 messages, while there should be at least
> 7247 messages.
> 
> Can somebody look at this and fix the make scripts?
> 
> Thanks in advance for your answers.
> 
> Best regards,
> Yuri

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk