Is there anything wrong with using Chinese as a parameter for multilingual components such as vue-i18n?

js can directly use Chinese as the variable name, so it is very convenient to use Chinese directly when setting language files. But is there a problem with this?

it"s usually like this: 

// 
export default {
  LIST: "List",
  SETTING: "Setting",
  DISABLE: "Disable",
}
// 
export default {
  LIST: "",
  SETTING: "",
  DISABLE: "",
}

then call: $t ("LIST");

if you directly use the Chinese bit key: 

// 
export default {
  : "List",
  : "Create",
  : "Setting",
  : "Disable",
}

$t ("list"); if the language file is not loaded, the list will be displayed directly; when the language file is loaded, the List will be displayed;

which method is good? Will there be any big holes in defining key, in Chinese?

Vue.js javascript
Jun.25,2021

with regard to this problem, I have personally practiced that it is not impossible to use Chinese as the key name, but it is technically feasible. But a big problem I faced later was that it was not a question of Chinese or English, but a question of internationalization. If it is only a Chinese-English interchange, it is possible to use any language as the primary key. But later, when we want to translate the website into Japanese, French, Spanish and Arabic, the problem arises. Now English is basically an intermediary language, and basically all native speakers understand English. the content can be translated into the corresponding text according to the English key name, and if the key name is Chinese, the person needs to know Chinese. Chinese is not strong enough to become a universal intermediary language in the short term, so the most appropriate thing to do is to use English as the key name.

obviously the first good. What if List is not called "list" in the future? And then it's associated with multiple languages. Do you just need to change the key one by one?
use a unified key to associate them, so that you will still build a corresponding "list" in Chinese: "list".
it doesn't make any sense.

Previous: On the mobile side, div contenteditable= "true" exceeds the limit on the number of input words and the cursor is positioned at the end after substring intercept.

Next: Mysql recovery data

css mysql arrays josn react html typescript webpack npm sass R objective-c .net sql-server jquery python-3.x angularjs django angular excel regex iphone ajax linux xml pandas vba spring database wordpress string wpf xcode windows bash postgresql oracle multithreading eclipse list firebase algorithm macos forms image scala visual-studio azure bootstrap spring-boot react-native python-2.7 docker performance function winforms matlab powershell apache dataframe api sqlite numpy rest shell selenium flutter dart maven loops qt swing android-studio csv express file class tensorflow sorting codeigniter perl
© 2021 CodesHelper
Advertising Contact us About us
Menu