Merge pull request #10650 from creative-commoners/pulls/5/remove-tran…

…slatable

ENH Remove unused Translatable code

src/Core/Extensible.php

@@ -157,7 +157,7 @@ protected function defineExtensionMethods()
      * @see http://doc.silverstripe.org/framework/en/trunk/reference/dataextension
      * @param string $classOrExtension Class that should be extended - has to be a subclass of {@link Object}
      * @param string $extension Subclass of {@link Extension} with optional parameters
-     *  as a string, e.g. "Versioned" or "Translatable('Param')"
+     *  as a string, e.g. "Versioned"
      * @return bool Flag if the extension was added
      */
     public static function add_extension($classOrExtension, $extension = null)

src/ORM/DataQuery.php

@@ -331,7 +331,7 @@ public function getFinalisedQuery($queriedColumns = null)
             "RecordClassName"
         );
 
-        // TODO: Versioned, Translatable, SiteTreeSubsites, etc, could probably be better implemented as subclasses
+        // TODO: Versioned, SiteTreeSubsites, etc, could probably be better implemented as subclasses
         // of DataQuery
 
         $obj = Injector::inst()->get($this->dataClass);

src/ORM/FieldType/DBLocale.php

@@ -5,7 +5,7 @@
 use SilverStripe\i18n\i18n;
 
 /**
- * Locale database field, mainly used in {@link Translatable} extension.
+ * Locale database field
  *
  * @todo Allowing showing locale values in different languages through Nice()
  */

src/i18n/i18n.php

@@ -14,8 +14,6 @@
 /**
  * Base-class for storage and retrieval of translated entities.
  *
- * Please see the 'translatable' module for managing translations of database-content.
- *
  * <b>Usage</b>
  *
  * PHP:
@@ -37,8 +35,6 @@
  * </code>
  *
  * File-based i18n-translations always have a "locale" (e.g. 'en_US').
- * Common language names (e.g. 'en') are mainly used in the 'translatable' module
- * database-entities.
  *
  * <b>Text Collection</b>
  *