{"id":13452668,"url":"https://github.com/sparanoid/chinese-copywriting-guidelines","last_synced_at":"2025-05-10T10:06:21.687Z","repository":{"id":15094837,"uuid":"17821467","full_name":"sparanoid/chinese-copywriting-guidelines","owner":"sparanoid","description":"Chinese copywriting guidelines for better written communication／中文文案排版指北","archived":false,"fork":false,"pushed_at":"2025-02-09T14:24:33.000Z","size":357,"stargazers_count":14748,"open_issues_count":32,"forks_count":1829,"subscribers_count":246,"default_branch":"master","last_synced_at":"2025-05-10T10:06:16.207Z","etag":null,"topics":["chinese","chinese-simplified","chinese-traditional","copywriting","css","documentation","guideline","leancloud","markdown"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/sparanoid.png","metadata":{"files":{"readme":"README.en.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null},"funding":{"github":null,"patreon":null,"open_collective":null,"ko_fi":null,"tidelift":null,"custom":"https://sparanoid.com/donate/"}},"created_at":"2014-03-17T08:27:16.000Z","updated_at":"2025-05-10T08:06:30.000Z","dependencies_parsed_at":"2025-02-18T13:10:51.417Z","dependency_job_id":"be554ca5-bc27-44b8-a4b3-d82625e3c416","html_url":"https://github.com/sparanoid/chinese-copywriting-guidelines","commit_stats":null,"previous_names":[],"tags_count":13,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sparanoid%2Fchinese-copywriting-guidelines","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sparanoid%2Fchinese-copywriting-guidelines/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sparanoid%2Fchinese-copywriting-guidelines/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/sparanoid%2Fchinese-copywriting-guidelines/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/sparanoid","download_url":"https://codeload.github.com/sparanoid/chinese-copywriting-guidelines/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":253398098,"owners_count":21902036,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["chinese","chinese-simplified","chinese-traditional","copywriting","css","documentation","guideline","leancloud","markdown"],"created_at":"2024-07-31T08:00:19.885Z","updated_at":"2025-05-10T10:06:21.620Z","avatar_url":"https://github.com/sparanoid.png","language":null,"funding_links":["https://sparanoid.com/donate/"],"categories":["miscellaneous","Misc","Others","写作","CoffeeScript","Uncategorized","起步","Typography Stylesheet","其他","Specifications","Others 其他","6. 排版","Popular \u0026 New Non-LaTeX Templates","cli","CoffeeScript (1)","资源"],"sub_categories":["Test","HUD","Uncategorized","Markdown","网络服务_其他","中文","Style Guide 风格指南","Others","collection","指南"],"readme":"# Chinese Copywriting Guidelines\n\nChinese copywriting guidelines for better written communication.\n\nOther languages:\n\n- [English](README.en.md)\n- [Chinese Traditional](README.md)\n- [Chinese Simplified](README.zh-Hans.md)\n\n* * *\n\n## Spacing\n\n\u003e Research shows that, people adding no space between Chinese and English suffer from pathetic relationships. 70% of them are married by the age of 34, with someone they don't love; 30% of them left everything for their cats and died. Blank spaces are essential to both romance and writing.\n\u003e\n\u003e 與大家共勉之。」——[vinta/paranoid-auto-spacing](https://github.com/vinta/pangu.js)\n\n### Place one space before/after English words\n\nGood:\n\n\u003e 在 LeanCloud 上，數據儲存是圍繞 `AVObject` 進行的。\n\nBad:\n\n\u003e 在LeanCloud上，數據儲存是圍繞`AVObject`進行的。\n\u003e\n\u003e 在 LeanCloud上，數據儲存是圍繞`AVObject` 進行的。\n\nAn example of complete and correct usage:\n\n\u003e 在 LeanCloud 上，數據儲存是圍繞 `AVObject` 進行的。每個 `AVObject` 都包含了與 JSON 兼容的 key-value 對應的數據。數據是 schema-free 的，你不需要在每個 `AVObject` 上提前指定存在哪些键，只要直接設定對應的 key-value 即可。\n\nExceptions: For product and brand names, please refer to the writing format of the official definition. For example, use “豆瓣FM” instead of “豆瓣 FM”.\n\n### Place one space before/after numbers\n\nGood:\n\n\u003e 今天出去買菜花了 5000 元。\n\nBad:\n\n\u003e 今天出去買菜花了 5000元。\n\u003e\n\u003e 今天出去買菜花了5000元。\n\n### Place one space between numbers and units\n\nGood:\n\n\u003e 我家的光纖入屋寬頻有 10 Gbps，SSD 一共有 20 TB。\n\nBad:\n\n\u003e 我家的光纖入屋寬頻有 10Gbps，SSD 一共有 20TB。\n\nExceptions: There should not be any spacing between numbers and degrees/percentages.\n\nGood:\n\n\u003e 角度為 90° 的角，就是直角。\n\u003e\n\u003e 新 MacBook Pro 有 15% 的 CPU 性能提升。\n\nBad:\n\n\u003e 角度為 90 ° 的角，就是直角。\n\u003e\n\u003e 新 MacBook Pro 有 15 % 的 CPU 性能提升。\n\n### No additional spaces before/after punctuation in fullwidth form\n\nGood:\n\n\u003e 剛剛買了一部 iPhone，好開心！\n\nBad:\n\n\u003e 剛剛買了一部 iPhone ，好開心！\n\u003e\n\u003e 剛剛買了一部 iPhone， 好開心！\n\n### `text-spacing` to the rescue?\n\n[`text-spacing`](https://www.w3.org/TR/css-text-4/#text-spacing-property) and [`-ms-text-autospace`](https://msdn.microsoft.com/library/ms531164(v=vs.85).aspx) provided by CSS Text Module Level and Microsoft can specify the autospacing and narrow space width adjustment of text. However it's not popular, and on other platforms such as OS X and iOS we can not use this feature. So it's better for you to keep up the habit.\n\n## Punctuation\n\n### Avoid duplicate punctuation\n\nAlthough the punctuation usage of China mainland admits to duplicate the punctuations, the sentence may become unpleasing to the eye by doing that.\n\nGood:\n\n\u003e 德國隊竟然戰勝了巴西隊！\n\u003e\n\u003e 她竟然對你說「喵」？！\n\nBad:\n\n\u003e 德國隊竟然戰勝了巴西隊！！\n\u003e\n\u003e 德國隊竟然戰勝了巴西隊！！！！！！！！\n\u003e\n\u003e 她竟然對你說「喵」？？！！\n\u003e\n\u003e 她竟然對你說「喵」？！？！？？！！\n\n## Fullwidth and halfwidth\n\nIf you’re not familiar with fullwidth and halfwidth forms please refer to article [Halfwidth and fullwidth](https://en.wikipedia.org/wiki/Halfwidth_and_fullwidth_forms) on Wikipedia.\n\n### Use punctuation in fullwidth form\n\nGood:\n\n\u003e 嗨！你知道嘛？今天前台的小妹跟我說「喵」了哎！\n\u003e\n\u003e 核磁共振成像（NMRI）是什麼原理都不知道？JFGI！\n\nBad:\n\n\u003e 嗨! 你知道嘛? 今天前台的小妹跟我說 \"喵\" 了哎!\n\u003e\n\u003e 嗨!你知道嘛?今天前台的小妹跟我說\"喵\"了哎!\n\u003e\n\u003e 核磁共振成像 (NMRI) 是什麼原理都不知道? JFGI!\n\u003e\n\u003e 核磁共振成像(NMRI)是什麼原理都不知道?JFGI!\n\nException: inline English titles of books and journals with italics, instead of fullwidth title marks.\n\n### Use numbers in halfwidth form\n\nGood:\n\n\u003e 這件蛋糕只賣 1000 元。\n\nBad:\n\n\u003e 這件蛋糕只賣 １０００ 元。\n\nExceptions: fullwidth numbers are acceptable for better visual alignment in graphic design.\n\n### Use punctuation in halfwidth form for English sentences\n\nGood:\n\n\u003e 賈伯斯那句話是怎麼說的？「Stay hungry, stay foolish.」\n\u003e\n\u003e 推薦你閱讀 *Hackers \u0026 Painters: Big Ideas from the Computer Age*，非常地有趣。\n\nBad:\n\n\u003e 賈伯斯那句話是怎麼說的？「Stay hungry，stay foolish。」\n\u003e\n\u003e 推薦你閱讀《Hackers＆Painters：Big Ideas from the Computer Age》，非常的有趣。\n\n## Nouns\n\n### Capitalize properly\n\nCapitalization is a matter of English, which is beyond the scope of this wiki. Here we exemplify some typical scenarios.\n\nGood:\n\n\u003e 使用 GitHub 登錄\n\u003e\n\u003e 我們的客戶有 GitHub、Foursquare、Microsoft Corporation、Google、Facebook, Inc.。\n\nBad:\n\n\u003e 使用 github 登錄\n\u003e\n\u003e 使用 GITHUB 登錄\n\u003e\n\u003e 使用 Github 登錄\n\u003e\n\u003e 使用 gitHub 登錄\n\u003e\n\u003e 使用 gｲんĤЦ8 登錄\n\u003e\n\u003e 我們的客戶有 github、foursquare、microsoft corporation、google、facebook, inc.。\n\u003e\n\u003e 我們的客戶有 GITHUB、FOURSQUARE、MICROSOFT CORPORATION、GOOGLE、FACEBOOK, INC.。\n\u003e\n\u003e 我們的客戶有 Github、FourSquare、MicroSoft Corporation、Google、FaceBook, Inc.。\n\u003e\n\u003e 我們的客戶有 gitHub、fourSquare、microSoft Corporation、google、faceBook, Inc.。\n\u003e\n\u003e 我們的客戶有 gｲんĤЦ8、ｷouЯƧquﾑгє、๓เςг๏ร๏Ŧt ς๏гק๏гคtเ๏ภn、900913、ƒ4ᄃëв๏๏к, IПᄃ.。\n\n注意：當網頁中需要配合整體視覺風格而出現全部大寫／小寫的情形，HTML 中請使用標準的大小寫規範進行書寫；並通過 `text-transform: uppercase;`／`text-transform: lowercase;` 對表現形式進行定義。\n\n### Avoid jargons\n\nGood:\n\n\u003e 我們需要一位熟悉 TypeScript、HTML5，至少理解一種框架（如 React、Next.js）的前端開發者。\n\nBad:\n\n\u003e 我們需要一位熟悉 Ts、h5，至少理解一種框架（如 RJS、nextjs）的 FED。\n\n## Dispute\n\nThe following usages comprise of personal characteristics. As such, from the perspective of copywriting guidelines, they are **still correct** regardless of whether they comply with the following rules.\n\n### Add extra spaces before/after links\n\nUsage:\n\n\u003e 請 [提交一个 issue](#) 並分配给相關同事。\n\u003e\n\u003e 訪問我們網站的最新動態，請 [點擊這裡](#) 進行訂閱！\n\ncompared with:\n\n\u003e 請[提交一个 issue](#) 並分配给相關同事。\n\u003e\n\u003e 訪問我們網站的最新動態，請[點擊這裡](#)進行訂閱！\n\n### Use corner brackets for Chinese Simplified\n\nUsage:\n\n\u003e 「老师，『有条不紊』的『紊』是什么意思？」\n\ncompared with:\n\n\u003e “老师，‘有条不紊’的‘紊’是什么意思？”\n\n## Tools\n\nRepository | Category | Language\n---------- | -------- | --------\n[pangu.js](https://github.com/vinta/pangu.js) | pangu | JavaScript\n[pangu-go](https://github.com/vinta/pangu) | pangu | Go\n[pangu.java](https://github.com/vinta/pangu.java) | pangu | Java\n[pangu.py](https://github.com/vinta/pangu.py) | pangu | Python\n[pangu.rb](https://github.com/dlackty/pangu.rb) | pangu | Ruby\n[pangu.php](https://github.com/cchlorine/pangu.php) | pangu | PHP\n[pangu.vim](https://github.com/hotoo/pangu.vim) | pangu | Vim\n[vue-pangu](https://github.com/serkodev/vue-pangu) | pangu | Vue.js (Web Converter)\n[intellij-pangu](https://plugins.jetbrains.com/plugin/19665-pangu) | pangu | Intellij Platform Plugin\n[autocorrect](https://github.com/huacnlee/autocorrect) | autocorrect | Rust, WASM, CLI tool\n[autocorrect-node](https://github.com/huacnlee/autocorrect/tree/main/autocorrect-node) | autocorrect | Node.js\n[autocorrect-py](https://github.com/huacnlee/autocorrect/tree/main/autocorrect-py) | autocorrect | Python\n[autocorrect-rb](https://github.com/huacnlee/autocorrect/tree/main/autocorrect-rb) | autocorrect | Ruby\n[autocorrect-java](https://github.com/huacnlee/autocorrect/tree/main/autocorrect-java) | autocorrect | Java\n[autocorrect-go](https://github.com/longbridgeapp/autocorrect) | autocorrect | Go\n[autocorrect-php](https://github.com/NauxLiu/auto-correct) | autocorrect | PHP\n[autocorrect-vscode](https://marketplace.visualstudio.com/items?itemName=huacnlee.autocorrect) | autocorrect | VS Code Extension\n[autocorrect-idea-plugin](https://plugins.jetbrains.com/plugin/20244-autocorrect) | autocorrect | Intellij Platform Plugin\n[jxlwqq/chinese-typesetting](https://github.com/jxlwqq/chinese-typesetting) | other | PHP\n[sparanoid/space-lover](https://github.com/sparanoid/space-lover) | other | PHP (WordPress)\n[sparanoid/grunt-auto-spacing](https://github.com/sparanoid/grunt-auto-spacing) | other | Node.js (Grunt)\n[hjiang/scripts/add-space-between-latin-and-cjk](https://github.com/hjiang/scripts/blob/master/add-space-between-latin-and-cjk) | other | Python\n[hustcc/hint](https://github.com/hustcc/hint) | other | Python\n[n0vad3v/Tekorrect](https://github.com/n0vad3v/Tekorrect) | other | Python\n\n## Examples of “Who is doing this?”\n\nWebsite | Copywriting | UGC\n------- | ----------- | ---\n[Apple China](https://www.apple.com/cn/) | Yes | N/A\n[Apple Hong Kong](https://www.apple.com/hk/) | Yes | N/A\n[Apple Taiwan](https://www.apple.com/tw/) | Yes | N/A\n[Microsoft China](https://www.microsoft.com/zh-cn/) | Yes | N/A\n[Microsoft Hong Kong](https://www.microsoft.com/zh-hk/) | Yes | N/A\n[Microsoft Taiwan](https://www.microsoft.com/zh-tw/) | Yes | N/A\n[LeanCloud](https://leancloud.cn/) | Yes | N/A\n[V2EX](https://www.v2ex.com/) | Yes | Yes\n[Apple4us](https://apple4us.com/) | Yes | N/A\n[Ruby China](https://ruby-china.org/) | Yes | Yes\n[少數派](https://sspai.com/) | Yes | N/A\n\n## References\n\n- [Guidelines for Using Capital Letters - ThoughtCo.](https://www.thoughtco.com/guidelines-for-using-capital-letters-1691724)\n- [Letter case - Wikipedia](https://en.wikipedia.org/wiki/Letter_case)\n- [Punctuation - Oxford Dictionaries](https://en.oxforddictionaries.com/grammar/punctuation)\n- [Punctuation - The Purdue OWL](https://owl.english.purdue.edu/owl/section/1/6/)\n- [How to Use English Punctuation Correctly - wikiHow](https://www.wikihow.com/Use-English-Punctuation-Correctly)\n- [格式 - openSUSE](https://zh.opensuse.org/index.php?title=Help:%E6%A0%BC%E5%BC%8F)\n- [Halfwidth and fullwidth forms - Wikipedia](https://en.wikipedia.org/wiki/Halfwidth_and_fullwidth_forms)\n- [引號 - 維基百科](https://zh.wikipedia.org/wiki/%E5%BC%95%E8%99%9F)\n- [Interrobang - Wikipedia](https://en.wikipedia.org/wiki/Interrobang)\n\n## Forks\n\nThe usage of forked projects may differ from this project.\n\n- [mzlogin/chinese-copywriting-guidelines](https://github.com/mzlogin/chinese-copywriting-guidelines)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsparanoid%2Fchinese-copywriting-guidelines","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsparanoid%2Fchinese-copywriting-guidelines","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsparanoid%2Fchinese-copywriting-guidelines/lists"}