taskGNU Chinese Translators Team - Tasks: task #15050, update/translation of...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #15050: update/translation of licenses/license-recommendations.html

Submitter:  郭俊余 <hagb>
Submitted:  Sun 23 Sep 2018 12:52:11 PM UTC
   
 
Category:  None Should Start On:  Sat 22 Sep 2018 04:00:00 PM UTC
Should be Finished on:  Fri 09 Nov 2018 04:00:00 PM UTC Priority:  5 - Normal
Status:  Done Privacy:  Public
Assigned to:  None Percent Complete:  100%
Open/Closed:  Closed Effort:  0.00

Jump to the original submission

Sun 01 Dec 2019 12:34:56 PM UTC, comment #26: 

Hi, Hagb:

同意并改正。
我觉得通常链接和连接在网络(超)链接上才有明显区别。
linker也叫连接器。

祝好!
wxie

Wensheng XIE <wxie>
Group administrator
Sun 01 Dec 2019 01:20:18 AM UTC, comment #25: 

Hi, wxie:

Some libraries implement free data formats that are competing against restricted data formats, such as … . The success of the free format requires allowing many proprietary application programs to link in the code to handle the format.
一些实现了自由标准的库与那些限制性标准竞争,例如……。自由标准的成功需要众多专有软件能够 连接自由标准库 来处理数据。

这里所指的“link”,印象中好像一般叫做“链接”。
“自由标准库”我第一次读下来是读成 自由的“标准库”这样的意思…… 我在想是不是“标准”和“库”之间加个“的”能够消除这种可能的歧义。

祝好
Hagb

郭俊余 <hagb>
Group Member
Fri 29 Nov 2019 01:31:20 PM UTC, comment #24: 

Hi, Hagb:

同意你的看法。我这里意思没有译对。
感谢审阅。

已经改成
在这些特殊的情况,我们建议此类处理自由格式的库使用 <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache 2.0 许可证</a>。

祝好!
wxie

Wensheng XIE <wxie>
Group administrator
Wed 27 Nov 2019 09:37:21 AM UTC, comment #23: 

Hi, wxie:

250~255行:
In these special situations, we recommend licensing the library that handles the free format under the <a href=\"http://www.apache.org/licenses/LICENSE-2.0\">Apache License 2.0</a>.
在这些特殊的情况,我们推荐 能够处理自由格式的 <a href=\"http://www.apache.org/licenses/LICENSE-2.0\">Apache 2.0 许可证</a>

我认为这里 that handles the free format 是 the library 的定语,译成“在这些特殊的情况,我们推荐 处理自由格式的库使用 Apache 2.0 许可证 ”或者意思与此相似的译文可能更符合原意。

祝好!
Hagb

郭俊余 <hagb>
Group Member
Sun 28 Jul 2019 08:27:49 AM UTC, comment #22: 

Updated to www.

Wensheng XIE <wxie>
Group administrator
Tue 25 Jun 2019 03:56:00 PM UTC, comment #21: 

Hi, wxie:

使用了书名号,并将引用的文章名改为了现在这些文章名在 gnu 上的中文译文。

祝好!
Hagb

郭俊余 <hagb>
Group Member
Sun 23 Jun 2019 10:00:20 AM UTC, comment #20: 

File is committed into www.

Wensheng XIE <wxie>
Group administrator
Tue 18 Jun 2019 03:20:26 PM UTC, comment #19: 

做了一些修改:将一个破折号改回了正常长度、使某一处更易读懂。

郭俊余 <hagb>
Group Member
Sat 09 Feb 2019 06:55:11 AM UTC, comment #18: 

File is reviewed and committed into www.

Wensheng XIE <wxie>
Group administrator
Fri 08 Feb 2019 02:59:46 AM UTC, comment #17: 

Hi,wxie:

已更新译者信息。

新年快乐
Hagb

郭俊余 <hagb>
Group Member
Sat 12 Jan 2019 12:59:58 PM UTC, comment #16: 

Hi, Hagb:

perfect.

The unpdated file is committed into www.
Happy end-term exams.

best regards,
wxie

Wensheng XIE <wxie>
Group administrator
Fri 11 Jan 2019 05:35:51 PM UTC, comment #15: 

Hi, wxie:

译者已经同意将其名字和联系方式列出。请将其写入 “GNUN-SLOT: TRANSLATOR'S CREDITS” 中。之后的同步中我会参照这次的格式填写 GNUN-SLOT: TRANSLATOR'S CREDITS。

祝好
Hagb

郭俊余 <hagb>
Group Member
Mon 31 Dec 2018 12:45:32 PM UTC, comment #14: 

Hi, Hagb:

committed into www.

元旦快乐!
祝2019年学习进步!

wxie

Wensheng XIE <wxie>
Group administrator
Mon 31 Dec 2018 05:52:04 AM UTC, comment #13: 

Hi,wxie:

补上了 GNUN-SLOT: TRANSLATOR'S CREDITS 里的换行

元旦快乐!
Hagb

郭俊余 <hagb>
Group Member
Sun 30 Dec 2018 12:43:14 PM UTC, comment #12: 

Hi, Hagb:

FIRST AUTHOR <EMAIL@ADDRESS>, YEAR 里 YEAR 要填哪个年份?
==>
我理解是应该填FIRST AUTHOR提交发布的年份。

元旦快乐!
wxie

Wensheng XIE <wxie>
Group administrator
Sun 30 Dec 2018 09:24:56 AM UTC, comment #11: 

Hi,wxie:

请问 FIRST AUTHOR <EMAIL@ADDRESS>, YEAR 里 YEAR 要填哪个年份?

元旦快乐!
Hagb

郭俊余 <hagb>
Group Member
Fri 23 Nov 2018 11:36:21 PM UTC, comment #10: 

Hi, Hagb:

译者不答复的情况下是否将其写入 GNUN-SLOT: TRANSLATOR'S CREDITS ?
==>这个我觉就先按你写的BLUG吧,作为一个团体,应该问题不大。BLUG也被知会了。
一般情况下,写个人名称/邮件时须征得同意,因为这个会在网页上公开的。

另:写在#区,问题不大,这个不会直接公开。

祝好!
wxie

Wensheng XIE <wxie>
Group administrator
Fri 23 Nov 2018 03:12:12 PM UTC, comment #9: 

Hi,wxie:

译者仍未答复……
译者不答复的情况下是否将其写入 GNUN-SLOT: TRANSLATOR'S CREDITS ?

谢谢
Hagb

郭俊余 <hagb>
Group Member
Sun 11 Nov 2018 09:48:26 AM UTC, comment #8: 

Hi,wxie:

2 =>
着急起来就忘记了……是否是指该篇文章的译者呢?我问他是否愿意列出名字,但是还没得到答复。译者是:Vimacs <vimacs.hacks@gmail.com>

另外请把文中的“GNU all-permissive license”的翻译改一下吧(我现在没有操作环境)。

谢谢
Hagb

郭俊余 <hagb>
Group Member
Sat 10 Nov 2018 12:57:55 PM UTC, comment #7: 

感谢Hagb.

Reviewed checked into www and www-zh-cn.

注意:
1. po文件最上面的#行也需要更新的——在emacs的po-mode用shift+#就可以更新。
2. #行里的First translator应该写为BLUG,不知道你有没有联系人?
3. fuzzy行翻译好后,可以在emacs的po-mode用tab键消去。

Wensheng XIE <wxie>
Group administrator
Sat 10 Nov 2018 02:36:16 AM UTC, comment #6: 

Hi, wxie:

已经审校完了,文件已提交至版本库。
请看看 GNUN-SLOT: TRANSLATOR'S CREDITS 里填的有没有问题?

谢谢
Hagb

郭俊余 <hagb>
Group Member
Sat 03 Nov 2018 05:03:43 AM UTC, comment #5: 

Hi, wxie:

现在可以说已经审校完毕了。等和 BLUG 那边确认好了并且明确一些还不明确的地方之后就同步到过来(下周)。

祝好!
Hagb

郭俊余 <hagb>
Group Member
Sat 27 Oct 2018 12:43:12 PM UTC, comment #4: 

Hi, hagb:

没问题的。
我们需要的是长期坚持。

祝好!
wxie

Wensheng XIE <wxie>
Group administrator
Sat 27 Oct 2018 04:21:25 AM UTC, comment #3: 

因语言水平和业余时间所限,这个审校比较缓慢。

郭俊余 <hagb>
Group Member
Mon 22 Oct 2018 12:49:20 AM UTC, comment #2: 

“For honesty's sake”是“出于诚实”或者类似的的意思吗?感觉放在这个语境下读不通。

原文:
If you choose to release your contributions under a different license for whatever reason, you must make sure that the original license allows use of the material under your chosen license. For honesty's sake, show explicitly which parts of the work are under which license.

我的看法:
For honesty's sake, show explicitly which parts of the work are under which license.
应该理解为
For honesty's sake, (please) show explicitly which parts of the work are under which license.
为了诚实起见,请明确指出该作品的哪个部分使用了哪个许可证。

Wensheng XIE <wxie>
Group administrator
Mon 01 Oct 2018 02:17:03 PM UTC, comment #1: 

已经写入.po文件。
我来做接下来的工作:处理差异和进行审校。

郭俊余 <hagb>
Group Member
Sun 23 Sep 2018 12:52:11 PM UTC, original submission:  

同步 BLUG 的译文

郭俊余 <hagb>
Group Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by wxie (Posted a comment)
  • -email is unavailable- added by hagb (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 25 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-01-24 wxie Open/ClosedOpen Closed
    2019-12-01 wxie StatusReady For Test Done
        Assigned towxie None
    2019-12-01 hagb StatusDone Ready For Test
        Assigned toNone wxie
        Open/ClosedClosed Open
    2019-11-29 wxie StatusReady For Test Done
        Assigned towxie None
        Open/ClosedOpen Closed
    2019-11-28 hagb Open/ClosedClosed Open
    2019-11-27 hagb StatusNone Ready For Test
        Assigned toNone wxie
    2019-07-28 wxie Assigned towxie None
    2019-06-25 hagb StatusDone None
        Assigned toNone wxie
    2019-06-23 wxie StatusNeed Info Done
        Assigned towxie None
    2019-06-22 wxie StatusDone Need Info
        Assigned toNone wxie
    2019-02-09 wxie StatusReady For Test Done
        Assigned towxie None
    2019-02-08 hagb StatusDone Ready For Test
        Assigned toNone wxie
    2018-11-10 wxie Percent Complete90% 100%
        Assigned towxie None

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code