-
Notifications
You must be signed in to change notification settings - Fork 603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse: Loose Matching #292
Labels
Comments
cc @pergardebrink @arschmitz (from original issue #288) |
ashensis
pushed a commit
to ashensis/globalize
that referenced
this issue
Mar 17, 2016
Globalize gets a logo
rxaviers
added a commit
that referenced
this issue
Nov 28, 2016
- Correctly handles prefix and suffix literals; #353; - Loose Matching: This implementation is now much closer to UTS#35 7.1.2 Loose Matching http://unicode.org/reports/tr35/#Loose_Matching and fixes all reported cases that related to it, including #288; - Regression: Drop scientific notation parsing support, which wasn't documented anyway and shall be implemented by #533. Ref #292 Fixes #353 Fixes #46 Fixes #288 Fixes #443 Fixes #457 Fixes #492 Fixes #587 Fixes #644
rxaviers
added a commit
that referenced
this issue
Nov 28, 2016
- Correctly handles prefix and suffix literals; #353; - Loose Matching: This implementation is now much closer to UTS#35 7.1.2 Loose Matching http://unicode.org/reports/tr35/#Loose_Matching and fixes all reported cases that are related to it, including #288; - Regression: Drop scientific notation parsing support, which wasn't documented anyway and shall be implemented by #533. Ref #292 Fixes #353 Fixes #46 Fixes #288 Fixes #443 Fixes #457 Fixes #492 Fixes #587 Fixes #644
rxaviers
added a commit
that referenced
this issue
Dec 13, 2016
rxaviers
added a commit
that referenced
this issue
Dec 13, 2016
- Correctly handles prefix and suffix literals; #353; - Loose Matching: This implementation is now much closer to UTS#35 7.1.2 Loose Matching http://unicode.org/reports/tr35/#Loose_Matching and fixes all reported cases that are related to it, including #288; - Regression: Drop scientific notation parsing support, which wasn't documented anyway and shall be implemented by #533. Ref #292 Fixes #353 Fixes #46 Fixes #288 Fixes #443 Fixes #457 Fixes #492 Fixes #587 Fixes #644
rxaviers
added a commit
that referenced
this issue
Dec 13, 2016
rxaviers
added a commit
that referenced
this issue
Dec 13, 2016
- Correctly handles prefix and suffix literals; #353; - Loose Matching: This implementation is now much closer to UTS#35 7.1.2 Loose Matching http://unicode.org/reports/tr35/#Loose_Matching and fixes all reported cases that are related to it, including #288; - Regression: Drop scientific notation parsing support, which wasn't documented anyway and shall be implemented by #533. Ref #292 Fixes #353 Fixes #46 Fixes #288 Fixes #443 Fixes #457 Fixes #492 Fixes #587 Fixes #644
rxaviers
added a commit
that referenced
this issue
Dec 13, 2016
rxaviers
added a commit
that referenced
this issue
Dec 30, 2016
rxaviers
added a commit
that referenced
this issue
Dec 30, 2016
rxaviers
added a commit
that referenced
this issue
Dec 31, 2016
rxaviers
added a commit
that referenced
this issue
Dec 31, 2016
rxaviers
added a commit
to rxaviers/globalize
that referenced
this issue
Feb 20, 2017
rxaviers
added a commit
to rxaviers/globalize
that referenced
this issue
Feb 23, 2017
rxaviers
added a commit
to rxaviers/globalize
that referenced
this issue
May 23, 2017
Merged
rxaviers
added a commit
to rxaviers/globalize
that referenced
this issue
May 23, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Handle Loose Matching in all parsing functions, which includes normalizing no-break space to space, different types of dashes, comma used as abbreviation, etc.
References:
String.prototype.normalize
and its polyill unorm.js.This might also be useful: http://userguide.icu-project.org/strings/unicodeset and http://userguide.icu-project.org/strings/properties
TODO:
PS: original issue #288
The text was updated successfully, but these errors were encountered: