this post was submitted on 15 Feb 2024
25 points (100.0% liked)

Mlem for Lemmy

5379 readers
1 users here now

Official community for Mlem, a free and open-source iOS Lemmy client.

Rules

  1. Keep it civil.
  2. This is a forum for discussion about Mlem. We welcome a degree of general chatter, but anything not related to Mlem may be removed at moderator discretion. This is not a forum for iPhone/Android debate. Posts and comments saying nothing but "iOS bad/I use Android" will be removed as off-topic.
  3. We welcome constructive criticism, but ask that it be both precise and polite.

FAQ

Download Mlem for iOS

GitHub

Website

Donate to Mlem

founded 1 year ago
MODERATORS
 

If I recall correctly, current versions of iOS have a built-in translation engine. Items posted to c/All are in a variety of languages. It would be nice if the user could choose Translate from the … menu when viewing a post.

top 3 comments
sorted by: hot top controversial new old
[–] [email protected] 13 points 6 months ago* (last edited 6 months ago) (1 children)

This would certainly be a useful feature. Unfortunately, Apple does not make their translation API available for us to use, so we'd have to use someone else's API instead. I haven't looked too deeply into potential options just yet, but have created an issue here to keep track of the suggestion 👍

[–] [email protected] 2 points 6 months ago (1 children)

If you allow selecting text in posts, then users can translate from the context menu (along with other benefits such as being able to quote parts of a post more easily). If this is already possible, I haven’t found a way to do it. That would be my preferred way to do it instead of a third party thing.

[–] [email protected] 4 points 6 months ago* (last edited 6 months ago)

Yep, that's another way it could be done. We're hoping to add a text-selecting popup in the next major update, which will make this possible. However, it's not quite as seamless as having a dedicated "Translate" button that replaces the post/comment content inline, which I'd prefer to use if implementing it proves to be feasible.