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

Update Simplified Chinese translations #5535

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

LittlePaw365
Copy link

Update Simplified Chinese translations in /i18n/extra/ based on the latest English text.

Some major changes in /i18n/extra/zh-cn.json

  1. Removed ‘型’ in the names of types. ‘型’ is a short form of ‘类型’, which means ‘type’. Removed it to improve the translations of system messages by avoiding redundant in messages like ‘Properties of type [TypeName]’, and allowing it make sense in others like ‘[TypeName] is a type and predefined property …’
  2. Changed ‘具有’ to ‘有’. ‘具有’ usually means that something inherently possesses a certain quality, and often takes abstract things as its object. Changed to ‘有’, which is a more general word that can take both concrete and abstract things as its object.
  3. Changed the format of date precisions to corresponds to the English one.

Update translations based on the latest English text. 

Some major changes
1. Removed '型' in the names of types. ‘型’ is a short form of ‘类型’, which means ‘type’. Removed it to improve the translations of system messages by avoiding redundant in messages like ‘Properties of type [TypeName]’, and allowing it make sense in others like ‘[TypeName] is a type and predefined property …’
2. Changed ‘具有' to '有'. '具有' usually means that something inherently possesses a certain quality, and often takes abstract things as its object. Changed to '有', which is a more general word that can take both concrete and abstract things as its object.
3. Changed the format of date precisions to corresponds to the English ones.
Update Simplified Chinese translations based on the latest English text.
Update Simplified Chinese translations based on the latest English text.
@jeffw16
Copy link

jeffw16 commented Oct 11, 2023

Are these changes also made in the corresponding Traditional Chinese i18n JSONs?

@LittlePaw365
Copy link
Author

Are these changes also made in the corresponding Traditional Chinese i18n JSONs?

I did not modify the Traditional Chinese ones, because I'm not quite sure about some of the word choices in Traditional Chinese. It would be great if you could offer some help.

@jeffw16
Copy link

jeffw16 commented Dec 15, 2023

Sorry for the prolonged delay.

I am not a fluent user of Traditional Chinese. I'm not sure if the word choice necessarily differs. I support just using the mapping if there is an injective mapping present for said character.

It can always be improved later. Better to have slightly incorrect Chinese than English :)

@krabina
Copy link
Contributor

krabina commented Dec 18, 2023

So you suggest to merge this?

@krabina
Copy link
Contributor

krabina commented Jan 12, 2024

@winstonsung can you have a look at this maybe?

'URIResolver' => [ 'URI分解器' ],
'UnusedProperties' => [ '未使用属性' ],
'WantedProperties' => [ '尚缺属性' ],
'URIResolver' => [ 'URI解析器' ],
Copy link
Contributor

Choose a reason for hiding this comment

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

"解析器" means "parser" instead of "resolver"?

Copy link
Author

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

(mark as resolved)

'info' => [ 0, '信息' ],
'concept' => [ 0, '概念' ],
'subobject' => [ 0, '子对象' ],
'smwdoc' => [ 0, 'SMW文档' ],
'smwdoc' => [ 0, 'smw文档', 'SMW文档' ],
Copy link
Contributor

Choose a reason for hiding this comment

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

Magic words aliases are case insensitive.

Copy link
Author

Choose a reason for hiding this comment

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

You're right. I will fix this.

Copy link
Contributor

Choose a reason for hiding this comment

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

(mark as resolved)

'set_recurring_event' => [ 0, '设置循环事件', '设置重复事件' ],
'declare' => [ 0, '声明' ],
'SMW_NOFACTBOX' => [ 0, '__无事实框__' ],
'SMW_SHOWFACTBOX' => [ 0, '__展示事实框__', '__显示事实框__' ],
Copy link
Contributor

Choose a reason for hiding this comment

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

We usually don't use "presentation" (展示) here, is there a reason to use this word first?

Copy link
Author

Choose a reason for hiding this comment

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

Just added as an alias. And in my opinion, "展示" is semantically more accurate here, though "显示" is usually used in the context of UI translation.

Copy link
Contributor

Choose a reason for hiding this comment

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

(mark as resolved)

}
},
"property": {
"labels": {
"_TYPE": "具有类型",
Copy link
Contributor

Choose a reason for hiding this comment

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

Better add to aliases for "具有"?

Copy link
Author

Choose a reason for hiding this comment

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

I will add some not quite wrong legacy translations as aliases.

Copy link
Contributor

Choose a reason for hiding this comment

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

(mark as resolved)

@winstonsung
Copy link
Contributor

winstonsung commented Jan 13, 2024

@winstonsung can you have a look at this maybe?

Done (as commented).

@winstonsung
Copy link
Contributor

(2 resolved, 2 to-do)

"_SUBP": "是……的子属性",
"_SUBC": "是……的子分类",
"_TYPE": "有类型",
"_URI": "等同物URI",
Copy link
Contributor

Choose a reason for hiding this comment

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

"等同物"?

Copy link
Author

Choose a reason for hiding this comment

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

According to the description and example, "equivalent" is a noun here.

Copy link
Contributor

Choose a reason for hiding this comment

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

(mark as resolved)

"_LCODE": "语言代码",
"_TEXT": "文本",
"_PDESC": "属性描述",
"_PVAP": "允许样板",
Copy link
Contributor

Choose a reason for hiding this comment

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

"样板" looks somewhat weird to me here.

"属性约束模式": "_CONSTRAINT_SCHEMA",
"属性配置文件模式": "_PROFILE_SCHEMA",
"有文件附件": "_FILE_ATTCH",
"有翻译":"_TRANS"
Copy link
Contributor

Choose a reason for hiding this comment

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

"翻译" (action) => "译文" (object)?

"_CONT_TITLE": "内容标题",
"_CONT_DATE": "内容日期",
"_CONT_KEYW": "内容关键词",
"_TRANS": "翻译",
Copy link
Contributor

Choose a reason for hiding this comment

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

"翻译" (action) => "译文" (object)?

"小数位数": "_PREC",
"文字": "_TEXT",
"有属性描述": "_PDESC",
"有允许样板": "_PVAP",
Copy link
Contributor

Choose a reason for hiding this comment

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

"样板" looks somewhat weird to me here.

@winstonsung
Copy link
Contributor

(2 issues to be resolved)

@krabina
Copy link
Contributor

krabina commented Feb 19, 2024

I have lost track of this PR. "2 issues to be resolved" means, that it is not finished yet, correct?

@winstonsung
Copy link
Contributor

Not finished.

@krabina krabina added the i18n internationalisation label May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n internationalisation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants