Beiträge von Spaeleus

  • Dreambox 920UHD and NasaTV UHD

    The NasaTV UHD channel has always been perfectly viewable on my 920.

    Since a couple of days the screen remains perfectly black (no video) while the audio is normally present.

    A streaming on PC via webif (VLC) works perfectly (audio and video present) and, always on PC, the playback of a recording is perfectly visible.

    On the Dreambox also the recording plays only the audio, while the screen remains black.

    Interestingly, if I zap directly to the channel the screen is always black, while if I tune to NasaTV HD and then switch to NasaTV UHD I always get a still image of the video broadcast at that moment.

    Below the stream data:



    I can't try with an OE2.6 box: can anyone confirm?

  • StartupToStandby mit erweiterter Funktion - StartupToIdle für DreamOS

    Zitat von Sven H

    In the next version i will support translate to other languages.

    Of course, the Italian translation is already available :winking_face: for when you want it...


    BTW, in StartupToIdleConfiguration.py:57

    ther is a little typo that might concern translations:


    self.list.append(getConfigListEntry(_("activate consolen debug output"), config.plugins.startuptoidle.showdebuginfo))


    I think it should be "console".


    Thank you again and have a nice day!

  • StartupToStandby mit erweiterter Funktion - StartupToIdle für DreamOS

    Zitat von Sven H

    Thanks for feedback :thumbs_up:


    There is also a third situation to test :winking_face:

    Power cut on standby (DeepStandby).

    Damn, I forgot about that :sleeping_face:

    Here it is.

    Simulated power failure during standby

  • StartupToStandby mit erweiterter Funktion - StartupToIdle für DreamOS

    Just tested on my 920.

    Simulated power failure with active box:

    Simulated power failure with box in idle mode:

    Great work! :thumbs_up:

  • SettingsCleaner-Plugin (DreamOS)

    Hi.

    Yes, those entries were not active settings.


    I removed them manually, restarted enigma2 and all is working fine.

    Now the plugin doesn't show the entries anymore, they have been removed.



    The mystery remains as to why it was impossible to remove entries from the plugin, either by selecting them all or by trying to delete one at a time.

    Anyway, thanks for everything!


    Have a nice day

  • SettingsCleaner-Plugin (DreamOS)

    Hi.

    It seems that not all settings can be removed.

    I recently manually edited my unicable.xml to add the unicable matrix I currently use, which was not present.

    Your plugin showed me the presence of three no longer active entries linked to the previous tuner configuration.

    Although I have tried several times to remove them, the entries are still present, without any errors being displayed (the same with v1.0.7)

    Is there any chance of getting a log of the operations to understand where the problem is?

    Here is a screenshot of the affected entries:



    BTW, here my update for italian translation based upon v1.0.8 :winking_face:

    Thanks!


    SettingsCleaner-v1.0.8-it.zip

  • SamsungVolumeRemote-Plugin

    If could help, here is my results:

    Box: dm920uhd with latest Merlin

    TV: Samsung QE55Q90RATXZT

    Soundbar: Samsung Q6R-Series (optical)

    The response to volume changes is immediate, almost comparable to the response time of the samsung remote control.

    In allegato i miei risultati da journalctl -f -u enigma2 e dal ping del televisore.


    Attached are my results from journalctl -f -u enigma2 and from pinging the TV.


    journalctl.log


    ping.log

  • how to make a plugin use its own translation

    I apologize for the silly question. :frowning_face:

    Let's assume we have an untranslated enigma2 plugin (e.g. MyPlugin), and we want to equip it with one or more translations.

    Let's assume that the plugin syntax is correctly structured to make the strings we are interested in translatable.

    Just as an example:

    Code
    # plugin.py
def print_some_strings():
    print(_("Hello world"))
    print(_("This is a translatable string"))
if __name__=='__plugin__':
    print_some_strings()

    Let's assume that we have extracted all the translatable strings from the sources, created a .po file, translated the strings, and correctly compiled the .mo file that we are going to place in the right directory

    ...MyPlugin/locale/<language>/LC_MESSAGES/MyPlugin.mo

    Using the file __init__.py we provide the information necessary to associate the path of the translations

    Example:

    What else needs to be done for the plugin code to use the translations dedicated to it?

    Thanks in advance for the help :winking_face:

  • enigma2 and enigma2 plugins online translation

    Hi.

    As I've already reported, even though my translation for enigma2.plugin has been completed, weblate goes on proposing me some strings (every day, always the same ones) as untranslated / to be verified.

    A deeper analysis allowed me to verify the following:


    1) String not yet translated into Italian (no reference, original string only in Dutch, Serbian, English, German, Italian, Spanish, Turkish)

    Make it more skin friendly

    2) Strings already translated in italian but to be verified (no reference, source strings only in Dutch, Serbian, English, German, Italian, Spanish, Turkish)

    No result from LDIF

    No result from Outlook export

    Searching in Outlook export...

    3) String already translated in italian but to be verified (no reference, source strings in every language)

    movies found!

    4) String already translated in italian but to be verified (no reference, source string only in English, Italian, Polish)

    search EPG from history...


    Is it possible to check if those strings are still necessary and why do these strings always come back to me?


    Thanks!

  • enigma2 and enigma2 plugins online translation

    Zitat von dhwz

    1) we have nothing to to with E2openPlugins

    2) translations from the upstream repository e.g EMC will be removed in a future version, the translations on opendreambox will be the leading/only translation.

    1) I know, but so why import their string for translation? Let them live their lives...

    2) It seems just what I was asking for... :winking_face:

    Zitat von Reichi

    We have some VERY reliant translators in numerous languages.

    Give them a "single point of translation" is why we change how translations are handled in plugins!


    It just makes their life (a lot) easier!

    True, but with some side effect, almost in some languages.

    The same string in different contexts can have very different meanings.

    A single available translation can be an extremely limiting factor, when the language being translated has, for example, different forms for masculine and feminine, singular and plural. Not to mention that some languages even have additional distinctions.

    Thus a single translation option risks being a "all purposes unisex form", perhaps simpler, but certainly less elegant and accurate.

    If I could choose, I would prefer that each plugin had its own separate translation: any translation tool (from Weblate to Poedit, just to mention two examples) has a translation memory that can provide a very good support for repeated strings, making the work much easier.

    Let me be clear, this is not meant to be a criticism, just my thoughts, my two cents.

    Another problem then are chained strings: for translators they can be a real nightmare, producing comical effects at best, tragic or misleading at worst.

    Something like writing "table book on is the".

    Again, I'm just expressing my opinion, about which I'd like to know the thoughts of other translators, especially those who are facing the same problems as me.