Closed marijnschraagen closed 4 years ago
Interesting bug :) Frog relies on Ucto to handle BOM markers. (that those are evil goes without saying), so I assume the bug is more of an Ucto issue. Will move the issue to Ucto,
Interestingly, this bug is hard to reproduce in Ucto itself, as Ucto Frog uses the Ucto API slightly different from Ucto itself. Still it is an Ucto problem.
I committed a fix in Ucto. This should solve the problem. Please test.
I tried to update lamachine but I got an error about installing Aptitude (even though I installed from scratch yesterday and everything worked smoothly). Maybe I can try updating just ucto using lamachine-update --only
, which packages should I specify to get the new ucto only?
@marijnschraagen you have to wait until @proycon updates LaMachine. In this case the Development version, until the bug fix is approved and officially relased. Hope @proycon reacts soon....
Sorry for the delay! Thanks for the fix @kosloot! I'm testing it right now and will do a release straight away if this indeed fixes it.
I tried to update lamachine but I got an error about installing Aptitude (even though I installed from scratch yesterday and everything worked smoothly).
That is strange, can you create an issue if it persists?
Maybe I can try updating just ucto using lamachine-update --only, which packages should I specify to get the new ucto only?
You can do lamachine-update --only languagemachines-basic
, which includes frog and ucto. But it will only work if you're on the development version. Or just hold on until I publish the release and then it'll work in the stable LaMachine too.
The fix works and I have now released ucto v0.22, it should be available in LaMachine after a lamachine-update (or a fresh installation).
If a text file starts with a byte-order mark directly followed by a space or a tab then Folia gives an error. Column-based output is not affected. See the attached file as an example: bom.txt This file starts with a byte order mark
EF BB BF
, then a space20
, thenJan loopt.
:This results in the following error:
Either removing the BOM or removing the space at the start (but leaving the BOM) results in succesful parsing of the file. A tab character instead of a space also triggers the issue.