Re: [Po4a-devel] Mots-clés pour identifier les chaînes à traduire

Hello, I'm answering in english because this is an english-speaking mailing list. Please do not stick to french ;) For the others, Binoyte would prefer to have an explicit \gettext{} macro in LaTeX to make sure that there is no false positive, ie text marked to translate where it should not (Binoyte, please correct me if I'm wrong). This could certainly be possible, but this is definitely not the approach chosen in po4a. We try to extract the string automatically, with no extra burden on the original author. From my personal experience, your latex source quickly becomes unmanageable when you start littering it with orthogonal macros. I fully agree that when po4a generates too much false positives, it gets annoying. But at the same time, these strings are rather easy to ignore, aren't they? We could also possibly instruct the LaTeX module to not have so much positives. Could you please setup a small example exemplifying how po4a marks too much content to be translated? Thanks in advance, and welcome in the community. Mt. On Tue, Sep 12, 2017 at 10:51:22AM +0200, Binoyte wrote: -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please!