Accents (é, á, etc.) as Titles of Menu items

[keanulee]

If a character with an accent is present in the title of a menu item, the entire title is empty.

menu.items(0, [{
  title: 'Some accént'
}])

[sarfata]

@keanulee iOS or Android? Or Both?

[keanulee]

Reproduced with iOS (unsure about Android)

[samuelmr]

Tested on CloudPebble and Android and 'Some accént' works as expected.
With CloudPebble and iOS the same code fails (empty title on the watch).
(I'm running 2.1.0-rc2 on Android and 2.5.1 on iOS. The watch is 2.8-beta9.)

Previously when I was working with OSX SDK, I was having trouble with non-ASCII characters. Solved the issue by making sure all my source files were using UTF-8 encoding.

[keanulee]

In my case the string with the accent came from another source (response of an XHR), so I don't think it has to with the JS source code encoding (the example I used above is just a simplified reproduction of the issue).

[samuelmr]

Nevertheless you should make sure your characters are in UTF-8. Just to make sure, try something like this:

menu.items(0, [{
  title: utf8(data.title)
}])

function utf8(str) {
  return unescape(encodeURI(str));
}

[samuelmr]

I bet there is an assumption somewhere that the length of a character is always one byte. In UTF-8, some characters take two bytes. Consider the following example:

var UI = require('ui');
var menu = new UI.Menu({
  sections: [{
    items: [
      {title: 'áéàè98765', // 9 characters, 13 bytes
       subtitle: 'tuvwxyz' // displays: 765
      },
      {title: '12345åäö', // 8 characters, 11 bytes
       subtitle: '987654' // displays ö
       }
    ]
  }]
});
menu.show();

The same bug is in Simply.js.

[Meiguro]

• Support for accents have been added in 7d5d6f1, ticket Pebblejs not support utf8 string and Chinese Language. #15 thanks to songfei.
• The subtitle disappearing was reported in a ticket that seems to be missing now, but the issue has been fixed in 1ca0d8a.

It takes time for changes to propagate to CloudPebble. Sorry for the wait everyone.

Odd that Simply.js has the same bug since it uses App Message directly to serialize strings. That would be an issue with PebbleKit JS itself. I'll verify and pass that along.