Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Update FAQ #9466

Closed
Closed

Description

@Hainish

A lot of the FAQ is outdated and requires a rewrite.

Activity

  1. Hainish commented on Apr 8, 2017

    @Hainish
    MemberAuthor
  2. Hainish commented on Apr 8, 2017

    @Hainish
    MemberAuthor

    Related: #9467

  3. Bisaloo commented on Apr 10, 2017

    @Bisaloo
    Collaborator

    Is the FAQ translated in other languages than English? I think it would be a nice improvement.

    Privacy badger already does it.

  4. Hainish commented on Apr 13, 2017

    @Hainish
    MemberAuthor

    @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.

  5. dvd2000 commented on Apr 17, 2017

    @dvd2000
    Contributor

    @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?

  6. Hainish commented on Apr 17, 2017

    @Hainish
    MemberAuthor

    @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.

  7. dvd2000 commented on Apr 17, 2017

    @dvd2000
    Contributor

    Ok @Hainish, thanks for your reply. I will wait for some news.

  8. Hainish commented on Apr 18, 2017

    @Hainish
    MemberAuthor

    @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.)

  9. Hainish commented on Apr 18, 2017

    @Hainish
    MemberAuthor

    And I suggest also holding off on this until we review the FAQ.

  10. dvd2000 commented on Apr 18, 2017

    @dvd2000
    Contributor

    @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?

  11. Hainish commented on Apr 18, 2017

    @Hainish
    MemberAuthor

    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 dtd file.

  12. dvd2000 commented on Apr 18, 2017

    @dvd2000
    Contributor

    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?

  13. dvd2000 commented on Apr 19, 2017

    @dvd2000
    Contributor
  14. Hainish commented on Apr 19, 2017

    @Hainish
    MemberAuthor

    A new issue would be fine.

  15. jdatapple commented on May 24, 2017

    @jdatapple

    Related: #10020

  16. Bisaloo commented on Feb 23, 2018

    @Bisaloo
    Collaborator

    From #7343 (comment):

  17. self-assigned this
    on Mar 28, 2019
  18. zoracon commented on Jul 23, 2020

    @zoracon
    Contributor

    The FAQ has been updated, closing. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions