├── .github
├── dependabot.yml
└── workflows
│ └── jekyll.yml
├── .gitignore
├── 404.md
├── Gemfile
├── LICENSE
├── README.md
├── Rakefile
├── _config.yml
├── _data
└── authors.yml
├── _i18n
├── en.yml
├── en
│ └── _posts
│ │ ├── 2017-05-12-introducing-gitlocalize.md
│ │ ├── 2017-08-02-github-marketplace-launch.md
│ │ ├── 2017-09-25-ruby-on-rails-support.md
│ │ ├── 2017-11-27-gitlocalize-webfundamentals.md
│ │ ├── 2019-02-03-gitlocalize-now-part-of-alconost.md
│ │ ├── 2019-05-28-gitlocalize-is-now-free.md
│ │ └── 2020-03-27-badges-filters-and-more.md
├── ja.yml
├── ja
│ └── _posts
│ │ ├── 2017-05-12-introducing-gitlocalize.md
│ │ ├── 2017-08-02-github-marketplace-launch.md
│ │ ├── 2017-09-25-ruby-on-rails-support.md
│ │ └── 2017-11-27-gitlocalize-webfundamentals.md
├── ru.yml
└── ru
│ └── _posts
│ ├── 2019-02-03-gitlocalize-now-part-of-alconost.md
│ ├── 2019-05-28-gitlocalize-is-now-free.md
│ └── 2020-03-27-badges-filters-and-more.md
├── _includes
├── disqus.html
├── footer.html
├── head.html
├── header.html
├── icons.html
└── muut.html
├── _layouts
├── default.html
├── page.html
└── post.html
├── _sass
├── base
│ ├── _global.scss
│ ├── _utility.scss
│ └── _variables.scss
├── external
│ ├── _reset.scss
│ └── _syntax.scss
├── includes
│ ├── _footer.scss
│ └── _header.scss
└── layouts
│ ├── _index.scss
│ └── _posts.scss
├── css
└── main.scss
├── favicon.ico
├── img
├── alconost_gitlocalize.png
├── badge.svg
├── badge_1.png
├── badge_de.svg
├── badge_fr.svg
├── badge_ptbr.svg
├── batch_PR.png
├── diff_management.png
├── filter_1.png
├── filter_2.png
├── flow.png
├── ghm
│ └── main.png
├── gitlocalize-is-free-now.png
├── gitlocalize-is-free.png
├── gitlocalize.png
├── icon.png
├── logo.png
├── ror
│ └── path_rule.png
└── webfundamentals_gitlocalize.png
├── index.html
└── js
├── jquery-3.2.1.min.js
└── katex_init.js
/.github/dependabot.yml:
--------------------------------------------------------------------------------
1 | version: 2
2 | updates:
3 | - package-ecosystem: 'bundler'
4 | directory: '/'
5 | schedule:
6 | interval: 'daily'
--------------------------------------------------------------------------------
/.github/workflows/jekyll.yml:
--------------------------------------------------------------------------------
1 | name: Deploy Jekyll
2 |
3 | on:
4 | push:
5 | branches: [ "main" ]
6 | workflow_dispatch:
7 |
8 | permissions:
9 | contents: read
10 | pages: write
11 | id-token: write
12 |
13 | concurrency:
14 | group: "pages"
15 | cancel-in-progress: true
16 |
17 | jobs:
18 | build:
19 | runs-on: ubuntu-latest
20 | steps:
21 | - uses: actions/checkout@v3
22 | - uses: ruby/setup-ruby@v1
23 | with:
24 | ruby-version: '3.0'
25 | bundler-cache: true
26 | cache-version: 0
27 | - uses: actions/configure-pages@v2
28 | id: pages
29 | - run: bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}"
30 | env:
31 | JEKYLL_ENV: production
32 | - uses: actions/upload-pages-artifact@v1
33 |
34 | deploy:
35 | environment:
36 | name: github-pages
37 | url: ${{ steps.deployment.outputs.page_url }}
38 | runs-on: ubuntu-latest
39 | needs: build
40 | steps:
41 | - uses: actions/deploy-pages@v1
42 | id: deployment
43 |
44 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | .bundle/
2 | .jekyll-cache/
3 | .sass-cache/
4 | _site/
5 | vendor/
6 |
7 | Gemfile.lock
8 |
--------------------------------------------------------------------------------
/404.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | title: "Page not found"
4 | permalink: /404
5 | hide: true
6 | ---
7 | Sorry, the requested page wasn't found on the server.
8 |
--------------------------------------------------------------------------------
/Gemfile:
--------------------------------------------------------------------------------
1 | source "https://rubygems.org"
2 |
3 | gem 'jekyll', '~>4'
4 |
5 | group :jekyll_plugins do
6 | gem 'jekyll-avatar', '~> 0.8'
7 | gem 'jekyll-feed', '~> 0.17'
8 | gem 'jekyll-sitemap', '~> 1.4'
9 | gem 'jekyll-paginate', '~> 1.1'
10 | gem 'jekyll-multiple-languages-plugin', '~> 1.8'
11 | end
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | The MIT License (MIT)
2 |
3 | Copyright (c) 2014 Rohan Chandra
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # GitLocalize blog
2 |
3 | ## Get started
4 |
5 | ```sh
6 | bundle install
7 | rake prepare
8 | ```
9 |
10 | ## Run locally
11 |
12 | ```sh
13 | rake watch
14 | ```
15 |
16 | ## Deploy
17 |
18 | ```sh
19 | rake deploy
20 | ```
21 |
--------------------------------------------------------------------------------
/Rakefile:
--------------------------------------------------------------------------------
1 | require 'jekyll-gh-pages'
2 |
--------------------------------------------------------------------------------
/_config.yml:
--------------------------------------------------------------------------------
1 | # SITE CONFIGURATION
2 | baseurl: "" # the subpath of your site, e.g. /blog/
3 | url: "http://blog.gitlocalize.com" # the base hostname & protocol for your site
4 |
5 | # THEME-SPECIFIC CONFIGURATION
6 | theme_settings:
7 | # Meta
8 | title: GitLocalize blog
9 | avatar: icon.png
10 | gravatar: # Email MD5 hash
11 | description: "GitLocalize: Continuous localization platform for GitHub repositories" # used by search engines
12 |
13 | # Header and footer text
14 | #header_text: >
15 | #
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
16 |
17 | #
Remove all header text in _config.yml to disable this feature.
18 | #header_text_feature_image:
19 | #footer_text: >
20 | # Powered by Jekyll with Type Theme
21 |
22 | # Icons
23 | rss: true
24 | email_address: "info@gitlocalize.com" # Full email address, e.g. "sam@example.com"
25 | behance:
26 | bitbucket:
27 | dribbble:
28 | facebook: gitlocalize
29 | flickr:
30 | github: gitlocalize
31 | google_plus:
32 | instagram:
33 | linkedin: # Full URL
34 | pinterest:
35 | reddit:
36 | soundcloud:
37 | stack_exchange: # Full URL
38 | steam:
39 | tumblr:
40 | twitter: gitlocalize
41 | wordpress:
42 | youtube:
43 |
44 | # Scripts
45 | google_analytics: "UA-79830225-4"
46 | disqus_shortname:
47 | muut_community_name: # From muut.com settings, e.g. "muttcommunityname"
48 | katex: true # Enable if using math markup
49 |
50 | # Localization strings
51 | str_follow_on: "Follow on"
52 | str_rss_follow: "Follow RSS feed"
53 | str_email: "Email"
54 | str_next: "Next"
55 | str_prev: "Prev"
56 | str_continue_reading: "Read More ↗"
57 |
58 | # Colours, typography and padding
59 | # Open the "_sass > base" folder, and open "_variables.scss"
60 | google_fonts: "Source+Sans+Pro:300,400,700,700italic,400italic"
61 |
62 | # Post navigation
63 | post_navigation: false
64 |
65 | # PAGINATION
66 | paginate: 5
67 | paginate_path: "page:num"
68 |
69 | # BUILD SETTINGS
70 | markdown: kramdown
71 | highlighter: rouge
72 | sass:
73 | sass_dir: _sass
74 | style: :compressed
75 | plugins:
76 | - jekyll-avatar
77 | - jekyll-feed
78 | - jekyll-sitemap
79 | - jekyll-paginate
80 | - jekyll-multiple-languages-plugin
81 | languages: ["en", "ja", "ru"]
82 | permalink: /posts/:categories/:title
83 | future: true
84 |
--------------------------------------------------------------------------------
/_data/authors.yml:
--------------------------------------------------------------------------------
1 | chikathreesix: Ryo Chikazawa
2 | ilyaspiridonov: Ilya Spiridonov
3 |
--------------------------------------------------------------------------------
/_i18n/en.yml:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/gitlocalize/blog/1cfe3e0dba70a90360f1902dbdd65d56fdc9a26a/_i18n/en.yml
--------------------------------------------------------------------------------
/_i18n/en/_posts/2017-05-12-introducing-gitlocalize.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: Introducing GitLocalize, a continuous localization platform for GitHub repository
4 | author: chikathreesix
5 | languages:
6 | - ja
7 | image: gitlocalize.png
8 | ---
9 |
10 | We are excited to announce the beta launch of our new localization platform, [GitLocalize](https://gitlocalize.com)!
11 |
12 | GitLocalize is a continuous localization platform for GitHub repositories and automates the process for developers. Because of the ever-changing nature of Internet-related product, keeping localizing them has been really challenging. GitLocalize solves this by connecting to your GitHub repository and naturally integrating with your development workflow in just a few clicks.
13 |
14 | We started supporting from Markdown files. Try GitLocalize in a minute if you have a documentation project that you want to localize.
15 |
16 |
17 | Get started now with GitHub
18 |
19 |
20 | # How it works
21 |
22 | You can immediately get started with your GitHub account, choose your repository to integrate with GitLocalize and localize your files. Here are the key features of the platform:
23 |
24 | ### GitHub based workflow
25 |
26 | 
27 |
28 | Once you integrate your repo with GitLocalize, it starts pulling all the localization related files into its platform and watching the changes.
29 |
30 | When you finish translating a file, you then make a review request and ask the team to review the changes, like what you do with a pull request.
31 |
32 | After the review process, you can send a pull request back to your repo. It makes each contribution on GitLocalize each user's commit on the repository.
33 |
34 | With GitLocalize, your team no longer need to do anything extra to localize your project and developers only need to look at those pull request coming.
35 |
36 | ### Diff management on translations
37 |
38 | 
39 |
40 | Since it automatically links a translation with its original sentence, it can show you which part needs to be translated when the original one is updated.
41 |
42 | No need to manually check which parts are affected due to the original updated. You just need to look at GitLocalize editor and fill in the missing translations.
43 |
44 | And of course, more features are lined up and will be shipped soon!
45 |
46 | # More details
47 |
48 | Check out the video below to see how it works in more depth!
49 |
50 |
51 |
52 | # Happy localizing!
53 |
54 | We need your feedback to improve and bring the product to create the better future for localization. Please feel free to give us any feedbacks [here](https://gitlocalize.com/inquiries/new). We will respond within a day.
55 |
56 | Also, we have [a Gitter channel](https://gitter.im/gitlocalize/Lobby?utm_source=share-link&utm_medium=link&utm_campaign=share-link) to chat. Feel free to join and jump into the conversation.
57 |
58 | And of course, this blog is localized into [Japanese](http://blog.gitlocalize.com/ja/posts/introducing-gitlocalize.html) with GitLocalize, make a suggestion for the translation from [here](https://gitlocalize.com/repo/80).
59 |
60 | We hope to make your localization far easier and smoother and support your product's global success! Happy localizing!
61 |
--------------------------------------------------------------------------------
/_i18n/en/_posts/2017-08-02-github-marketplace-launch.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: GitLocalize is Now Available on GitHub Marketplace!
4 | author: chikathreesix
5 | languages:
6 | - ja
7 | image: ghm/main.png
8 | ---
9 |
10 | We are excited to announce that we have launched [GitLocalize](https://github.com/marketplace/gitlocalize) on [GitHub Marketplace](https://github.com/marketplace) as the first localization app!
11 |
12 | 
13 |
14 | [GitLocalize](https://gitlocalize.com) is a one of the seven new apps that lauched on [GitHub Marketplace](https://github.com/marketplace) on August 1st and our category [localization](https://github.com/marketplace/category/localization) is the new category on the marketplace!
15 |
16 | GitHub introduces the new apps including [GitLocalize](https://gitlocalize.com) in their official blog post, ["Introducing seven new apps to GitHub Marketplace"](https://github.com/blog/2411-introducing-seven-new-apps-to-github-marketplace). Check out the article to know more about other cool apps on the marketplace.
17 |
18 | Go to our [app page](https://github.com/marketplace/gitlocalize) to find out more and sign up for a free account today!
19 |
--------------------------------------------------------------------------------
/_i18n/en/_posts/2017-09-25-ruby-on-rails-support.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: Localize Your Ruby on Rails App with GitLocalize
4 | author: chikathreesix
5 | languages:
6 | - ja
7 | image: gitlocalize.png
8 | ---
9 |
10 | Struggling to manage your i18n YAML files and the accompanying localization work with Ruby on Rails? Well, we have great news for you. GitLocalize is now here to help you take care of all that tedious Rails i18n work!
11 |
12 | # Get Started
13 |
14 | If you haven't signed up yet, register with GitLocalize for free and get ready to localize your Rails app with zero stress.
15 |
16 |
17 | Get Started for Free
18 |
19 |
20 | Read [our blog article](/posts/introducing-gitlocalize.html) to learn more about how GitLocalize works and what it can do for you.
21 |
22 | # Register Your Rails App
23 |
24 | Navigate to the `Add Repository` page from your profile. Here, you'll see the form to register your GitHub repository with the GitLocalize platform.
25 |
26 | In the middle of the page, specify where your source i18n files are located and where you want to generate translated files.
27 |
28 | For example, let's say that you have source English i18n YAML files at `config/locales/en.yml` and want to have translated ones at `config/locales/ja.yml` or `config/locales/es.yml`. Set the drop-down menu on the left to `File`, then type `config/locales/en.yml` for `Source Path` and `config/locales/%lang%.yml` for `Translation Path`.
29 |
30 | 
31 |
32 | This `%lang%` is a placeholder for the two-character code of your translation target languages. For example, if you're translating to Japanese and Spanish, `ja.yml` and `es.yml` will be generated, respectively.
33 |
34 | If you have multiple i18n files, simply click the `+ Add Rule` button to register more rules.
35 |
36 | # Start Localizing
37 |
38 | Once you submit and add your repository, you can start continuous localization work with your Rails app on GitLocalize.
39 |
40 | Simply go to your repository page from your profile, choose a language, navigate to the YAML file, and open the editor. You're all set!
41 |
42 | Check out the video below or [our docs](http://docs.gitlocalize.com/getting_started.html) to see how the rest of the process works!
43 |
44 |
45 |
--------------------------------------------------------------------------------
/_i18n/en/_posts/2017-11-27-gitlocalize-webfundamentals.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: Google’s Web Fundamentals Is Now Localizing With GitLocalize
4 | author: chikathreesix
5 | languages:
6 | - ja
7 | image: webfundamentals_gitlocalize.png
8 | ---
9 |
10 | 
11 |
12 | We are excited to announce that [Google is now experimenting with GitLocalize](https://developers.google.com/web/resources/translations)! We’re assisting the Web Fundamentals community with localizing their website.
13 |
14 | So far, the Web Fundamentals community has been able to localize the site into 17 languages. But keeping the translations up-to-date has proven to be more than challenging. We believe that GitLocalize is the perfect solution to this problem!
15 |
16 | Join the Web Fundamentals community to localize their vast knowledge of cutting-edge web technology into your language today. Innovation should never get lost in translation.
17 |
18 | [Contribute to the project](https://gitlocalize.com/repo/107)
19 |
--------------------------------------------------------------------------------
/_i18n/en/_posts/2019-02-03-gitlocalize-now-part-of-alconost.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: GitLocalize Is Now Part of Alconost!
4 | author: ilyaspiridonov
5 | languages:
6 | - ru
7 | image: alconost_gitlocalize.png
8 | ---
9 |
10 | 
11 |
12 | ### Good news everyone!
13 |
14 | We are excited to announce that [GitLocalize](https://gitlocalize.com) is now part of [Alconost](https://alconost.com)!
15 |
16 | Alconost Inc. is a U.S.-based Multi-Language Vendor that helps companies around the world with localization of their products and content into 80+ languages. Alconost will use its professional team and expertise in localization to support and improve GitLocalize, and to bring professional language services closer to developers.
17 |
18 | Stay tuned for future updates!
19 |
20 |
21 | Should you have any questions, feel free to [join our community chat](https://gitter.im/gitlocalize/Lobby) or [book a call with us directly](https://calendly.com/is-alconost)!
22 |
--------------------------------------------------------------------------------
/_i18n/en/_posts/2019-05-28-gitlocalize-is-now-free.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: GitLocalize Is Free!
4 | author: ilyaspiridonov
5 | languages:
6 | - ru
7 | image: gitlocalize-is-free-now.png
8 | ---
9 |
10 | 
11 |
12 | We are excited to announce that [GitLocalize](https://gitlocalize.com) is now free for everyone!
13 |
14 | ### Is everything free?
15 | Yes. All the features — the synchronization of repositories, the webhook to keep your projects up-to-date, manual and machine translation into all the supported languages, and teamwork — are available for free.
16 |
17 | ### Is it free for anyone?
18 | Practically. Whether you own OSS or private projects, you can sync them to GitLocalize and translate their documentation, guides and resource strings into all the languages. We intend to keep the platform free for every project, except really huge ones — in such cases we will have to discuss an Enterprise plan with additional technical support from our team.
19 |
20 | ### Is it always going to be free?
21 | Yes, we intend to keep it that way.
22 |
23 | GitLocalize is still far from perfect, and what we need now is as much feedback as possible. Feel free to sign in or sign up with your GitHub account, add a new repo, and start translating right away. Our team will be more than happy to answer any questions — [join the community chat](https://gitter.im/gitlocalize/Lobby) or [book a call](https://calendly.com/is-alconost) to share your experience!
24 |
25 |
26 |
27 |
28 |
--------------------------------------------------------------------------------
/_i18n/en/_posts/2020-03-27-badges-filters-and-more.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: 🚀 Badges, Filters and More
4 | author: ilyaspiridonov
5 | languages:
6 | - ru
7 | ---
8 |
9 |
10 | We've been working hard to make GitLocalize better. Check out the cool features that we've added recently.
11 |
12 | ---
13 |
14 | ### 🔍 Filters
15 |
16 |
17 | Translating updates just got easier. You can now select to display only untranslated strings or only machine translated strings, which is especially important if you’re working with large markdown or json files. Just click on the filter icon in the top right part of the editor
18 |
19 | 
20 |
21 | and select the desired view:
22 |
23 | 
24 |
25 | ---
26 |
27 | ### 🏷 The GitLocalized badge
28 |
29 |
30 | If you want your community to see the translation progress of your project, feel free to add our  badge to your Readme file, Wiki or Contributing Guidelines.
31 |
32 | To generate the badge link, head to the Badge tab in Project Overview:
33 | 
34 |
35 | You can also generate badges for each of the project languages:
36 |
37 | 
38 | 
39 | 
40 |
41 |
42 | Check out how other GitHub projects are using our badge:
43 |
44 | [Hacker Laws](https://github.com/dwmkerr/hacker-laws#translations)
45 |
46 | [SlimeFun4](https://github.com/TheBusyBiscuit/Slimefun4/wiki/Translating-Slimefun)
47 |
48 | ---
49 |
50 | ### 🗞 Group multiple files in a single pull request
51 |
52 | If you're a language moderator or project owner, you may now find it easier to send multiple translated files (review requests) in a single pull request
53 | 
54 |
55 | ---
56 |
57 | _Stay tuned for future updates!_
58 |
59 |
60 | Should you have any questions, feel free to [join our community chat](https://gitter.im/gitlocalize/Lobby) or [send us an email](mailto:info@gitlocalize.com).
61 |
--------------------------------------------------------------------------------
/_i18n/ja.yml:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/gitlocalize/blog/1cfe3e0dba70a90360f1902dbdd65d56fdc9a26a/_i18n/ja.yml
--------------------------------------------------------------------------------
/_i18n/ja/_posts/2017-05-12-introducing-gitlocalize.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: 'GitLocalizeのご紹介: GitHubリポジトリのための継続的ローカライゼーションツール'
4 | author: chikathreesix
5 | languages:
6 | - en
7 | image: gitlocalize.png
8 | ---
9 |
10 | 新しいローカライゼーションプラットフォーム、[GitLocalize](https://gitlocalize.com)のベータ版がローンチしました!
11 |
12 | GitLocalizeは、GitHubリポジトリ用の継続的なローカリゼーションプラットフォームで、開発者向けにプロセスを自動化します。インターネット関連の製品はアップデートが頻繁に起こるため、ローカライズを維持することは本当に難しい作業でしたが、 GitLocalizeはGitHubリポジトリに接続し、数回のクリックで開発ワークフローと自然に統合することで、継続的なローカライゼーションの問題を解決します。
13 |
14 | 現在Markdownファイルをサポートしてますので、ローカライズするドキュメントプロジェクトがある場合は、是非GitLocalizeを試してみてください。
15 |
16 | GitHubですぐに始める
17 |
18 | # 主な特徴
19 |
20 | GitHubアカウントを使ってすぐに始めることができます。リポジトリを選択してGitLocalizeと統合し、ファイルをローカライズします。プラットフォームの主な機能は次のとおりです。
21 |
22 | ### GitHubベースのワークフロー
23 |
24 | 
25 |
26 | リポジトリをGitLocalizeと統合すると、ローカライゼーション関連のすべてのファイルがプラットフォームにpullされ、変更が監視され始めます。
27 |
28 | ファイルの翻訳が完了したら、レビューリクエストを作り、変更をレビューするようチームに依頼します。GitHubで行なっている、プルリクエストと同じようなフローです。
29 |
30 | レビューが完了したら、プルリクエストをリポジトリに送り返すことができます。GitLocalizeでの貢献が、それぞれのユーザーのコミットとなります。
31 |
32 | GitLocalizeを利用すると、チームはプロジェクトをローカライズするために余分な作業を行う必要がなくなり、開発者はプルリクエストを見るだけで済みます。
33 |
34 | ### 翻訳文の差分管理
35 |
36 | 
37 |
38 | 自動的に元の文と翻訳をリンクするので、元の文が更新されたときに、どこを翻訳すれば良いのかすぐにわかります。
39 |
40 | オリジナルの更新によって影響を受ける部分を目視で確認する必要はありません。GitLocalizeエディタを見て足りない翻訳を行うだけです。
41 |
42 | もちろん、これから続々と機能が追加されて行きます!
43 |
44 | # もっと詳しく
45 |
46 | どのように動くのか、詳しくは以下のビデオをご覧ください!
47 |
48 |
49 |
50 |
51 |
52 | # 楽しいローカライゼーションを!
53 |
54 | 製品を改善し、ローカライゼーションのより良い未来を作るため、皆様のご意見が必要です。[こちらに](https://gitlocalize.com/inquiries/new)是非フィードバックをお寄せください。即日でご返信します。
55 |
56 | こちらの[Gitterチャンネル](https://gitter.im/gitlocalize/Lobby?utm_source=share-link&utm_medium=link&utm_campaign=share-link)もありますので、自由に参加して会話に参加してください。
57 |
58 | もちろん、このブログはGitLocalizeを使って日本語にローカライズされていますので、[ここ](https://gitlocalize.com/repo/80)から翻訳を提案してください。
59 |
60 | ローカライゼーションを簡単かつスムーズにし、製品のグローバルな成功をサポートできるよう願っています!
61 |
--------------------------------------------------------------------------------
/_i18n/ja/_posts/2017-08-02-github-marketplace-launch.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: GitLocalizeがGitHubマーケットプレイスにローンチされました!
4 | author: chikathreesix
5 | languages:
6 | - en
7 | image: ghm/main.png
8 | ---
9 |
10 | [GitLocalize](https://github.com/marketplace/gitlocalize)が[GitHub Marketplace](https://github.com/marketplace)にて最初のローカリゼーションアプリとしてローンチされました!
11 |
12 | 
13 |
14 | [GitLocalize](https://gitlocalize.com)は、8月1日に[GitHub Marketplace](https://github.com/marketplace)にローンチされた7つの新しいアプリケーションの1つで、[ローカリゼーション](https://github.com/marketplace/category/localization)は新しいカテゴリです!
15 |
16 | GitHubは、 [GitLocalize](https://gitlocalize.com)を含む新しいアプリを、公式のブログ記事["Introducing seven new apps to GitHub Marketplace"](https://github.com/blog/2411-introducing-seven-new-apps-to-github-marketplace)にて紹介しています。記事を読んで、他の素晴らしいアプリについてもチェックして見てください。
17 |
18 | [アプリのページ](https://github.com/marketplace/gitlocalize)から、価格の詳細を確認して、是非今すぐ無料プランを始めてみてください!
19 |
--------------------------------------------------------------------------------
/_i18n/ja/_posts/2017-09-25-ruby-on-rails-support.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: GitLocalizeを使ってRuby on Rails アプリをローカライズ
4 | author: chikathreesix
5 | languages:
6 | - en
7 | image: gitlocalize.png
8 | ---
9 |
10 | Ruby on Railsのi18n YAMLファイルを管理とそれに伴うローカリゼーション作業に苦労していませんか? GitLocalizeは面倒なRails i18nのすべての作業を簡単にすることができます!
11 |
12 | # 開始する
13 |
14 | まだサインアップしていない場合は、無料でGitLocalizeに登録して、Railsアプリをストレスなくローカライズする準備をしましょう。
15 |
16 |
17 |
18 | 無料で始める
19 |
20 |
21 | GitLocalizeが実際にどう動くのか、[こちらのブログ記事](/posts/ja/introducing-gitlocalize.html) をチェックしてみてください。
22 |
23 | # Railsアプリを登録する
24 |
25 | プロフィールから `Repository追加` ページへ移動すると、GitHubリポジトリをGitLocalizeに追加するフォームがあります。
26 |
27 | ページの中央で、ソースi18nファイルの場所と翻訳ファイルの生成場所を指定します。
28 |
29 | たとえば英語のi18n YAMLファイルが`config/locales/en.yml`にあり、 翻訳したいファイルが`config/locales/ja.yml`や`config/locales/es.yml`にあるとします。この場合、左側のドロップダウンメニューで`File`を選択し、 `Source Path`に`config/locales/en.yml` 、`Translation Path`に`config/locales/%lang%.yml`を入力します。
30 |
31 | 
32 |
33 | この `%lang%` は翻訳対象言語の二文字の言語コードのプレースホルダーです。例えば、日本語とスペイン語を翻訳している場合、`ja.yml` と `es.yml` がそれぞれ生成されます。
34 |
35 | i18nファイルが複数ある場合は、 `+ Add Rule`ボタンをクリックすることで、複数のルールを登録できます。
36 |
37 | # ローカライズを始める
38 |
39 | リポジトリの登録が完了したら、GitLocalizeであなたのRailsアプリの継続的ローカライズを始めることができます。
40 |
41 | プロフィールページからリポジトリページに移動し、言語を選択し、YAMLファイルに移動してエディタを開きます。
42 |
43 | 以下のビデオや [ドキュメンテーション](http://docs.gitlocalize.com/getting_started.html) をみて、この後のプロセスについて学んでみてください。
44 |
45 |
46 |
47 |
--------------------------------------------------------------------------------
/_i18n/ja/_posts/2017-11-27-gitlocalize-webfundamentals.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: GoogleのWeb FundamentalsがローカライズにGitLocalizeを試験運用開始
4 | author: chikathreesix
5 | languages:
6 | - en
7 | image: webfundamentals_gitlocalize.png
8 | ---
9 |
10 | 
11 |
12 | [GitLocalizeがGoogleのプロジェクトにて試験的に導入が開始されました](https://developers.google.com/web/resources/translations)! Web Fundamentalsのウェブサイトを、コミュニティと共にGitLocalizeを活用してローカライズを進めて行きます。
13 |
14 | 現在Web Fundamentalsのコミュニティはウェブサイトを17の言語にローカライズしてきました。しかし翻訳を常に最新の状態に保つのはとても難しいことでした。GitLocalizeがそれを解決することを願っています!
15 |
16 | Web Fundamentalsのコミュニティに参加して、最新のウェブ技術の知見を自分の言語にローカライズしてみましょう! イノベーションに言語の壁が邪魔してはいけないはずです。
17 |
18 | [プロジェクトに参加する](https://gitlocalize.com/repo/107)
19 |
--------------------------------------------------------------------------------
/_i18n/ru.yml:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/gitlocalize/blog/1cfe3e0dba70a90360f1902dbdd65d56fdc9a26a/_i18n/ru.yml
--------------------------------------------------------------------------------
/_i18n/ru/_posts/2019-02-03-gitlocalize-now-part-of-alconost.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: GitLocalize объединяется с Alconost!
4 | author: ilyaspiridonov
5 | languages:
6 | - en
7 | image: alconost_gitlocalize.png
8 | ---
9 |
10 | 
11 |
12 | ### Отличные новости!
13 |
14 | Рады сообщить, что [GitLocalize](https://gitlocalize.com) стал частью компании [Alconost](https://alconost.com)!
15 |
16 | Alconost Inc. — студия локализации из США, которая помогает компаниям во всем мире локализовывать продукты и контент более чем на 80 языков. Благодаря опыту и профессиональной команде Alconost, GitLocalize будет продолжать совершенствоваться, а пользователям платформы станут доступны профессиональные услуги перевода.
17 |
18 | Следите за новостями!
19 |
20 | Если у вас возникли вопросы, вы можете задать их в [чате коммьюнити](https://gitter.im/gitlocalize/Lobby) или [запланировать с нами звонок](https://calendly.com/is-alconost)!
21 |
--------------------------------------------------------------------------------
/_i18n/ru/_posts/2019-05-28-gitlocalize-is-now-free.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: GitLocalize – теперь бесплатно!
4 | author: ilyaspiridonov
5 | languages:
6 | - en
7 | image: gitlocalize-is-free-now.png
8 | ---
9 |
10 | 
11 |
12 | Мы рады сообщить, что платформа [GitLocalize](https://gitlocalize.com) стала бесплатной!
13 |
14 | ### Что доступно в бесплатной версии?
15 |
16 | Весь функционал: синхронизация репозиториев, вебхуки для обновления проектов, ручной и машинный перевод на все поддерживаемые языки — все это доступно в бесплатной версии.
17 |
18 | ### Бесплатно для всех?
19 |
20 | Практически для всех. Независимо от того, приватный у вас проект либо OSS, его можно синхронизировать с GitLocalize и переводить документацию, руководства и ресурсные строки на любые языки. Мы будем делать все, чтобы платформа оставалась бесплатной для любых проектов, за исключением очень крупных: для таких случаев есть индивидуальный план Enterprise с дополнительной технической поддержкой.
21 |
22 | ### Бесплатно всегда?
23 |
24 | Да, мы сделаем все возможное, чтобы платформа всегда оставалась бесплатной.
25 |
26 | GitLocalize — далеко не совершенный продукт, и сейчас мы хотим получить как можно больше обратной связи от пользователей. Регистрируйтесь или авторизуйтесь с помощью аккаунта GitHub, добавляйте репозиторий и начинайте переводить. Наша команда будет рада ответить на любые вопросы — [присоединяйтесь к чату комьюнити](https://gitter.im/gitlocalize/Lobby) или [забронируйте звонок с нами](https://calendly.com/is-alconost), чтобы поделиться впечатлениями!
27 |
--------------------------------------------------------------------------------
/_i18n/ru/_posts/2020-03-27-badges-filters-and-more.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: 🚀 Бэджи, фильтры и не только
4 | author: ilyaspiridonov
5 | languages:
6 | - en
7 | ---
8 |
9 | Мы прилагаем все усилия, чтобы сделать GitLocalize лучше. Вот какой интересный функционал мы недавно добавили.
10 |
11 | ---
12 |
13 |
14 |
15 | ### 🔍 Фильтры
16 |
17 | Переводить обновления стало проще. Теперь можно переключиться в режим отображения только непереведенных строк (либо переведенных машинным переводом). Это особенно важно при работе с большими файлами .md или .json.
18 | Нажмите иконку фильтра в правой верхней части редактора
19 |
20 | 
21 |
22 | и выберите нужный режим отображения:
23 |
24 | 
25 |
26 | ---
27 |
28 |
29 |
30 | ### 🏷 Бэдж GitLocalized
31 |
32 | Если вы хотите, чтобы участники вашего коммьюнити видели прогресс перевода вашего проекта, добавьте наш бэдж  в Readme, вики или гайды для контрибьюторов.
33 |
34 | Сгенерировать ссылку на бэдж можно во вкладке Badge:
35 | 
36 |
37 | Кроме того, можно генерировать отдельные бэджи для каждого языка проекта:
38 |
39 |  
40 | 
41 |
42 | Посмотрите, как другие проекты на GitHub используют наш бэдж:
43 |
44 | [Hacker Laws](https://github.com/dwmkerr/hacker-laws#translations)
45 |
46 | [SlimeFun4](https://github.com/TheBusyBiscuit/Slimefun4/wiki/Translating-Slimefun)
47 |
48 | ---
49 |
50 |
51 |
52 | ### 🗞 Объединяйте несколько файлов в один pull request
53 |
54 | Если вы модератор языка или владелец проекта, возможно, вам будет удобнее отправлять несколько переведенных файлов (review request-ов) в одном пуллреквесте.
55 | 
56 |
57 | ---
58 |
59 | Следите за нашими новостями!
60 |
61 | Если у вас возникли вопросы, вы можете задать их в [чате коммьюнити](https://gitter.im/gitlocalize/Lobby) или [отправить нам письмо](mailto:info@gitlocalize.com).
62 |
--------------------------------------------------------------------------------
/_includes/disqus.html:
--------------------------------------------------------------------------------
1 |
2 |
10 |
11 |
--------------------------------------------------------------------------------
/_includes/footer.html:
--------------------------------------------------------------------------------
1 | {% if site.theme_settings.katex %}
2 |
3 | {% endif %}
4 |
5 | {% if site.theme_settings.footer_text %}
6 |
9 | {% endif %}
10 |
--------------------------------------------------------------------------------
/_includes/head.html:
--------------------------------------------------------------------------------
1 |
2 |
3 | {% if page.title %}{{ page.title }} |{% endif %} {{ site.theme_settings.title }}
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 | {% if site.theme_settings.google_fonts %}
30 |
31 | {% endif %}
32 |
33 |
34 | {% if site.theme_settings.katex %}
35 |
36 |
37 | {% endif %}
38 |
39 |
40 | {% if site.theme_settings.google_analytics %}
41 |
50 | {% endif %}
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 |
64 |
--------------------------------------------------------------------------------
/_includes/header.html:
--------------------------------------------------------------------------------
1 |
2 |