You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
@Bisaloo it is not. I agree, it would be good to have. We could perhaps leverage transifex for this, but we don't want to do it until after we actually update the FAQ.
@Hainish actually the translation of the FAQ to other languages is happening here: EFForg/www-l10n. Personally I'm working on the italian one. Should we wait for the update of the FAQ?
@dvd2000 thanks for the notification - it looks like there hasn't been a commit for quite a while in that repo, though. I'll check with our web dev team to see if it's still active. Also, be aware that we've moved the FAQ (as well as a few other HTTPS Everywhere pages) into the repo: https://github.com/EFForg/https-everywhere/tree/master/docs
We should change the structure and maybe format of the docs path to support localization.
@dvd2000 apparently that repo was created but never used to uplift translations as our web dev team deprioritized it. I'd suggest any translation be made in this repo, restructuring the docs path to support i18n in a PR (e.g. our current docs could go under docs/en_US.)
@Hainish Thanks for the update. I'll make a PR to move the docs and maybe write something to explain how to translate and how to add a new language; should I wait for the FAQ review?
EFF has a Transifex profile here. I think that moving the translation process there would be better. What do you think?
Probably that's not a good idea, it isn't very common to translate large pieces of text with transifex and as you said it will be quite hard to generate markdown from translation files.
Maybe it will be easier to use normal PR's here on github.
Should I open a separate issue for discussing about the translation of the docs?
Activity
Hainish commentedon Apr 8, 2017
Related: #8187 #7936 #7282 #2088
Hainish commentedon Apr 8, 2017
Related: #9467
Bisaloo commentedon Apr 10, 2017
Is the FAQ translated in other languages than English? I think it would be a nice improvement.
Privacy badger already does it.
Hainish commentedon Apr 13, 2017
@Bisaloo it is not. I agree, it would be good to have. We could perhaps leverage transifex for this, but we don't want to do it until after we actually update the FAQ.
dvd2000 commentedon Apr 17, 2017
@Hainish actually the translation of the FAQ to other languages is happening here: EFForg/www-l10n. Personally I'm working on the italian one. Should we wait for the update of the FAQ?
Hainish commentedon Apr 17, 2017
@dvd2000 thanks for the notification - it looks like there hasn't been a commit for quite a while in that repo, though. I'll check with our web dev team to see if it's still active. Also, be aware that we've moved the FAQ (as well as a few other HTTPS Everywhere pages) into the repo: https://github.com/EFForg/https-everywhere/tree/master/docs
We should change the structure and maybe format of the docs path to support localization.
dvd2000 commentedon Apr 17, 2017
Ok @Hainish, thanks for your reply. I will wait for some news.
Hainish commentedon Apr 18, 2017
@dvd2000 apparently that repo was created but never used to uplift translations as our web dev team deprioritized it. I'd suggest any translation be made in this repo, restructuring the
docspath to support i18n in a PR (e.g. our current docs could go underdocs/en_US.)Hainish commentedon Apr 18, 2017
And I suggest also holding off on this until we review the FAQ.
dvd2000 commentedon Apr 18, 2017
@Hainish Thanks for the update. I'll make a PR to move the docs and maybe write something to explain how to translate and how to add a new language; should I wait for the FAQ review?
EFF has a Transifex profile here. I think that moving the translation process there would be better. What do you think?
Hainish commentedon Apr 18, 2017
I thought about moving the translations to the Transifex page. To do this, first you need to create the new strings in the files under https://github.com/EFForg/https-everywhere/tree/master/src/chrome/locale/en. Every night, Transifex reads these files and creates new fields for the translators to fill.
This may be the way to go, though I suspect it would be kind of hard to auto-generate the markdown from the
dtdfile.dvd2000 commentedon Apr 18, 2017
Probably that's not a good idea, it isn't very common to translate large pieces of text with transifex and as you said it will be quite hard to generate markdown from translation files.
Maybe it will be easier to use normal PR's here on github.
Should I open a separate issue for discussing about the translation of the docs?
dvd2000 commentedon Apr 19, 2017
@Hainish
Hainish commentedon Apr 19, 2017
A new issue would be fine.
jdatapple commentedon May 24, 2017
Related: #10020
Bisaloo commentedon Feb 23, 2018
From #7343 (comment):
zoracon commentedon Jul 23, 2020
The FAQ has been updated, closing. Thank you!