• Replies 38 replies
  • Subscribers 22 subscribers
  • Views 13762 views
  • Users 0 members are here
Options
Related

The function equals has bug when operand contains non-ASCII?

li2niu

https://youtu.be/xzEiET8Z-UY

As the video. I have two menu items, Count(计数) & Time(计时).

In English mode, I can select Count to choose from 100 to upper and select Time to choose from 1 to upper.

However, when I switch language to Chinese, the two items are the same(the pickers are both Time pickers). Why?

I don't own a physical device that supports Chinese, so I have no idea about the actual running status.

  • Not all languages are supported in the sim, and in the case of Chinese, that's an APAC device and the sim only does ROW/World Wide devices,

  • in reply to jim_m_58

    But the APAC language is properly rendered. 

    jim_m_58 said:
    Not all languages are supported in the sim

    Maybe, my device only supports some languages excluding Chinese. APAC characters will show as squares, which is quite different from that in the simulator.

  • in reply to flowstate

    Emma. There are no tricks in my code, I suppose. The snippet is copied from the official custom image menu demo with some modification. Later, I will try to find a device that supports APAC to investigate this issue.

  • in reply to li2niu

    Plus the sim literally allows you to select Chinese.

    jim_m_58 said:
    Not all languages are supported in the sim, and in the case of Chinese, that's an APAC device and the sim only does ROW/World Wide devices,

    Is the implication here that "if you pick Chinese in the sim, don't expect it to work properly?" (Note that by "work properly" I do not mean "simulate an APAC device perfectly".)

    If that was the case, you'd think the sim would simply not have that option.

    As a counter-example, WW/ROW devices do not support Asian languages, so they don't give you the option to select those languages, which is perfectly reasonable.

  • in reply to flowstate

    Try other languages in the sim (Non APAC devices) with things in Gregorain.Info,  Arabic, Czech, etc.

  • in reply to flowstate

    BTW, IMO, using language support as a differentiation strategy will be despised. As a user from APAC, I have to pay more for the language support. Does the language pack worth it? Or does the storage cost that much?

  • in reply to li2niu

    APAC and ROW devices are different HW and Part numbers,  You can't add Chinese to a ROW device.

  • in reply to jim_m_58

    1) That doesn't really explain why this specific case would not work (navigating to subitems in a Menu2), unless those subitems are chosen based on comparisons with the selected menu item text (in the Monkey C code itself, not behind the scenes), which is why I wanted to see the code. Even if that were the case, it still sounds like a bug to me.

    2) (re: Gregorian.Info) Localization/language-specific errors would make more sense, although they would still be disappointing.

    3) So as usual, the sim is not expected to work properly in certain edge cases. Good to know. Is there any way to know this advance (e.g. documentation / warnings in the sim) or is it as usual "privileged knowledge" that we can only learn by coming to the forums or finding out for ourselves?

    e.g. If Arabic isn't supposed to work properly in the sim, then when you select it in the sim, the sim could display a warning message. Or it could be documented somewhere.

  • in reply to li2niu

    In this case I don't think it's a deliberate market segmentation strategy (like releasing 245, 645 and 935) as much as it's a way for Garmin to save money on storage. i.e. I don't think Garmin expects to increase sales by having separate ROW and WW versions, it's just that they would rather save money on storage by not supporting all languages on all devices. (I realize that's kind of a meaningless distinction. I def see Western customers getting angry when they buy a discount Forerunner on Amazon only to find it's the APAC version which has old firmware.)