On 28-09-2013, at 12:34 AM, Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com> wrote:

> I suggest that we move the last bits of difference from MultiCharacter* -> CharacterScanner, properly classify what is *Multilingual related, and then remove the Multi* classes. Sounds right?

In general, yes. The smart thing is to end up with CharacterScanner instead of MultiCharacterScanner, just because the name is simpler. 

We can probably fudge things a little to make the Multi-* classes acceptable in all normal-running, swap code to not refer to the non-Multi classes, then they can be cleaned up without fear of breaking anything live, then swap everything back to non-Multi, then delete all Multi-*.

Then maybe we can do the same to Paragraph & NewParagraph and any other confused classes.

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Never write software that patronizes the user.