Skip to content

Conversation

@lll-lll-lll-lll
Copy link
Contributor

Important

The original sentence was translating the same text twice. I have modified it to the appropriate version.

The corresponding English text is as follows:

To understand how the technology works, let's walk through the process of setting up https://example.com/ with a certificate management agent that supports Let's Encrypt.
->この技術がどのような仕組みなのかを理解するために、Let's Encrypt をサポートする証明書管理エージェントを使用して https://example.com/ を設定する過程を見ていきましょう。

There are two steps to this process. First, the agent proves to the CA that the web server controls a domain. Then, the agent can request, renew, and revoke certificates for that domain.
→このプロセスには2つのステップがあります。 1つ目は、CA に対して、ウェブサーバーがドメインをコントロールしていることを証明するプロセスです。 2つ目は、そのドメインに対して、エージェントが証明書のリクエスト・更新・無効化を行うプロセスです。

@ludekjanda ludekjanda self-assigned this Nov 24, 2024
@ludekjanda
Copy link
Collaborator

Hello @lll-lll-lll-lll

🙏🏻thank you for contributing with your translations. The localization process looks this way:

  • first translations are saved in our Crowdin project
  • then they are exported from Crowdin to Github
  • only the files which are 100% translated get exported

Unfortunately if you submit changes to Github only, they may get overwritten with different translations coming from Crowdin.

I can see your changes are in content/how-it-works.md file.
https://crowdin.com/editor/lets-encrypt-website/142/en-ja?view=side-by-side&filter=basic&value=3

I have saved them there. However there are still 5 segments missing translations and that's the reason I am unable to export the latest version of this file in Japanese to Github.

You may want to check out our project yourself.

Thank you

@ludekjanda
Copy link
Collaborator

I am merging this update because I have save all these translations to Crowdin. However the standard localization process looks differently, see my comment above.

@ludekjanda ludekjanda merged commit e202f32 into letsencrypt:main Nov 24, 2024
4 checks passed
@ludekjanda ludekjanda added translation https://github.com/letsencrypt/website/blob/main/TRANSLATION.md i18n l10n labels Nov 24, 2024
@lll-lll-lll-lll
Copy link
Contributor Author

@ludekjanda
Thank you so much for the detailed explanation of the translation process and for letting me know that my changes have been saved in Crowdin. I will check the remaining untranslated segments and take care of them.
Thanks again, and I look forward to working together!

@ludekjanda ludekjanda removed the i18n label Nov 24, 2024
bdaehlie pushed a commit that referenced this pull request Jan 9, 2025
# Important

The original sentence was translating the same text twice. I have
modified it to the appropriate version.

The corresponding English text is as follows:

> To understand how the technology works, let's walk through the process
of setting up https://example.com/ with a certificate management agent
that supports Let's Encrypt.
->この技術がどのような仕組みなのかを理解するために、Let's Encrypt をサポートする証明書管理エージェントを使用して
https://example.com/ を設定する過程を見ていきましょう。

>There are two steps to this process. First, the agent proves to the CA
that the web server controls a domain. Then, the agent can request,
renew, and revoke certificates for that domain.
→このプロセスには2つのステップがあります。 1つ目は、CA
に対して、ウェブサーバーがドメインをコントロールしていることを証明するプロセスです。
2つ目は、そのドメインに対して、エージェントが証明書のリクエスト・更新・無効化を行うプロセスです。
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

translation https://github.com/letsencrypt/website/blob/main/TRANSLATION.md

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants