FreeCAD / FreeCAD/FreeCAD-Homepage

Stop using AI translation in wiki.

Open
#355 7 comments 0 reactions 0 assignees View on GitHub
Dominant language
CSS
Stars
88
Forks
71
PR merge metrics
No merged PRs in 30d

Description

I didn't find a proper way to get contact with the document maintainers, so just start a issue here.

This is the screenshot on [release note in Chinese language on wiki](https://wiki.freecad.org/Release_notes_1.1/zh):

Image

In case you don't know Chinese, here are what the two underscored lines means:

the first one:

> 好的,这是简体中文翻译:

This means

> Ok, here is the Traditional Chineses translation:

the second one:

> 要不要我把这些PR的**核心改动点**整理成一份更易懂的中文总结?

This means:

> Need me to organize **core changes** of these PRs into a more understoodable summary in Chinese?

THIS IS PURE RUBBISH AND NOT ACCEPTABLE.

If you don't have hands to do such work like translation that is fine. I believe someone from the community would do this (maybe myself if I have enough time and knowledge of FreeCAD). And even no one would do this, it's still fine, because I believe if a people speaking Chinese is able to access this article, he would be able to read in English (like myself). And even only removing these AI generated contents apart of translations is still OK for me, currently AI does do a good translation job.

But leaving these two sentence here makes me feel like being fooled and can not read the doc anymore.

I noticed that we have a website repositry now, I hope things like this will not happen again. Either translate by someone who speaks chinese, or support English content only for now, or at least to have someone check these AI generated contents.

Contributor guide

Open the contributing guide

Research direction

Start with the linked Chinese release-notes page on the FreeCAD wiki and inspect the surrounding translated content. Remove or replace the two identified AI-generated sentences without changing valid translation, then verify the rendered page no longer shows the unwanted boilerplate.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.