Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pleroma-fe pleroma-fe
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 310
    • Issues 310
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 42
    • Merge requests 42
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Pleroma
  • pleroma-fepleroma-fe
  • Issues
  • #1111

Closed
Open
Created Sep 10, 2021 by Tusooa Zhu@tusooaContributor

Make fe more i18n-friendly

Currently a lot of places in FE has put only segments for translation, ignoring the sentence or phrase structure. This is not particularly not friendly to languages with a word order other than SVO.

For example ([xxx] = i18n text)

Current                              Desired
[Reply to] {account}                 [Reply to {account}]
[Mentions] {accounts}                [Mentions {accounts}]
[Replies:] {ids}                     [Replies: {ids}]
{thread-muted}[, has words:] {words} [Thread muted, has words: {words}]
{account} [(You)]                    [{account} (You)]                   // self-mention tag in status

Using the <i18n> component instead of the $t() function will be desirable here (as some examples here represent links)

Assignee
Assign to
Time tracking