Jonathan Washington
Jonathan Washington
I can also confirm that this is an issue with version 0.1.0, and it's interfering with pip installation of audiotools as well. The solution seems to be to either `touch...
I should clarify: by "version 3", I meant audiotools, not python. It's available here: http://audiotools.sourceforge.net
Still seems to be a problem. In `apertium-ote` I'm getting output like the following: ``` ^mi fädi/*mi fädi$ ^bi guatʼi/*bi guatʼi$ ^bi tagi/*bi tagi$ ^bi bo̱nga/*bi bo̱nga$ ^mi zu̱ni/*mi zu̱ni$...
Yes, I would say that's likely. But the following behaviour reported by @TinoDidriksen suggests that whether or not it's related to that, there's a major problem that needs to be...
@mikhael84, as a work-around, try commenting out the `apertium-tagger` blocks of `modes.xml` (and then recompile).
Also, this looks like an apertium-tagger bug; perhaps the issue should go in [apertium](https://github.com/apertium/apertium/issues) so the relevant devs see it?
> None of us use CentOS, and there is a functional workaround: You can use the Ubuntu setup in a lightweight chroot, Docker container, or virtual machine. I don't think...
Is this a problem with `lt-proc`, the `br` dictionary, or something else?
@hectoralos, could you clarify whether you're using shallow or recursive transfer?
> I've not yet used recursive transfer. Ah, that would explain the confusion. The code that @mr-martian posted wasn't pseudo-code, but the actual `apertium-recursive` formalism.