Translation Day 2 日本語訳 - WordBench Nagoya 2016年11月
•Transferir como PPTX, PDF•
1 gostou•609 visualizações
This slide was originally made by Petya Raykovska from WordPress Polygots Team and translated into Japanese, added some workshop notes that we did at WordBench Nagoya on Nov. Thank you Petya. 11月のWordBench名古屋は「Global WordPress Translation Day２」として開催しました。 11月12日は、世界各地で一斉にWordPressに関する翻訳作業や多言語化について取り組む日です。 日本では東京・大阪・福岡・男木島（香川）などでも行われます。 プラグインやテーマ、WordPressに関する情報を日本語に訳すのにチャレンジ。WordPressそのものへの理解が深まりステップアップするチャンスです。 このスライドは、Translation Day を企画した、ブルガリア在住で、イギリスの超有名 WordPress 系のウェブ開発会社 Human Made という会社に在籍されている Petya (ペティア) さんが作成したスライドに日本語翻訳と WordBench 名古屋の勉強会の内容を追加したものです。
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (14)
Mais de Katz Ueno
Mais de Katz Ueno (20)
Translation Day 2 日本語訳 - WordBench Nagoya 2016年11月
- 1. Petya Raykovska#WPTranslationDay W O R D B E N C H N A G O Y A 2 0 1 6 . 1 1 T R A N S L A T I O N D A Y S B Y K A T Z U E N O ( W P : K A T Z 5 1 5 T W : K A T Z U E N O )
- 2. Petya Raykovska#WPTranslationDay T R A N S L A T I O N D A Y S 1 4 : 0 0 - W O R D P R E S S 翻 訳 1 4 : 3 0 - デ モ : W O R D P R E S S . O R G T R A N S L A T I O N . W O R D P R E S S . O R G で の 紹 介 1 5 : 0 0 - ワ ー ク シ ョ ッ プ
- 3. Petya Raykovska#WPTranslationDay M A K I N G W O R D P R E S S G L O B A L I N T R O D U C T I O N T O WordPress をグローバルに Japanese translated (日本語翻訳) by Katz Ueno (katz515)
- 4. Petya Raykovska#WPTranslationDay W O R D P R E S S T R A N S L A T I O N D A Y ! H A P P Y WordPress トランスレーションデー！
- 5. Petya Raykovska#WPTranslationDay L E A R N H O W T O T R A N S L A T E G O A L S F O R T O D A Y : E V E R Y O N E 今日のゴール：みんなで翻訳を学ぼう
- 6. Petya Raykovska#WPTranslationDay L E A R N H O W T O M A K E S O F T W A R E R E A D Y F O R T R A N S L A T I O N G O A L S F O R T O D A Y : D E V E L O P E R S 今日の開発者のゴール： （テーマやプラグインを）翻訳可能にしよう
- 7. Petya Raykovska#WPTranslationDay M E E T A M A Z I N G P E O P L E G O A L S F O R T O D A Y 今日のゴール： 素晴らしい人々と出会おう
- 8. Petya Raykovska#WPTranslationDay H A V E F U N W H I L E M A K I N G T H E W E B A B E T T E R P L A C E G O A L S F O R T O D A Y 今日のゴール： Web をよりよい環境に導こう
- 9. Petya Raykovska#WPTranslationDay L 1 0 N L O C A L I S A T I O N = T R A N S L A T E T E R M S W E ’ R E U S I N G 用語の解説： L10N = Localization の略 = 翻訳
- 10. Petya Raykovska#WPTranslationDay I 1 8 N I N T E R N A T I O N A L I S A T I O N = T R A N S L A T I O N R E A D Y D E V E L O P M E N T T E R M S W E ’ R E U S I N G 用語の解説： I18N = Internationalization の略 = 翻訳可能な状態にすること
- 11. Petya Raykovska#WPTranslationDay L O C A L E = L A N G U A G E + P L A C E + T E X T D I R E C T I O N + D A T E S , N U M B E R S , C U R R E N C Y … T H E T E R M S W E N E E D T O K N O W 用語の解説： LOCALE = 言語+場所+方向+日付+数字+通貨…
- 12. Petya Raykovska#WPTranslationDay 1 6 2 L O C A L E S A V A I L A B L E
- 15. Petya Raykovska#WPTranslationDay L O C A L I S E D D O W N L O A D S U N T I L 2 0 1 4
- 16. @petyeah#WPTranslationDay 7,196,847 6,538,463 T O T A L D O W N L O A D S O F W O R D P R E S S 4 . 0
- 17. Petya Raykovska#WPTranslationDay 1 6 2 L O C A L E S
- 18. Petya Raykovska#WPTranslationDay 5 5 L O C A L E S A T 1 0 0 %
- 19. Petya Raykovska#WPTranslationDay 1 2 L O C A L E S A T M O R E T H A N 9 0 %
- 20. Petya Raykovska#WPTranslationDay 2 3 L O C A L E S A T M O R E T H A N 5 0 %
- 21. Petya Raykovska#WPTranslationDay 6 2 L O C A L E S A T L E S S T H A N 5 0 %
- 22. Petya Raykovska#WPTranslationDay W O R D P R E S S A T 1 0 0 % T O P 1 0 0 P L U G I N S A N D T H E M E S A T 1 0 0 % O U R N E X T T A R G E T : 次の目標： WordPress コアを翻訳 100% の状態を保つこと Top 100 のプラグインやテーマの 100% 翻訳
- 23. Petya Raykovska#WPTranslationDay 3 0 0 0 0 P L U G I N S 7 0 0 0 T H E M E S T H E N E W C H A L L E N G E :
- 24. Petya Raykovska#WPTranslationDay W O R D P R E S S 専 用 の 翻 訳 プ ラ ッ ト フ ォ ー ム T R A N S L A T E . W O R D P R E S S . O R G 翻 訳 の 流 れ
- 25. Petya Raykovska#WPTranslationDay T R A N S L A T E . W O R D P R E S S . O R G
- 26. Petya Raykovska#WPTranslationDay S T E P 1 : 翻 訳 T R A N S L A T E . W O R D P R E S S . O R G 翻 訳 の 流 れ
- 28. Petya Raykovska#WPTranslationDay S T E P 2 : 翻 訳 レ ビ ュ ー T R A N S L A T E . W O R D P R E S S . O R G 翻 訳 の 流 れ
- 29. Petya Raykovska#WPTranslationDay S T E P 3 : リ リ ー ス L O C A L . W O R D P R E S S . O R G 翻 訳 の 流 れ ※ 各ロケール(日本語だと ja.wordpress.org)
- 30. Petya Raykovska#WPTranslationDay S T E P 3 : リ リ ー ス 自 動 リ リ ー ス H O W D O E S I T W O R K ?
- 31. Petya Raykovska#WPTranslationDay 言 語 パ ッ ク ユ ー ザ ー の 操 作 が 何 も 要 ら な い 自 動 翻 訳 ア ッ プ デ ー ト 翻 訳 の 流 れ
- 32. Petya Raykovska#WPTranslationDay イ ン ス ト ー ル 時 に 言 語 を 選 択
- 33. Petya Raykovska#WPTranslationDay 管 理 画 面 で 言 語 を 選 択
- 34. Petya Raykovska#WPTranslationDay バ ー ジ ョ ン を ダ ウ ン ロ ー ド 多 言 語 済 み の
- 35. Petya Raykovska#WPTranslationDay W P - M U L T I B Y T E P A T C H 日 本 語 独 自 の 注 意
- 37. Petya Raykovska#WPTranslationDay W P M U L T I B Y T E P A T C H の 主 な 機 能 •文 字 数 カ ウ ン ト の 日 本 語 対 応 検 索 の 全 角 ス ペ ー ス 対 応 メ ー ル 送 信 の 文 字 化 け 対 応 日 本 語 フ ァ イ ル 名 の ア ッ プ ロ ー ド 対 応 R S S フ ィ ー ド の 文 字 化 け エ ラ ー 対 応 公 式 テ ー マ T W E N T Y X X X の W E B フ ォ ン ト 無 効 化
- 38. Petya Raykovska#WPTranslationDay 自 動 ア ッ プ デ ー ト ユ ー ザ ー の 操 作 が 一 切 い ら な い シ ス テ ム 翻 訳 の 流 れ
- 39. Petya Raykovska#WPTranslationDay W O R D P R E S S P O L Y G L O T S チ ー ム の 紹 介 誰 が 作 っ て る の ？
- 40. THE POLYGLOTS 5000名以上の ボランティア。 WordPress を160 言語以上に翻訳
- 42. THE POLYGLOTS 日 本 語 も も ち ろ ん あ り ま す M A K E . W O R D P R E S S . O R G / P O L Y G O T S / T E A M S
- 44. コ ミ ュ ニ ケ ー シ ョ ン ツ ー ル 400+ EDITORS
- 45. Petya Raykovska#WPTranslationDay C H A T . W O R D P R E S S . O R G W O R D P R E S S S L A C K ( ス ラ ッ ク )
- 46. Petya Raykovska#WPTranslationDay 3 0 0 0 0 P L U G I N S 7 0 0 0 T H E M E S T H E N E W C H A L L E N G E :
- 48. Petya Raykovska#WPTranslationDay U P D A T E S N O T I F I C A T I O N S
- 49. Petya Raykovska#WPTranslationDay W P J A . S L A C K . C O M 日 本 語 S L A C K
- 50. Petya Raykovska#WPTranslationDay 3 0 0 0 0 P L U G I N S 7 0 0 0 T H E M E S T H E N E W C H A L L E N G E :
- 52. C O M M U N I C A T I O N T O O L S 400+ EDITORS Blogs
- 54. C O M M U N I C A T I O N T O O L S 400+ EDITORS Local content
- 57. Petya Raykovska#WPTranslationDay す べ て を 翻 訳 し よ う ！ 新 し い チ ャ レ ン ジ
- 58. Petya Raykovska#WPTranslationDay 3 0 0 0 0 P L U G I N S 7 0 0 0 T H E M E S T H E N E W C H A L L E N G E :
- 59. Petya Raykovska#WPTranslationDay 翻 訳 し よ う 3 0 , 0 0 0 プ ラ グ イ ン 7 , 0 0 0 テ ー マ 新 チ ャ レ ン ジ ：
- 60. Petya Raykovska#WPTranslationDay 3 0 0 0 0 P L U G I N S 7 0 0 0 T H E M E S T H E N E W C H A L L E N G E :
- 61. Petya Raykovska#WPTranslationDay W O R D P R E S S を 翻 訳 し よ う ！ 翻 訳 チ ュ ー ト リ ア ル
- 62. Petya Raykovska#WPTranslationDay S T E P 1 : ア カ ウ ン ト 作 成 L O G I N . W O R D P R E S S . O R G 翻 訳 チ ュ ー ト リ ア ル
- 63. Petya Raykovska#WPTranslationDay S T E P 2 : 翻 訳 サ イ ト に 訪 問 T R A N S L A T E . W O R D P R E S S . O R G 翻 訳 チ ュ ー ト リ ア ル
- 64. Petya Raykovska#WPTranslationDay S T E P 3 : 翻 訳 開 始 ! T R A N S L A T E . W O R D P R E S S . O R G 翻 訳 チ ュ ー ト リ ア ル
- 65. 翻 訳 ツ ー ル 400+ EDITORS G L O T P R E S S . O R G
- 67. Petya Raykovska#WPTranslationDay T R A N S L A T E . W O R D P R E S S . O R G / L O C A L E / J A 翻 訳 先
- 68. Petya Raykovska#WPTranslationDay 3 0 0 0 0 P L U G I N S 7 0 0 0 T H E M E S T H E N E W C H A L L E N G E :
- 70. Petya Raykovska#WPTranslationDay 翻 訳 リ ソ ー ス 翻 訳 チ ュ ー ト リ ア ル
- 71. Petya Raykovska#WPTranslationDay T H E T R A N S L A T O R H A N D B O O K M A K E . W O R D P R E S S . O R G / P O L Y G L O T S / H A N D B O O K / 翻 訳 チ ュ ー ト リ ア ル
- 72. Petya Raykovska#WPTranslationDay 日 本 語 C O D E X : W O R D P R E S S の 翻 訳W P D O C S . O S D N . J P / W O R D P R E S S _ の 翻 訳 翻 訳 チ ュ ー ト リ ア ル
- 73. Petya Raykovska#WPTranslationDay 日 本 語 チ ー ム M A K E . W O R D P R E S S . O R G / P O L Y G L O T S / T E A M S / ? L O C A L E = J A 翻 訳 チ ュ ー ト リ ア ル
- 74. Petya Raykovska#WPTranslationDay チ ー ム 参 加 の リ ク エ ス ト を し よ う 翻 訳 チ ュ ー ト リ ア ル
- 75. Petya Raykovska#WPTranslationDay 現 在 の 翻 訳 エ デ ィ タ に 連 絡 ( S L A C K や フ ォ ー ラ ム ) S T E P 1
- 77. Petya Raykovska#WPTranslationDay エ デ ィ タ が 忙 し か っ た ら チ ー ム リ ー ダ ー に 連 絡 M A K E . W O R D P R E S S . O R G / P O L Y G L T O S S T E P 2
- 78. Petya Raykovska#WPTranslationDay P O L Y G L O T S チ ー ム リ ー ダ ー が 翻 訳 エ デ ィ タ に コ ン タ ク ト を 取 り 、 翻 訳 エ デ ィ タ に 追 加 し て も ら い ま す S T E P 3
- 79. Petya Raykovska#WPTranslationDay み ん な ボ ラ ン テ ィ ア で や っ て い る の で 首 を 長 く し て お 待 ち 下 さ い ち ょ っ と 時 間 が か か る か も
- 80. Petya Raykovska#WPTranslationDay 自 分 の 言 語 の チ ー ム が な い 場 合 H T T P S : / / M A K E . W O R D P R E S S . O R G / P O L Y G L O T S / T E A M S / 翻 訳 チ ュ ー ト リ ア ル
- 81. Petya Raykovska#WPTranslationDay 新 L O C A L E を リ ク エ ス ト し よ う M A K E . W O R D P R E S S . O R G / P O L Y G L O T S 翻 訳 チ ュ ー ト リ ア ル
- 82. Petya Raykovska#WPTranslationDay L O C A L チ ー ム 役 割 と 権 限 翻 訳 チ ュ ー ト リ ア ル
- 83. R O L E S A N D C A P A B I L I T I E S • General Translation Editor (一般翻訳エディタ) - そのロケールの責任者 。翻訳者の追加・承認や、新しいエディタやプロジェクト翻訳編集者 の追加・承認の権限を持つ • Project Translation Editor (プロジェクト翻訳エディタ) - 一つのプロジ ェクトの責任者 (テーマやプラグイン)。翻訳者を追加・承認。 • Translation Contributor (翻訳コントリビュータ) - プロジェクトへ翻訳 の提案ができる
- 84. Petya Raykovska#WPTranslationDay 自 分 の 言 語 の 用 語 集 や ス タ イ ル ガ イ ド H T T P S : / / M A K E . W O R D P R E S S . O R G / P O L Y G L O T S / H A N D B O O K / T O O L S / L I S T - O F - G L O S S A R I E S - P E R - L O C A L E / 翻 訳 チ ュ ー ト リ ア ル 日 本 語 用 語 集 ス タ イ ル ガ イ ド 翻 訳 の は じ め 方
- 85. Petya Raykovska#WPTranslationDay 翻 訳 者 に 求 め る こ と 翻 訳 の 仕 様
- 86. 翻 訳 者 に 求 め る こ と • 適当なリンクを入れない • 翻訳は直訳よりも、自然な翻訳に • トーンは原文と同じくらいの丁寧さ (カジュアルであればカジュ アルな表現に） • 方言や一部の人にしかわからない専門用語は使わない • 他の翻訳を参考に • 一定のレベルを保つ
- 87. よ く あ る 間 違 い • 翻訳ではなく直訳すぎる (plugins, themes) • マークアップを削除してしまう （「s%」に注意） • Google Translateに頼りすぎる • 自分が十分理解できないことを翻訳する • 翻訳者のコメントを無視する • 翻訳の文脈を無視する
- 88. よ く あ る 間 違 い • 実際の WordPress で動作確認しない
- 89. Petya Raykovska#WPTranslationDay 品 質 を 高 め よ う 首 尾 一 貫 し よ う 翻 訳 チ ュ ー ト リ ア ル
- 90. Petya Raykovska#WPTranslationDay 用 語 集 や 、 ス タ イ ル ガ イ ド の 更 新 に 協 力 を お 願 い し ま す 重 要 な ル ー ル
- 91. Petya Raykovska#WPTranslationDay 新 し い ル ー ル を 作 り た い ？ 作 れ ま す ！ 重 要 な ル ー ル
- 92. Petya Raykovska#WPTranslationDay L E T ’ S T R A N S L A T E ! T R A N S L A T E : G E T S T A R T E D
- 93. Petya Raykovska#WPTranslationDay F O R G O T E V E R Y T H I N G I S A I D ? T R A N S L A T E : G E T S T A R T E D C L I C K H E R E : H T T P S : / / M A K E . W O R D P R E S S . O R G / P O L Y G L O T S / H A N D B O O K / A B O U T / G E T - I N V O L V E D / G E T T I N G - S T A R T E D - A T - A - C O N T R I B U T O R - D A Y /
- 94. Petya Raykovska#WPTranslationDay T R A N S L A T E . W O R D P R E S S . O R G L E T ’ S T R A N S L A T E
- 95. Petya Raykovska#WPTranslationDay H A V E F U N T O D A Y !
- 96. Petya Raykovska#WPTranslationDay 自 分 で 翻 訳 し た フ ァ イ ル を 試 そ う P O E D I T を 使 う H T T P S : / / P O E D I T . N E T / W O R D P R E S S で 試 そ う
- 97. Petya Raykovska#WPTranslationDay T R A N S L A T E . W O R D P R E S S . O R G か ら 翻 訳 フ ァ イ ル を ダ ウ ン ロ ー ド P O E D I T で 翻 訳
- 98. Petya Raykovska#WPTranslationDay P O E D I T で 翻 訳 し て み る デ モ で 紹 介 し ま す W O R D P R E S S で 試 そ う
- 99. Petya Raykovska#WPTranslationDay T R A N S L A T E . W O R D P R E S S . O R G か ら M O フ ァ イ ル を ダ ウ ン ロ ー ド W O R D P R E S S で 試 そ う
- 100. Petya Raykovska#WPTranslationDay T R A N S L A T E . W O R D P R E S S . O R G か ら M O フ ァ イ ル を ダ ウ ン ロ ー ド W O R D P R E S S で 試 そ う
- 101. Petya Raykovska#WPTranslationDay T R A N S L A T E . W O R D P R E S S . O R G か ら W O R D P R E S S に 実 装 W O R D P R E S S で 試 そ う
- 102. Petya Raykovska#WPTranslationDay T R A N S L A T E . W O R D P R E S S . O R G か ら W O R D P R E S S に 実 装 W O R D P R E S S で 試 そ う 「languages」フォルダの 中に mo ファイルを入れる
- 103. Petya Raykovska#WPTranslationDay プ ラ グ イ ン 作 者 に 多 言 語 対 応 し て も ら お う ！ プ ラ グ イ ン 多 言 語 化 H T T P S : / / D E V E L O P E R . W O R D P R E S S . O R G / P L U G I N S / I N T E R N A T I O N A L I Z A T I O N / L O C A L I Z A T I O N / テ ー マ 多 言 語 化 H T T P S : / / D E V E L O P E R . W O R D P R E S S . O R G / T H E M E S / F U N C T I O N A L I T Y / I N T E R N A T I O N A L I Z A T I O N / 多 言 語 対 応 し て い な い プ ラ グ イ ン は ？
- 104. Petya Raykovska#WPTranslationDay ワ ー ク シ ョ ッ プ W O R D P R E S S T R A N S L A T I O N D A Y
- 105. Petya Raykovska#WPTranslationDay 4 つ の グ ル ー プ に 別 れ ま す - W O R D P R E S S コ ア ( 4 . 7 ) - プ ラ グ イ ン - テ ー マ - 開 発 者 向 け ワ ー ク シ ョ ッ プ
Notas do Editor
- Internationalization means creating software that is translation ready software. In other words internationalisation means preparing the things you build for localization.
- From a geographic perspective, a locale is a place. From a software perspective, a locale is an ID used to select information associated with a a language and/or a place. Locale information includes the name and identifier of the spoken language, sorting and collating requirements, currency usage, numeric display preferences, and text direction (left-to-right or right-to-left, horizontal or vertical).
- The answer is “A lot” WordPress speaks more than 100 languages and is learning new languages every day. It has 156 locales and new one are being requested almost every week. From those 156, 67 are fully translated and another 20 are partially translated and can still be used. Including two different versions of Swiss German & a separate locale for Romansch.
- Going into it's 12th year of existence, WordPress is growing extremely fast. In just four years it managed to grow by almost 10% and a huge part of this growth the software owes to the very smart way it approaches internationalization.
- Your local community may be well established and organised like the German, French and Portuguese one. It can be filled with bubbling enthusiasts like the Bulgarian one or it can be a single person, like the turkish one. Install WordPress in your own language and test the translations. There’s always room for improvement
- For 4.0 locale downloads surpassed english downloads
- 162 locales. 55 locales at 100%. 4 locales have more than 95%. 8 locales have more than 90%. 23 locales have more than 50%. 62 locales have less than 50%.
- 162 locales. 55 locales at 100%. 4 locales have more than 95%. 8 locales have more than 90%. 23 locales have more than 50%. 62 locales have less than 50%.
- 162 locales. 55 locales at 100%. 4 locales have more than 95%. 8 locales have more than 90%. 23 locales have more than 50%. 62 locales have less than 50%.
- If your locale is not at 100%, you can only leave WordPress as your next target. If it’s already translated, our global target for 2016 is the top 100 plugins and themes (by number of downloads). That answers the question “Which projects should I start to translate?” that many contributors will be asking themselves.
- Find your local validators and ask what they need help with and how you can start
- Everyone with a WordPress.org username can translate You can translate WordPress, default themes, core plugins (import plugins, etc) You can suggest changes to existing translations and correct mistakes
- Everyone with a WordPress.org username can translate You can translate WordPress, default themes, core plugins (import plugins, etc) You can suggest changes to existing translations and correct mistakes
- GlotPress How does it work - Everyone can translate A trusted group of people can validate the translations that actually go in If your language doesn’t have a validator you can become one!
- Everyone with a WordPress.org username can translate You can translate WordPress, default themes, core plugins (import plugins, etc) You can suggest changes to existing translations and correct mistakes
- Everyone with a WordPress.org username can translate You can translate WordPress, default themes, core plugins (import plugins, etc) You can suggest changes to existing translations and correct mistakes
- Everyone with a WordPress.org username can translate You can translate WordPress, default themes, core plugins (import plugins, etc) You can suggest changes to existing translations and correct mistakes
- Everyone with a WordPress.org username can translate You can translate WordPress, default themes, core plugins (import plugins, etc) You can suggest changes to existing translations and correct mistakes
- UI
- UI
- Your local community may be well established and organised like the German, French and Portuguese one. It can be filled with bubbling enthusiasts like the Bulgarian one or it can be a single person, like the turkish one. Install WordPress in your own language and test the translations. There’s always room for improvement
- Everyone with a WordPress.org username can translate You can translate WordPress, default themes, core plugins (import plugins, etc) You can suggest changes to existing translations and correct mistakes
- Everyone with a WordPress.org username can translate You can translate WordPress, default themes, core plugins (import plugins, etc) You can suggest changes to existing translations and correct mistakes
- The polyglots community consists of locals, people who speak and use the language every day in it’s native environment in a local context. What’s even more important is that a lot of those people are not developers. And that’s important, because developers are not known for their excellent text representation skills. Developers like logic and usually translate literally. They usually don’t use software in their language, they use English, so when they translate for English, they usually make a huge mess for everyone else. Whenever I try to explain why non devs need to be involved localisation process, I like to give as an example a couple of localisation fails by big brands who thought literal translation was the way to go.
- The polyglots community consists of locals, people who speak and use the language every day in it’s native environment in a local context. What’s even more important is that a lot of those people are not developers. And that’s important, because developers are not known for their excellent text representation skills. Developers like logic and usually translate literally. They usually don’t use software in their language, they use English, so when they translate for English, they usually make a huge mess for everyone else. Whenever I try to explain why non devs need to be involved localisation process, I like to give as an example a couple of localisation fails by big brands who thought literal translation was the way to go.
- Your local community may be well established and organised like the German, French and Portuguese one. It can be filled with bubbling enthusiasts like the Bulgarian one or it can be a single person, like the turkish one. Install WordPress in your own language and test the translations. There’s always room for improvement
- Find your local validators and ask what they need help with and how you can start
- Find your local validators and ask what they need help with and how you can start
- Your local community may be well established and organised like the German, French and Portuguese one. It can be filled with bubbling enthusiasts like the Bulgarian one or it can be a single person, like the turkish one. Install WordPress in your own language and test the translations. There’s always room for improvement
- Your local community may be well established and organised like the German, French and Portuguese one. It can be filled with bubbling enthusiasts like the Bulgarian one or it can be a single person, like the turkish one. Install WordPress in your own language and test the translations. There’s always room for improvement
- Find your local validators and ask what they need help with and how you can start
- Find your local validators and ask what they need help with and how you can start
- Your local community may be well established and organised like the German, French and Portuguese one. It can be filled with bubbling enthusiasts like the Bulgarian one or it can be a single person, like the turkish one. Install WordPress in your own language and test the translations. There’s always room for improvement
- Your local community may be well established and organised like the German, French and Portuguese one. It can be filled with bubbling enthusiasts like the Bulgarian one or it can be a single person, like the turkish one. Install WordPress in your own language and test the translations. There’s always room for improvement
- Find your local validators and ask what they need help with and how you can start
- Find your local validators and ask what they need help with and how you can start
- Find your local validators and ask what they need help with and how you can start
- Find your local validators and ask what they need help with and how you can start
- - Before asking for help, get to know the translators handbook
- - Before asking for help, get to know the translators handbook
- - Before asking for help, get to know the translators handbook
- - Before asking for help, get to know the translators handbook
- GlotPress How does it work - Everyone can translate A trusted group of people can validate the translations that actually go in If your language doesn’t have a validator you can become one!
- Find your local validators and ask what they need help with and how you can start
- Find your local validators and ask what they need help with and how you can start
- - Before asking for help, get to know the translators handbook
- - Before asking for help, get to know the translators handbook
- - Before asking for help, get to know the translators handbook
- It needs to have a link to your local team, example: https://make.wordpress.org/polyglots/teams/?locale=bg_BG
- It needs to have a link to your local team, example: https://make.wordpress.org/polyglots/teams/?locale=bg_BG
- First try to use the contact form of your local site (ex. If you’d like to translate in Bulgarian, use the contact form on http://bg.wordpress.org) A quicker way to get in touch is to contact the translation editors directly. On the list of current teams, the “Team” link will lead you to the locale’s page where you will find a list of the current Translation Editors. Look for their Slack names and try to contact them on the WordPress Slack Team in the #Polyglots channel. Some Translation Editors don’t leave contact information on their profiles. If that is the case, go to https://make.wordpress.org/polyglots and write a post, mentioning the translation editors’ username (ex. @petya). In that post, explain you’d like to get involved and ask them to add you as a translation editor. The translation editors should get an email notification because you mentioned them in the post. It’s possible that the team is not inactive, but simply delayed for some reason. Please be patient and give the translation editors at least a week to respond.
- Step 2: Contact a Polyglots team lead. If you don’t hear back from a Translation Editor after a week, contact a Polyglots team lead (again, by posting on make/polyglots) and let them know the steps you’ve taken so far and that you haven’t heard back, or that you have heard back from a Translation Editor and they are no longer working on translating WordPress.
- Step 3: Polyglots team lead contacts current Translation Editor(s). The Polyglots team lead has a way to contact a translation editor and will make a final effort to get in touch with them.
- It needs to have a link to your local team, example: https://make.wordpress.org/polyglots/teams/?locale=bg_BG
- It needs to have a link to your local team, example: https://make.wordpress.org/polyglots/teams/?locale=bg_BG
- Your local style guide and glossary
- Come talk to me, I’ll get you hooked.
- Don’t include random links: The language files for WordPress projects should only contain links to pages found in wordpress.org domains (or other relevant project domains such as bbpress.org) or the translation community’s official documentation. If you need to link to a translated version of the original link, make sure it has a permanent home in one of those places. Don’t translate literally, translate organically: As a translator, you undoubtedly know that each language is unique. Given that, try to avoid composing your translation in the same structure as the original English string, while sounding natural and still conveys the same message. Try to keep the same level of formality (or informality): Exactly what level of formality or informality to use for each message in your target language is something you and your team will have to figure out on your own, but WordPress messages (informational messages in particular) tend to have a politely informal tone in English. Try to accomplish the equivalent in the target language, within your cultural context. Don’t use slang or audience-specific terms: Refrain from using colloquialisms that only a certain group of readers will understand. If the uninitiated blogger were to install WordPress in your language, would they know what the term means? Words like pingback, trackback, and feed are exceptions to this rule; they’re terminology that are typically difficult to translate, and many translators choose to leave in English. Learn from other localizations in your language: To get a feel for things like commonly used terms and formality level, try reading through the translations of other popular software or service. Of course, WordPress has its own tone and feel, so keep that in mind when you’re reading other localizations, but feel free to dig up UI terms and the like to maintain consistency with other software in your language. Keep it consistent: Consistency is one of the most important characteristics of high quality translation. To maintain consistency throughout various WordPress projects, you can use glossary and style guide specific to your language.
- Try and give a couple of examples in each of these use cases. Feel free to add additional slides with mistakes typical for your language. You will be able to showcase most of the mistakes during the demo that follows this slide.
- Try and give a couple of examples in each of these use cases. Feel free to add additional slides with mistakes typical for your language. You will be able to showcase most of the mistakes during the demo that follows this slide.
- Come talk to me, I’ll get you hooked.
- Come talk to me, I’ll get you hooked.
- Come talk to me, I’ll get you hooked.
- Come talk to me, I’ll get you hooked.