Date: Sat, 22 Oct 2022 18:17:46 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 267274] Please remove the zh-CN Handbook of the current FreeBSD website Message-ID: <bug-267274-9@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267274 Bug ID: 267274 Summary: Please remove the zh-CN Handbook of the current FreeBSD website Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Books & Articles Assignee: doc@FreeBSD.org Reporter: yklaxds@gmail.com The simplified Chinese translation of the handbook on the FreeBSD website is now about a decade out of date overall: https://docs.freebsd.org/zh-cn/books/handbook/=20 Outdated articles often give many misconceptions to newcomers to FreeBSD th= at the development of FreeBSD has stalled. The overall structure of the Handbook is all wrong. Also, I was unable to participate in the translation of the FreeBSD documentation group because i= ts translation schedule was 100% - because the old documentation was not completely removed. Small fixes are no longer useful and we have to start translating the Handbook from scratch. The documentation and websites in FreeBSD now use the AsciiDoc syntax, so if you want to translate it you have to use a command to convert it to a .po f= ile and then use software like poedit to translate it. There are many problems = with this step. Many of us don't know AsciiDoc syntax, only simple Markdown synt= ax. The .po file cannot determine exactly what changes have been made upstream,= on which lines and in which characters. If several paragraphs in the document = were completely removed upstream of FreeBSD and several different paragraphs were added, then the problem would be even greater and the entire paragraph woul= d be misplaced. And generating .po files for three dozen files at a time is tedi= ous and painful - I've done it more than once when I've tried to translate Free= BSD websites, and there are even thousands of .po files in there that need to be generated manually. Even if there were a script that could generate them on= e by one, it would be difficult to determine the scope of the changes and what exactly they were. For Chinese, some of the English changes are meaningless, meaning that the tense or singular and plural are not represented by indivi= dual words, but by the whole sentence. I understand that this is necessary but it does not help our translation. I tried to use poedit to translate, but I so= on realized that it was unrealistic, that it didn't show me the changes I had = made in real-time, that I didn't know where the errors were, that it was a paywa= re program and I had paid for it, but the author of poedit told me that I was making a lot of money with his program because he had seen me translate more strings than he had expected with his program But the truth is that I make a lot of money from it every time I open it. But the truth is that every time= I open this software, it starts to translate automatically. The changes I made to it were to translate the Handbook into Simplified Chi= nese into Markdown syntax, keeping it as close to AsciiDoc syntax as possible. I also deployed it to the server using vuepress and GitHub. The PDF export function is also supported. This way, even those who do not have access to GitHub can forward their translations to me via text files. Markdown syntax= is easy to learn and can be mastered in five minutes, as there is no need to master complex syntax such as HTML nesting, which is barely covered in the article. Also, as far as updates go, just create a new GitHub repository for only the Handbook adoc files upstream of FreeBSD. After some time (usually a month), then delete the original content and put it in the new adoc file, a= nd GitHub will automatically show the difference between the two. You can then compare the changes.=20 Simplified Chinese translations of documents are now deployed in https://handbook.bsdcn.org/ . The documentation is located at https://github.com/FreeBSD-Ask/Handbook . The source code for the Document Deployment website is located at https://github.com/FreeBSD-Ask/Handbook-Next In summary, please consider removing the now obsolete Handbook from the Fre= eBSD website.And, if possible, can it be linked to https://handbook.bsdcn.org/ ? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267274-9>