So, we have this processing function for <bb>, like, { s/a/bb/g; }. Cool. But what if I have another metatag called "<a>" ? It got instantly more complicated. Now I have to write code to the processor that will apply the substitution only for text outside of metatags, that means writing code to detect the tags inside the substitution text.
Now, suppose I make another metatag "<foo>" that will substitute "foo => bar":
"<foo>fo<U>o bar</U></foo>" => "baR BAR".
Now, the replacer wouldn't find "foo" because there was "<U>" inside it, even though the "<U>" should be null length and invisible.
Maybe that would explain my preference to do it with plaintext and array of offsets and tag types (the second approach)?
In reply to RE: (tye)Re: Metatag processing (overlapping regions)
by kaatunut
in thread Metatag processing (overlapping regions)
by kaatunut
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |