Am Freitag, 1. September 2017 um 18:21:06, schrieb Jean-Pierre Chrétien <jeanpierre.chret...@free.fr> > Le 01/09/2017 à 17:38, Jean-Pierre Chrétien a écrit : > > > > > <cite> > > [...] > > > cd ../../newmaster/po && /usr/bin/msgmerge --update --lang=it it.po > > lyx-2.3.0dev.pot > > ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... > > > > terminé. > > it.po:33529: AVERTISSEMENT : un message à traduire ne doit pas contenir de > > séquence d'échappement « \f » > > it.po:33529: AVERTISSEMENT : un message à traduire ne doit pas contenir de > > séquence d'échappement « \f » > > cd ../../newmaster/po && rm -f it.gmo && /usr/bin/msgfmt -c --statistics > > --verbose -o it.gmo it.po > > it.po : 7212 messages traduits. > > [...] > > </cite> > > > > Could that come from the fact that, being in 2.3.x with an existing > > compilation > > in dir buildmaster, I ran in newmaster (my current git clone) > > > > $ git checkout master > > $ cd ../buildmaster > > $ make > > > > without erasing the contents of buildmaster or rerunning > > ../newmaster/configure --with-version-suffix --enable-qt5 > > before make? > > > > I will recompile from scratch to be sure. > > > > Done, I still get these messages (I have only kept those from it.po above, > but > they appear also from fi.po). > > BTW, the translation is e.g.: > it.po:33529: WARNING : a message to be translated cannot contain escape > sequence "\f" > > I guess "\f" is an invisble character like "\r" or "\n"? > > Could this come from Jean-Marc's patch? >
More like having (literally) \f in the po-file, correct would have been to have
\\f like for instance
at line 33522
#~ "* linenos,fontsize=\footnotesize,lang=fortran\n"
should be
#~ "* linenos,fontsize=\\footnotesize,lang=fortran\n"
Kornel
signature.asc
Description: This is a digitally signed message part.
