[B! Style Guide] makoto15ã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

makoto15 id:makoto15

Style Guideã«é–¢ã™ã‚‹makoto15ã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (6)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

ã€Œè‹±æ–‡ã® grammatical structuresã‚’æ—¥æœ¬èªžè¨³ã«åæ˜ ã™ã‚‹ã€ã¨ã¯ - ITç¿»è¨³è€…ã®ç–‘å•
Microsoftã¯ä»¥å‰ã‹ã‚‰ãƒ©ãƒ³ã‚²ãƒ¼ã‚¸ãƒãƒ¼ã‚¿ãƒ«ã§ã‚¹ã‚¿ã‚¤ãƒ«ã‚¬ã‚¤ãƒ‰ã‚’å…¬é–‹ã—ã¦ã„ã¾ã™ãŒã€ã“ã®ã‚ˆã†ãªãƒšãƒ¼ã‚¸ã‚‚ã‚ã‚‹ã®ã‚’æœ€è¿‘çŸ¥ã‚Šã¾ã—ãŸã€‚ learn.microsoft.com ã‚¹ã‚¿ã‚¤ãƒ«ã‚¬ã‚¤ãƒ‰å…¨ä½“ã‚’èªã‚€æ™‚é–“ã‚’ã‹ã‘ã‚‹ã»ã©ã§ã¯ãªã„ã€çŸæœŸã®ç¿»è¨³ä½œæ¥ã®å ´åˆã®ãŸã‚ã«æœ€é‡è¦ãƒ«ãƒ¼ãƒ«10å€‹ã‚’è¨€èªžã”ã¨ã«æŒ™ã’ã¦ã„ã‚‹ã¨ã®ã“ã¨ãªã®ã§ã€ã•ã£ããæ—¥æœ¬èªžã®Top 10 Tipsã‚’è¦‹ã¦ã¿ã¾ã—ãŸã€‚ learn.microsoft.com 1. Keep the audience in mind 2. Stay true to the structure and intent of the source 3. Be flexible 4. Pick the right term 5. Be aware of expressions and tone 6. Understand basic writing styles 7. Enclos
makoto15 2023/01/03
l10n

Style Guide
ãƒªãƒ³ã‚¯
Google Developer Documentation Style Guideè‡ªåˆ†ç”¨ã¾ã¨ã‚ - Qiita
ãƒ—ãƒãƒ³ãƒ—ãƒˆã‚’è¡¨ã™ã€Œ$ã€ã‚’ã¤ã‘ã‚‹ ä»–ã®ãƒžã‚·ãƒ³ã«sshã—ãŸã¨ããªã©ã¯ãƒ—ãƒãƒ³ãƒ—ãƒˆã‚’å¤‰ãˆã¦ã‚‚è‰¯ã„ å…¥åŠ›ã¨å‡ºåŠ›ã¯å›²ã¿ã‚’åˆ†ã‘ã‚‹ å®Ÿéš›ã®å€¤ã§ç½®ãæ›ãˆã‚‹ã¹ããƒ—ãƒ¬ãƒ¼ã‚¹ãƒ›ãƒ«ãƒ€ã¯<var>ã‚¿ã‚°ã§å›²ã‚€ã€‚ã™ã‚‹ã¨è¦‹ãŸç›®ã¯ã‚¤ã‚¿ãƒªãƒƒã‚¯ã§æ–‡å—è‰²ãŒãƒ”ãƒ³ã‚¯ã«ãªã‚‹ã€‚ OK: cp from to NG: cp <from> <to> NG: cp {from} {to} ãƒ¦ãƒ¼ã‚¶ãƒ¼ãŒå…¥åŠ›ã™ã‚‹æ–‡å—åˆ—ã¯<kbd>ã‚¿ã‚°ã§å›²ã‚€ <code>ã‚¿ã‚°ã®ä½¿ã„æ–¹ ä»¥ä¸‹ã®ã‚‚ã®ã¯<code>ã‚¿ã‚°ã§å›²ã‚€ è¨€èªžã®ã‚ãƒ¼ãƒ¯ãƒ¼ãƒ‰ ã‚¯ãƒ©ã‚¹å ãƒ¡ã‚½ãƒƒãƒ‰åã€é–¢æ•°å XMLã‚„HTMLã®è¦ç´ å å±žæ€§åã¨å€¤ ãƒ•ã‚¡ã‚¤ãƒ«åã‚„ãƒ‘ã‚¹ å±žæ€§ã‚„å€¤ã®å–ã‚Šã†ã‚‹å®šæ•°å€¤ åå‰ç©ºé–“ã®ã‚¨ã‚¤ãƒªã‚¢ã‚¹ HTTPã®å‹•è©ž HTTPã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚³ãƒ¼ãƒ‰ HTTPã®content-typeã®å€¤ ã‚¯ã‚¨ãƒªãƒ¼ãƒ‘ãƒ©ãƒ¡ãƒ¼ã‚¿åã¨ãã®å€¤ ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£å ä»¥ä¸‹ã®ã‚‚ã®ã¯æ™®é€šã®ãƒ•ã‚©ãƒ³ãƒˆã§è¡¨è¨˜ã™ã‚‹ URL ãƒ¡ãƒ¼ãƒ«ã‚¢ãƒ‰ãƒ¬ã‚¹
makoto15 2019/12/04
google

ã‚¹ã‚¿ã‚¤ãƒ«ã‚¬ã‚¤ãƒ‰

Style Guide
ãƒªãƒ³ã‚¯
Highlights Â |Â Google developer documentation style guide Â |Â Google for Developers
Send feedback Highlights Stay organized with collections Save and categorize content based on your preferences. The style guide covers a lot of material, so the following page provides an overview of its most important points. For more information about topics on the page, follow the links. Tone and content Be conversational and friendly without being frivolous. Don't pre-announce anything in docu
makoto15 2019/12/04
google

ã‚¹ã‚¿ã‚¤ãƒ«ã‚¬ã‚¤ãƒ‰

Style Guide
ãƒªãƒ³ã‚¯
https://jp.techcrunch.com/2017/09/08/20170907google-publishes-its-documentation-style-guide-for-developers/
makoto15 2017/09/08
google

ã‚¹ã‚¿ã‚¤ãƒ«ã‚¬ã‚¤ãƒ‰

Style Guide
ãƒªãƒ³ã‚¯
The Chicago Manual of Style, 18th Edition
Find it. Write it. Cite it. The Chicago Manual of Style Online is the venerable, time-tested guide to style, usage, and grammar in an accessible online format. Â¶ It is the indispensable reference for writers, editors, proofreaders, indexers, copywriters, designers, and publishers, informing the editorial canon with sound, definitive advice. Â¶ Over 1.75 million copies sold!
makoto15 2011/05/26
ã‚¹ã‚¿ã‚¤ãƒ«ã‚¬ã‚¤ãƒ‰

Style Guide
ãƒªãƒ³ã‚¯
http://www.globalization-group.com/edge/2010/02/translation-style-guides/
makoto15 2011/03/29
ã‚¹ã‚¿ã‚¤ãƒ«ã‚¬ã‚¤ãƒ‰

Style Guide
ãƒªãƒ³ã‚¯
1