Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i18n-ISSUE-484: Use BCP47 instead of ISO 639-1 for identifying languages #87

Closed
r12a opened this issue Mar 16, 2016 · 1 comment
Closed
Labels
needs-resolution i18n expects this item to be resolved to their satisfaction. recycle Attach to closed items where the issue needs to be ressurected for a next version of the spec. s:vehicle-data https://w3c.github.io/automotive/vehicle_data/data_spec.html

Comments

@r12a
Copy link
Contributor

r12a commented Mar 16, 2016

http://www.w3.org/Mail/flatten/index?subject=i18n-ISSUE-484&list=public-automotive

Raised by:Steven Atkin
Opened on:2015-08-19

8.2 Language Configuration Interface
http://www.w3.org/TR/2015/WD-vehicle-data-20150616/#attributes-49

BCP47 should be used to identify languages instead of ISO 639-1.
See https://tools.ietf.org/html/bcp47

One of the problems with using ISO 639-1 2 letter codes is that it does not adequately address the handling of Chinese. For example, in ISO 639-1 Chinese is represented as zh. This code cannot indicate whether the writing system is Simplified Chinese or Traditional Chinese. The BCP47 standard clearly indicates which writing system is in use. In this case if Simplified Chinese was being used the code would be zh-Hans and for Traditional Chinese it would be zh-Hant.

@r12a r12a added the s:vehicle-information-api https://w3c.github.io/automotive/vehicle_information_api/vehicle_information_api_specification.html label Mar 16, 2016
@r12a r12a added the needs-resolution i18n expects this item to be resolved to their satisfaction. label Nov 16, 2018
@r12a r12a added the recycle Attach to closed items where the issue needs to be ressurected for a next version of the spec. label Nov 14, 2019
@r12a
Copy link
Contributor Author

r12a commented Nov 14, 2019

Closing because the document was published as a deprecated WG Note in Jun 2018. Leaving a recycle label in place in case this comes up again, since it indicates that the issue wasn't addressed.

@r12a r12a closed this as completed Nov 14, 2019
@plehegar plehegar added s:vehicle-data https://w3c.github.io/automotive/vehicle_data/data_spec.html and removed s:vehicle-information-api https://w3c.github.io/automotive/vehicle_information_api/vehicle_information_api_specification.html labels Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-resolution i18n expects this item to be resolved to their satisfaction. recycle Attach to closed items where the issue needs to be ressurected for a next version of the spec. s:vehicle-data https://w3c.github.io/automotive/vehicle_data/data_spec.html
Projects
None yet
Development

No branches or pull requests

2 participants