Skip to content

Conversation

@ZYSzys
Copy link
Member

@ZYSzys ZYSzys commented Nov 9, 2018

Refs: #1890

/cc @nodejs/nodejs-cn

@willin willin requested a review from a user November 9, 2018 00:52
current: 'Current'
pending: 'Pending'
maintenance: '长期支持版(维护)'
active: '长期支持版(活跃)'
Copy link
Contributor

Choose a reason for hiding this comment

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

It reads awkwardly. but i have no idea how to figure it out. @Maledong

wx20181109-084422 2x

p.s. 注意一下前人翻译的术语。 长期维护版

Copy link
Member Author

Choose a reason for hiding this comment

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

对于这两个词的翻译我也有点纠结,翻译还是保留原版英文,等待你们提供修改意见

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.

因为都是在 LTS 下分的两个阶段,所以感觉似乎。。。我没找到合适的词来形容

Copy link
Contributor

Choose a reason for hiding this comment

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

稳定版 & 最新版?

We had a long discussion before on how to call "Current" version. The word "Current" is the out come of the discussion and so I don't think we should have the same discussion again when we translate. So I think we can keep the direct translation here:

11.1.0 当前版 最新功能

Copy link
Member Author

Choose a reason for hiding this comment

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

current => 当前版, 那么 Maintenance LTSActive LTS 应该如何翻译呢 ?

Maintenance LTS => 当前版 ?
Active LTS => 最新功能 ?

Copy link
Contributor

@stevemao stevemao Nov 9, 2018

Choose a reason for hiding this comment

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

Your current changes look fine to me:

maintenance: '长期支持版(维护)'
active: '长期支持版(活跃)'

@stevemao stevemao added the i18n Issues/PRs related to the Website Internationalisation label Nov 9, 2018
@stevemao
Copy link
Contributor

@ZYSzys I think you can take the last commit to a new PR against the master branch. This PR is against feature/lts-release-plan which might take longer to merge I think.

@stevemao
Copy link
Contributor

also 最新发布版 should probably be 当前版 (it was called latest before but changed).

Copy link
Contributor

@stevemao stevemao Nov 10, 2018

Choose a reason for hiding this comment

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

This should also be 其它当前版下载

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

1、LTS的全称是“Long Term Support”,翻译成“长期支持”不错。

2、Maintance LTS:根据时间表看,说明这个LTS版本不是作为在首页上出现的主要版本推广(不是主推的,但是处于维护阶段)。
3、Active LTS:活跃长期支持版(推荐的,在Nodejs主页上显示的)。

根据实际情况使用下来,建议意译更好:

1)Active LTS:长期支持版(主推)
2)Maintance LTS:长期维护版

@stevemao :Active LTS,从字面上翻译的确是“活跃的长期支持版”,但是我觉得这样翻译太过于直白,而且不符合中国人的思维习惯——其实“活跃的长期支持版”意味着这个版本是当前在Nodejs主页上主要推荐的,所以我大胆地翻译成“主推长期支持版”。

至于Maintance LTS,其实已经是过了“保鲜期”到了“维护期”(参考Nodejs10.X作为主推版之后,Nodejs8.x进入了维护阶段)。所以为了区分两者,建议后者翻译成“长期维护版”,没有必要再把“支持”翻译出来了。

@ZYSzys
Copy link
Member Author

ZYSzys commented Nov 10, 2018

@Maledong 改好了,现在这样如何 ?

@ghost
Copy link

ghost commented Nov 10, 2018

谢谢!
稍等,让其他人看看,@stevemao?因为这个是大家讨论的,如果我的意见大部分人无法接受就多数人决定为准,所以保险起见还是问一下比较好呢 :)

@stevemao
Copy link
Contributor

Thanks! I'm neutral on these :)

@ghost ghost merged commit 372be71 into nodejs:feature/lts-release-plan Nov 11, 2018
@fhemberger
Copy link
Contributor

Thank you!

fhemberger pushed a commit that referenced this pull request Nov 11, 2018
1. Add release schedule

2. Current => 当前版

3. Translate maintenance & active
@ZYSzys ZYSzys deleted the feat branch November 12, 2018 05:09
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

i18n Issues/PRs related to the Website Internationalisation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants