Minor update - May

This release adds official support for Moodle 5.2.

• Languages Added:
  Bulgarian, Lithuanian, Latin American Spanish and Estonian are now available as language options in the block.

Fixes:
A language fallback issue in the webReader UI causing vl_es to default to English instead of Spanish is resolved.

Minor update - December

New features:

• Mobile App Plugin:
  Our plugin for the Moodle app/Branded Moodle app/Moodle Workplace app will be available from this release. Note that the app integration must be enabled by a Moodle system administrator as well as by ReadSpeaker. Contact our support team for more information.


• Statistics:
  The plugin can now be configured to automatically save the course, section name, and page title, which will then show up in the usage stats in the ReadSpeaker customer portal. This is only available in the desktop plugin.


• Translation Source Language:
  It is now possible to configure the plugin to detect the source language based on the page that the content is on, or the language set in webReader. This is only available in the desktop plugin. (Note: Requires webReader update 3.8.7)


• Close the Floating Player:
  When the webReader player is launched from a sidebar block, it detaches and floats on top of the page. Before this update, there was no way to close the player, but we have now added a close button to it. This is only available in the desktop plugin.

Fixes and improvements:

• 
  

  Argentinian Voice Added:
  The Argentinian voice Alba has been added to the plugin for both desktop and the mobile app.

  
  


• 
  

  PHP warning changes:
  Fixed an issue where PHP warnings were appearing in some PHP versions.

  
  

Patch fix - April

• Fixed an issue with docReader proxy that caused documents that contained special characters (such as applied parameters) to not open correctly with docReader.

Fixed a typo issue when accessing a translation in settings which caused an error message to appear.

New features

• Added a setting which allows admin to set a restricted mode per block instance. When in restrictive mode, certain features can be disabled separately from default configuration (such as translation, dictionary etc) by the ReadSpeaker support team.


• Added setting which allows admin to use latest version of webReader for Education scripts. Intended to be used for testing before requesting script update to new version.


• Added setting for disabling webReader for Education when in edit mode.

Changes and fixes

• When using Snap or Boost themes, an additional parameter will be sent to the ReadSpeaker server for applying additional reading rules in order to improve reading experience. Will for example silence certain texts that did not make sense to read.


• Added additional reading languages:
  
  
  
  • English (New Zealand)
  
  
  • Latvian
  
  
  • Afrikaans
  
  
  • isiNdebele
  
  
  • isiXhosa
  
  
  • isiZulu
  
  
  • Sepedi
  
  
  • Sesotho
  
  
  • Setswana
  
  
  • Siswati
  
  
  • Tshivenda
  
  
  • Welsh
  
  
  • Xitsonga
  
  
  
  


• Switched to loading docReader script from customer specific folder to using r-catalogue instead, in order to improve future updates.


• Added sanitization of $_COOKIE usage in docReader proxy.


• Changed from using legacy docReader ID (letter combination) to using Enterprise customer ID (number combination) instead to follow modern implementation practice.


• Removed accesskey from Listen button HTML markup in order to conform to modern standards.

Fixes in version 2022112301

• Fixed an issue where the Listen button title text was not correctly set in the code.

Fixes in version 2022112201

• The translation/phrases used in the Listen button now follows the Moodle standard and is contained in individual language packs. The Listen button will now display the Listen/Listen to this page using ReadSpeaker in the same language set by the Moodle system/course/user. The webReader UI language will now also follow the Moodle UI and the uilang-parameter will be set for the player based on the Moodle system/course/user language selected. If a language is not found en_us will be used as a fallback.


• Corrected the references for configurations in the plugin to follow the Moodle standard.


• Changed use of random string function for docReader proxy component to use system build function instead.

Also made some improvements in terms of naming conventions, standardizing use of translations (using phrases from block instead of hardcoded values) and changes to some comments.

block_readspeaker_embhl

Moodle block which inserts a Listen button on pages that enable users to listen to content using ReadSpeaker text-to-speech functionality.

Requirements

This plugin requires Moodle 3.0+.

Motivation for this plugin

The block_readspeaker_embhl can be used to insert a block with a Listen button into pages to enable the functionality of ReadSpeaker webReader for Moodle.

Installation

Install the plugin to the folder
/blocks/block_readspeaker_embhl

See https://docs.moodle.org/en/Installing_plugins for details on installing Moodle plugins

Usage & Settings

After installing the plugin, it needs to be configured with customers specific details that you recevied from ReadSpeaker after purchasing a license.
You can view installation instructions and customer specific details by logging in to the ReadSpeaker portal at https://app.readspeaker.com/portal with the credentials you recieved from the ReadSpeaker support team.
If you do not remember your login or did not receive an email from the ReadSpeaker support team with login details, please contact your ReadSpeaker account manager or get in direct contact with the ReadSpeaker support team at: mailto:support@readspeaker.com.

License / Subscription details

This plugin requires a paid license with ReadSpeaker in order to use the webReader for Moodle and docReader functionality.
A license for using webReader for Moodle and docReader can be purchased by contacting ReadSpeaker: https://www.readspeaker.com/contact/.

Requirements

This is a paid plugin that requires a license with ReadSpeaker in order to use.

Requirements for the functionality of webReader for Moodle and docReader are outlined in the specification documentation for respective products whne you purchase a license.

For docReader it is important to note that since the functionality for the product relies on the docReader server fetching and parsing documents, the Moodle platform used must be publically available to the docReader server and there is no firewall or other measurement preventing the docReader proxy component (located in the plugin) for making a request towards the Moodle platform in order to retrieve the document and return it to the docReader server.