Sitellite Sitellite CMS → 5.0.4

Comments and changes to this ticket

• 

  semias April 15th, 2011 @ 09:45 AM

  There is another variant of this "issue".

  For instance: when generating .spt files by defining te spt contents as a string variable, the {intl } tags are ignored by the translation indexer.

  Solving this is done by adding a _translate() function, which explicitly runs through all strings in a php file and adds them to the translation table.

  example:
  

  source: /saf/lib/GUI/DataGrid.php
  
  var $template = '
  {if obj.addUrl}
      <p><a href="{addUrl}?collection={collection}">{intl Add Item}</a></p>
  {end if}
  ';
  
  function _translate () {
      intl_get ('Add Item');
  }
  

  This way, the {intl } tags are discovered and the text is made translatable.

• 

  semias April 22nd, 2011 @ 03:49 AM

  Sometimes javascript is called using a "define" function. Here the javascript is encapsulated in quotes, so the PHP code has to be inserted in a different manner.
  Example:
  

  Source: /inc/app/sitemailer2/conf/properties.php
  
  $intl_confirm = intl_get("Are you sure you want to delete this item?");
  
  define ('CMS_JS_DELETE_CONFIRM', '<script language="javascript" type="text/javascript">
  <!--
  
  function cms_delete_confirm () {
      return confirm ("' . $intl_confirm . '");
  }
  
  // -->
  </script>');
  

• 

  semias April 22nd, 2011 @ 05:28 AM

  • State changed from “new” to “open”

  Every alert and confirm pop-up window has been internationalized.
  There is one exception located at:
  

  /inc/app/siteblog/lib/Filters.php:50-52
  

  It is possible to translate the given strings, but for some reason they are not translated in the actual view. (which is located in the control panel > content > blog comments)

• 

  semias April 22nd, 2011 @ 08:08 AM

  • State changed from “open” to “resolved”