Curve-Line System - Bluetoes edition

[Mauro]

@Mauro what do you need from me transcription-cleaning wise (is this even a term or did I just make it up?..)
Until now I have been using the below as a "whole manuscript" base check 

#=IVTFF EvaT 2.0 M 3
# Extracted from LSI_ivtff_0d.txt
# Version 2a of 02/02/2023

My preference however is, very strongly, with Rene's transcription "LZ v. 3a" The other was just easier for bulk conformance checks. 
My code is set up to deal with some things in this transcription, however ambiguity, extended eva etc, I was dealing with myself. 
Over 10 pages this was fine (I felt), but going beyond that does my code need to account for this in some way? I'm guessing "delete" is the usual option.. I doubt this makes a massive difference overall, but things like "is this a, or o?" when a or o make my system work.. its a bit painful to say "delete". Moreover I probably slightly disagree with Rene on maybe 1 glyph per page on average, but others can be (and usually are) several, it adds up.

First I'd need a clear explanation of how your system works (ie.: how to convert EVA characters to curve-line).

For the transcription what I need is a single text file without metadata, converted to your curve-line system. Words separated by spaces or newlines (or any other formatting character actually).

The best would be to start from the same RF1a-n transcription I used in my study, for consistency (not sure if it's "LZ v. 3a", but it comes from René's website). The exact text I used is called "Rf1a-n-x7 without question marks.txt" and it's posted on Github in this folder:

You are not allowed to view links. Register or Login to view.

PS.: there's a header line starting with %c% which you can remove