OMG! luv <3 ???? (°_°)

¡¡¡¡Yo lo vi por un momento!!! pero luego recorde ponerme los lentes y todo volvio a la normalidad

Chicos, no se han dado cuenta?... el gran FSM esta tratando de enviarnos señales, solo los elegidos pueden verlo, recibamos con alegría y devoción.

yo vi ponnies... pero en la noche ya se arreglo todo!

no he cambiado mi navegador ni nada, solo le tuve que dar ctrl+F5 como 4 veces y se reparo.

Aquí el parche

Have withstood pain to create many weapons.

w00W! lo que hace Photoshop verdad

saludox

http://img296.imageshack.us/my.php?image=clabluv39qi.jpg


http://img209.imageshack.us/my.php?image=clabponnies6qj.jpg

Para mi que es una broma de Team de clab

No puede ser que los que NO somos swat...etc lo veamos y los que son Swat y otros del team de clab NO lo vean

Es mi punto de vista

Jajaja. Siempre quice ver un error de mis maestros.

This page is not Valid XHTML 1.0 Transitional!

Below are the results of checking this document for XML well-formedness and validity.

1. Error Line 51 column 41: there is no attribute "name".

... <li id="tutoriales" name="tutoriales"><a href="http://www.cristal

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.

✉
2. Error Line 52 column 40: there is no attribute "name".

<ul id="submenu" name="submenu">

✉
3. Warning Line 156 column 0: character "<" is the first character of a delimiter but occurred as data.

<...</p>

This message may appear in several cases:
* You tried to include the "<" character in your page: you should escape it as "&lt;"
* You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
* Another possibility is that you forgot to close quotes in a previous tag.

✉
4. Warning Line 269 column 190: cannot generate system identifier for general entity "oacu...".

...enu de navegaci&oacute;n con selecci&oacu...</a></li>

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

✉
5. Error Line 269 column 190: general entity "oacu..." not defined and no default entity.

...enu de navegaci&oacute;n con selecci&oacu...</a></li>

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

✉
6. Warning Line 269 column 197: reference not terminated by REFC delimiter.

...navegaci&oacute;n con selecci&oacu...</a></li>

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

✉
7. Error Line 269 column 197: reference to entity "oacu..." for which no system identifier could be generated.

...navegaci&oacute;n con selecci&oacu...</a></li>

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

✉
8. Info Line 269 column 189: entity was defined here.

...Menu de navegaci&oacute;n con selecci&oacu...</a></li>

I am the bone of my sword.
Steel is my body, and fire is my blood.
I have created over a thousand blades.
Unknown to death.
Nor known to life.
Have withstood pain to create many weapons.
Yet, those hands will never hold anything.
So as I pray, "Unlimited Blade Works".

yo no veo nada... pero si dijera "Reyner apesta.. " creanme que yo seria muy feliz!

al pasar por tu casa
me ladraron los perros
quise agarrar una piedra
y que me embarro los dedos