Make fe more i18n-friendly #1111

Open
opened 2021-09-10 13:43:28 +00:00 by tusooa · 0 comments
Owner

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)

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)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma-fe#1111
No description provided.