Comments

  • Hi @TaisFukushima thank you for your reply and all of your efforts.
  • Thank you so much @TaisFukushima for this correction, It's done!
  • Other differences, prune, book For both of the above words there are two results elements in V2 while in V1 there is only one results element This seems to be a discrepancy since for a word like "provision" in both versions V1 and V2 there is only one results element!
  • Another case: dino which gives DINO and dino
  • Hi Admins, I have also seen such problem, Please check the word "think" as a verb in entries endpoint. In version 1 for the first definition I see these examples: text: "she thought that nothing would be the same again" text: "it's thought he may have collapsed from shock" text: "up to 300 people were thought to have died"…
  • Hi @Simone, This feature is very valuable and important in learning. I am so interested in implementing this feature in my app. When do you make this feature available? can I test it in version 2? Best Regards,
  • Dear @AmosDuveen, Thank you so much for your answer. As I have investigated I found that non-native English learners are used to the symbol /ʌ/. When they see /ˈməðər/ they pronounce it as "mether" not "mother". I am worried this policy makes the users confused. Best Regards,
  • Dears @AmosDuveen and @joughtred, Thank you so much for your help and complete details. I checked the aforementioned websites and understood what happens. The reason that made me confused is that I have also checked another website of Oxford: https://oxfordlearnersdictionaries.com/us/definition/english/mother_1?q=mother…
  • Dear @AmosDuveen Thank you for your response. I got it.
  • Dear @AmosDuveen Thank you for your consideration. I have set a detector in my app to warn me whenever such discrepancies happen. I will notify you here if I encounter another one. Kind Regards,
  • Dear @AmosDuveen Thank you so much for your explanation in details. Yes, I also had come to the same conclusion to use "search" endpoint for these cases. but I was not sure about it since it leads to one more api call. However, for such cases I see it is the only solution . All the best,