Decision - review expanding name translation support for other special characters
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
There is a [discourse question](https://discourse.onebc.ca/t/name-translations/489) asking if we are going to support special characters outside of what we currently allow now for name translations.
We need to review the existing state of name translations and make a decision on this.
What we currently allow for name translations via [schema validation rules](https://github.com/bcgov/business-schemas/blob/651e53541031303783b6394d091382a18318cd48/src/registry_schemas/schemas/name_translations.json#L17):
* spaces
* A-Z & a-z
* accented letters
* Underscore (_)
* At symbol (@)
* Period/dot (.)
* Forward slash (/)
* Hash/pound sign (#)
* Apostrophe/single quote (')
* Ampersand (&)
* Plus sign (+)
* Hyphen/dash (-)
* max length = 50
**Tasks**
- [ ] Review current name translation rules
- [ ] Make decision if we will expand special character support for name translations
- [ ] Cut tickets as req’d
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.