--- nfo/php/libs/org.netfrag.glib/DataSource/Locator.php	2003/03/11 03:05:01	1.19
+++ nfo/php/libs/org.netfrag.glib/DataSource/Locator.php	2003/03/11 03:17:37	1.20
@@ -21,9 +21,12 @@
  * <b>Cvs-Log:</b>
  *
  * <pre>
- * $Id: Locator.php,v 1.19 2003/03/11 03:05:01 joko Exp $
+ * $Id: Locator.php,v 1.20 2003/03/11 03:17:37 joko Exp $
  *
  * $Log: Locator.php,v $
+ * Revision 1.20  2003/03/11 03:17:37  joko
+ * + fixed metadata for phpDocumentor
+ *
  * Revision 1.19  2003/03/11 03:05:01  joko
  * + fixed metadata for phpDocumentor
  *
@@ -169,12 +172,13 @@
     * using metadata from $_options and some
     * other presets.
     *
-    * {@see build}, which acts as a dispatcher
-    * depending on $_options[datasource]. (main dispatching level)
+    * See {@link build}, which acts as a dispatcher
+    * depending on $_options[datasource]. <br>
+    * (main dispatching level)
     *
     * The structure of a full blown locator looks like this:
     *
-    * <code>
+    * <code><pre>
     *  $locator = array(
     *    type => '<your type specifying the datasource-type>',
     *    metadata => array(
@@ -182,14 +186,14 @@
     *    ),
     *    [dsn => '<your dsn markup>'],
     *  );
-    * </code>
+    * </pre></code>
     *
     * Example 1 - data is inside a rdbms, using a dsn to connect to it:
-    * <code>
+    * <pre><code>
     *  $locator = array(
     *    dsn => 'mysql://username:password@localhost/database',
     *  );
-    * </code>
+    * </code></pre>
     *
     * Example 2 - data is inside an odbms, reachable by doing remote procedure calls (rpc):
     * <code>