Kornel Benko wrote: > > i mean we would just adopt the sequence of various command from "make > > lyx.pot-update" > > from quick view something like: > > python ./lyx_pot.py -b .. -o qt4_l10n.pot -t qt4 > > ../src/frontends/qt4/ui/*.ui > > python ./lyx_pot.py -b .. -o layouts_l10n.pot -t layouts > > ../lib/layouts/*.layout ../lib/layouts/*.inc ../lib/layouts/*.module > > python ./lyx_pot.py -b .. -o languages_l10n.pot -t languages > > ../lib/languages > > python ./lyx_pot.py -b .. -o encodings_l10n.pot -t encodings > > ../lib/encodings > > python ./lyx_pot.py -b .. -o ui_l10n.pot -t ui ../lib/ui/*.ui > > ../lib/ui/*.inc > > python ./lyx_pot.py -b .. -o external_l10n.pot -t external > > ../lib/external_templates > > python ./lyx_pot.py -b .. -o formats_l10n.pot -t formats ../lib/configure.py > > cat qt4_l10n.pot layouts_l10n.pot languages_l10n.pot encodings_l10n.pot > > ui_l10n.pot external_l10n.pot formats_l10n.pot | \ > > msguniq -o lyx.po && rm -f qt4_l10n.pot layouts_l10n.pot > > languages_l10n.pot encodings_l10n.pot ui_l10n.pot external_l10n.pot > > formats_l10n.pot > > /usr/bin/msgmerge --update --backup=none XXX.po lyx.pot > > > > where XXX.pot is taken from LINGUAS file. > > In cmake we use the supplied po-files instead. > > > > > and give some special target, so cmake users could write cmake po-update... > > and po files would be regenerated. > > But maybe the big difference is creating "POTFILES.in". > Here it is > #wc POTFILES.in > 352 352 9351 POTFILES.in > and the filenames inside are _not_ sorted. (This is a difference between > globbing in cmake and globbing in a shell) > We could sort it though ...
can you try it? ;) the holy grail would be to get rid of scons completely and have identical .po creation from automake and cmake... pavel
