Main Page
Today is: Sunday, November 24 2024
3.144.249.63, Welcome to the OpenPLi Wiki
| Current version: 6.2 |
|---|
Attention
There is a new section in the Wiki named Problems and Solutions to hopefully improve the chance you finding a solution to problems you might encounter. As a consequence some content of the Tips and Tweaks section has moved over to this new section. Also both sections have been alphabetized, we hope this helps and improves the readability of the content.
Contents
OpenPLi - Installation and configuration:
• Supported Receivers
Overview of all supported receivers and how to flash a your receiver. Also there is a comparison table were many receivers are listed and are compared right down to component level, so you can make an easier choice if you want to buy one. Also there is a special table that gives the power consumption of many receivers.
• OpenPLi installation
Here will be explained how to install OpenPLi on your receiver, various methods are explained and below are the various links that you might need. The link to the what, how and why to backup is recommended.
• Backup
Before you update, upgrade or change anything it is good to have a backup. Here the plugins "Autobackup" (by default installed) and the "BackupSuite" (has to be installed) are explained.
• Cable settings information
Looking for network ID's, symbolrates and frequency's to scan your cable channels..? Here you can find the information of our cable provider.
• Channel Settings for satellite receivers
Channel settings file for various satellites.
• External device support
Here you will find a list of known external devices that are known to work with OpenPLi.
• Softcam Wiki
When you want to look at encrypted channels and not only Free to Air (FTA) you can use a softcam. In this section is explained how to install and use a few.
• Tips and Tweaks
Many useful tips on various stuff on working with OpenPLi, Putty, SSD useful or not, debugging, how to crashlog, etc. etc.
• Problems and Solutions
This section deals with all kind of problems and possible solutions. If you run into a problem using OpenPLi you can take a peak here to find a solution.
OpenPLi - Functions and default plugins
• Hidden functions
Some functions are not easy to find, but can be very helpful, here there are a few.
• HDMI-CEC
This feature can make your devices work better together, so like using one remote to control TV and receiver. Note it is turned off by default
• Hotkey
With this function Hotkeys can be (un)selected to make things easier.
• MountManager
Here the mountmanager is explained. It is used to mount (make) accessible external drives, like with a NAS or (the harddisk of) other receivers. Mounting means associating a storage device to a particular location in the directory tree.
• Plugin browser
If want to extend the functions of OpenPLi you can install plugins from the feed. Remember these plugins are not maintained by OpenPLi, so always backup before installing.
• Fallback remote receiver
This function gives you the option to use the tuners from another OpenPLi receiver, when they are wired or wireless (WiFi) connected. This way you can watch TV when there is no access to satellite or cable or expand your tuners.
• Webif
Information about the Webif (webinterface) and how to access and configure it.
OpenPLi - Information for advanced users
• Knowledge base
Many useful information on various subjects.
OpenPLi - Information for developers
• Information for Developers
• How to create a Bootlogo
OpenPLi - Information for translators
• Information for Translators
OpenPLi is always looking for help to have it translated properly in many languages. But we kindly ask you to translate in your native language or in a language that you are really familiar with. OpenPLi is not looking for automated translation jobs.
Quick start guide
- We recommend that you download and install PoEdit from this site (please consider to register it if you appreciate it): https://poedit.net/
- Once installed go into: Preferences - Advanced - suppress the wrap line option and tick preserve original file format
- Download the language file you want to work on from: https://github.com/OpenPLi/enigma2/tree/develop/po (click on the file name, it will show you the file content, press the RAW button and save it locally on your disk).
- Open it up with PoEdit
- You can start translating the file
- Save it, you will get 2 files xx.po and xx.mo (where xx is your language code)
- Upload your updated xx.po file to the forum and we will put it back into github for you: https://forums.openpli.org/forum/55-en-enduser-support/ (we don't need to xx.mo file only the xx.po is important for us).
How can I test my translation on my OpenPLi?
In order to test you translation work on you receiver, you will need a FTP access to it.
You can get a free FTP client from: https://filezilla-project.org/ (or any FTP client of your choice).
Advice: if you use FileZilla client go into Parameters - Transferts - FTP: file type : set it to Binary (this will avoid you many problems when using FTP).
- You have a local file that you have worked on called: xx.mo (where xx is your language code) rename it into: enigma2.mo
- Connect to your receiver and go to this path: /usr/share/enigma2/po
- There you will see a series of folders, one per language, enter the language that you are working on: /usr/share/enigma2/po/xx/LC_MESSAGES
- Rename the file already existing on your receiver enigma2.mo into enigma2.bak (this step is important if you want to be able to rollback your changes)
- Transfert your own enigma2.mo file
- Restart your receiver
- Enjoy your translation
My enigma2.mo gives trouble: how to rollback?
- If you have followed the previous step carefully, connect with FTP to you receiver go back into the folder, delete your enigma2.mo and rename the enigma2.bak into enigma2.mo
- Restart you receiver.
What are Fuzzy lines in PoEdit?
The po files are generated based on the translatable strings that are in the source code, but the source code evolves and the strings are subject to change.
So when the script detect that an already translated string is changed in the source code, it is marked as fuzzy, this mean that the string must be reviewed by the translators.
It can happen that the translation is still correct, so don't forgot to untick the fuzzy flag in PoEdit because a fuzzy string is never displayed, only validated translation are.
There is a mistake in the original strings that I want to translate, how can I fix it?
If you find a mistake in the original strings / sentences that you need to translate it is useless to try to fix it in the po file. The correction must done in the source code.
So please report the error on the OpenPLi forum and wait to have it fixed into the source code and the po files including the correction to be generated again.
You can continue to translate in between, just skip the erroneous strings.
Do I need to translate every strings?
Some strings, perhaps, doesn't need to be translated, you can of course decide to skip those strings and leave them untranslated. From my side, I'd like to have the po file that I manage always translated at 100%. Why? Because I'd like to see immediately the strings that I still need to translate, otherwise you will read over and over the untranslated strings. But it's up to you to decide.
My plugins are not translated, can I add manually the missing strings in the OpenPLi po files to have it translated too?
No never add manually missing strings/sentences into OpenPLi file to translate, for exemple plugin, because the po files are generated on a regular basis and every strings/sentences that is included in a po file but not found in the OpenPLi source code will just deleted. So you will lose your work.
Remark: I will explain later on how to properly translated plugins (stay tuned).
Can I edit po file without using PoEdit?
po files are just plain text, so yes of course any linux compatible text editor can do the job but PoEdit is real help to avoid some common mistake that you can make when editing it with a text editor.
PoEdit report warning in my po file, is it normal?
Yes, PoEdit can report warning that are not mistakes, for exemple a capital letter set when it is not in the original string, this is not blocking. If you are happy with you translation, don't care about warnings.
But if PoEdit report errors then you need to fix them, errors are important and will prevent you from saving the file. So you need to fix them all.
To be continued...
