7 цитат Стива Джобса, которые изменят вашу жизнь
И самое главное, подтянут ваш английский! Из этих цитат вы вынесете для себя очень много полезных фраз и слов.
1. Your time is limited. Don’t waste it living someone else’s life.
Ваше время ограничено. Не тратьте его впустую, живя чьей-то чужой жизнью.
2. I think if you do something and it turns out pretty good, then you should go do something else wonderful, not dwell on it for too long. Just figure out what’s next.
Я думаю, что если вы что-то делаете, и это получается довольно хорошо, вам следует пойти сделать что-то еще замечательнее, не останавливайтесь на этом слишком долго. Просто выясните, что будет следующим.
3. My favorite things in life don’t cost any money. It’s really clear that the most precious resource we all have is time.
Мои любимые вещи в жизни не стоят никаких денег. Совершенно ясно, что самый ценный ресурс, который у нас есть — это наше время.
4. Being the richest man in the cemetery doesn’t matter to me … Going to bed at night saying we’ve done something wonderful … that’s what matters to me.
Быть самым богатым человеком на кладбище не имеет значения для меня. ложиться спать по ночам, говоря себе, что мы сделали что-то замечательное . вот что действительно важно.
5. Sometimes when you innovate, you make mistakes. It is best to admit them quickly, and get on with improving your other innovations.
Иногда, когда вы вводите новшества, вы делаете ошибки. Лучше всего признать их быстро, и получить вместе с тем улучшением других ваших инноваций.
6. Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple. But it’s worth it in the end because once you get there, you can move mountains.
Что-то простое может быть сложнее, чем что-то сложное: вы должны упорно работать, чтобы сделать Ваше мышление достаточно чистым, чтобы сделать что-то простое. Но это того стоит, потому что, как только вы добьетесь чистоты в сознании, вы сможете сдвинуть горы.
7. You have to be burning with an idea, or a problem, or a wrong that you want to right. If you’re not passionate enough from the start, you’ll never stick it out.
Вы должны гореть идеей, или проблемой, или ошибкой, которую вы хотите исправить. Если Вы не достаточно увлечены с самого начала, вы никогда не укрепите положение.
Ошибки валидации — как исправить?
Подскажите пожалуйста не могу разобраться в скрипте,проверяю через http://validator.w3.org/check
выдает непонятные ошибки вот например что-то вроде этого
Как исправить??
Validation Output: 4 Errors
Line 4, Column 9: document type does not allow element «HEAD» here
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a «style» element in the «body» section instead of inside «head» — or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s «self-closing» tags for «meta» and «link» in the «head» section of a HTML document may cause the parser to infer the end of the «head» section and the beginning of the «body» section (where «link» and «meta» are not allowed; hence the reported error).
Line 8, Column 11: document type does not allow element «BODY» here
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a «style» element in the «body» section instead of inside «head» — or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s «self-closing» tags for «meta» and «link» in the «head» section of a HTML document may cause the parser to infer the end of the «head» section and the beginning of the «body» section (where «link» and «meta» are not allowed; hence the reported error).
Line 24, Column 7: «HEAD» not finished but containing element ended
✉
Line 24, Column 7: end tag for «HTML» which is not finished
✉
Most likely, you nested tags and closed them in the wrong order. For example
is not acceptable, as must be closed before
. Acceptable nesting is:
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is «not finished», not complete. For instance, in HTML the element must contain a child element, lists require appropriate list items (
- and
- require
; requires and ), and so on.
Ошибки валидации
коллеги, пмогите разобраться, что не так при валидации в W3C Line 113, Column 12: there is no.
Ошибки микроразметки валидации Яндекса
Добрый вечер, подскажите пожалуйста, сделал микроразметку shema.org на странице.
Ошибки валидации при микроразметке на сайте услуг
Добрый вечер, уважаемые форумчане! Подскажите пожалуйста юному подавану, как справиться с этими.
При валидации ошибки, хотя все правильно
Помогите с исправление кода пожалуйста!Много ошибок » Атрибут” align “для элемента” p » является.
Line 4, Column 9: document type does not allow element «HEAD» here
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a «style» element in the «body» section instead of inside «head» — or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s «self-closing» tags for «meta» and «link» in the «head» section of a HTML document may cause the parser to infer the end of the «head» section and the beginning of the «body» section (where «link» and «meta» are not allowed; hence the reported error).
Line 8, Column 11: document type does not allow element «BODY» here
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a «style» element in the «body» section instead of inside «head» — or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s «self-closing» tags for «meta» and «link» in the «head» section of a HTML document may cause the parser to infer the end of the «head» section and the beginning of the «body» section (where «link» and «meta» are not allowed; hence the reported error).
Line 10, Column 9: NET-enabling start-tag requires SHORTTAG YES
✉
For the current document, the validator interprets strings like according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the «/» character in such contexts. NB: If you expect to be interpreted as an XML-compatible «self-closing» tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more «/». Example: W3C. In such cases, the solution is to put quotation marks around the value.
Line 12, Column 9: NET-enabling start-tag requires SHORTTAG YES
✉
For the current document, the validator interprets strings like according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the «/» character in such contexts. NB: If you expect to be interpreted as an XML-compatible «self-closing» tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more «/». Example: W3C. In such cases, the solution is to put quotation marks around the value.
Line 16, Column 17: NET-enabling start-tag requires SHORTTAG YES
✉
For the current document, the validator interprets strings like according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the «/» character in such contexts. NB: If you expect to be interpreted as an XML-compatible «self-closing» tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more «/». Example: W3C. In such cases, the solution is to put quotation marks around the value.
Line 19, Column 7: NET-enabling start-tag requires SHORTTAG YES
✉
For the current document, the validator interprets strings like according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the «/» character in such contexts. NB: If you expect to be interpreted as an XML-compatible «self-closing» tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more «/». Example: W3C. In such cases, the solution is to put quotation marks around the value.
Line 21, Column 116: duplicate specification of attribute «TITLE»
…age» alt=»картинка отсутствует» title=»image» height=»200″ width=»300″ border…
✉
You have specified an attribute more than once. Example: Using the «height» attribute twice on the same «img» tag.
Line 23, Column 63: there is no attribute «HEIGHT»
…enter» border=»4″ width=»1356″ height=»768″ bordercolor=»blue» cellpadding=»1…
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the «Strict» document type with a document that uses frames (e.g. you must use the «Transitional» document type to get the «target» attribute), or by using vendor proprietary extensions such as «marginheight» (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 23, Column 82: there is no attribute «BORDERCOLOR»
…width=»1356″ height=»768″ bordercolor=»blue» cellpadding=»10″ cellspacing=»0″>
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the «Strict» document type with a document that uses frames (e.g. you must use the «Transitional» document type to get the «target» attribute), or by using vendor proprietary extensions such as «marginheight» (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 31, Column 58: document type does not allow element «P» here; missing one of «APPLET», «OBJECT», «MAP», «IFRAME», «BUTTON» start-tag
…
КиберФорум — компьютер…
✉
The mentioned element is not allowed to appear in the context in which you’ve placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you’ve forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as «
» or »