Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translate content to Spanish #498

Open
JMPerez opened this issue Nov 16, 2019 · 31 comments
Open

Translate content to Spanish #498

JMPerez opened this issue Nov 16, 2019 · 31 comments
Labels
good first issue Good for newcomers translation world wide web

Comments

@JMPerez
Copy link
Contributor

JMPerez commented Nov 16, 2019

These are the core templates - without which we cannot release any translated chapters. They are in the language specific templates directory:

  • base.html -
  • base_chapter.html-
  • error.html-

2022

  • base.html -
  • contributors.html -
  • index.html -
  • table_of_contents.html -

2021

  • base.html -
  • base.html - foreword
  • contributors.html -
  • index.html -
  • table_of_contents.html -

2020

  • base.html -
  • base.html - foreword added later
  • contributors.html -
  • index.html -
  • table_of_contents.html -

2019

  • base.html -
  • contributors.html -
  • index.html -
  • table_of_contents.html -

These are the chapters to be translated, in rough order of popularity. They exist in the content directory:

2022

  • css -
  • javascript -
  • markup -
  • structured-data -
  • fonts -
  • media -
  • webassembly -
  • third-parties -
  • interoperability -
  • seo - @carloscastromx
  • accessibility -
  • performance -
  • privacy - @decrecementofeliz
  • security -
  • mobile-web -
  • capabilities -
  • pwa -
  • cms -
  • jamstack -
  • sustainability -
  • page-weight -
  • cdn -
  • http -

2021

  • css -
  • javascript -
  • markup -
  • structured-data -
  • media -
  • webassembly -
  • third-parties -
  • seo -
  • accessibility -
  • performance - @nucliweb
  • privacy -
  • security -
  • mobile-web -
  • capabilities -
  • pwa -
  • cms -
  • ecommerce -
  • jamstack -
  • page-weight -
  • compression -
  • caching -
  • cdn -
  • resource-hints -
  • http -

2020

  • css -
  • javascript - @alangdm
  • seo - @carloscastromx
  • markup -
  • accessibility -
  • cms -
  • performance -
  • security -
  • jamstack -
  • fonts -
  • mobile-web -
  • pwa -
  • http2 - @moniloria
  • capabilities -
  • third-parties -
  • caching -
  • resource-hints -
  • privacy -
  • compression -
  • ecommerce -
  • media -

2019

Additionally the following pages need translated too in the language specific templates directory, but less important than core templates and chapters:

  • accessibility_statement.html -
  • accessibility_statement.html additional update -
  • base_ebook.html -
  • 2021/methodology.html -
  • 2020/methodology.html -
  • 2019/methodology.html -

There is no need to translate the chapters HTML pages are they are generated off the markdown combined with the above templates.

Please include "Makes progress on #498 " in all pull requests so a link is created from the PR to this issue.


Common notes for writing consistency are here: https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Translators'-Guide. Feel free to edit that and/or add Spanish-specific extras by editing this comment.

Spanish-specific extra advice:

  • None yet
@c-torres
Copy link
Contributor

Should we include the specific pages? Like Table of Contents, Methodology, etc.

@rviscomi
Copy link
Member

@c-torres there are still some changes happening to those pages so let's leave those for last.

@c-torres
Copy link
Contributor

Working on the JavaScript chapter.

@c-torres
Copy link
Contributor

Working on the CSS chapter.

@tunetheweb
Copy link
Member

Working on the CSS chapter.

Hey @c-torres just so you're aware, very shortly (I hope - nudge, nudge @rviscomi !!😉 ) we will be merging #511 which contains a change of format for the diagrams and more descriptive text for them.

We already did the JavaScript chapter and I checked and you got the latest version so that's cool. However unfortunately we will need you guys to revist the other chapters you've already done.

So before you submit the CSS chapter you might be best to double check master to ensure you've got the latest diagram markdown. Or alternatively take the source from the figures_new_format branch under the assumption it will be merged.

Sorry about this change, but I thought it would be worthwhile giving you the heads up to this as know there are a lot of figures in the CSS chapter!

@c-torres
Copy link
Contributor

No worries, thanks for the heads up, really appreciated.

@tunetheweb
Copy link
Member

That's now merged to master @c-torres and will shortly be updated in prod. So you're good to grab the latest version. It was the same that was in the branch if you've already started on that. Will raise a separate issue for the other chapters already done to have another look over.

@c-torres
Copy link
Contributor

Submitted a PR for CSS translation. Will continue working on Media Chapter.

@tunetheweb
Copy link
Member

Hey @c-torres @JMPerez @taytus !

We’re now in the position to launch chapters that have been translated without having to wait for all chapters to be translated.

To do that however we do need base_chapter.html translated and also probably a good idea to review base.html. These are both quite short so a lot easier to translate than the chapters.

Would any of you have the time to have a look? Would be great to get the chapters you’ve worked on out there available to the public and might even encourage others to help out with the remaining chapters.

@taytus
Copy link

taytus commented Mar 17, 2020

Hello @tunetheweb , unfortunately, I'm totally swamped and won't be able to help at this moment.
I'm sorry 😔

tunetheweb added a commit that referenced this issue Jan 3, 2021
* merge from main/upstream

* Update src/content/es/2020/http2.md

Co-authored-by: Barry Pollard <[email protected]>

* Update src/content/es/2020/http2.md

Co-authored-by: Barry Pollard <[email protected]>

* Update src/content/es/2020/http2.md

Co-authored-by: Barry Pollard <[email protected]>

* Update src/content/es/2020/http2.md

Co-authored-by: Barry Pollard <[email protected]>

* Update src/content/es/2020/http2.md

Co-authored-by: Barry Pollard <[email protected]>

* Update src/content/es/2020/http2.md

Co-authored-by: Barry Pollard <[email protected]>

* Update src/content/es/2020/http2.md

Co-authored-by: Barry Pollard <[email protected]>

* Update src/content/es/2020/http2.md

Co-authored-by: Barry Pollard <[email protected]>

* Update src/content/es/2020/http2.md

Co-authored-by: Barry Pollard <[email protected]>

* Update src/content/es/2020/http2.md

Co-authored-by: Barry Pollard <[email protected]>

* adding minor changes in Spanish and English versions

* Update src/content/es/2020/http2.md

Co-authored-by: Barry Pollard <[email protected]>

* changes for table 22.17

Co-authored-by: Barry Pollard <[email protected]>
@alangdm
Copy link
Contributor

alangdm commented Apr 28, 2021

I will try to do 2020's javascript article

@tunetheweb
Copy link
Member

Great stuff. Let us know if you have any questions. The first chapter can always take a bit longer as you get used to the content/format/process but always willing to help!

@excellenseo
Copy link

excellenseo commented Apr 28, 2021

Hi @tunetheweb , let me know where can I help.

@tunetheweb
Copy link
Member

@excellenseo edit the first item to put your name against one of the ones that are not done yet and away you go! Translate and submit a PR for review. They are in rough popularity order.

There was a foreword added to src/templates/en/2020/base.html which doesn't exist in the es version and maybe that would be a nice easy one to start with before you tackle a full chapter?

After that maybe the 2020 SEO one tempts you, given your username? 😀

@tunetheweb
Copy link
Member

Actually sorry, I see @carloscastromx has nabbed the SEO one already! So either ask them if they're willing to trade or grab one of the others that haven't been assigned yet.

@excellenseo
Copy link

excellenseo commented Apr 29, 2021

@tunetheweb I will start with the base.html and will continue with http2.
@carloscastromx let me know if you need help for the SEO chapter.

@tunetheweb
Copy link
Member

Looks like http2 is already done for 2020. And think we should work on 2020 now as less people interested in 2019. So I'd pick another chapter if I were you. Unless you're really interested in HTTP/2, in which case go for it.

@excellenseo
Copy link

excellenseo commented Apr 29, 2021

Oh I was looking at 2019 instead of 2020. I selected markup. Thanks @tunetheweb

@carloscastromx
Copy link
Contributor

carloscastromx commented Apr 30, 2021

@tunetheweb I will start with the base.html and will continue with http2.

@carloscastromx let me know if you need help for the SEO chapter.

Will do!

@tunetheweb tunetheweb mentioned this issue Jun 20, 2021
6 tasks
tunetheweb added a commit that referenced this issue Jun 25, 2021
* Translation & fixed typos

Translated chapter and fixed some typos on the English chapter

* Add new Translator

* Alphabetical order fix

* Update Microformats to Microformats2

Co-authored-by: Barry Pollard <[email protected]>

* "elements" consistency

Co-authored-by: Barry Pollard <[email protected]>

* Spacing after coma

Co-authored-by: Barry Pollard <[email protected]>

* Alt not needed

Co-authored-by: Barry Pollard <[email protected]>

* Github Handle

Co-authored-by: Barry Pollard <[email protected]>

* Alt not needed

Co-authored-by: Barry Pollard <[email protected]>

* Alt not needed

Co-authored-by: Barry Pollard <[email protected]>

* Alt not needed

Co-authored-by: Barry Pollard <[email protected]>

* Alt not needed

Co-authored-by: Barry Pollard <[email protected]>

* Fix other translations

Co-authored-by: Barry Pollard <[email protected]>
Co-authored-by: Barry <[email protected]>
@tunetheweb
Copy link
Member

We added a small note to our Accessibility Statement about colour contrast issues:

{# TODO - Translate this <p>
We recognize that some of the color choices for our visualizations do not meet WCAG color contrast requirements. We make a conscious effort to use the more contrasting colors and labels to reduce the impact of this. We hope the detailed descriptions, as well as access to the underlying data itself can help with this issue. We aim to improve the accessibility of our visualization color schemes in future years.
</p> #}

Would be great if someone could translate this. Very small and easy!

@nucliweb
Copy link

nucliweb commented Dec 8, 2021

Hi @tunetheweb I can help with the Spanish translation 2021, and I would like to start with performance, resource-hints, javascript and webassembly sections.

@tunetheweb
Copy link
Member

Great news @nucliweb ! Edit the first comment to stick your name by one of them to "claim" that translation and away you go. Maybe don't claim all 4 of them initially to give any others a chance.

@nucliweb
Copy link

nucliweb commented Dec 8, 2021

Great news @nucliweb ! Edit the first comment to stick your name by one of them to "claim" that translation and away you go. Maybe don't claim all 4 of them initially to give any others a chance.

Of course 😅

decrecementofeliz added a commit that referenced this issue Nov 19, 2022
tunetheweb added a commit that referenced this issue Nov 23, 2022
* Spanish Translation - Privacy chapter

Make progress on #498

* removed trailing spaces

* Fix bad markup

* Add profile

Co-authored-by: Barry Pollard <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers translation world wide web
Projects
None yet
Development

No branches or pull requests