Status
Progress: Completed (2016.5.23)
Official Document: http://www.w3.org/TR/2011/REC-CSS2-20110607/
W3C Index: https://www.w3.org/2005/11/Translations/Query?titleMatch=css+2.1&lang=zh-hans&search1=Submit
Chinese Translation: http://www.ayqy.net/doc/css2-1/cover.html
GitHub: https://github.com/ayqy/CSS2-1
License: MIT. You can take it freely, but re-publishing is not recommended because subsequent error corrections are difficult to synchronize (having N buggy translation versions is not much better than having no translation at all).
Declaration
This document is a Simplified Chinese translation of the "Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification (W3C Recommendation 07 June 2011)".
Due to the limited level of the translator, errors may exist. The Chinese translation is for reference only; please refer to the official document for the accurate specification content. (If you find any errors during reading, please submit an Issue/PR or contact ayqy so they can be corrected promptly.)
During the translation process of this document (2016.3.29-2016.5.23), the CSS 2.2 specification made new progress (the first Working Draft was released on 2016.4.12). Currently (2016), the most widely supported version is still CSS 2.1 (i.e., this specification). For the latest situation regarding CSS specifications, see CSS.
Thanks to
Why?
See the original email below (Translator to w3c-translators); the content is not translated:
I have confirmed that another translation (the second link above) is ongoing (and I consulted it during this translation), but it seems something went wrong with it.(Many months passed away, but it turns to nowhere). So...just like the way Momdo Nakamura did it.
Comparing the completion level of the W3C Japanese documents, some things happen for a reason.
Finally
In 2 months, I just wanted to read through one of the frontend textbooks carefully (to give myself one more quality check before entering the workforce).
Also, W3C staff are very friendly and not scary at all, and there are some things that we FEers need to complete, aren't there?
nonsense
Some say our frontend circle is very impetuous, that newcomers have poor foundations and lack the spirit of older generations of programmers... Personally, I admit I really can't do 20 pull-ups, but some things happen for a reason.
I've been in contact with frontend for about 2 years—reading books, asking seniors for cultivation methods, accumulating knowledge, and digging into certain points... Now I'm about to "leave the factory" (my graduation thesis is right on the table; the timing is perfect), and on second thought, I feel quite insecure:
-
box model
-
line box
-
layout(position, overflow)
-
flow(in-flow/out of flow)
-
containing block
-
bfc
-
margin collapse
-
base line
-
writing mode
-
bidi
-
aural style sheet
-
...http://www.cnblogs.com/winter-cn/archive/2013/05/11/3072926.html
Are these things useful? Or useless? But as a frontend developer, this is absolutely basic skill, the foundation of foundations.
Initially, I also felt that "theoretical stuff" was useless. Is someone who knows BFC inherently stronger than me? Can't you handle page layout without knowing these things?
I gradually discovered that seniors with deep expertise "always talk about specifications" (only as a joke, of course). It's not that you'll be despised if you don't understand BFC, but if you want to go further, what you owe will have to be paid back sooner or later. Besides, as a frontend developer, how can it be acceptable to have never even read the textbook?
When I wanted to read the textbook (which was when translating CSS3 Selectors, 2015.3), I found that there was no Chinese version available... Of course, many people must have discovered this problem before me. The seniors have studied the spec and understand it much more deeply than I do, but they are very busy now. Yes, it's that deadlock—those with good technical skills don't write books, and those who write books don't have top-tier technical skills.
Fortunately, many seniors are very friendly; if you are willing to ask, they are willing to tell you. However, such an environment is not very friendly for newcomers entering the industry.
Comparing it to the completion level of the W3C Japanese documents, I was truly shocked.
These words shouldn't be spoken by a green frontend newcomer, but that is the reality.
No comments yet. Be the first to share your thoughts.