[feat] Add separate "Posting language" setting #750

Closed
opened 2024-04-20 11:46:32 +00:00 by partizan · 5 comments

The idea

I want to specify "Posting language" independent of my "Interface language".

The reasoning

I'm using English as interface language, but mostly post in Ukrainian and having this two settings as separate makes sense.

I have found one post on forums mentioning this: https://meta.akkoma.dev/t/mastodon-features/42/3

Have you searched for this feature request?

  • I have double-checked and have not found this feature request mentioned anywhere.
  • This feature is related to the Akkoma backend specifically, and not pleroma-fe.

This feature is related to backend first, but also needs to be implemented on frontend.

### The idea I want to specify "Posting language" independent of my "Interface language". ### The reasoning I'm using English as interface language, but mostly post in Ukrainian and having this two settings as separate makes sense. I have found one post on forums mentioning this: https://meta.akkoma.dev/t/mastodon-features/42/3 ### Have you searched for this feature request? - [x] I have double-checked and have not found this feature request mentioned anywhere. - [ ] This feature is related to the Akkoma backend specifically, and not pleroma-fe. This feature is related to backend first, but also needs to be implemented on frontend.
partizan added the
feature request
label 2024-04-20 11:46:32 +00:00
Author

If you find this useful, but have other priorities, i can try to implement this myself and add a PR. But please tell me where to start, and maybe provide general instructions.

(I'm mostly write in python/vue, but always wanted to try Elixir)

If you find this useful, but have other priorities, i can try to implement this myself and add a PR. But please tell me where to start, and maybe provide general instructions. (I'm mostly write in python/vue, but always wanted to try Elixir)

this is already implemented on both the front and backed

the only real thing that could be added would be a default for the drop-down

this is already implemented on both the front and backed the only real thing that could be added would be a default for the drop-down
Author

Yes, i'm talking about default for the drop-down.

Probably somewhere here:

image

Is there need to add something to backend here? or can this be implemented fully on front-end?

Yes, i'm talking about default for the drop-down. Probably somewhere here: ![image](/attachments/60f726e1-7ab6-4f69-93e7-4364f1869535) Is there need to add something to backend here? or can this be implemented fully on front-end?

this could be done entirely frontend in theory

this could be done entirely frontend in theory
Author

Very good, thanks.

Very good, thanks.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
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: AkkomaGang/akkoma#750
No description provided.