SDL 0202-Supported Character Sets

jordynmackool commented 6 years ago

Hello SDL community,

The review of "SDL 0202 - Supported Character Sets" begins now and runs through December 18, 2018. The proposal is available here:

https://github.com/smartdevicelink/sdl_evolution/blob/master/proposals/0202-character-sets.md

Reviews are an important part of the SDL evolution process. All reviews should be sent to the associated Github issue at:

https://github.com/smartdevicelink/sdl_evolution/issues/612

What goes into a review?

The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of SDL. When writing your review, here are some questions you might want to answer in your review:

Is the problem being addressed significant enough to warrant a change to SDL?
Does this proposal fit well with the feel and direction of SDL?
If you have used competitors with a similar feature, how do you feel that this proposal compares to those?
How much effort did you put into your review? A glance, a quick reading, or an in-depth study? Please state explicitly whether you believe that the proposal should be accepted into SDL.

More information about the SDL evolution process is available at

https://github.com/smartdevicelink/sdl_evolution/blob/master/process.md

Thank you, Jordyn Mackool

Program Manager - Livio jordyn@livio.io

jordynmackool commented 5 years ago

The Steering Committee returned this proposal for revisions on 2018-18-14 to allow the author time to make changes to the proposal. It was determined that the UTF 16 items will need to be removed as there are JSON limitations that have been discovered in the current proposal. The author will keep UFT 8 full-set and sub-set as items. In addition to the updates to the enum, the author will provide a better description of the character set parameter in the textField struct.

jordynmackool commented 5 years ago

The Steering Committee voted to fully accept this proposal on 2018-12-19. It was noted by the author that an OEM will support at least one of the character sets and if they support the entire UTF character set then they would implicitly support the other two as well.

jordynmackool commented 5 years ago

Issue entered: iOS Android Core RPC Generic HMI SDL HMI JavaScript Suite

smartdevicelink / sdl_evolution

SDL 0202-Supported Character Sets #612