Give Private, Scheduled, None and Parent a context per screen

Open
  • Is something wrong?
#489 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
69/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go, react, typescript
Domain
internationalization, localization

Research direction

Start with the listed usages in frontend/src/content/StatusTabs.tsx, DocumentPanels.tsx, fields.tsx, FieldsPanel.tsx, GroupFieldsDialog.tsx and ParentPicker.tsx; compare their existing msgctxt pattern with Published, Draft and Trash. Add context-specific Spanish and French translations, retire the old POEditor terms with make translations-retire, and pin the Spanish wording in tests. Done means each listed use has the intended context and the tests check the Spanish forms.

Written by the indexing model from the issue text.

Description

enhancement help wanted i18n

What

Give Private, Scheduled, None and Parent a msgctxt at each place that uses them, the way Published, Draft and Trash already carry post status (frontend/src/content/StatusTabs.tsx:40-44). WordPress marks Private and Scheduled the same way, with _x( 'Private', 'post status' ). Today one msgid serves several screens:

  • Private: frontend/src/content/StatusTabs.tsx:43, frontend/src/content/DocumentPanels.tsx:26 and :38, frontend/src/content/fields.tsx:38
  • Scheduled: frontend/src/content/fields.tsx:36
  • None: the parent column in frontend/src/content/fields.tsx:125, frontend/src/content/FieldsPanel.tsx:269 and frontend/src/content/GroupFieldsDialog.tsx:480
  • Parent: frontend/src/content/ParentPicker.tsx:46 and frontend/src/content/fields.tsx:124

Then draft the Spanish and French answer for each context, retire the old terms on POEditor with make translations-retire, and pin the Spanish words in the tests.

Why

Spanish and French words carry a gender, so one answer cannot fit every screen. "Privada" fits an entry, "Ninguno" fits a parent element, and an empty field choice may need yet another form. Today the catalogue has to pick one form for all of them.

Dominant language
Go
Stars
293
Forks
50
Avg merge
20h 45m
Merged PRs (30d)
128

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gopherium/gophenberg

All issues in gopherium/gophenberg

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.