Add zh-CN translation

[k08045kk]

Thank you for the translation. (https://github.com/k08045kk/CopyTabTitleUrl/issues/62)

Sorry, we have the following changes: I would appreciate it if you could revise the translation. Please translate overviewL〇〇. options〇〇Title has been deprecated. options〇〇LegendContent is scheduled to be deprecated. options〇〇InnerText is scheduled to be deprecated.

Please translate overviewL〇〇. Use on store pages. If not translated, the English text will be displayed.

options〇〇Title has been deprecated. wiki/Options takes care of that.

Is it necessary to translate options〇〇LegendContent, optionsContext〇〇Content? Personally, I think of it as a commonly used term that does not depend on language. It might be better to translate it, but I don't want to translate it if I don't have to do it. Please tell me your opinion. (We use similar English words in the format field names. Users should be able to understand them.)

options〇〇InnerText has been redefined as an item that does not require line breaks. (I will handle it. No processing required) optionsShortcutDescriptionContent optionsShortcutChromeDescriptionContent optionsShortcutFirefoxDescriptionContent

The following items are special features. We will cancel the translation to prevent users from using it carelessly and causing trouble. However, translation will be required when we officially support it in the future (I will handle it. No processing is necessary) optionsCopyProgrammableContent optionsCopyScriptingContent optionsMenusFormat9Title optionsExtendedEditContent optionsExtendedModeContent

[k08045kk]

Sorry, I will reconsider the translation. If you specifically need a translation for zh-CN, please raise another issue or PR.

[Crystal-RainSlide]

Sorry for the late response, I'd wait a bit more before applying the translation, so the entries can settle down.

About options〇〇LegendContent, optionsContext〇〇Content... For a translation, those commonly used terms can be skipped. However, for a language localization, optimize the terms for a locale is as important as traslating foreign language.

Morever, optionsContext〇〇Content and specifically "Browser Action" in options〇〇LegendContent is very troublesome in Chinese if not translated, or if translated just literally.

• The word "Context" is not used with "Menu" in Chinese, "Context Menu" is translated to "Right Click Menu" or Just "Menu".
• "Browser Action" don't even exist in Chinese, there is only "Click the extension icon". Also, generally, "Browser Action" don't seem to be well adopted outside the WebExtension developer community.

[k08045kk]

First of all, we are still in the transition period of development. Therefore, the options screen is subject to change. We are already starting to deviate from the latest GitHub updates. It would be better to start translation slowly after development has settled down.

options〇〇LegendContent optionsContext〇〇Content I don't understand the nuance of it, but I have grasped the nuance. I guess some languages may have problems with the English word as it is. I will rescind the abolition. (If you are going to translate the browser action, you might as well translate the others as well, to maintain the overall atmosphere.)

I'm wondering how I should approach translation. I chose not to translate. However, I now know that there is a problem with this.

I don't know how to understand the translation. For example, if a translation contains a sentence with malicious intent, I would not be able to understand it. There is a proposal to adopt a translation that many people agree with. However, the number of people who come here is small. There are also plans to return to machine translation. I worry about something. Even if we receive a translation, we may not be able to hire you. It's not your fault. I'm just immature.