I've been able to reproduce the loop and fix it. It was mainly due to an unexpected pattern in the testvoc script, but there was also a typo in the bidix that contributed to the problem.
1. The testvoc script did not account for bidix entries with empty translations and would add extra slashes in many cases. These are used to test multiple translations for a single entry, which is done by an awk script in a while loop that could not be escaped. I have fixed the issue with the extra slashes and changed the while loop to a for limited to 50 iterations. This should be enough for any pair and the loop includes a condition to escape it before the 50 iterations, so there is no extra unnecessary processing. I'll post a pull request directly to the repo with the fixes shortly. 2. There is an entry in the bidix (and probably Arpitan monodix as well, because it generates properly), "Salinas de Gotari", with a line break after the last tag. It looks like a typo. This typo appears to be valid in Apertium format but the testvoc script assumes an entry per line and the double slashes occurred here too. Thanks to the loop limit, testvoc doesn't get blocked anymore by this entry (and it doesn't appear in the list of errors, because it generates properly), but it should be fixed. Regards, *Marc Riera* Missatge de Marc Riera Irigoyen <marc.riera.irigo...@gmail.com> del dia ds., 15 d’ag. 2020 a les 11:53: > Hello Hèctor, > > I see that the testvoc script you're using is the one I developed based on > previous scripts used in several pairs. It shouldn't be producing a loop > and have never found it before. Given that it's happening only when > translating from Arpitan to French, I guess there may be something that I > didn't account for when developing the script. I'll take a look and try to > recreate it. > > Regards, > > *Marc Riera* > > > Missatge de Hèctor Alòs i Font <hectora...@gmail.com> del dia ds., 15 > d’ag. 2020 a les 10:46: > >> I am experiencing a very strange behaviour in the fra-frp testvoc. While >> there is not any problem in the frp2fra side (the test is finished in less >> than 30 minutes in my computer), in the fra2frp there is a kind of >> infinitive loop. The same fine is again and again created and deleted and >> the tesvoc does not end even waiting during more than 24 hours. The file >> which is deleted and created again and again (always with the same name) >> has exactly the same content. The first lines are: >> >> >> [\^frère<adj><m><sg>$]^frère<adj><m><sg>/~/frâre<adj><m><sg>$+^.<sent>/~/.<sent>$ >> >> [\^frère<adj><m><pl>$]^frère<adj><m><pl>/~/frâre<adj><m><pl>$+^.<sent>/~/.<sent>$ >> >> [\^frère<adj><f><sg>$]^frère<adj><f><sg>/~/frâre<adj><f><sg>$+^.<sent>/~/.<sent>$ >> >> [\^frère<adj><f><pl>$]^frère<adj><f><pl>/~/frâre<adj><f><pl>$+^.<sent>/~/.<sent>$ >> >> [\^frère<adj><f><sg>$]^frère<adj><f><sg>/~/frâre<adj><f><sg>$+^.<sent>/~/.<sent>$ >> >> [\^frère<adj><f><pl>$]^frère<adj><f><pl>/~/frâre<adj><f><pl>$+^.<sent>/~/.<sent>$ >> >> [\^frère<adj><m><sg>$]^frère<adj><m><sg>/~/frâre<adj><m><sg>$+^.<sent>/~/.<sent>$ >> >> [\^frère<adj><m><pl>$]^frère<adj><m><pl>/~/frâre<adj><m><pl>$+^.<sent>/~/.<sent>$ >> >> [\^frère<adj><f><sg>$]^frère<adj><f><sg>/~/frâre<adj><f><sg>$+^.<sent>/~/.<sent>$ >> >> [\^frère<adj><f><pl>$]^frère<adj><f><pl>/~/frâre<adj><f><pl>$+^.<sent>/~/.<sent>$ >> >> [\^1er<adj><f><pl>$]^1er<adj><f><pl>/~/1ér<adj><ord><f><pl>$+^.<sent>/~/.<sent>$ >> >> [\^1er<adj><f><sg>$]^1er<adj><f><sg>/~/1ér<adj><ord><f><sg>$+^.<sent>/~/.<sent>$ >> >> [\^1er<adj><m><pl>$]^1er<adj><m><pl>/~/1ér<adj><ord><m><pl>$+^.<sent>/~/.<sent>$ >> >> [\^1er<adj><m><sg>$]^1er<adj><m><sg>/~/1ér<adj><ord><m><sg>$+^.<sent>/~/.<sent>$ >> >> [\^abattu<adj><f><pl>$]^abattu<adj><f><pl>/~/abatu<adj><f><pl>$+^.<sent>/~/.<sent>$ >> >> [\^abattu<adj><f><pl>$]^abattu<adj><f><pl>/~/dèfêt<adj><f><pl>$+^.<sent>/~/.<sent>$ >> >> [\^abattu<adj><f><pl>$]^abattu<adj><f><pl>/~/dèchesu<adj><f><pl>$+^.<sent>/~/.<sent>$ >> >> [\^abattu<adj><f><sg>$]^abattu<adj><f><sg>/~/abatu<adj><f><sg>$+^.<sent>/~/.<sent>$ >> >> I have never seen such a thing before and I cannot imagine what can cause >> this behaviour. Any ideas? >> >> Hèctor >> _______________________________________________ >> Apertium-stuff mailing list >> Apertium-stuff@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/apertium-stuff >> >
_______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
