ipfs / ipfs/i18n

Generic "pt" vs "pt-PT" and "pt-BR"

Open
#7 6 comments 2 reactions 0 assignees View on GitHub
help wanted kind/discussion
Dominant language
No language data
Stars
24
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Now and then, someone requests adding `pt-BR` "Portuguese (Brazil)" to our translation projects at Transifex.

Until now I believed country-specific variants of Portuguese do not differ as much as Chinese ones, so it was more efficient to deduplicate efforts and focus on a single, generic locale:

- https://www.transifex.com/ipfs/dashboard/all_projects/pt/

I don't speak Portuguese myself, so hereby I summon some native speakers active in IPFS community (including managers of js.ipfs.io website) to weight on this :-)

@satazor @hugomrdias @PedroMiguelSS @hacdias @fsdiogo @pgte @daviddias
@agentofuser @dntxos

### Question:

- Are differences between `pt-PT` and `pt-BR` in written language big enough to justify duplicated efforts?
- Would be useful to provide examples of existing translations that would look different in `pt-BR`
- Perhaps its just a few labels that we could work around by creating a generic glossary?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.