[EN Number] Entities recognized incorrectly in input cases like "5k-20k"
See original GitHub issueDescribe the bug Don’t recognize 5k-20k
To Reproduce Steps to reproduce the behavior:
- code
Gson gson = new GsonBuilder().create();
System.out.println("====A");
String input = "5k-20k";
System.out.println("input:" + input);
System.out.println("====B");
List<ModelResult> results = NumberRecognizer.recognizeNumber(input, Culture.Chinese);
results.forEach(e -> {
System.out.println(gson.toJson(e));
});
System.out.println("====C");
results = NumberRecognizer.recognizeNumberRange(input, Culture.Chinese);
results.forEach(e -> {
System.out.println(gson.toJson(e));
});
2.result ====A input:5k-20k ====B WARN: Look-behind groups with no maximum length not supported. Java version <= 8. ====C {“text”:“5k-20k”,“start”:0,“end”:6,“typeName”:“numberrange”,“resolution”:{}}
3.error
- recognizeNumber don’t recognize
- recognizeNumberRange recognized,but
resolution is null
Expected behavior
- recognizeNumber:5000,20000
- recognizeNumberRange:5000 - 20000
Platform (please complete the following information):
- Platform: Java
- Environment: package & console
- Version of package : master
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
(PDF) Woodward 26348B ECM 3
The ECM3 is designed to be installed directly on the engine. On engine mounting minimizes wiring cost by minimizing wiring length and the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing now as we’ve validated it works in Java too.
@LionbridgeCSII this issue was originally reported in Java, but the issue fix is only validated on .NET, so I don’t think it can be closed yet. While Java is outside your scope, if the new specs pass for Java, then we can close it. Could you test that?