-
Notifications
You must be signed in to change notification settings - Fork 6
Translating Canute into other languages and Braille codes
Canute 360 is designed as a 'dumb' e-book reader first and foremost, i.e. without smart features such as live conversion to Braille from non-Braille sources. As such Canute can support book files in any language or code so long as they are encoded in US BRL ASCII and stored in BRF files (see Changing the Canute's BRF ASCII encoding).
By default Canute loads into Unified English Braille Grade 2 and comes pre-loaded with UEB Grade 1 as an alternative. It is simple enough to learn how to use Canute and in a pinch it is possible to memorise the key commands to move between books without being fluent in the language.
However distributors or individuals will want to support their own language and/or code at some point, which will change the menu labels and the help files. It is also important to prioritise translating the manual.
The following assumes the reader is a distributor with professional translator and transcriber services on hand. Individuals can try this at their own risk, though we cannot offer support to non-professional individuals doing translation or transcription, or following the technical process.
The manual is the largest section of text to translate. This can be translated and transcribed without any technical knowledge of the Canute itself and is non-intrusive.
The original is kept publicly here: https://github.com/Bristol-Braille/canute-ui/wiki/Canute-360-User-Manual
If the translator clicks edit they will get the 'markdown' source file. We use this source to create the Word document version which is shipped as a paper copy with the units.
The paper copy also contains images which we licence from Techno-Vision Systems Ltd, which is generated from a DOCX file. Please contact BBT for permissions to edit the DOCX version if you want to include the images.
The next largest single piece of text is the paper Brailled quick-start guide included with the Canutes. This can be translated and transcribed without any technical knowledge of the Canute itself and is non-intrusive.
See the English version here: English Quick-start guide for Brailling.
Next and most complex is the user interface localisation. This process is technical and requires understanding of the Canute's software and making intrusive changes to the Canute's system.
Your translator/transcribers will need to be familiar with industry standard POT/PO/MO files (see below). Please check that your translators are familiar with them before assigning them the work.
Here is the source POT (PO template) file they will need to download to work from: https://github.com/Bristol-Braille/canute-ui/blob/master/ui/locale/canute.pot
And here is an example of a completed PO file for Uncontracted Unified English Braille: https://github.com/bristol-braille/canute-ui/blob/master/ui/locale/en_GB.UTF-8%40ueb1/LC_MESSAGES/canute.po
As they will see it needs to have the 'msgstr' entries filled in with Unicode Braille characters, with line breaks so they don't go over 40 cells.
It is important that the Braille lines do not exceed 40 cells (characters) or they will not show up properly on the Canute, which does not line wrap incorrectly formatted text.
Please see this README file for instructions on generating PO files for the Canute 360 (it can be done by other means but the method described therein is preferable): https://github.com/Bristol-Braille/canute-ui/tree/master/ui/locale
Once a new PO has been generated in your chosen language and code it will need to be loaded into the Canute. This is not as simple as adding a new PO file in; the existing POT and PO files will need to be adjusted too to reflect the new language/code option in the language menu.
If you are a distributor we can help with this process, either for loading onto existing machines you have as an upgrade or for adding to future machines before you receive them.
For doing it yourself as an individual please see Making changes to the Canute's software.