Just in case, I've taken a screenshot in the same area with a Pixel 2 XL on Android 8. Note: This app translates English into Korean and vice versa Korean to English uses Google's translator engine. What are the pros to converting the alphabet in these cases? I would think it'd be much easier to navigate if the name displayed in Maps were as physically accurate as possible. Lastly, these are names, so these can't possibly all be official translations and, in my opinion, more likely to contain errors, making finding a street with the map potentially more difficult than it was originally.Įspecially on the flip side, where someone from the US traveling to South Korea is a lot less likely to understand the pronunciation rules of Hangul. If they were in English, a Korean-only speaker would still be able to match the symbols to the physical street signs, something they could not do if they had no idea how to pronounce the letters andĪ Korean-only speaker unfamiliar with the area would have a very difficult time showing the map to someone native to the area to help get further, more detailed instructions. Wouldn't it be more useful if they remained in English? I can only see pros to doing so:
The picture at the bottom is of somewhere near downtown Orlando. (I have my phone is Korean as an attempt to aid myself in learning Korean) I've always wondered something, about how Maps (and a lot of other apps, like the native iOS weather app) convert city names and street names to Hangul (the Korean alphabet), as apposed to leaving them in English.
0 kommentar(er)
