Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(Admin/AI): add docs for translate2 #12120

Merged
merged 1 commit into from
Aug 29, 2024
Merged

feat(Admin/AI): add docs for translate2 #12120

merged 1 commit into from
Aug 29, 2024

Conversation

kyteinsky
Copy link
Contributor

☑️ Resolves

  • Fix #…

🖼️ Screenshots

image
image

@kyteinsky
Copy link
Contributor Author

/backport to stable30

@DaphneMuller
Copy link
Contributor

DaphneMuller commented Aug 23, 2024

Looks good. Under the known limitations:

  • I'm not sure if the first point of "likely to generate false information" applies to a translation model. Is this thing likely to hallucinate and make up information, like a text-generation model does? If not, you can remove this

Add:

  • AI translations are not a replacement for human professional translations and in many cases post-editing is required. AI translations can be used for understanding the main content of a text but not for translations that require special knowledge (such as technical content or legal content), or translations that require specific writing style to convey style, deeper meaning, or emotions (such as marketing content or translating books).
  • While the quality of the output will be fine for the most common languages (English, French, Spanish) the quality will suffer for languages that have less coverage in the original training set.

@kyteinsky kyteinsky enabled auto-merge (squash) August 29, 2024 08:01
@kyteinsky kyteinsky merged commit d4cc23a into master Aug 29, 2024
12 checks passed
@kyteinsky kyteinsky deleted the feat/translate2 branch August 29, 2024 08:11
Copy link

backportbot bot commented Aug 29, 2024

The backport to stable30 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable30
git pull origin stable30

# Create the new backport branch
git checkout -b backport/12120/stable30

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick c0773fb8

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/12120/stable30

Error: Failed to cherry pick commits: error: no cherry-pick or revert in progress
fatal: cherry-pick failed


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants