Permalink
Browse files

Test larger text for common documentation

  • Loading branch information...
1 parent 1b5a784 commit b16257c8777033e98b08e5f3f3736a49e678962c @beberlei beberlei committed Jul 3, 2011
Showing with 5 additions and 2 deletions.
  1. +4 −1 en/_static/default.css
  2. +1 −1 en/reference/annotations.rst
View
@@ -80,6 +80,8 @@ abbr,acronym { border:0; }
div.document {
margin-right: 30px;
+ font-size: 12pt;
+ text-align: left !important;
}
div.documentwrapper {
@@ -319,7 +321,8 @@ pre {
tt {
background-color: #ecf0f3;
padding: 0 1px 0 1px;
- font-size: 1.4em;
+ /*font-size: 1.4em;*/
+ font-weight: bold;
}
th {
@@ -60,7 +60,7 @@ In this snippet you can see a variety of different docblock annotations:
How are these annotations loaded? From looking at the code you could guess that the ORM Mapping, Assert Validation and the fully qualified annotation can just be loaded using
the defined PHP autoloaders. This is not the case however: For error handling reasons every check for class existance inside the AnnotationReader sets the second parameter $autoload
of ``class_exists($name, $autoload)`` to false. To work flawlessly the AnnotationReader requires silent autoloaders which many autoloaders are not. Silent autoloading is NOT
-part of the [PSR-0 specification](http://groups.google.com/group/php-standards/web/psr-0-final-proposal) for autoloading.
+part of the `PSR-0 specification <http://groups.google.com/group/php-standards/web/psr-0-final-proposal>`_ for autoloading.
This is why Doctrine Annotations uses its own autoloading mechanism through a global registry. If you are wondering about the annotation registry being global,
there is no other way to solve the architectural problems of autoloading annotation classes in a straightforward fashion. Additionally if you think about PHP

0 comments on commit b16257c

Please sign in to comment.