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

A bit optimized. #14

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

A bit optimized. #14

wants to merge 1 commit into from

Conversation

evrmji
Copy link

@evrmji evrmji commented Jan 5, 2020

Optimized the translation and expression of Chinese

Optimized the translation and expression of Chinese
@libgenapps
Copy link
Owner

Looks good but I would like @VaslD to take a look as well.

@VaslD
Copy link
Contributor

VaslD commented Jan 24, 2020

Thank you evrmji. Please correct the following issues, which I consider grammatical or critical:

  • 请不要在中文语句中使用英文标点, 例如这样. Don't use English punctuation: ... should be or ……, () should be (), etc. You may need a good text editor to see issues like this.
  • 请不要像这句话一样用 空格 将 专有名词(英语中通常需要首字母大写的名词)与句子中的其它部分隔开;建议像这样使用“引号”。 Don't use space to separate Named Entities, such as Proper Nouns, from the rest of the sentence. I don't think I see many day-to-day examples that do this. If you feel it's important to make sure people know that Something Like This is a button, tab or status, consider enclosing in quotes.
  • 如果之前很简短的翻译修改后被加长(例如:OCR > OCR(光学文字识别)),请运行一遍 Libgen Desktop 看一下实际效果。有些布局设计导致长度很长的翻译显示效果极差。 If you extended a previously very short translation to a longer version, do run Libgen again and see what the new translation looks like. Some UI elements, such as table headers and tooltips, don't look good when populated with a full sentence. Consider using my version if weirdness happens, I know it may not sound that good but at least it gets the job done in the limited space.

I'm on mobile so I'll do a full proofread when I get home.

Copy link
Contributor

@VaslD VaslD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for writing more specific comments in Chinese. I think a feedback in target language communicates better with translators.

I apologize for being too picky on details.

"CreatingIndexes": "正在创建索引",
"LoadingIds": "正在加载标识符",
"ImportingData": "正在导入数据",
"Step": "共 {total} 第 {current} 步",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“第 {1} 步,共 {2} 步”是 Windows 平台中文化进度描述的习惯,非特殊情况(标点或文字空间限制)下不建议修改。如有需要请说明更改此习惯用法的原因?

Comment on lines +297 to +300
"DataLookup": "查询表结构定义..",
"CreatingIndexes": "建立索引...",
"LoadingIds": "加载标识符...",
"ImportingData": "导入数据...",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

请使用中文标点。全文件有多次混用,不再重复创建 Review。

Comment on lines +413 to +414
"Dpi": "DPI(分辨率)",
"Ocr": "OCR(光学字符识别)",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • 建议使用中文标点。

  • OCR 是个勾选列的表头,写明全称有些长了。

    LibgenDesktop_2020-01-24_20-22-13
  • DPI 也有一点类似问题,但是长度还不太明显。

    LibgenDesktop_2020-01-24_20-27-21

"MainMenu":
{
"DownloadManagerTooltip": "下载",
"BookmarksTooltip": "书签",
"NoBookmarks": "无书签",
"NoBookmarks": "",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

直接写“空”会让弹出窗口有些莫名其妙吧?

2020-01-24_20-31-20

"DatabaseCorrupted": "数据库“{database}”已损坏。",
"LibgenServerDatabase": "“{database}” Libgen 服务器所用数据库,由于格式不同,不能用于 Libgen 桌面版。",
"LibgenServerDatabase": "“{database}”数据库为 Libgen 服务端专用的,格式不同,不能用于 Libgen 桌面。",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

建议去掉“的”,也能通顺。中文能不使用“XXX 是 YYY 的”尽量换一种写法,这种用法是英语习惯(的),汉语念出来会有些别扭(的)。

@@ -453,7 +453,7 @@
"Month": "月",
"Day": "天",
"Volume": "卷册",
"Issue": "期刊",
"Issue": "发行",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

其实我也不知道此处应该如何翻译,这是个中英文语序差异。

英语文化中序数词可以以数字形式标在所形容物体之后:例如 "the 30th issue" >> "Issue 30",中文最佳说法应还是“第 30 期”,并没有类似“期刊 30”这种说法。而 "Issue 30" 写成变量形式 "Issue: {1}" ("Issue: 30") 之后中文就不好单独翻译 "Issue" 了。

实话说“期刊”的翻译并不好。如果要改为“发行”,请咨询一下经常阅读中外科学杂志的人确保这种说法易于理解并且符合使用习惯。

@@ -591,28 +591,28 @@
"DownloadProgressKnownFileSize": "已下载 {downloaded}/{total} B ({percent}%)",
"DownloadProgressUnknownFileSize": "已下载 {downloaded} B,总大小未知",
"Log": "日志",
"TechnicalDetails": "技术细节",
"TechnicalDetails": "细节(开发者)",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

更改此翻译的理由?

"EnableSqlDebugger": "启用 SQL 调试器"
}
},
"About":
{
"WindowTitle": "关于 Libgen 桌面版",
"ApplicationName": "Libgen 桌面版",
"Version": "版本:{version},发布时间:{date}",
"Version": "版本:{version},发布:{date}",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

一定要更改“发布时间”的话,也把“发布”改成“发布于”吧?

"TransformationError": "传输信息: {transformation} 失败.",
"TransformationReturnedIncorrectUrl": "Transformation {transformation} 返回了无效的 URL.",
"Attempt": "共 {total} 第 {current} 次尝试",
"MaximumDownloadAttempts": "超过重试次数。",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“超过重试次数”有些别扭。“重试次数”就是重试过的次数,怎么超过呢?新翻译并没有比旧翻译好。

"TransformationReturnedIncorrectUrl": "Transformation {transformation} returned an invalid URL.",
"Attempt": "第 {current} 次尝试(共 {total} 次)",
"MaximumDownloadAttempts": "重试次数超限。",
"OfflineModeIsOn": "离线模式已启用。",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

”打开“或”启用“请统一用词,请修改其它表示功能已经可以使用或正在生效的描述。

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

Successfully merging this pull request may close these issues.

3 participants