search

letsencrypt / website

Let's Encrypt Website and Documentation
https://letsencrypt.org
Mozilla Public License 2.0
841 stars 573 forks source link

i18n - RLT languages #1067

Open tdelmas opened 4 years ago

tdelmas commented 4 years ago

The arrows are in the wrong direction: https://github.com/letsencrypt/website/pull/1010#issuecomment-626889626

image

The margin is wrong in become-a-sponsor: https://github.com/letsencrypt/website/pull/1010#issuecomment-626192535

yarons commented 4 years ago

Can I add the application screen directionality issue in here or open another one?

tdelmas commented 4 years ago

A new one would be perfect!

yarons commented 4 years ago

I have 2 more questions:

  1. When will we see some source string updates on Crowdin?
  2. Is there a way to set the number of certificated issued as global parameter so the users will see the same number in all translations?
tdelmas commented 4 years ago
  1. When will we see some source string updates on Crowdin?

Ideally I would like to see the import into Crowdin finished (translations and proofreading) before doing anything else there, to avoid complications. But, if needed, maybe I could selectively and carefully update some pages if needed.

  1. Is there a way to set the number of certificated issued as global parameter so the users will see the same number in all translations?

Having some global variables, for that and other things could be a good idea, but we must be careful, it may complicate the translation: some languages are really complicated with numbers, because some not only have singular/plural, but a lot more rules: https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals

Example: image

yarons commented 4 years ago

Oh yes sorry, completely forgot about that.

How well does Hugo supports i18n and plural forms becuase I haven't found anything in its docs?

tdelmas commented 4 years ago

They do: https://gohugo.io/content-management/multilingual/#translation-of-strings

yarons commented 4 years ago

Do you think we should use that for the title or just update whenever the number changes? Because templating this is relatively easy now that I see what you've presented.

We still have some checks to do in order to make sure Crowdin will support that syntax and will allow proper pluralization, otherwise we'll just have to contact support and send them the documents that you sent me in order to support it.

tdelmas commented 4 years ago

I'll do some tests. But I think the number should not be "live", but the value that the Let's Encrypt team decide (i.e. not me)