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.
*तन्मय खन्ना * *Tanmai Khanna* On Thu, Aug 27, 2020 at 1:27 AM Kevin Brubeck Unhammer <unham...@fsfe.org> wrote: > Tanmai Khanna <khanna.tan...@gmail.com> > čálii: > > > Thanks Unhammer! > > So now we have three kinds of units: block tags, superblanks, and > wordbound > > blanks. Block tags are hard breaks in the text, wordbound blanks move > > around with words, and superblanks are tags that aren't hard breaks but > not > > attached to words (such as <br/>). Tino can give you a list of tags and > > their classifications. > > > > As per your question about transfer, the <b pos="1"/> refer to the > > superblanks if they exist in the input. Wordbound blanks will reorder > > automatically and block tags won't move at all. > > > > We can also decide to make the remaining superblanks immovable and just > > output them when a rule is matched, but that is a decision that can be > > taken in the future. For now, blanks in transfer rules work for any > > superblanks that still exist in the stream. Hope that answered your > > question :)) > > Almost :) If input has <br/> somewhere, and my transfer rules don't have > any <b pos="…"/> (only maybe <b/>), will it still be output? > _______________________________________________ > 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
