Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.1.0
-
Component/s: None
-
Labels:
-
Sprint:Sprint 2 - Cumberland, Sprint 3 - Cumberland, Sprint 4 - Cumberland, Sprint 5 - Cumberland, Sprint 6 - Cumberland, Sprint 7 - Cumberland, Sprint 8 - Cumberland, Sprint 9 - Cumberland, Sprint 10 - Cumberland
Description
As we move to a more I18N aware system, we will run into the issue (especially in Europe, Korea etc.) of whether data is in canonical composed or decomposed form. The simplest/lowest cost solution would be to add a CXF interceptor to perform normalization on the way into and out of the API.
I would personally argue for NFKD as it tends to work better for search applications, and especially those with ngram matching.
