Hmm, well then I guess for now the small list of tags that still exist as blanks have to be printed using the <b pos="1"/> option. I could change it so that it flushes all blanks, or keeps them in their position if possible. The good thing is that these aren't wordbound semantically so them not being in their "correct" position won't cause a lot of issues.
This can be discussed: Do we want control over where to print these tags if they exist in the stream (not wordbound tags or block tags), or do we want that they flush out anyway and the user shouldn't worry about the blanks. *तन्मय खन्ना * *Tanmai Khanna* On Thu, Aug 27, 2020 at 1:20 PM Kevin Brubeck Unhammer <unham...@fsfe.org> wrote: > Tanmai Khanna <khanna.tan...@gmail.com> > čálii: > > > I always thought that's the default behaviour. That if some blanks aren't > > explicitly printed in the transfer rules then they're flushed. I'll check > > it out, but it should be that. > > The old behaviour has been to just throw away anything that's eaten by > a rule but not explicitly printed. So if you had a rule matching two > patterns, for example the words "ph'nglui mglw'nafh", and your input was > "ph'nglui <blink>mglw'nafh</blink>", but you just used <b/> and not > <b pos="1"/>, then transfer would eat the first blink giving "ph'nglui > mglw'nafh</blink>" and you would not be eaten first. > _______________________________________________ > 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
