Final WPCredits Report: Astra Translation for Spanish (Costa Rica)

WPCredits · Final report

Astra Translation for Spanish (Costa Rica)

A short account of the work, the problems I ran into, and what I learned from submitting 150 translation suggestions.

Introduction

I am Sergio Camacho, a Computer Science student at Universidad Fidélitas. This is my final report for the WPCredits program. My project was a public translation contribution to WordPress.

Team and project

I contributed to the Polyglots team by translating interface strings from the Astra theme into Spanish for Costa Rica. My working target was 100 useful strings. I continued to 150 so the contribution would still be substantial if reviewers ask for changes.

Learning resources

I used the Polyglots handbook, the Spanish (Costa Rica) glossary and style guide, the public Astra translation project, and the Learn WordPress course. Together they explained the locale rules, the review process, and the technical parts of strings that must not be changed.

Polyglots handbook
Astra project for Spanish (Costa Rica)

Challenges and solutions

The easiest mistake was changing something that was not ordinary text. Placeholders such as %s and HTML such as <br /> had to remain exact. I translated only the surrounding words and skipped strings when the context was unclear.

Consistency was another problem. Before requesting review, I checked the complete set for formal “usted,” sentence case, locale vocabulary, placeholders, and HTML.

My contributions

I submitted 150 Astra translation suggestions for es_CR. Editorial review is now in progress. As of July 29, 94 are approved, 55 are still waiting, and 1 has changes requested.

The links below are filtered to my WordPress.org account, so they show my own suggestions rather than the totals for the full Astra project.

Key learnings

Software translation is not just replacing words. The result has to fit the locale, preserve the program’s technical structure, stay consistent with earlier translations, and pass review by volunteers. I also learned to keep “submitted” and “approved” separate when reporting progress.

New skills

  • Using the WordPress translation interface.
  • Following locale terminology and style rules.
  • Preserving placeholders and HTML.
  • Auditing a translation set for consistency.
  • Requesting review through the Polyglots workflow.

Reflection and next steps

Translation gave me a practical way to make a public, measurable contribution without changing WordPress code. The only participation activity still pending is the scheduled WordPress event. After that, I will complete the remaining course closeout steps and respond to any corrections from the translation editors.

Leave a comment