Complete
over 5 years ago

Expected.

Hebrew presented as question marks in simulator

I have created a Hebrew resources file in UTF-8 and entered Hebrew characters.  I know that the encoding is correct since I use System.println() the exact string that it is about to print out.  This comes out like this:

However when it comes up on the simulator with encoding Hebrew it looks like this:

Is there a bug with the simulator or am I doing something wrong?

Former Member
Former Member
  • over 1 year ago

    I don't understand this: some of the old models do display Hebrew characters in the simulator (i.e: instinct2, descentg1), but the newest models (i.e: fr965, epix2pro42mm) still don't

  • over 2 years ago in reply to flocsy🤠

    > This is not expected

    From a user perspective, I understand that it is not behaving as you'd expect. Once you've considered what the simulator would have to do to make this work for all devices, you realized why.

    > isn't the simulator using the same fonts as the real devices?

    Unfortunately, the ConnectIQ simulator does not use the same font data as the device.

    To put it simply, the simulator isn't capable of duplicating the behavior of the different versions of the font rendering system in a single application. That is one issue that prevents us from just using the native font data directly; compatibility. This is not the only reason.

    > The real device (i.e fenix6) displays the same text in Hebrew.

    Yes, real devices will be the only way to perfectly reproduce what users experience.

    > All we want is to see the same in the simulator. The same text in fr255 works even in the simulator.

    I believe that this works because the simulator fonts for fr255 were generated after those for the fenix6, and a much more complicated process was followed to generate them.

    I am pretty confident that we could fix the font data for fenix6 to work like it does for fr255. It would require completing the work to get the font data generation scripts to follow the new process (if that hasn't been completed yet), and re-generating the font data for the fenix6. I'd also bet that there are other devices that would benefit from this, you're just testing on the flagship devices.

    There are already a handful of bug reports on this, some of which were reported by you. Instead of creating a new one, I'm just going to update the most recent one to reference this post and indicate that we should fix the font generation process and re-apply it to recent devices.

  • over 2 years ago

    there's something I don't understand about your comment that "this is expected":

    1. This is not expected Slight smile

    2. The real device (i.e fenix6) displays the same text in Hebrew. All we want is to see the same in the simulator.

    3. The same text in fr255 works even in the simulator.

    So to me it looks that it is a bug either in the simulator's config (probably) or the font that the older devices (i.e fenix6) use in the simulator is not the same as on the real device

  • over 3 years ago

    I don't understand something: isn't the simulator using the same fonts as the real devices? If I see a glyph on a real fenix6 then why the fenix 6 in the simulator doesn't have that glyph?