Korean and Japanese are different. The two collide and the output is in Japanese.

[nasungtae]

problem in ios.
Korean and Japanese are different. The two collide and the output is in Japanese.
android not problem.
Android and IOS have the same settings, but how is the output different?

setting hints:
options.languageHints = @[@"ko",@"en",@"zh-CN",@"ja"];
ios
CODE:
FIRVision *vision = [FIRVision vision];
FIRVisionCloudTextRecognizerOptions *options = [[FIRVisionCloudTextRecognizerOptions alloc] init];
//kor,@"en",@"ja",@"zh-CN"
options.languageHints = @[@"ko",@"en",@"zh-CN"];
FIRVisionTextRecognizer *textRecognizer = [vision cloudTextRecognizerWithOptions:options];
FIRVisionImage *image = [[FIRVisionImage alloc] initWithImage:img];
[textRecognizer processImage:image
completion:^(FIRVisionText *_Nullable result, NSError *_Nullable error) {
[self stopIndicator];
if(error != nil || result == nil) {
...
Note : ios deletes ja and ko is read.

android

[cs-googler]

This is the could text recognizer that is provided by firebase. We made some changes to Firebase ML Kit to better distinguish the on-device APIs from cloud based APIs. "ML Kit"(without firebase branding) contains all the on-device APIs. Here's the migration guide from firebase mlkit to mlkit. All further improvements and new APIs will be released only with the new ML Kit.

We are working on adding more language support in the on device mlkit as it currently only support Latin. Please stay tuned.