3 ms·
> Where do you draw the line, though? I think the likely answer is going to be – no, they won't allow any language, they will keep to a restricted alphabet for
by skissane 6y ago
> Where do you draw the line, though?
I think the likely answer is going to be – no, they won't allow any language, they will keep to a restricted alphabet for company names, based on what characters are used in a list of allowed languages. What they'll do, is extend that list to include indigenous languages of British Columbia. So likely there will be a process, in which an indigenous community will submit an application to have its script allowed in company names (and possibly other names such as personal names). The government will ask professional linguists to advise on the application to ensure its correctness. Then the characters used to write that particular language will be added to the allowed list.
I think the argument is that the British Columbia government has a special moral duty to its indigenous peoples to help preserve their languages and culture, which justifies them going the extra mile to support the official use of their languages. I don't think it has the same moral duty to preserve Tibetan or Northern Kurdish (Kurmanji) so it would be justified in not extending this provision to those languages.
One potential issue I foresee is data interchange. I presume that British Columbia shares company data with other Canadian provinces, the Canadian federal government, probably even foreign governments (especially the US) and private sector firms (such as D&B Hoovers). What if the data interchange format doesn't allow these additional characters?
One solution is to give the company two names – its name in the indigenous language, and an English/French approximation to that. The system would store both names. Data interchanges which can't support the indigenous language characters would only receive the English/French approximation name.