Multi-language Translation: a Tokeny case study
Translate documents into multiple languages with automatic grammar and expression proofreading. Follow the recorded task, execution screenshots, actual files and verification notes.
By the Tokeny team · Windows · Tokeny 1.7.8 · gpt-6-sol
Prepare the inputs
Create a separate workspace in Tokeny, download and unpack the sample inputs, then select a model that supports tools. The sample uses synthetic data or the public sources named in the article.
- manual.md
Send the task to Tokeny
The original task was executed in Chinese. Copying these instructions reproduces the same task; the results below include an English report.
将中文版使用说明译成英文和日文，保留数字、产品名称和语义；提供术语表以及逐项校对说明。 交付文件：manual.en.md、manual.ja.md、glossary.csv。 验收要点： - 两种语言都有 3 人限制与删除前导出提示 - 营业时间和时区不变 这是使用合成演示输入或指定公开资料的真实操作案例。请先读取工作空间输入，再实际生成文件并自检。所有写入、脚本与临时服务限于当前工作空间；临时服务只监听 127.0.0.1，执行后关闭；不触达外部收件人、不发布、不付款、不更改系统设置，不调用子智能体。需要公开资料时可读取给定 URL。只启用完成任务必需的工具。另写 report.md（中文）和 report.en.md（英文），每份 400–800 字，包含输入、处理步骤、真实结果、检查方式和局限；失败或未验证部分如实记录，不能宣称成功。最终回复用中文列出产物、关键结果与待核实项。
The recorded run used an isolated demonstration workspace. Review the commands and file paths before approving operations in your own workspace.
What actually ran
The task was submitted through the Tokeny input box. An online model read the inputs and executed tools. This run covers the local sample task and its actual files. Results and checks are recorded below.
Results and verification
Input
The only business input processed was manual.md in the workspace. It is a five-line quick-start manual titled “松果任务板快速使用.” The source contains three ordered actions: create a workspace and invite up to 3 members; create a new task and enter the assignee and due date; and export a CSV file in Settings. It also states that the Free plan does not provide automatic backups, instructs the user to export before deleting a task, and gives customer service hours as 09:00–18:00 on business days (Beijing Time). ENVIRONMENT.md was read only as an environment note and was not treated as business content.
Processing Steps
I read the source line by line and identified information that must remain stable: the product identity, the number 3, the CSV format, the plan limitation, the pre-deletion export warning, the business-day scope, the service hours, and the time zone. I then created manual.en.md and manual.ja.md, keeping the Markdown heading, numbered steps, step order, numerals, and time notation. In English, “负责人” is translated as “assignee” and “截止日期” as “due date.” In Japanese, these are “担当者” and “期限.” The source product name “松果任务板” is retained in both translated headings; the glossary additionally provides “Songguo Task Board” and “松果タスクボード” as explanatory renderings. I also created glossary.csv with 16 core terms, their English and Japanese equivalents, and usage notes.
Actual Results
All three requested translation assets and both reports were written to the current workspace. Both language versions explicitly contain the limit of up to 3 members, the Free-plan automatic-backup limitation, the instruction to export before deletion, CSV export, and customer service hours of 09:00–18:00 on business days in Beijing Time. No external public source was needed or accessed. No messages were sent, content was published, payment was made, or system setting was changed.
Verification Method
I compared the source and both translations item by item for the product expression, numeric value, CSV label, backup limitation, deletion warning, service hours, business-day scope, and time-zone meaning. I also checked that the glossary has a header row and consistent comma-separated records, and that all five deliverables exist and are non-empty.
Limitations
This was a translation exercise based on synthetic demonstration input, not a verification of a live product interface. I did not perform native-speaker review, glossary-import testing, or renderer compatibility testing. The glossary’s English and Japanese explanatory renderings are semantic choices; the source product name is retained in the manuals. if the product team has official localized brand names, those names should replace the current forms and be reviewed before publication.
Download and inspect the outputs
The archive contains the files created during this run. Use these checks when adapting the example to your own data.
- Reconcile the reported results against the downloadable sample inputs.
- Open the generated files and check the contents relevant to your task.
- Review the limitations and any unverified steps in the report.