I'm not sure about this one:

When marking a integer field as searchable, the integer-value was stored as `str` in the index until Plone 4.2.
But with Plone 4.3 it is now a `unicode`, because of [changes in Products.CMFPlone](https://github.com/plone/Products.CMFPlone/blob/master/Products/CMFPlone/UnicodeSplitter/splitter.py#L193).

This is not a collective.dexteritytextindexer issue and may not be a problem but I don't have a good feeling about mixing `str` and `unicode` in an index - although this might not be an issue when in `SearchableText` (e.g. which is not sorted usually).