This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can device name support multi-language

Hi,

We have a device needs to support user change the device name. We already finished this function. The changed device name can be store in internal flash, and broadcast from next advertising. My question is: whether the device name can support multi-language. The user scenario as below,

  1. User set their favorite name through Android or iOS App, the name may be in Chinese, Japanese, German,...or any other country language.
  2. nRF51822 store the new name in the internal flash.
  3. Next advertising, user can see their setting name on App correctly.

Please give me any your advice to achieve this function. Thanks for any coming information.

Parents
  • From the Bluetooth spec

    12.1 DEVICE NAME CHARACTERISTIC
    The Device Name characteristic shall contain the name of the device as an UTF-8 string ...
    

    Since UTF8 encodes every unicode codepoint then you can have any and every language you like.

  • 'sniffing with the nordic sniffer'. That doesn't really mean anything, it just sniffs bytes and passes them to probably wireshark for display. Wireshark (in my experience) just shows bytes and if each individual byte represents an ASCII character, it shows that. Wireshark doesn't try to interpret sequences of bytes as UTF-8 or anything else. This is no different from encoding a 32bit integer, wireshark just shows 4 bytes of data and if it shows characters at all, it just shows the ASCII version of each byte.

    You need to stop conflating a sequence of bytes with how a particular app might interpret them. The nordic sniffer is a byte-based raw sniffer, it's not going to have a clue that the bytes represent unicode.

Reply
  • 'sniffing with the nordic sniffer'. That doesn't really mean anything, it just sniffs bytes and passes them to probably wireshark for display. Wireshark (in my experience) just shows bytes and if each individual byte represents an ASCII character, it shows that. Wireshark doesn't try to interpret sequences of bytes as UTF-8 or anything else. This is no different from encoding a 32bit integer, wireshark just shows 4 bytes of data and if it shows characters at all, it just shows the ASCII version of each byte.

    You need to stop conflating a sequence of bytes with how a particular app might interpret them. The nordic sniffer is a byte-based raw sniffer, it's not going to have a clue that the bytes represent unicode.

Children
No Data
Related