Thanks Ben. Ok that makes sense. Normally if you roll the source code yourself there are no issues since you are taking responsibility for the code being delivered to the AppStore.
I know that sometimes Apple insta-rejects based upon the symbols in your binary. Collisions with private APIs makes sense too. >From what I gather though is that the ICU library adds quite a footprint ~25Mb which is kinda prohibitive relative to our app size. http://sqlite.1065341.n5.nabble.com/unicode61-FTS-tokenizer-td62499.html Dr Richard Hipp states in the above linked post that `unicode61` is independent of ICU yet I keep getting the following error: 'unknown tokenizer: unicode61' Which makes me thinks the rules for v6.1 of unicode are hard baked into the code somewhere. Worst case scenario you are saying that rolling a build of sqlite3+ICU won't get rejected from Apple AND the `unicode61` tokenizer works? This is good news. I'd still like confirmation of how to get the ICU-less version working if it is at all possible. -- View this message in context: http://sqlite.1065341.n5.nabble.com/Unicode61-Tokenizer-tp76113p76115.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
