Skip to content

Translation parity for Pubky/contacts supported languages #911

@piotr-iohk

Description

@piotr-iohk

Problem or use case

Some Pubky profile/contact strings are still inconsistent across iOS and Android (different key names or wording), and recent parity updates need translation coverage.

Proposed solution

Keep this task focused and simple:

  • provide translations for Pubky/contacts strings for all currently supported locales
  • ensure iOS and Android keys/copy are aligned where parity is intended
  • include any missing keys introduced by recent parity PRs

Supported locales (current app localization set):

  • ar, ca, cs, de, el, es, es-419, fr, it, nl, pl, pt, pt-BR, ru

Alternatives considered

N/A

Additional context

N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions