Unicode char issue

[maxaalexeeva]

Text: where locations are indexed by i, observational periods are indexed by t, b is the parameter of interest, and ∈ is the error.
Webapp:

The ∈ symbol is not processed right:

[BeckySharp]

we may need to use the non-normalized text......... masha, can you check to see if we have any options in processors as to what kind of normalization we have "on" and what we don't? Worst case scenario, we can use the raw tokens, but it will still affect the parse unless we can maybe disable the replacement or do some preprocessing of some kind...

…

On Sun, Jan 26, 2020 at 1:57 PM Maria (Masha) Alexeeva < ***@***.***> wrote: *Text:* where locations are indexed by i, observational periods are indexed by t, b is the parameter of interest, and ∈ is the error. *Webapp:* [image: Screenshot from 2020-01-26 14-53-10] <https://user-images.githubusercontent.com/31713912/73142439-dd6f3880-404b-11ea-91b7-a0e72c0b5e78.png> The *∈* symbol is not processed right: [image: Screenshot from 2020-01-26 14-53-49] <https://user-images.githubusercontent.com/31713912/73142441-df38fc00-404b-11ea-8b02-823ab2cef071.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#103?email_source=notifications&email_token=ABJCPCNHMCANBR7J5ACSLXTQ7YBMXA5CNFSM4KLZOOTKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IIZDUNA>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJCPCPYTCEJC5JU27BGQZDQ7YBMXANCNFSM4KLZOOTA> .

[maxaalexeeva]

@BeckySharp, haven't located that kind of option yet.. I'll look into it more soon.