Comments (17)
我把 Chapter 1 调整了新的格式,你看一下这样行不行?
我觉得挺好的,后续全部改为这样的方式吧!
from software-engineering-at-google.
这样的 Markdown 布局好像不太方便阅读
已经全部修改完毕了,可以关闭了
from software-engineering-at-google.
这样的 Markdown 布局好像不太方便阅读
这是注解部分,我们本意是与正文区分开来,如果有更好的布局方式,我们可以一起尝试看看。
from software-engineering-at-google.
建议可以这样写,用 >
达成缩排效果!
事实上,很难设想任何可以被认为是现代软件工程的任务不立即采用VCS。鉴于你了解版本控制的价值和需要,你现在可能会问你需要什么类型的版本控制。
3 Indeed, I’ve given several public talks that use “adoption of version control” as the canonical example of how the norms of software engineering can and do evolve over time. In my experience, in the 1990s, version control was pretty well understood as a best practice but not universally followed. In the early 2000s, it was still common to encounter professional groups that didn’t use it. Today, the use of tools like Git seems ubiquitous even among college students working on personal projects. Some of this rise in adoption is likely due to better user experience in the tools (nobody wants to go back to RCS), but the role of experience and changing norms is significant.
3 事实上,我曾多次公开演讲,以 "版本控制的采用 "为例,说明软件工程的规范是如何随着时间的推移而演变的。根据我的经验,在20世纪90年代,版本控制被理解为一种最佳实践,但没有得到普遍遵守。在21世纪初,不使用版本控制的专业团体仍然很常见。今天,即使在从事个人项目的大学生中,像Git这样的工具的使用似乎也是无处不在的。这种采用率的上升可能是由于在工具中更好的用户体验(没有人愿意回到RCS),但经验和不断变化的规范的作用也很重要。
from software-engineering-at-google.
建议可以这样写,用
>
达成缩排效果!事实上,很难设想任何可以被认为是现代软件工程的任务不立即采用VCS。鉴于你了解版本控制的价值和需要,你现在可能会问你需要什么类型的版本控制。
3 Indeed, I’ve given several public talks that use “adoption of version control” as the canonical example of how the norms of software engineering can and do evolve over time. In my experience, in the 1990s, version control was pretty well understood as a best practice but not universally followed. In the early 2000s, it was still common to encounter professional groups that didn’t use it. Today, the use of tools like Git seems ubiquitous even among college students working on personal projects. Some of this rise in adoption is likely due to better user experience in the tools (nobody wants to go back to RCS), but the role of experience and changing norms is significant.
3 事实上,我曾多次公开演讲,以 "版本控制的采用 "为例,说明软件工程的规范是如何随着时间的推移而演变的。根据我的经验,在20世纪90年代,版本控制被理解为一种最佳实践,但没有得到普遍遵守。在21世纪初,不使用版本控制的专业团体仍然很常见。今天,即使在从事个人项目的大学生中,像Git这样的工具的使用似乎也是无处不在的。这种采用率的上升可能是由于在工具中更好的用户体验(没有人愿意回到RCS),但经验和不断变化的规范的作用也很重要。
第一章已经被修改为引用方式,可以对照一下效果。
from software-engineering-at-google.
from software-engineering-at-google.
我今天看到 Footnotes now supported in Markdown fields 这份文档,我觉得这语法虽然不支持在 Markdown 文档中使用,只能用在 Issue 与 Gist 里面,但我觉得这样的格式蛮好的,更清楚的标示他是一个注脚。
Here is a simple footnote1. With some additional text after it.
Footnotes
-
My reference.
↩
from software-engineering-at-google.
我今天看到 Footnotes now supported in Markdown fields 这份文档,我觉得这语法虽然不支持在 Markdown 文档中使用,只能用在 Issue 与 Gist 里面,但我觉得这样的格式蛮好的,更清楚的标示他是一个注脚。
Here is a simple footnote1. With some additional text after it.
Footnotes
- My reference.
↩
在https://github.com/qiangmzsx/Software-Engineering-at-Google/blob/main/zh-cn/Chapter-21_Dependency_Management/Chapter-21_Dependency_Management.md#user-content-fn-3-65093b4d140a2ca10c285f3aadcc0f0e 我们已经使用了注释链接方式。我们可以把两者结合使用。
from software-engineering-at-google.
我把 Chapter 1 调整了新的格式,你看一下这样行不行?
from software-engineering-at-google.
@qiangmzsx 有全改吗?我好像还看到旧的布局格式?
等等,这应该不是「注脚」的部分,不过我觉得应该也要改成 >
的布局方式才好看。
from software-engineering-at-google.
@qiangmzsx 有全改吗?我好像还看到旧的布局格式?
等等,这应该不是「注脚」的部分,不过我觉得应该也要改成
>
的布局方式才好看。
原文也没有使用引用的方式:
如果有更好的样式,可以验证试试。
from software-engineering-at-google.
其实「注脚」的布局应该跟「引用」的布局不太一样。但是 GitHub 的 Markdown 文档不支持「注脚」样式,所以我们才退而求其次的使用「引用」的方式来呈现,呈现上也不会觉得奇怪。
你的截图就是确确实实的「引用」样式,我认为 Markdown 也可以用这种格式来呈现,这种方式才不会让文章出现 horizontal scrollbar,阅读上也比较舒适。
from software-engineering-at-google.
看着不是很舒服。可以看看是否还有更好的方式。
from software-engineering-at-google.
我觉得蛮舒服的
无论如何,我觉得比出现 horizontal scrollbar 舒服多了!
from software-engineering-at-google.
我觉得蛮舒服的
😄 无论如何,我觉得比出现 horizontal scrollbar 舒服多了!
你可以提交PR修改看看效果
from software-engineering-at-google.
我修了 Ch6 与 Ch7,你看一下这样可以吗?
from software-engineering-at-google.
我修了 Ch6 与 Ch7,你看一下这样可以吗?
可以的,已经合并了
from software-engineering-at-google.
Related Issues (11)
- trade-off 个人觉得翻译为「权衡」更合适些 HOT 4
- 只有我在线阅读地址打开是白页吗? HOT 1
- 軟體工程
- 非常好的项目!如果能单独读英文或单独读中文就好了。 HOT 3
- 是否能够构建单独的中文版本 HOT 4
- 目录标题建议统一成不带冒号 HOT 1
- 请先介绍一下版权问题 HOT 10
- 生成page的workflow介意分享一下吗? HOT 7
- 是否可以开启 GitHub Sponsor? HOT 1
- chapter 5 有人翻译吗? HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from software-engineering-at-google.